Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS-ORG (Application Component) Transport Organizer⤷
SCTS_TRA (Package) CTS: Transport Control & System Configuration
Basic Data
| Data Element | TR_TARGET |
| Short Description | Transport Target of Request |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TR_TARGET | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table |
Further Characteristics
| Search Help: Name | TCE_TRANSPORT_TARGET | |
| Search Help: Parameters | TR_TARGET | |
| Parameter ID | ||
| Default Component name | TRANSPORTZIEL | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Target |
| Medium | 20 | Transport Target |
| Long | 30 | Transport Target |
| Heading | 30 | Transport Target |
Documentation
Definition
The transport target specifies where a transport request is imported.
Use
There are three ways to define transport targets. They differ in syntax and function.
Syntax Example Explanation
1. <SYS> C11 Target system
2. <SYS>.<CLI> C11.021 Target system and client
3. /<Group name>/ /EUROPE/ Target group
The second and third options can only be used when extended transport control has been activated.
For transport targets without a specified target client (first option), the client into which the client-specific objects are to be imported is only determined at the time of import by the system administrator.
However, if the target client is already defined in the transport target, the system administrator no longer has to make this decision.
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 20070418 |
| SAP Release Created in |
