Show TOC

Process documentationSAP ME Configuration for SAP ME ERP Integration

 

You can use this process to configure SAP ME to communicate with SAP ERP.

Prerequisites

You have executed the SAPMEINTCTC configuration wizard tasks.

Process

  1. You verify that the following is configured in SAP ME:

    • Site that matches an existing SAP ERP plant (see Site Maintenance)

    • MESYS user assigned to the SYSTEM user group (see User Maintenance)

    • The following system rule settings (see System Rule Maintenance)

      • Specific BOM Component Version Required set to false

      • ERP Integration Active set to true

      • Track Production set to true

      • Track Resource Time set to Yes - Track Idle Time

    • The following system properties (see System Setup Maintenance)

      • erp.basicAuth.user set to MESYS

      • erp.basicAuth.password set to <MESYS password>

      • erp.mii.webClient.poolSize set to 50

    • The following custom data fields, values for which are populated when IDocs come from SAP ERP and the corresponding SAPMEINT messages are sent from SAP MII to SAP ME (see Custom Data Maintenance)

      Custom Data Category

      Custom Data Field

      Comment

      BOM

      ERP_MATERIAL

      Routing Step (Operation)

      • CONTROL_KEY

      Routing

      • ERP_MATERIAL

      • ERP_VALIDITY_FROM

      • ERP_VALIDITY_TO

      • ERP_LOT_SIZE_FROM

      • ERP_LOT_SIZE_TO

      Reason Code

      COST_CENTER

      The operator must enter value for this custom data field for the reason code starting with RTN- or SCR- to clear the floor stock reservations in SAP ERP.

    • Collaboration links and directives (see Configuring SAP ME Outbound Collaboration)

  2. In Activity Maintenance, you retrieve Pack/Unpack (PK020) and set values for the following integration-related activity rules to send container close confirmations to SAP ERP (see Transfer of Production Yield Confirmation):

    • ERP_ITEM_FILTER

    • ERP_OPERATION

    • ERP_REPORTING_STEP

    • ERP_SEQUENCE

    For more information about these activity rules, see Pack/Unpack.

  3. You create and configure data type for floor stock integration as follows:

    1. In Data Field Definition Maintenance, you create the following data fields:

      • CENTRAL_STORAGE_LOCATION

      • BATCH_NUMBER (necessary for batch-managed materials)

    2. You deploy SAP ME and perform an initial load. This automatically creates an ERP_INV_RCPT_DATA data type of the Assembly category and assigns the following data fields to it:

      • CENTRAL_STORAGE_LOCATION

      • BATCH_NUMBER

      • VENDOR_LOT

      • VENDOR_DATE_CODE

      • VENDOR

      • MAT_DOC_YEAR

      • MAT_DOC_NUM

      • LINE_NUM

    3. You add ERP_INV_RCPT_DATA as Data to Collect on Floor Stock Receipt on the Build tab page of Material Maintenance for inventory IDs initially received in SAP ME via the floor stock IDoc.

      Note Note

      Make sure that VENDOR, which is coming along with INVCON02 IDoc, exists in SAP ME, before transferring the INVCON02 IDoc to SAP ME. This vendor must be configured in SAP ME to receive and consume the material for which the inventory is received.

      End of the note.

    For more information, see Transfer of Floor Stock Data.

  4. In Reason Code Maintenance, you create reason codes for clearing floor stock reservations.

    The reason codes must begin with the following prefixes to trigger the collaboration event COLLABORATION_ERP_INV_CLEAR_RESERVATION:

    • RTN-

      used for return to floor stock

    • SCR-

      used for scrap

    For more information, see Transfer of Floor Stock Return and Scrap Data.

More Information

Configuration of SAPMEINT Standard Interfaces

Setting Up the System