Batch Control File Customization Guidelines

Follow these guidelines for Batch Control File Customization:

• The file batch_oat_list.txt is the only batch control file in which customers can overwrite the label for GA set names listed in OAT.

• For all other batch control files, avoid overwriting GA set names. GA batch control files have provided various hooks for the batch process. For additional custom steps, try to put them into the hooks.

• GA batch control files have provided a mechanism to skip certain GA steps using boolean scalar measure that can be set in the domain.

• For a GA hierarchy that is unused in your implementation (such as attribute hierarchy), provide an empty hierarchy file. For unused GA measures, there is no requirement to provide the data file. RPASCE will be able to skip it if no files are provided.

• Do not remove any GA clnd hierarchy reorder steps; these steps are essential to the proper functioning of the application.

• For ease of maintenance, all custom batch set name or step names should be prefixed with c_

Examples

The following is an example of custom batch_exec_list.txt, batch_calc_list.txt, batch_loadmeas_list.txt, and batch_exportmeas_list.txt.

In this example, the following modification were added to the batch _weekly process:

• Hierarchy and measure data file were unpacked.

• Custom measures were loaded after GA measure load.

• Outlier indicators for preprocessing were calculated use custom rules

• Custom approval alerts were run after GA alerts and before approval

• Promotion effects were exported after GA exports