on 05-28-2008 7:28 AM
why is it in capacity levelling (tcode cm25) all released or confirmed production orders can still be moved to different dates? is this standard? how can i restrict this?
help!
Hi Rafi
It is required in case u are doing capacity planning. Lets say you want to firm your planning. So when u dispatach to a different date then in CO02 no one can change the dates. In case reschduling is reqd, deallocate, change the date & again dispatch. So in this way even if some one authorised to change the date manually through CO02, he cannot unless an authorized person deallocate the dates.
But in typical scenario people does not use that, because in no production process. the planning & execution run in sync
Hope u got the answer
Thanks & regds
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
so do you mean to say that all released or confirmed orders can still be moved or rescheduled, once they've been dispatched? what is the logic in this? to my understanding, once released or confirmed, it is already in the production floor, actual production has ensued.
Edited by: raf timan on Jun 10, 2008 7:30 AM
hi raf,
Since you are performing finite schedulling you are optimising the time period of a production order.
In real time if u deal with for discreate scenario some orders get completed before the actual planned time and some get delayed due to breakdown,in order to offset the minor differences you can adjust accordingly.
regards
ramesh
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.