Getting Started Store

Community WIKI SAP Community Welcome, Guest Login Register Search the Community

ERP Financials / … / Profitability Analysis Common Issues

COGS not posted to costing based CO-PA during Goods Issue

Created by Waman Shirwaicar, last modified by Vivienne Smith on Mar 01, 2016

Purpose
Customers often expect that the COGS (cost of goods sold) will be posted to costing based CO-PA during the goods issue and feel that the system behavior is wrong when this does not happen. This WIKI
has been created to explain the system behavior in this regard.

Overview
 The picture below shows how customers typically check that the CO-PA document is missing.

Basically in costing based COPA the system does not post the cost of goods sold to COPA during goods issue but it is done at the time of posting the invoice since the system design is to see the
revenues and the COGS values together. The reason for the system design is to make reporting easier i.e. if the revenues and the costs are posted together then profitability analysis will be accurate at any
point in time.

Since the system posts the COGS into CO-PA at the time of invoice posting (VPRS condition posts to CO-PA), if this is also done during goods issue then you will have duplicate entries in CO-PA (i.e. the
COGS will be doubled). For this reason, no costing based line items will be created in the standard R/3 system for transaction VL01N/VL02N.

Modifications available
If for some reason you still wish to post the COGS to COPA during goods issue you have to do the same through a modification of the system. From EHP4 onwards SAP note 1167439 is available. Please
read this note.

As per SAP note 1167439 you can control the activation of additional business transactions depending on the following characteristics:

Business transaction (GLVOR)

Reference business transaction (AWTYP)
Transaction key (KTOSL)
Transaction type (BWART)

You can check these Characteristics in the table ACCTIT from SE16 for a given material document.

Then choose the required fields to display as below:

Please note that the Transaction key is relevant for the entries with a PA segment number (PAOBJNR).

Then compare this to the control table in transaction SM30 using the view V_TKE_BUS_TRANS /Transactions KEGS.

Please note that the first line shown above for “RMWL” is the system default setting.

In the example above the customer has specified the transaction key “PRD” and “UMB” to update COPA but we know from the above table ACCTIT that the transaction key (KTOSL) for the material
document 4911322846 is “AUM”.

If you would like to transfer transaction key “AUM” then you will need to update the above settings.

To post goods issue (business transaction RMWL) to CO-PA prior to EHP4 you need to either implement note SAP 324688 or 214381. If you have implemented SAP note 214381 for a certain movement
type (for example movement type 122), the corresponding document posted with that movement type is transferred to CO-PA. Basically, SAP note 214381 can be tailored for certain movement types but in
case of SAP note 324688 it will post price differences in case of business transaction RMWL (GI for delivery) or RMRU irrespective of movement type.

So it basically depends on your requirements; if you only want to post to CO-PA for some certain movement types then you need to use note 214381 for those movement types. But if you always want to
post price differences for goods issue (RMWL) irrespective of the movement type, then SAP note 324688 would be better.

Conclusion
SAP does not recommend posting the COGS to CO-PA during the goods issue since in standard it is posted to CO-PA via the VPRS condition in the billing document.

If it is a business requirement then one of the modifications explained above could be implemented. However in this case the customer should think of switching off the VPRS posting to CO-PA during
billing to avoid double posting of COGS.

Related Content
Related Documents

Related SAP Notes/ KBA

SAP Note 1167439: Activating additional business transactions

SAP Note 324688: Posting price differences

SAP Note 214381: No CO-PA document for stock transfers in two steps
cogs rmwl goods issue movement types co-pa kegs

4 Comments
Guest
Hello,

I've activated the 1167439 note so I could transfer the goods issue documents into COPA, but the system does not fill in the Sales Order number characteristic in the resulting document. I
need the Sales Order number for some additional characteristic derivations but you cant use user exit derivations to get the sales order number from the goods issue number. Is  the same
case on your system, and would you think of this as a bug?
 Arturo Senosain
Hi Waman. Thanks for share.

I have a question:  If I work with ML and copa revaluations KE27, the system work OK? I want to test the modification if the revaluation work.

thanks

Arturo.

Former Member
As per my requirement there is a customized sales order which is used for dumps wherein no billing document is created. Client needs a COPA document to be posted when no Billing
document is created. The Document flow being Sales Order -> Delivery -> Picking request -> Goods Issue. As per your suggestion, i tried with sap note 214381 but the release mentioned in teh
note is an old version, doesn't fit in my landscape.

Please suggest. Is there any other way?

Thanks,

AK

Former Member
Very good information Waman.

Regards

Madhu

Contact Us SAP Help Portal

Privacy Terms of Use Legal Disclosure Copyright Cookie Preferences Follow SCN