Computation type (Pegging setting)

Set the summary requirement based on time: day, week, month. This function allows compression of the data and reduction in the calculation effort.

See Computation time

Detail

All pegging (forecast, order, customer order, etc.) is displayed separately. This setting makes sense, if purchases are issued ordered related or if it is goods of high value.

Day/week/month/sum

The peggings are summarized corresponding to chosen the time period.

This is recommended, if no detailed declaration of the pegging or resource is necessary and one has to deal with high amounts of data. The calculation time is shortened, and the view is clearer. This setting can also be defined in the item master data.

In Item master this setting can be applied. Higher summary level always has priority.

See Item master - Planning.

Resource scheduling (MRP2) is based on lead time calculation. Therefore  "Calculate lead time for assembly" must be activated if resource scheduling is required.

If enabled, lead time is calculated using the integrated capacity planning tool based on the routing production times defined.

The calculation is carried out by means of backward scheduling simulation. Existing capacities are not taken into account. If a material is assigned to an operation sequence directly, then the start date of the operation sequence is assigned (time: start of processing).

Depending on the depth of the production structure and the accuracy of the forecast, the computation can by time consuming.

If disabled the item lead time and the lead time defined in the Configuration Wizard serves as a reference. The calculation time is significantly shortened. The "Resources - Activate resource planning function is disabled.

Note: Lead time means production time of the assembly without consideration of  sub-assemblies lead times.

Example

Example: Here is the item structure:

Assembly A (Lead time = 10 work days)

 Assembly B (Lead time = 5 work days)

The date of finished production A and B is the requirement date

Start date A: Requirement date – Lead time A (10 days)

Start date B: Start date A – Lead time B (5 days)

See: calculate resources

Sales documents

If this feature is active, calculate the requirement date for sales documents.  Links between operation sequence and bill of material are considered. It is enabled by default.

If this option is disabled, the links are not considered, which means that the calculated manufacturing start date is always used as the requirement date for the bill of material items. By disabling this option, the calculation will take less time.

Production

Iif this option is enabled, the start date of the operation is used for calculating the requirement date of the bill of material items. Otherwise, the start date of the work order position is used. If this option is disabled, the delivery date is used.

See Computation of order recommendation date

Only visible if Calculate lead time for assemblies has been deactivated.

This computes e.g. the complete material requirements and complete resource requirement in advance.

The necessary resources (material and tools) are calculated based on the  the production lot size and stored accumulated. This calculation type is much faster than the Calculate lead time for assembly option andit provides a good estimate.

•Check box active: Group requirements by versions (all batches/serials item managed by versions are then split to display the real requirement for each version).
 

•Check box empty: Display the the whole item requirement ignoring any version.

By default, this parameter is disabled (i.e. not grouping the requirements by version).

NOTE: If a batch/series managed Item has information in the I-Version field, but there is no existing I-Version, this field is used as information, and the MRP is going to consider this item as a non-version managed item.

Therefore, if the flag "Consider I-Version" is enabled in the MRP Scenario, this MRP Scenario is not going to be able to show any requirement for this Item. To see the requirements, you should execute an MRP Scenario with this flag disabled.