Within this example the “recommended” settings for a contract based service scenario are used:
SAP Scheduling parameters for order-type/plant:
Service call type definition (/PACG/ECM_SCTD) for company / order type
The following work center capacities are used:
· Start 07:00:00
· Finish 16:30:00
· Length of breaks 00:30:00
· Operating time 9,00
1.1 Order Creation (SAP Backend-Scheduling)
The creation date is the 09.02.2021 and the duration is two hours. Basic start and end date of the order will be set manually to the end of the month:
The scheduling type “forward in time” is used. Based on that, the current date and time is used for scheduling (instead of the starting time of the shift).
Due to that, the duration of the work (duration plus break) can not be made within the operating time of the work center. Therefore the earliest finish will be the next day:
14:45:05 + 2 Hours + 6 Minutes + 40 Seconds =16:51:45
Shift ends at 16:30:00 00:21:45 will be transferred to the next shift
Next shift starts at 07:00:00
14:45:05 + 2 Hours + 2/9 x 0,5 Hours = 07:21:45
Because the basic dates of the order header are decoupled from the operation, the end date can be different on header level:
1.2 Planning and Dispatching
When having a look on the service call, it is reflecting pretty much the scheduling of the service order:
But with the recommended settings, the activity contains both, the scheduled dates AND the lates possible due date for execution, coming from the order header:
