1. Data Structure Design Guide
  2. Understanding Processing Options Templates

Understanding Processing Options Templates

A processing option template is a special kind of data structure. It contains one or more data dictionary items. It can also contain one or more tab pages that you can use to categorize data items.

Each tab page has a descriptive title.

You can add data items on processing option templates. Each data item contains a descriptive label and an edit field.

You can also add comments on a tab page. A comment is a text string that is displayed on the processing option dialog. It helps users understand the data items.

At runtime, a processing option dialog displays a set of tabs. Each tab represents a category of processing options. When you click the tab header, the tab body displays the set of processing options for that category.

Important: Changes to processing option text can conflict with changes to processing option templates. Template changes do not take effect until another package is built, but text changes occur immediately.

The following steps describe how to create and implement processing options:

  1. Create processing option template.

  2. Attach this template to an application and create event rules so that the application uses these values.

  3. Create versions of the application. Save different processing option values to different versions. Specify the default version.

  4. Specify how the processing options are handled at application launch time. You can set up the menu to do one of the following:

    • The processing options dialog appears. The user can select to supply values to processing options.

    • A version list appears. The user can select a version to launch.

    • The system runs a particular version with the processing option values saved for that version.

At runtime, depending on how you set up the application, one of the following events occurs:

Processing option template is created through Oracle's JD Edwards Processing Option Design Aid. When working with processing option design aid (PODA), all processing option template information is stored in Processing Option Text (POTEXT) Table Access Management (TAM) specifications until you check it in. When you check in the processing option template, it is moved from POTEXT TAM to the F98306 table. Data values for processing options are stored in the F983051 table. For batch versions, the Versions List table has an identifier that points to specifications for overrides (report overrides, data sequencing, data selection, or override location).

Each version of an application can be associated with a list of processing option values.