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. |