top of page

Step-by-Step Guide: Transport of copies(TOC).

Used to copy a server from one to another, such as development to quality server. SE01 is the transaction code.

What is the reason for using TOC?

TOC will just make a duplicate of the transport request. So, if any modifications are needed in the quality server, they can be made to an existing transport request that is present in the development server, and then take a TOC and move it to the quality server. If a transport request is moved from one server to another, the changes are not reflected on the receiving server.

STEPS: T-code : 'SE01'.

1. Enter the user name in the transports tab.

2. Select copy transport

3. Select modifiable

4. Select Create.

1. Enter a brief description

2. Select the destination system.

 3. Save the TOC.

Once the transport request has been generated, the child transport copy must be pushed into the transport copy. As shown in the image below.

Once the preceding process is completed, all configurations available for that kid transport request will be copied to TOC.

The copied transport request must then be released before being imported into the quality server.

AFTER THE TR HAS BEEN RELEASED FROM THE SOURCE SYSTEM TO THE TARGET SYSTEM, THE TARGET SYSTEM REQUIRES AN IMPORT.

Import SAP Transport Requests :

Follow the steps below to add transport requests to the import queue and import them:

1. To access the transport management system, go to transaction STMS or stms_import.

2. Click the import icon's [Import Overview]

3. To load the transport request into the import queue, double-click on it.

4. Select Extras > Other Requests from the menu and sub menus. Add

5. Enter the transport request (for example, ITMK620_00035U as the name of the transport request), and it will be added to the import buffer once you press the Enter key.

6. As shown below, choose the transport request that had been added to the import buffer (for instance, ITMK620_00048U):

7. The menu and sub menus buttons Demand > Import.

8. Enter the client number to which the transport will be applied, then choose "Immediate" for the start date; Select "Asynchronous" for the execution mode; Click the enter key after selecting "Leave the transport Request in queue for later import", "Import transport again", "Override original", and "Overwrite objects in unconfirmed repairs". The importation transport will begin.




Check the Status of Transport Requests :#

All transport requests are listed in the import overview of the transaction STMS in the transport management system.

In the "RC" column, the status of the transport requests is shown.

 

If a bar is green, the import was successful. To examine the error messages in the event of any warnings or faults, double click on the icon.

Move transport request:

Transport requests are moved using this procedure from the development server to the production server.

Press enter to select customization requests or start a new transport request.

1.Request to release a child for transfer

2.Request to release the parent transport.

This transport request will now be imported to the production server by the TR team.

Copy transport request from client to client (Within server):

This procedure is used to transfer requests for transport from one client to another within the same server, such as in production. Code for transactions SCC1.

1. Type the parent/child transport request number and the source client.

2. The run should start now.

Please follow us for more updates:




62 views0 comments

Recent Posts

See All

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page