Skip to Content
Technical Articles

SAP Central Finance (CFIN) Introduction Part 2 – Mapping

Hi All,

 

One of the main purposes of Central Finance is to load/replicate data from the source system to the S/4 HANA system. But before we can start the data load, the business mapping between the systems should be configured.  In this blog post, I would do a brief introduction to the key function.

This blog post is based on my system’s configurations (system version S/4HANA 1709). Different system versions may have different configuration paths. You may need to find the correct ways by yourself based on your system’s version, configurations, enhancements, and business requirements.

Before reading the blog post, let’s imagine a simple scenario, there is a company that has 1000 open A/P invoices created from the purchase orders (the goods receipts and invoice receipts were generated successfully without issue) in the source system (an SAP system). The company wants to load the documents to the Central Finance system for testing purposes. The objects in the source system should link to different identifiers/codes in the Central Finance system. In this scenario, how many objects should be mapped between the source system and the Central Finance system? (Please be aware, there is not a certain answer to this question as different systems may have different configurations and scopes.)

# Overview of Mapping in Central Finance

The mapping between the source system and the Central Finance system can be identified into three categories:

Mapping for ‘Business Object Identifiers’

This is the ‘Key Mapping’ for the IDs (for example customer ID, vendor ID or material ID) between the systems. This is done through MDG key mapping functions.

Mapping for ‘Codes’

This is the ‘Value Mapping’ for the codes (for example company code, business area or country code) between the system. This is done through MDG value mapping functions.

Mapping for ‘Short-living Cost Objects’

Sometimes, there are some short-living cost objects (for example production order, internal order) that should be mapped between the systems. This kind of mapping is done through the Customizing in the Central Finance system.

In addition to the three mapping categories, some Business Add-ins (BADIs) can be used to do the mapping in the Central Finance system.

# How to configure the mapping?

After we have an overview of the mapping categories, the next question is how can we configure the mappings?

As mentioned, mapping happens between the source system and the Central Finance system. So firstly, we should maintain the systems’ information in the Central Finance system.

‘Set Up System’

Configuration Path:

SPRO-Financial Accounting (New)-Central Finance-Central Finance: Target System Settings-Set Up Systems

We should make sure the RFC destination, logical systems are maintained correctly in the configurations ( ‘Set up RFC Destination for Source System’, ‘Maintain Source Systems and RFC Assignments’, ‘Check Logical System Assignment for Central Finance Client’, ‘Assign RFC Destination for Displaying Objects from Source System’).  Other configurations are needed for other purposes, I will introduce them in another blog post.

‘Define Technical Settings for All Involved Systems’

Configuration Path:

SPRO-Financial Accounting (New)-Central Finance-Central Finance: Target System Settings-Mapping-Define Technical Settings for All Involved Systems

We should maintain the relationship between the business system name and the logical system name (maintained in the above step) on the list.

Please be aware, ‘Central Finance uses the System Landscape Directory (SLD) to determine the local business system.’ So, the business system information in SLD and access to SLD should be maintained correctly. SLD configuration is not in the scope of this blog post.

In the same configuration, we can add the restrictions at the business object type level for the systems.

‘Define Mapping Actions for Mapping Entities’

After we defined the systems’ information. We may want to define different mapping actions for different mapping entities at the system level.

Configuration Path:

SPRO-Financial Accounting (New)-Central Finance-Central Finance: Target System Settings-Mapping-Define Mapping Actions for Mapping Entities

The mapping entities can be found from the list.

Users can define which mapping action is needed for the mapping entity.

There are four mapping actions can be used:

‘Keep Data’: Reuse the original data from the source system in the Central Finance system

‘Mapping Obligatory’: Must be mapped in the Central Finance system, otherwise the system will raise an error

‘Map if Possible’: the system will try to do the mapping, but if there is no map existing then the system will reuse the original data from the source system and no error will be raised

‘Clear Data’: ‘fields of this kind area are always cleared’

For example, there are two source systems, ‘system A’ and ‘system B’. After analysis, we think company code from system A should be reused in the Central Finance system and company code from system B may need additional mapping, but if there is no mapping exist then the company code should be reused in the Central Finance system. In this scenario, we can select the mapping entity ‘BUKRS’ from the list and set the system A’s mapping action is ‘Keep Data’ and the system B’s mapping action is ‘Map if Possible’.

‘Define Mapping Entities (Enhanced Configuration)’

Sometimes we may want to add a customizing mapping entity or we want to add fields to the pre-delivered mapping entities. This can be done through this customizing activity.

Configuration Path:

SPRO-Financial Accounting (New)-Central Finance-Central Finance: Target System Settings-Mapping-Advanced Settings-Define Mapping Entities (Enhanced Configuration)

Users can use ‘Define Mapped Fields(Customer)’ to define the fields which will be used for the mapping entity, ‘Definitions made here override definitions delivered by SAP.’

Before you do any change here, I recommend you carefully read the ‘IMG activity documentation’ of this customizing activity and make sure you have fully understood the usage and restriction of this customizing activity.

‘Define Key Mapping (ID Mapping)’

Before we add a new key mapping record, we should clearly understand what is key mapping and why we need it. A good example and a detailed description of key mapping have been provided in the path below. I advise you to read it first before continue reading this blog post.

Path:

SPRO-Financial Accounting (New)-Central Finance-Central Finance: Target System Settings-Mapping-Define Key Mapping (ID Mapping)-General Information

After understanding what is key mapping and why we need it, the next question is how to configure it.

Configuration Path:

SPRO-Financial Accounting (New)-Central Finance-Central Finance: Target System Settings-Mapping-Define Key Mapping (ID Mapping)-Create and Edit Key Mapping

This customizing activity is web-based, you can also open the web page by transaction code MDG_KM_MAINTAIN.

The screenshot below is an example of business partner key mapping between the source system and the Central Finance system. This key mapping is for map business partner ‘100’ in the source system to business partner ‘300001’ in the Central Finance system. If there is another business partner from another source system that should also be mapped to business partner ‘3000001’ in the Central Finance system, we can use the ‘Add Row’ button to add a new record with different ‘System ID’ and ‘Object ID’.

‘Define Value Mapping (Code Mapping)’

Before we can maintain the value mapping at the field level, we should create a code list for the element and system. After we create the code list, a namespace will be arranged by the Central Finance system for the specific source system’s value mapping.

Configuration Path:

SPRO-Financial Accounting (New)-Central Finance-Central Finance: Target System Settings-Mapping-Define Value Mapping (Code Mapping)-Assign Code Lists to Elements and Systems

The key elements of this assignment can be found from the ‘IMG Activity Documentation’ of this customizing activity.

The ‘Type’ and context structure of the global data type can be found from the related mapping entity (we introduced ‘Mapping Entity’ in the blog post).

After the code list is created, we can start to maintain the value mapping.

Configuration Path:

SPRO-Financial Accounting (New)-Central Finance-Central Finance: Target System Settings-Mapping-Define Value Mapping (Code Mapping)-Maintain Value Mapping

In the general case, there is no need to change any value in the list. We should find the global data type from the list and click the ‘Navigation’ button.

In this blog post, I will use ‘BUKRS’ (Company Code) as an example.

Step 1: Find the GDT from the list and click the ‘Navigation’ button

Step 2: Input values for the fields: ‘Mapping ID’, ‘List Agency ID’, ‘List ID’, ‘List Version ID’ and ‘Internal List ID’.

Reuse the values (‘List Agency ID’, ‘List ID’, ‘List Version ID’ and ‘Internal List ID’) which we maintained in customizing activity ‘Assign Code Lists to Elements and Systems’ at here.

Step 3: Define value mapping for the specific source system

I want to map the company code ‘ZJC1’ in the Central Finance system to the company code ‘ZMC1’ in the source system.

‘Cost Object Mapping’

We should first define/maintain the cost object mapping scenarios and then define the mapping rule for the mapping scenarios.

‘Define Scenarios for Cost Object Mapping’

Configuration Path:

SPRO-Financial Accounting (New)-Central Finance-Central Finance: Target System Settings-Mapping-Define Cost Object Mapping-Define Scenarios for Cost Object Mapping

There are 5 pre-delivered template scenarios that can be found from the list (dependent on the system version).

1. ‘Source Characteristic’ and ‘Central Characteristic’

The ‘Source Characteristic’ and ‘Central Characteristic’ defines which fields will be used to do the cost object mapping for the specific scenario.

It is noted that the fields (‘Source Characteristic’, ‘Central Characteristic’) of the template scenarios are unchangeable. Users can copy the template scenario to a new scenario and change the fields.

2. ‘Production Order’

‘Production orders are too detailed for Central Finance and thus are not replicated’.  So the production orders in the source system will be mapped to the product cost collectors in the Central Finance system.

3. ‘Cardinality’

There are two cardinalities can be used to do the cost object mapping.

‘1:1’ means one object in the source system can be mapped to one object in the Central Finance system. Otherwise, an exception will be raised by the system.

‘N:1’ means multiple objects in the source system can be mapped to one object in the Central Finance system.

 

‘Define Mapping Rules for Cost Object Mapping Scenarios’

Configuration Path:

SPRO-Financial Accounting (New)-Central Finance-Central Finance: Target System Settings-Mapping-Define Mapping Rules for Cost Object Mapping Scenarios

After selecting the mapping scenario, users can input the values to the fields defined in the mapping scenario (‘Source Characteristic’ and ‘Central Characteristic’).

Things below should be considered when users define the mapping rules:

  • If there is nothing inputted in one field, then this field means value any.
  • When there are two mapping rules defined for one Central Finance object, the rule has more specific values that have higher priority.
  • If two rules defined for one Central Finance object and the two rules have the same priority, then conflict will appear.
  • Conflict within one scenario or conflict between scenarios may happen. A built-in check has been implemented. But sometimes the check not catch the conflicts then a run time issue will appear, users may need to check the issue in transaction code ST22.

 

‘Correct Cost Object Mapping’

Configuration Path:

SPRO-Financial Accounting (New)-Central Finance-Central Finance: Target System Settings-Mapping-Correct Cost Object Mapping

Sometimes we may want to change the mapping rules after the data has been loaded/mapped based on the mapping rules. After the change happens, we should use this customizing activity to update the related cost objects based on the new mapping rule.

 

# Summary

This blog post gave a brief introduction to mapping configurations in the Central Finance system. The ‘COPA Mapping’ will be introduced in another blog post. I hope this blog will give you some ideas about how to do the mapping configurations between the source system and the Central Finance system.

Let’s come back to the question asked at the beginning of the blog post, could you share your idea in the comment area?

In the next blog, I will introduce ‘Account Receivable’ and ‘Account Payable’ in the Central Finance system.

Best regards,

Jason Lu

 

2 Comments
You must be Logged on to comment or reply to a post.
  • Hello Jason Lu, You have explained the basic mapping concepts with great details. Many thanks for sharing your knowledge here.

    Can you please elaborate a bit on the Value Mapping – Step 2: Input values for the fields: ‘Mapping ID’, ‘List Agency ID’, ‘List ID’, ‘List Version ID’ and ‘Internal List ID’.

    Is there any naming convention for Mapping ID ? what is List Agency ID and the Internal List ID purpose  ?

    • Hi Sesha,

       

      Please check my answers.

       

      1. Is there any naming convention for Mapping ID?

      I do not think there is a naming convention, if you keep the field empty when you save your change, the system will generate a number for it. But you can also give a number to it.

       

      2. What is List Agency ID and the Internal List ID purpose?

      Internal List ID‘ is only needed for the global data type (GDT) has a context structure.

      For example, the ‘Dunning Area’ (MABER) has a context structure ‘BUKRS’.

      You can find the context structure information from SPRO-Financial Accounting (New)-Central Finance-Central Finance: Target System Settings-Mapping-Advanced Settings-Define Mapping Entities (Enhanced Configuration)

      List Agency ID‘: The system will use ‘List Agency ID’, ‘List ID’, ‘List Version ID’ to identify a source system in the code mapping process. You can use the ‘Business System’ name as the ‘List Agency ID’ in customizing activity ‘Assign Code Lists to Elements and Systems’ (‘We recommend that you enter the business system of the source system.‘). Simply say, you can think this field is to identify the source system.

      For example, I have source systems SYS1001 (Business System name) and I want to map company code from the source systems to the target system SYS3001. I will set the ‘List Agency ID’ to ‘SYS1001’ (in customizing activity ‘List Agency ID’ in customizing activity’ and ‘Maintain Value Mapping’) as recommended.