Show TOC

 Fixed Pegging

Purpose

You use fixed pegging if you want to fix assignment of a stock or receipt element to a requirement. Fixed pegging is retained, even after a document change.

Using fixed pegging has the following advantages:

  • Stable confirmations

    When you use fixed pegging, the assignment of a sales order item to a receipt element remains stable. Moreover, the component assignments can be kept stable over multiple levels. In other words, components that are assigned to an order via fixed pegging cannot be consumed by other, competing orders. This means that it is easier to keep the confirmation date that you have given to your customer.

    Note Note

    If you carry out the ATP check on the basis of the fixed pegging, SAP APO can take the scope of the check and the checking horizon into account in the ATP check.

    End of the note.

  • Fixing the material flow for production planning

    Until now, dynamic pegging sometimes caused unexpected results during detailed scheduling because the assignments between the receipt and requirement elements were recalculated in every process step. Using fixed pegging, the material flow remains stable. This increases transparency and the quality of the planning result.

Implementation Considerations

Integration

The fixed pegging relationships in SAP APO are retained even after a document change in the SAP R/3 system . For example, if you have created fixed pegging relationships between a sales order and a planned order, then the pegging relationship to the sales order still exists even after the planned order has been converted into a production order.

The system copies the existing fixed pegging relationships from a preceding document (for example, a planned order) to the follow-on document (for example, a production order). This ensures that fixed pegging relationships between receipt and requirement elements are retained in production planning and during manufacturing execution, even after various document changes . SAP Note 698427 describes exactly which document changes are supported.

You can use fixed pegging with retention of fixed pegging relationships even after document changes, if you use SAP APO with an SAP R/3 system with release 4.6C or 4.70 and plug-in 2004.1.

Features

  • Automatically create or delete fixed pegging relationships

    You can use the heuristic SAP_PP_019 to create fixed pegging relationships for a single level or for multiple levels starting from the finished product. You define the parameters that control how the system proceeds when creating the fixed pegging relationships in the heuristic settings in Customizing for PP/DS.

    You delete fixed pegging relationships using the heuristic SAP_PP_011 . You can use parameters to define which fixed pegging relationships should be deleted.

    You can also integrate both heuristics into the MRP run so that the fixed pegging relationships are created automatically when the net requirements calculation is carried out.

  • Manually create or delete fixed pegging relationships

    • You can also create and delete pegging relationships manually. You can do this in the pegging overview . In the pegging overview, you can check existing fixed pegging relationships or manually create fixed pegging relationships yourself. It is also possible to assign partial quantities only and to create fixed pegging relationships for these partial quantities.

    • In the context of an order , you can also manually maintain fixed pegging relationships. You can manually fix the dynamic pegging relationships created by the system to one level or to multiple levels or delete pegging relationships that have previously been fixed.

    • On the pegging tab page in the order processing view , you can also create fixed pegging relationships by entering the pegging quantity manually.

  • Fixed Pegging and Net Requirements Calculation

    In the first step of the net requirements calculation the fixed pegging quantity is not included. Only the requirement, receipt, and stock quantities for which no fixed pegging relationships exist, are included in the net requirements calculation.

Constraints

Constraints Associated with Integration

  • Fixed pegging is not integrated into the SAP R/3 system, meaning that affected assignments in SAP R/3 between requirement and receipt elements are not created as fixed pegging in SAP APO.

    Example Example

    You carry out batch determination in SAP R/3. This assignment does not automatically lead to a fixed pegging relationship in SAP APO. For the same reason there is no integration of R/3 collective orders.

    End of the example.

  • Conversely, a fixed pegging relationship that you create in SAP APO between a requirement and a receipt element does not lead to an assignment in SAP R/3.

    Example Example

    In SAP APO, you create a fixed pegging relationship between an order reservation and a batch stock. This does not automatically lead to a batch assignment to the order reservation in SAP R/3.

    End of the example.
Functional Constraints

  • Material flow optimization

    No material flow optimization takes place when fixed pegging relationships are created or changed. This means that an assignment of the exact quantity cannot be guaranteed, for example, where equal external priorities exist.

  • Assignment of exact quantity

    Fixed pegging relationships are created or changed using the heuristic SAP_PP_019, according to the assignment strategies supplied in the standard system. These assignment strategies do not guarantee the assignment of an exact quantity of the receipt element to the requirements.

  • Quantity propagation

    If you only create fixed pegging relationships for a portion of the component requirements of in-house production orders, the quantities are not automatically adjusted for the finished product.

Constraints Associated with Processes

  • Shelf life process

    The shelf life process is not supported because the fixed pegging heuristics do not take shelf life data into account.

  • Container resources

    The fixed pegging heuristics do not take the limited capacity of a container resource into account.

    When requirements that are assigned to container resources are moved, receipts that are assigned to these requirements via fixed pegging are not automatically moved with them.

  • Continuous requirements and receipts

    A continuous material flow is not taken into account when fixed pegging relationships are created.

  • Interactive backorder processing

    Interactive backorder processing is used to manually assign a confirmed quantity to the requirements schedule line. Fixed pegging is not taken into account. For example, stocks that are assigned to a sales order via fixed pegging can be assigned to a different sales order in interactive backorder processing.

  • Backorder processing (BOP)

    When the ATP check is used on the basis of time series, the system can simultaneously, and very quickly, carry out the availability check in a mass call for a number of sales orders in backorder processing. When the ATP check is used with fixed pegging, you can also use backorder processing. However, the performance is not as good as when the ATP check on the basis of time series is used.

  • APO production backflush is not supported.

  • Consumption - comparison of planned independent requirements with customer requirements

    The fixed pegging relationship between a planned independent requirement and a receipt element is not transferred to the sales order when consumption for sales orders is carried out.

  • For further constraints, see SAP Note 704583.