You are here: Blog JD Edwards - BI Publisher JD Edwards Enterprise One 9.1 & BI Publisher Integration

JD Edwards Enterprise One 9.1 & BI Publisher Integration Featured

Rate this item
(3 votes)

BI Publisher for JD Edwards Enterpriseone - Online Training

There are three ways, JDE users can use the BI Publisher

  • Embedded BI Publisher Reporting
  • BI Publisher Reporting with JD Edwards Data Access Driver
  • EnterpriseOne One View Reporting

Embedded BI Publisher Reporting

Embedded BI Publisher reporting is driven by a JD Edwards EnterpriseOne batch application (UBE)

When to use Embedded BI Publisher Reporting

  • The report needs to update, insert, or delete JD Edwards EnterpriseOne data.

    Examples of report processes that update JD Edwards EnterpriseOne data are: updating the product shipped date, advancing the sales order status, and updating the statement print date.
  • The report needs to perform JD Edwards Enterprise One business logic.

    Examples of business logic include: determining the correct pricing for a product, computing an employee's salary or benefits, and calculating commissions for sales staff.

BI Publisher Reporting with JD Edwards Data Access Driver

When to use BI Publisher Reporting with JD Edwards Data Access Driver

BI Publisher reporting with JD Edwards Data Access Driver should be used under the following circumstances:

The requested report is not part of a standard JD Edwards EnterpriseOne business process, or the requirements for the report change over time. The following are examples of these types of reports:

  • The CIO requests a list of current open Account Receivables.
  • A manager wants to review year-to-date budget amounts compared to actuals.
  • A manager requests a report showing current inventory levels.
  • Requests for other typical ad-hoc reports.

JD Edwards EnterpriseOne One View Reporting

  • Oracle's JD Edwards EnterpriseOne One View Reporting is a real time operational reporting solution.
  • One View Reporting is all about delivering the right data to the right person, right now
  • One View Reporting enables users to access and personalize transaction data into lists, charts, graphs and tables thus simplifying the consumption of information.

One View Reporting Across the Enterprise

  • Total 178 Prebuilt Reports available across all the applications.
  • User can add new custom reports based on the requirements
  • These Report can be accessed through …
    1. Standard Enterprise One Applications
    2. Data Browser
    3. Custom Enterprise Applications

One View Reporting for Customer Ledger Enquiry Application







Add Custom Report to One View...




Creating a Embedded BI Publisher Report…

Report Definitions

  • Report definitions specify the information that BI Publisher requires to process and deliver output.
  • The details in a report definition include:
    • The UBE and optional version to use as the source of data
    • Associated templates, transformations, and localizations
    • Output types
    • Language options
    • Bursting options
    • Delivery options

Creating customized reports using BI Publisher involves these steps:

Step 1 – Use Oracle’s BI Publisher Template Builder, Microsoft Excel, Microsoft Word, or Adobe Acrobat to create a blank template file. In Word, this would be a blank .rtf file.

Step 2 – Add an object to the JD Edwards XML Publisher Object Repository (P95600), using the template name for the object name.
After clicking OK, you will be prompted to upload the rtf file.
Then you need to set the Effective dates for the template. Pick the current date/time for start, and leave the end date blank to specify no expiration.

Step 3 Using a FAT client, create a report definition in the JD Edwards XML Publisher Report Definition application (P95620), associating the source batch application (UBE) and the template. Use Blind Submission here as an option.
Name and description
Source UBE that will extract the data
Optionally select a version if the Report Definition is limited to one specific version

Step 3 (cont)
After clicking “Next”, set the types of outputs you want to allow, and which one is the default.
Set the Language preference to use.

Step 3 (cont)
After clicking “Next”, set the bursting and delivery options. These are actually optional, NOT required.
Select whether to burst
Select which field to burst on
Requires full XPath to be typed Typically want to burst based on a level break header section
Printing: only supported for PDF output & PostScript printers
Email: based on single email address, Addr. Book number, or by data from the report (via Xpath)
Finally, click “End” to finish the RD


Step 6 – Use the XML data to design the template in the desktop application that you used to create the template (such as Word).
In Word, after loading your blank document, from the BI Publisher Ribbon, “Load Data” section, click “Sample XML” to load the XML the server generated in the previous step.
Proceed with template design. (*part of the next session)

BIP Embedded Output Repository

Creating Oracle BI Publisher Reports with JD Edwards Data Access Driver

To implement JD Edwards EnterpriseOne reporting using the Data Access Driver with Oracle Business Intelligence (BI) Publisher

  • Install Oracle Business Intelligence Enterprise Edition (OBIEE) 11g.
  • Install the JD Edwards EnterpriseOne Data Access Driver.
  • Register the JD Edwards EnterpriseOne Data Access Driver in Server Manager.
  • Configure the JDBC Driver (Data Access Driver) in Oracle BI Publisher

Configuring the JDBC Driver in Oracle Business Intelligence Publisher

To configure the JDBC Driver in Oracle BI Publisher:
Start the Oracle BI Publisher server.
Sign in to Oracle BI Publisher Enterprise Console.
Click the Administration tab.
Under the Data Sources section, select JDBC Connection.
The Data Sources form appears, with the JDBC tab selected.
Click Add Data Source.
Enter the following values on the Add Data Source form:

Data Sources list displays newly added data source

Naming Conventions

Read 23945 times

Leave a comment

Make sure you enter the (*) required information where indicated.
Basic HTML code is allowed.