Batch Control Files
Batch processes can involve loading hierarchies, loading measure data, running batch calculations, reporting plan data from a solution, and so on. All of these activities must be run in a particular sequence. In order for you to define the sequence of activities, RPASCE leverages a framework of batch control files that are simple text files. Within a batch control file, you define the pre-configured tasks to execute. RPASCE Online Administration Tools (OAT) capabilities are then used to schedule and provide parameterized inputs to execute batch activities using the control files.
The following list provides some example batch control files and the purpose for each file. For more details about the structure of the control files and the other control files that are available, see the Oracle Retail Merchandise Financial Planning Cloud Service Implementation Guide.
Table 1-1 Example Batch Control Files
| File Name | Description |
|---|---|
|
batch_calc_list.txt |
Defines the different mace expressions or rule groups to run in a particular order. |
|
batch_loadmeas_list.txt |
Defines the different sets or groups of measures that must be loaded together. |
|
batch_exportmeas_list.txt |
Defines the different sets of exports, with the file names and list of measures to be exported for each set. |
|
batch_exec_list.txt |
Defines a typical daily or weekly batch process, which calls the predefined sets in other control files in a particular order. |
|
batch_oat_list.txt |
Defines what batch calc, batch exec, batch load, and batch export tasks are visible in the Online Administration Tools, with user-understandable labels for those tasks. |