This chapter contains the following topics:
This chapter provides overviews of processing options and processing options templates, and discusses how to define a processing options data structure (template), attach a processing options template, and work with processing options.
Processing options are a set of start up values that are provided to an interactive or batch application when it is launched. You can use processing options to change the way in which an application or a report appears or behaves. You can attach different processing option values to different versions of the same application, which enables you to change the behavior of an application without creating a new application. Additionally, you can use processing options to:
Control the path that a user can use to navigate through a system.
Set up default values.
Customize an application for different companies or different users.
Control the format of forms and reports.
Control page breaks and totaling for reports.
Specify the default version of a related application or batch process.
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:
Create processing option template.
Attach this template to an application and create event rules so that the application uses these values.
Create versions of the application. Save different processing option values to different versions. Specify the default version.
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.
You can create a processing options data structure (template) that lists the values for data items that are passed to the application at runtime. Any changes that you make to the template reside on the workstation until you check in the template. This ensures that current users of the existing template are not immediately affected by the changes. After you check in the changes, the next Just-In-Time-Install (JITI) replicates the changes to the other users.
Create a processing options data structure.
You should follow JD Edwards EnterpriseOne naming standards whenever possible unless you have a strong business case for doing otherwise. Following the naming standards ensures a consistent approach to programming.
The name of a data structure can be a maximum of 10 characters-only 9 if you begin the name with a T and is formatted as Txxxxxyyyy:
Where:
T = Processing option data structure.
xxxxxyyyy = The program number for the application or report.
For example, the processing option data structure name for the P0101 application is T0101.
Use these guidelines when you define a tab title for a processing option:
Avoid abbreviations.
For future processing options, indicate that they are currently unavailable by entering the word FUTURE. If the entire tab is unavailable, enter FUTURE behind the extended description for the tab. If a single processing option is unavailable, place FUTURE behind the data item description.
Ensure that each tab exists only one time and that it is not divided into multiple tabs. For example, use Process instead of Process 1, Process 2.
Include the application name, such as P4310, in the text when referencing versions that are to be used. The Version tab should always begin with the comment block. Enter the version to be used for each program. If left blank, ZJDE0001 will be used.
Use application-specific tabs sparingly and only when no other categories are appropriate. To allow for increased length of text when the text is translated, the name of an application-specific tab should be no longer than 10 characters in English.
Use one of the eight standard tab titles. Along with the extended description and processing options for each, they are as follows:
Display: Options that determine whether specific fields appear or which format of a form appears on entry.
Defaults: Options that assign default values to specific fields.
Edits: Options that indicate whether the system performs data validation for specific fields.
Process: Options that control the process flow of the application.
Application-specific tabs are:
Currency: Options that are specific to currency.
Categories: Options that assign default category codes.
Print: Options that control the output of a report.
Versions: Options that specify which versions the system runs of applications that are called from this application.
Use these guidelines when you enter a comment for a processing option:
Note:
When several processing options are grouped together, you can select to number the processing options or the comments. Choose whatever works best for the situation.Number every option on a tab. Use sequential numbering, starting at 1, for each tab.
Use nouns, such as Customer Master, to describe the processing option. The action required is defined in the glossary for that processing option.
Add the word "Required" to the end of the processing option if a processing option is required.
Use a comment block when multiple processing options refer to the same topic. The comment block is a title for the logical group of processing options.
Use these guidelines when creating a data item for a processing option:
When necessary, change the name of the data item to be descriptive.
When renaming the data item element, the field element should comply with the naming standards for event rule variables, with the alias appended, such as szCategoryCode3_CT03.
Use a relevant data item when the data dictionary glossary applies. The user can display the glossary from the processing options. Do not use generic work fields, such as EV01.
You can change a processing option template to incorporate language features.
When you add a new processing option template for an application that is language-enabled, complete the following tasks:
Create the application.
Create the processing option template for the base language.
Add the language text.
You must attach a processing options template (data structure) to an application to enable processing options at runtime. A processing options template has these characteristics:
It exists as a separate object.
It can be attached to multiple applications.
When you attach a processing options template, if any of the processing options are designed to process on a certain event, you must attach event rule logic to enable those processing options.
This section discusses how to:
Define a processing options data structure (template).
Change a template for text translation.
Attach a processing options template.
Access the JD Edwards Object Management Workbench form.
Check out the processing options data structure with which you want to work.
Ensure that the data structure is highlighted, and then click the Design button in the center column.
On Processing Option Design, click the Design Tools tab, and then click Start the Processing Option Design Aid.
The Processing Options Design tool launches. The area on the left of the form displays how the processing option will look to the user.
Locate the data items that you need for the processing options with the Data Dictionary Browser.
Use one of these methods to select the data items that you want to add to the processing options:
Double-click the item in the Data Dictionary Browser. The item appears in the left side of the form under the tab.
Drag the item from the Data Dictionary Browser to the position where you want it in the structure members.
Click an item to edit it.
You can use the hatching around the control to reposition it.
You can select text, and then delete or overwrite it.
Processing Options Design automatically adjusts the size and position of data items to fit the width of the tab.
Click the text button (A) to add comments.
Choose an object in the area on the left side of the form, and select Properties from the View menu.
Right-click a data item to view its properties and change the item name if necessary. The item name should be unique.
You can click the Help Override Data Item tab to add an alternate data dictionary name from which to get the help.
Right-click the processing option, and then select Properties from the menu.
On Data Item Properties, click the Help Override Data Item tab, and then complete the Data Item Help Override Name field.
Note:
When you name Help Override Data Items, you should use the naming guidelines as defined in the JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide.Click OK.
To view tab properties, click the tab and select Properties from the View menu.
You can also right-click a tab and select Current Tab Properties from the menu that appears.
On Current Tab Properties, you can enter a short and long name for the tab.
Use the Help File Name field to add the name of the help file for the tab.
To add a new tab, select New Tab from the File menu.
You can also right-click an existing tab and select New Tab from the menu that appears.
Access the Work With PO Text Translations form.
Complete these fields and click Find:
Template Name
To Language
Work with PO Text Translations displays processing option text for the processing option template and language that you specify.
Choose a row with the text type that you want to change and click Select.
Text types include tabs, items, and comments.
On PO Text Translation, enter the new text.
On JD Edwards Form Design Aid, from the file menu, select Application Properties.
On the Application tab, click the .. button under the Processing Options Template.
On Select Processing Option Template, select the processing option template that you want to use and click OK.
Important:
If you disconnect that template from the application or connect a different template to the application, the application might not run properly.To change the processing option template, first remove all existing versions of the application. Then, examine all event rules within the application to ensure that references to the old processing option items are removed. Then attach the new processing option template.