on 06-10-2016 3:32 PM
Hi All
I want to Dispatch PP, PM orders for one Work center.
I use CM40 transcation to perform this action.
Here is a list of orders we can see in CM21 transaction.
Here is selection screen and result of CM40
Lets see result in CM21
As you can see CM40 Dispatch three orders - 4000404, 4000405, 1000104
but didn't touch 1000120 1000140 and 1000141 orders
I can't understand why?
If I select 1000120 1000140 and 1000141 in CM21 and press Dispatch
it Dispatches them with not problem
They are not blocked, no other problem with them.
But CM40 don't want to Dispatch them.
Can anyone explay why?
I found that a planned order 5333 a strange effect on the result.
In the previous example, the date of the planned order is between orders 4000404, 4000405, 1000104 and orders 1000120 1000140 and 1000141.
It looks as if the process stops on the planned order and no further proceeds.
If I move planned order 5333 before all the orders then CM40 doesn't take in account any orders
If I move date of the planned order 5333 after all the orders then CM40 takes in account all the orders and Dispatches them.
How can be explained such a behavior of CM40?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Please check the planned order dates. Does it come under selection condition.
Also note if the objects affected can be blocked by another transaction could not dispatch.
Check s the capacities of the selected order operations for the 'Relevant for finite scheduling' indicator if you use a scheduling type that only calculates capacity requirements. If this indicator is not set, the system prevents a dispatching without a capacity scheduling.
Refer consulting note 545930 - Selection / filter with mass planning CM40
Best Regards,
R.Brahmankar
Hello R.Brahmankar
Please check the planned order dates. Does it come under selection condition.
I am shure that planned order dates do come under selection condition becuse I can see this order in CM21.
But how this or other planned order dates can can cause a similar problem.
Dates in planned order should only affect hits or misses the planned order of processing. But I have a completely different problem.
Also note if the objects affected can be blocked by another transaction could not dispatch.
It is not possible. I'm the only user in the system. And I always close the transaction of editing before starting Dispatches.
Moreover the CM40 transaction writes a log when some order is blocked.
Check s the capacities of the selected order operations for the 'Relevant for finite scheduling' indicator if you use a scheduling type that only calculates capacity requirements. If this indicator is not set, the system prevents a dispatching without a capacity scheduling.
'Relevant for finite scheduling' is set for my Work Center.
I didn't find similar inidcator in the order postion.
If 'Relevant for finite scheduling' was not set then CM40 then, the transaction would not ever worked for this Work Center.
But it does not work only depending on the date of the planned order.
Hello R.Brahmankar
I don't use CM25.
I used CM40 with overall profile SAPCRPG001.
And also I used CM21 and CM22 (It asks no profile).
I tested CM40 with overall profile SAPPM_G001 but it writes - No capacity requirements were found in the evaluation period
and do nothing at all with PM, PP and Planned Orders.
I could understand if certain type of profiles just ignore or take in account certain types of order.
But when it interrupt the process and ignore all the rest of orders after it stumbles upon a Planned Order it looks like a bug.
Could you please try the same using CM25 with overall profile SAPCRPG001?
Here is the result
CM25
overall profile SAPCRPG001
Work Center 10000005
See Planned Order is 5333
Lets select All the orders and Dispatch them.
Dispatch
Log
Lets restart CM25
Only first three orders dispatched
Now lets repeat Dispatch All
See no result. Result Log is Empty.
Ne lets select only last three Production Orders and Dispatch them.
See, they are dispatched. It dispatches them if no planned order in the selected list.
Hello,
What is difference in Planned Order is 5333 with other planned orders?
Or you are not able to dispatch any planned orders?
Did you get an any error when you try to dispatch Planned Order 5333?
In OPPQ -Overall Plant Maintenance there is a setting for Conversions under the planned order section. Make sure that you have a default order type assigned to the Planned order --> Production order conversion.
Please refer this discussion,
Best Regards,
R.Brahmankar
Hello,
If you check the log of CM40 these orders 1000120 1000140 and 1000141 are not selected.
For PM order try the Overall profile like SAPPM_G001.
In OPD0 check the Overall profile SAPCRPG001 Selection profile have the
Object set and Filter set 5KAUFNRV used the work orders
Also check time profile transaction OPD2 such that the database read period, the planning period and the evaluation period for all these orders.
Best Regards,
R.Brahmankar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.