Dispatch an operation of a PM order

Question

Hi Experts,
Could you tell me if a BAPI, FM, Method or anything else can be used to dispatch an operation of a PM order?
Here is the need:
Our customer uses the Planing Board (CM25) to dispatch operations of PM orders.
When the related work can't be executed on field, corresponding operations need to be dispatched a second time (at another time and day).
Currently we simply add a constraint on the StartPoint date/time and change the status of the operation to DSPT. But this doesn't take into account the workcenter capacity. So it can result to workcenter capacity overload.
For that pupose I'm looking for a standard FM or BAPI or ... that can do the job.
I think the following information should be sufficient to make the dispatching: Order nr, Workcenter, operation, day, time.
I found some threads about his on SDN forums but none answer my question.
Thanks a lot.
Regards,
Philippe
Edited by: Philippe Tsalos on Jan 18, 2010 9:33 AM

Answer 1

Hi Philippe,
So you want to reschedule considering available capacity. That is exactly what dispatching in the planning table does.
If you were to re-dispatch the operation dependent upon the availability of capacity, it may not end up at day + 2. It may be shifted to some other time in the future, assuming you have search in the forward direction as your strategy. So is your intent simply to "throw" it forward somewhere or is it a hard requirement that it is re-scheduled for today + 2? I presume you know how to change the operation details programatically.
For the sake of the following, I presume that the order operations to be re-scheduled were once dispatched in the planning table.
So why don't you explore the following:
Why don't you collect all the order operations together and undispatch (deallocate) them with Transaction CM40 in background? and then after you have changed their dates to day + 2, reschedule them, then dispatch them with CM40 again in background?
By using an appropriate profile, you can specify the appropriate work centres and the order operations belonging to them that need dispatching. say profile SAPPM_G006 - define the plant and workcentre on the first screen, then the orders on the filter screen.
If you feel like a little more of a challenge, you can review the coding of RCCYMAB2, particularly the subroutine EXECUTE_MASS_DISPATCHING, which shows all the details. Unless you are really confident, I'd stick with the transaction CM40 if I were you and set the objects and filter according the definition of your overall profile to define the order operations you wish to dispatch / undispatch.
I should point out that CM40 is designed to let the system do a first cut dispatch for all the requirements on a workcentre prioritised according to the strategy sort key. In your case you don't want (I don't think you want) to deallocate and then dispatch all non-dispatched requirements - just those of the particularl order operations. That is why the filter is necessary to further restrict which order operations are to be processed. You could also use the selection schema as well, selecting those with user status NOEX.
Is that helpful?
Edited by: Andrew Barnard on Jan 26, 2010 11:05 PM