UBEs for JD Edwards EnterpriseOne Report Definitions

Use these guidelines when designing a JD Edwards EnterpriseOne report to use as the batch application (UBE) for a JD Edwards EnterpriseOne report definition. Use the JD Edwards EnterpriseOne Report Design Aid to create the UBE.

• Report Constants

  Avoid including any report constants in the UBE layout, unless the constant is used in the BI Publisher report layout.

• Report Variables

  Report variable names act as a root element data tag in the resulting XML file. Make the report variable name as representative as possible. The data dictionary alias, type and length should be included in the report variable name. Report variables must be unique in the report design.

• Section Names

  Section names act as group element data tag in the resulting XML file. Make the section name as representative as possible.

• Level Breaks

  Level breaks represent the grouping in the XML structure. Include as many level breaks as the number of groups you will have in the BI Publisher layout. It is preferable to have level break footer totals processed by the UBE to avoid calculation during BI Publisher processing.

• Sorting

  Sort the data in the UBE design as you want it to appear in the BI Publisher report. Sorting in the BI Publisher template will affect performance and should be avoided.

• Page Related Data

  Headers, Footers, Brought Forward and Carried Forward sections should be avoided. Any data related to a page should not be included in the UBE design. The UBE used in a BI Publisher report definition does not generate pages as the output, it generates an XML file without pages. Any page related information loses context when the XML file is generated.

• Conditional Sections

  Group similar information in conditional sections. For example, Address Book information could be in an AddressBookInformation Section called from the Customer or from the Supplier sections.

• Data Formatting

  Ensure the data is formatted properly in the UBE. BI Publisher does not have access to user preferences, so the date format and the amount decimal separator must be handled by the UBE engine.