Configuring TMS - Transport Management System - for the First Time
Note: if you already have a TMS configured, do not use this section to add a new instance to the existing TMS configuration. You could severely damage any pre-existing transports, making them untransportable. Instead, use the following section Adding New Instance to TMS Setup.
1. Log on to client 000 of the SAP instance to serve as the Domain Controller.
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. If the popup doesn't say that, press F6 to change to the correct popup box.
6. Fill in the TMS: Configure Transport Domain popup with the Description, Name of DOMAIN_, and the description of the Transport Domain. Then click Save.
7. On the Transport Management System screen (if you aren’t there, back out until you are), assuming that this is the first SAP instance and there are no other installed SAP instances in your landscape yet, and assuming that you want your transport requests to be transportable and not local only, click on Overview → Systems.
8. On the System Overview – Domain Domain_ screen, click SAP System → Create → External System. Fill in QAS if you are going to have a three system configuration or PRD if you are going to have a two system configuration, or make up a if you are never really going to have another SAP system. Fill in the rest of the information including the Path which is assumed to be \\:\usr\sap\trans for NT or /usr/sap/trans for UNIX. Click Environment → Transport Routes.
9. On the Display Transport Routes screen, click the User Settings button, turn “on” the Hiergraphical List Editor, and click the √ Continue button. Back out
This document is the intellectual property of Jo Spencer and may not be edited without permission.
of the screen and then go back in – you should see the list in a text mode which makes it easier to handle.
10. On the Display Transport Routes screen, click the Display<>Change button to toggle into Change Mode.
11. On the Change Transport Routes screen, click Configuration → Standard Configuration → Development and Production System.
12. Fill in the Development and Production System popup, using your current SAP system SID as the Development system and the SAP instance you created in step #8 as the Production system. Click the √ mark to Continue.
13. Back on the Change Transport Routes screen, click the Save icon and confirm all the popup questions.
14. On the Change Transport Routes screen, back out until you can once more see the Transport Management System screen. Click Overview → Systems.
15. On the Display TMS Configuration: System XXX screen, double-click the TMS Domain domain controller SAP instance.
16. On the Display TMS Configuration: System XXX screen, click the Display<>Change button to toggle into Change Mode. Click the Communication tab and make sure that the Transport Group Name is correct. It should contain of the Domain Controller in the format of DOMAIN_ where is the System ID of the SAP Domain controller. Use the dropdown to find the correct entry it the field is blank. 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.
17. Do step #16 for every system in your TMS Domain, making sure to change all Transport Group Names are the same and the CTC row is added to each with a value of 1.
18. Save your way back the the main STMS screen.
19. You may now leave STMS.
Return to Index...
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...
Viewing the Transport Queue History
1. Go to transaction STMS and click Overview → Imports. Double-click the queue for which you want to view the history.
2. Click on the Import History button or press Ctrl+F7. The resulting list can be sorted and filtered to produce a more exacting report if needed.
Return to Index...
Re-Transport Several Change Requests at Once
1. Go to transaction STMS and click Overview → Imports. Highlight the queue into which the transport(s) to be moved again were originally transported – the “FROM” queue - and click the Import History button or press Ctrl+F7.
2. If your SAP instance is older, you may have a very long Import History list in the next screen. Use some of the available filters and sort options to create a more controllable list of transports. Use the F9 to select and/or unselect as many as you need to transport.
3. Once all choices have been made, click Request → Forward → System. Fill in the “TO” system and click on the Execute green √ mark.
4. Now you can go to the “TO” queue and refresh the list. Your imports should all be there.
Return to Index...
Transport Tool System Confirmation
This document is the intellectual property of Jo Spencer and may not be edited without permission.
1. Go to transaction STMS and click Overview → Imports.
2. On the Import Overview screen, click Import Queue → Check → Transport Tool. You may get a message asking if you want to check the the transport tool for all systems. If only want to check a limited subset of the SAP instances, use F9 to select and/or deselect those systems before you click Transport Tool.
3. On the TMS: Check Transport Tool screen, a list of all selected SAP instances to be checked will appear.
If you see any thing but red green Oks, expand all the lines with the non-OK marks and look for more information. Correct these problems and then run this report again until it comes back clean.
Return to Index...
Use Target Groups to Transport to Mulitple Clients in Two Different Instances
1. Log on to client 000 of your TMS Domain Controller SAP Instance.
2. Go to transaction STMS.
3. On the Transport System Management screen, click Overview -> Transport
Routes.
4. On the Display Transport Routes screen, click the Display<>Change button to
toggle into Change mode. Click on the Target Groups line and click the
Create button.
5. In the Create Transport Group popup, fill in the Target Group as /XXXCLNTS/,
give a Short Description and click the Client Assignment button. Be aware
that the Target Group name must start and end with a “/”.
6. Enter each Target system and Target client you need. For our example, we will
DEV 100, QAS 200, and QAS 210. Click the green check mark to Transfer. You
now have a target group. Now you must create a Consolidation Layer.
7. Back on the Change Transport Routes screen, click on Transport Routes and
click Create.
8. In the Create Transport Route popup, click the Extended Transport Control
button at the bottom of the popup. Make sure Consolidation is "on" and fill
in the information using our Target Group as the Consolidation Target.
9. Click the green check button to Save the change.
10. You now have a Transport Group. Confirm the Disturbution of it to the other
SAP Instances.
Return to Index...
Configure TMS to Use SAP's Quality Assurance Functionality
A Quality Assurance system must have a) a delivery route leading from it to
another instance, and b) be the target of a consolidation route. See topic
Using Target Groups to Transport to Mulitple Clients in Two Different Instances
to fulfill the a) requirement.
1. Log on to client 000 of your TMS Domain Controller SAP Instance.
2. Go to transaction STMS.
3. On the Transport System Management screen, click Overview -> Transport
Routes.
4. On the Display Transport Routes screen, click Display<>Change button to
toggle into change mode. Click on the instance in which you want to control
QA. Normally, this is QAS and the instance to be controlled is PRD. Under
Transport Routes, click on the QAS instance and click Create.
5. On the Create Transport Route screen, make sure Delivery is "on" and fill in
Source and Delivery systems with QAS and PRD. Click the green check mark to
save. Now you have met condition a. 6. Back on the Change Transport Routes screen, click on the QAS instance and
click the single pencil Change button. You will see a Change System
This document is the intellectual property of Jo Spencer and may not be edited without permission.
Attributes popup. Click "on" Quality Assurance - Delvery After Confirmation.
If you want to change the people who OK the transports, click the
Procedure button and make your changes. Then back out. Click the green check
to Transfer your changes.
7. Back on the Change Transport Routes screen, click on the Target Groups line
and click the Create button.
8. In the Create Transport Group popup, fill in the Target Group as /XXXCLNTS/,
give a Short Description and click the Client Assignment button. Be aware
that the Target Group name must start and end with a “/”. Enter each Target
system and Target client you need. Click the green check mark to Transfer.
You now have a target group. Now you must create a Consolidation Layer.
9. Back on the Change Transport Routes screen, click on Transport Routes and
click Create.
10. In the Create Transport Route popup, click the Extended Transport Control
button at the bottom of the popup. Make sure Consolidation is "on" and fill
in the information using our Target Group as the Consolidation Target. Click
the green check button to Save the change.
11. You now have a Transport Group. Confirm the Disturbution of it to the other
SAP Instances.
12. You may now leave the STMS transactions.
Return to Index...
Automate the Transport Process
1. Log on to client 000 of your TMS Domain Controller SAP Instance.
2. Go to transaction STMS.
3. On the Transport System Management screen, click Overview -> Imports.
Double-click on the queue for the SAP instance are in.
4. On the Import Queue screen, click the Refresh button. Click on the Import
All Requests button.
5. On the Start Import popup, fill in the information for the job. Make sure "At
Start Time" is on. Although Period appears grayed out, you can still change
it to the periodic value you need. I recommend every hour in DEV, 4 times a
day in QAS, and once an evening in PRD. Click on the green check mark to
Continue.
6. You may now leave tSTMS transaction. If you ever need to change this job,
he you must do it via STMS and not SE37.
7. On the Transport Management System screen (if you aren’t there, back out until you are), assuming that this is the first SAP instance and there are no other installed SAP instances in your landscape yet, and assuming that you want your transport requests to be transportable and not local only, click on Overview → Systems.
8. On the System Overview – Domain Domain_
9. On the Display Transport Routes screen, click the User Settings button, turn “on” the Hiergraphical List Editor, and click the √ Continue button. Back out
This document is the intellectual property of Jo Spencer and may not be edited without permission.
of the screen and then go back in – you should see the list in a text mode which makes it easier to handle.
10. On the Display Transport Routes screen, click the Display<>Change button to toggle into Change Mode.
11. On the Change Transport Routes screen, click Configuration → Standard Configuration → Development and Production System.
12. Fill in the Development and Production System popup, using your current SAP system SID as the Development system and the SAP instance you created in step #8 as the Production system. Click the √ mark to Continue.
13. Back on the Change Transport Routes screen, click the Save icon and confirm all the popup questions.
14. On the Change Transport Routes screen, back out until you can once more see the Transport Management System screen. Click Overview → Systems.
15. On the Display TMS Configuration: System XXX screen, double-click the TMS Domain domain controller SAP instance.
16. On the Display TMS Configuration: System XXX screen, click the Display<>Change button to toggle into Change Mode. Click the Communication tab and make sure that the Transport Group Name is correct. It should contain of the Domain Controller in the format of DOMAIN_
17. Do step #16 for every system in your TMS Domain, making sure to change all Transport Group Names are the same and the CTC row is added to each with a value of 1.
18. Save your way back the the main STMS screen.
19. You may now leave STMS.
Return to Index...
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...
Viewing the Transport Queue History
1. Go to transaction STMS and click Overview → Imports. Double-click the queue for which you want to view the history.
2. Click on the Import History button or press Ctrl+F7. The resulting list can be sorted and filtered to produce a more exacting report if needed.
Return to Index...
Re-Transport Several Change Requests at Once
1. Go to transaction STMS and click Overview → Imports. Highlight the queue into which the transport(s) to be moved again were originally transported – the “FROM” queue - and click the Import History button or press Ctrl+F7.
2. If your SAP instance is older, you may have a very long Import History list in the next screen. Use some of the available filters and sort options to create a more controllable list of transports. Use the F9 to select and/or unselect as many as you need to transport.
3. Once all choices have been made, click Request → Forward → System. Fill in the “TO” system and click on the Execute green √ mark.
4. Now you can go to the “TO” queue and refresh the list. Your imports should all be there.
Return to Index...
Transport Tool System Confirmation
This document is the intellectual property of Jo Spencer and may not be edited without permission.
1. Go to transaction STMS and click Overview → Imports.
2. On the Import Overview screen, click Import Queue → Check → Transport Tool. You may get a message asking if you want to check the the transport tool for all systems. If only want to check a limited subset of the SAP instances, use F9 to select and/or deselect those systems before you click Transport Tool.
3. On the TMS: Check Transport Tool screen, a list of all selected SAP instances to be checked will appear.
If you see any thing but red green Oks, expand all the lines with the non-OK marks and look for more information. Correct these problems and then run this report again until it comes back clean.
Return to Index...
Use Target Groups to Transport to Mulitple Clients in Two Different Instances
1. Log on to client 000 of your TMS Domain Controller SAP Instance.
2. Go to transaction STMS.
3. On the Transport System Management screen, click Overview -> Transport
Routes.
4. On the Display Transport Routes screen, click the Display<>Change button to
toggle into Change mode. Click on the Target Groups line and click the
Create button.
5. In the Create Transport Group popup, fill in the Target Group as /XXXCLNTS/,
give a Short Description and click the Client Assignment button. Be aware
that the Target Group name must start and end with a “/”.
6. Enter each Target system and Target client you need. For our example, we will
DEV 100, QAS 200, and QAS 210. Click the green check mark to Transfer. You
now have a target group. Now you must create a Consolidation Layer.
7. Back on the Change Transport Routes screen, click on Transport Routes and
click Create.
8. In the Create Transport Route popup, click the Extended Transport Control
button at the bottom of the popup. Make sure Consolidation is "on" and fill
in the information using our Target Group as the Consolidation Target.
9. Click the green check button to Save the change.
10. You now have a Transport Group. Confirm the Disturbution of it to the other
SAP Instances.
Return to Index...
Configure TMS to Use SAP's Quality Assurance Functionality
A Quality Assurance system must have a) a delivery route leading from it to
another instance, and b) be the target of a consolidation route. See topic
Using Target Groups to Transport to Mulitple Clients in Two Different Instances
to fulfill the a) requirement.
1. Log on to client 000 of your TMS Domain Controller SAP Instance.
2. Go to transaction STMS.
3. On the Transport System Management screen, click Overview -> Transport
Routes.
4. On the Display Transport Routes screen, click Display<>Change button to
toggle into change mode. Click on the instance in which you want to control
QA. Normally, this is QAS and the instance to be controlled is PRD. Under
Transport Routes, click on the QAS instance and click Create.
5. On the Create Transport Route screen, make sure Delivery is "on" and fill in
Source and Delivery systems with QAS and PRD. Click the green check mark to
save. Now you have met condition a. 6. Back on the Change Transport Routes screen, click on the QAS instance and
click the single pencil Change button. You will see a Change System
This document is the intellectual property of Jo Spencer and may not be edited without permission.
Attributes popup. Click "on" Quality Assurance - Delvery After Confirmation.
If you want to change the people who OK the transports, click the
Procedure button and make your changes. Then back out. Click the green check
to Transfer your changes.
7. Back on the Change Transport Routes screen, click on the Target Groups line
and click the Create button.
8. In the Create Transport Group popup, fill in the Target Group as /XXXCLNTS/,
give a Short Description and click the Client Assignment button. Be aware
that the Target Group name must start and end with a “/”. Enter each Target
system and Target client you need. Click the green check mark to Transfer.
You now have a target group. Now you must create a Consolidation Layer.
9. Back on the Change Transport Routes screen, click on Transport Routes and
click Create.
10. In the Create Transport Route popup, click the Extended Transport Control
button at the bottom of the popup. Make sure Consolidation is "on" and fill
in the information using our Target Group as the Consolidation Target. Click
the green check button to Save the change.
11. You now have a Transport Group. Confirm the Disturbution of it to the other
SAP Instances.
12. You may now leave the STMS transactions.
Return to Index...
Automate the Transport Process
1. Log on to client 000 of your TMS Domain Controller SAP Instance.
2. Go to transaction STMS.
3. On the Transport System Management screen, click Overview -> Imports.
Double-click on the queue for the SAP instance are in.
4. On the Import Queue screen, click the Refresh button. Click on the Import
All Requests button.
5. On the Start Import popup, fill in the information for the job. Make sure "At
Start Time" is on. Although Period appears grayed out, you can still change
it to the periodic value you need. I recommend every hour in DEV, 4 times a
day in QAS, and once an evening in PRD. Click on the green check mark to
Continue.
6. You may now leave tSTMS transaction. If you ever need to change this job,
he you must do it via STMS and not SE37.
1 comment:
SAP APO Online Training classes
Post a Comment