Introduction
In this two-part blog series, we dive straight into the technical details of the Central Finance Mapping enablers. As avid followers of this transformative solution, we assume that you are already well-versed in the capabilities and benefits of SAP Central Finance. If you are new to the subject and need an introduction to the wonders of Central Finance, there is a plethora of information on this website, but I can recommend this blog post from vinay.dhamnani for a comprehensive overview.
In SAP Central Finance, mapping emerges as a critical component, playing a pivotal role in the seamless conversion of data from source systems to the unified landscape of CFIN. As organisations embark on their CFIN journey, mapping takes centre stage, ensuring the accurate translation of financial information and the preservation of data integrity. zhengzhang.lu has written a detailed blog on SAP Central Finance Mapping which you can read here. I will start this blog series from where he concludes.
In this two-part blog series, we will explore the following in detail.
- Part 1 - Key Mapping - Enable Audit Log for Key Mapping
- Part 2 - Value Mapping - Enable Transports for Value Mapping
Details
Part 1 - Key Mapping - Enable Audit Log for Key Mapping
Value Mappings are maintained in the Central Finance system primarily for Enterprise Structure (Company Codes, Controlling Area etc.) or Reference Data (Payment Terms, Payment Methods, Document Types etc.). Key Mappings, on the other hand, are mostly maintained for Master Data objects (Customers, Vendors, G/L Accounts, Materials etc.).
Value Mappings are mostly configured in the Development system and transported through the landscape into Production. It makes sense as the target mapping objects (such as Company Codes, Payment Terms etc.) are also configured in the Development system, and captured in transports before they move to Test or Production. Master Data is usually created directly in the Production system and does not necessarily need any transports from Development. Hence mapping between source Master Data and CFIN equivalents is maintained directly in Production via Key Mappings.
Since Key Mappings are not transported, the only possibility of tracking changes, deletions or additions is via change logs. However, change logs are not active for Key Mappings by default. This blog describes the various configuration steps required to enable Audit Log or Change Log for Key Mapping.
Configuration Steps
Change Logs are activated at a “Mapping Context” level and not at the level of individual Key Mapping IDs. Transaction Code FINS_CFIN_MAP_MANAGE is usually used as the central point to display, upload, download or delete mapping in Central Finance. But the Mapping entity displayed here is the Key Mapping ID, for example, CUSTOMER_ID for Customer Numbers in the screenshot below. Hence, as a starting point, it is important to identify the Mapping Contexts corresponding to the relevant Key Mapping IDs. For example, the change log for Customer Numbers is activated at the Mapping Context or Main Context 'BusinessPartner' level.
Mapping Entity to Main Context
In this section, we will first explore the steps of identifying the Main Context corresponding to the Key Mapping ID (Steps 1 and 2) before we discuss how to activate the Change Logs for those objects (Steps 3 and 4).
Identification of Mapping Contexts
Step 1: Identify Business Object Type for relevant Key Mapping IDs.
SPRO Path: Cross-Application Components > Processes and Tools for Enterprise Applications > Master Data Governance > Central Governance > Key Mapping > Enhance Key Mapping Content > Define Business Object Identifiers
Identify Business Object Type
Step 2: Identify the Main Contexts to which relevant Business Object Types are assigned
SPRO Path: Cross-Application Components > Processes and Tools for Enterprise Applications > Master Data Governance > Central Governance > Key Mapping > Enhance Key Mapping Content > Assign Business Objects to Main Contexts
Identify Main Contexts
Step 3: Define Mapping Contexts for UKMS or ensure they exist for relevant Business Object Types
SPRO Path: Cross-Application Components > Processes and Tools for Enterprise Applications > Master Data Governance > Central Governance > Key Mapping > Define a Mapping Context for UKMS > Define Mapping Contexts
Please Note: Usually these should exist in the system by default
Define Mapping Contexts
Step 4: Activate Change Logs for Mapping Contexts corresponding to relevant Business Object Types
SPRO Path: Cross-Application Components > Processes and Tools for Enterprise Applications > Master Data Governance > Central Governance > Key Mapping à Define a Mapping Context for UKMS > Activate Change Log for Mapping Contexts
Please add the name of the Main Context, select the checkbox called Changes and save. This should initiate the activation process for the change log.
Activation of Change Log
At this point, the change log for these Key Mapping entities should get activated in the system. The change log activation cannot be transported across systems. These have to be activated at the individual client level. It is recommended that these are activated in the Production system during cutover before any Mapping is loaded. It can be activated retrospectively as well, but calibrating existing changes may take long and it should be thoroughly tested in lower environments.
Please Note: Activation of the Change Log triggers a job in the background of Program RMDG_UKM_LOG_PREPARE.
Job Logs
Job Results of Activation
Results
The results can be seen via Transaction Code FINS_CFIN_KM_AUDIT (Central Finance: Key Mapping Audit). Please work with your Security Team so that you have the right roles assigned for accessing these change logs.
You can search these logs by Date and Time or even by source or target values, but as mandatory inputs, you would need the Business System and Mapping Entity as search parameters. Please see the example of Customer Number Mapping below.
Customer Number Mapping Change Log
Some Mapping Entities have contexts associated with them. For example, Cost Centres can only be mapped within the context of the Controlling Area. In such cases, when you select the Mapping Entity, an additional selection field for the mapping context appears on the FINS_CFIN_KM_AUDIT screen. The search results can be filtered further based on the source or target Controlling Area where required.
Cost Centre Mapping Change Log
Conclusion
Change Logs for Key Mappings can be very handy from a system support perspective. It also provides an additional audit point for any replication inconsistency. Central Finance will not prevent you from changing a G/L Account Mapping halfway through the month (not recommended), and neither would it auto-correct replicated transactions retrospectively. But when the month-end numbers do not reconcile, assessing change logs of such G/L Mappings can prove extremely beneficial in explaining the inconsistencies. However, based on the Master Data volume in the system, change logs would mean additional storage space, so please consult with your administrators so that the systems can be sized up accordingly. Where possible, limit your searches with specific filter criteria while using FINS_CFIN_KM_AUDIT for optimum performance.
This was the first blog in a two-part series. In the next part, we will discuss how to enable Transports for Value Mappings. Hope you found this blog useful.
Reference:
SAP Help Document – History of Key Mapping
Special Thanks:
Andrew Soesanto for setting this challenge up for me.
System Details:
This Blog was written based on S/4HANA 2021 version
System Details
- SAP Managed Tags:
