on 09-09-2008 11:19 PM
Hello Friends,
WE uses Stock Transport Order in two steps for transfering Stock from one plant to another. We have defined a Condition type FRB1 to capture the Freight cost involved in the stock transfer.
When the Post goods issue is done for the Stock Transport Order. following Accounting documents are generated.
Accounting
Profit Center
COPA
Spec. Purpose Ledger
Controlling Document
Material Ledger document.
But When the Post goods issue is reversed through transaction code VL09 all the above documents are generated except for COPA document. Though in controlling document it shows the object type hit is REO i.e profitability Analysis
For further information we have mapped cost element (600150) with Value field in PA transfer structure (Direct assignment from FI and MM. Movement type used for PGI are 641 & 642.
Thank you
This happens sometimes when you manually change the automatically derived assignments like cost center.
The document does not get generated even though if you put back the same derived cost center.
I had an issue like this earlier.
Hope this is the case
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Colleagues
I thank all those who put in thier time and efforts for possible solution for my problem. But I could resolve this issue with help from SAP.
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 wants to see the revenues and the COGS values together.
Since the system posts the COGS into COPA at the time of invoice posting, you will appreciate that if this is also done during goods
issue then you will have duplicate entries in your COPA (i.e. the COGS will be doubled).
If in transaction VL01N/VL02N a costing-based line item would be posted, the costs would be double in CO-PA (the billing and goods issue). For this reason, no costing based line items will be created in the standard R/3 system for transaction VL01N/VL02N.
If for some reason you still wish to post the COGS to COPA during goods issue you have to do the same thro a modification of the system.In your case you have applied note 214381 for the same. Please note here that movement type '641' is used as an example. For other movement types you will need to code accordingly.
as per note 337488 point 2. the changes of note 214381 were not required in our case. Therefore we reverted these changes in LKEIIF01 and added the relevant coding for movement type 642 in function COPA_DOCUMENT_CHECK as per note 337488 point 2.
Looking forward for your continued support
Regards
Umesh Gothankar
Hi Umesh,
Thank you very much for your valuable input.
Pl help me as in our scenario system is generating CO-PA document for mvmt 301(Plant to Plant single step) where as for STO with Mvmt 641 (without billing) it is not creating any CO-Pa document.
Since there is no billing we need CO-PA document at the time of delivery. Please help us to resolve this issue.
Thanks
Prasad
Hello Prasad,
You need to implement SAP Note 337488 - Go to correction instructions of SAP note - select the correction instructions depending on SAP version in your company. As per the correction instructions you need to delete a block and insert a new block. the movement type given there is 641, You should make the correction in block for the movement types which you require.
If you can not do this, Ask your Abaper to do it for you. Also study SAP Note 214381 before you do the changes. Hope this helps
Good Luck
Umesh
HI Umesh,
In my current company they are looking for to capture some data/want to transfer some value/data to COPA in case of Stcok Transfer order between two plant(May or may not belongs to same company code).
Any body have any document or steps to configure and things to consider to provide the solution to the business.
Regards,
Lokanath
User | Count |
---|---|
103 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.