SAP® Documentation

Single view

/GBT/R_EVENT_DI - Initial Load of GBT Events via Direct Input

Vendor Master (General Section)   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You use this program to import batch where-used records (events) into the SAP Global Batch Traceability system by direct input.

The program reads the sequential file specified as a parameter and updates the data in the events. The file must be located on the application server.

Integration

Prerequisites

The input file for this program is located on the application server at the path specified by the logical file name GBT_EVENTS.

It is a unicode ASCII file with the concatenated fields of the following structures. There is one structure per line in the file and the structures are repeated for each event.

  • /GBT/S_SESSION_DATA_DI
  • /GBT/S_EVENT_DI
  • /GBT/S_EVENT_CON_DI

Structure /GBT/S_EVENT_DI contains the initial network node, target network node, and the attributes of an event.

Structure /GBT/S_EVENT_CON_DI contains the connecting business documents of an event.

Initial network node, target network node, and connecting business documents are called network-relevant objects. Every network-relevant object has a corresponding DDIC structure with its key fields. The input file must contain the key fields in exactly the same order as specified in the corresponding key structure.

All network-relevant object types are defined in Customizing for SAP Global Batch Traceability under Definition of Object Types.

If the batch where-used records are available in a different format, it can be mapped or converted into the required structure with the Legacy System Migration Workbench (transaction LSMW).

Note

If you want to delete an event, enter value D in field ACTION_CODE of structure /GBT/S_EVENT_DI.

Features

Selection

Standard Variants

Output

Activities

Usually, you use the Legacy System Migration Workbench (transaction LSMW) with import method Direct Input and enter object type 4711 GBT Event.

Alternatively, if the sequential file with the input data is already available in the correct format and it is located on the application server, the program can be started directly.

Example

Examples of network-relevant objects are batch, outbound delivery item, and material document item.

The batch key components are defined as fields of DDIC structure /GBT/S_BAT_ITM_KEY: Material Number, Batch Number, Plant. The object type of a batch is BAT.

The key components of an outbound delivery item are defined as fields of DDIC structure /GBT/S_DLIO_KEY: delivery number, year of delivery creation, delivery item number. The object type of an outbound delivery is DIO.

The key components of a material document item are defined as fields of DDIC structure /GBT/S_MDIT_KEY: material document number, year of material document creation, material document item number. The object type of a material document item is MDI.






CPI1466 during Backup   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 3647 Date: 20200410 Time: 213422     sap01-206 ( 33 ms )

Our Service

Looking for Support? Questions?

The

Consolut

Callback-Service

Leave us your contact details and we will call you back. Panels marked with * are mandatory.