Show TOC

Process documentationSAP ME Configuration for SAP ME ERP Integration Locate this document in the navigation structure

 

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

Prerequisites

You have executed the SAPMEINTCTC configuration wizard.

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 rules (see System Rule Maintenance)

      • Specific BOM Component Version Required set to false t

      • ERP Integration Active set to true

      • Track Production set to true

      • Track Resource Time set to Yes - Track Idle Time

    • erp.basicAuth.user and erp.basicAuth.password system properties (see System Setup Maintenance)

    • 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

      Material

      STORAGE_LOCATION

      BOM

      • ERP_MATERIAL

      • ERP_BOM

      Routing Step (Operation)

      • SEQUENCE

      • CONTROL_KEY

      • IS_LAST_REPORTING_STEP

      Resource

      • PLANT_MAINTENANCE_ORDER

      • EQUIPMENT_NUMBER

      • MEASUREMENT_POINT

      Tool Number

      • PLANT_MAINTENANCE_ORDER

      • EQUIPMENT_NUMBER

      • MEASUREMENT_POINT

      The operator must enter correct values for EQUIPMENT_NUMBER and MEASUREMENT_POINT for the tool to report the tool’s status change to SAP ERP.

      Shop Order

      • PRODUCTION_VERSION

      • ERP_UOM

      User

      ERP_USER

      NC Code

      • ERP_CATALOGUE_TYPE

      • ERP_CODE_GROUP

      • ERP_QN_CODE

      The operator must enter the correct values for these custom data fields when an NC code is created.

      Reason Code

      • CENTRAL_STR_LOC

      • COST_CENTER

      The operator must enter value for these custom fields for the reason code starting with RTN- or SCR- to clear the inventory 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:

    • ERP_ITEM_FILTER

    • ERP_OPERATION

    • ERP_REPORTING_STEP

    • ERP_SEQUENCE

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

  3. You configure data types for inventory integration as follows:

    In Data Type Maintenance, you create the following data types for the Assembly category:

    • FLOOR_STR_LOC

    • BATCH_NUMBER

    Then you add the following data types as Data to Collect on Inventory Receipt on the Build tab page of Material Maintenance for inventory IDs initially received in SAP ME via the inventory IDoc:

    • FLOOR_STR_LOC

    • BATCH_NUMBER

    • VENDOR_LOT

    • VENDOR_DATE_CODE

    • VENDOR

    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 Inventory Data

  4. In Reason Code Maintenance, you create reason codes for clearing inventory 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 inventory

    • SCR-

      used for scrap

    For more information, see Transfer of Inventory Return and Component Scrap Data.

  5. You may also need to configure .xslt mapping files for SAPMEINT messages in XSLT Maintenance (see XSLT Maintenance)

More Information

Configuration of Standard SAPMEINT Interfaces

Setting Up the System