Pegging (SAP Library - SAP Advanced Planner and Optimizer (SAP APO))

Pegging

Use

Pegging is used during planning to assign product receipts, which should cover the requirement, to a product requirement. Pegging links the requirements elements and receipt elements through all BOM levels, that is, it organizes the material flow, from the procurement of components and raw materials to delivery of a sales order, for example. Orders that are linked together, and their pegging relationships, form a Pegging Structure. The graphic below gives an example of a pegging structure. The arrows represent the material flow, that is, the pegging relationships.

A production order, which requires a specific component can, for example, be pegged to a purchase requisition for the component (external procurement) or to a production order for the component (in-house production). With an in-house production order, the component is the output product of a specific activity. The availability date of the component is determined by the activity date. Thus, the activity dates are also relevant for a pegging relationship to an in-house production order.

The following pegging procedures are available:

Dynamic Pegging is carried out automatically by the system when planning, if the requirements or receipts situation changes. With dynamic pegging, the system deletes existing pegging relationships and creates new ones. Thus, with dynamic pegging, the assignment of a receipt element to a requirement element is generally not retained for long if the planning changes.

Fixed Pegging is used if you wish to fix the assignment of a receipt element to a requirements element and if the system should not change this assignment during automatic planning. Fixed pegging relationships are retained during planning and can only be deleted manually.

Features

Pegging Area

Pegging can only link requirements elements and receipt elements within a pegging area, that is, requirements elements and receipt elements must

consume or deliver the same product (with the same characteristics)
be in the same location
be planned in the same planning version
have the same account assignment
be in the same planning section

Alerts

In connection with pegging, quantity problems (uncovered requirements, surplus receipts) and date problems (receipts too early or too late) may occur during planning. The system can create alerts for these problems and display the alerts in the planning interface or in the Alert Monitor. For more information, see Display of Alerts.

Displaying Pegging Information

You can display pegging information in the order processing view. For more information, see Display pegging information

Considering pegging relationships in detailed scheduling

The system can consider pegging relationships in Detailed scheduling, that is, it can carry out scheduling or rescheduling of objects (orders, operations, activities) such that pegging relationships are taken into consideration and requirements dates are not violated. This can mean that a date change is automatically transferred to dependent objects. You can determine if and how the system should consider pegging relationships in the Detailed scheduling strategy. For more information, see considering pegging relationships