Integration of Planned Orders (Repetitive Manufacturing)
You can use this process to transfer planned order data for repetitive manufacturing between SAP ERP and SAP ME.
The planned order is an MRP request for the procurement of a particular material at a determined time. It specifies when the inward material movement should be made and the quantity of material that is expected. In case of repetitive manufacturing, the planned order is not only used for planning purposes but also for producing a particular material.
Planned orders are sent to SAP ME with Build Quantities
. Production supervisor creates SFC numbers for the actual quantity to be built. If more materials are to be built, the production supervisor creates more SFC numbers to the Repetitive
shop order. Base SAP ME functionality allows any quantity, even greater than the build quantity to be released to a Repetitive
shop order.
See the following topics:


You create a planned order for repetitive manufacturing. You can do this automatically by using the MRP run or manually, for example, in the planning table (transaction MF50
) or the transaction MD11
.
Recommendation
If you do not use DRF for distribution of planned orders, you can define a filter so that only the planned orders that you consider relevant to SAP ME are transferred (see Defining a Filter for Planned Orders
in Other Customizing Activities in SAP ERP).
If DRF is activated, the filter is maintained via the transaction DRFF
.
You schedule the order or the system schedules it automatically, based on the system configuration.
SAP ERP 6.05 with activated business function LOG_PP_MES_INT_02
distributes planned orders based on the DRF filter settings (see DRF Integration for MES Processes). Planned orders due for distribution are transferred automatically. In the other cases the system distributes the orders that become due at the current date using the report linked to transaction DRFOUT
, scheduled for daily execution.
This configuration type also supports the update scenario. Planned orders, changed manually or by planning, are redistributed to SAP ME and the corresponding Repetitive
shop orders are updated.
If DRF is not activated, you transfer the planned order using transaction POIT
.
Note
You can execute the transaction POIT
in the background with suitable selection criteria, such as every morning.
SAP ERP sends the planned order IDoc to SAP MII, where message mapping takes place. SAPMEINT sends the planned order data to SAP ME.
SAPMEINT creates (or updates) a Repetitive
shop order based on the data received from SAP ERP (see Transfer of Planned Order). The data specifies the BOM and routing (based on production version). SAPMEINT adapts this data from the previously transferred master data.
You release the shop order using Shop Order Release
(see Shop Order Release).
You start production, assemble components, and complete product.
SAP ME triggers confirmation updates to SAP ERP at the last reporting step upon a Complete
.
The system sends confirmation data to SAP MII (see Transfer of Planned Order Confirmation and Transfer of Scrap Confirmation for Planned Order).
Depending on the settings in SAPMEINT, the corresponding planned order is confirmed in SAP ERP or the cost collector is updated. The standard functions for confirmation are then carried out in SAP ERP.
Note
If DRF is activated for planned orders, the confirmation messages must relate to the original planned order rather than to the cost collector. The cost collector is updated only implicitly. This confirmation mode ensures that the planned orders in SAP ERP and the corresponding Repetitive
shop orders in SAP ME are kept consistent, even if the ERP planned orders are changed after initial distribution to SAP ME.
If the planned order is updated manually or by MRP, the updated version is distributed to SAP ME automatically.