Objective
At ABC Corporation, one of your responsibilities is to acquire data. Since you are using SAP S/4HANA Accounting, you need to understand the integration with group reporting.
Let’s learn more about this below.
Learn how group reporting and accounting are integrated in the following video.
As postings occur in the general ledger for integrated companies, they're captured in the ACDOCA (Accounting Document for Actual) table. Before the data is released into group reporting, the general ledger trial balance report can be used to view the group reporting related data in ACDOCA.
You can also view group reporting data in the accounting journal entry. This feature is related to the preparation ledger, which became available in the 2022 edition. The benefit is that reporting and reconciliation can occur before the Data Release task (the sooner discrepancies are discovered, the better).
In the following image, there are four steps in the data release process:
Note
As postings occur in the general ledger, group reporting fields are recorded along with the rest of the accounting data. You can view the group reporting fields in the Manage Journal Entries app with these steps:
There are several group reporting fields that are recorded in the general ledger (ACDOCA table):
Note
Group reporting data can also be displayed when accessing the line items of general ledger documents.
As postings occur in the general ledger, group reporting information is recorded in the ACDOCA table. The data is later released into group reporting. You need to learn how to view the group reporting data in the general ledger.
As postings occur in the general ledger, group reporting information is recorded in the ACDOCA table. The data is later released into group reporting. You need to learn how to view the group reporting data in the general ledger.
The main steps in this exercise are:
In order to test the release process, post an adjusting entry into the general ledger.
Note
In the Journal Entries group, go to the Post General Journal Entries tile.
Open the Journal Entries group.
Open the Post General Journal Entries tile.
Input the header data as follows:
| Field | Value |
|---|---|
| Journal Entry Date | December 31, 2025 |
| Posting Date | December 31, 2025 |
| Period | 12 |
| Journal Entry Type | SA |
| ... | |
| Company Code | 1010 |
| Transaction Currency | EUR |
Note
Enter the data provided in the Journal Header table.
Enter the line item data as follows:
| Line Item | C.Code | G/L Account | Debit | Credit | Profit Ctr |
|---|---|---|---|---|---|
| 001 | 1010 | 10010000 | 550 | 0 | P90## |
| 002 | 1010 | 31000000 | 0 | 550 | P90## |
Enter the data (except for the Profit Center. field) as provided above.
Use the ellipse (…) to access the credit field if needed.
Expand line item 001.
Scroll down and input P90## under Profit Center.
Expand line item 002.
Scroll down and input P90## under Profit Center.
Post the document.
On the lower right, choose Post.
Choose Display.
In the Line Items section of the Journal Entry screen, keep the Ledger View tab selected and choose 0L (Ledger 0L) . Check for both Journal Entry Items the following Group Reporting field values in the ACDOCA table:
| Field | Value |
|---|---|
| Consolidation Unit | DE## |
| Company | 1010 (DE Company) |
| Consolidation Chart of Accounts | Y1 |
| Consolidation Financial Statement Item | 111100 (for Journal Entry Item 000001) |
| 311000 (for Journal Entry Item 000002) | |
| Consolidation Subitem Category | 1 (Transaction Types) |
| Consolidation Subitem | 915 |
On the Journal Entry page open the Line Items tab.
Keep Ledger View selected.
In necessary, use the drop-down right to the Ledger field and select 0L (Ledger 0L).
Choose >(Details) for the first line item and confirm the Group Reporting field values as described in the table above.
Choose <(Back) on the upper left.
Choose >(Details) for the second line item and confirm the Group Reporting field values as described in the table above.
Choose the 
icon to return to the SAP Fiori Launchpad Home Page.
Note
One of the main sources of reported data is SAP S/4HANA Finance. You release accounting data (from the SAP General Ledger) into group reporting using the data monitor. The data release process controls the flow of data into group reporting.
Data release is an important control mechanism that prevents unwanted data from becoming available to group reporting.
Prerequisites:
The period is open.
The company is a consolidation unit.
G/L accounts are mapped to FS items.
The data release task can be run from the Data Monitor using the Update function. As a result, the task logs screen is shown.
If you use the Start w. Selection option instead of Update, and then select the Classic Result Screen option, the system opens the classic result screen after execution of the data release task.
Note
In theRelease of Universal Documents - Result screen, you can see the following:
After you closed the period in accounting, data release should be run for the last time (for that period). After you run Release of Universal Journals, you can then block the task.
When transferring accounting financial data, the system derives the posting period based on the accounting posting date and the period definition of the assigned fiscal year variant (FYV).
Example: You assign the K4 (Calendar Year, 4 Special Periods) FSV to a consolidation unit and make an accounting posting using December 31 as the posting date and any of the four special periods (13, 14, 15, or 16) as the posting period. In group reporting, the system releases data using the same special period as in accounting.
When you had used the Start w. Selection option, you are in the Release of Universal Documents - Result screen. From there you can access the Documents view to display the data by FS Item (Summary Result based of (Financial Statement Item) .
You can then toggle to the G/L account (Summary Result based of (Account Number)) view as well.
After data is released into group reporting, the Line Item Validation is run. This detects incorrect sub assignments such as a missing trading partner for an intercompany account. Sub-assignment issues would most likely need to be fixed in accounting and then data release would need to be run again.
If there’s a G/L account that isn’t mapped to an FS item, the data validation log displays an error. To resolve this G/L account-mapping issues, complete the following steps:
As a result, the value for the previously unmapped G/L account will be in group reporting and the log won't display any errors.
You can use the Schedule Jobs for Consolidation Tasks app to schedule and monitor jobs for consolidation tasks using the provided templates. If you have manual activities that you often need to do at a specific time (such as data release), this app can reduce your workload by automatically running these tasks smoothly in the background.
To schedule data release, complete the following steps:
Note
The preparation for consolidation group changes and reclassification job templates bundle multiple tasks.
In this video, you'll see how to schedule the data release task. Scheduling the data release is similar to scheduling other tasks.
At ABC Corporation, new postings in the general ledger need to be released into group reporting. You need to learn how the data release process works.
The new postings in the general ledger need to be released into group reporting. You need to learn how the data release process works.
Note
The main steps in this exercise are:
From the Consolidation Data Preparation group open the Data Monitor tile.
Go to the Consolidation Data Preparation group.
Select the Data Monitor tile.
Right-click on World and choose Open Period.
In the ribbon, click on Global Parameters, remove World, and choose Continue.
Click on Global Parameters, enter Cons. Group World and choose Continue.
Run the Release Universal Journal task for DE## using the Start w. Selection update possibility.
Right-mouse click the "x" icon in the cell at the intersection of DE## and Rel Uni.J.
Choose Start w. Selection.
Release the data with the following settings:
| Field | Selection |
|---|---|
| Current Period - Delta | select |
| Classic Result Screen | select |
| Test Run | de-select |
On the Release of Universal Documents for Consolidation page enter the information provided in the table.
Choose Execute.
In the Release of Universal Documents for Consolidation dialog choose Continue.
View the document for the U## line item. Toggle to the view accounts. Return to the Data Monitor. Finally, return to the SAP Fiori Launchpad Home Page.
Select the line with version U##.
Choose Documents.
Choose Toggle View in the lower right of your screen.
Choose Continue.
Choose <(Back) until you are in the Data Monitor.
Choose the 
icon to return to the SAP Fiori Launchpad Home Page.
When a Line item Validation task is executed in the data monitor, all the validation rules of following two validation rule types are always run:
So all Line Item Validation tasks check the same validation rules!
Custom validation rules are maintained with the Manage Substitution/Validations Rules - Group Journal Entries app.
The following figure gives an overview of line item validations during the consolidation preparation process.
For the Line Item Validation of the Reported Financial Data and the Manual Postings according to the figure above, no task has to be defined, assigned and executed in the data monitor since the validation is automatically done in the background when data is provisioned.
For the Line Item Validation of the Data to Release, Released and corrected data and Rep. Data for staggered close according to the figure above, different Line Item Validation tasks have to be created and executed from the data monitor.
Especially for the Released and corrected data it is strictly recommended to run a subsequent line item validation task to check the data consistency since these data records are not checked during the entry on these posting levels.
To detect missing mappings between G/L accounts and FS items, assign content task S015 - Line item Val. on Acct. LIs to the data monitor and execute this Line Item Validation task before the data release task in the data monitor. You can then correct the missing mappings between G/L accounts and FS items and finally execute the data release task.
For example, you have the following entry in ACDOCA:
The Line Item Validation task can be run in the data monitor or using the Schedule Jobs for Consolidation Tasks app.
Note
At ABC Corporation, you've released data from accounting into group reporting. Now you want to run the built-in line item validation task.
The main steps in this exercise are:
Note
From the Consolidation Data Preparation group open the Data Monitor tile.
Go to the Consolidation Data Preparation group.
Select the Data Monitor tile.
Run the line item validation for DE## and view the log for the U## version. Finally, return to the SAP Fiori Launchpad Home Page.
Right-click on the intersection of DE## and LIV GR
Choose Update.
The built-in validation task is run and the Line Validation - Task Log screen opens.
See the following example for group 90:
Note
Note
Note
Choose the 
icon to return to the SAP Fiori Launchpad Home Page.
Use the Display Group Journal Entries tile to display the release document for version U##.
Go to the Consolidation Data Preparation group.
Open the Display Group Journal Entries tile.
In field Version enter U## and choose Go.
In the details of the first line item, confirm that the posting level is Realtime Update. Finally, return to the SAP Fiori Launchpad Home Page.
Right to the first Document Number row choose >(Details) .
Choose the icon to return to the SAP Fiori Launchpad Home Page.