Different types of derivations in COPA
Different types of derivations in COPA:
This blog post will give you information about the various types of derivations available in COPA and specific scenarios with examples for which these can be used.
There are in total 5 types of derivations as below:
- Derivation rule
- Table look up
We will discuss each type in detail along with its usage. First of all, we need to understand why we require derivations.
Derivation in COPA is a functionality through which we can derive the value of any field defined as COPA characteristic, from other fields within or outside COPA. We can derive master data fields and configuration values as well.
Since COPA is a management reporting tool so it requires different characteristics to flow from different places like SD, MM, FI and combine them together so as to present better reporting.
Now, we will check each type of derivation in detail:
- Derivation Rule:
It is kind of direct derivation in which we need to specify source and target fields along with its values. This is useful when client is having requirement to maintain specific values for certain COPA characteristics and then derive those based on certain parameters.
|Controlling Area||Profit Center||Market Segment||Subscription Type||Product Category|
In this table, Co. Area and Profit Center are standard fields which are defined as source fields however Market Segment, Subscription type and Product category are custom fields defined in COPA and taken as target fields.
For these kind of requirements, direct derivation can be written to fetch target values.
Go to transaction code KEDR and click new, it will give you type of derivations which can be used. Select derivation rule and continue.
In the definition tab, select source and target fields as given in table.
If you click on magnifying glass against target fields, you can select if you will get multiple options to overwrite value for target fields.
Another tab is condition tab where any condition can be given, as in upon successful execution of conditions only, derivation will work.
Last tab is Attributes under which you can control the derivation like if you want error should be given if no rule values found, rules values should be maintained with specific dates etc.
After saving of derivation rule, values can be maintained directly from same screen by clicking rule values option.
Once values have been saved, you can test it directly from that screen also.
Click on Test icon and system will take you to COPA PSG segment screen where you can give your input criteria and click on derivation to see if desired values are derived or not.
2. Table Look Up:
Table look up is used when you want the value of some COPA characteristics should be updated based on some pre-conditions which are dependent on table.
As an example, our client requirement is to populate sales order line item field against one COPA characteristics for which we can use table look up.
Benefit of table look up is, it is one time activity of mapping fields from tables so unlike direct derivation as in Ist type, no separate one to one mapping is required.
Let us take an example that one custom characteristic is to be filled as “Customer reference” field in sales order line item data.
For that, we can go with table look up from sales order table (VBKD having customer reference field).
Once source and target fields are defined, conditions and attributes can be used in similar way as mentioned for direct derivation rule type.
Move type can be used in 2 ways:
a) One is if you want the value of one characteristic to flow to another characteristics.
b) Another is if the requirement is to fix the value of any characteristic.
As an example, client requirement is to fix the value of field manufacturer number if certain conditions are met then we can use “move” type.
Similar to move, clear type is used when there is requirement to clear any characteristic value based on certain conditions.
Enhancement is a specific type which is designed for some custom coding logic to be used through User Exit.
If client requirement is such which can’t be met through other types of derivations and some custom code is to be written then this type of derivation is to be used.
There are multiple standard user exits in COPA which can be used to fetch values.
These are the 5 types of derivations which can be used based on different requirements.
Digits specific derivation:
Within derivation, there is another feature to take the values based on specific digits of source or target fields.
To understand this, let us take same example as given in type 2 (table lookup) however in place of fetching complete value from customer reference field, we only require first 10 digits, to be populated in Offer Code.
To do this, click on magnifying glass against customer reference field and you will get the option to define the digits.
Conclusion: There are multiple types of derivations in COPA which can be used for different scenarios based on requirement. It is also possible that a requirement can be met with more than one type of derivation so decide carefully which one you want to use and best suited for your requirement.