Skip navigation

NewFeature.pngThe Financial Accounting Standards Board (FASB) and the International Accounting Standards Board (IASB) created a joint standard regarding the recognition of revenue.


Business processes and financial standards outline when you can recognize revenue for the amounts you bill to customers. You cannot recognize revenue for billed amounts or Cost of Goods Sold (COGS) amounts associated with the billing amount until the performance obligation to the customer is satisfied.

Every company and each of their customers must agree to the terms that constitute the completion of a performance obligation. Performance obligations can be satisfied in different ways and at different times. Examples include:


  • Retail
    • The customer takes possession of the goods and is billed at the time of the sale. The performance obligation is complete and revenue is recognized at billing.
  • Services
    • Services are completed for a customer and they sign off on the work. The performance obligation is complete at the time the customer signs off on the work and revenue is recognized at billing.
  • Distribution
    • Goods are shipped to a customer and they are billed at the same time. The performance obligation is not complete until the customer takes possession of the goods and accepts them as complete. Therefore, you cannot recognize revenue at the time of billing.
    • The system accounts for the billing amount as a performance liability. Once the customer takes possession and accepts the goods, the revenue is recognized and the performance liability cleared. Any COGS amounts associated with the billing amount is also considered a performance liability and can only be recognized once the performance obligation is complete.
  • Construction
    • In some industries, such as construction, customers are billed for portions of the contract that are complete, or for time and materials as they occur. Revenue recognition is tied to the terms of the
      contract for each type of billing line. Some billing lines can be recognized immediately and others may be considered a performance liability until other terms have been met.

For more information, please review New Enhancement For FASB – Revenue Recognition in Accounts Receivable For Release 9.1 (Doc ID 2030115.1).

The JD Edwards EnterpriseOne Health & Safety Module (P54HS) has been updated with a few features.


  • OVR Statistics Filter

OVR Statistics Filter provides a way to narrow down Safety Hours Group content. Health and Safety One View Reporting Statistics Inquiry Filter - P54HS260 (Doc ID 2036281.1) provides information on the filter and how to obtain the ESU.

  • Incident Report One Click Printing

Incident Report one click printing allows you to print a detailed incident report by selecting the printer icon in Manage Incidents (P54HS00).  Refer to Detailed Incident Report (R54HS400) - One Click Print Icon in Manage Incidents (Doc ID 2036258.1) for more details.

ic-Cloud-red.pngWe are pleased to announce the availability of JD Edwards EnterpriseOne enhancements to ensure JD Edwards EnterpriseOne standard business interfaces, such as business services and embedded UI can be leveraged by Oracle Sales Cloud customers to coexist. Two new One View Reports are also now available.


The enhancements include:

  • Business Services - a new method on Customer Manager – getCustomerV3 that provides the ability to search by customer address.
  • Business Services - new methods on SalesOrder Manager – getSalesOrderV4 and processSalesOrderV5 that support query and updates of opportunity ID info through BSSV.
  • Sales Order Entry (P42101)  – added the Opportunity ID field (OPPID) to the grid for queries by Opportunity ID.
  • One View Sales to Date Inquiry (P42272)  – added two new OVR reports, Sales by Opportunity and Opportunity Trends.
  • Item Batch Outbound (R4101ZO) – provide new XML export capability of the Item Master Information.


For more information on the integration and affected objects, refer to the following documents:

  • JD Edwards EnterpriseOne Announces Enhancements to Support Oracle Sales Cloud (Doc ID 1906361.1)
  • Integrating Oracle Sales Cloud with JD Edwards EnterpriseOne (Doc ID 1645923.1)

budget.jpgBudget Checking is fairly simple to understand if budgets are not being accumulated. If budgets are not set to accumulate in the Purchase Order Entry (P4310) processing options, then the only budget considered will be the one attached to the expense account on the purchase order detail line.


The majority of questions and issues are with regard to budget accumulation. One thing that many users are not aware of when upgrading is that E1 fundamentally changed how accumulation works in release 8.9 and above.


In releases XE and 8.0, budget accumulation was done by object account. This method allows users to set budgets based upon object account hierarchies.


The functionality changed beginning with EnterpriseOne release 8.9.  Beginning with release 8.9, budget accumulation occurs at the business unit level. This means that every account within the business unit can lend its budget to any other account within the business unit, regardless of object account set up.


There are two ways that budgets are accumulated in E1:

    1. Accumulation is done based upon object account. This is the functionality in releases XE, 8.9, and 9.1*.

    2. Accumulation is done based upon business unit. This is the functionality in releases 8.9, 8.10, 8.11, 8.11SP1, 8.12, 9.0, and 9.1*.


*Note that release 9.1 is in both examples above. In 9.1 Bug 18235598 changes the accumulation logic to accumulate by Object Account rather than Business Unit. If the ESU for Bug 18235598 is applied in your 9.1 environment, it is critical to understand the difference before testing Budget Accumulation.


For additional information on budget accumulation and budget checking, review the following documents:

You use JD Edwards EnterpriseOne Contract and Service Billing from Oracle to bill customers for services and goods rendered. JD Edwards Contract and Service Billing offers a suite of features to accommodate the intricacies of both interdivisional and customer billing.  Have you wondered which may be more suited for your billing needs? 

How To Understand the Difference Between Service Billing (48S) and Contract Billing (52) In EnterpriseOne (Doc ID 626871.1) may help you decide which application or a combination of applications would work best for your billing needs.  

This document gives you a comparison of the major billing processes such as Workfile Generation, Revenue Generation, Invoice Generation and Creating AR and GL Entries.  It also shows the major functionality differences in setup and Invoice Generation, as well as an outline of the advantages and disadvantages of Service Billing and Contract Billing. 

The quote, “The Only Thing That Is Constant Is Change -” by Heraclitus is ever so true when it comes to computing.  Looking around today, the cell phone technology is more powerful than computers a few years ago and as computers change, likewise the software.

If you have grown with the JD Edwards EnterpriseOne (E1) software and Internet Explorer (IE) through the years, you are well aware of our use of activeX controls and the subsequent requirement of compatibility view with IE10 and IE11. 

Compatibility view has been more of a recent requirement which is fortunately no more, but is still causing mischief and misunderstanding depending on your E1 tools release.

As Microsoft has improved on the browser, they have gone from the Standard Mode to a new Edge Mode with IE11. With the E1 code being built to run on standard mode, this required the use of Compatibility view for all of the E1 functionality to work correctly.

With the release of 9.1.5, the IE code in E1 has been uplifted to utilize the edge IE coding and html5 throughout E1, which means we no longer use the old IE standard mode. When reviewing the minimum technical requirements (MTR) via Certifications on MyOracle Support (MOS) this is reflected by support for only IE10 and IE11 with 9.1.5. 



Supported TR

Compatibility View

IE 8

8.98.1 –


IE 9 –


IE 10

9.1.2 –


IE 10

9.1.5 - Onward


IE 11

9.1.4 –


IE 11

9.1.5 - Onward



Based on the requirements in the table and your installed release, open Internet Explorer and click on the drop down for settings, Compatibility View is in the list.  From here it is easy to add or remove the URL based on the tools release requirements.


For 9.1.5, when compatibility view is turned off, the catch is ensuring not only the removal of any E1 URL previously added but removing the check box for "Display intranet sites in Compatibility View". 

Please note: A symptom in 9.1.5 of the check box or URL not being removed is a missing preference item for the Enable Simplified Row/Form Exits. 

Filter Blog

By date: By tag:

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see for instructions.