Rescheduling of production orders in APO after (partial) confirmation in R3

[Former Member]

Hi all,

I'm scheduling a production order in APO. Later I release it in R3 and (partially) confirm it. Now the production order is rescheduled based on the time and quantity of the confirmation.

I don't want to have the order rescheduled - and would like to see it after the confirmation on the same dates where the order was before the confirmation.

Any hints??

Thanks,

Michael

[somnath_manna · Accepted solution]

Hi Michael,

This is standard APO feature you are observing. The changes in the order (partial confirmation) in R/3 are sent to APO where it reschedules automatically subsequent activities in liveCache. The same changes are then sent to R/3 in a key completion queue.

Using an user exit solution you can change the standard behavior. Please check Note 586685 which provide details of the user exit /SAPAPO/CL_EX_CIF_IP to be used. Also check notes 572644 and 579758.

Hope this helps.

Thanks,

somnath

[Former Member]

Please read note 515913 for complete description of behaviour on various types of confirmations on manufacturing orders in R/3.

If you are confirming only one operation, then only that particular partially confirmed operation would recieve the confirmation date. The rest of the operations should remain at their previous planned dates.

If you are confirming the entire order itself, then it is treated as confirmation of each and every operation and the above behaviour repeats.

Even if you try to override this behaviour in APO, it serves no purpose as further date changes to fully confirmed operations in APO will be ignored in R/3. But partially confirmed operations can be interrupted and rescheduled in APO and taken over by R/3.

Rgds

Harsha

[Former Member]

Hi Harsha

I have one additional query to it:

If I date fix the opration in APO then during the partial confirmation -It is unfixed , It seems to be a designed behavior - My query :Technically why the behavior ?If the date fix not removed will it harm?

Kind regards

sundar

[Former Member]

Guys,

we still try to fix it without implementing some OSS-notes

After some first test we found two ways:

It seems that it is enough, if the box "automatic scheduling" in the control data tab in the order is not ticked. If I remove that tick, save the order and do the PCONF the order is not automatically rescheduled in APO

Also if I change the scheduling type to "only capacity requirments", save the order and do the PCONF it looks good.

Both settings can be done also in the R3-config for the order type. So then there is no need to do that manually in every order.

Any experience with that??

Cheers,

Michael

[pp_groep]

Hello Michael,

How did you resolve this issue?

We are dealing with the same type of behaviour ...

thank you,

Philippe