You can transfer existing batch where-used records to SAP Global Batch Traceability (SAP GBT) before you start the delta load collection. This data of the initial load, together with other data of the collection, is relevant to build up a global batch traceability network for a specific object that you want to track in SAP GBT.
To prepare the data transfer, you must start the copying of all relevant batch where-used records to the corresponding transfer tables in SAP ERP, using report /GBTINT/R_INITIAL_LOAD.
This report copies the data to the transfer tables. In addition, the report considers further material movements of batch managed materials between locations, which are not considered in the batch where-used list (table CHVW). For more information, see SAP Note 1706299.
Note
The data copying is dependent on the Customizing settings you make for the filtering of events. For more information about filtering events, see Filter for Events by Plant.
Additional disk space for the processed IDocs during an initial transfer of master data to SAP GBT is required. To avoid sizing problems, we recommend to archive or delete the incoming IDocs quickly after their processing to free up disk space.
To collect this data, start report /GBT/R_EVENT_COLLECTOR manually or as a background job in SAP GBT. For more information about the report /GBT/R_EVENT_COLLECTOR, see Delta Load of Where-Used Data from SAP ERP.
The following figure illustrates the integration mechanisms:
Initial Load of Batch Where-Used Records
If a business object in SAP ERP is already archived, for example, deliveries, SAP GBT does not consider these archived business objects. However, SAP GBT creates the global batch traceability network anyway. To do this, SAP GBT creates non-available data objects for the already archived business objects.
Caution
You can start the initial load for the same period several times as long as the data in the original SAP ERP system is identical each time. If you, for example, archive connecting business documents for this period in between initial loads, data inconsistencies occur. You cannot repair these data inconsistencies.
For integration with SAP ERP as of release 6.0, you must have installed integration component GBTRINT.
You have made the necessary Customizing settings to integrate batch where-used records.
On the SAP Easy Access screen for SAP ERP, choose
.Enter your selection criteria for the where-used records and choose Execute. The report copies the data of the batch where-used list (table CHVW) to the transfer tables in SAP ERP. In addition, the report considers further material movements of batch managed materials between locations, which are not considered in the batch where-used list. For more information, see SAP Note 1706299.
Note
If you want to check the number of selected entries before you start the execution of the report, choose Show number of selected entries.
At the end of the executed report, the application log with the results is shown. The application log is maintained for every executed run.