cancel
Showing results for 
Search instead for 
Did you mean: 

transports

Former Member
0 Kudos

how can we make os transports

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Manohar,

Steps :Transport configuration for the first time

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_<SID>, 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 &#8594; Systems.

8. On the System Overview – Domain Domain_<SID> screen, click SAP System &#8594; Create &#8594; 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 <SID> 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


<current server>:\usr\sap\trans for NT or \usr\sap\trans for UNIX. Click Environment &#8594; Transport Routes.

9. On the Display Transport Routes screen, click the User Settings button, turn “on” the Hiergraphical List Editor, and click the &#8730; Continue button. Back out 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 &#8594; Standard Configuration &#8594; 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 &#8730; 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 &#8594; 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_<SID> where <SID> 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.

reward points welcome!

regards,

S.Rajeshkumar

Former Member
0 Kudos

hi manohar...

it seems you are new to OS transports.

Please never try to perform transports if you are not sure abt the process..

especially in Live environment..

To start,

All the methods that are described above will be useful if the target system is in Transport domain.

If the destination is a standalone system then you need to copy those transports first in to target system.(plz refer to my post which is posted in your question )

cheers

JPReyes
Active Contributor
0 Kudos

Hi Manohar,

To Start you need to add the transport request to the target system imput buffer,

tp addtobuffer <Target_SID> <SID>K9XXXXX

tp import <Target_SID> <SID>K9XXXXX Client=XXX

Regards

Juan

Former Member
0 Kudos

Hai,

A transport is essentially a set of files that contain information about SAP objects. Think of these files as a recipe. These files, when imported into a system, tell the system how to reconstruct the objects that the files contain.

There can be up to three different files that can comprise a transport:

1.The cofile

a. located in /usr/sap/trans/bin/cofiles

b. takes the form of K<6 digits>.<source SID> (example: K941988.DVL)

c. contains the meta-data about the transport

2.The R data file

a. located in /usr/sap/trans/bin/data

b. takes the form of R<6 digits>.<source SID> (example: R941988.DVL)

c. contains application-specific data objects

3.The D data file

a. also located in /usr/sap/trans/bin/data

b. takes the form of D<6 digits>.<source SID> (example: D941988.DVL)

c. contains application programs

Most of the time, only the cofile and R data file exist. When you actually perform an import, the transport’s cofile will know which files to look for.

The SAP <b>‘tp’ </b>utility is used to manually import transports into a system from the OS level. In order to utilize the tp utility, you need to be logged onto the OS as <sid>adm, and you should be in the /usr/sap/trans/bin directory.

The main<b> tp commands </b>that we use

1. <b>tp showbuffer <SID></b> (example: tp showbuffer TR2) --> Shows which transport headers are currently in the buffer

2.<b>tp addtobuffer <transport #> <SID></b> (example: tp addtobuffer DVLK942697 NT1) -->Adds the transport header info to the tp buffer for import

3.<b>tp import <transport #> <SID> client=<client #> <any umodes> pf=<path to TPPARAM file></b> -->Example: “tp import DVLK942697 NT1 client=200 u126

More information about tp commands can be found at:

http://help.sap.com/sapdocu/crossind/crm/crm40/helpdata/EN/3d/ad5af24ebc11d182bf0000e829fbfe/framese...

Hope this helps..

regards,

Gopinathan