2 Understanding Batch Versions

This chapter contains the following topics:

2.1 Report Writing

Oracle JD Edwards EnterpriseOne provides reports across many systems to meet your business needs, including:

  • JD Edwards EnterpriseOne Financial Management

  • JD Edwards EnterpriseOne Human Capital Management

  • JD Edwards EnterpriseOne Logistic

  • JD Edwards EnterpriseOne Manufacturing

JD Edwards EnterpriseOne reports can be processed and viewed in these formats:

  • Online in PDF

  • In hardcopy

    Report can be sent to a printer.

  • In a spreadsheet program

    Reports can be exported to a spreadsheet program.

To help you meet all of your business needs, you can create versions of these reports. Using the JD Edwards EnterpriseOne Batch Versions application on either the Microsoft Windows client (P98305) or the web client (P98305W), you can create versions to present specific information that is vital to your business.

2.2 Report Processing

You cannot process a report without a batch version. From the Microsoft Windows client, batch versions are submitted for processing and can be processed either locally or on the server. Typically, servers are faster, so processing on a server is more efficient. From the web client, batch versions are submitted on the server only. Once submitted, a batch version runs without user interaction. You do not interact with the report again until processing is complete.

Once you have submitted a batch version for processing, you have no control over the flow of the attached logic. You must make changes to the flow of logic in Oracle's JD Edwards EnterpriseOne Report Design Aid (RDA) and resubmit the batch version.

2.3 Table Conversion Processing

You run table conversions by submitting batch versions. Table conversions are a type of batch process that enables you to rapidly manipulate the data in tables. Like batch applications, table conversions include a template and associated versions. You can override some of the properties within a version at runtime.

This table describes the conversion types used by the Oracle's JD Edwards EnterpriseOne Table Conversion tool to manipulate data:

Conversion Type Description
Data Conversion Enables you to transfer or copy data from an input table or business view into output tables using the logic necessary to perform the transfer.

You can also use Data Conversion to update records in a table or business view.
Data Copy Enables you to copy tables from one data source or environment to another data source or environment, when the tables are identical.
Data Copy with Table Input Enables you to copy tables based on information from an input table.

For example, the input table might provide information about which tables are copied, the location to where they are copied, and so on.
Batch Delete Enables you to delete records from a table or business view.

See "Table Conversions" in the JD Edwards EnterpriseOne Tools Table Conversion Guide.

2.4 Output Management

Output management refers to the different output options that you have available for reports, such as:

  • File types

    You can output reports to different file types such as, PDF, OSA, and CSV.

  • Printers

    You can output a report to multiple printers, locally or globally. You can send versions of a report to different printer drawers or to printers across the country.

  • Forms and paper sizes

    You can output reports to forms and define custom paper sizes.

JD Edwards EnterpriseOne accommodates simple output processes such as viewing a report online or sending it to a network printer.

SeeJD Edwards EnterpriseOne Tools Report Printing Administration Technologies Guide.

2.5 Report Components

A report exists as a set of specifications that are read by the JD Edwards EnterpriseOne batch engine for processing. You can create variations of a report template using batch versions. The first step in creating a report is to create a report object within JD Edwards EnterpriseOne. This report is actually a template from which multiple versions can be created.

See JD Edwards EnterpriseOne Tools Report Design Aid Guide.

2.5.1 Report Templates

Report templates are the master specifications created in RDA. These specifications describe the report to the batch engine and define how the data is selected, sorted, displayed, and formatted.

RDA includes a Report Director that you can use to guide you through the report development process. You begin the report development process by selecting:

  • Sections to include in the report.

  • An appropriate business view.

  • Fields for the section layout.

  • Records to be included in the report.

2.5.2 Batch Versions

Batch versions read the master specifications from the report template. The sections and fields that you select in the report template appear in the associated batch versions. However, batch versions typically differ slightly from the report template. You can define different data selection, data sequencing, and processing options for each batch version.

There are also several report specifications that can be overwritten at the version level, including:

  • Layout

  • Data selection

  • Event rules

  • Database output

  • Data sequencing

Batch versions enable you to preserve template integrity while providing custom processing to meet a specific business need. Instead of creating a separate report template to provide multiple variations of a report, you can create one report template with multiple batch versions. For example, you might design a monthly variance report that contains totals for the entire company. If you need to run a quarterly variance report that includes only data for the Western region, you can create a version of the report template and define data selection to meet the requirement.

Batch versions process the specifications read from the report template and any changes that are overwritten in the version. Batch versions first read the master specifications from the report template, then override these specification with the version specifications. You can create additional batch versions by either adding a new version or copying an existing version.

2.6 Batch Versions

In JD Edwards EnterpriseOne, the design for report templates and batch processes are stored in the report template specifications. Batch versions are variations on the report template. They use all of the same report definition information as the template but can also contain changes to the way the report is processed or displayed. Depending on how security is applied to the JD Edwards EnterpriseOne applications, end users can select different batch versions or create new batch versions based on business requirements.

Versions are a powerful and convenient way to modify the behavior of reports. Typically, administrators control the creation, modification, and location of the initial batch version files. When you upgrade JD Edwards EnterpriseOne or a specific application to a new release level, you can apply the existing batch versions without additional modification.

When you process a batch application (that is, when you submit a batch job) you must use a batch version. Depending on how the report was designed, when you submit the batch version you might have the option to override:

  • Processing option values

  • Data sequencing

  • Data selection

  • Default locations

For example, you have a report that prints financial information that is required by two different audiences: an American subsidiary and a French subsidiary. For the American subsidiary, you can create a batch version that displays financial information in U.S. dollars for a specific time period and formats the report for American-sized paper. For the French subsidiary, you can create a version that displays financial information in euros for a different time period and formats the report for European-sized paper. You can also display additional information in the report by inserting additional fields into the batch version.

2.6.1 Characteristics of Batch Versions

This table defines the characteristics of batch versions:

Characteristics Definition
Data sequencing defined at the version level. For example, you can create multiple batch versions of a single report template: one version might sort checks by date, one by check number, one by address number, and one that sorts checks by amount.
Data selection defined at the version level. For example, you can specify which records to fetch for each version, such as Business Unit 10-30 and 70, or all address book records where Category 1 is equal to North.
Additions or overrides in the version. You can modify batch versions to add or override functionality attached to the section of a report template. At the section level, you can override section layout, data selection, data sequencing, event rules, and database output. You cannot delete sections in a version that exist in the report template, however, you can hide unwanted sections.
A specific set of processing option values. For example, you can set a general ledger post processing option value to print a different account number format on the report.
Change functionality. For example, you can set processing options to purge records to a history file after a report runs.
Change input parameters. For example, you can set processing options to specify which category code to use when processing a report and you can define different report interconnect values for different batch versions.
Define data. For example, you can set a processing option to define the fiscal year for which you want to run a report. You can also define the number of aging days in an accounts receivable aging report.
Additional detail sections. For example, you can include additional detail sections, each with a different business view attached.

2.6.2 Batch Versions Created on the Web Client

You can create new batch versions of a report on the web client. You can use the Add and Copy options on the Work With Batch Versions - Available Versions form to create a batch version. To change the data selection, data sequencing, or processing options of a version, select Data Selection, Data Sequencing, or Processing Options from the Row menu.

You cannot create a new version, or copy an existing version, of a table conversion on the web client.

2.7 JD Edwards Naming Conventions

To provide consistency for developers and users, all JD Edwards EnterpriseOne objects follow standard naming conventions. The naming conventions require that each object, such as a table, report, interactive application, or menu, has a unique name. The naming conventions help you identify object types and help prevent users from creating objects with duplicate names.

See "Understanding JD Edwards EnterpriseOne Naming Conventions" in the JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide.