Pass On Independent Requirements Information 

Use

This function passes on the sort criteria that you entered for the independent requirements to the dependent requirements that are linked to the independent requirements via fixed pegging relationships.

Passing on independent requirements information to dependent requirements makes sense in the following cases:

·        When you create fixed pegging relationships and want to create multi-level fixed pegging relationships, starting from the requirement of the finished product. You achieve this by including the heuristic in the MRP run. The system then creates a complete pegging structure starting from the independent requirement down to the lowest manufacturing level.

·        When you delete fixed pegging relationships and want to delete the pegging relationships of pegging structures on a multi-level basis, starting from an independent requirement.

Integration

·        In the case of fixed pegging relationships, the system passes on the sort criteria to the lower BOM levels according to the sort profile that you defined in the heuristic Creation of Fixed Pegging Relationships.

·        When you delete fixed pegging relationships, the system uses the special sort profile for the categories that you created and entered in the sort profile for passing on the independent requirements information.

·        If you have set the Only Unconfirmed Requirements indicator, the confirmation of a sales order is passed on to the lower BOM levels. In this case, the pegging relationships between requirements and receipt elements must not be deleted on the lower BOM levels.

Prerequisites

In the heuristic settings you have set the indicator Pass On Independent Requirements Information.

Features

Creating Fixed Pegging Relationships

If you have set the indicator, the system passes on the sort criteria that it has determined to the dependent requirements. You can define in the sort profile, for example, that the sales orders have a higher priority than the planned independent requirements. A dependent requirement caused by a planned order that is linked to a sales order by fixed pegging therefore inherits therefore the ATP category BM (for sales order). This dependent requirement has a higher priority than a dependent requirement with the category FA (for planned independent requirement) that inherited this category from a planned independent requirement that is linked to the originating planned order via fixed pegging. A dependent requirement with a higher priority is assigned to a receipt element before a dependent requirement with a lower priority.

Deleting Pegging Relationships

If you have created multi-level pegging structures for all sales orders of a finished product using the heuristic Creation of Fixed Pegging Relationships and now want to keep only the pegging structures of the confirmed sales orders, you can use this indicator together with the indicator Only Unconfirmed Requirements to define that the system deletes all fixed pegging relationships of unconfirmed sales orders on a multi-level basis.