Usually, it is the requirement from most of the clients to do cost allocation to COPA based on Product Revenue. In our example, we will cover how to distribute operating expenses (i.e., Administrative Expenses) posted on cost centers into product wise operating expenses.
In this document we will see how we can define COPA Assessment cycles allocate the expenses to Product using the Variable portions based on Product Revenue.
As we all are aware that Account-Based COPA is simplifying COPA by accounts rather than value fields (used in Costing based CO-PA).
Here we have booked cost to a Cost Center with reference to a Primary Cost Element via FB60 (Vendor Invoicing) and in the month end, this same cost has to be transferred to COPA characteristics for analyzing Product Wise Profitability.
Posting of Expenses using FB60
Displaying the posted document using FB03
Enter a document number, company code and fiscal year and then hit enter.
In below snapshot you can see the accounting document with reference to relevant cost center.
Displaying the Cost in Controlling Report
To display the same results in Controlling reports, use t-code KSB1. Enter a relevant controlling area, cost center, and select the date range and then the execute the report.
In below screenshot results can be seen in the controlling report.
Now to allocate the above posted amount of 200,000 to COPA we need to create a COPA Assessment Cycle.
Define COPA Assessment Cycle
To create a COPA Assessment Cycle, we need to use transaction code KEU1.
Enter a cycle name and start date.
In a cycle you define the sender-receiver relationships and the corresponding distribution rules.
You can define several groups (i.e., Segments) within one cycle. A group contains related sender-receiver relationships.
In below screen you need to maintain text for the cycle and relevant controlling area.
Segment Header:
Within the allocation cycle we need to attach a segment consisting of the details of sender and receiver cost centers and cost allocation basis.
As this has been mentioned earlier that we can define several groups (segments) within one cycle that’s why we need to maintain segment name and description.
Then we maintain the following under Segment Header:
Remember by entering a percentage less than 100%, you can stipulate that only a portion of the sender value is distributed/assessed. The remaining amount is left on the sender.
Rule: This field controls how receiver tracing factors are determined. Like what will be basis of allocation of sender amount to the receiver.
We have the following option:
Relevant to us is the option no. 1 variable portion as we need to allocate the cost based on product wise revenue. This point will be clear further while moving towards receiver tracing factor tab.
Senders/Receivers:
In the below snapshot, under the sender/receiver tab we specify Cost element 65100000 and Cost Center ADMIN_CCTR which needs to be allocated to the receiving products. Parallelly under receiver side we maintain the product range as we need to allocate the cost to product.
Receiver Tracing Factor:
In the below screen, under the receiver tracing factor we maintain the Cost Element 41000000. This is the cost element where the product revenue has been recorded and the system uses this cost element as the tracing factor basis.
Mentioned below is the working for reference.
Sender Cost Center distributes 200,000 to three receivers.
The SAP system calculates the following values:
Receiver 1: 110,000/132,010 X 200,000 = 166,654.04
Receiver 2: 10/132,010 X 200,000 = 15.15
Receiver 3: 22,000/132,010 X 200,000 = 33,330.81
After saving the segment, we can save the allocation cycle.
COPA Reports Before Executing Assessment Cycle:
Before executing the allocation cycle, to verify the posted amount on Cost Element 41000000 use t-code KE30 (COPA Report). In below screenshot we can check the figures with reference to Product and Cost Element.
Here it can be seen that we can’t have Product Wise Admin Expenses breakup before executing assessment cycle we have defined in earlier steps.
KE24 COPA Line-Item Screenshot can be referred to confirm the actual revenue generated on sample products.
Execute COPA Assessment Cycle:
Now we can execute the COPA Assessment Cycle using t-code KEU5.
Enter period, fiscal year and cycle name and then the execute the cycle.
COPA Reports After Executing Assessment Cycle:
Once cycle has been executed, verify the results by using the same KE30 COPA Report and KE24 COPA Line-Item Report. Below are the screenshots for reference. Admin Expenses are now broken down to product level with the help of COPA Assessment Cycles. Additionally, the same has been done based on revenue generated from each product.
Conclusion:
Thanks for reading whole document. This document describes how to break the operating expenses charged to cost center product wise using COPA Assessment in S/4 HANA. For any query, please mention in the comments section.
In this document we will see how we can define COPA Assessment cycles allocate the expenses to Product using the Variable portions based on Product Revenue.
As we all are aware that Account-Based COPA is simplifying COPA by accounts rather than value fields (used in Costing based CO-PA).
Here we have booked cost to a Cost Center with reference to a Primary Cost Element via FB60 (Vendor Invoicing) and in the month end, this same cost has to be transferred to COPA characteristics for analyzing Product Wise Profitability.
Posting of Expenses using FB60
Displaying the posted document using FB03
Enter a document number, company code and fiscal year and then hit enter.
In below snapshot you can see the accounting document with reference to relevant cost center.
Displaying the Cost in Controlling Report
To display the same results in Controlling reports, use t-code KSB1. Enter a relevant controlling area, cost center, and select the date range and then the execute the report.
In below screenshot results can be seen in the controlling report.
Now to allocate the above posted amount of 200,000 to COPA we need to create a COPA Assessment Cycle.
Define COPA Assessment Cycle
To create a COPA Assessment Cycle, we need to use transaction code KEU1.
Enter a cycle name and start date.
In a cycle you define the sender-receiver relationships and the corresponding distribution rules.
You can define several groups (i.e., Segments) within one cycle. A group contains related sender-receiver relationships.
In below screen you need to maintain text for the cycle and relevant controlling area.
Segment Header:
Within the allocation cycle we need to attach a segment consisting of the details of sender and receiver cost centers and cost allocation basis.
As this has been mentioned earlier that we can define several groups (segments) within one cycle that’s why we need to maintain segment name and description.
Then we maintain the following under Segment Header:
- Assessment Cost Element: This is the secondary cost element, and the amount will be posted to this element. This cost element must be mapped to COPA report as an admin expense.
- Sender Values:
Rule: This field controls how the sender values are calculated and here we maintain (Posted Amounts). This states that whatever the amount posted in sender cost center will be allocate to COPA.
Share in %: Percentage of the sender value credited to the sender and here we maintain 100%.
Remember by entering a percentage less than 100%, you can stipulate that only a portion of the sender value is distributed/assessed. The remaining amount is left on the sender.
- Receiver Tracing Factor:
Rule: This field controls how receiver tracing factors are determined. Like what will be basis of allocation of sender amount to the receiver.
We have the following option:
- Variable portions (The tracing factors are determined automatically from the totals record file. You can define the criteria for this database access in the Tracing Factor tab).
- Fixed Amounts (You can define fixed amounts in the Receiver Tracing Factor tab).
- Fixed Percentages (You can define fixed percentages for the receivers in the Receiver Tracing Factor tab).
- Fixed Portions (You can define fixed portions for the receivers in the Receiver Tracing Factor tab).
Relevant to us is the option no. 1 variable portion as we need to allocate the cost based on product wise revenue. This point will be clear further while moving towards receiver tracing factor tab.
- Amount/Qty Field: Maintain this field if you work with a variable receiver tracing factor for allocations. The system uses the entry in this field to determine the receiver tracing factor of each allocation. And here we can select the quantity and the amount. As discussed earlier that we are allocating the cost based on product wise revenue therefore we maintain the Total Costs in this field.
Senders/Receivers:
In the below snapshot, under the sender/receiver tab we specify Cost element 65100000 and Cost Center ADMIN_CCTR which needs to be allocated to the receiving products. Parallelly under receiver side we maintain the product range as we need to allocate the cost to product.
Receiver Tracing Factor:
In the below screen, under the receiver tracing factor we maintain the Cost Element 41000000. This is the cost element where the product revenue has been recorded and the system uses this cost element as the tracing factor basis.
Mentioned below is the working for reference.
Sender Cost Center distributes 200,000 to three receivers.
| Receiver S. No | Receiver Product | Cost Element | Amount | |
| 1 | 1100 KG | 41000000 | 110,000.00 | |
| 2 | NEW BAG | 41000000 | 10.00 | |
| 3 | CONTROL-MT | 41000000 | 22,000.00 | |
| Total | 132,010.00 | |||
The SAP system calculates the following values:
Receiver 1: 110,000/132,010 X 200,000 = 166,654.04
Receiver 2: 10/132,010 X 200,000 = 15.15
Receiver 3: 22,000/132,010 X 200,000 = 33,330.81
After saving the segment, we can save the allocation cycle.
COPA Reports Before Executing Assessment Cycle:
Before executing the allocation cycle, to verify the posted amount on Cost Element 41000000 use t-code KE30 (COPA Report). In below screenshot we can check the figures with reference to Product and Cost Element.
Here it can be seen that we can’t have Product Wise Admin Expenses breakup before executing assessment cycle we have defined in earlier steps.
KE24 COPA Line-Item Screenshot can be referred to confirm the actual revenue generated on sample products.
Execute COPA Assessment Cycle:
Now we can execute the COPA Assessment Cycle using t-code KEU5.
Enter period, fiscal year and cycle name and then the execute the cycle.
COPA Reports After Executing Assessment Cycle:
Once cycle has been executed, verify the results by using the same KE30 COPA Report and KE24 COPA Line-Item Report. Below are the screenshots for reference. Admin Expenses are now broken down to product level with the help of COPA Assessment Cycles. Additionally, the same has been done based on revenue generated from each product.
Conclusion:
Thanks for reading whole document. This document describes how to break the operating expenses charged to cost center product wise using COPA Assessment in S/4 HANA. For any query, please mention in the comments section.
- SAP Managed Tags:
3 Comments
