[BPC 11] Improvements for Consolidation Monitor
The BPC consolidation monitor is used as a central place to trigger consolidation related tasks and show the status for the execution.
In BPC 11, some additional improvements are delivered in consolidation monitor to make it more flexible and user-friendly.
PS: These new improvements are only available for consolidation monitor in embedded model now. But it’s also planned to provide these capabilities for standard model in the future SP.
Support Control and Work Status
Now user can define task for Control or Work Status in the consolidation monitor.
Additional settings for different types of task
In previous release (embedded model), the additional settings for different types of task can be defined in the task sequence definition but with limited capabilities.
Now, the additional settings can be configured for each task itself in a dedicated dialog UI.
General Settings for all tasks
Now user can define the task frequency for different tasks.
For example, the Balance Carry Forward rule is only needed for the beginning period of the current year.
Three options are available for the task frequency:
- Every period with period 000
- Every period without period 000
- Customer defined by giving the sequence number for the required periods
Please notice that the sequence number for period 000 is ‘0’.
In previous release, the task sequence is model related setting. This means for all Category members, the task sequence will be the same.
But in most cases, the Category dimension will be used to identify different business scenarios. Some tasks may not be needed for a particular category member.
Now in BPC 11, user can define which category members are valid for the current task.
This means, now user can define different task sequence for different category members.
Task specific settings
Due to the nature of different task types, there’re some task specific settings for different types of task.
The control context definition may be different with the context of consolidation monitor.
In consolidation monitor, the additional dimension should be given with a proper value in order to correctly show the control status and trigger the control task. The dimension member can be defined in the control task definition.
Furthermore, user can also define the execution level for the corresponding control task.
This also means user can define multiple control tasks for different control level, such as Control for ‘Loaded Data’ before Currency Translation task, or Control for ‘Consolidated Data’ after Elimination and Adjustment task.
Similar with control, the definition of work status may also contains additional dimensions compared with the consolidation monitor context.
In this case, user can also define a proper value for this dimension in order to correctly show the work status in the monitor.
One special case is, if Group dimension is also part of the work status dimension.
In consolidation monitor context, the Group dimension member is also used to show the whole ownership hierarchy for that group, including the subgroups and the entities. Directly using the group member from the context to show the work status for all subgroups and entities may not be needed.
In this case, two different options are available for group dimension.
‘Non-Group’ means the work status will always use a non-group member to decide the status.
‘Direct Parent’ means, for the work status of each entity, the status will be decided by it’s direct parent group in the ownership hierarchy.
One additional field called ‘Other Dimension Filter’ is available for all business rule tasks. It can be used to define additional restrictions for the related task.
This field should be maintained with a text string by manual input, the syntax would be:
<dimension_name1>=<member_A>, <member_B> ; <dimension_name2>=<member_C>
The defined selection condition will be used as additional restrictions when read data in the business rule execution. In most cases, such design only works for user defined dimensions.
One additional setting for Account-based Calculation is to define which rule will be executed.
One additional setting for Currency Translation is to define the member for Rate Entity dimension.
Two additional settings are now available for the whole task sequence.
Enable Task Dependency
In previous release, although the tasks are defined with sequence, but there’s no dependency between each other.
In BPC 11, now user can decide whether the task has dependency in the sequence.
If the setting is selected, then when a task is re-executed, the status for all afterwards tasks will be reset to ‘To be executed’. This would ensure that all the tasks should be executed in sequence.
Allow to change settings in Consolidation Monitor
In previous release, when trying to trigger the task from the consolidation monitor, a dialog will pop up to show the related parameters. And user is still able to change the parameter before execution.
Now a setting is available to decide whether the end user is allowed to change the parameters via the consolidation monitor pop up dialog.