Automation Settings
The automation settings control what happens before and after the dimension is built by the automation steps. In the Business Segment Maintenance page the automation settings are grouped. The Automation Setting Group can be selected using the Settings Filter.
General Settings
A summary of the important automation settings. Some of these settings appear in other automation setting groups.
Setting | Description |
---|---|
Last Update End Time | The time stamp of last update. |
User | User running last update. |
Comment | You can use this parameter to enter commentary. |
Delete All Elements | Y - Delete all the elements in the existing hierarchy before rebuilding the hierarchy from the source data defined in the automation steps. To be used with caution. If an element does not exist in the source data it will be permanently deleted from the hierarchy. Any data against a deleted element will also be permanently deleted. It is often safer to unwind the dimension, see below, and then investigate if the orphan elements are required or can be manually deleted. |
Unwind Dimension | Y - To break the components of the consolidates before rebuild the components from the source data defined in the automation steps. |
List of consolidations to unwind | The top node consolidation of the rollup to be unwound. The components under the top node in the rollup will be broken before the rollup is rebuild by the automation steps. If multiple nodes need to be unwound then list all the top nodes separated by the List Separator for unwind consolidations. When left blank, all consolidations in the hierarchy will be unwound. |
Unwind Recursively | N - Unwind the direct components of the consolidation. Y - Unwind the all levels the consolidation to the leaf element. |
Allow N to C element type conversion | N - Do not allow the converstion of leaf elements to consolidations. Y - This is only possible if the dimension does not contain alternate hierarchies. Allow leaf elements to be converted to Consolidations. To be used with caution. If the leaf element has any data against the element that data will be permently deleted when the leaf element is converted to a consolidation. |
Update Element Security | Y - Update the business segment security with any changes with heirarchy structure. |
Dimension Cleaning
Automation setting relating to the how the existing hierarchy is to be prepared and how the final hierarchy is to be clean up after it is been rebuilt by the Automation Steps.
Setting | Description |
---|---|
Delete All Elements | Y - Delete all the elements in the existing hierarchy before rebuilding the hierarchy from the source data defined in the automation steps. To be used with caution. If an element does not exist in the source data it will be permanently deleted from the hierarchy. Any data against a deleted element will also be permanently deleted. It is often safer to unwind the dimension, see below, and then investigate if the orphan elements are required or can be manually deleted. |
Unwind Dimension | Y - To break the components of the consolidates before rebuild the components from the source data defined in the automation steps. |
List of consolidations to unwind | The top node consolidation of the rollup to be unwound. The components under the top node in the rollup will be broken before the rollup is rebuild by the automation steps. If multiple nodes need to be unwound then list all the top nodes separated by the List Separator for unwind consolidations. When left blank, all consolidations in the hierarchy will be unwound. |
List Separator for unwind consolidations | Character separator for multiple consolidations to be unwound. |
Unwind Recursively | N - Unwind the direct components of the consolidation. Y - Unwind the all levels the consolidation to the leaf element. |
Allow N to C element type conversion | N - Do not allow the converstion of leaf elements to consolidations. Y - This is only possible if the dimension does not contain alternate hierarchies. Allow leaf elements to be converted to Consolidations. To be used with caution. If the leaf element has any data against the element that data will be permently deleted when the leaf element is converted to a consolidation. |
Group Orphan N Elements | Y - Orphan leaf elements will be grouped into the unallocated node as per the naming convention in the Standard Unallocated Node setting in APQ Std Variable Names System Settings. The default name for the unallocated node is ‘Unallocated’. |
Delete Orphan C Elements | Y - Any consolidated elements that have no components will be removed from the hierarchy. |
Automatically Create ToPNode | Y -  A root element will be added to the dimension using the naming convention set for Std Top Node Name from the APQ Std Variable Names System Settings. The default is the dimension name suffixed with ‘Rollup’. All consolidations that have no parent element will be added to the root element. |
Create NA element | Y - Create a NA element for the business segments. The NA element is added to the Total consolidation for the business segment. |
Automatically Create Dummy N Elements | Y - Create at leaf element under each consolidation of the consolidation. The element principal name for the new leaf element will be, the consolidation principal name suffixed with the Std Dummy N Element setting from the APQ Std Variable Names System Settings. The default setting is ‘_N’. |
Delete and Recreate Attributes | Y - Delete all attributes and their values. Recreate the attributes from the source data. |
Dimension Sort Order
Automation setting relating to the how the hierarchy is to be sort in Planning Analytics. The affect how the heirarchy is presented in the subset editor.
Setting | Description |
---|---|
Dimension Sort Order | Y - The sort order should be applied |
Component Sort Type | Defines how components of consolidated elements appear in the hierarchy. ByInput - Retains the order in which components were originally inserted into the consolidations. ByName - Sorts components of consolidations by name. |
Component Sort Sense | Defines the sort sense for components of the consolidations. This is a required argument, but it applies only when the Component Sort Type is ByName. Ascending - Sorts components of consolidations in ascending alphabetical order. Descending - Sorts components of consolidations in descending alphabetical order. |
Element Sort Type | Defines a sort order for dimension elements. ByInput - Retains the order in which elements were originally inserted into the hierachy. ByName - Sorts dimension elements by name. ByLevel - Sorts dimension elements by level. ByHierarchy - Sorts dimension elements by rollup. |
Element Sort Sense | Defines the sort sense for dimension elements. This is a required argument, but it applies only when the Element Sort Type is ByName or ByLevel. Ascending - Sorts dimension elements in ascending order, either alphabetically or by level. Descending - Sorts dimension elements in descending order, either alphabetically or by level. |
Framework Update
Automation settings that run updates for other parts of Business Segment maintenance after the Business Segment heirarchy has been rebuilt.
Setting | Description |
---|---|
Launch Standard Subset Updates | Y - Changes in Business Segments heirarchy will be applied to the standard subsets. See Standard Subsets for more information about standard subsets. |
Launch Subset Framework Updates | Y - Changes in the Business Segment heirarchy will be applied to static and semi-dynamic subsets. See Static Subset Popup and Dynamic Subset Popup for more information about static and semi-dynamic subsets. |
Launch Attribute Framework updates | Y - Apply attribute override value to the heirarchy. |
Update Element Security | Y - Update the business segment security with any changes with heirarchy structure. |
Full element security refresh (including automatic group creation) | Y - Not used. Automatically create user groups based on heirarchy. |
Element security refresh for preconfigured groups | Y - Element security will be refreshed for all existing groups. |
Pre and Post Processing
Addition steps that can be taken before or after the hierarchy is updated.
Setting | Description |
---|---|
Launch process BEFORE step 1 | The selected process will be run before commencing dimension updates. |
Launch AFTER the final step | The selected process will be run after all other update steps are finished. |
Launch another dimension | The selected dimension will be launched after all other steps are finished. |