Global Parameters

Default: ALOG$(syear)$(yweek)

Value range: Text

Here, you specify the name of a file in which tp stores information about every transport step for each change request. The file is always stored in the transport directory log.

Default: 0

Value range: Boolean

ctc stands for Client Transport Control and represents a configuration method for transport routes. This parameter lets you set specific transport routes using various clients in your system landscape. This method requires an extension of the import buffer. This new format is not understood by old tp programs. This new function is therefore deactivated. To use it, you need to explicitly activate it.

At the same time, the profile generator from Transport Management System (TMS) is also delivered. Along with the transport route configuration in the TMS, transport profile parameter ctc is automatically activated from the TMS if required for your transport landscape.

When parameter ctc is set, tp requires you to set the value for parameter tp_version to at least 264. This prevents transport control programs with lower version numbers from working with this import buffer. Parameter ctc can therefore only be activated if all the transport control programs that work with a specific SAP system have at least version 264.

Client category definition enables new options during import, and the general handling of transport requests and target systems. There are also the command optionsclires and defaultclient.

If you set parameter ctc, this changes the output for the command showbuffer, since the corresponding target client also needs to be output.

Default: 0

Value range: Boolean

Transport request names can be up to 20 characters in length. However, these transport requests cannot be processed in the import buffer's previous format. If you set the new parameter nbufform, you can switch this format so that transport requests with names between 10 and 20 characters can be processed. As with parameter ctc, you have to protect this change to the import buffer format from transport control programs that are too old.

tp requires that, when you activate the parameter nbufform, you also set the value for parameter tp_version to at least 264 at the same time. This prevents transport control programs with lower version numbers from working with this import buffer. The new parameter nbufform can therefore only be activated if all the transport control programs that work with a specific SAP system have at least version 264.

Default: 0

Value range: Boolean

A file is created for each user of an SAP system in the transport group in the sapnames subdirectory of the transport directory. The file is given the name of the user. However, non-valid user names in the SAP system may be used as file names in some of the operating systems. Special characters such as " ",".", and so on, or the length of the file name permitted could cause problems.

tp offers a solution: The user names are modified to create file names that are valid in all operating systems. The original user name is stored in the corresponding file.

Default: 9

Value range: Numerical

Parameter repeatonerror has an effect similar to parameter stoponerror, with the difference that repeatonerror specifies the return code up to which a change request is considered to be successfully processed. Return codes lower than repeatonerror are still accepted. Change requests that have not been processed completely remain in the buffer.

The option selectivelanguageimport (sli) is available to control the selective language import. The default value for this option is sli=no. By selecting sli=yes, you can ensure that language-dependent data is only imported for languages that exist in the system.

Default: 1

Possible values: Boolean

This parameter is connected with parameter stoponerror.

If one of the tools (R3trans, DD Activation, etc.) called by tp outputs a return code that is equal or higher to stoponerror, tp stops immediately.

If stopimmediately = 0, tp lets the current import phase run to completion. If serious problems occur, the same error messages might reoccur (like with database problems). If temporary problems occur, this can lead to sequence problems. We therefore advise you not to change the default value.

Default: 9

Value range: Numerical

If stoponerror is set to 0, tp is never stopped in the middle of an import- or put- call. If stoponerror is set to a value greater than 0, tp stops as soon as a change request generates a return code that is equal to or greater than this value. Change requests that still have to be processed for the current step are first completed. However, a syncmark in the buffer of the relevant SAP system functions as a limit here.

If you call tp showparams <SID>, you can see that two variables were set: stoponerror itself is treated as a Boolean variable that determines if tp is stopped if the return code is too high. The numeric value of the stoponerror parameter is stored in the variable <badrc>.

Default: SLOG$(syear)$(yweek).$(system)

Value range: Text

Here, you name a file in which tp stores information about the progress of import actions for a specific SAP system. The file does not contain information about any particular change request. The file is always stored in the transport directory log.

The system-specific transport log flies are written to a shared log directory. Given the amount of files concerned, this directory can easily become cluttered. If you set <sid>_log_files to true, tp does not write system-specific transport log files to the log transport directory, instead it writes them to an additional subdirectory called <sid> (.../log/<sid>).

Default: 0

Value range: Version number

If this parameter is set to a value not equal to zero, lower versions of tp are not allowed to work with this transport profile. It the default value 0 is set, this does not apply.

Default: never

Possible Values: never, c_only, always

If you set the parameter to either c_only or always, additional steps are triggered during the import. These generate versions of the imported objects in the target system. This concerns the import and put commands. For more information about these steps, see the tp online help for both commands. To do this, call tp with just one of the import or put commands and do not specify any other options.

The additional steps are:

• Before importing the ABAP Dictionary sources, the transport request itself is imported (command file Import).
• The version maker is then called in the batch to store the object versions before importing to the versions database. Versions are only created at this stage if the current version of the object is not the same as the latest version in the database, or if a version does not yet exist for the object in the versions database.
• The version maker is called during the import steps at a point where it has already been called in order to set the flags on the imported objects in the versions database. If vers_at_imp is configured differently from never, real versions are written to the versions database at this point.

The difference between the values c_only and always lies in how the various transport methods are handled. If parameter vers_at_imp is set to always, all transport versions are made according to the new method. Value c_only restricts this to transports of originals only.

Transports of originals are:

• C transports: Relocation without changing the development class (for a normal consolidation transport, the object must be transported back again.).
• O transports: Relocation with change of package (In future, the object can be transported from the original system with a consolidation transport. This can only be done if the package is changed during the transport.)
• E transports: Relocation of a complete package (optionally you can specify a new transport layer.)