SAP S/4 Central Finance Mapping for FI/CO postings (Initial load and Replication)
In this blog post, I am going to give you an overview of setup required for real time replication of FI Postings (COPA Mapping is not covered in this blog post) in SAP S/4 Central Finance system. Before we dwell into the details, let’s see briefly what is and why to use SAP S/4 HANA Central Finance.
What is SAP S/4 HANA Central Finance?
Central Finance system creates a single financial source of truth for executing reports and finance process. With Central Finance, customers can connect multiple Finance systems such as SAP ECC or any Non SAP Financial system. Data is replicated in Central Finance in real time basis there by allowing the reporting process much simpler and easier than traditional approaches.
Why Central Finance?
Typically, Customers perform ETL process from various systems and do the reporting in OLAP data ware housing tools. This process takes time due to long running batch jobs on nightly / weekly basis and in addition there are several dependencies such as closing the periods across multiple systems. Furthermore, data is not harmonized in data warehouse system and it not easy to reconcile the data and consumes too much time to trace back if there is any problem in account discrepancy let alone the correction process.
As Finance Process built into the Central Finance system, moving the data to separate application is no longer required. Business can run the reports in real time basis thereby providing instant insights. It is also possible to drill down the accounting information to highest granularity. Fast Closing is possible with Financial Closing Cockpit. S/4 HANA Central Finance allows customers to adopt the SAP latest innovations without disrupting their existing ERP systems.
Prerequisites / Setup Required:
- Setup of source system and necessary configuration is completed in SLD (SAP Landscape Directory).
- Before initial load, baseline configuration and mapping must be there in the systems
- SLT (SAP Landscape Transformation Replication server) setup completed and the replication is “real time” as shown below. Typically, the default option would be “Real time”.
- AIF (Application Interface Management) setup completed.
- For real time replication, Initial Load has been completed. In other words, historical data of Cost Objects and FI/CO postings have been transferred to Central Finance System.
- TCODE: LTRC
Setup Required For Real time replication:
1) Source System Settings:
Go to CFINIMG -> Source System settings or alternatively go to SM30 and enter the view “VCFIN_SOURCE_SET”.
Set the Initial Load Flag once the initial load is completed and the FI postings are ready for replication. This setting is required for each company code.
2) Central Finance Target System Settings:
Central Finance Source system -> General Settings: Once Initial load is completed, set the initial load flag. This is similar setting that was performed in source system.
3) Business Mappings:
Business Mapping plays key role in the Central Finance. Data harmonization happens based on the business mappings. Business Mapping can be performed using MDG, but it is not mandatory to use MDG. Instead, this can be performed directly in the Central Finance System.
The following mapping is required both for Initial load and to replicate the data on real time basis.
Mapping Action of Mapping Entity: For each mapping entity, set the mapping action at this level. The following mapping actions are available.
- Keep Data: This action holds the data that is coming from the source system.
- Mapping Obligatory: This action means the mapping is obligatory from source system to Target system, if mapping is missing an error occurs.
- Map if possible: This action means that if possible map the data.
- Clear Data: This action clears the data that is coming from the source data.
Path to Key Mapping:
Central Finance Target System Settings -> Mapping ->Define Key Mapping (ID Mapping) ->Define Mapping Action for mapping entities
For example, if the requirement is to keep the company data as it is coming from the source system, the mapping would look like as follows.
As you see, this mapping action can be setup differently for each source system.
Key Mapping: Any mapping related to master data identifiers are configured at this level. (Ex: G/L Account, Profit Center)
Path to Key Mapping:
Central Finance Target System Settings -> Mapping ->Define Key Mapping (ID Mapping) ->Create and Edit Key Mapping
For example, if the requirement is to map the business object type cost center, the setup would look like as follows.
- Business Object Type: Cost Center
- Business System of Central Finance Instance: Central Finance business system name.
- Object ID Type: Cost Center ID (ERP)
- ID of the Object in Central Finance System: KOSTL
Maintain the configuration using “Add Row” buttons. In the field system ID maintain the source system ID. In the field Object ID, enter the equivalent field of Cost center of the source system.
Hint: To check the existing Key Mapping Settings, use the Transaction code ‘MDG_ANALYSE_IDM‘
- Value Mapping: Each system has its own sets of codes, in order to transform the source codes to target system code (central finance system), perform the mapping in the Value mapping section.
(For ex: Company Code, Country Code). This mapping is at field level.
In this blog post, I am going take an example how to map the field Company Code (BUKRS) in Central Finance system.
Step 1- Assign Code Lists to Elements and Systems
In this step, assign the list ID’s for each Global Data Type per each source system.
- Type – Enter Data Element (As BUKRS is straight forward and only field).
- GDT – BUKRS
- Internal List – Leave empty, this is applicable only for fields dependent on another GDT
- Business System – Enter Source system ID. (Enter the source business system configured and mapped on the target side IMG
- List ID – Identifies the external code list.
- List Agency ID – Enter Source system or define the agency responsible (ex-IFRS,GAAP,..)
- (Business system which is defined comes here)
- List Version ID – enter “01”
Central Finance Target System Settings -> Mapping ->Define Value Mapping (Code Mapping) ->Assign Code Lists to Elements and Systems
Step 2 – In this step, select the Global data type that you want to map. In our case it is BUKRS.
By default, this global data type must be available.
Path: Central Finance Target System Settings -> Mapping ->Define Value Mapping (Code Mapping) ->Maintain Value Mapping
Navigate (boxed in red) to the view Assign Code Lists. In our example, we are doing for only one Source system. So enter 1 line item as below. If there is a need to map this field to multiple systems, enter one mapping line item at this level per each source system keeping the Mapping ID unique.
Select the Mapping and click on “Define Value Mapping”. At this level, list all the codes that you would like to map as seen below.
Internal Code Value – Codes present in Central Finance System.
External Code Value – Code from Source System.
In this example, company code RK01 from Source system is mapped to company code “RAJE” in the target system.
Tip: Instead of entering value by value, it is also possible to import multiple values either using csv file or XML using “External Codelist”.
Once the configuration has been completed and master data has been set up, FI transactions will be reposted in Central Finance System oppose to copying the data from table to table. This means the errors could occur while posting the transactions in Central Finance, however it is possible to reprocess the FI documents by analyzing the error and correcting the fix in customization. This is done by AIF (Application Integration Framework).
Tip: Perform Configuration Consistency check prior to Initial Load and Replication using TCODE: “FINS_CFIN_CC” to ensure the configuration settings between source system and Target system are consistent.
Hope this is helpful!