Ansicht
Dokumentation

/UIF/WRITE_TRANSPORT_ENTRIES - Write transport entries for LRep contents (support only)

rdisp/max_wprun_time - Maximum work process run time   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Purpose

This report writes transport entries for files in the layered repository (LRep). You can write a transport entry for one LRep file or transport entries for multiple LRep files. The created transport entry/entries will be of the form R3TR .

Example: R3TR LRCD 24TBB36PKEM4BZL3M23WY2E4QQ

Integration

Prerequisites

Features

Selection

If you want to write a transport entry for a single LRep file you can specify its transport object name and - type in the input fields 'Transport object name' and 'Transport object type', respectively. You also have to provide the LRep layer of the file in field 'Layer type' and the ID of a modifiable workbench or customizing request in field 'Request/Task'. In case the LRep file is located in a cross-client LRep layer (layer is VENDOR, PARTNER or CUSTOMER_BASE) in addition, the package the file is assigned to has to be filled into field 'Package'. When the original language of the LRep file differs from your logon language you have to specify the logon language in field 'Original language'. As the input fields 'Package' and 'Original language' are only relevant for cross-client layers they are only displayed when the file is in a cross-client layer. If you want to write transport entries for multiple LRep files you can provide their transport object names as a list (one transport object name per line) in a .txt file that you can specify in field 'Filepath'. The entries in fields 'Transport object type', 'Layer', 'Package' and 'Original Language' (the latter two only applicable for cross-client LRep files) are then valid for all LRep files listed in the .txt file.

Note that there are constraints/interdependencies regarding/between the possible values in fields 'Layer type', 'Transport object type' and 'Request/Task'.

In field 'Layer type' the values VENDOR, PARTNER, CUSTOMER_BASE and CUSTOMER are possible. CUSTOMER is a client-dependent layer while the other layers are cross-client.

In field 'Transport object type' the following values are allowed

-,,LRCC,,,,General LRep cross-client content

-,,LRCD,,,,General LRep client-dependent content (workbench request)

-,,LRST,,,,General LRep client-dependent content (customizing request)

-,,ADVC,,,,Cross-client app Variant

-,,ADVD,,,,Client-dependent app Variant (workbench request)

-,,ADVT,,,,Client-dependent app Variant (customizing request)

-,,CACC,,,,Cross-client CDM app configuration

-,,CACD,,,,Client-dependent CDM app configuration (workbench request)

-,,CACT,,,,Client-dependent CDM app configuration (customizing request)

-,,CCAC,,,,Cross-client ,,CDM catalog

-,,CCAD,,,,Client-dependent CDM catalog (workbench request)

-,,CCAT,,,,Client-dependent CDM catalog (customizing request)

-,,CGRC,,Cross-client CDM group

-,,CGRD,,Client dependent CDM group (workbench request)

-,,CGRT,,,,Client dependent CDM group (customizing request)

There is a dependency between the value in field 'Layer type' and the allowed value in field 'Transport object type'. If the layer in field 'Layer type' is a cross-client layer only transport object types for cross-client contents are possible values.

Example:

Value VENDOR in field 'Layer type' and value LRCC in field 'Transport object type' are an allowed combination. Not allowed is the combination VENDOR in field 'Layer type' and LRCD in field 'Transport object type'.

In addition there is a dependency between the kind of transport request (workbench/customizing) and the specified layer and transport object type

-,,for a cross-client layer/transport object type only workbench requests are allowed

-,,for a client-dependent layer for transport object types LRCD, ADVD, CACD, CCAD and CGRD only workbench requests are allowed

-,,for a client-dependent layer for transport object types LRST, ADVT, CACT, CCAT and CGRT only customizing requests are allowed

Standard Variants

Output

Activities

Example

Vendor Master (General Section)   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 4539 Date: 20240419 Time: 010140     sap01-206 ( 43 ms )