This chapter contains the following topics:
You can change Oracle JD Edwards EnterpriseOne batch versions without changing the associated report template or table conversion. When you change the specifications at the version level, you should include a description of the modifications in the Version Detail field on the Version Detail form. The description should include the differences between the report template, or table conversion, and the version specifications.
This section provides overviews of overriding specifications in batch versions and overriding properties for versions of table conversions, lists prerequisites, and discusses how to:
Override specifications in batch versions.
Change the properties of versions for table conversions.
Override the report specifications at the version level to change the design of a batch version. The changes you make to the specifications of the batch version do not affect the report template or any other batch version associated with the report template. The override specifications feature is a section level option. You must override specifications for each section that requires modification. You can override specifications by type. This table describes the different specification override options:
| Specification Type | Description |
|---|---|
| Section Layout | Enables you to change section properties, delete columns, add columns, move columns, or change column headings on a batch version. |
| Section Data Selection | Enables you to define specific data selection by version. For example, a version for customer information only and a version for employee information only. |
| Section Event Rules | Enables you to define specific event rules by version. For example, you can define a version for employee information with a calculated percentage raise amount, date title, or Balance Auditor. |
| Section Database Output | Enables you to use a different database mapping than the one defined in the report template. |
| Section Sort Sequence | Enables you to sort data differently than the report template. For example, you can define the data in a version to sort by name rather than by address number. |
Once you have selected to override one of the specification types in a batch version, modifications that you make of the same specification type in the report template are not read by the overridden version. For example, if you override the section layout in a section of a batch version, then add a new field to that same section in the report template, the new field is not read by the batch version.
When you submit a version to process a table conversion, you can override the conversion properties. This table describes the different conversion properties that can be overridden:
Before you begin changing the design of batch versions, ensure that you:
Create a report template.
Create a batch version of the report template.
Ensure that JD Edwards EnterpriseOne Report Design Aid (RDA) is not open.
Before you begin changing properties of versions for table conversions, ensure that you set up a table conversion template.
Access the Work with Batch Versions - Available Versions form.
Enter the name of a report or batch process in the Batch Application field and click Find.
In the detail area, select a batch version that is checked out and with which you want to work.
From the Row menu, select Advanced.
On the Advanced Operations form, select Design Version from the Row menu.
RDA opens reading the master specifications from the report template.
On the JD Edwards Report Design Aid form, click in a section and select Override Version Specifications from the Section menu.
Select the appropriate overrides, and click OK.
The changes that you make affect only the version on the local workstation.
To make these changes available to the enterprise, you must check in the version. If you do not want to check in the version, erase the checkout so that other users can check out the version.
Access the Work With Batch Versions - Available Versions form.
Enter the name of the table conversion in the Batch Application field and click Find.
Add a new version of the table conversion.
On the JD Edwards Table Conversion Version Design form, select the Tools tab and click Properties.
On the Properties form, review and override the environments, data selection, table options, and logging options specified in the table conversion.
These forms are similar to the forms in JD Edwards EnterpriseOne Table Conversion Design.
To use debug logging, select the Debug Logging tab to perform these steps:
To use the jde.ini settings for the trace level and row-by-row conversion process, select the Use ini settings for trace level and number of rows to process option. This option ensures that the system uses the settings contained in the jde.ini instead of the values entered in the Trace Level and Number of Rows fields.
To override the trace level in the jde.ini, clear the Use ini settings for trace level and number of rows to process option. Enter a value from 0 to 10 in the Trace Level field.
To convert a specific number of records (for example, if you want to test the table conversion), clear the Use ini settings for trace level and number of rows to process option. Enter the number of rows to convert in the Number of Rows field. If you enter 0 in this field, the system processes all rows.
This option corresponds to the StopAfterRow setting in the jde.ini. If you enter a value here, you override any specifications in the jde.ini.