Dear All PP Gurus ,
I would like to publish this document related to Activities Recalculation issue which we faced in Standard Program for CO11N . We solved this very serious issue with the help of SAP Labs support team. And I would like to highlight this thing to every PP Process Consultants here , so that they are aware of this issue and get it rectified.
Description : When we make Confirmations for Production Orders using CO11N Tcode , we provide Yield Quantity ( i.e the quantity to be Yielded with the corresponding Confirmation made ) . Usually it is picked from the Production Order ( CO01 ) but while making confirmations we can also change it. And we know that each Production Order involves the BOM Components ( materials involved for Producing a GOOD ) and Activities ( Activities ( Non Material Component ) involved in Production like Human Resource , Machine , Power etc. which is maintained using Routing Data.
Now , while doing Confirmation whenever we change the Yield Quantity corresponding Activities are also Recalculated . But when we make a change in Shift and after that make a change in Yield Quantity then Activities were not recalcualted and this was the issue.
Consider the below Example :
Now I change the Yield Qty :
You can see that System Prompts for Activities Recalculation and it does the same.
But if you make Changes in Yield Quantity first and after that you change Shift , Activity Recalculations are not carried out and this was the Bug.
System will not prompt for Activities recalculation and the Confirmation will be saved with Old Activities Value which is wrong.
And this was the issue , due to which wrong Costing Data was posted.
And the issue was that SY-UCOMM ( technically speaking ) for Shift Change was not being capture , which I was very obvious being an ABAP Programmer but I was not able to locate the Exact point where the changes was to be made. Contacted SAP Labs and they cooperated with us to find the solution. Changed the Standard Code and tested the solution given. And got this very serious issue solved .
Solution : Note 1966340 ( Yet to be released ).
I was very astonished to find that this issue was no where discussed in this forum.
So I posted this document in order to make all aware of this and get this serious Bug eradicated.
Component version : SAP ECC 6.0
Release : 604