Hi experts,
I have a question regarding milestone operation confirmation.
I have 2 operations in routing:
0010 Normal operation with one activity (base qty = 1PC and activity = 10 min)
0020 Milestone operation with one activity (base qty = 1PC and activity = 10 min)
Our controlling would like to have built in impact of scrap (for costing purposes) in routing activities. Because normally we need 10min per PC, but if scrap happens we need more time. First idea was to increase activity values for let’s say 10% for scrap:
New setup:
0010 Normal operation (base qty = 1PC and activity = 11 min)
0020 Milestone operation (base qty = 1PC and activity = 11 min)
For example in actual production run we had a bad day and for 5PC of yield we had recorded 2PC of scrap (40% of scrap) and actual time of 70min (totally 7PC x 10min)
However system will now propose 77 minutes for each operation based on estimated scrap in activity (5PC + 2PC) x 11 min.
In CO11N we have opportunity to overwrite this estimated activity figure when confirming milestone operation with actual figure (70min) but when milestone confirmation will be triggered on operation 10 (based on 7PC confirmed in operaton 20) we will have actual quantity wrong (77min) because system is double posting the scrap in activity now.
I assume we have a wrong approach here … any suggestions?