Financial Close Overall Delay 
The analytical app displays the Key Performance Indicator (KPI) Financial Close Overall Delay. You can find out about the overall delay in hours of a closing cycle. You can also find out about the reasons for the overall delay and follow up through SAP Jam or emails so that the responsible agent can speed up.
Key Features
Determine the overall delay in hours of a closing cycle.
To do so, the app first determines the end time of the current closing cycle in the following way:
The app uses the following three parameters to determine which task lists are relevant for the current closing cycle:
Closing Type
Closing Period
Fiscal Year
Among the task lists that are relevant for the current closing cycle, the app picks out the task lists that have the following statuses:
Released
Active
Paused
The app compares the end time of all the task lists that have been picked out. The apps defines the end time of whichever task list that ends the latest as the end time of the current closing cycle.
The app then determines the overall delay in hours of the current closing cycle in the following way:
The app calculates the delay in hours for each of the task lists that have been picked out. The calculation rule is different depending on whether a task has successors:
For tasks with successors:
For each successor path, the app calculates the buffer between the end time of the task and the planned start time of its successor. It also calculates the buffer between the planned end time of the last task in the successor path and the end time of the current closing cycle. The app then calculates the sum of the two buffers for each successor path and chooses the smallest sum. If the smallest sum is less than the planned duration of the task in question, the app considers that the task will cause delay.
For tasks without successors:
If a task is in progress, the app does not consider that the task will cause any delay no matter how little time is left till the end time of the closing cycle.
If a task is not started or with errors, the app considers that the task will cause delay if the time left till the end time of the closing cycle is less than the planned duration of the task.
The app chooses the longest delay among all the task lists that have been picked out as the overall delay in hours of the current closing cycle.
If you drill down to the second level, the app displays the successors of the task that causes the longest delay.
Display a table which shows detailed information about the overall delay in the closing cycle after you drill down from the KPI tile.
System Landscape Requirements
The app consists of front-end components and back-end components. The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori.
SAP Smart Business Product | SAP Smart Business for financial close 1.0 |
|---|---|
Contains Virtual Data Model (VDM) | SAP HANA Analytics for FCC 1.0 |
SAP Business Suite Product | SAP Financial Closing Cockpit 2.0 |
For more information about the system landscape to run SAP Smart Business cockpits, see Installation.
Component for Customer Incidents
CA-GTF-FCC