use Target Groups to Transport to Mulitple Clients to Different Instances in SAP

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.

1.   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.  

2.   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 “/”.

3.   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.

4.   Back on the Change Transport Routes screen, click on Transport Routes and

    click Create.

5.   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.

6.   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.

view a history of what changes have been transported in SAP

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.

verify that the transport system is up and running in SAP

Transport Tool System Confirmation

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.

transport several change requests at once in SAP

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.

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.

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.

transport a change from one R/3 system to another

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.