Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS-ORG (Application Component) Transport Organizer⤷
SCTS_REQ (Package) CTS: Request Editing
Basic Data
| Data Element | TRTARCLI |
| Short Description | Target Client for the Request |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR3 | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 0 | |
| Medium | 15 | Target client |
| Long | 15 | Target client |
| Heading | 0 |
Documentation
Definition
Client in the target system into which all client-specific objects in the request are to be imported.
Use
In the request-specific tables, this field is not filled until the import is performed. The respective field is therefore only filled in the target system.
You can define the target client when you maintain the transport route configuration, and by doing this, guarantee that the transports are always imported into the correct client.
If you do not specify the client when you define the transport route, the number of the source client will be copied as the number of the target client during import.
If you want to import a request into another target client, then you must specify this explicitly to the transport control program tp as "client=<target_client>" when you import.
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
