on 02-07-2014 10:45 AM
Hi SDB SDB,
Were the characteristic requirements for the block basis definitions been maintained for the model-independent version in /SAPAPO/RES01?
Is block planning consideration active in the strategy profile you're using to create the orders or in the strategy settings of the heuristic?
Is the block planning class assigned to the block planned activity in the PDS?
If you display the details of the block planned activity in the order details in /SAPAPO/RRP2, are you able to see the valuation of the activity?
That's all I can think of.
Regards,
Tiago
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi SDB SDB.
A Planned Order is not assigned to a block. Rather, activities of a planned order can be planned in a block planning scenario.
In general, if the block planning class is assigned to the activity in the PDS (as shown in the third screenshot from my previous reply), the classification of the planned orders you create will be propagated to the block planned activities (so the block planned activities themselves will be classified, not just the planned order).
Once the activity in a planned order is classified and that block planning is considered in the strategy used for scheduling (second screenshot from my previous reply), that activity will only be scheduled in a given block if this block is suitable.
In this case, during scheduling, liveCache will compare the classification of the activity with the characteristic requirements maintained for the block basis definition (first screenshot from my previous reply) of the block. If the classification of the activity matches the characteristic requirements of the block, the activity can be scheduled in that block (given enough capacity).
So, all of these settings need to be in place to work with block planning. Please, let me know if this helps.
Regards,
Tiago
Thanks Tiago Furlanetto
User | Count |
---|---|
7 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.