In Group Reporting, consolidation versions are used to separate data in the database for different consolidation purposes. Each type of task, therefore, supports the use of consolidation versions according to task-specific needs. In this blog, I would like to share how the Total Validation and Intercompany Elimination tasks support the consolidation extension versions.
Total Validation
Total validation tasks check the reported, standardized, or consolidated data against the predefined validation rules. With the introduction of the consolidation extension, validation tasks are also enhanced in multiple releases. Below is the release information for supported features:
*GC = Group Currency, LC = Local Currency
Support in SAP S/4HANA (on-premise edition):
(*) Apply notes 3363948 and 3364587 to down port the feature to S4 2022.
When validating data of GC extension version or regular extension version, the system aggregates the data according to the defined version stack. For example, extension version Y11 is defined as an extension version that references standard version Y10, with local currency data stored. In the consolidation database table ACDOCU, we have the following data stored:
The account balance for the data validation run is below:
Be aware the assignment of validation method (a group of rules) to consolidation unit/group is based on data entry special version. Suppose you want the different rules to be checked for the different extension versions, you need to create various data entry special versions, then assign the validation methods individually under those special versions. Otherwise, the extension versions share the same special version as the reference version.
In the below example settings, the system uses the validation rule group S001 for the data check for standard version Y10 and GC extension version Y11 but a different rule group S002 for extension version Y12.
When running validation tasks for the standard version, the corresponding extension versions with automatic run mode will be run in parallel with the standard version. By contrast, users can manually trigger the data validation for extension versions with run mode "Manual run".
After the validation, GC extension versions and extension versions validation results can be independently displayed in the Manage Validation Result app or Task Logs app.
There is also a business request to check the data across versions, e.g., if balance of account A exists for version Y10, then balance of account B should also exist in version Y11. In general, such capability is not available yet, but some customers use the version stack to partially achieve cross-version data check.
In summary, total validation tasks can support extension version concept well and the cross-version data check feature will be considered in future enhancement.
Intercompany Elimination
Intercompany matching and reconciliation (ICMR) solution can support end-to-end data matching, reconciliation, and elimination. Two data models (with CDS views) are pre-delivered by SAP to support different business purposes. As the purposes differ, the extension version support differs for each data model.
The reconciliation case uses this data model can read reported data from S/4HANA accounting data table (ACDOCA) and the data of non-S/4HANA consolidation units from consolidation data table (ACDOCU) in real time for document matching, reconciliation, and IC elimination. In reality, document matching is only needed once for the standard version, but the elimination should be done for both the standard version and GC extension versions. Since SAP S/4HANA Cloud 2302, ICMR can generate elimination postings for GC extension versions when running IC elimination task for the standard version. For on-premise editions, this feature will be released in the coming S/4HANA 2023 release. Customers with earlier releases can apply SAP Note 3303956 to get the feature implemented.
If customers want to do intercompany elimination for extension versions other than GC extension versions, they need to use a reclassification task. The system checks and prevents the assignment of a task group with IC elimination task to extension versions.
This data model is mainly for reporting purposes and is not recommended for IC elimination use. Customers use this data model for reconciliation reporting for all types of versions. For example, users can define a reconciliation case based on this data model, then display reconciliation balance data for both standard and extension versions. The system reads the defined version stack for the extension version to sum up the data from the standard version and the delta data in the extension versions.
More Information
For more information, you can refer to the following:
Total Validation
Total validation tasks check the reported, standardized, or consolidated data against the predefined validation rules. With the introduction of the consolidation extension, validation tasks are also enhanced in multiple releases. Below is the release information for supported features:
| Support in SAP S/4HANA Cloud: | GC Extension Version | Extension version with run mode "Automatic Run" | Extension version with run mode "Manual Run" and LC values stored | |
| LC values not stored | LC values stored | |||
| Reported Data Validation | N/A | N/A | Yes | Yes |
Standardized Data Validation | Yes | Yes | Yes | Yes |
| Consolidated Data Validation | Yes | Yes | Yes | Yes |
*GC = Group Currency, LC = Local Currency
Support in SAP S/4HANA (on-premise edition):
| GC Extension Version | Extension version with run mode "Automatic Run" | Extension version with run mode "Manual Run" and LC values stored | ||
| LC values stored | LC stored | |||
| Reported Data Validation | N/A | N/A | Since 2023 FPS0 | Since 2023 FPS0(*) |
Standardized Data Validation | Since 2020 FPS1 | Since 2020 FPS1 | Since 2020 FPS1 | Since 2023 FPS0(*) |
| Consolidated Data Validation | Since 2020 FPS1 | Since 2020 FPS1 | Since 2020 FPS1 | Since 2023 FPS0(*) |
(*) Apply notes 3363948 and 3364587 to down port the feature to S4 2022.
When validating data of GC extension version or regular extension version, the system aggregates the data according to the defined version stack. For example, extension version Y11 is defined as an extension version that references standard version Y10, with local currency data stored. In the consolidation database table ACDOCU, we have the following data stored:
| Account 1 | Account 2 | Account 3 | |
| Y10 | 1000 USD | 100 USD | |
| Y11 | 100 USD | 100 USD |
The account balance for the data validation run is below:
| Task run | Account 1 | Account 2 | Account 3 |
| Version Y10 | 1000 USD | 100 USD | |
| Version Y11 | 1100 USD | 100 USD | 100 USD |
Be aware the assignment of validation method (a group of rules) to consolidation unit/group is based on data entry special version. Suppose you want the different rules to be checked for the different extension versions, you need to create various data entry special versions, then assign the validation methods individually under those special versions. Otherwise, the extension versions share the same special version as the reference version.
In the below example settings, the system uses the validation rule group S001 for the data check for standard version Y10 and GC extension version Y11 but a different rule group S002 for extension version Y12.
When running validation tasks for the standard version, the corresponding extension versions with automatic run mode will be run in parallel with the standard version. By contrast, users can manually trigger the data validation for extension versions with run mode "Manual run".
After the validation, GC extension versions and extension versions validation results can be independently displayed in the Manage Validation Result app or Task Logs app.
There is also a business request to check the data across versions, e.g., if balance of account A exists for version Y10, then balance of account B should also exist in version Y11. In general, such capability is not available yet, but some customers use the version stack to partially achieve cross-version data check.
In summary, total validation tasks can support extension version concept well and the cross-version data check feature will be considered in future enhancement.
Intercompany Elimination
Intercompany matching and reconciliation (ICMR) solution can support end-to-end data matching, reconciliation, and elimination. Two data models (with CDS views) are pre-delivered by SAP to support different business purposes. As the purposes differ, the extension version support differs for each data model.
- Data Model with accounting data and consolidation data union (e.g. CDS view ICA_CONSJOURNALENTRIES_4)
The reconciliation case uses this data model can read reported data from S/4HANA accounting data table (ACDOCA) and the data of non-S/4HANA consolidation units from consolidation data table (ACDOCU) in real time for document matching, reconciliation, and IC elimination. In reality, document matching is only needed once for the standard version, but the elimination should be done for both the standard version and GC extension versions. Since SAP S/4HANA Cloud 2302, ICMR can generate elimination postings for GC extension versions when running IC elimination task for the standard version. For on-premise editions, this feature will be released in the coming S/4HANA 2023 release. Customers with earlier releases can apply SAP Note 3303956 to get the feature implemented.
If customers want to do intercompany elimination for extension versions other than GC extension versions, they need to use a reclassification task. The system checks and prevents the assignment of a task group with IC elimination task to extension versions.
- Data Model with consolidation table data only (CDS view ICA_CONSJOURNALENTRIES_3)
This data model is mainly for reporting purposes and is not recommended for IC elimination use. Customers use this data model for reconciliation reporting for all types of versions. For example, users can define a reconciliation case based on this data model, then display reconciliation balance data for both standard and extension versions. The system reads the defined version stack for the extension version to sum up the data from the standard version and the delta data in the extension versions.
More Information
For more information, you can refer to the following:
- SAP Financial Consolidation 10.1 Product Availability Matrix
- SAP product strategy for consolidation (SAP Note 2866878)
- SAP S/4HANA for group reporting
- SAP S/4HANA for group reporting Community
- SAP S/4HANA for group reporting Road Map Explorer
- SAP Managed Tags:
