Consolidation Data Release Cockpit
Application component: Real-Time Consolidation
App type: Transactional
Line of business: Finance
Leading industry: Cross Industry
Solution capability: Corporate Close (S/4)
Description: With this app, local accountants can view and verify financial data of specified consolidation model and entities before releasing the data. Based on status of last released data, system controls whether currency translation, validation and release is possible for new posting data, and presents released and to-be-released amount in both local currency and/or group currency. Data release history can be retrieved for comparison purpose. 
An app to display consolidation data status and to validate data
Key features:  Data Status Overview After specifying the model and optionally the version, entities, and fiscal period range, you get an overview of the following statuses for each entity:   Lock Status: Shows whether the period is still open for data release.  Period Status: Shows the status of the reported data for a timespan from the beginning of the period until the time that it is released. Adjustment Status: Shows the status of the adjusted data after the latest release, that is which data is in the translation, validation, or release phase. New Posting: Shows if a new posting is detected in the universal journal or through flexible upload, the data of which has not yet entered the data release cycle.   Reported Data in Detail For a specified fiscal period, the table Reported Data displays the data reported within different timespans and therefore with various statuses. The table contains the following columns or settings:  LC/GC Opening: The amount in period 000. This amount is not the amount carried forward in accounting, but the amount carried forward by the consolidation transaction to the consolidation table ACDOCC.  LC/GC New Posting: The amount of journals posted after the latest data release cut-off time. LC/GC To Be Released: Once the Currency Translation (optional) and Validation task for the new posting data is executed successfully, the amount is moved from New Posting to this column. LC/GC Released: Once the Release task for the to-be-released data is executed successfully, the amount is moved from To Be Released to this column. LC/GC YTD: The sum of Opening and Approved amounts for prior periods, and To Be Released and Released amounts for the current period. Display Group Currency: If a group currency amount with a posting level equal to or lower than 09 exists, data can be displayed in your selected currency. Note LC and GC stand for local currency and group currency respectively.The hierarchy of financial accounts in the table is defined as Financial Statement Version (transaction code OB58), and assigned to the combination of model, ledger, and entity in transaction Method Assignment (transaction code RTCMA). In general, when documents are posted for an entity, the system checks if the data can be validated and translated. If not, the newly-posted data is represented as a New Posting in the table. Otherwise, the newly-posted data is merged with the most recent data in the validation and the optional translation process, and the merged data is shown as the To Be Released amount. Once it is released, the data is displayed as Released. The status change of the amounts displayed for reported data described above is illustrated in the following figure:     Note When expanding to account item level, you have the option to drill through to the original journal entries in the consolidation table (ACDOCC).   Run Currency Translation (Optional) and Validation Before releasing data for group consolidation, the reported financial data of each entity needs to be validated against the defined rules, and translated into group currency if configured accordingly. After choosing Run Translation and Validation, a background job is triggered and lined up in the system job queue. You can choose Log  Background Job Log or Currency Translation Log to check the details log. If validation fails, you can view its details under Validation to check which validation rule the data fails to meet. The Status column shows whether the reported data has passed the rule check. Failed validation is followed by an explanation in the Rule Result column, which was defined as Fail Message Outputs when setting up the rules in the Fiori app Define Validation Rules.  For any rule of your interest, you can run validation with the latest data in simulation mode using the button Simulation. To get more insights on the validation results, you can choose Show Extra Columns on the top right corner of the table, so that you can navigate to drill-through reports defined when setting up rules, add comments when validation against a soft rule fails with exemption, or add an attachment for further explanation.  Release Following a successful data validation, you can release the data for approval. The Release History lists all your data releases and their statuses within the specified fiscal period. You can choose any two releases to compare the value differences of each accounting entry in the local and group currencies.  Reverse You have the option to reverse your last released data, the status of which will be changed to the preceding status Validation Passed, and data is moved from the Released column to the To Be Released column in the Reported Data table. Note This app replaces the following transaction codes that are available in SAP S/4HANA 1610 and become obsolete from SAP S/4HANA 1709 onwards:  RTCDSR: Raise Data Submit Request   RTCRL: Data Submit Request List   RTCPL: Pull Request - Period Lock/Unlock  Refer to SAP Note 2569477  to disable the transaction codes in the back-end systems.
Business roles: Consolidation Specialist
Consolidation Specialist : 
Is responsible for the Consolidation setting, processing for the FI or other business data from subsidiaries. Generates the legal & management consolidated reports.