Transporting Target Systems
Use report DIAGCV_TRANSPORT_TARGET_SYSTEM to add customer target systems to a transport (the report was provided via SAP Note 2277492).
If you would like to transport target systems from a development SAP Solution Manager into a productive SAP Solution Manager you can perform this task using the following information to specify the necessary table contents.
Tables DIAGCV_TSCUS_HDR and DIAGCV_TSCUS_DAT
Customer target systems are stored in tables DIAGCV_TSCUS_HDR (header) and DIAGCV_TSCUS_DAT (data). So you need to specify in the transport request those target systems you would like to transports.
Transport Request
The request/task needs at least 2 entries
| Short Description | Program ID | Object Type | Object Name |
|---|---|---|---|
| Table Contents | R3TR | TABU | DIAGCV_TSCUS_DAT |
| Table Contents | R3TR | TABU | DIAGCV_TSCUS_HDR |
To transport one target system you need to specify in Function for
DIAGCV_TSCUS_HDR the table Key as: The target system id follow by an asterix (example using 0ALERT):
| Table Keys |
|---|
| 0ALERT* |
DIAGCV_TSCUS_DAT the table Key as: Concatenate column RELID and SRTFD follow by an asterix.
The link between DIAGCV_TSCUS_DAT and DIAGCV_TSCUS_HDR is column SRTFD. So can specify which config stores (each having a separated SRTFD) should be transported.
This example uses all config stores of target system 0ALERT (ABAP_TRANSPORTS / AUTH_PROFILE_USER / GLOBAL / J2EE_PSE_CERT / PSE_CERT).
| Table Keys |
|---|
| RF0050569B00861EE290F3EDC225FA5821* |
| RF0050569B00861EE290F3EDC225FA7821* |
| RF0050569464271ED3AABF5E3C370385AA* |
| RF0050569B00861EE290F3EDC225FA1821* |
| RF0050569B00861EE290F3EDC225FA3821* |
Remarks
The target system 0ALERT is stored in tables DIAGCV_TSSAP_HDR and DIAGCV_TSSAP_DAT .