sap Adding a New SAP Instance to an Existing TMS Domain Controller

1. Log on to client 000 in the SAP instance you want to add to the existing TMS
Domain.
2. Go to transaction SE06.
3. Click on the Perform Post Installation Actions button.
4. Go to transaction STMS.
5. You should see a popup box with the title TMS: Configure Transport Domain. Press F6 until you see a TMS: Include System in Transport Domain popup.
6. Fill in the TMS: Include System in Transport Domain popup with the Description, Target Host, and System number of the TMS Domain Controller then click Save.
7. You should see a message that says SAP System waiting to be included in the Transport Domain.
8. on to client 000 of the Transport Domain Controller and go to transaction
Log STMS, keeping your original session in the other SAP instance open.
9. On the Transport Management System screen, click Overview → Systems.
Highlight the System you just added and then click SAP System → Approve.
Then confirm all the messages.
10. Back on the Transport Management System screen, click Environment →
Transport Routes.
11. On the Display Transport Routes screen, click the Display<>Change button
to toggle into Change Mode. Click on Edit → Transport Route → Create.
11. On the Create Transport Route popup, use the Consolidation boxes to enter
the SID of the transport domain, create a Z* transport layer, and the SID
This document is the intellectual property of Jo Spencer and may not be edited without permission.
of the system you are adding. Click Save and confirm. Back out to the main
Transport Management Screen.
12. Back on the Transport Management System screen, click Overview → Systems.
Double-click on the new system, and click on the Communications tab. Make
sure that the Transport Group name is the name of the original transport
domain. If not, change it. Click the Transport Tool tab. Verify that the
information on the tab is correct and click the Insert Row button. Add a
Parameter of CTC and a Value of 1. Click the Save button.
13. You can switch back to the new instance, and confirm that the SAP System
waiting to be included in the Transport Domain has disappeard.
14. You may now log out of both SAP instances.
Return to Index...
Make a Local Transport into a Transportable Transport
Sometimes, mistakes just happen. For this example, we will use a transport
SM1K00047 as the erroneous change request. Make sure to release SM1K00047 before
beginning this procedure.
1. Log on to the client who is the owner of the local transports that needs fixed.
2. Go to SE03.
3. On the Transport Organizer List screen, click on Merge Object Lists which is
in the Requests/Tasks section.
3. On the Merge Objects List screen, put SM1K00046 in the first Request/Task
field. Make sure that the Released check box is "on" in the Request Status
section and click the Execute icon.
4. On the Merge Objects List screen, click on the Merge icon. 5. On the Enter Transport Request popup, click the Create Request icon. 6. On the Select Request Type popup, click "on" radio buttion Workbench Request. 7. On the Create Request popup, fill in the necessary information and make sure
that the fill in the Target field so that the transport request is NOT local. Click the Save, OK, √ icon, etc. until everything is done. You will
get a new transport request number, in our case SM1K00050. This new request
can be released using one of the transport organizer Transactions like SE10,
etc. Once it is released, you can go to /usr/sap/trans on the OS level and in
directory cofiles copy K00050.SM1 to K00046.SM1, and in directory data copy
R00050.SM1 to R00046.SM1.
8. You may now leave SE03.
Once you have control of your session again, the transports are done. Verify their return code in the Import Queue list. It shoud have been updated automatically.
Return to Index...
Transporting Change Requests
To manually transport change requests from DEV/QAS to PRD:
1. Make sure the change request(s) has been released via Se10 or one of the other Transport Organizer Transactions.
2. Go to transaction STMS and click Overview → Imports. Double-click the PRD queue.
3. Click the refresh button to make sure you have the most current view of the PRD queue. Make sure the change request(s) you want to transport shows in the queue.
This document is the intellectual property of Jo Spencer and may not be edited without permission.
4. Using the F9 button, highlight all the transactions you want to manually transport.
5. Click on Extras → Activate Inactive Requests. Confirm the popup. This bypasses the STMS_QA process.
6. Leave the change requests highlighted. Click Request → Import. On the popup, make sure that the target is client 300. Make sure that Synchronous radio button is "on" in the Execution tab. Make sure that the first three options are checked "on" in the Options tab. When you are done, click on the green √ and confirm the next popup.
Once you have control of your session again, the transports are done. Verify their return code in the Import Queue list. It shoud have been updated automatically.
Return to Index...
Adding a Change Request to a Transport Queue
1. Make sure the change request(s) has been released via Se10 or one of the other Transport Organizer Transactions.
2. Go to transaction STMS and click Overview → Imports. Double-click the PRD queue.
3. Click on Extras → Other Requests → Add. Fill in the Number of the Transport Request to be added to the queue and then press Enter.
4. Confirm the Add Transport Request popup. The transport request should now appear at the bottom of the queue list.
Return to Index...