PP-CRP: Scheduling and order dates calculation

126

Scheduling and order dates calculation

The planned and production order dates calculation is a complex topic and the results can be influenced by several different customizing and master data settings. Scheduling and order dates calculation !! how to ?

The documentation of this topic, however, is extense and very detailed.

If the results of the scheduling of an order is unclead or if you would like to have a better understanding about this topic, you will find below a collection of the most useful notes about this topic:

1913017 MRP: Forward scheduling and adjust basic dates
499604 Incorrect scheduling result
156933 Consulting: Scheduling routing
156115 Consulting: Scheduling of planned order for recipe
152319 Consulting: Scheduling of planned order for routing
151551 Consulting: Scheduling of network
151503 Consulting: Scheduling of process order
150007 Consulting: Scheduling of production orders
46237 Consulting: determination of the order dates
1857912 PP-SFC: Order is rescheduled after confirmation
680454 Order dates after confirmation

Click to show SAP Notes.

[toggle title=”SAP NOTE: 1913017 – MRP: Forward scheduling and adjust basic dates” state=”close”]

1.MRP: Forward scheduling and Adjust Basic Dates

Symptom

On the customizing scheduling parameters for planned orders you have chosen “forward scheduling” and also the option “adjust basic dates”.

For a planned order created by MRP, you observe the following symptoms:

MRP considers the requirement date as basic finish date and calculates the basis start date using backward scheduling
The planned order basic finish date is equal to the requirement date and it is not adjusted according to the production finish date.

Environment

SAP ERP Release Independent
Material Requirements Planning – PP-MRP

Reproducing the Issue

On the customizing transaction OPU5 (scheduling parameters for planned orders) you have set the option adjust basic dates and forward scheduling
The planned order basic date was not adjusted or not calculated by forward scheduling.

Scheduling and order dates calculation
Scheduling and order dates calculation

Cause

During the MRP run, a planned order will be always firstly scheduled backwards according to the in-house production time defined on the material master. In this process, system considers the requirement date and schedules the planned order backwards to calculate the basic start date.

The order finish date of the planned order is generally not adjusted by scheduling since it identifies the requirements date of the material.

If you have defined the forward scheduling for planned order on the scheduling customizing (OPU5), when the lead-time scheduling for the planned order is executed, the planned order will be scheduled forwards, considering the basic start date as the starting point of the forward scheduling.

The basic finish date will be only adjusted if the basic finish date initially calculated is after the requirement date. That generally occurs when basic start date is calculated in the past and system automatically switches to forward scheduling and if the production finish date is less or equal the requirement date. Also, the basic finish date will be adjusted to match the requirement date.

When you are creating a planned order manually, however, the basic finish date is adjusted, since there is no restriction regarding the requirement date.

Resolution

System is working as designed and it cannot be changed.

You should make sure that the in-house production time defined on the material master is as close as possible to the times defined on the routing, so that the basic finish date matches the production finish date. Transactions CA97 or CA97N can be used to update the in-house production time with the information from the routing.

[/toggle]

[toggle title=”SAP NOTE: 499604 – Incorrect scheduling result” state=”close”]

Symptom

A scheduling result is incorrect. You use a shift sequence with defined breaks.

Other Terms

Work break schedule, shift definition, shift sequence

Reason and Prerequisites

The incorrect scheduling result can be caused by an invalid work break schedule. The following constellations are not allowed in the work break schedules:

  • Breaks must not start at the shift start.
  • Breaks must not end at the shift finish.
  • Breaks must not start before the shift start.
  • Breaks must not end after the shift finish.
  • Breaks must not overlap or must not be joined.

Solution

Maintain the breaks so that they meet the above requirements.

[/toggle]

[toggle title=”SAP NOTE: 156933 – Consulting: Scheduling routing” state=”close”]

Symptom

The result of scheduling a routing is unclear.

Other Terms

CA01, CA02, scheduling, routing, check list, basic dates, in-house production time, scheduling result, overlapping, splitting

Reason and Prerequisites

Solution

Check your settings according to the questions listed below:

Check list

* Which dates cannot be explained?
1. Scheduling result: Refer to point 1.
2. Operation dates: Refer to point 2.

1. Scheduling result

* Do the basic dates change?
Depending on scheduling type, it is scheduled starting with the entered basic date where the other basic date is always redefined.

* Is it possible to explain the basic dates on the basis of the operation dates?
1. Yes: The problem is caused by the operation dates. Refer to point 2. “Operation dates”.
2. No: Continue.

* Check float before/after production in scheduling result of the routing
Float before/after production are transferred from the material master and are included in the calculation of interoperation time.

* Have night shifts been assigned to the last operation relevant to scheduling?
Yes: Note that for a backward scheduling the finish date is the end of the night shift of the previous day so that the order finish date can be moved by one day. As a result, the production dates can fall on a day off, according to factory calendar.

* Is it possible to explain the durations of the time segments in scheduling result?
Note that the durations of the time segments are compressed and rounded from the durations of the individual operation segments and, therefore, these are approximate values.
Operation segments that are lying in parallel are only considered once.
All durations are calculated considering the shifts stored at the work center and displayed in unit DAY. For this, the duration of the operation segment is set in relation to the duration of the shift at the work center.
Example: Processing time is 8 hrs. At the work center used, a shift exists with an operating time of 8 hrs for each workday. Then for this processing time a duration of 1 day results in scheduling result.

* Check the assembly scrap

2. Operation dates

* Are the durations of the operation segment correct?
1. No: Refer to point 2.1. “The durations of the operation segments are not correct”.
2. Yes: Refer to point 2.2. “The durations of the operation segments are correct yet the individual dates cannot be explained”.


2.1 The durations of the operation segments are not correct

* Are the operations relevant to scheduling?
Check the operation control keys for this.
Note that for operations which are not relevant to scheduling it is not checked whether the operation is on a day off since it can always be executed directly before or after another operation.

* Have you not only defined units of measurement shorter than a “day” for the default values?
The unit of measurement for the time segments setup, processing, and teardown is the same for all three time segments. It is determined as the largest of all the units of measure for the default values.
The durations calculated by means of the formulas are converted in accordance with the global units of measure from Customizing. A day has 24 hours, for example. This is because when the durations are determined, different available capacities could be taken into account, ones based on different operating times. That is why generally no decision can be taken on how long a day at a work center lasts since the work center available capacity can be a different one every day.
As a result, the dates and the in-house production time might not be determined as you would expect (see also sections 2.2.1 and 2.2.2).
Should you encounter problems of this kind, check whether the introduction of a new time unit, such as 1 workday = 8 hours, for example, can solve the problem.

* Has a splitting been executed?
Yes:

  • If the number of splittings entered does not match the number of the individual capacities which is stored in the work center of the operation for the capacity relevant to scheduling, the system uses the smaller value of the two values for calculation (Note 101308).
  • Note the minimum processing time.

* Is it an external processing operation?
Check the operation control keys for this. Note that operations with characteristic attribute “Internally processed operation/external processing possible” are not interpreted as externally processed operations when you schedule.
If the operation is defined as an external processing operation, the planned delivery time is displayed and used as processing time. The operation is scheduled with planned delivery time according to the Gregorian calendar.
Since Release 4.0, you can also schedule externally processing operations via formulas at the work center. For this, indicator “Scheduling external operation with standard values” must be activated in the respective control key. In this case, the planned delivery time is not taken into account.

* Has flow manufacturing been set?
Yes: Then the durations of the operations are extended according to the operation with the longest duration.

* Have you set a reduction at the start of scheduling?
1. No: Refer to point 2.1.1.
2. Yes: Refer to point 2.1.2.

2.1.1 No reduction was executed

  • Queue time

Has the queue time been entered manually in the operation?
No: Check whether the queue time was transferred correctly from the work center of the operation.
If the operation overlaps with a previous operation, the system transfers the queue time of the first overlapped operation.

  • Setup, processing, tear down

Check the formulas for calculating the execution time in the work center as well as the standard values used in the routing.

    • Which variables are used in the formulas?

For example, if a split was executed for the operation without having an effect on the calculated duration, check whether the number of splits is considered in the formulas of scheduling.

    • How is the result calculated?
    • Try to reproduce the problem for the work center stored in the operation using Transaction CR04. With this transaction, you can test scheduling formulas of the work center. For this, enter both the general operation values and the standard values and execute scheduling (F5).
  • Wait time

Check whether a minimum wait time has been entered in the operation.

  • Move

Has the move time been entered manually in the operation?

    • Yes: Check that transfer has been executed correctly.
    • No: Check whether the move time has been calculated correctly from the move time matrix.


2.1.2 A reduction has been executed
Check whether the durations of the operation segments have been calculated correctly according to reduction. For this, refer to 2.1.1, if necessary.
If an overlapping occurred, refer to point 2.3, if necessary.


2.2 The durations of the operation segments are correct yet it is not possible to explain the individual dates.
* Do parallel sequences exist?
The dates of the operations of a parallel sequence result from the alignment. For the alignment with latest dates, the operations of the parallel sequence have the latest possible dates. For the alignment with earliest date, the operations of the parallel sequence have the earliest possible dates. Here, the alignment refers to the branch or return operation.
Note that the standard sequence has also an alignment.

* Are the operations overlapped?
1. Yes: Refer to point 2.3.
2. No: Continue.

* Does the unit of the operation segments correspond to unit day or is it even larger?
1. Yes: Refer to point 2.2.1.
2. No: Refer to point 2.2.2.

2.2.1 The unit of the operation segment is larger than or equal to day.
Note that the dates determined are shifted to the next relevant productive date under consideration of the available capacity in the work center, provided a work center is stored for the operation.

* Does an active version of the available capacity exist?
1. Yes: Scheduling is executed to the day using the days on which shifts are defined. If no operating time is maintained for the specified period, the system schedules according to the Gregorian calendar.
2. No: Continue.

* Has a factory calendar been stored in the work center?
1. Yes: Scheduling is executed to the day using the workdays of the factory calendar.
2. No: Scheduling is executed to the day using the plant calendar

2.2.2 The unit of the operation segment is smaller than day.
* Does an active version of the available capacity exist?
1. Yes: Refer to point 2.2.2.1.
2. No: Refer to point 2.2.2.2.

2.2.2.1 An active version of the available capacity exists.
* Has a shift sequence been stored?

  • No: It is scheduled using the shifts stored in the interval of available capacity, where the planned breaks are distributed equally over the entire shift duration.
  • Yes: If work break schedules are stored in the shift definitions of the shift sequence, the system schedules using the shifts stored in the interval of available capacity, while in doing so the planned breaks are distributed equally over the entire shift duration.

Scheduling customizing option “Scheduling with breaks” indicator will not be considered in case of scheduling in routing.

2.2.2.2 An active version of the available capacity does not exist.
* Has a standard available capacity been stored?

  • No: It is scheduled according to the Gregorian calendar.
  • Yes: If a factory calendar is stored, scheduling is executed using the standard available capacity and the workdays of the factory calendar, while in doing so the breaks are distributed equally over the entire shift duration.

If no factory calendar is stored, scheduling is executed using the standard available capacity and the workdays of the plant calendar, while in doing so the breaks are distributed equally over the entire shift duration.

2.2.2.3 The problem also exists when these rules are considered.
Before entering a customer message, try to reproduce the problem for the work center stored in the operation by using Transaction CR04. With this transaction, you can simulate scheduling using a work center. For this purpose, you can on the one hand specify the start or end of the productive time as well as a duration so that the missing date is determined with regard to the shifts of the work center. On the other hand, with regard to the shifts, the productive time between the dates can be calculated by specifying the two dates and an initial duration. Start the determination of productive time (F8) for the two simulation types and take the “Breaks” indicator into account for scheduling allowing for breaks.


2.3 The operations are overlapped.

  • Consider the minimum send-ahead quantity and the minimum processing time.
  • Processing time of the following operation starts after processing and move time required for the minimum send-ahead quantity. Note that the setup time is before this processing time and that due to this reason the following operation can start before the predecessor (to be exact if the setup duration of the successor is greater than the setup, processing and transfer duration of the predecessor).
  • Processing time of the following operation does not start immediately after processing and move time required for minimum send-ahead quantity if processing time of the successor is smaller than processing time of the predecessor. In this case, the finish time of the successor is first calculated with the send-ahead quantity from the finish date of the predecessor. The start time of the successor is calculated from this finish date through backward scheduling of the successor.
  • In flow manufacturing, the operations are overlapped and extended according to the longest operation.
  • If the last flow manufacturing operation overlaps with the next operation as usual, the last flow manufacturing operation has to be the longest operation for flow manufacturing. Similarly, the first flow manufacturing operation has to be the longest operation for flow manufacturing if the previous operation overlaps with the first flow manufacturing operation as usual.


3. You cannot explain the result, also after checking the stated points.

Before you enter a customer problem message:

  • Search for notes in the SAPNet – R/3 Frontend.

Search for notes of your release in component PP-CRP-SCH (scheduling). Do not mention keyword “scheduling” because this keyword has already been defined sufficiently by component assignment. For the search, use additional keywords that characterize your problem or the data to be scheduled in more detail, for example: Routing, in-house production time, basic dates, overlapping, splitting …

  • If you cannot find a note that solves your problem, create a customer problem message for component PP-CRP-SCH. Answer the following questions in your problem description:

1. How does your problem look like?
For this, restrict your problem as far as possible using this check list.
2. Where does your problem occur or can the problem be reproduced?

    • If possible, make example data available and describe how your problem can be reproduced.
    • If your problem can be restricted to scheduling of one operation, try to reproduce the problem for the work center stored in the operation using Transaction CR04.

With this transaction, you can simulate scheduling using a work center. For this purpose, you can on the one hand specify the start or end of the productive time as well as a duration so that the missing date is determined with regard to the shifts of the work center. On the other hand, with regard to the shifts the productive time between the dates can be calculated by specifying the two dates and an initial duration. Start the determination of productive time (F8) for the two simulation types and take the “Breaks” indicator into account for scheduling allowing for breaks.
Furthermore, you can test scheduling formulas of the work center with this transaction. For this enter the general operation values as well as the standard values and execute scheduling (F5).
In the same way as for scheduling formulas you can test the formulas which are the basis for the capacity requirement calculation (F6) and costing (F7).
3. What other determining factors do exist?
For example, parameters of Customizing, scheduling type, parallel sequences, overlapped operations…

[/toggle]

[toggle title=”SAP NOTE: 156115 – Consulting: Scheduling of planned order for recipe” state=”close”]

Symptom

The result of lead time scheduling of a planned order for a recipe is not clear.
The system does not display the material requirements dates correctly.

Other Terms

MD11, MD12, MD01, MD02, MF50, planned order, scheduling, check list
Basic date, operation date, splitting, overlapping, shift, night shift

Reason and Prerequisites

Solution

Check your settings according to the questions listed below:

Check list

* A lead time scheduling does not occur!

    1. Check scheduling indicators in Customizing.
    2. Using the basic dates, check whether the order is outside of scheduling horizon.In this case, no lead time scheduling is executed for this scheduling level.Scheduling horizon is stored in Customizing of scheduling parameters.
    3. Check that the task list group and group counter refer to a recipe.
    4. Ensure that the recipe is active, that is, it is not marked for deletion, for example.
    5. Check whether the lot size of the planned order is valid for the recipe.
    6. Check that the recipe is valid for the expansion time.
    7. Check Customizing for the routing selection.


* Note the following general rules
Planned orders are generally scheduled both forward and backward for recipes.The scheduling type defines which scheduling direction is taken into account first.
The dates of the earliest dates result from forward scheduling.The dates of the latest dates result from backward scheduling.
For each scheduling level, the system displays the latest dates of the capacity requirements.


* Which results cannot be explained?

    1. Basic dates: Go to point 1.
    2. Operation dates: Go to point 2.
    3. Phase dates: Go to point 3.
    4. Capacity requirements: Go to point 4.

1. Basic dates

* The basic dates are filled incorrectly after pressing Enter!
The basic dates are always filled from the in-house production time of the material master.A lead time scheduling may only adjust the basic dates if alternative ‘Adjust basic dates’ is selected.
The order finish date of the planned order is not adjusted by scheduling since it identifies the requirements date of the material.As of Release 4.6, the order finish date can also be adjusted for scheduling type ‘Forward’ and alternative ‘Adjust basic dates’.

* Do the basic dates change?
Check whether the alternative ‘Adjust basic dates’ is selected for scheduling parameters.
Check whether the basic dates are set correctly on the basis of the phase dates.For this, check in Customizing with which scheduling level the dates should be adjusted.

* Is it possible to explain the basic dates on the basis of the phase dates?

    1. Yes: The problem is caused by the operation or phase dates.Proceed with the questions stored under “2. Operation dates”.
    2. No: Continue.Check the recipe which is used as a basis and the standard values.

* Check float before/after production of the order or scheduling margin key
* Have night shifts been assigned to the last phase relevant to scheduling?
Yes:Note that for a backward scheduling the finish date is the end of the night shift of the previous day so that the order finish date concerning this can be moved by one day into the past.As a result, the production dates can fall on a day off according to factory calendar.

2. Operation dates

The operation dates are determined from the dates of the respective phases.Here, the min max rule applies, that is, the earliest start and latest finish date are copied.

* I do not receive any scheduling result for a scheduling level!

    1. Check that the ‘Generate capacity requirements’ indicator is activated for scheduling level in Customizing.Note that the dates of capacity requirements are displayed.
    2. Using the basic dates, check whether the order is outside of the scheduling horizon.In this case, no lead time scheduling is executed for this scheduling level.Scheduling horizon is stored in Customizing of scheduling parameters.

* Does the system display all operations from the routing or the recipe?
No:Check whether capacity requirements should be calculated for the operations according to the control key.

* Is it possible to explain the operation dates from the dates of the respective phases according to the min max rule?
Yes: Go to point 3.

* Has the operation been dispatched?
If the operation is dispatched, the operation dates result from capacity requirements planning on the basis of the dispatching dates.

3. Phase dates

· Are the durations of the operation segments correct?

    1. No: Go to point 3.1.
    2. Yes: Go to point 3.2.

3.1. The duration of the phase is not correct

3.1.1 Check the formula in the work center
Check both the formula for calculating the execution time in the work center and the standard values used in the order.

  • Which variables are used for the formulas?
  • How is the result calculated?
  • Using Transaction CR04, try to reproduce the problem for the resource stored in the phase.With this transaction, you can test the scheduling formulas of the resource.For this enter both the general operation values and the standard values and execute scheduling (F5).

3.1.2 Check status and type of the phase
* Are the phases relevant to scheduling?
For this, check the control keys of the phases.Note that for phases not relevant to scheduling, the system does not check whether the phase is on a day off since the phase can always be executed directly before or after another phase.

· Is it an externally processed phase?
For this, check the control key.Note that operations with characteristic attribute ‘Internally processed operation/external processing possible’ are not interpreted as externally processed operations when you schedule.
If the phase is defined as an externally processed phase, the system displays and takes the planned delivery time as processing time into account.The phase is scheduled with planned delivery time according to the Gregorian calendar.
As of Release 4.0, you can schedule externally processed phases also using the formulas at the work center. For this, indicator Scheduling external operation with standard values must be activated in the respective control key.In this case, the planned delivery time is not taken into account.

* Is it a secondary resource?
Secondary resources are not scheduled by means of the standard values.The dates are calculated on the basis of their earliest/latest dates for the phase; in this case, the stored offsets are evaluated for the start and end.The system copies the duration between the dates found this way as a processing time of the secondary resource.

* Can the phase be extended?
Yes: The phase is extended according to the duration of free float.The free float corresponds to the possible delay until a successor occurs without having the dates of the successor being moved.

* Has a reduction been executed when you schedule?
For this, check scheduling log.
Yes: Check the reduction parameters of scheduling.

3.2. The duration of the phase is correct, however, the dates cannot be explained.

In general, phases and relationships are scheduled using the operating time of a stored work center.If no work center is stored but a factory calendar, it is scheduled to the day using the factory calendar.If neither work center nor factory calendar are stored, it is scheduled according to the Gregorian calendar.

* Have relationships been maintained?

  • To which category does the relationship belong?Which phase is the predecessor, which one is the successor?
  • Has a duration of the relationship been maintained?

* Has the phase been dispatched?
Check the status of the phase.If the phase is dispatched, the phase dates result from capacity requirements planning on the basis of the dispatching dates.

* Does the duration unit corresponds to the unit day or is it even larger?

    1. Yes: Go to point 3.2.1.
    2. No: Go to point 3.2.2.

3.2.1. The time unit is larger than or equal to day
Note that the calculated dates, provided that a work center is stored at the operation, are moved to the next productive date in each case considering the available capacity at the work center.

* Does an active version of the available capacity exist?

    1. Yes:Scheduling is executed to the day using the days on which shifts are defined.If no operating time is maintained for the specified period, the system schedules according to the Gregorian calendar.
    2. No: Continue.

* Has a factory calendar been stored in the work center?

    1. Yes:Scheduling is executed to the day using the workdays of the factory calendar.
    2. No: Scheduling is executed to the day using the plant calendar.

3.2.2. The time unit is smaller than day
* Does an active version of the available capacity exist?

    1. Yes: Go to point 3.2.2.1.
    2. No: Go to point 3.2.2.2.

3.2.2.1. An active version of the available capacity exists
* Has a shift sequence been stored?

  • No:It is scheduled using the shifts stored in the interval of available capacity; in this case, the planned breaks are distributed equally over the entire shift duration.
  • Yes:Check whether work break schedules are stored in the shift definitions of the shift sequence and whether the ‘Scheduling allowing for breaks’ indicator is activated in Customizing.

If work break schedules are stored in the shift definitions of the shift sequence and the ‘Scheduling allowing for breaks’ indicator is activated, the system schedules using the shifts stored in the interval of available capacity, while in doing so, the breaks are taken permanently into account.If this is not the case, the system schedules using the shifts stored in the interval of available capacity, while in doing so the planned breaks are distributed equally over the entire shift duration.
3.2.2.2. An active version of the available capacity does not exist
* Has a standard available capacity been stored?

  • No: It is scheduled according to the Gregorian calendar.
  • Yes:If a factory calendar is stored, scheduling is executed using the standard available capacity and the workdays of the factory calendar, while in doing so the breaks are distributed equally over the entire shift duration.

If no factory calendar is stored, scheduling is executed using the standard available capacity and the workdays of the plant calendar, while in doing so the breaks are distributed equally over the entire shift duration.
3.2.2.3. The problem also exists when these rules are considered
Before you enter a customer message, try to reproduce the problem for the resource stored in the phase by using Transaction CR04.With this transaction, you can simulate scheduling using a resource.For this purpose, you can on the one hand specify the start or end of the productive time as well as a duration so that the missing date is determined with regard to the shifts of the resource.On the other hand, with regard to the shifts, the productive time between the dates can be calculated by specifying the two dates and an initial duration.Start for the two simulation types the determination of productive time (F8) and take the ‘Breaks’ indicator into account for scheduling allowing for breaks.


4. Capacity requirements

In the planned order, the system displays the detail results of scheduling only if the capacity requirements of the respective operations/phases are greater than zero.If no capacities exist from recipes for operations/phases, the system does not display scheduling data of these operations/phases in the planned order.
Capacity requirements are calculated during lead time scheduling.The dates of the respective phases are copied to the dates of capacity requirements.For operations, the capacity requirements are not calculated with the standard values of the operation but the capacity requirements of an operation result from the total of the capacity requirements of the respective phases. Changes relevant to scheduling (for example, changes to the lot size) are only copied to the capacity requirements after another scheduling.
You receive a detailed display and have an option for evaluating the capacity requirements data in the capacity requirements planning.


4.1. The system displays capacity requirements for a capacity category.

* Is the amount of the capacity requirements correct?

  • Yes: The result is correct
  • No: Check the following points:
    • Check the standard values of the phase and the formula for the capacity category at the resource.
    • If necessary, test the formula in the resource with the standard values you used and with the lot size of the phase.
    • Has an optimization of setup time been executed in the capacity planning table which reduced the proportional setup capacity requirements?

· Does the system display capacity requirements for all relevant capacity categories?

  • Yes: The result is correct
  • No: Check the capacity categories existing at the resource


4.2. The system does not display any capacity requirements although capacity requirements ought to be calculated

* Have you set in Customizing of scheduling, that the capacity requirements should be calculated for planned orders?

  • No: Make this setting and execute scheduling again.If no capacity requirements exist after this, continue.
  • Yes: Check the following points:
    • Check the standard values of the phase.
    • Check the formula used for the capacity category at the resource and test the formula with the standard values at the resource, if necessary.
    • Check the control key used.If the control key of the phase does not support any capacity requirements planning, no capacity requirements are calculated.
    • Check the capacity requirements of the operations.Does the capacity requirements of the operation correspond to the total of the capacity requirements of the respective phases?


4.3. The system displays capacity requirements although no capacity requirements ought to be calculated

You can deactivate the capacity requirements planning in different ways. If you do not want the system to calculate any capacity requirements for the entire planned order, deactivate the `Capacity requirements` field in Customizing of scheduling.
If you only want the system not to calculate any capacity requirements for individual operations or phases, choose a corresponding control key for this operation or phase or use a resource without capacity categories.


5. The result can also not be explained after the stated points have been checked

Before you enter a customer problem message:

  • Search for notes in SAPnet-R/3 Frontend

Search for notes of your Release for component PP-CRP-SCH (scheduling). Do not mention key word ‘scheduling’ because the key word has already been sufficiently defined by the component assignment.For the search, use additional key words which characterize your problem or which characterize the data to be scheduled in more detail, for example: Basic dates, phase dates …

  • If you cannot find a note that solves your problem, create a customer problem message for the PP-CRP-SCH component.Answer the following questions in your problem description:

1. What does your problem look like?
For this, restrict your problem as far as possible with this check list.
2. Where and when does your problem occur or can the problem be reprocessed?

    • If possible, make example data available and describe how your problem can be reprocessed.
    • If your problem can be restricted to scheduling of one phase, try to reproduce the problem for the resource stored in the phase using Transaction CR04.

With this transaction, you can simulate scheduling using a resource.For this purpose, you can on the one hand specify the start or end of the productive time as well as a duration so that the missing date is determined with regard to the shifts of the resource.On the other hand, with regard to the shifts, the productive time between the dates can be calculated by specifying the two dates and an initial duration.Start for the two simulation types the determination of productive time (F8) and take the ‘Breaks’ indicator into account for scheduling allowing for breaks.
Furthermore, you can test scheduling formulas of the resource with this transaction.For this enter both the general operation values and the standard values and execute scheduling (F5).
In the same way as for scheduling formulas, you can test the formulas which are the basis for the capacity requirement calculation (F6) and costing (F7).
3. What other determining factors do exist?
for example, parameters of Customizing, scheduling type …

[/toggle]

[toggle title=”SAP NOTE: 152319 – Consulting: Scheduling of planned order for routing” state=”close”]

Symptom

The result of the lead time scheduling of a planned order for a routing is unclear.
The system does not correctly display the material requirements dates.

Other Terms

MD11, MD12, MD01, MD02, MF50, planned order, scheduling, check list,
basic date, operation date, splitting, overlapping, shift, night shift

Reason and Prerequisites

Solution

Check your settings according to the questions listed below:

Check list

* A lead time scheduling is not executed!

    1. Check the scheduling settings in Customizing.
    2. Using the basic date, check whether the order is outside of the scheduling horizon. In this case, no lead time scheduling is executed for this scheduling level. The scheduling horizon is stored in Customizing of the scheduling parameters.
    3. Check whether a valid routing exists for the material of the planned order.
    4. Ensure that the routing is set to active, that is, for example, the routing is not marked for deletion.
    5. Check whether the lot size of the planned order is valid for the routing.
    6. Check that the routing is valid at the expansion time.
    7. Check Customizing for the routing selection.


* Which dates cannot be explained?
1. Basic dates
2. Operation dates of the individual scheduling levels
3. Material requirements dates

1. Basic dates

* The basic dates are filled incorrectly after pressing ENTER!
The basic dates are always calculated from the in-house production time of the material master. A subsequent lead time scheduling may adjust the basic dates if you select alternative “Adjust basic dates” for which the basic dates must always lie on a workday according to the factory calendar.
The order finish date of the planned order is not adjusted by scheduling since it identifies the requirements date of the material. If the in-house production time in the material master differs greatly from the lead time of the routing, this can lead to the calculated production start date being too late. See also the release notes for Release 4.6A (PP-MRP-PP).
As of Release 4.6, the order finish date can also be adjusted for scheduling type “Forward” and for alternative “Adjust basic dates”.

* Do the basic dates change?
Check whether alternative “Adjust basic dates” has been chosen for the scheduling parameters.
Check whether the basic dates are set correctly on the basis of the operation dates. For this, check in Customizing with which scheduling level the date is to be adjusted. If necessary, create a production order for the same routing and with the same settings and compare the scheduling results.

* Is it possible to explain the basic dates on account of the operation dates?
1. Yes: The problem is caused by the operation dates. Proceed with the questions stored under “2. Operation dates”.
2. No: Continue. Check the routing which is used as a basis and check the standard values.

* Has a “today” scheduling been executed?
For this, check the scheduling log. To receive the log, you must start lead time scheduling for the planned order in the change mode.
Note that the scheduling type set is automatically overridden by a “today” scheduling as soon as the order start date is further in the past than the number of days defined in Customizing.

* Check float before/after production which are store in the material master!
* Have night shifts been assigned to the last operation relevant to scheduling?
Yes: Note that for a backward scheduling the finish date is the end of the night shift of the previous day so that the order finish date related to this can be moved by one day. As a result, the production dates can be on a non-working day according to the factory calendar.

* How is the time of the order finish date calculated?
Check the in-house production time of the header material of the order in the material master as the time of the order finish date is determined by the following logic:

  • In-house production time is greater than zero days:

The system interprets the order finish date of the planned order as a requirements date for the material. Therefore the following rule applies: If an in-house production time greater than 0 days has been defined in the material master, the requirements date is at the beginning of the day, that is, the order finish date is set to 00:00 hours. In this case, the order finish date differs by one day from the production finish date of the order because the production must have already been finished on the previous day so that the material is available at the beginning of the next day.

  • With an in-house production time equal to zero days, it is assumed that the material can be produced at any time of day. For this reason, the order finish date is set to 24:00 hours.

2. Operation dates

Note that the system displays the dates of the calculated capacity requirements. The system does not display the dates of operations which are relevant to scheduling and which have no capacity requirements.

* I do not receive any scheduling result for a scheduling level!
1. Check that the “Generate capacity requirements” indicator is activated for the scheduling level in Customizing.
2. Using the basic dates, check whether the order is outside of the scheduling horizon. In this case, no lead time scheduling is executed for this scheduling level. The scheduling horizon is stored in Customizing of the scheduling parameters.

* Does the system display all operations of the routing?
No:

  • Check whether capacity requirements are to be calculated for the operations according to the control key.
  • If alternative sequences exist in the routing and if an order type is maintained in MRP Customizing for the conversion from planned order into production order, the system evaluates the “Sequence exchange” indicator of the Customizing parameters of the order type. Check that the operations of the sequence to be selected according to this Customizing setting were scheduled. If no order type is maintained for the conversion from planned order into production order, the system schedules the standard sequence.

* No scheduling of overall networks is executed although a directly manufactured component is assigned.
Note that no scheduling of the overall network is executed for planned orders. For the components requirements dates are determined. In order to cover them, planned orders are created in the next MRP run. Since the requirements are not managed using the exact time, the results of the planned order scheduling and of a scheduling of the overall network of the converted collective order can differ.

* Are the durations of the operations or the temporal difference between start and end correct?
1. No: Go to point 2.1 “The durations of the operations are not correct”.
2. Yes: Go to point 2.2 “The durations of the operation segments are correct, however, the individual dates cannot be explained”.

2.1 The durations of the operations are not correct

* Order start and order finish dates have been copied to the operation dates
Order start date and order finish date are copied to the operation dates/dates of the capacity requirements if lead time scheduling has not been activated in Customizing.
If necessary, create a production order for the same routing and schedule this production order since the system displays all production orders for all operation data there. Compare the two results and refer to the related Consulting Note 150007 for the scheduling of production orders.

* Are the operations relevant to scheduling?
Check the operation control keys for this.
Note that for operations not relevant to scheduling, the system does not check whether the operation is on a non-working day since an operation can always be executed directly before or after another operation.

* Did you not only define units shorter than “day” for the standard values?
The unit for the time segments setup, processing, and tearing down is identical for all three time segments. It is determined as the greatest of all units of the standard values.
The durations calculated via the formulas are converted in accordance with the global units from Customizing, for example, a day has 24 hours. This can be traced back to the fact that different available capacities that are based on different operating times could be taken into account when determining the durations. It can therefore generally not be decided how long a day takes at the work center, since the available capacity of the work center can be different for every day.
As a result, the dates are not determined as you would expect, see also sections 2.2.1 and 2.2.2.
If you experience problems in this respect, check whether the implementation of a new time unit, for example, 1 workday = 8 hours could solve the problem.

* Has a splitting been executed?
Yes:

  • If the entered number of splitting does not match the number of the individual capacities which are stored in the work center of the operation for the capacity relevant to scheduling, the system uses the smaller value of the two values for calculation (Note 101308).
  • Note the minimum processing time.

* Is it an externally processed operation?
Check the operation control keys for this. Note that operations with characteristic attribute “Internally processed operation/external processing possible” are not interpreted as externally processed operations when you schedule.
If the operation is defined as an external processing operation, the system displays and takes the planned delivery time as the processing time into account. The operation is scheduled with the planned delivery time according to the Gregorian calendar.
As of Release 4.0, you can also schedule externally processed operations with formulas at the work center. For this, indicator “Scheduling external operation with standard values” must be activated in the respective control key. In this case, the planned delivery time is not taken into account.

* Has a flow manufacturing been set?
Yes: Then the duration of the operations are extended according to the operation with the longest duration.

* Has a reduction been executed when you schedule?
Check scheduling log.
1. No: Go to point 2.1.1.
2. Yes: Go to point 2.1.2.

2.1.1 No reduction is executed
Check the settings for the following time segments in the routing.

  • Queue time

Has the queue time been entered manually in the operation (box “Interoperation times”)?

    • No: Check whether the queue time has been copied from the work center of the operation correctly.
    • Yes: Check whether the queue time has been copied from interoperation times correctly.

If the operation overlaps with a previous operation, the system copies the queue time of the first overlapped operation.

  • Set up, process, tear down

Check both the formulas for calculating the execution time in the work center as well as the standard values used in the routing.

    • Which variables are used for the formulas?

For example, if a split has been executed for the operation without having an effect on the duration calculated, check whether the number of splits is taken into account in the formulas of scheduling.

    • How is the result calculated?

Using Transaction CR04, try to reproduce the problem for the work center stored in the operation. With this transaction, you can test scheduling formulas of the work center. For this, enter the general operation values as well as the standard values and execute scheduling (F5).

  • Wait time

Check whether a minimum wait time has been entered in the operation (view “Interoperation times”).

  • Transport

Check whether the move time has been entered manually in the operation (box “Interoperation times”).

    • Yes: Check that the transfer has been executed correctly.
    • No: Check whether the move time has been calculated correctly from the move time matrix.

2.1.2. A reduction has been executed
Check the reduction parameters of scheduling and scheduling log.
Check whether the dates have been calculated correctly according to the reduction. For this go to 2.1.1, if necessary.
If an overlapping occurred, you may go to point 2.3.


2.2. The durations of the operation segments are correct, however, the individual dates cannot be explained.

Note that the system always displays only the latest operation dates. This means that the dates are displayed including the queue times.

* Are the operations overlapped?
1. Yes: Go to point 2.3.
2. No: Continue.

* Does the unit of the operation segments correspond to unit day or is it even greater?
1. Yes: Go to point 2.2.1.
2. No: Go to point 2.2.2.

2.2.1 The unit of the operation segment is greater than or equal to day.
Note that the calculated dates are moved to the next productive date considering the available capacity at the work center, provided that a work center is stored in the operation.

* Does an active version of the available capacity exist?
1. Yes: Scheduling is executed to the day using the days on which shifts are defined. If no operating time is maintained for the specified period, the system schedules according to the Gregorian calendar.
2. No: Continue.

* Has a factory calendar been stored in the work center?
1. Yes: Scheduling is executed to the day using the workdays of the factory calendar.
2. No: Scheduling is executed to the day using the plant calendar

2.2.2 The unit of the operation segment is smaller than day.
* Does an active version of the available capacity exist?
1. Yes: Go to point 2.2.2.1.
2. No: Go to point 2.2.2.2.

2.2.2.1 An active version of the available capacity exists.
* Has a shift sequence been stored?
1. No: It is scheduled using the shifts stored in the interval of available capacity. Here, the planned breaks are equally distributed over the entire shift duration.
2. Yes: Check whether work breakdown schedules are stored in the shift definitions of the shift sequence and whether the “Scheduling allowing for breaks” (view “Master data”) has been set to active. If work break schedules are stored in the shift definitions of the shift sequence and the “Scheduling allowing for breaks” indicator is activated, the system schedules using the shifts stored in the interval of available capacity, whereby the breaks are taken permanently into account. If this is not the case, the system schedules using the shifts stored in the interval of available capacity, whereby the planned breaks are distributed equally over the entire shift duration.

2.2.2.2 An active version of the available capacity exists.
* Has a standard available capacity been stored?
1. No: It is scheduled according to the Gregorian calendar.
2. Yes: If a factory calendar is stored, scheduling is executed using the standard available capacity and the workdays of the factory calendar, whereby the breaks are distributed equally over the entire shift duration.
If no factory calendar is stored, scheduling is executed using the standard available capacity and the workdays of the plant calendar, whereby the breaks are distributed equally over the entire shift duration.

2.2.2.3 The problem exists also when these rules are considered.
Before you enter a customer message, try to reproduce the problem for the work center stored in the operation by using Transaction CR04. With this transaction, you can simulate scheduling using a work center. For this, you can on the one hand specify the start or end of the productive time as well as a duration so that the missing date is determined with regard to the shifts of the work center. On the other hand, with regard to the shifts, the productive time between the dates can be calculated by specifying the two dates and an initial duration. For both simulation types start the determination of productive time (F8) and take the “Breaks” indicator into account for scheduling allowing for breaks.


2.3 The operations are overlapped.

  • Note the minimum send-ahead quantity and the minimum processing time.
  • Processing time of the following operation starts after processing and move time required for the minimum send-ahead quantity. Note that the setup time is before this processing time and that due to this reason the following operation can start before the predecessor (to be more exact, if the setup duration of the successor is greater than the setup, the processing, and the move time of the predecessor).
  • Processing time of the following operation does not start directly after processing and move time required for minimum send-ahead quantity if the processing time of the successor is less than the processing time of the predecessor. In this case, the finish time of the successor is first calculated with the send-ahead quantity from the finish date of the predecessor. The start time of the successor is calculated from this finish date through backward scheduling of the successor.
  • During flow manufacturing, the operations are overlapped and extended according to the longest operation.
  • If the last flow manufacturing operation overlaps normally with the next operation, the last flow manufacturing operation must be the longest operation for the flow manufacturing. Similarly the first flow manufacturing operation must be the longest operation for the flow manufacturing if the previous operation overlaps normally with the first flow manufacturing operation.

3. Material requirements dates

* Has a lead time scheduling been executed?
1. No: The requirements date of the component results from the order start date taking the lead-time offset stored in the bill of material into account.
2. Yes: Continue with the following questions.

* Is the component assigned to an operation?

  • Yes: For the determination of the component’s requirements date, the operation date is included, if necessary.
  • No: If the component is assigned to a phantom assembly, the component is assigned to that operation which the phantom assembly has been assigned to in order to determine the component’s requirements date.

If the component is not assigned to a phantom assembly, the component is assigned to the first operation.

Using the safety time/lead-time offset from the bill of material and the operation dates, check whether the material component has a correct requirements date. Here, consider on the one hand whether the requirements dates of the dependent requirements should be adjusted to the operation or to the order start date in Customizing. If the requirements dates are adjusted by the operation dates, check also in Customizing whether the materials with the latest operation dates should be adjusted.

4. The result can also not be explained after checking the listed points.

Before you enter a customer problem message:

  • Search for notes in the SAPNet – R/3 Frontend.

Search for notes for your release for component PP-CRP-SCH (scheduling). Do not use the key word “scheduling” because this key word has already been sufficiently defined by the component assignment. For the search use additional key words which characterize your problem or which characterize the data to be scheduled in more detail, for example: basic dates, operation dates, overlapping, splitting, night shift …

  • If you cannot find a note that solves your problem, create a customer problem message for the PP-CRP-SCH component. Answer the following questions in your problem description:

1. What are the symptoms of your problem?
For this, restrict your problem as far as possible using this check list.
2. Where and when does your problem occur or can the problem be recreated?

    • If possible, make example data available and describe how your problem can be recreated.
    • If your problem can be restricted to scheduling of one operation, try to reproduce the problem for the work center stored in the operation using Transaction CR04. With this transaction, you can simulate scheduling using a work center. For this, you can on the one hand specify the start or end of the productive time as well as a duration so that the missing date is determined with regard to the shifts of the work center. On the other hand, with regard to the shifts, the productive time between the dates can be calculated by specifying the two dates and an initial duration. For both simulation types, start the determination of productive time (F8) and take the “Breaks” indicator into account for scheduling allowing for breaks.

Furthermore, this transaction can be used to test scheduling formulas of the work center. For this, enter the general operation values as well as the standard values and execute scheduling (F5).
You can test the formulas, which are the basis for the capacity requirement calculation (F6) and costing (F7), in the same way as for scheduling formulas.
3. What other determining factors exist?
For example, parameters of Customizing, scheduling type, parallel sequences, overlapped operations …

[/toggle]

[toggle title=”SAP NOTE: 151551 – Consulting: Scheduling of network” state=”close”]

Symptom

The result of the network scheduling is not clear.
The system does not display the capacity requirements calculated by scheduling correctly.

Other Terms

CN21, CN22, CN24, network, scheduling, checklist, overall network scheduling, capacity requirement, cap. reqmnt,
basic date, operation date, shift, AOB, relationship, night shift,

Solution

Check your settings according to the questions listed below:

Checklist

* Note the following general rules

Networks are generally scheduled both forwards and backwards. The scheduling type defines which scheduling direction the system takes into account first.
The dates of the earliest dates result from forward scheduling. The dates of the latest dates result from backward scheduling.

* Which set of dates is used for scheduling?

Check which set of dates is selected.

* Which results cannot be explained?

1. Basic dates/forecast dates
2. Activity dates
3. Capacity requirements

1. Basic dates/forecast dates

* Do the basic dates change?

Check whether the alternative “Adjust basic dates” has been chosen for the scheduling parameters. In this case, the subsequent backward scheduling is executed from the scheduled finish date for scheduling type forward. In the case of scheduling type backward, the system schedules from the scheduled start date, or if “today” scheduling is to be executed, it schedules from the current date onward.
If “Adjust basic dates” indicator is not set, forward and backward scheduling are executed from the basic dates entered. If no basic date is specified, the respective scheduling is executed from the scheduled date.
Check whether the basic dates are set correctly on the basis of the activity dates.

* Is it possible to explain the basic dates on the basis of the activity dates?

1. Yes: The problem is caused by the activity dates. Proceed with the questions listed under “2. Activity dates”.
2. No: Continue.

* Has “today” scheduling been carried out?

Check the scheduling log for this.
Note that the forward scheduling is automatically overridden by “today” scheduling once the order start date lies further in the past than the number of days defined in Customizing. You can also maintain the number of the days allowed in the past in the dialog box for the network.
If no order start date is defined, “today” scheduling is executed provided the scheduled start date lies sufficiently far in the past.

* Are activities already finally confirmed?

Basic dates are adjusted only under consideration of the dates for activities that have not yet been finally confirmed.
The system does not redetermine any dates for finally confirmed activities but copies the actual dates to the activity dates.

* Are night shifts assigned to the last activities relevant to scheduling?

Yes: For backward scheduling, note that the finish date is the end of the night shift of the previous day so that, in this respect, the order finish date can be moved by one day. As a result, the production dates can fall on a day that is a day off according to the factory calendar.

2. Activity dates

* Are the durations of the activity segments correct?

1. No: Go to point 2.1 “The durations of the activities are not correct”.
2. Yes: Go to point 2.2 “The durations of the activities are correct. However, the individual dates cannot be explained.”

2.1. The durations of the activities are not correct

* Check both the formula for calculating duration in the work center and the values entered in the network.

  • Which variables are used for the formulas?
  • How is the result calculated?
  • Using Transaction CR04, try to reproduce the problem for the activity stored in the work center. You can use this transaction to test the scheduling formulas of the work center. To do this, enter both the general activity values and the standard values and execute scheduling (F5).

* Are activities already finally confirmed?

Finally confirmed activities are no longer scheduled. The actual dates are copied to the activity dates. The durations are calculated from the actual dates.

* Are activities already partially confirmed?

For partially confirmed activities, the remaining duration is scheduled during forwards scheduling after the confirmed actual dates. The earliest start date is calculated from the confirmed actual start date. The earliest finish date is the same as the actual start date plus the forecasted processing time. If you have maintained a finish date for the forecast during the confirmation, scheduling adopts the finish date for the forecast for the earliest finish date. If there is neither a forecasted duration nor a forecasted finish date, the system then takes the planned duration (benchmark) as a starting point and adds it to the actual start date.
The latest dates are not adjusted to the actual situation. For the latest start and finish date, the activities are scheduled backwards from the start date of the successors with the remaining duration so that the buffers can be calculated for the activity.
Exception: If you set the “Shift order” indicator, the earliest dates are scheduled only with the remaining duration; the actual dates of the partially confirmed activities are not taken into account.

* Are the activities relevant to scheduling?

For this, check the activity control keys.
Note that for activities not relevant for scheduling, the system does not check whether the activity falls on a day off since the activity can always be executed directly before or after another activity. The duration of activities not relevant to scheduling is 0.

* Is the activity replaced by a subnetwork?

If the activity is not relevant to scheduling according to the control key, the activity is replaced by the subnetwork when an overall network is scheduled with the result that the subnetwork is copied to the activity.
If the activity is relevant to scheduling, the duration of the subnetwork is not copied to the activity duration.

* Is it an externally processed activity?

If the activity is defined as an externally processed activity, the system displays the planned delivery time as processing time and takes it into account. The activity is scheduled with the planned delivery time according to the Gregorian calendar.
Note that activities with the “Internally processed operation /external processing possible” characteristic in the relevant control key are not interpreted as externally processed activities during scheduling.

* Is it an activity element?

The activity element dates are calculated on the basis of their earliest/latest dates for the activity; in this case, the stored offsets are evaluated for the start and end. The duration defined by the dates found in this way is stored.

* Can the activity be extended?

Yes: The activity is extended according to the duration of the free float.

* Are the floats of the activity correct?

Check the floats using the dates of predecessors and successors.

* Has a reduction been executed during scheduling?

Check the scheduling log or the “Reduction” field in the order header screen.

  • Yes: Check the reduction parameters of scheduling and the scheduling log.

Check whether the duration of the in-house production has been calculated correctly according to the reduction.
Check whether the duration falls short of the minimum duration of the activity due to the reduction. In this case, the duration is set to the minimum duration.

2.2. The durations of the activities are correct. However, the individual dates cannot be explained.

In general, activities and relationships are scheduled using the operating time of a stored work center. If no work center is stored but a factory calendar is, the system performs scheduling to the day using the factory calendar. If neither work center nor factory calendar are stored, scheduling is performed according to the Gregorian calendar.

* Have relationships been maintained?

Here, note the time-dependent relationship representation in the network structure overview if necessary.

  • To which category does the relationship belong? Which activity is the predecessor, which one is the successor?
  • Has a duration of the relationship been maintained?
  • Do external relationships exist for activities of other networks?

In this case, the system takes the dates of the external activities into account as restriction dates. Here, the external network is not scheduled unless you start overall network scheduling.

* Is the operation scheduled?

Check the status of the activity and, if necessary, the scheduling dates.

* Have restriction dates been maintained for the activity?

Check the type of the restriction dates and check whether the activity dates are correct on account of the restrictions. Note that the restriction dates must always be taken into account unless the activity is dispatched or finally confirmed.

* Is the activity assigned to a WBS element?

For this, check the assignments of the activities (for example, on the general overview of activities).
The dates of the WBS element are adhered to if the element is determining the dates, that is, if you do not set the “Network scheduling” indicator in the WBS element. If you set the “Network scheduling” indicator in the WBS element so that the network determines the dates, the system does not take the WBS dates into account.
This does not apply if the activity is dispatched or finally confirmed or if restriction dates have been maintained.

* Does the time unit of the activity or the relationship corresponds to the unit day or is it even larger?

1. Yes: Go to point 2.2.1.
2. No: Go to point 2.2.2.

2.2.1. The time unit is greater than or equal to “day”

2.2.1.1. A work center is stored for the activity or relationship

Note that the dates determined are moved to the next respective productive date, under consideration of the capacity at the work center.

* Does an active version of the available capacity exist?

  • Yes: Scheduling is executed “to the day” using the days on which shifts are defined.

If no operating time is maintained for the specified period, the system performs scheduling according to the Gregorian calendar.

  • No: Continue.

* Has a factory calendar been stored in the work center?

  • Yes: Scheduling is executed “to the day” using the workdays of the factory calendar.
  • No: Scheduling is executed according to the Gregorian calendar.

2.2.1.2. No work center is stored for the activity or relationship, but a factory calendar is

Scheduling is executed “to the day” using the workdays of the factory calendar.
2.2.1.3. Neither a work center nor a factory calendar is stored for the activity or relationship

Scheduling is executed according to the Gregorian calendar.
2.2.2. The unit of the activity segment is smaller than “day”

2.2.2.1. A work center is stored for the activity or relationship
* Does an active version of the available capacity exist?

  • Yes: Has a shift sequence been stored?
    • No: Scheduling is performed using the shifts stored in the interval of available capacity. In this case the planned breaks are distributed equally over the entire shift duration.
    • Yes: Check whether work break schedules are stored in the shift definitions of the shift sequence and whether the “Scheduling allowing for breaks” indicator is activated in Customizing for the scheduling parameters.

If work break schedules are stored in the shift definitions of the shift sequence and the “Scheduling allowing for breaks” indicator is active, the system performs scheduling using shifts stored in the interval of available capacity, with breaks taken into account in a fixed manner.
If this is not the case, scheduling is performed using the shifts stored in the interval of available capacity. In this case, the planned breaks are distributed equally over the entire shift duration.

  • No: Has a standard available capacity been defined?
    • No: Scheduling is performed according to the Gregorian calendar.
    • Yes: If a factory calendar is defined, scheduling is executed using the standard available capacity and the workdays of the factory calendar, and the breaks are distributed equally over the entire shift duration.

If no factory calendar is defined, scheduling is executed using the standard available capacity and the workdays of the plant calendar, and the breaks are distributed equally over the entire shift duration.

  • The problem exists also when these rules are taken into account

Before you enter a customer message, try to reproduce the problem for the activity stored in the work center using transaction CR04. With this transaction, you can simulate scheduling using a work center. For this purpose, you can – on the one hand – specify the start or end of the productive time as well as a duration so that the missing date is determined with regard to the shifts of the work center. On the other hand, the productive time between the dates can be calculated by specifying the two dates and an initial duration under consideration of the shifts. For the two simulation types, start the determination of productive time (F8) and take the “Breaks” indicator into account for scheduling including breaks.

2.2.2.2. No work center is stored for the activity or relationship, but a factory calendar is

Scheduling is executed using the workdays of the factory calendar

2.2.2.3. Neither a work center nor a factory calendar is stored for the activity or relationship

Scheduling is executed using the plant calendar
3. Capacity requirements

Capacity requirements are calculated during scheduling. The dates of the respective activities are copied to the dates of the capacity requirements. Changes relevant to scheduling (for example, changes to the lot size) are copied to capacity requirements only after repeat scheduling.
In the network, check the “Person assignment” procedure detail screen to determine whether capacity requirements have been generated for this activity. You can receive a detailed display and an evaluation of the capacity data in the capacity requirements planning. You can branch directly from the network to graphical capacity requirements planning.
3.1. The system displays capacity requirements for a capacity category.

* Is the amount of the capacity requirements correct?

  • Yes: The result is correct
  • No: Check the following points:
    • Check the work for the activity and the formula for the capacity categories at the work center.
    • If necessary, test the formula at the work center with the work you maintained for the activity.

* Does the system display capacity requirements for all relevant capacity categories?

  • Yes: The result is correct
  • No: Check the capacity categories that exist for the work center

3.2. “Person assignment” detail screen does not exist even though you want to calculate capacity requirements

* Have you set the “Capacity requirements” indicator in the “Scheduling” header screen of the network?

  • No: Set this indicator and perform scheduling again. If no capacity requirements still exist afterwards, continue. The “Capacity requirements” indicator is copied from the settings for scheduling Customizing to the network header. If you want capacity requirements to be calculated as a general rule, change your Customizing accordingly.
  • Yes: Check the following points:
    • Check the work entered for the activity.
    • Check the formula used for the capacity category at the work center and, if necessary, test the formula at the work center with the value of the work used for the activity.
    • Check the control key used. If the control key of the activity does not support capacity requirements planning, the system does not calculate any capacity requirements.
    • Check the status of the activity. If the activity partially confirmed or finally confirmed? Finally confirmed operations no longer have capacity requirements.

3.3. Capacity requirements are displayed, even though you do not want capacity requirements to be calculated
You can deactivate capacity requirements planning in different ways. If you do not want the system to calculate capacity requirements for the entire network, deactivate the “Capacity requirements” field in the header of the network. If you never want the system to calculate capacity requirements, change your Customizing so that the “Capacity requirements” indicator is always inactive.
If you want the system to calculate no capacity requirements only for individual activities, choose a corresponding control key for this activity or use a work center without capacity categories.
4. The result still cannot be explained after the stated points have been checked
Before you enter a customer message:

  • Search for SAP Notes in the SAP Support Portal

Search for SAP Notes of your release for the components PP-CRP-SCH (Scheduling) and PS-DAT-NET (Network Scheduling). Do not mention key word “scheduling” because this key word is already sufficiently defined by the component allocation. For the search, use additional key words which characterize your problem or which characterize the data to be scheduled in more detail, for example: basic dates, activity dates, night shift, scheduling of overall network …

  • If you cannot find an SAP Note that solves your problem, create a customer problem message for the PP-CRP-SCH or PS-DAT-NET component. Answer the following questions in your problem description:

1. What does your problem look like?
For this, use this check list to define your problem as closely as possible.
2. Where and when does your problem occur and can the problem be reproduced?

    • If possible, make example data available and describe how your problem can be reproduced.
    • If your problem can be restricted to the scheduling of one activity, try to reproduce the problem for the work center stored in the activity using Transaction CR04.

With this transaction, you can simulate scheduling using a work center. For this purpose, you can – on the one hand – specify the start or end of the productive time as well as a duration so that the missing date is determined with regard to the shifts of the work center. On the other hand, the productive time between the dates can be calculated by specifying the two dates and an initial duration under consideration of the shifts. For the two simulation types, start the determination of productive time (F8) and take the “Breaks” indicator into account for scheduling including breaks.
You can also test the scheduling formulas of the work center with this transaction. To do this, enter both the general activity values and the standard values and execute scheduling (F5).
In the same way as for scheduling formulas, you can test the formulas which are the basis for the capacity requirement calculation (F6) and costing (F7).
3. What other determining factors exist?
For example, Customizing parameters scheduling type, relationships.

[/toggle]

[toggle title=”SAP NOTE: 151503 – Consulting: Scheduling of process order” state=”close”]

Symptom

The result of scheduling a process order is unclear.
The system does not correctly display the capacity requirements calculated by scheduling.

Other Terms

COR1, COR2, process order, scheduling, check list, collective order
capacity requirements, basic date, operation date, splitting, overlapping, shift, night shift

Reason and Prerequisites

Solution

Check your settings according to the questions listed below:

Check list

* Note the following general rules
Process orders are generally scheduled both forwards and backwards. The scheduling type defines which scheduling direction is taken into account first.
The dates of the earliest dates result from forward scheduling. The dates of the latest dates result from backward scheduling.

If a collective order scheduling is executed, check the following points. Otherwise, continue with the next question.

    1. Check which order in the collective order is scheduled.

If a collective order scheduling is executed for an order belonging to the collective order, the system schedules only the subnetwork defined by this order. Higher-level orders are not scheduled. Here, the basic dates of lower-level orders are determined by the requirements dates of the directly manufactured component.

    2. Check the framework dates and the scheduling type.

During collective order scheduling, scheduling is carried out from the framework dates in the collective order while during an order scheduling the basic dates of the order are used. The system takes framework dates of lower-level orders into account (see Note 97344) provided the ‘Adjust basic dates’ indicator is not set to active. If thealternative ‘Adjust basic dates’ is chosen, the basic dates of lower-level orders are adjusted if necessary.

    3. Check whether a relationship has been maintained in the directly manufactured component.

If a relationship is maintained in the detail screen of the component (here the specification of a unit of the duration is the decisive factor), the system copies the requirements date of the component to the order finish date of the lower-level order. If no relationship is maintained, the finish date of the last operation of the lower-level order is set to the requirements date. In this case, the order finish date of the lower-level order can be diffentiated from the requirements date of the component provided a float after production has been maintained in the lower-level order.

    4. Check to which operation/which phase the directly-manufactured component is assigned?

Note that for a transfer of the dates of the lower-level order into higher-level order in a forwards scheduling, the directly-manufactured component must be assigned to a phase, since only phases get a lead time scheduling and as a result, only phases enable dates to be transferred. Operations get their dates from the phase dates, as described in point 2.

Which results cannot be explained?
1. Basic dates
2. Operation dates
3. Phase dates
4. Capacity requirements

1. Basic dates

Check whether scheduling should be executed with the specification of time. For this, check the scheduling type in Customizing.

* Do the basic dates change?
Check whether the alternative ‘Adjust basic dates’ has been chosen for the scheduling parameters.
Check whether the basic dates are set correctly on account of the operation dates.

* Is it possible to explain the basic dates on account of the production dates?
1. Yes: The problem is caused by the operation dates. Proceed with the questions stored under “2. Operation dates”.
2. No: Continue.

* Has a “today” scheduling been executed?
Check the scheduling log for this.
Note that the scheduling type set is automatically overridden with a “today” scheduling as soon as the order start date lies further in the past than the number of days defined in Customizing. In the order, this value can be overridden by the scheduling parameters.

* Check the float before/after production of the order or the scheduling margin
* Have phases already been finally confirmed?
The system does not determine the dates for finally confirmed phases again but copies the actual dates to the phase dates. Relationships are not taken into account when the dates of the finally confirmed phase are determined. Relationships for successors of the finally confirmed phase are scheduled from the actual dates. Basic dates are only adjusted in consideration of the dates of not yet finally confirmed phases.

* Have night shifts been assigned to the last phase relevant to scheduling?
Yes: Note that for a backward scheduling the finish date is the end of the night shift of the previous day so that the order finish date concerning this can be moved one day into the past. As a result, the production dates can fall on a day off according to the factory calendar.

* How is the time of the order finish date calculated?
Check the in-house production time of the header material of the order in the material master since the time of the order finish date is determined regarding the following logic:

  • In-house production time is larger than 0 days:

For material-related orders, the system interprets the order finish date as a requirements date for the material. Therefore, the following rule applies: If an in-house production time greater than 0 days has been defined in the material master, the requirements date is at the beginning of the day, that is, the order finish date is set to 00:00. In this case, the order finish date of the production finish date differs by one day from the order because the production must have already been finished on the previous day so that the material is available at the beginning of the next day.

  • With an in-house production time equal to 0 days, it is assumed that the material can be produced at any time of a day. For this reason, the order finish date is set to 24:00.

2. Operation dates

The operation dates are determined from the dates of the respective phases. Here, the min max rule applies, the earliest start and latest finish dates are copied.

* Is it possible to explain the operation dates according to the min max rule from the dates of the respective phases?
Yes: Go to point 3.

* Is the operation duration correct?
The operation duration results from operation dates; in this case the duration is determined considering the available capacity of the resource.

* Has the operation been dispatched?
If the operation is dispatched, the operation dates result from capacity requirements planning due to the dispatching dates.

3. Phase dates

* Are the durations of the phases correct?
1. No: Go to point 3.1 ‘The duration of the phase is not correct’.
2. Yes:  Go to point 3.2 ‘The duration of the phase is correct. However, the dates cannot be explained.’.

3.1. The duration of the phase is not correct

3.1.1. Check the formula of the resource
Check both the formula for calculating the execution time in the resource and the standard values used in the process order/phase.

  • Please note that for calculating the execution time of phases, the formula for ‘duration of internal processing’ maintained in the resource is taken into account exclusively. All other formulas (‘duration of setup’, ‘duration of processing’ and ‘duration of tear down’) are not taken into account when determining the duration of the individual phases.
  • Which variables are used for the formulas?
  • How is the result calculated?
  • Using Transaction CR04, try to reproduce the problem for the resource stored in the phase. With this transaction, you can test the scheduling formulas of the resource. For this enter both the general operation values and the standard values and execute scheduling (F5).

3.1.2. Check status and type of the phase
* Have phases already been finally confirmed?
The system does not determine the dates for finally confirmed phases again but copies the actual dates to the phase dates. Relationships are not taken into account when the dates of the finally confirmed phase are determined. Relationships for successors of the finally confirmed phase are scheduled from the actual dates. Operations dates are only adjusted under consideration of the dates of not yet finally confirmed phases.

* Have phases already been partially confirmed?
For partially confirmed phases, the remaining duration is scheduled after the confirmed actual dates.
Exception: If indicator ‘Shift order’ is activated, the remaining duration of the actual dates can be scheduled separately.

* Are the phases relevant to scheduling?
For this, check the control keys of the phases.
Note that for phases not relevant to scheduling the system does not check whether the operation falls on a day off since the phase can always be executed directly before or after another phase.

* Is it an externally processed phase?
For this, check the control key. Note that operations with the ‘Internally processed operation/external processing possible’ characteristic are not interpreted as externally processed operations during the scheduling.
If the phase is defined as an externally processed phase, the system displays and takes the planned delivery time as processing time into account. The phase is scheduled with the planned delivery time according to the Gregorian calendar.
As of Release 4.0, you can schedule externally processed phases also using the formulas at the work center. For this, indicator Scheduling external operation with standard values must be active in the respective control key. In this case, the planned delivery time is not taken into account.

* Is it a secondary resource?
Secondary resources are not scheduled by means of standard values. The dates are calculated due to their earliest/latest dates for the phase; in this case, the stored offsets are evaluated for start and end. The system copies the duration between the dates found this way as a processing time of the secondary resource.

* Can the phase be extended?
Yes: The phase is extended according to the duration of the free float.
The free float corresponds to the possible delay until a successor occurs without having the dates of the successor being moved.

* Has a reduction been executed during scheduling?
For this, check the scheduling log or the ‘Reduction’ field in the order header screen.
Yes: Check the reduction parameters of scheduling.

3.2. The duration of the phase is correct, however, the dates cannot be explained.

In general, phases and relationships are scheduled using the operating time of a stored resource. If no resource is stored but a factory calendar, it is scheduled to the day using the factory calendar. If neither resource nor factory calendar is stored, it is scheduled according to the Gregorian calender.

* Have relationships been maintained?

  • To which category does the relationship belong? Which phase is the predecessor, which one the successor?
  • Has a duration of the relationship been maintained?
  • Do external relationships exist for phases of other process orders?

In this case, the system takes into account the dates of the external phase as a restriction date. Here, the external process order is not scheduled unless you have started scheduling of external relationships.

* Has the phase been dispatched?
Check the status of the phase. If the phase is dispatched, the phase dates result from capacity requirements planning due to the dispatching dates.

* Does the duration unit corresponds to unit day or is it even larger?
1. Yes: Go to point 3.2.1.
2. No:  Go to point 3.2.2.

3.2.1. The time unit is larger than or equal to day
Note that the dates that have been determined, provided that a work center has been stored in the operation, are shifted to the next production date, taking the available capacity in the work center into account.

* Does an active version of the available capacity exist?
1. Yes: Scheduling is executed to the day using the days on which shifts are defined. If no operating time is maintained for the specified period, the system schedules according to the Gregorian calendar.
2. No: Continue.

* Has a factory calendar been stored in the work center?
1. Yes: Scheduling is executed to the day using the workdays of the factory calendar.
2. No: Scheduling is executed to the day using the plant calendar.

3.2.2. The time unit is smaller than day
* Does an active version of the available capacity exist?
1. Yes Go to point 3.2.2.1.
2. No  Go to point 3.2.2.2.

3.2.2.1. An active version of the available capacity exists
* Has a shift sequence been stored?

  • No: It is scheduled using the shifts stored in the interval of available capacity; in this case, the planned breaks are distributed equally over the entire shift duration.
  • Yes: Check whether work break schedules are stored in the shift definitions of the shift sequence and whether the ‘Scheduling allowing for breaks’ indicator (view master data) is activated.

If work break schedules are stored in the shift definitions of the shift sequence and the ‘Scheduling allowing for breaks’ indicator is activated, the system schedules using the shifts stored in the interval of available capacity, while in doing so, the breaks are taken permanently into account. If this is not the case, the system schedules using the shifts stored in the interval of available capacity, while in doing so the planned breaks are distributed equally over the entire shift duration.
3.2.2.2. An active version of the available capacity does not exist
* Has a standard available capacity been stored?

  • No: It is scheduled according to the Gregorian calendar.
  • Yes: If a factory calendar is stored, scheduling is executed using the standard available capacity and the workdays of the factory calendar, while in doing so the breaks are distributed equally over the entire shift duration.

If no factory calendar is stored, scheduling is executed using the standard available capacity and the workdays of the plant calendar, while in doing so the breaks are distributed equally over the entire shift duration.

3.2.2.3. The problem exists also when rules are considered
Before you enter a customer message, try to reproduce the problem for the resource stored in the phase using Transaction CR04. With this transaction, you can simulate the scheduling using a resource. For this purpose, you can on the one hand specify the start or end of the productive time as well as a duration so that the missing date is determined with regard to the shifts of the resource. On the other hand, with regard to the shifts, the productive time between the dates can be calculated by specifying the two dates and an initial duration. Start for the two simulation types the determination of productive time (F8) and take the ‘Breaks’ indicator into account for scheduling allowing for breaks.


4. Capacity requirements

Capacity requirements are calculated during scheduling. The dates of the respective phases/operations are copied to the dates of the capacity requirements. Changes relevant to scheduling (for example, changes to the lot size) are only copied to the capacity requirements after another scheduling.
The system calculates capacity requirements for phases with the phase due to the standard values and the resource. Operations receive the total of the capacity requirements of the respective phases as capacity requirements, therefore the capacity requirements for operations are not calculated on the basis of the standard values of the operation.
You receive a display and an evaluation of the capacity data in the capacity requirements planning.


4.1. The system displays capacity requirements for a capacity category.

* Is the amount of the capacity requirements correct?

  • Yes: The result is correct
  • No: Check the following points:
    • Check the standard values in the phase and the formula for the capacity category in the resource.
    • If necessary, test the formula in the ressouce with the standard values you used and with the lot size of the phase.
    • Has the capacity requirements of an operation been correctly calculated from the total of the capacities of the respective phases?
    • Has an optimization of setup time been executed in the capacity planning table which reduced the proportional setup capacity requirements?
    • Has a confirmation with forecast values been entered for the respective phase so that the confirmed forecast values replace the standard values when the formula is calculated?

* Does the system display capacity requirements for all relevant capacity categories?

  • Yes: The result is correct
  • No: Check the capacity categories existing at the work center


4.2. The system does not display any capacity requirements although capacity requirements ought to be calculated

* Have you set the ‘Calculate capacity requirements’ indicator in the ‘Control’ header screen of the order?

  • No: Set this indicator and execute scheduling again. If still no capacity requirements exist afterwards, continue. Indicator ‘Calculate capacity requirements’ is copied from the settings of the Scheduling Customizing to the order header. If you basically want to have capacity requirements calculated, change your Customizing correspondingly.
  • Yes: Check the following points:
    • Check the standard values in the phase.
    • Check the formula used for the capacity category in the resource and test the formula with the standard values of the resource, if necessary.
    • Check the control key used. If the control key of the phase does not support any capacity requirements planning, the system does not calculate any capacity requirements.
    • Check the status of the phase. Does a remaining quantity to be produced exist after a partial confirmation or has the entire lot size of the phase already been confirmed? Finally confirmed phases have no longer any capacity requirements.


4.3. The system displays capacity requirements although no capacity requirements should be calculated

You can deactivate the capacity requirements planning in different ways. If you do not want the system to calculate any capacity requirements for the entire process order, deactivate the `Calculate capacity reqs` field in the header of the order. If you want the system to never calculate capacity requirements, change your Customizing correspondingly so that the `Calculate capacity requirements` indicator is always inactive.
If you only want the system to calculate no capacity requirements for individual operations, choose a corresponding control key for this operation/phase or use a resource without capacity categories.


5. The result can also not be explained after the stated points have been checked.

Before you enter a customer problem message:

  • Search for notes in the Online Service System

Search for notes of your release for component PP-CRP-SCH (scheduling). Do not mention key word ‘scheduling’ because this key word is already sufficiently defined by the component allocation. For the search, use additional key words which characterize your problem or which characterize the data to be scheduled in more detail, for example: Basic dates, operation dates, night shift …

  • If you cannot find a note that solves your problem, create a customer problem message for the PP-CRP-SCH component. Answer the following questions in your problem description:

1. What does your problem look like?
For this, restrict your problem as far as possible with this check list.
2. Where and when does your problem occur or can the problem be reprocessed?

    • If possible, make example data available and describe how your problem can be reprocessed.
    • If your problem can be restricted to the scheduling of one phase, try to reproduce the problem for the resource stored in the phase using Transaction CR04.

With this transaction, you can simulate scheduling using a resource. For this purpose, you can on the one hand specify the start or end of the productive time as well as a duration so that the missing date is determined with regard to the shifts of the resource. On the other hand, with regard to the shifts, the productive time between the dates can be calculated by specifying the two dates and an initial duration. Start for the two simulation types the determination of productive time (F8) and take the ‘Breaks’ indicator into account for scheduling allowing for breaks.
Furthermore, you can test the scheduling formulas of the resource with this transaction. For this enter both the general operation values and the standard values and execute scheduling (F5).
In the same way as the for scheduling formulas, you can test the formulas which are the basis for the capacity requirements calculation (F6) and costing (F7).
3. What other determining factors do exist ?
For example, Customizing parameters, scheduling type, parallel sequences …

[/toggle]

[toggle title=”SAP NOTE: 150007 – Consulting: Scheduling of production orders” state=”close”]

Symptom

The result of production order scheduling is unclear.
The system does not display the capacity requirements calculated by scheduling correctly.

Other Terms

CO01, CO02, production order, scheduling, check list, collective order, capacity requirements, basic date, operation date, splitting, overlapping, shift, night shift

Solution

Check your settings according to the questions listed below.

Check list

If a collective order scheduling is executed, check the following points. Otherwise, continue with the next question.

    1. Check which order of the collective order is scheduled.

If a collective order scheduling is executed for an order associated with the collective order, the system only schedules the subnetwork defined by this order. Higher-level orders are not scheduled. Here, the basic dates of lower-level orders are determined by the requirements dates of the directly manufactured component.

    2. Check the framework dates and the scheduling type.

During collective order scheduling, scheduling is carried out from the framework dates in the collective order whereas, during an order scheduling, the basic dates of the order are used. The system takes framework dates of lower-level orders into account (see Note 97344) provided the “Adjust basic dates” indicator is not activated. If the alternative “Adjust basic dates” is selected, the basic dates of lower-level orders are adjusted, if necessary.

    3. Check whether a relationship has been maintained in the directly manufactured component.

If a relationship is maintained in the detail screen of the component (here the specification of a unit of the duration is the deciding factor), the system copies the requirements date of the component to the order finish date of the lower-level order. If no relationship is maintained, the finish date of the last operation of the lower-level order is set to the requirements date. If scheduling parameters are set to “Dependent requirements to operation dates”, the move time between the last operation of the lower-level order and the operation to which the component is allocated is taken into account. In this case, the order finish date of the lower-level order can differ from the requirements date of the component provided a float after production has been maintained in the lower-level order.

Which dates cannot be explained?

    1. Basic dates
    2. Operation dates
    1. 3. Capacity requirements

1. Basic dates

Check whether scheduling should be performed with a time being specified. For this, check the scheduling data of the scheduling type in Customizing.

* Do the basic dates change?

Check whether the alternative “Adjust basic dates” has been selected for the scheduling parameters.
Check whether the basic dates are set correctly on account of the operation dates.

* Is it possible to explain the basic dates on account of the operation dates?

    1. Yes: The problem is caused by the operation dates. Proceed with the questions stored under “2. Operation dates”.
    2. No: Continue.

* Has a “today” scheduling been executed?

For this, check the scheduling log.
Note that the scheduling type set is automatically overridden with a “today” scheduling as soon as the order start date lies further in the past than the number of days defined in Customizing. In the order, this value can be overridden by the scheduling parameters.

* Check the float before/after production of the order or the scheduling margin key.
* Have operations already been finally confirmed?

Finally confirmed operations are no longer scheduled. The actual dates are copied to the operation dates. These are no longer taken into account when the remaining operations are scheduled. The basic dates are adjusted correspondingly only under consideration of the dates of not yet finally confirmed operations.

* Have night shifts been assigned to the last operation relevant to scheduling?

Yes: Note that for a backward scheduling the finish date is the end of the night shift of the previous day so that the order finish date concerning this can be moved one day into the future. As a result, the production dates can fall on a day off according to the factory calendar.

* How is the time of the order finish date calculated?

Check the in-house production time of the header material of the order in the material master since the time of the order finish date is determined with regard to the following logic:

  • In-house production time is longer than 0 days:

For material-related orders, the system interpretes the order finish date as a requirements date for the material. Therefore, the following rule applies: If an in-house production time that is longer than 0 days has been defined in the material master, the requirements date is at the beginning of the day, that is, the order finish date is set to 00:00. In this case, the order finish date of the production finish date differs by one day from the order because the production must have already been finished on the previous day so that the material is available at the beginning of the next day.

  • With an in-house production time equal to 0 days, it is assumed that the material can be produced at any time of a day. For this reason, the order finish date is set to 24:00.

2. Operation dates

* Are the durations of the operation segments correct?

    1. No: Go to point 2.1 “The durations of the operation segments are not correct”.
    2. Yes: Go to point 2.2 “The durations of the operation segments are correct, however, the individual dates cannot be explained”.

2.1 The durations of the operation segments are not correct.

2.1.1 Check the individual operation segments.

  • Queue time

Has the queue time been entered manually in the operation (Interoperation times view)?
No: Check whether the queue time has been copied from the work center of the operation correctly.
If the operation has been overlapped by a previous operation, the system uses the queue time of the operation overlapped first.

  • Setup, processing, tearing down

Check both the formulas for calculating the execution time in the work center and the standard values used in the order.

    • Which variables are used for the formulas?

If a split has been executed, for example, for the operation without this having any effect on the duration calculated, check whether the system has taken the number of splits into account in the scheduling formulas.

    • How does the system calculate the result?
    • Using Transaction CR04, try to reproduce the problem for the operation stored in the work center. With this transaction, you can test the scheduling formulas of the work center. For this enter both the general operation values and the standard values and execute scheduling (F5).
  • Wait time

Check whether a minimum wait time has been entered in the operation (Interoperation times view).

  • Transfer

Has the move time been entered in the operation manually (Interoperation times view)?

    • 1. Yes: Check that the transfer has been executed correctly.
    • 2. No: Check whether the move time has been calculated correctly from the move time matrix.

2.1.2 Check the status and type of the operations
* Have the operations been finally confirmed already ?

Finally confirmed operations are no longer scheduled. The actual dates are copied to the operation dates. The durations are calculated from the actual dates.

* Have operations been partially confirmed ?

For partially confirmed operations, the remaining duration is scheduled after the confirmed actual dates.
Exception: If the “Shift order” indicator is activated, the remaining duration of the actual dates can be scheduled separately. Here, note that the setup duration is calculated again.

On rescheduling an operation after partial confirmation has been performed, the queue time is set to 0. Since the operation has already started and completed partially, the queue time has already been considered and it will not be considered again for the remaining quantity or duration.

* Are the operations relevant to scheduling ?

For this, check the operation control keys.
Note that for operations not relevant to scheduling the system does not check whether the operation falls on a day off since the operation can always be executed directly before or after another operation.

* Have you defined not only units of measurement less than “Day” for the standard values?

The unit of measurement for time segments Setup, Processing, and Tearing down is equal for all three time segments. It is defined as the largest of all units of measurement of the standard values.
The durations calculated via the formulas are converted in accordance with the global units of measurement from the Customizing, for example, a day has 24 hours. This can be explained by the fact that various quotations could possibly be taken into account for the determination of the durations. The various quotations are based on different operating times. Hence, you generally cannot decide how long a day at the work center lasts since the quotation of the work center can be different every day.
Thereby, the schedules might not be determined as expected (see also sections 2.2.1 and 2.2.2).
If you encounter problems in this respect, check whether the introduction of a new time unit, as, for example, 1 work day = 8 hours, could serve as a solution.

* Has a splitting been executed ?

Yes: As of Release 4.5, the system displays the actual number of splittings on the operation detail view “Splitting”.

  • If the number of splittings entered does not match the number of the individual capacities stored in the work center of the operation for the capacity relevant to scheduling, the system uses the smaller value of the two values for the calculation (Note 101308).
  • Note the minimum processing time.

* Is it an external processing operation?

For this, check the operation control key. Note that operations with the “Internally processed operation/external processing possible” characteristic are not interpreted as externally processed operations during scheduling.
If the operation is defined as an operation processed externally, the system displays and takes the planned delivery time as processing time into account. The operation is scheduled with the planned delivery time according to the Gregorian calendar.
As of Release 4.0, you can also schedule externally processed operations with the formulas at the work center. For this, indicator “Scheduling external operation with standard values” must be active in the relevant control key. In this case, the planned delivery time is not taken into account.

* Is it a sub-operation ?

Sub-operations are not scheduled using standard values. The dates are calculated on the basis of their earliest/latest dates for totals operation. In this case, the stored offsets are evaluated for start and end. The system copies the duration between the dates found this way as a processing time of the sub-operation.

* Has a flow manufacturing been set?

Yes: Then the durations of the operations are extended according to the operation with the longest duration.

* Has a reduction been executed during scheduling ?

For this, check the scheduling log or the “Reduction” field on the order header screen.
Yes: Check the reduction parameters of the scheduling (reduction of the queue time, move time indicator, overlapping, split).
Check whether the durations of the operation segments have been correctly calculated according to the reduction. For this, go to section 2.1.1, if necessary.
If an overlapping occurred, go to section 2.3, if necessary.

2.2 The durations of the operation segments are correct, however, the individual dates cannot be explained.

* Has the operation been dispatched?

Check the status of the operation. If the operation is dispatched, the operation dates result from capacity requirements planning due to the dispatching dates.

* Do parallel sequences exist?

The operation dates of a parallel sequence result from the alignment. In case of an alignment with latest date, the operations of the parallel sequence have the latest possible dates. In case of an alignment with earliest date, the operations of the parallel sequence have the earliest possible dates. Here, the alignment refers to branch or return operation.
Note that the standard sequence also has an alignment.

* Has the correct alternative sequence been selected?

For this, check the sequence overview and choose the “Exchange sequences” function, if necessary.

* Have the operations been overlapped?

Yes: Check section 2.3 “The operations are overlapped”.

* How is move time scheduled?

If a move time matrix is stored, the move time matrix is scheduled making allowance for the operating time stored in the move time matrix, even if the move time matrix was entered in the transaction manually.
If a move time matrix is not stored, scheduling is performed making allowance for the work center quotation, to which the move time is assigned (refer to 2.2.1 and 2.2.2 which follow).

* How ist the wait time scheduled?

The wait time is scheduled acc. to the Gregorian calendar, i.e. neither a factory calendar nor the capacity of the work center are taken into account.

* Does the unit of the operation segments correspond to unit “Day” or is it even larger?

    1. Yes: Go to section 2.2.1.
    2. No: Go to section 2.2.2.

2.2.1 The unit of the operation segment is larger than or equal to day

Note that the schedules which have been determined are postponed to the next productiion date, taking the quotation in the work center into account – provided that a work center is stored in the operation.

* Does an active version of the available capacity exist ?

    1. Yes: Scheduling is executed to the day using the days on which shifts are defined. If no operating time is maintained for the specified period, the system schedules according to the Gregorian calendar.
    2. No: Continue.

* Has a factory calendar been stored in the work center?

    1. Yes: Scheduling is executed to the day using the workdays of the factory calendar.
    2. No: Scheduling is executed to the day using the plant calendar.

2.2.2 The unit of the operation segment is smaller than day
* Does an active version of the available capacity exist?

    1. Yes: Go to section 2.2.2.1.
    2. No: Go to section 2.2.2.2.

2.2.2.1 An active version of the available capacity exists.
* Has a shift sequence been stored?

  • No: It is scheduled using the shifts stored in the interval of available capacity. In this case, the planned breaks are distributed equally over the entire shift duration.
  • Yes: Check whether work break schedules are stored in the shift definitions of the shift sequence and whether the “Scheduling allowing for breaks” indicator (Master data view) is activated. This indicator has been copied from the Customizing of scheduling.

If work break schedules are stored in the shift definitions of the shift sequence and the “Scheduling allowing for breaks” indicator is activated, the system schedules using the shifts stored in the interval of available capacity while in doing so the breaks are taken permanently into account. If this is not the case, the system schedules using the shifts stored in the interval of available capacity, while in doing so the planned breaks are distributed equally over the entire shift duration.

2.2.2.2 An active version of the available capacity does not exist.
* Has a standard available capacity been stored?

  • No: It is scheduled according to the Gregorian calendar.
  • Yes: If a factory calendar is stored, scheduling is executed using the standard available capacity and the workdays of the factory calendar, while in doing so the breaks are distributed equally over the entire shift duration.

If no factory calendar is stored, scheduling is executed using the standard available capacity and the workdays of the plant calendar, while in doing so the breaks are distributed equally over the entire shift duration.

2.2.2.3 The problem also exists when these rules are considered.

Before you enter a customer message, try to reproduce the problem for the operation stored in the work center using Transaction CR04. With this transaction, you can simulate the scheduling using a work center. For this purpose, you can on the one hand specify the start or end of the productive time as well as a duration so that the missing date is determined with regard to the shifts of the work center. On the other hand, with regard to the shifts, the productive time between the dates can be calculated by specifying the two dates and an initial duration. Start for the two simulation types the determination of productive time (F8) and take the “Breaks” indicator into account for scheduling allowing for breaks.
2.3 The operations are overlapped.

  • Note the minimum send-ahead quantity and the minimum processing time.
  • The processing time of the following operation starts after the processing and move time required for the minimum send-ahead quantity. Note that the setup time is before this processing time and that the following operation can start before the predecessor due to this reason (to be exact if the setup duration of the successor is greater than the setup, processing, and transfer duration of the predecessor).
  • The processing time of the following operation does not start immedately after the processing and move time required for the required minimum send-ahead quantity if the processing time of the successor is smaller than the processing time of the predecessor. In this case, the finish time of the successor is first calculated with the send-ahead quantity of the finish date of the predecessor. The start time of the successor is calculated from this finish date through a backward scheduling of the successor. This occurs since the operations are processed without any interruption.
  • During flow manufacturing the operations are overlapped and extended according to the longest operation.
  • If the last flow manufacturing operation overlaps with the next operation as usual, the last flow manufacturing operation has to be the longest operation for flow manufacturing. Similarly, the first flow manufacturing operation has to be the longest operation for flow manufacturing if the previous operation overlaps with the first flow manufacturing operation as usual.

3. Capacity requirements

Capacity requirements are calculated during scheduling. The dates of the respective operations are copied to the dates of the capacity requirements. Changes relevant to scheduling (for example, changes to the lot size) are only copied to the capacity requirements after another scheduling.
Check the operation detail screen “Split allocation” in the production order to check whether capacity requirements have been generated for this operation. A detailed display and evaluation of the capacity data can be obtained in the capacity requirements planning.
3.1 The system displays capacity requirements for a capacity category.

* Is the amount of the capacity requirements correct?

  • Yes: The result is correct.
  • No: Check the following points:
    • Check the standard values in the operation and the formula for capacity category at the work center.
    • If necessary, test the formula at the work center with the standard values you used and with the lot size of the operation.
    • Has an optimization of the setup time been executed in the capacity planning table which reduced the setup capacity requirements ?
    • Has a confirmation with forecast values been entered for the respective operation so that the confirmed forecast values replace the standard values when the formula is calculated?

* Does the system display capacity requirements for all relevant capacity categories?

  • Yes: The result is correct.
  • No: Check the capacity categories existing at the work center.

3.2 The system does not display any capacity requirements although capacity requirements ought to be calculated.

* Have you set the “Calculate capacity requirements” indicator in the “Control” header screen of the order ?

  • No: Set this indicator and execute scheduling again. If still no capacity requirements exist afterwards, continue. Indicator “Calculate capacity requirements” is copied from the settings of scheduling Customizing to the order header. If you basically want to have capacity requirements calculated, change your Customizing correspondingly.
  • Yes: Check the following points:
    • Check the standard values in the operation.
    • Check the formula used for the capacity category with the work center and test the formula with the standard values at the work center, if necessary.
    • Check the control key used. If the control key of the operation does not support any capacity requirements planning, the system does not calculate any capacity requirements.
    • Check the status of the operation. Does a remaining quantity to be produced exist after a partial confirmation or has the entire operation quantity been confirmed already ? Finally confirmed operations have no more capacity requirements.

3.3 The system displays capacity requirements although no capacity requirements should be displayed.
You can deactivate the capacity requirements planning in different ways. If you do not want the system to calculate any capacity requirements for the entire order, deactivate the “Calculate capacity reqs” field in the order header. If you want the system to never calculate any capacity requirements, change your Customizing correspondingly so that the “Calculate capacity requirements” indicator is always inactive.
If you only want the system not to calculate any capacity requirements for individual operations, select a corresponding control key for this operation or use a work center without capacity categories.
4. The result can also not be explained after the stated points have been checked.

Before you enter a customer problem message:

  • Search for notes in the Online Service System.

Search for notes relevant to your release in component PP-CRP-SCH (scheduling). Do not specify keyword “scheduling” because this key word is already sufficiently defined by the component allocation. For the search, use additional keywords which characterize your problem or which characterize the data to be scheduled in more detail, for example: Basic dates, operation dates, overlapping, splitting, night shift …

  • If you cannot find a note that solves your problem, create a customer problem message for the PP-CRP-SCH component. Answer the following questions in your problem description:

1. What does your problem look like?
For this, restrict your problem as far as possible using this check list.
2. Where and when does your problem occur or can the problem be reprocessed?

    • If possible, make sample data available and describe how your problem can be reprocessed.
    • If your problem can be restricted to the scheduling of one operation, try to reproduce the problem for the work center stored in the operation using Transaction CR04.

With this transaction, you can simulate scheduling using a work center. For this purpose, you can on the one hand specify the start or end of the productive time as well as a duration so that the missing date is determined with regard to the shifts of the work center. On the other hand, with regard to the shifts, the productive time between the dates can be calculated by specifying the two dates and an initial duration. Start for the two simulation types the determination of productive time (F8) and take the “Breaks” indicator into account for scheduling allowing for breaks.
Furthermore, you can test the scheduling formulas of the work center with this transaction. For this enter both the general operation values and the standard values and carry out scheduling (F5).
In the same way as the scheduling formulas, you can test the formulas which are the basis for the capacity requirements calculation (F6) and costing (F7).
3. What other determining factors exist?
For example, Customizing parameters, scheduling type, parallel sequences, overlapped operations …

[/toggle]

[toggle title=”SAP NOTE: 46237 – Consulting: determination of the order dates” state=”close”]

Symptom

Production dates (scheduled start date and finish date of the order) are on a non-working day.
The order finish date is one day later than the production finish date.
The order finish date of a planned order is not adjusted although ‘Adjust forward scheduling with basic date’ was set in Customizing.
The production dates in the planned order do not match the operation dates.

Other Terms

MF50, MD01, MD02, MD03, MD11, MD12

Reason and Prerequisites

——————————————-
Calculation of the scheduled order dates
——————————————-
For material-related orders, the scheduled order dates are the same as the production dates. We subsequently speak about production dates to simplify the matter.Scheduling calculates the production dates of an order by means of the operation dates. The earliest start date of all operations determines the production start date of the order, the latest finish date of the operations determines the production finish date of the order.
Operation dates and therefore production dates of the order can be on a non-working day according to the factory calendar.

  • For work center shifts, a shift can be started or finished past the minimum period in days on a non-working day.
  • If according to the control keys operations are not relevant to scheduling, there is not a check whether operation is scheduled on a non-working day because it can always be executed directly before or after another operation.

————————-
Calculation of basic dates
————————-
Adjust basic dates indicator

The basic dates can be adjusted by scheduling depending on the control parameters. Then, they are always on a workday in this case. If the dates are not adjusted, they are not changed by scheduling, so that they can also be on a non-working day.

In the planning run, the basic dates of the planned orders are determined via the in-house production time from the material master. The order finish date which is determined by the planning run displays the requirements date of the material. A subsequent scheduling of the planned order must not change this requirements date even if the ‘Adjust basic dates’ indicator is set. A date adjustment is only required if the in-house production time in the material master is too small. The in-house production time in the material master should be maintained so that no adjustment of the order finish date is required. As of Release 3.0C, an exception message is displayed in the MRP list and in the stock/requirements list.

Time of the basic dates

Certain order categories support scheduling types, in which scheduling is “starting from of basic dates with times”. The following applies to a scheduling type for which no times can be specified for the basic dates:
The order start date is set to 00:00 o’clock.
The order finish date is set to the end of the day, that is, 24:00 o’clock for all material-independent orders / networks.
In material-related orders, the order finish date is interpreted as requirements date for the material, therefore, the following rule applies: If an in-house production time is defined as more than 0 days in the material master, the requirements date is set to the beginning of the day, that is, the order finish date is set to 00:00 o’clock. You assume that the material can be produced at any time of the day with an in-house production time that is equal to 0 days. The order finish date is then set to 24:00 o’clock.
If the order finish date was set to 00:00 o’clock, it differs from the production finish date of the order by one day because the production must already be finished at the day before so that the material is available at the beginning of the next day.
——————————————————–
Calculation of the production dates in the planned order
——————————————————–
In the planned order, the production dates are calculated via the minimum and maximum operation dates. However, only operations which have capacity requirements can be displayed in the planned order. However, during the calculation of the production dates, also operations which have no capacity requirements must be considered because all exisiting operations must be within the production dates. Therefore, the minimum and maximum dates in the operation overview and the production dates in the planned order can differ.
For specifying the production dates also the operations which are according to the control key not relevant for scheduling must be considered. These operations are not scheduled itself but receive dates due to the predecessor or successor operations. If the first operation is an operation not relevant for scheduling, this operation has as date the order start date during a forward scheduling. If the last operation is an operation not relevant for scheduling, this operation has the order finish date as a date during a backward scheduling. Then the production dates might match the basic dates although the work centers of the operations relevant for scheduling are not productive at the date of the basic dates.

Solution

This is not an error; see the explanation above.

[/toggle]

[toggle title=”SAP NOTE: 1857912 – production order is rescheduled after confirmation” state=”close”]

Symptom

  • Prod Order Latest Schedule Finish Date affected by confirm
  • rescheduling after confirmation
  • Basic start dates overwritten after order confirmation

Environment

  • all SAP Releases

Reproducing the Issue

  1. Create an order in CO01
  2. Release the order in CO02
  3. Post a confirmation for this order (CO11N, CO11,….)
  4. Check this order in CO03
  5. See the order is rescheduled

Cause

Customizing of the used production scheduling profile.

 

Resolution

  1. Goto CO03 and display the effected order
  2. Choose tab ‘Control’
  3. Check the assigned production scheduling profile
  4. Goto Customizing OPKP
  5. Choose the plant and production scheduling profile
  6. Unset flag “Adjustment of Operation/Component Quantities to Act. Values”OPKP Screen.png

If the flag “Adjustment of Operation/Component Quantities to Act. Values” is set, then the confirmation lead to rescheduling of the order, this is documented and correct.
See F1-Help of this flag, here it’s listed “After confirmation, the order is rescheduled in the background.”

[/toggle]

[toggle title=”SAP NOTE: 680454 – Order dates after confirmation” state=”close”]

Symptom

After the partial or final confirmation of an operation the system does not adjust the operation dates and the order dates.
As long as there are still remaining requirements for the operation, the system displays it with its original resource dates in the planning table of the capacity requirements planning.

Other Terms

CO01, CO02, production order, process order, scheduling, capacity requirements, Capacity Reqmts, CM21, CM29, CM25

Reason and Prerequisites

Solution

The system works correctly.
After a confirmation, the system does not perform a rescheduling of the order. With a confirmation, the system does not adjust planned dates of the operation and the order which existed prior to the confirmation. Status NTUP is not set in the order.
The system only adjusts the capacity requirements.
You can achieve an adjustment of the dates by rescheduling the order or by scheduling, rescheduling or deallocating an operation of the order in the planning table of the capacity requirements planning.

[/toggle]

LEAVE A REPLY

Please enter your comment!
Please enter your name here