Integrating Master Data and Organizational Data from SAP ERP

You can transfer relevant master data using IDocs. For example, you can transfer the batch master with the batch classification data or the debitor master.

You can transfer relevant organizational data via remote function call (RFC). For more information about address data, see Processing of Address Data.

Prerequisites

Prerequisites to Integrate Master Data

You have made all settings to set up the Application Link Enabling (ALE) distribution. For more information, see Customizing for SAP GBT under General Settings.
You have defined the mapping for the IDoc types. For more information, see Customizing for SAP GBT under General Settings or Mapping of IDoc Types.
If you use batch classification in SAP ERP, transfer the corresponding batch class definitions and their class characteristic definitions to SAP GBT. For more information, see Integrating Batch Classes and Characteristics from SAP ERP.

Consider further prerequisites:

Data	Description	Information about the Maintenance in Customizing for SAP ERP
Unit of Measure (UoM)	Make sure that the Customizing of the UoM is synchronized between SAP GBT and the connected SAP ERP system. To check the synchronization, you can use transaction code `SCU0`. The UoM is transferred via the ISO code. If you have not defined an ISO code for the UoM in Customizing for SAP ERP, the internal SAP code is transferred. If you have not defined the UoM in Customizing for SAP ERP, the material master cannot be transferred to SAP GBT.	SAP NetWeaver General Settings Check Units of Measurement
Currency	Make sure that the Customizing of the currency is synchronized between SAP GBT and the connected SAP ERP system. To check the synchronization, you can use transaction code `SCU0`.	SAP NetWeaver General Settings Currencies
Country	Make sure that the Customizing of the country is synchronized between SAP GBT and the connected SAP ERP system. To check the synchronization, you can use transaction code `SCU0`.	SAP NetWeaver General Settings Set Countries Specify Countries in mySAP Systems (CRM, SRM, SCM,..)

Data

Description

Information about the Maintenance in Customizing for SAP ERP

Unit of Measure (UoM)

Make sure that the Customizing of the UoM is synchronized between SAP GBT and the connected SAP ERP system. To check the synchronization, you can use transaction code SCU0.

The UoM is transferred via the ISO code. If you have not defined an ISO code for the UoM in Customizing for SAP ERP, the internal SAP code is transferred.

If you have not defined the UoM in Customizing for SAP ERP, the material master cannot be transferred to SAP GBT.

SAP NetWeaver General Settings Check Units of Measurement

Currency

Make sure that the Customizing of the currency is synchronized between SAP GBT and the connected SAP ERP system. To check the synchronization, you can use transaction code SCU0.

SAP NetWeaver General Settings Currencies

Country

Make sure that the Customizing of the country is synchronized between SAP GBT and the connected SAP ERP system. To check the synchronization, you can use transaction code SCU0.

SAP NetWeaver General Settings Set Countries Specify Countries in mySAP Systems (CRM, SRM, SCM,..)

Note Note

While UoM is widely used, currencies may only occur as costing characteristics in batch classification.

End of the note.

If you want to use your own product hierarchy and product category, create them in SAP GBT. For more information, see Maintain Product Without Customizing Transfer from Back-End Systems
If you need product categories in SAP GBT, for example, the SAP ERP material type, you can set up the product categories in SAP GBT. For more information, see Product Category.

Prerequisites to Integrate Organizational Data

To determine which where-used data SAP ERP should transfer to SAP GBT, you have maintained the SAP GBT relevant plants. On the SAP Easy Access screen, choose Cross-Application Components SAP Global Batch Traceability Data Collection in SAP ERP Specify Filter for Events .

Integration

Integrating Master Data and Organizational Data

You can integrate master data or organizational data from SAP ERP with SAP Global Batch Traceability (SAP GBT) in the following way:

To integrate master data, you can use IDocs and transfer them using Application Link Enabling (ALE).

To prepare the master data transfer, maintain the respective IDoc types and message types in SAP ERP. This master data is transferred via ALE to the IDoc inbound interface in SAP GBT.

You can transfer the changed master data using change pointers. For more information, look for Change Pointer (Master Data Distribution) in the documentation of SAP NetWeaver at http://help.sap.com/nw703 Application Help Function-Oriented View English .
To integrate the organizational data plant master, you transfer it using report /GBT/R_ERP_PLANT_RETRIEVE. To transfer the plants from SAP ERP to the business partner in SAP GBT, start the report on the SAP Easy Access screen. Choose Cross-Application Components SAP Global Batch Traceability Data Collection in SAP ERP Retrieve Plant Master . Enter a logical system and choose Execute. SAP GBT retrieves the plant master from SAP ERP.

The following figure illustrates this integration mechanism:

This graphic is explained in the accompanying text.

Integrating Master Data and Organizational Data

Integrating Customer Data, Vendor Data, and Plant Data

You can transfer customer data or vendor data, for example, the name and the address, and plant data from SAP ERP to SAP GBT. This transfer ensures that important information, for example, the customer address, is locally available in SAP GBT without a further lookup in SAP ERP. SAP GBT maps the SAP ERP customer number, vendor number, and plant number to a business partner number. The business partner number is independent from the SAP ERP number and only used internally. That is because the numbers in SAP ERP for the different objects can be the same. For example, one customer and one vendor can have the same number in SAP ERP. In this case, the number is not a unique number and cannot be used for two business partner instances in SAP GBT. Within SAP GBT, the SAP ERP numbers are used for display purposes in reports, for example, in the distribution list. The business partner data provides further information, for example, the name or address.

Note Note

Instead of the internal business partner number, SAP GBT displays the customer number, vendor number, or plant number that was transferred from SAP ERP.

End of the note.

The mapping of the SAP ERP numbers to the business partner numbers is stored within the key mapping of SAP Master Data Governance. For more information about the key mapping in SAP Master Data Governance, see SAP Library for SAP ERP Central Component on SAP Help Portal at http://help.sap.com/erp606 SAP ERP SAP ERP Cross-Application Functions Cross-Application Components Master Data Governance Working with Master Data Governance General Functions Key Mapping . The key mapping is automatically created by the integration.

Features

The following table lists the standard SAP ERP IDocs, and message types that SAP GBT uses to import master data from SAP ERP.

IDoc Description (in SAP GBT)	Maintenance in SAP ERP	Message Type in SAP ERP	IDoc Type in SAP ERP	IDoc Type in SAP GBT
Import of batch master data	Enter transaction code `BD21`. Optionally, you can distribute batch master data with report `/GBTINT/R_SEND_BATMAS`. In SAP ERP on the SAP Easy Access screen, choose Logistics Central Functions Global Batch Traceability Interface Send Batches .	`BATMAS`	`BATMAS03`	`/GBT/BATMAS03`
Import material master data You can influence the integration using `BAdI /GBT/EX_IL_MATMAS`. For more information, see the BAdI documentation.	On the SAP Easy Access screen, choose Tools ALE ALE Master Data Administration Cross-Application Material Send (alternatively enter transaction code `BD10`).	`MATMAS`	`MATMAS05`	`/GBT/MATMAS05`
Import creditor master data used as vendor in SAP GB	On the SAP Easy Access screen, choose Tools ALE ALE Master Data Administration Cross-Application Vendor Send (alternatively enter transaction code `BD14`).	`CREMAS`	`CREMAS05`	`/GBT/CREMAS05`
Import debitor master data	On the SAP Easy Access screen, choose Tools ALE ALE Master Data Administration Cross-Application Customer Send (alternatively enter transaction code `BD12`).	`DEBMAS`	`DEBMAS06`	`/GBT/DEBMAS06`
Import of address data of business partner	Enter transaction code `BD21`.	`ADRMAS`	`ADRMAS03`	`/GBT/ADRMAS`

The following table gives you an overview of where to maintain, in SAP ERP, the SAP ERP IDocs, and message types that SAP GBT uses to import classification data from SAP ERP.

Type of Master Data	Path in SAP ERP: On the SAP Easy access screen, choose the following:	Message Type in SAP ERP and SAP GBT	IDoc Type in SAP ERP
Characteristics	Logistics Logistics Execution Transportation Transportation Planning External Planning System ALE Monitoring Go To Master Data Distribution Logistics Classification System Characteristic Send (alternatively enter transaction code `BD91`)	`CHRMAS`	`CHRMAS01`
Classes	Logistics Logistics Execution Transportation Transportation Planning External Planning System ALE Monitoring Go To Master Data Distribution Logistics Classification System Class Send (alternatively enter transaction code `BD92`)	`CLSMAS`	`CLSMAS01`
Classification	You can send the classification to SAP GBT in the following ways: You have implemented Business Add-In (BAdI) `VBW_BATCH_REPLICATE` (Replication of Batches). Then the classification is automatically sent together with the batch master data, using IDoc `BATMAS`. You send the classification separately from the batch master data. On the SAP Easy Access screen, choose Logistics Logistics Execution Transportation Transportation Planning External Planning System ALE Monitoring Go To Master Data Distribution Logistics Classification System Classification Send (alternatively enter transaction code `BD93`). Selecting all classifications of a class also includes the classified batch material in SAP ERP. This classification is ignored in the IDoc for the inbound process since the IDoc processing displays status 53 (Application document posted).

Type of Master Data

Path in SAP ERP:

On the SAP Easy access screen, choose the following:

Message Type in SAP ERP and SAP GBT

IDoc Type in SAP ERP

Characteristics

Logistics Logistics Execution Transportation Transportation Planning External Planning System ALE Monitoring Go To Master Data Distribution Logistics Classification System Characteristic Send (alternatively enter transaction code BD91)

CHRMAS

CHRMAS01

Classes

Logistics Logistics Execution Transportation Transportation Planning External Planning System ALE Monitoring Go To Master Data Distribution Logistics Classification System Class Send (alternatively enter transaction code BD92)

CLSMAS

CLSMAS01

Classification

You can send the classification to SAP GBT in the following ways:

You have implemented Business Add-In (BAdI) VBW_BATCH_REPLICATE (Replication of Batches). Then the classification is automatically sent together with the batch master data, using IDoc BATMAS.
You send the classification separately from the batch master data. On the SAP Easy Access screen, choose Logistics Logistics Execution Transportation Transportation Planning External Planning System ALE Monitoring Go To Master Data Distribution Logistics Classification System Classification Send (alternatively enter transaction code BD93).
Selecting all classifications of a class also includes the classified batch material in SAP ERP. This classification is ignored in the IDoc for the inbound process since the IDoc processing displays status 53 (Application document posted).

Activities

Compare the Customizing Using the Customizing Cross Viewer

For more information, see Compare Customizing Using the Customizing Cross Viewer.