Mapping data in the GRDC

JoaoPauloAlmeida_2810 — Wed, 23 Sep 2026 21:03:25 GMT

We're working on GRDC mapping and the idea of source/destination fields but we've a question:
E.g: The source field will map the company where the destination field is consolidation, so the source will send a value with the 'C1000'. Where can we map when the source field is C1000 should be '1000' in the consolidation unit that is the destination field.

For us is not clear where we can do this connection of value data.

Is it by GR Substitution Rule app?

Please let me know about your thoughts.

Regards.

Re: Mapping data in the GRDC

HenrikeGroetecke — Thu, 24 Sep 2026 15:04:34 GMT

Hello, thank you for your question. It has been forwarded to the experts. Kind regards, Henrike

Re: Mapping data in the GRDC

dawid90 — Fri, 25 Sep 2026 20:51:30 GMT

Dear @JoaoPauloAlmeida_2810,

Based on the standard SAP Group Reporting Data Collection (GRDC) mapping functionality this value conversion should be handled in the GRDC mapping file rather than through a Group Reporting substitution rule

In GRDC Data Mapping, the mapping file defines the relationship between input/source dimensions and output/target dimensions. The individual rows in the mapping file represent the mapping rules. SAP describes Data Mapping as an ETL functionality that supports source-to-target mappings and transformations before the data is loaded to the target

For your example the mapping would be:

Source field: Company or the corresponding company field in the source
Source value: C1000
Destination field: Consolidation Unit
Destination value: 1000

For another company the same logic could be:

C2000 -> 2000

Therefore if the source system provides C1000 the corresponding mapping rule should derive 1000 for the target ConsolidationUnit field

In the GRDC mapping file the company-related source field would be defined as an input (I) column and ConsolidationUnit as the corresponding output/target column. SAP explicitly requires ConsolidationUnit to be provided as a target dimension when data is mapped to ACDOCU

I would therefore not use the Manage Substitution/Validation Rules – Group Journal Entries app (F4407) for this requirement. This application is intended to validate, derive, or substitute fields in the Group Reporting journal-entry processing context. It is a separate mechanism from the GRDC source-to-target transformation performed by Data Mapping

GR Substitution Rules would be relevant in a different scenario: if the objective is to derive Group Reporting fields, including the Consolidation Unit as part of the accounting or Group Reporting posting logic. For the requirement described here transforming a source value such as C1000 into target Consolidation Unit 1000 within GRDC Data Mapping the mapping file is the appropriate standard mechanism

More details below:

SAP Help – When to Use SAP Group Reporting Data Collection Data Mapping

SAP Help – Create a Data Mapping Definition

SAP Help – Use a Mapping File Template

SAP Help – Substitution/Validation Rules in Group Reporting

Best Regards,

Dawid

Question Re: Mapping data in the GRDC in Technology Q&A

Mapping data in the GRDC

Re: Mapping data in the GRDC

Re: Mapping data in the GRDC