You use this heuristic to create a link between orders in SAP APO based on the collective orders in the SAP ERP system.
You can interactively invoke this heuristic from the
If you want to run the heuristic in the background, choose
.You have made the necessary heuristic settings in the activity Maintain Heuristics
in the Customizing for Production Planning and Detailed Scheduling (PP/DS). The heuristic is supplied in standard Customizing as SAP_PP_MRPDS
.
You can choose from the following settings:
Ignore Purchase Orders and Purchase Requisitions
Ignore Wait and Move Times of Production Orders
Ignore Replication of Planned Orders
Ignore Wait and Move Times of Planned Orders
You have executed an MRP run for the collective orders.
You have transferred all orders to SAP APO using CIF.
Restrictions detailed in the OSS note 698427 are applicable to this heuristic.
Since an RFC is used to read data from the SAP ERP system, the heuristic is performance-intensive.
The orders in the network formed by the collective orders is rescheduled only based on the strategy setting Consideration of Fixed Pegging Relationships
. This means the system only schedules or reschedules an object so that the availability date/time
is as punctual as possible, or at least lies before the requirements date/time.
This heuristic creates fixed pegging relationships between orders in SAP APO based on those in SAP ERP. You can execute this heuristic on a product, a planned order, or a production order, where the planned order or production order is part of a collective order. You can invoke the heuristic either interactively or in the background.
This heuristic also considers the buffer times (move time and wait time) that exist between operations of the related orders in a collective order. Each order in this collective order has its own order number.
You can set indicators to define if the heuristic must ignore buffer times for planned orders and production orders.
Note
If subassemblies are produced directly for superior orders that lie within a production process, without physically entering the warehouse, then it is useful to have collective orders.
For example, if you change the order quantity in an order, the relevant quantity changes are made in the dependent orders automatically.
On execution of the heuristic, the system carries out the following steps:
Based on the logical system, the heuristic reads collective order data from the corresponding SAP ERP system. It checks if the planned orders and production orders exist in SAP APO. If the orders exist in SAP APO, then the algorithm executes on these orders.
The heuristic creates fixed pegging relationships between the collective orders received from the SAP ERP system. The planning-related time interval of the input node (UNPLAN_OFFSET_VALUE
) is updated with the maximum wait and move times. The planning
offset (OFFSET_VALUE
) is updated with the minimum wait and move times.
Note
If buffer times are changed in SAP ERP, you must execute the heuristic again for the new buffer times to be reflected in SAP APO.
On the Detailed Scheduling Planning Board, ensure that the overall profile is SAP_MRPDS
or its copy.
On the main screen of the Detailed Scheduling Planning Board, from the Product Chart
select an order or the product that has the top order in the order network.
Execute the heuristic by choosing
. Logs are generated for successful or unsuccessful executions.The system creates fixed pegging relationships for the collective orders as shown below. When the collective orders are replicated in SAP APO using CIF, a multilevel fixed pegging relationship exists between the production order or the planned order of the preceding orders and the dependent demands.
When the heuristic is executed, the collective orders are read from SAP ERP through the RFC connection and the fixed pegging is carried out between dependent demands and the related orders.
The system replicates buffer times as shown in the figure below. The planning-related offset and planning offset values of the input node of production orders and planned orders are filled with values as shown below.