Enable TOC - Transport of Copies for Testing

This guide describes the one-time configuration required to create Transport of Copies (ToC) in SmartChange:

enabling the global feature, creating a ToC destination, assigning it to the project, and – if the TM Server and DEV system are not the same – setting up the trusted RFC connection. Finally, the actual ToC run is triggered.

Open

Step 1 – Global Setting: Enable Transport of Copies

1. Start transaction /N/RTC/TM.

2. Open the menu path SmartChange → Settings → Global (SmartChange Transport Management – Global Settings).

3. Switch to the “Feature” tab and enter Edit mode.

4. In the “Transport of Copies Testing” section, set the “Enable Transport of Copies Testing” flag.

5. Define the ToC Selection (e.g. Multiple selection) and determine the short text of the automatically created ToC transports:

●       “Short text based on original (one ToC per TR)” → format: ToC from <ORIGIN_TR> : <ORIGIN_TEXT>  (recommended), or

●       “Custom short text” → e.g. SmartChange generated TOC (ends in quality system)

6. Review the optional switches depending on your landscape: Hide project/destination selection popup during TR creation, Enable Allowlist Projects for modifiable requests (active in the example), Exclude transport requests without objects from ToC creation.

7. Under the Default User Settings tab, activate the option “display modifiable requests” and activate this also in your personal settings.

8. Save.

Open

Open

Result: ToC creation is enabled globally; the short text of new ToC transports follows the selected rule. Modifiable Requests are displayed in the Workflow monitor.

Step 2 – Destinations: Create a ToC Destination

A ToC destination for Type of Request “T” must be created, which is then assigned to a destination that is to be enabled for ToCs.

1. In /RTC/TM, open the Destinations view and enter Edit mode.

2. Under Logical destination, create the ToC destination (in the example below):

3. Assign the ToC destination (Type T) to the logical target levels (in the example Development / Quality / Production; Quality → System SBQ, client 100).

4. Use “ToC Destination” or the Where-Used list to check which destination the ToC destination is assigned to (columns Dest. / SID / Client / Level / Desti text / TR types / ToC Dest.).

5. Save.

Open

Result: A ToC destination of type “T” exists and is assigned to the target destination to be used for ToCs.

Step 3 – ProjectManager: Assign ToC Destination to the Project

1. In the ProjectManager, open the relevant project (Edit mode).

2. Assign the previously created ToC destination to the project.

3. Save.

Result: With the project you can create ToCs to the assigned ToC destination.

Step 4 – Set up Trusted RFC (only necessary if TM Server / Controller ≠ DEV system)

If the TM Server (Controller) is not the DEV system, a trusted RFC connection between the development system(s) and client(s) and the TM Server is required.

RFC destination naming convention: ZRTC4_TM_<targetSID>_<targetClient>_TRUST

where <targetSID> is the SID of the development system and <targetClient> is its client from which TOCs can be created.

1. Make sure the RFC destination is set up as trusted: SM59 → Logon and Security tab → Trust relationship = “Yes”.

2. Check whether the systems are already trusted systems: the TM Server must be a trusted system of the development system (SMT1 on DEV).

If NO, continue with the following steps on the DEV system:

3. SM59: Create an RFC of type ABAP named TMS (= SID of the TM Server) to the TM Server.

4. SMT1: Create a new trusted connection via the wizard and add TMS as the RFC there.

●       On the TMS system, a new RFC TRUSTING@"DEVsid"_"DEV_installationnumber" is created.

●       Test the connection.

• • If it is not successful – error message “Service 'sapmsDEV' unknown”: on the operating system level, check the service file (/etc/services) and create the entry if needed:

• • If error e.g. 00024No authorization to log on as a Trusted System (L-RC=1 T-RC=1)

Step 5 – Create a ToC (Functional Test)

1. Create a transport request, assign it to your default destiantion (mapped to the TOC destination), and release only the task.

2. Select this transport request in the Modifiable Requests area in the TM Workflow Monitor.

3. Click the “Start TOC” button and confirm the popup.

Result: SmartChange creates a ToC transport (type T = Transport of Copies) to the configured ToC destination.

Additional Information

• If the Status Switcher is used, it is recommended to review your variants if you want to handle the ToCs differently

• General information:

FAQs

Q1: Which SmartChange Authorizations are needed for creation of ToCs?
A1: Minumim TM Developer (/RTC/TM_DEV) or Approver Role(s) (/RTC/TM_APPR1, /RTC/TM_APPR2).

Q2: What transport requests will be displayed in the “Modifiable request” folder/view in the TM monitor?
A2: All connected systems with clients where a modifiable request was found will be displayed. There is no cross-check against the development systems defined in TM Global settings. Prerequisites for a system to appear in the tree: 1. the /RTC/TM_BADI configuration must be active / 2. transaction /RTC/TM_FILL_MOD_TR must be run one-time to push all existing modifiable TRs in TM / 3. Afterward when creating a TR, the information is automatically distributed (≥ TM Version 5.4.4.0)

Q3: Can ToC be started for all displayed requests, or only for those with a ToC destination?
A3: The functional enablement of ToC per development line is controlled at the project/destination configuration level, thus only for those destinations with an according ToC destination assigned.

Q4: What is the checkbox “Enable Allowlist Projects for modifiable requests” for?
A4: Enables assigning, at transport creation, to a project/destination that uses “Allowlist Objects” quality checks. Use this in ITSM integration to create an empty transport request from a ticket and assign it to its destination.

Q5: How do I assign a destination to transports created before activating the ToC feature?
A5: Select the desired transports (multiple rows in TM Monitor) → click the “Project/Destination” button → assign. Please note: all selected transports must be of the same transport type for multi-assignements.

Q6: What is the button “reload from development system” for?
A6: For manual load/re-load of all modifiable requests from the connected development systems (prerequisites to be met, see also A2).

Q7: Can a ToC destination path only have one system ?
A7: A ToC destination path can have multiple / several non-productive systems to be delivered with ToCs for testing purposes and a ToC destination can be assigned to multiple projects. Multiple ToC destinations can also be created and assigned as needed.

Q8: Why are my ToC transports not beeing imported automatically into the Quality System but are waiting in/for signature?
A8: Depending on the respective configuration an status switcher job needs to be in place for ToCs. Status Switcher Jobs can also be configured to switch only certain project/destination combinations if needed.

Summary