All peggings (forecast, order, customer order, etc.) are displayed separately. This setting makes sense if purchases are issued as order-related or it has goods of high value.
Purchase order for several instances of the same Item with different delivery dates is supported. The items therefore appear in several lines in Order recommendation.
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.
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 defined routing production times.
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.
ATTENTION: In case of sub-assemblies, the parameter only affects lead time calculation of order-related sub-assemblies used as WO BoM! For storage-related sub-assemblies, the system uses fix lead time defined in Item master data.
Example - Assembly with order-related sub-assembly:
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)
If this feature is enabled, calculate the requirement date for sales documents. Links between operation sequence and bill of material are considered. It is enabled by default.
If 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 materials items. By disabling this option, the calculation takes less time.
Production
If this option is enabled, the start date of the operation is used for calculating the requirement date of the Bill of materials items. Otherwise, the start date of the work order position is used. If this option is disabled, the delivery date is used.
Only visible if "Calculate lead timefor 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 gradually faster than the "Calculate lead timefor assemblies" option and it 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/serial-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 display any requirement for this Item. To see the requirements, you should execute an MRP Scenario with this flag disabled.
Non-batch/serial managed items with item version are not supported. If this type of item has item version with separate Bill of Materials, the MRP calculation result will be incorrect. For more information seeDataCheck.
- By Documents: Cover the demand of the coverage calculation by documents.
Priority for coverage calculation is defined in requirement coverage calculation.
Priority of documents:1. WO, 2. Sales Documents, 3. Forecast.
- By Date: Cover the demand of coverage calculation by date.
Documents affected for this parameter in coverage calculation: 1. WO, 2. Sales orders and Precalculations, 3. User table. NOTE: The "By Date" parameter does not consider Forecasts in the calculation.
