Considering Fixed Pegging Relationships 

Use

You can define in the detailed scheduling strategy whether the system should consider the fixed pegging relationships to other dependent objects when scheduling or rescheduling an object (activity, operation or order). Considering fixed pegging relationships means scheduling or rescheduling the object and its dependent object such that no requirements dates are violated. You have the following options:

·         Do not consider fixed pegging relationships

·         Consider fixed pegging relationships

·         Consider fixed pegging relationships in the propagation range

In principle, the system retains fixed pegging relationships during scheduling or rescheduling; that is, the assignment of a receipt element or stock element to a requirements element is maintained.

Prerequisites

If the system is to consider fixed pegging relationships during scheduling or rescheduling, you must also define in the detailed scheduling strategy that the system should consider time relationships between operations.

Features

Do not consider fixed pegging relationships

The system schedules or reschedules an object without considering requirements dates. This means that the requirements dates may be violated. If the availability date/time is earlier or later than the alert thresholds specified in the location product master, the system will create a date/time alert.

Consider fixed pegging relationships

The system must schedule or reschedule an object such that the availability date/time is as close as possible to, but still before the requirements date. If the object has a fixed pegging relationship to an unfixed object, the system must schedule or reschedule this dependent object accordingly; for an unfixed deallocated activity, the system must also adjust the dates and modes.  A fixed dependent object defines a fixed availability date/time or a fixed requirements date which restricts the scheduling or rescheduling of the object. If it is not possible to schedule or reschedule the object and its dependent objects accordingly, because the resources are occupied, for example, the system does not carry out scheduling or rescheduling.

A sales order or a planned independent requirement is fixed and defines a fixed requirements date. With the consider fixed pegging relationships option, the system must schedule a planned order for the sales order or planned independent requirement so that the availability date/time is as close as possible before the requirements date.

The system cannot correct an existing delay situation - in a pegging relationship the availability date/time is after the requirements date - , that is, it schedules or reschedules the object without time constraints.

Consider fixed pegging relationships only in the propagation range

Objects outside the propagation range are, in principle, fixed during planning, that is, these objects define fixed availability dates/times or requirements dates. This can lead to severe limitations for scheduling. With the consider fixed pegging relationships only in the propagation range option, you can plan more flexibly, since the system must consider a pegging relationship between an object in the propagation range and an object outside the propagation range (see do not consider fixed pegging relationship); the system can schedule or reschedule the object in the propagation range without constraints. However, the system must consider pegging relationships between objects within the propagation range (see Consider Fixed Pegging Relationships).