Skip navigation

JD Edwards EnterpriseOne One View Reporting is a real time operational reporting solution designed specifically for end users. An intuitive interface empowers users to access and personalize transactional data into lists, charts, graphs, and tables. With One View Reporting, users can select the data fields and perform specific data selection from within JD Edwards EnterpriseOne applications and leverage the layout capabilities within Oracle BI Publisher to define the report output formatting. It was first introduced with JD Edwards EnterpriseOne Applications release 9.1 and later it was also offered for Applications release 9.0.


One View Reporting enables end users to create and run One View reports based on Business Views using search criteria in applications (standard or custom Find Browse Forms) or even in Data Browser. These reports are typically specific to the user or role and are those that the user will run on a daily, weekly, or other periodic basis as part of their normal activities. With this type of report users are allowed a high degree of personalization regarding data selection, sequencing, data columns included, and data visualization (charts, tables, graphs). These end-user reports improve user productivity by providing users with better visibility into operational data as part of their standard day-to-day business process. Common use cases are customer reports, supplier reports, sales reports, and employee reports.


Together with the One View reporting feature a number of dedicated standard One View Applications and Reports were added for various JD Edwards EnterpriseOne modules. In Financial Management new One View Applications were added for General Accounting, Accounts Payable and Accounts Receivable. Standard One View Reports for various use cases are delivered with each One View Application.


General Accounting


  • One View G/L Inquiry (P09219). One View G/L Inquiry can be used to analyze General Ledger transactions. It is based on the One View G/L Inquiry (F0911-F0901-F0006) Business View (V09219), which includes columns from the Account Ledger table (F0911), Account Master table (F0901), and Business Unit Master table (F0006).
  • One View Account Balance Inquiry application (P09217). One View Account Balance Inquiry can be used to report on account balances. It is based on the One View Account Balance Inquiry business view (V09217), which includes columns from the Account Balance table (F0902), F0901, and F0006.


Accounts Receivable


  • One View Customer Ledger Inquiry application (P03B2022). One View Customer Ledger Inquiry uses the One View Customer Ledger Inquiry Business View (V03B11I) (which includes columns from the Customer Ledger table (F03B11) and Customer Line of Business Master table (F03012)) to analyze the Customer Ledger.
  • One View Customer Receipt/Draft Inquiry application (P03B720). One View Receipt/Draft Inquiry should be used to inquire on Receipt/Draft transactions. It is based on the One View Receipt Draft Inquiry Business View (V03B720), which includes columns from the Receipt Detail table (F03B14), Receipt Header table (F03B13), and Customer Master table (F03012).


Accounts Payable


  • One View Supplier Ledger Inquiry application (P042022). One View Supplier Ledger Inquiry can be used to analyze supplier ledger transactions. It is based on the One View Supplier Ledger Inquiry Business View (V042022), which includes columns from the Accounts Payable Ledger table (F0411), Supplier Master table (F0401), and the Address Book table (F0101).
  • One View Supplier Payment Inquiry application (P04720). One View Supplier Payment Inquiry can be used to inquire on supplier payment transactions. It is based on the One View Supplier Payment Inquiry Business View (V04720), which includes columns from the Payment Detail table (F0414), Payment Header table (F0413), F0401, and F0101.


Additional details about this feature can be found in the following documents:


  • One View Reporting for JD Edwards EnterpriseOne (Doc ID 1464568.2)
  • JD Edwards EnterpriseOne One View Reporting Now Available for 9.0 (Doc ID 1522883.1)


For a complete reference check the guides.

Year-end processing is in full effect!


The late leg/reg ESU for payroll year-end processing is available.  Please refer to 2015 Payroll Year-End Processing Late Leg/Reg ESU (Doc ID 1612477.1) for ESU content and downloading details.



JDE1 HCM Oracle Year-End Support

Do you ever wonder if your ESU Install is successful?  Do you know what to look for to determine that the ESU install was successful?  Search no further...

A Diagnostic Assistant has been provided to verify the Payroll Year-End ESU Specification Merge (R98700) has no merged objects. Access Diagnostic Assistant (DA) for validating the ESU Spec Merge for JD Edwards EnterpriseOne Accounts Payable/GL (1099), Canadian Payroll (T4) and US Payroll (W2) Year End (Doc ID 2092042.2) for the utility download and instructions.

If you pay employees in the state of Pennsylvania this message is for you!


The year-end process requires that you run the repost, R07136.  We have found that when the repost is run, the incorrect PSD information is updated to the F06136B (tax information) is history file for PA.  The incorrect information will affect the information reported on your W2.

R07136 Incorrectly Reposts PA Remit Area And PSD Detail Values In The F06136B (Doc ID 2095515.1) for details on bugs and resolutions.

Announcement.pngUDC 04/ST, if not maintained to match Publication 1220, may cause IRSTAX.txt file with combined Federal and State Electronic Filing to be rejected.

See Correct Participating States for Combined Federal and State Electronic Filing To Update UDC 04/ST Correctly (Doc ID 2096393.1) to manually update UDC table 04/ST before you file with combined Federal and State Electronic Filing to the IRS.

The difference between a lot controlled item and a serialized item is that  quantities for receipt or shipment from a lot number are only limited by availability. It is not possible to receive or ship a quantity greater than 1 of a specific serial number.


EnterpriseOne provides two methods for managing serial numbered items. One method, the older method. stores a serial number in the Serial Number (F4220) table, which has a one-to-many relationship with the Item Location (F41021) table. The second method, the newer method, stores the Serial Number in the Lot/Serial field (LOTN) in the Item Location (F41021) table. Using the newer method, it is possible to track a both a lot number and serial number by linking to the Memo Lot 1/2/3 (LOT1/LOT2/LOT3) fields in the Lot Master (F4108).


The differences in setup and functionality of the two methods of serial number control are significant and are explored  in greater detail in our new knowledge document Lot Processing and Serial Number Control (Doc ID 2094021.2).

A Transfer Order is an internal sales order used to transfer inventory from one warehouse (branch) to another. The Transfer Order program (P4210) creates both a sales order in the "From Branch", the shipping branch, and a purchase order in the "To Branch", the receiving branch.


Transfer Orders (ST/OT) are designed to be used to move quantities from one Branch/Plant to another. Non-stock items, direct ship items and other items that do not have quantities in the Item Balance (F41021) table are not appropriate for transfer orders and are  not supported. Also, kits containing a parent item with K stocking type and a bill of material with component items are not supported for Transfer Orders. The individual component items can be used for transfer orders provided the line types meet the line type requirements for Transfer Orders.


The default document types created for transfer orders are ST (sales order) and OT (purchase order), and are often referred to as an ST/OT order. When a sales transfer order (ST) order is created, the purchase transfer order (OT) is also created, regardless of whether the "Generate Purchase Order" flag is activated or not in the line type constants (P40205). Additionally, the Transfer/Direct Ship/Intercompany field (SDS011) in the Sales Order Detail file (F4211) is marked with a '1', indicating a transfer order.


Transfer Orders have unique setup considerations compared with regular customer sales orders which will be discussed in detail in document Transfer Order (ST/OT) (Doc ID 2094796.2).

In compliance with the year-end reporting requirements of the federal government, companies must prepare and submit several forms. Your JD Edwards EnterpriseOne system includes programs to produce these required forms, as well as to generate electronic files.


The JD Edwards Year-End programs are available as an electronic software update (ESU). An ESU is a downloadable package used to correct problems that a specific defect bug reports or to deliver enhancements to year-end objects. The package is delivered in a self-extracting executable file, and you must merge it into the appropriate JD Edwards EnterpriseOne environment. The attached diagnostic assistant will determine if the ESU was applied successfully.


To run the diagnostic utility:

  •     Access the Install tab
  •     Follow the steps on the Use section
  •     Review the results

For all of the details on this new tool please see Diagnostic Assistant (DA) for Validating the ESU Spec Merge for JD Edwards EnterpriseOne Accounts Payable / GL (1099), Canadian Payroll (T4), and US Payroll (W2) Year End (Doc ID 2092042.2).

CA ICON.pngThe Oracle Technology Stack provides the foundation for this application. Change Assistant allows a single point of entry to facilitate administration of software updates & fixes. This application utilizes a navigational tree to help manage your deployment processes and enhance your search capability over Update Center and My Oracle Support information.


  • The Change Assistant tool allows a single point of entry to facilitate administration of software updates & fixes
  • Change Assistant centralizes and economizes the process of searching, identifying, downloading, and deploying many types of software fixes (e.g., ESUs, Tools Releases, etc.).
  • Release independent JAVA-based tool but greater functionality in newer release.
  • Processes remain same (i.e., applying an ESU) Change Assistant makes process easier.
  • Can also be used to deploy Business Accelerators (OBAs) and Configuration Solutions (created with Configuration Assistant).

The change Assistant can be downloaded from the update Center.

  1. On Update Center home page click on the “Download the Change Assistant Application”.

CA Download.jpg

   2. Install the JAVA and then Change Assistant.

CA Download1.jpg

Java Download page :

JAVA Download Page.jpg

Change Assistant Download:

Change Assistant jnlp Save File.jpg


  1. Double Click on the Change Assistant downloaded file.
  2. Set Preferences in Change Assistant :

User Id: Oracle update Center/SSO  User ID/Email

Password: Oracle Support SSO password

User Name: Your User Name

Email: Email Address


Click Next

  • Default Timeout in Millisecond is 30000
  • Number of Retries: 5

         (Keep it As it is)


  • Enter Download Directory where all the Updates ( ESUs, ASUs, ASIs ) will be downloaded on your machine at the time of deployment.
  • Selecting “Include Dependencies” will download and deploy dependent ESUs automatically.


  • Enter the Log Directory for Change Assistant:


  • Accept the Terms of Use and Click Finish


For further details on Change Assistant. Go through the below mentioned documents :

  • JD Edwards Diagnostic Tools: Change Assistant (Doc ID 2012571.1)
  • Change Assistant Overview and Benefits (Doc ID 1536620.1)

For details on troubleshooting the Change Assistant Install issues :

  • Troubleshooting EnterpriseOne and World Change Assistant Tool Installation (Doc ID 637515.1)

For details on troubleshooting the Change Assistant Launch Issues:

  • Troubleshooting Errors And Known Issues Found When Launching Change Assistant (Doc ID 1264247.1)

In case you are facing some issues other than what are recorded in above documents or My Oracle Support documentation, please raise a Technical SR with the

  • How to create a Technical Software Service Request (SR) (Doc ID 1321379.1)

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.