Status Management in the Consolidation Monitor
You use this function to monitor the progress of the tasks for each individual consolidation unit or consolidation group.
Note
Using Status Reporting, you can create reports on the progress of task processing and task group processing in the consolidation monitor.
Status management is activated by default.
Recommendation
You should deactivate status management in exceptional cases only. You can do this in the process view of the workbench under Consolidation Area
, on the Settings
tab.
The other prerequisites are the same as those described in Consolidation Monitor.
Whenever status management is activated, a consolidation unit hierarchy is status-relevant by default, which means that the consolidation monitor shows the status of the hierarchy.
In the consolidation area settings, you can use the Hierarchy-dependent Status Management is Active in Monitor
indicator to have the consolidation monitor hide the hierarchies that are not status-relevant.
If this indicator is selected, for each hierarchy you can specify whether it is not status-relevant or not displayed in the Consolidation Monitor. (Go to the process view of the workbench and choose ).
The consolidation monitor displays the status by organizational unit for each status-relevant hierarchy: for each task and summarized for task groups.

Legend of Symbols for the Status Display
Status | Explanation/Example | System Sets Status | User Sets Status |
|---|---|---|---|
Initial Stage | The task has not yet been executed in update mode. | X | |
Incomplete | The task has been executed in update mode but is still incomplete, for example, due to the following:
| X | |
Errors | Errors occurred while the task was being executed in update mode. | X | |
Pending Completion of Preceding Task |
| X | |
No Errors with Warnings | No errors occurred in update mode, but warning messages did arise. | X | |
Without Errors, Without Warnings | The task was executed in update mode without any errors or warnings. | X | |
Blocked | The task is blocked against (another) execution. The user can block the task only if it has been executed without errors and the preceding tasks are blocked. Exceptions: Data collection and manual standardizing tasks. These can be blocked without having been run (however, the preceding tasks must first be blocked). You can block a copy task after it has been executed without errors if its source task or tasks have been blocked. | Optional | |
Blocked, Pending Approval | A user wants to block the task. A workflow for approving status changes is assigned to the task. The status change has not yet been approved. | Optional | |
Blocked by User Intervention | Users can block tasks at any time (regardless of the status of preceding tasks). However, you should use this option only when there is justification to do so, and only in exceptional circumstances. | Optional | |
Blocked by User Intervention, Pending Approval | A user wants to block the task, regardless of the status of the task (for example, | Optional | |
Unblocked | After a task has been blocked, you can unblock it if it needs to be re-executed. | Optional | |
Unblocked, Pending Approval | A user wants to unblock the task. A workflow for approving status changes is assigned to the task. The status change has not yet been approved. | Optional | |
Not Applicable |
| X | |
Reset | When the source task of a copy task is reset, the system resets the status of the copy task and the tasks that follow. You should | X (for the copy task) | Optional |
Reset, Pending Approval | A user wants to reset the task. A workflow for approving status changes is assigned to the task. The status change has not yet been approved. You should set the status to | X (for the copy task) | Optional |
To display the details of the status of an organizational unit and a task (or task group), go to the context menu of the header row or header column and choose .
The details include the user name, date, and time of the last change.
When you run a task in update mode, the system updates the status for the relevant organizational units.
You can execute task "B" even if its preceding task, "A", has not been blocked yet. In this case, task "B" is set to status Pending Completion of Preceding Task
.
A task can only be blocked (in the menu) if it was executed without any errors and all preceding tasks have been blocked.
Exceptions to this are the data collection and manual standardizing entries tasks. These can be blocked without having been run.
You can block the tasks of a task group as a bundle.
If you block a task for a consolidation group (in the menu: ), the system simultaneously blocks the subordinate consolidation groups and units.
Once a task has been blocked, it must be unblocked before it can be run again. Note that this also automatically unblocks all downstream tasks. For example, if you unblock the task for data collection, the system simultaneously unblocks the tasks for currency translation and so on.
You can unblock the tasks of a task group as a bundle.
If you unblock a task for a consolidation group (in the menu: ), the system simultaneously unblocks the task for the subordinate consolidation groups and units. However, you can also unblock individual consolidation groups for tasks that are executed at the consolidation group level without also unblocking subordinate consolidation groups (in the menu: ). You can use this option, for example, to unblock a copy task at a specific hierarchy level.
The system uses the same update logic for higher-level and lower-level organizational units, and for the overall status.
Only in exceptional cases should you Reset
the status (in the menu: ). Here is an example: Suppose the system sets the status of currency translation to Not Applicable
because the local currency is the same as the group currency. At a later date, a local currency change takes place. In this case, you need to manually reset the status of currency translation.
The system then resets the following statuses of the organizational units for the selected task:
The status of the selected consolidation unit or group
The statuses of the lower-level consolidation units and groups
The statuses of the higher level consolidation groups
The system also resets the downstream tasks.
Furthermore, when a source task of a copy task is reset, the system resets the status of the copy task and the tasks that follow.
Another function for exceptional cases is the function for deactivating status management (see Customizing for the consolidation area on the Settings
tab).
If you have activated the business function Financials, Group Close, Check Digits (FIN_ACC_GC_CHKDGT
), you can also change the task status (block, block by user intervention, unblock, or reset) manually for multiple consolidation units simultaneously. This is possible for the following tasks and task groups:
Tasks that are processed per consolidation unit
Task groups that contain only tasks that are processed per consolidation unit
In the context menu, on a matrix point (intersection between consolidation unit and task or task groups), choose the entry Lock/Unlock with Selection Screen
. The User Restrictions
dialog box appears, in which you enter the selection conditions (in particular the consolidation units) as well as the type of the intended status change (for example, unblock). When you choose Execute
, the system executes the status change (if possible or permitted) for the specified selection and updates the task status display in the consolidation monitor.
You can save the selection conditions that you want to reuse again in the User Restrictions
dialog box as a variant in the consolidation workbench: In the context menu for a task of type Data Entry
, Currency Translation
, or Capitalization and Valuation Allowances
, choose the Variants for Status Changes
entry.
In general, periods are always initially open for task processing.
You can open and close the periods of a fiscal year for all tasks to ensure that documents are always posted in the correct period. This is always done for a selected consolidation group (including its lower-level organizational units) or for a single consolidation unit.
You can also close the processing of consolidation units only. In this case, only the tasks at consolidation group level can be executed. To do this, choose .
If the period (including all tasks) is already closed, you can reopen task processing for the consolidation groups by choosing .
Note
You require special authorization to open and close periods.
The following figure shows which colors are used to highlight the nodes of the organizational units when periods are open or closed.

Color legend for opening and closing periods