Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

To load non-ABAP Transports into TM in a predefined project/ destination and status, a special loader can be used.

Scenario:

You want to load non-ABAP Transports into TM in a predefined project/ destination and status.

For example, you have a PO system which is connected to a SAP solution manager via CTS+ and if the transports are released, you want them to be added into TM automatically.

Configuration steps

  1. Maintain table /RTC/TM_TAUT in the ABAP communication system

    1. R3 SID: SID of your development system (where the transport request originates from). E.g., if you want to load PO transports, the SID might be POD or similar. You can check this in your ABAP communication system, checking the transport request prefix.

    2. R3 CLIENT: The client your transports are associated with. If you are not sure, you can check the client information in table E070C.

    3. D TM: The SID of your TM System.

    4. PJ DESTI: The TM project, you want the transport request to be added. Please use the exact name (no typos, case-sensitive), otherwise the loader will not work.

    5. DESTI NAME: The TM destination you want the transport request to be added. Please use the exact name (no typos, case-sensitive), otherwise the loader will not work.

    6. Status: The initial status of the transport request. (The initial level is configured in the destination).

  2. Schedule report /RTC/TM_LD_81 periodically on the ABAP communication system. Any time it runs, it checks for new released transport requests from your non-ABAP system and will insert them into TM.

Technical info:

Once the transport request have been loaded into TM they will be written into table /RTC/TM_LOAD. If you want to reload them, you have to delete the respective entries in this table.

  • No labels