Show TOC

Background documentationIntegration with Non-SAP ERP Systems Locate this document in the navigation structure

 

Besides an SAP ERP system, you can also connect other systems to transfer where-used data and master data.

Note Note

The integration of organizational data from non-SAP systems is not supported.

End of the note.

The following figure gives you an overview of the integration of where-used data and master data:

This graphic is explained in the accompanying text.

Integration of Where-Used Data and Master Data

Integration of Where-Used Data

You have the following options to transfer where-used data from non-SAP ERP systems to SAP Global Batch Traceability (SAP GBT):

  • Using the enterprise service TrackedGoodsRelationNotification_In

    For more information, see Enterprise Service.

    Note Note

    Optionally, you can use SAP Manufacturing Integration and Intelligence (SAP MII) or SAP NetWeaver Process Integration (SAP NetWeaver PI) to transfer where-used data from non-SAP ERP systems.

    If you want to create your own SAP GBT objects, you can also use this enterprise service to create the events that is the relationships between standard SAP GBT objects and your own objects.

    End of the note.
  • Using a file import via the SAP Legacy System Migration Workbench

    You can send data by e-mail and import it directly with an ASCII file using the SAP Legacy System Migration Workbench. For the file import, you can use report /GBT/R_EVENT_DI. The program reads the sequential file specified as a parameter, and updates the data in the events. You must save the file on the application server.

    For more information, see the report documentation for report /GBT/R_EVENT_DI.

    To start SAP Legacy System Migration Workbench, use transaction LSMW.

Integration of Master Data

You can use SAP Legacy System Migration Workbench to support master data migration from non-SAP ERP systems to SAP GBT. SAP Legacy System Migration Workbench facilitates the conversion of data to the necessary format. You can use transaction LSMW to start SAP Legacy System Migration Workbench.

Note Note

If you use SAP Legacy System Migration Workbench, you can only transfer master data from non-SAP ERP systems for which inbound IDoc function modules exist in SAP GBT, for example, a function module for inbound IDoc BATMAS.

End of the note.
Integration of Organizational Data

The integration of organizational data from non-SAP ERP systems to SAP GBT is not supported.

Implementation Considerations

Implementation Considerations to Integrate Where-Used Data
  • You have to enable the enterprise service, and install the service-oriented architecture (SOA). For more information, see the master guide for SAP GBT under Service Enablement and Installation of the Service-Oriented Architecture (SOA).

    Note Note

    With the enterprise service, you can only create the batch where-used relationships (the key information) in SAP GBT without any further details of the object information, for example, the material description.

    End of the note.
  • You can monitor the enterprise service using transaction code SXMB_MONI.

Implementation Considerations to Integrate Master Data
  • Depending on the format used by the non-SAP ERP system to export master data, you have to adjust the settings in SAP Legacy System Migration Workbench.

    For more information about SAP Legacy System Migration Workbench, look for Legacy System Migration Workbench in the documentation of SAP NetWeaver at   http://help.sap.com/nw703   Application Help   Function-Oriented View   English  .

  • For master data objects where IDoc Inbound is available on SAP GBT, you can use SAP Legacy System Migration Workbench to import master data from non-SAP ERP systems. You must import these data sets in file format. You can either import them to the application server where SAP GBT is running, or directly upload the data sets manually.