Wednesday 24 August 2011

Manual Import process of a transport at Os level with TP program


This article answers following queries :
Ø  How to import a transport manually with TP program?
Ø  How to import a transport without using STMS in SAP?
Ø  How to import a transport at Os level  in SAP ?
Ø  How to insert a request into the import queue of an SAP R/3 system manually?
Ø  When performing a request import manually, what will happen if client is not mentioned?
Ø  Can we manually import all the requests that are present in the import queue of an SAP system? If so, how ?
Ø  What is the parameter file name which was similar to TP_<domain>.PFL file which was used in older SAP versions?
Ø  What will happen in the background if a transport request  is added to the import queue of an SAP system ?
Ø  What will happen if the client in which you want to import does not exist in the target system?

-----------------------------------------------------------------------------------------------
Sometimes, there will be situations like you have to process transport imports manually. This can be done by TP program from the operating system level.

Transport control program TP is controlled by a parameter file TP_<domain>.PFL which is present under bin subdirectory of the transport directory.
Please note in older releases of SAP R/3, the file is termed as TPPARAM.
Before using TP for the first time, it is suggested to test the connection to the desired target system.
To perform this test, following command can be used.
tp  connect   <target system>  pf=<complete path of the parameter file>
If this test results are fine you can proceed further otherwise you need to troubleshoot the same and identify the reason for the same.

In order to insert a request into the import queue of an SAP R/3 system, use the following command:
tp  addtobuffer   <request>   <target system>  pf=<complete path of the parameter file>

If the above command is successful then, datafile and cofile of the request will get copied under respective  data subdirectory and cofiles subdirectory of the transport directory.
As the request is inserted to the import queue, it can now be imported using the following command.
tp  import  <request>   <target system>  pf=<complete path of the parameter file>
In case you would like to import all the requests that are present in the import queue of an SAP system  in the current sequence then provide the following command at oslevel.
tp  import all  <target system>  pf=<complete path of the parameter file>

You can add the following to specify a specific client for import:
client = <number of the client>
If the client is not mentioned, the data is copied to the client with the same number as the client from which the data was exported.

If the client into which you would like to import a request does not exist in the target system, the import terminates with an error message.

Enter your email address:

Delivered by FeedBurner



0 comments:

Post a Comment