Understanding Processing Option Templates
Processing options designate parameters that are used by reports. When reports are processed, the processing option template passes values that are entered by the user. These values are used by the event rules that are attached to the report to perform customized processing.
Processing option templates are included in Oracle's JD Edwards EnterpriseOne. You can also create custom processing option templates to meet your business needs.
You can use processing options to:
Control how reports process data.
Set up default values.
Customize batch versions for different companies or even different users.
Control the format of reports.
Control page breaks for reports.
Control totaling for reports.
Processing option templates can contain one or multiple parameters. You can add tabs, with descriptive names, to the processing option template to categorize the parameters. For example, you can name a tab Print to describe parameters that affect how a report prints or which printer is used.
At runtime, processing option templates display the set of tabs which are referred to as pages. When you select a tab, the page changes to display the set of processing options for that category.
You can add comments to processing options. The comment should describe the purpose of the available parameters and any information that is required by the user. For example, Use this processing option to indicate the preferred format of labels for printing.
Each processing option page displays parameters that are accompanied by a description. The description often includes valid values when appropriate. Add data items to the processing option page to create the parameters. You can change the description of the data item to better describe the purpose of the parameter. For example, Enter 1 to print single column labels and 2 to print two-column labels.
Each data item that you include on the processing option template includes a member name. This name is located on the Properties form of each parameter. You want to modify the member name of generic fields to represent their specific purpose. Modify the member name to be a descriptive name that you will recognize in Event Rules Design. The recommended naming convention for member names is:
Add the Hungarian Notation at the beginning of the name.
Append the data item alias at the end of the name, preceded by an underline.
Do not include spaces in the name.
For example, the Add [Y/N] data item is often used in processing options for entering a yes or no value. The alias for the Add [Y/N] data item is A, and the field is defined as a character data type. With that in mind, you might modify the member name to read cDisplayCommentsColumn_A.