Derivation rule is widely used function in SAP COPA. In this blogpost we will explore all the aspects of derivation rule. Below is the taste of blogpost:
- Introduction & use of derivation rule
- Types of derivation rules
- Step by step configuration of derivation rule
- Conclusion
Introduction & use of derivation rule
In COPA documents we know that system collects characteristics and value fields. Derivation rule helps to determine/derive characteristics by having different conditions and rules. It also helps to override what has been derived by the system, you can create a derivation step to determine the characteristic
values during posting of the CO-PA documents.
Disclaimer: This blogpost is a chapter of eBook Controlling Profitability Analysis. In order to consume this blogpost more efficiently, you should have fair understanding of COPA. If you are new to SAP COPA or want to deep dive into this sub-module, then you can consider reading this eBook.
Below infographic helps to understand, how derivation helps to determine/manipulate determination of characteristics in COPA document.
Note: Derivations are used only for characteristics. You can’t modify value fields using derivations.
The CO-PA derivations are defined by five different types of derivation steps:
- Derivation rule – This rule is based on an “if-then” where you define a condition and a derivation to use if the condition is met.
In above image, we can notice product group and strategic business unit is maintained in combination. So it will be like, if product group is ‘100’ then derive strategic business unit ‘electronic’
- Table lookup – System will read a specified table that contains a key that must exist as a characteristic, and then it will derive the field content from this table to the characteristic if the characteristic has the same definition as the table field. It can be used, for example, to derive a value from the material master table that is not present in the posting document. (it will be more clear when we will see config in upcoming section)
- Move – This step will move a characteristic value or a constant to a target field.
- Clear – This step will delete the characteristic value.
- Enhancement – If you want to create a custom program to define the characteristic derivation, use COPA0001.
In below sections we will see the configuration for each characteristics derivation type.
Also read: Functioning of CO-PA in make to order scenario
Step by step configuration of derivation rule
Access the activity using the following navigation options:
| SAP Easy Access | Controlling -> Profitability analysis -> Master data -> Define characteristics derivation |
| Transaction code | KEDR |
Click on the create button
Select the derivation rule and hit enter
You will be prompted with the above screen
In this screen, you’ll enter the step description and then build the derivation rule. In the Source Fields area, you select the “If” condition for the derivation, and in the Target Fields area, you select the “Then” field.
After defining the “If and Then” for the derivation rule, click on Maintain Rule Values button
to update the values for the Source Fields and Target Fields.
Here you can see the rule, as per the rule, whenever the characteristic customer containing value 105 then the sales district characteristics will be updated as NORTH
Read eBook: Manual and electronic bank reconciliation in SAP
Returning to the first customizing screen, two more tabs are left to discuss: Condition and Attributes.
In the condition tab, you can further restrict the derivation rule by defining user filters for the derivation selection. The last tab, Attributes, shows additional options for the derivation rule.
With this condition, now the above derivation rule only be valid for IN country key
In the Attributes tab, you can define whether the system will issue an error when the derivation doesn’t find a value to derive, define if the validation will have a starting date, and restrict the validation by removing the from-to option.
| Common error in practice |
| If you indicate that an error will be issued when no value is found for the derivation, it will block the creation of the CO-PA document, and consequently the FI document. Make sure this is the desired outcome before choosing this option. |
Table Lookup
Click on the create button
Select the table lookup and hit enter
Enter the table name, from which table you want the value in COPA field.
Source Fields
In the below image we can see that following information has to be maintained:
- Origin (Table Name) and Origin Field (Field Name) from standard table
- Origin (CO-PA) and Origin Field (Field Name)
This information works as the basic condition, in the below example we can see the KNA1-KUNNR as source in standard tables and COPA-KNDNR in CO-PA Tables. This means the value in COPA-ARTNR is to be passed on to table KNA1 under field KUNNR to identify the information under target field.
Target Fields
In the below image we can see that following information has to be maintained:
- Origin (Table Name) and Origin Field (Field Name) from standard table
- Origin (CO-PA) and Origin Field (Field Name)
This information under KNA1-KTOKD i.e. Customer account group is identified in the table for KTOKD value available from source field and is passed on to KDGRP field under CO-PA.
This rule will get the customer number from COPA document and search it in KNA1 table, it will find out the customer account group and enter in COPA Field KDGRP.
The functioning of other two tabs condition and attributes is same here also; in condition tab we can assign more condition to apply this rule, e.g. making this rule valid only for specific sales org.
- Move
Hit enter
Here we are moving the product number to material number field
And as required condition tab is also available as this kind of rule cannot be applicable for everyone you can make it specific to any smallest object. E.g. you can validate this rule to one customer also.
- Clear
Select clear
As the name suggest, it will remove the values from field region in COPA.
These are all use cases and config of derivation rule in COPA.
Conclusion
Derivation rule is very important function of SAP COPA and it is used very often. At start the maintenance of rule may seem complicated, but once you configure it and test the result it becomes very easy and useful tool. You will find this structure of derivation rule configuration in multiple submodules like treasury & logistics.
Watch same blogpost in video format::
Hope you enjoyed reading the post. You can subscribe to our newsletter to get update of new blogpost.
Nenhum comentário:
Postar um comentário