How to load transports into TM via Report /RTC/TM_LD_15

Scenario:

You want to load transport requests from your development system into TM, but the development system and the TM server are different systems. In this setup, the transports cannot be inserted into a local TM directly. Instead, they must be transferred to the remote TM server.

Report /RTC/TM_LD_15 handles this distribution: whenever a transport request is exported in the development system, a background event triggers the report, which then transfers the transport request into the remote TM system.

Configuration steps

1. Configure the TM Business Add-In (transaction /RTC/TM_BADI)

Open the BAdI configuration in the development system and maintain the settings as follows:

• As Distribution method, select Distribution with report /RTC/TM_LD_15.

• Enter the SID of the TM system.

• Assign an Event ID, e.g. TM_TRIGGER. This event will later be used to trigger the background job.

• Fill in the remaining BAdI settings (status, expanded nodes, assignment, checks, etc.) as usual.

Afterwards, activate both Business Add-Ins (/RTC/TM BEFORE EXP 1 and /RTC/TM AFTER EXP 01) in the section “Step 2 - Activate Business Add-Ins”.

Open

2. Create the batch event (transaction SM62)

Create a new background processing event for the trigger:

• Go to transaction SM62 and choose Create on the BckProcEvnts tab.

Open

• Enter the event name defined in the BAdI configuration, e.g. TM_TRIGGER, and a description.

• Do not set the System checkbox.

• Save the event.

Open

3. Create a variant for report /RTC/TM_LD_15 (transaction SE38)

Create a variant for the report which will be used by the background job:

• Go to transaction SE38, enter program /RTC/TM_LD_15, select Variants and choose Create.

Open

• Enter a variant name, e.g. LOAD.

Open

• On the selection screen, enter the SID of the TM system and select mode Load.

Open

• Maintain a description in the variant attributes and save the variant.

4. Schedule the background job (transaction SM36)

Schedule a periodic, event-triggered job for the report:

• Go to transaction SM36 and enter a job name, e.g. /RTC/TM_LD_15.

Open

• Create a Step with ABAP program /RTC/TM_LD_15 and the previously created variant (e.g. LOAD).

Open

• As Start condition, choose After Event and enter the event created before, e.g. TM_TRIGGER.

• Set the Periodic Job checkbox.

Open

• Save and release the job.

Technical info:

Whenever a transport request is exported in the development system, the activated BAdI raises the background event (e.g. TM_TRIGGER). This event starts the scheduled job, which runs report /RTC/TM_LD_15 with the maintained variant and transfers the transport request into the remote TM system specified in the variant.