Setting Requirements and Delivery Relevance (SAP Library - Scheduling Agreements for Component Suppliers (SD-SLS-OA))

Setting Requirements and Delivery Relevance

Use

Requirements and delivery relevance in delivery schedules is influenced by the document type, and the schedule line category that the system determines using the requirements planning indicator specified in the scheduling agreement header.

Integration

To decide which type of delivery schedule is currently relevant for requirements and delivery, the system uses the JIT delivery schedule horizon and the material requirements planning indicator in the scheduling agreement header.

If there are planning delivery schedules in the scheduling agreement and you have entered a planning delivery schedule instruction, the system determines requirements and delivery relevance according to different criteria. If this is the case, see the requirements and delivery relevance section on planning delivery schedules.

The R/3 System contains the following settings for the requirements and delivery relevance indicator:

Blank - Delivery schedules are not used.

A - Only forecast delivery schedules are relevant for requirements planning.

B - Forecast delivery schedules and JIT delivery schedules are relevant for requirements planning and delivery.

C - Only forecast delivery schedules are relevant for requirements planning. Only JIT delivery schedules are relevant for delivery.

D - Forecast delivery schedules and JIT delivery schedules are relevant for requirements planning. Only JIT delivery schedules are relevant for delivery.

E - JIT delivery schedules are not used.

The system determines relevance for requirements as follows:

MRP indicator B or D

Up to the JIT delivery schedule horizon, the JIT delivery schedule is relevant for requirements
After the JIT delivery schedule horizon, the forecast delivery schedule is relevant for requirements

MRP indicator A or C

The JIT delivery schedule is not relevant for requirements
The forecast delivery schedule is relevant for requirements

The system determines relevance for delivery as follows:

MRP indicator A or B

Up to the JIT delivery schedule horizon, the JIT delivery schedule is relevant for delivery
After the JIT delivery schedule horizon, the forecast delivery schedule is relevant for delivery

MRP indicator C or D

Up to the JIT delivery schedule horizon, the JIT delivery schedule is relevant for delivery
Schedule lines occurring after the JIT delivery schedule horizon are not relevant for delivery

Note the following when setting requirements planning and delivery relevance:

When a schedule line in a forecast delivery schedule begins within the JIT delivery schedule horizon and ends outside of it, the horizon is reset and the forecast delivery schedule becomes relevant for requirements planning and delivery according to the planning indicator you have set.

If, for example, a JIT delivery schedule horizon ends on 04/02 and the schedule line in the forecast delivery schedule begins on 04/01, the system sets the JIT horizon back to 03/31. The forecast delivery schedule is then relevant for planning and delivery as of 04/01 for planning indicator "B", for example.

Relevance for requirements planning and delivery may change automatically when you make changes to the scheduling agreement. For example, when you move the date of the JIT delivery schedule closer to the current date, schedule lines in the forecast delivery schedule drop out of the JIT delivery schedule horizon and become relevant for delivery.

Activities

To set or view the material requirements planning indicator, choose Goto ® Header ® Sales in the scheduling agreement.