Skip to Content

“Shift Order” indicator in customizing tcode OPU3 controls if the actual dates of the partially confirmed operations are taken into account during a new scheduling run.

Prerequisite

  1. Create a production order in tcode CO01 and release it. Scheduling is automatically executed.
    /wp-content/uploads/2015/06/1_717497.png
    Operation 0010 starts on 2015.6.2 and ends on 2015.6.4.
    /wp-content/uploads/2015/06/2_717498.png
    Operation 0020 starts on 2015.6.4 and ends on 2015.6.6.
    /wp-content/uploads/2015/06/3_717499.png
  2. Execute partial confirmation with 5 qty for operation 0010 in tcode CO11N on 2015.05.28.
    6-4-2015 9-04-22 AM.png

When “Shift Order” is ON


System ignores the existing actual dates as if no confirmation happeded, and shift the order to the dates when re-scheduling is executed.

6-4-2015 9-05-59 AM.png

Execute scheduling by clicking the scheduling icon in tcode CO02.Today is 2015.6.4.
Check the rescheduling result. The planned start date was on 2015.6.2, now it starts on 2015.6.4, the date when re-scheduling is executed.
6-4-2015 9-22-25 AM.png
You can also check the “Confirmed dates” view. The order qty is 10, 5 of them has been confirmed on 2015.5.28, the other 5 starts from current date 2015.6.4.
6-4-2015 9-23-12 AM.png

When “Shift Order” is OFF


System takes actual confirmed dates 2015.5.28 in to consideration during re-scheduling.
6-4-2015 9-15-01 AM.png

Execute scheduling by clicking the scheduling icon in tcode CO02. Check the rescheduling result. The planned start date was on 2015.6.2, now it starts on 2015.5.28, the actual dates when the partial confimation was executed.
6-4-2015 9-12-53 AM.png

You can also check the dates in “Confirmed Dates” view. Start time is same as the actual confirmed dates.
6-4-2015 9-12-01 AM.png

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply