Pegging Logic: Fixed
Use
You can decide whether the assignment of replenishment elements to pegged requirements should take place based on MRP Logic using the fixing rule.
Note
Since the distribution of costs for a replenishment element is based on the results of pegging that are stored in an assignment table, all the changes in the requirements display as a result of cost transfer postings. You should check which of the logic types best suit your requirements and business processes.
Using the Fixing Rule
This rule always attempts to copy as many assignments for the replenishment element from the previous pegging run as possible. The goal is to minimize the number of cost transfer postings as a result of rescheduling or changes to the requirement quantity. Rescheduling without changing the requirement quantity does not influence the results displayed in pegging.
Activities
The system executes the following steps during the assignment:
The current requirements situation is determined during the first pegging run and the replenishment elements are distributed based on materials requirement planning (MRP) logic.
The next run checks whether historical assignments exist.
If yes, these assignments are read from the database and copied.
If no, the results based on MRP logic are copied as the result of this pegging run.
Example
Work breakdown structure (WBS) element A requires 6 units of a material and WBS element B 4 units of the same material. The assignment of the replenishment elements, in this case 2 purchase orders of 5 units each, takes place as follows:
Note
You can use a Business Add-In (BAdI) to implement your own customer-specific logic to check or adjust the assignments made by the system (for more information, see Transaction Codes/BAdIs ).
See also: