Show TOC

 Scheduling of Requirements Dates Locate this document in the navigation structure

Use

During scheduling, the requirement s dates of components are also determined. The requirement s date of a component is set to the order start date of the order to which the component is assigned. You find the requirements date in the component tab on the General data tab page in the Dates section.

If a component is required at a later or earlier stage, y ou can shift the requirements date. To do this, you use the Lead-time offset and Op.LdTimeOffset fields on the component tab on the General data tab page , in the Dates section.

Lead-Time Offset

If you make an entry in the Lead-time offset field , the requirements date, which is initially set to the order start date , is moved . During order scheduling, only negative values are allowed. That is, the component must be available before the scheduled start ( lead time ).

Example Example

The order start date of an order is 04.20.2000 7:00am You enter a safety time of 2 days for component ABC (2- entered in the field). The requirement date of the component is set to 04.18.2000 7:00am

End of the example.

Lead-Time Offset for an Operation

If you make an entry in the Lead-time offset field, the requirements date, which starts as the start date of the operation to which the component is assigned, is moved. Depending on the symbol that you enter: Lead-time offset (positive value): Component can be available after the start date of the operation

Lead time (negative value): Component must be available before the start date of the operation

Example Example

Component ABC is required for operation 10. The start date of operation 10 is 5.4.2000 at 9.15am. You enter a lead-time offset of 3 days. The requirements date of component ABC is set to 5.10.2000 at 09:15am, taking into account the weekend.

End of the example.

The entries in the Lead-time offset and Op.LdTimeOffset fields are transferred from the bill of material and can be changed in the order, except in the case of directly produced component s . If both values are maintained, the entry in the Op.LdTimeOffset field takes precedence. The field with the time unit is valid for both fields.