This blog is intended for project members responsible for implementing Central Finance. this blog explains the various options for Cost Object Framework and the special Considerations for Cost Object Framework along with pre-requisites. it Covers the Understand of supported cost object mapping scenarios , Configure cost object mapping scenarios and Define cost object mapping Rules.
Introduction: with The Cost Object Framework, a cost Object in the source system can be mapped to a cost object in central Finance system. You can customize how a cost object in the source system is mapped to a cost object in target system. Cost object in the central system can be generated automatically, according to the customization, mapping information between cost object in the source system and central system. The changes of cost object in the source system, can be updated to the already replicated cost object in the central finance system.
Define Scenarios for Cost Object Mapping: In the Customizing activity Define Scenarios for Cost Object Mapping, you can define, activate, and delete scenarios for cost object mapping
Defining scenarios for cost object mapping builds mapping between the following:
- The source production order and target product cost collector
- The source production cost collector and target product cost collector
- The source internal order and target internal order
- The source maintenance order (service order) and target maintenance order
- The source quality management order and target quality management order
This makes it possible for the FI/CO documents from the CO source objects to be posted to the replicated CO objects in the Central Finance system. Once a CO source object (for example, an internal order or product cost collector) has been created in the source system, it is replicated in the Central Finance system by using the relevant scenario and its mapping rules.
Customer fields contained in the customer include CI_ AUFK of the table AUFK are also supported Note that you can also access this CO configuration by calling transaction SE54, choosing Edit View Cluster, entering the view cluster FINS_CFINVC_COST_OBJECT and choosing Test.
You create scenarios under this CO configuration, to define how a cost object category in a source system is mapped to a cost object category in the Central Finance system. When you activate a scenario, the system uses a metadata set to generate a mapping table. After you define mapping rules for scenarios, you can use the scenario to map a source cost object to a target cost object.
|Scenario Template||Cost Object in Source System||Cost Object in Central system||Cardinality|
|Sap001||Production Order||Product Cost Collector||N:1|
|Sap002||Product Cost Collector||Product Cost Collector||1:1|
|Sap003||Internal Order||Internal Order||N:1/1:1|
|Sap004||Service Order (PM Order)||Service Order (PM Order)||N:1/1:1|
|Sap005||QM Order||QM Order||N:1/1:1|
|Sap005||Production Order||Internal Order||N:1/1:1|
You can copy these scenarios and use the source characteristics and the target characteristics as defined or you can change the characteristics.
How to create a New Scenario:
You can also create a new scenario.
- To do so, choose New Entries, enter a scenario name, description, and table name, and select a source cost object category, a cost object category, and the cardinality (relationship of objects: 1 to 1, N to 1):
- Save the scenario and select it.
- Click on Source Characteristic. Characteristics are attributes of source and target cost objects. Based on these you can determine which source cost object will be mapped to which cost object. Define the source characteristics that you want to use for mapping. The system adds some frequently used fields (for example, Order Type, Material Number for Order) by default. You can adjust the fields according to your requirements: If you click on New Entries, you see a list of characteristics which you can add to your scenario as source characteristics.
4.Define the cost objects characteristics you want to use for mapping. The system adds some frequently used fields by default. You can adjust the fields according to your requirements: The characteristics are used to: ○ Create a new cost object if it does not exist in system ○ Determine an existing cost object as selection criteria. The indicator Derive from Local means that these characteristics will be used for cost object creation or selection and the value will come directly from the corresponding characteristics of the source cost object, thus you do not need to maintain a value manually for the cost object in the next configuration step. Therefore, you will not be able to edit the fields with this indicator in the next step.
- Save and activate the scenario. During the activation, a transparent table is generated in the back end and the status of the scenario becomes active.
Afterwards, you can edit a scenario but if the scenario has already been used when transferring a document, the system will only allow you to edit the scenario description. If you have to edit it, remember to activate this scenario again here to regenerate the mapping table. To copy a scenario, you select an existing scenario, copy, and then follow the same steps as when you create a scenario starting by entering a scenario name, description, and table name. To delete an existing scenario, check for assignment data and mapping data:
- If assignment data exists for the selected scenario (documents have been replicated using this scenario), you cannot delete the scenario.
- If mapping data exists for the selected scenario, the system displays a warning message and you must confirm the deletion. Mapping data is done in the next configuration step Define Mapping Rules for Cost Object Mapping Scenarios, which can be accessed also via transaction CFIN_MAPPING.
Define Mapping Rules for Cost Object Mapping Scenarios:
In this Customizing activity, you define the mapping relationship between source cost objects and cost objects for Central Finance. You can also access it by calling transaction CFIN_MAPPING.
- Select the scenario you created in the previous step, which determines how a source cost object category (for example, a production order) is mapped to a cost object category (for example, a product cost collector). Choose Execute:
- Enter the details of a source cost object in the fields marked with local: Note that all the source characteristics (for example, order type, material number for order) that you included when you created the scenario in the previous configuration step should be available here so you can enter the relevant values. Note also that if you do not enter source characteristics, the system can match any characteristic to the cost object (N:1).
- The system enters the relationship between the source cost object and the target cost object in an assignment table based on the scenarios you have created for cost object mapping and on which source cost object is mapped to a target cost object
When creating scenario rules, you should take into account the following:
- An empty field means value any.
- The more specific rule has higher priority.
- Rules will conflict with one another if they have the same priority.
- A built-in check has already been implemented. It can detect both conflicts within one scenario and partial conflicts across scenarios.
Once you have created your scenario, you can check if it conflicts with other scenarios, or if different line items from the same scenario result in a conflict. In this case, if you try to save this scenario the system will issue an error message and you must first correct the scenario. If, for some reason, no error message is triggered, a runtime error will be issued during cost object replication.
Upon creation of new cost object, the system automatically creates a new entry in the mapping table FINS_CFINT_ASGMT
Smoke Test for Cost Object Mapping and CO Document Replication:
In this customizing activity, you simulate cost object mapping by executing all the necessary checks, without creating the cost object mapping and is intended to help you find missing customizing and master data before data replication via SLT takes place.
Edit /Correct Cost Object Mapping:
In this customizing activity, you correct the assignment between source and target cost objects, due to a change in the corresponding mapping rules. Sometimes, after cost objects have been replicated from source system to target system, you may want to change the mapping rules for cost object mapping scenarios. After you have made the change, the cost objects that have already been mapped must 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. This activity achieves both above. The target cost object created under the old mapping rule is not deleted.
Delete Cost Object Mapping and Cost Objects:
You use this activity to clean up the assignments and cost objects created during the initial load. It is important to clean up the data in the Central Finance system in order to avoid problems with a subsequent initial load. This activity only deletes the cost objects; it does not delete the master data and transnational data that refers to the cost objects. Assignments are deleted synchronously, and cost objects are deleted asynchronously. Once an assignment or cost object has been deleted, you cannot undo the deletion.
Relevant Sap Notes :
2303031 – Central Finance: Support Customer Fields in Cost Object Mapping Framework
2180924 – Supported scenarios in cost object mapping framework
2394923 – Support process order in Central Finance
2308365 – Central Finance: More details of Cost Object Change Replication
- Below Fields cant be removed from Source Characteristic and Central Characteristic of Cost Object Framework Configuration .
|Internal Order||ASTKZ||Identifier for Statistical Order|
|Production Order||AUART||Order Type|
|Maintenance Order||AUART||Order Type|
|VAPLZ||Main work center for maintenance tasks|
|Quality Management Order||AUART||Order Type|
2. AUFK (order) Must not be created with Date Filter in SLT .
3. COBK filter Should match with the Initial Load setting in Source system VCFIN_SOURCE_SET .
4. Delete Cost Object Mapping and Cost Objects- If you execute this transaction code system will delete all Data from assignment table even Transaction data is exist .
5. You cant change the configuration in Cost object framework even some data available in the assignment table in the other client ,as its cross client configuration .
6. Below CO Bus.Transaction Types only Supported by SAP Cfin for secondary posting .
|KAMV – Manual Cost Allocation|
|KOAL – Actual Settlement of Internal Activity Allocation|
|KOAO – Actual Settlement (Not for CO-PA scenario)|
|KSI0 – Actual Cost Center Split|
|KSI1 – Actual Split Costs (Primary)|
|KSI2 – Actual Split Costs (Secondary)|
|KSI3 – Actual Split Costs Internal Activity Allocation|
|KSII – Actual Price Calculation|
|KZPI – Actual Overhead (Periodic)|
|RKIU – Actual Overhead Assessment|
|RKIV – Actual Overhead Distribution|
|RKL – Actual Activity Allocation|
|RKLN – Revaluation at Actual Price|
|RKLT – Actual Template Allocation|
|RKU1 – Repost Costs|
|KZPR – Actual Overhead (Realtime)|
|RKIL – Actual Inverse Activity Allocation|
|RKS – Enter Statistical Key Figures|
|RKLX – Predistribution of fixed costs|
|KAZI – Actual cost center accrual|
|RKIB – Actual Periodic Reposting|
|RKU2 – Repost revenue|
|KTDA – COPA: TOP-DOWN: Actuals|
|RRIU – Segment adjust.: Act. Assess.|
|RRIV – Segment adjust.: Act. distrib.|
|RKN – Actual non-alloc. activities|
|KOLI – Collective order delivery|
|RRIB – Seg. adjust.: Act.per.repost|
|RKU3 – Repost CO line items|
|GPDP – Distribution Primary Costs|
|GPDS – Distribution Secondary Costs|
This blog is very useful for all the customers and Consultants who are planning to implement Central Finance .it Covers the Consideration of Understand the supported cost object mapping scenarios , Configure cost object mapping scenarios and Define cost object mapping Rules.