Show TOC

Process documentationIntegration of Planned Orders (Repetitive Manufacturing) Locate this document in the navigation structure


You can use this process to transfer planned order data for repetitive manufacturing between SAP ERP and SAP ME.


ERP Configuration Type C

This graphic is explained in the accompanying text.

ERP Configuration Types A and B

This graphic is explained in the accompanying text.

  1. 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 Recommendation

    For ERP configuration types A and B, 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).

    For the configuration type C, the filter is maintained via the transaction DRFF.

    End of the recommendation.
  2. You schedule the order or the system schedules it automatically, based on the system configuration.

  3. SAP ERP 6.05 with activated business function LOG_PP_MES_INT_02 (configuration type C) 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.

    For ERP configuration types A and B, you transfer the planned order using transaction POIT.

    Note Note

    You can execute the transaction POIT in the background with suitable selection criteria, such as every morning.

    End of the note.

    SAP ERP sends the planned order IDoc to SAP MII, where message mapping takes place. SAPMEINT sends the planned order data to SAP ME.

  4. 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.

  5. You release the shop order using Shop Order Release (see Shop Order Release).

  6. You start production, assemble components, and complete product.

  7. 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.

  8. 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 Note

    The ERP configuration type C requires that the confirmation messages are related to the original planned order and not related 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.

    End of the note.