Return to Projected Balance Sheet Model Overview
Elements in the Batch Procedure Configuration dimension contain the definition of batch procedures to be run by the end user. The dimension is made up of multiple levels:
| Level | Description |
| All Batch Procedures | Root element that encloses all types of procedures. |
| All ... Procedures | Parent element that encloses all procedures of the same type. |
| Standard ... Procedure | Executable procedure accessible in the report: See Article Projected Balance Sheet Projection Configuration. Please note creating custom procedures is not supported by the user interface. |
| Step | Base element of the dimension. This is the step that is executed as a part of a particular procedure. Elements on this level can be added, modified or removed using the Projected Balance Sheet Projection Configuration. |
The Batch Procedure Configuration elements contain the following attributes:
|
Attribute |
Description |
| Name | Readable name of the element. This attribute is visible in the report. There is no hard-coded behavior implemented on this name (string). |
|
Description |
Long text description of the element (string). |
| Enabled | Indicates whether a particular step or procedure is enabled or disabled. Restricted to either 1 or 0 (Checked or unchecked, numeric). |
|
Executable |
Applies only to procedures. Procedures must be set to 1 and must be an empty string for all the others. Restricted to either 1 or an empty string (Checked or unchecked, text). |
|
Ledger |
The ledger (at the level of a Standard ... Procedure) the journal entry belongs to |
|
Level.Step |
Defines the execution order of the steps. Valid values are whole numbers (e.g. 0, 1, 2, 3 …) before and after the decimal point (e.g. 1.1, 1.2, 1.3...). The first number represents the level of the standard procedure and the second is for the step. |
|
FilterVersionPattern |
Defines which versions a particular step applies to using regular expressions. Examples: ^.*$,
|
|
FilterMonthFrom |
Defines the months a particular step applies to using the beginning of a date range. Example: 1900-01 (starting from January 1900) |
|
FilterMonthTo |
Defines the months a particular step applies to using the end of a date range. Example: 2099-12 (ending on December 2099) |
|
FilterLegalEntityFrom |
Defines the legal entities a particular step applies to using the beginning of an alphanumeric range. Example: 0 (could be any number, uppercase letter or lowercase letter) |
|
FilterLegalEntityTo |
Defines the legal entities a particular step applies to using the end of an alphanumeric range. Example: zzzzzzzz (could be any number, uppercase letter or lowercase letter) |
|
Integrator Project |
Applies only to procedures. Location of the actual Integrator implementation. This is not subjection to configuration. |
|
Integrator Job |
Applies only to procedures. Location of the actual Integrator implementation. This is not subjection to configuration. |
|
Configuration Report |
Applies only to steps. Location of the report to modify the configuration. This is not subjection to configuration. |
Updated January 13, 2023