This chapter provides an overview of the JD Edwards BI Publisher Report Definitions application (P95620) and discusses how to:
Create BI Publisher report definitions.
Modify BI Publisher report definitions.
Copy BI Publisher report definitions.
Manage BI Publisher objects in Object Management Workbench.
Configure BI Publisher objects for Object Management Workbench.
Understanding JD Edwards EnterpriseOne BI Publisher Report Definitions
Report definitions specify the information that BI Publisher requires to process and deliver BI Publisher output. The details in a report definition include:
The UBE and optional version to use as the data source.
Associated templates, transformations, and localizations.
Output types.
Language options.
Bursting options.
Delivery options.
You use the BI Publisher Report Definitions application (P95620) to create, update, copy, and delete report definitions. After a report definition is created, it can be submitted to BI Publisher to produce the defined output types.
Note. Before creating a report definition, ensure that the necessary templates have been created and uploaded into the BI Publisher Object Repository (P95600).
See Creating JD Edwards EnterpriseOne Embedded BI Publisher Objects.
Creating BI Publisher Report DefinitionsThis section provides an overview of the report definition process and discusses how to:
Define the source of data, template names, and transformations.
Define languages and output types.
Define bursting and delivery options.

Understanding the Report Definition Process
Although the BI Publisher Report Definitions application (P95620) is available on both the web client and the Microsoft Windows client, you must use the Microsoft Windows client to create a new report definition or to modify an existing report definition.
Adding a report definition is a three-step process. The first step consists of entering the required details for the report definition and defining the source of data and the templates to process. Additionally, if a template uses one or more transformations, they are defined in this step.
Second, you define the output types that a user can select when submitting the report definition. You also define the default output types and default languages for the XML output.
In the third step, you define the optional bursting field for the report definition, as well as the delivery options for the output. A report definition must comply with the following conditions to allow bursting to be configured:
Templates of type TL (Microsoft Excel) and TS (XSL) cannot be used.
A transformation cannot be used.
Microsoft PowerPoint and XML output types cannot be used.

Forms Used to Create BI Publisher Report Definitions
|
Form Name |
FormID |
Navigation |
Usage |
|
BI Publisher Report Definitions |
W95620A |
On JD Edwards Solution Explorer EnterpriseOne Life Cycle Tools task view, select Report Management, BI Publisher, Report Definitions or enter P95620 in the Fast Path field. |
Select a BI Publisher report definition. |
|
Add Report Definition |
W95620C |
Click Add on the BI Publisher Report Definitions form. |
Add a report definition. |
|
Add Report Definition-Languages and Output Types |
W95620H |
Click Next on the Add Report Definition form. |
Define available output types, default output types, and default languages. |
|
Add Report Definition-Bursting and Delivery |
W95620J |
Click Next on the Add Report Definitions-Languages and Output Types form. |
Define an optional bursting field for the report definition, and delivery details for the output. |
|
Update Report Definition |
W95620C |
On the BI Publisher Report Definitions form, select a record in the grid and then click Select. |
Update a report definition. |

Defining Source of Data, Template Names, and Transformations
Access the Add Report Definition form.
|
Report Definition |
Enter the name of the report definition, using a maximum of 10 characters. Oracle recommends that report definition names start with the letters RD. |
|
Description |
Enter a meaningful description for the report definition. |
|
Product Code |
Select a product code from the 55–59 client reserved range. |
|
Product System Code |
Select a product code that indicates where the reporting data resides. |
|
Source Type |
The source type (user-defined code (UDC) H95|RY) appears automatically and is based on the source type of the data that the report definition uses. |
|
Source UBE |
Enter the name of the Report Design Aid (RDA) report template that is used to generate data for the report definition. |
|
Source Version |
(Optional) Enter the name of a version only if the report definition is limited to one version of the UBE. If a version is not specified, the user will have to select a version at submission time. |
|
Blind Submission |
(Optional) Leave this option blank to prompt the user with the available output, delivery, and language options when submitting the report definition to BI Publisher. If blind submission is selected, the user is not allowed to change the report definition options when submitting the report definition. |
|
Template Name |
Enter the name of the template that you want to associate with the report definition. |
|
Template Description |
The template description appears automatically and cannot be changed. |
|
Active Status |
Active Status is determined by the effective dates of the template. The status appears automatically and indicates whether the template is active or inactive. |
|
Transformation Name |
(Optional) Enter the name of the transformation that you want to associate with the report description. |
|
Transformation Description |
The transformation description appears automatically and cannot be changed. |
|
Active Status |
Active Status is determined by the effective dates of the transformation. The status appears automatically and indicates whether the transformation is active or inactive. |
After entering the required report definition details, click Next to move to the Languages and Output Types form.

Defining Languages and Output Types
Access the Languages and Output Types form.
Note. The templates, translations, and localizations that are attached to the report definition determine the languages that appear in the Object Language column.
|
Available Output Types |
Select the output types to be available to users when they are submitting the report definition. The type of template attached to the report definition determines which output types are available. |
|
Default Output Types |
Select the default output types that will be selected when the report definition is submitted. Default output types are not enabled unless they are first defined as available output types. If the report definition is defined as blind submission, the default values indicate the type of output that will be produced when the report definition is submitted to BI Publisher. Note. When you run a report definition, the system does not automatically generate a PDF. |
|
*ALL Active Languages |
If this option is selected, all languages for the defined templates, localized templates, and translations that are active will process when a report definition is submitted to BI Publisher. Languages associated with the templates are displayed in the grid. |
|
User Preference Language |
If this option is selected, when a report definition is submitted to BI Publisher and the sign on user's language preference has been defined, the language preference for the sign on user is processed. A user's language preference is defined in the user's system profile. The User Preference Language option is not enabled if *ALL Active Languages is selected. |
|
Object Language |
A code that indicates the language defined for a template, localization, or translation. |
|
Language Description |
A description of the language code assigned to a template, localization, or translation. |
The output types available depend on the type of template that is used, as described in this table:
|
Template Type |
Output Type |
|
RTF |
PDF, RTF, Excel, HTML |
|
|
|
|
EFT/EDI (eText) |
eText |
|
Excel |
Excel |
|
XSL |
XML |
After defining the output types and languages, click Next to move to the Add Report Definition-Bursting and Delivery form.

Defining Bursting and Delivery Options
Access the Add Report Definitions-Bursting and Delivery form.
|
Burst Report |
(Optional) Select this option if bursting will be performed for a report definition. |
|
Burst Field |
A report definition can burst on any level break section defined within the batch or report version that is used as its source of data. Typically, when you burst a report, you break on a level break header section. The field must contain the complete XPath as it appears in the XML data output that was created from the batch process. |
|
Printer |
Select to direct output to a printer. |
|
Address Book Number E-Mail |
Select to deliver output to the email address that is associated with a specific Address Book number. When a report definition is submitted to BI Publisher, all output produced is to the email address. |
|
Distribution List Type |
Select to deliver output to all members of the distribution list type who are associated with the provided Address Book number. If the distribution list type is not entered, the output is sent to the primary email address associated with the Address Book number. |
|
E-Mail Address |
Select to deliver output to a specific email address. When the report definition is submitted to BI Publisher and an email delivery address has been defined, all output produced is sent to the defined email address. |
|
Data Driven E-Mail |
Select to deliver the output to email recipients based on the data generated by the source batch version or report version. |
|
Distribution List Type |
Select to deliver output to all members of a distribution list and distribution list type that are associated with the data. If the distribution list type is not entered, the output is sent to the primary email address associated with the Address Book number. |
|
Data Driven Recipient |
Select to deliver the report definition output to the recipients as determined by the data from a particular data item within the XML output. |
After defining bursting and delivery details, click End to save the report definition and exit.
Modifying BI Publisher Report Definitions
Access the BI Publisher Report Definitions form on the Microsoft Windows client.
On the BI Publisher Report Definitions form, select a report definition in the grid and then click Select.
On the Update Report Definition form, you can modify these options:
Description
Product code
Product system code
Source UBE
Version
Template
To modify output or language options, select Output/Languages from the Form menu.
On the Update Report Definition-Languages and Output types form, add options, modify options, or delete options, and then click OK.
To modify bursting or delivery options, select Burst/Delivery from the Form menu.
On the Update Report Definition-Bursting and Delivery form, add options, modify options, or delete options, and then click OK.
On the Update Report Definition form, click OK to save the report definition modifications.
Note. Modifying the Source UBE, Version, or Template fields could invalidate the languages, output types, bursting, and delivery options that were defined previously for the report definition. If you modify any of these values, the Languages and Output Types form and the Bursting and Delivery form will appear automatically, enabling you to make any necessary changes.
Copying BI Publisher Report Definitions
Copying and modifying a report definition might be more efficient than creating a new, but similar, report definition. The copy feature is available only in the Microsoft Windows version of the BI Publisher Report Definitions application.
To copy a report definition:
Enter P95620 in the Fast Path field.
On the BI Publisher Report Definitions form, select a report definition and then click Copy.
On the Copy Report Definition form, enter a name and description for the new report definition.
If the report definition will be submitted without user input, click Blind Submission.
After completing the required information, click OK.
Managing BI Publisher Objects in Object Management Workbench
When you access the BI Publisher Repository (P95600) or BI Publisher Report Definitions (P95620) applications from JD Edwards Solution Explorer, the objects that you create are added to your default project in Object Management Workbench (OMW). As non-Object Librarian objects, templates and report definitions are not available to users in other environments until they are advanced through project statuses and, finally, transferred to a data source. To advance the status of an object, you must move it from your default project to a project.
In addition to being available in JD Edwards Solution Explorer, you can also access the BI Publisher Repository and BI Publisher Report Definitions applications through OMW. To add new objects within OMW, select an OMW project and then click Add. Select either Report Definition or BI Publisher Object, as this form illustrates:
When you click OK, either the BI Publisher Repository application or the BI Publisher Report Definition application launches, depending on the type of object that you are creating.
Once the objects exist in OMW, you can modify them by clicking the Design button, which will launch the appropriate application. You can also use OMW to copy or delete templates and report definitions, as you would with other OMW objects.
See Getting Started with JD Edwards EnterpriseOne OMW.

Searching for BI Publisher Objects
To search for BI Publisher objects or report definitions within OMW, in the Category field select either XML Publisher Objects or Report Definitions. After selecting the category, the Search Type field enables you to search by object name, description, or system code.
When you perform an Advanced Search within OMW, BI Publisher Objects are type XMLP and report definitions are type RPDF.
Configuring BI Publisher Objects for Object Management Workbench
To perform actions on BI Publisher objects and report definitions within OMW projects, you must configure object transfer activity rules. For each object type on which you want to perform an action, you must define this information:
Project statuses at which users can add, design, and delete objects.
Status changes at which objects will be transferred.
Project statuses at which object tokens are released.
See Getting Started with JD Edwards EnterpriseOne OMW.