Central Finance (CFIN) – Cost Object Mapping

This blog post is proposed for the Central Finance implementation project team. Sharing this information based on my experience in Central Finance project. The landscape was SAP 4.6C source system, separate instance of SLT and Target S4 HANA 1709

1. Overview of Cost Object Mapping

Cost object in source system mapped with cost object in central finance system. Central Finance cost object mapping allows to replicate cost objects such as production order, internal order etc. to central finance system cost object. SAP provide many types of the standard mappings in system.

In source system posting can be done on many objects like Internal order, Production order etc. However same cost object can not be created in Target system due to short living & high number. Here requirement of cost object to map all source cost object with target cost object and relation is N:1.

2. Requirement of Cost Object mapping

If any document posted in source system get replicate in target system. In General expense posting required cost object and cost center is most common cost object. However, Cost Centre can be maintained in CFIN system as long-living master data. Source and target cost center mapping can be done in CFIN system via FINS_CFIN_MAP_MANAGE. In case of other cost object like production order, process order, internal order, WBS, maintenance order, QM order etc. These all are short-living cost object. One to one mapping is not possible so there will be N: 1 (Source: Target) mapping need to be done.

3. CFIN Settings

Central Finance configuration available in SPRO.

Define scenario of cost object mapping – In this step you find scenarios of cost object. If your source system internal order replicate in target system with N:1 relation. SAP provide some standard scenario.

SAP Supported notes:

2180924 – Supported scenarios in cost object mapping framework

2394923 – Pilot note – process order is supported in central finance replication

Active Scenario – Once you click on active button, in background table is generated and rule become active.

Edit Scenario – Once scenario is activated and you are doing, and changes expect description. You must regenerate it again.

Delete Scenario- Not to delete standard SAP scenario. If you like to play, please copy and do play. Once data is available in table. You are not able to delete the scenario.

Define mapping rules for cost object mapping scenarios – Value of selected characteristic will be fill in the template. This template can be fill manually or upload as well using excel. There is option of download and upload. Transaction code for this screen is CFIN_MAPPING

Now select the scenario created in previous object like SAP001 (Production order to product cost collector)

There are two type of field description with “Local” meaning that source data and without local meaning the Target data. Once you enter the data in respective field system create the relationship between the source and target cost object. You can view this relationship in table FINS_CFINT_ASGMT.

When creating scenario rules, you should consider the following:

1. An empty field means value any.

2. The more specific rule has higher priority.

3. Rules will conflict with one another if they have the same priority.

3. A built-in check has already been implemented. It can detect both conflicts within one scenario and partial conflicts across scenarios.

Once date enter in template. You can view the data using table name in SE16 or SE16N. (this table created in previous step)

Correct Cost Object Mapping - In this Customizing activity, you can make a correction for the assignment between source/target cost objects, due to a change in the corresponding mapping rules. Sometimes, after the replication of cost objects from source system to target system happens, you might want to change the mapping rules for cost object mapping scenarios. After the change takes place, the already-replicated cost objects need to be remapped according to the new mapping rules. In addition, the related cost object mappings need to be updated according to the new mapping rules.

Delete Cost Object Mapping and Cost Objects – Sometimes, during order master data replication, you need to clean up the existing assignments and created cost objects. In this Customizing activity, you can clean up and delete assignments and cost objects.

This activity only deletes the cost objects; it does not delete the master data and transactional data that refer to the cost objects. Assignments are deleted synchronously, and cost objects are deleted asynchronously. Once an assignment or cost object is deleted, you cannot undo the deletion.

4. Cost object initial load

The initial load must be executed in the right order:          

1. First load the cost objects

2. Perform the initial load of FICO postings

3. Start the initial load of internal CO postings

Initial Load of cost object

1. Performed by SLT

2. Requires configuration of cost object mapping framework in the central framework system

3. Basis for replication: table AUFK and related tables

4. SLT filters

Initial load of cost object (AUFK)

1. Smoke test of cost object

This is an ABAP report in CFIN system.IT reads the cost object directly from the source system via RFC. This tool also tests the creation of a cost object without commit so no cost object will be persisted in the central finance system.

2. Simulation of cost object

The simulation of cost object is the tool to replicate cost object via SLT and through AIF. It simulates the complete replication process without any commit and it is recommended for high volume data.

5. Replication overview

– Initial load and real time replication are done through SLT

– In the central system, payload is handed over to function module FINS_CFIN_CO_OBJECT_ASSIGN

– Based on the mapping rule maintained in step 2 the central system will decide whether to map the local order to an existing central order or to generate a new central order for mapping