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. 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. To post goods issue (business transaction RMWL) to CO-PA prior to EHP4 you need to either implement note SAP 324688 or 214381.
Sap movement type 453 profit center update#
If you would like to transfer transaction key “AUM” then you will need to update the above settings. 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”. Please note that the first line shown above for “RMWL” is the system default setting. Then compare this to the control table in transaction SM30 using the view V_TKE_BUS_TRANS /Transactions KEGS. Please note that the Transaction key is relevant for the entries with a PA segment number (PAOBJNR). Then choose the required fields to display as below: You can check these Characteristics in the table ACCTIT from SE16 for a given material document. Please read this note.Īs per SAP note 1167439 you can control the activation of additional business transactions depending on the following characteristics: From EHP4 onwards SAP note 1167439 is 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. For this reason, no costing based line items will be created in the standard R/3 system for transaction VL01N/VL02N. 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.
if the revenues and the costs are posted together then profitability analysis will be accurate at any point in time. The reason for the system design is to make reporting easier i.e. The picture below shows how customers typically check that the CO-PA document is missing.īasically 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. This WIKI has been created to explain the system behavior in this regard. 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.
0 kommentar(er)
