All objects created with Datavard Glue can be transported between SAP systems using the Glue Transport Management (Glue TM) and the SAP Transport Management System (STMS).

Transaction:

/DVD/GLTR

With the help of the Glue Transport Management, you can select Glue objects which you want to transport. After that, the Glue TM relies on the standard STMS transports. The SAP transport contains the complete definition of transported Glue meta-objects together with the standard SAP classes and reports necessary for a Glue meta-object (for example an ABAP Extractor). All these SAP objects with the definition of Glue meta-objects help us to recreate the Glue object on the target system.

You can also use Glue Transport Management for the following scenarios:

Transport new objects to a target system.
Delete objects on the target system.
Transport changed, existing objects on the target system. For more information about supported change operations, see Change Scenarios of Glue Objects.

Transport objects to a target system

To transport Glue objects from a source system to a target system, you should create a standard transport and then import it in the target system.

Instructions

Step 1: Create a standard transport on a source system

Go to Glue Transport Management through the transaction /DVD/GLTR.
Select objects which you want to transport to the target system.

You can filter the objects by:

Package
User name – user who created the object
Select objects by type – using this option, you'll need to specify the type of Glue objects. Following objects are supported: Glue Table, InfoProvider, Extractor, Variant, Script and Glue Business Objects.

3. Click Execute.

4. Table with a list of filtered Glue objects is displayed. In this table, you can select specific objects.

Variants and extractors that are part of the package without an assigned transport layer (e.g. $TMP package), cannot be added to a transport.

5. Click Add to transport and select the Request number which you want to use.

6. Release the transport with the standard SAP procedure.

In the case the storage on the source system has a different Storage ID as on the target system or you want to use a different storage on the target system, you must set up the mapping of storages. This step is necessary before the import of the transport. For more information, see Transport Management#Storage mapping functionality.

Step 2: Import the standard transport on a target system

Import the transport through the standard STMS transaction.
Go to the Glue Transport Management, click Import request and select the Request ID you want to import.
If a transport contains an object, which already exists on the target system, it will be either replaced by the imported object or the transport of this object will fail. For more information, when this situation occurs, please see Transport Management#Transport changed objects to the target system.
You can view the import logs through the transaction SLG1, Object '/DVD/GL'and Subobject '/DVD/TMS'.

Delete objects on the target system

You may use the deletion transport to choose Glue objects which were already deleted on the source system and delete them on the target system.

Instructions

Step 1: Create a deletion transport

Go to the Glue Transport Management through the transaction /DVD/GLTR.
Mark the Deletion transport checkbox.
1. You may also add not deleted objects to the deletion transport by marking List also saved objects.
Select objects which you want to delete on the target system.
You can filter the objects by:
- User name – user who deleted the object on the source system.
- Select objects by type – using this option you'll specify the type of Glue objects. Following objects are supported: Glue Table, InfoProvider, Extractor, Variant, Script and Glue Business Objects.
1
3. Click Execute.
4. Table with a list of filtered Glue objects is displayed. In this table, you can select specific objects.
Variants and extractors that are part of the package without an assigned transport layer (e.g. $TMP package), cannot be added to a transport.
5. Click Add to transport and select the Request number which you want to use.
6. Release the transport with the standard SAP procedure.

Step 2: Import the deletion transport on a target system

Import the deletion transport through the standard STMS transaction.
Go to the Glue Transport Management, click Import request and select the Request ID you want to import.

You can view the import logs through the transaction SLG1, Object '/DVD/GL' and Subobject '/DVD/TMS'.

When you import a deletion transport, all the Glue objects in the transport are deleted by the standard Glue procedures.

This means that if you delete for example a Glue table, all Glue objects related to this table are also deleted (all extractors, variants, etc.).

Transport changed objects to the target system

Depending on the changes you performed on the source object (please see Change Scenarios of Glue Objects), you should either use a standard transport or a deletion transport to transport the updated object to the target system.

If you performed changes on the Glue object with a green status in the chapter Change Scenarios of Glue Objects, you should use the standard transport for updating the object on the target system.
In this case proceed as described in Transport Management#Transport changed objects to the target system.

In the case you alter an Glue object in a way that is marked red in the chapter Change Scenarios of Glue Objects and transport it with a standard transport, the transport of this Glue object will fail.

If you performed changes on the object with a red status in the chapter Change Scenarios of Glue Objects, you have two options how to transport the changed object to another system.

We recommend to use the first option, as you may transport changes from a source system to a target system without deleting the Glue object on the source system. During this option, delete the Glue object on the target system first and then import the changed Glue object from the source to the target system.

The first option consists of these steps:

Change the Glue object on the source system.
Create a deletion transport for the Glue object you want to delete on the target system. To perform this:
1. Go to the Glue Transport Management through the transaction /DVD/GLTR and mark the Deletion transport checkbox.
  1. To add saved objects (not deleted Glue objects) to the deletion transport mark List also saved objects.
2. The next steps are the same as in the section Delete objects on the target system, starting from point 3 and ending with point 6.
  In this case you shouldn't import the deletion transport.
Create and import the standard transport with the same Request number for the changed Glue object. Proceed as described in Transport Management#Transport changed objects to the target system.
Imported transport includes both the standard and the deletion transport.

The second option consists of these steps:

Delete the Glue object on the source system.
Create and import a deletion transport for this object, as described above in Transport Management#Delete objects on the target system.
Create newly changed Glue object on the source system.
Transport newly changed Glue object through a standard transport as described in Transport Management#Transport changed objects to the target system.

Storage mapping functionality

Storage mapping functionality enables you to set up the storage of a transported Glue table on the target system.

You may use this functionality, if:

The storage on the source system has a different Storage ID as on the target system.
You want to use a different storage on the target system.

For more information about external storage of Glue table, see the section Storage.

To set up the storage mapping:

Go to Table Maintenance through the transaction /DVD/RL_TM. For more information about this topic, see the chapter Datavard Table Maintenance.
Enter the table /DVD/GL_TR_STR_M.
Execute two times.
Click New entry to add a record in the table /DVD/GL_TR_STR_M on the target system.
- In Source storage specify the name of the storage on the source system
- In Target storage specify the name of the storage on the target system
Execute.

For example, if the storage ID in Source storage is H_CNN_MSI and the storage ID in Target storage is H_CNN_MSH, then each Glue table in the transport with the storage ID H_CNN_MSI on a source system, will use the storage ID H_CNN_MSH on a target system.

Glue TM cleanup

Cleanup redundant metadata

When you create a transport on the source system, Glue metadata in a form of a table content is created. After the release of the transport request, this metadata is redundant and you may manually delete it.

To delete these metadata use following steps:

Go to Glue Transport Management through the transaction /DVD/GLTR.
Select Glue STMS released (F7) in the Tool menu of the screen toolbar.

Cleanup all metadata

When you transport a request with inconsistent metadata to the target system, by trying any not supported actions (see Change Scenarios of Glue Objects) by Glue TMS, you can delete all metadata on the system. This will remove Glue TMS metadata for all non-transported or non-deleted Glue objects.

To delete all metadata use the following steps:

Go to Glue Transport Management through the transaction /DVD/GLTR.
Select Cleanup all in the Tool menu of the screen toolbar.

Browser not supported