"tp import" instead of "tp put"
Among other things, the transport control program "tp" is used to import transport requests into a specific target system. There are basically two different commands for the program "tp" (on operating system level) available to do this:
Before SAP Release 3.0A, the recommended call of the import was
tp put <TSID>.
This call has certain disadvantages for the customer who normally only transports small changes, since this call for example
The reason that this command was nevertheless recommended was due, for example, to the fact that structure conversions of tables could not be carried out with the alternative call "tp import all <TSID>".
However, as of SAP Release 3.0A this call is complete in this respect. Thus, as of Release 3.0A the SAP recommendation is that imports are made with the call tp import all <TSID>
As of SAP Release 3.0A, ADO objects (for example forms) will also be
automatically imported into the correct target client. This target client is
(as for all other objects) the client specified by the client parameter in the
tp command line. If the client parameter is missing, the client from which the
export was performed is used as default.
A prerequisite for this, however, is that program RDDIMPDP be scheduled in
client 000 as background job. It can be scheduled in every client by running
the program RDDNEWPP under user name DDIC. It must be scheduled in each
existing client once after the upgrade.
The same is true for the correct client handling of the ADO objects for the
commands "tp export" and "tp put". Further information about this can be found
in the documentation of the ABAP/4 report RDDIMPDP.
The call "tp put <TSID>" was also improved together with improvements in the call "tp import all <TSID>". For customer transports, it is no longer necessary that the SAP system or the underlying database be stopped or started in the course of a "tp put" call. However, this remains necessary for future SAP release upgrades or for upgrades of the maintenance level using the command "tp put". For this reason, this functionality could not be completely removed.
As a customer, however, you can change the parameters of the program "tp"
so that neither the SAP System nor the underlying database be stopped or
started for your own transports during a "tp put" call. To do this, you must
change entries in the parameter file of program "tp". This parameter file is
on operating system level under the following path:
under UNIX: /usr/sap/trans/bin/TPPARAM
under Windows NT: \usr\sap\trans\TPPARAM
In this file, you can delete all entries of the following forms:
<SID>/startsap = <Value>
<SID>/stopsap = <Value>
<SID>/startdb = <Value>
<SID>/stopdb = <Value>