SAP Library - Find your answers

Use report RSCLCCOP to transport user master records, profiles and authorizatons between clients in an R/3 system.

Start RSCLCCOP from the target client which the users and authorizations should be copied.

What is the steps to transport an object using se01 or se09?

After creating a transport request. To Transport a request go to

SE09 (Workbench Organizer) or SE10 (Customizing Organizer)

In the intial screen Check the boxes

1) Modifable (Which are yet to be released)
2) Released (Already Released)

Then press enter

Now in that screen check for your created request by pressing Ctrl+F .
In that request check if it is having any child nodes or not. If it is having any child node then first release it and then only you will be able to release parent node

Releasing a Transport Request:

Put your cursor on Child node and then press F9 or you can see a truck symbol which means for transport in SAP click on that. In the same way after releasing child node release the Parent node also then ask your basis person to transport that request from Development to Quality or Production.

Transporting from Development to other servers:

Go to the tcode STMS to where you can transport the request from one server to another server. Usually, only the basis person can do this.

SAP Maintenance transport requests work flow

An example of a basic principle and flow is:-

1. A request for a change is submitted to support team

2. Change is done in DEV (if approved) and tested by support team (limited testing only due to lack of productive data)

3. Change is transported to TST

4. User testing takes place

5. User approves or rejects (giving reasons)

6. System manager approves the change to go into PRD

7. Change is transported to PRD

All transports are done by the support team.

If a change is urgent it is transported straight away, if not they are batched up and done once a week.

The Workflow can be controlled by a software like a Lotus Notes database so you can have a record of approval at every step.

Note :-

The system manager is the manager of the support team. The system "belongs" to him i.e. it is his responsibility and he has the final say on what goes into the PRD system. 99.999% of the time he will approves the change, this is mainly a way of keeping him informed of what changes are happening in the system.

You cannot rollback a transport, not in R/3 Enterprise, or in any release. You should create a new transport which includes the corrections to the objects which were in the initial transport. This new transport should be imported into the production system. It will correct the buggy objects which were imported initially.

Have you ever been working on a project with 10-15 Basis administrators, and someone transported a request which was not supposed to be transported? This is a very common problem faced by many team leads. What would you do in this situation? STMS will not give you a log which tells you who has executed the transport.

The solution is table - TPLOG. Table TPLOG gives you all the data which you would like to record.

Keyword: BASIS
Title : Transport Guide :: Tips for Different SAP Objects

1.Log into Production Server
2.Go to PFCG and enter the role which you want to transfer to other system.
3.Goto Role->Download it will ask the path where to download/save that role on local desktop give the location and save it.
4.Log into Development
5.Go to PFCG
6.Upload and give the Role Path or location

To find the locked objects:-

Look in the tables TLOCK, E070, E071, and E070C. Sometimes, data in these tables can become orphaned, and may need to be processed manually (this is rarely necessary).

Keyword: BASIS
Title : Database Tables contaning Transport Requests

1. A request for a change is submitted to support team
2. Change is done in DEV (if approved) and tested by support team (limited testing only due to lack of productive data)
3. Change is transported to TST
4. User testing takes place
5. User approves or rejects (giving reasons)
6. System manager approves the change to go into PRD
7. Change is transported to PRD

All transports are done by the support team. If a change is urgent it is transported straight away, if not they are batched up and done once a week. The Workflow can be controlled by a software like a Lotus Notes database so you can have a record of approval at every step.

Note :-
The system manager is the manager of the support team. The system "belongs" to him i.e. it is his responsibility and he has the final say on what goes into the PRD system. 99.999% of the time he will approves the change, this is mainly a way of keeping him informed of what changes are happening in the system.
Many companies uses the core modules MM, PP, FI, CO. The problem with transporting single transports is that if it is a program, the complete program buffer is reloaded therefore giving a performance hit. Therefore you tend to leave them and just have one performance hit per week (although most weeks there are no program changes). When you are in production the number of transports will settle down to a reasonable figure. Maybe about 10 transports a week, and most of those are material groups (which, although they are user data, they are classed as customising). This rises if you are doing any modifications or changing business processes etc, but 10 is about quite normal for most.

Transfer of R/3 System components from one system to another.

The components to be transported are specified in the object list of a transport request.

Each transport consists of an export process and an import process:

The export process reads objects from the source system and stores them in a data file at operating system level.
The import process reads objects from the data file and writes them to the database of the target system.
The system maintains a transport log of all actions during export and import.

When an object is edited by a developer, it is normally locked in a transport request and until the transport is released, the object remains locked for other users to work on that object.

Sometimes it is necessary to unlock the object so that others can work on that modification. Ex: While applying Support Packs. In that case you can follow the steps.

Go to SE03

Run unlock object expert tool:

Check the “Create versions of objects” and “create transport of copies” and execute.

Then developer can be able to edit on this request now.

If option "Set to released" is selected the objects in the transport request is unlocked and the transport request is released.

The transport types:

K type: The system owner does not get changed with K type transport. This kind of transport is only allowed to consolidation and production system. After the K type of transport is done no correction is allowed to those objects. Any changes to K type transport objects in consolidation system are called repair.
The repairs can be done to those objects if the change option is selected in SE06 and change option is there in client level selection in T00 table. Generally K type transport is used for stage and production environment.

C type: With the C type transport the ownership of that object is also transferred to the target. After the transport is done, the target system is the owner of the transported objects. The objects will be originals of the target system. These kind of transports are generally done in a four tier architecture, where a bundle of development objects can go from the sandbox environment to development environment or development environment to integration environment and vice versa. SAP recommends doing these transports when the objects should move to another system for further development work.

T type: T type is called a transport of copy. The ownership of the object remains with the source; the target system just gets the copy of the objects. When a sap patch is applied to the development system and transported to other systems, those are perfect example of T type transports.

Follow the steps to add an object to a existing unreleased transport request:-


1.Log on to the client in which the transport request is created.

2.Go to transaction SE10 and find the transport request.

3.Select the transport request in the list and click on Ctrl+F11. Dont select the Sub-Task.

4.Turn “on” the radio button “Freely selected objects” that appears in the popup and press Enter.

5.In the “Include objects in request” screen, turn “on” the “Selected Objects" in the "Selection by type and name" section.

6.Check “on” the check box on the appropriate Object Type, and enter the name of the object to be added to the transport request. Click the Execute button or press F8.

7.On the “Include objects in request” screen, click the “Include Request” button or press F9. You will see a confirmation message in the status bar at the bottom of the screen.

8.Go back to SE10 and release the transport request.

Keyword: BASIS
Title : Transport Management System (TMS): Basics

Keyword: BASIS
Title : TMS : Setting up an R/3 Transport Landscape

Keyword: SAP HR
Title : How To Transport Organizational Structure

Keyword: SAP HR
Title : How To Transport Organizational Structure