/
(Glue-2408) Standard transport

(Glue-2408) Standard transport

Owned by SNP
Aug 20, 2024
5 min read

Instructions for successful transport of SNP Glue™ objects

  1. Create a standard SAP transport on a source system SE01

  2. Collect SNP Glue™ objects to transport via transaction /DVD/GLTR

  3. Release transport with standard SAP procedure (transaction SE01)

  4. Import transport to target via standard SAP procedure (transaction STMS)

  5. Import transport via SNP Glue™ Transport Management (transaction /DVD/GLTR)

Step 1: Create a standard transport on a source system

Step 2: Collect SNP Glue™ objects to transport

  1. Go to SNP Glue™ Transport Management through the transaction /DVD/GLTR.

  2. Select the objects which you want to transport to the target system.

You can filter the objects by:

  • Package

  • User name – a user who created the object

  • Select objects by type – using this option, you'll need to specify the type of SNP Glue™ objects. The following objects (by default checked for selection) are supported: SNP Glue™ Table, Extractor, Variant, InfoProvider, Extractor 2.0 objects (including process variants), and SNP Glue™ Queues. Additionally by default unchecked: SNP Glue™ Settings and SNP Glue™ Profiles.

By clicking on the Execute button, a table with a list of filtered SNP Glue™ objects is displayed. In this table, you can select specific objects.

When the additional (SNP Glue™ Settings, SNP Glue™ Profiles) checkboxes are checked, the list of SNP Glue™ objects will be filled on the top by other objects for collection after the Execute button. These two objects are not bound to the filter and will fill the list only with the Deletion transport checkbox unchecked.

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

For adding objects to transport click Add to transport and select the Request number which you want to use.

Step 3: Release transport with standard SAP procedure (SE01)

Release the transport with the standard SAP procedure.

If the storage on the source system has a different Storage ID as on the target system or you want to use different storage on the target system, you must set up the mapping of storages. This step is necessary before the import of transport. More information can be found in the section Storage mapping functionality. 

Step 4: Import transport to target via standard SAP procedure (transaction STMS)

Step 5: Import transport via SNP Glue™ Transport Management (transaction /DVD/GLTR)

Import the transport on a target system

Go to the SNP Glue™ Transport Management, click Activate request and select the Request ID you want to import.

Confirm the popup with the Request ID of the transport.

You will receive the Advanced activation popup where you can see how the objects on the source system were collected. More information about this functionality can be found in the chapter Advanced import. If you don’t want to change anything and want to proceed with the request on how it was created, click on the OK button.

Choose execution type.

After the import of objects is done a window is displayed with logs for standard transport.

One transport can consist of both, standard objects for creation and objects for deletion. If transport is imported through SNP Glue™ TMS, transport management's logic will first delete all objects in the transport and then create new objects in this transport.

If 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. When this situation occurs, read the instructions in the chapter Changed scenarios of SNP Glue™ objects.

Transport management and logical object folders

If the user is using logical object folders in transaction /DVD/GL80, transport management will transport these folders as well.

When some object is mapped to a specific folder on a source system and this object is transported through SNP Glue™ transport management, mapping the object in a specific folder and the folder itself will be transported to the target system.

Similarly, if this object is deleted on a source system, transported with deletion transport, mapping of this object in a logical folder will also be deleted.

Transport management logic will also delete all manually created empty folders on a target system.

Mapping in logical folders is transported with objects only if logical folders have been used at least once.

You can view the transport management import logs (TMS logs) through the transaction SLG1.

Related content