As of Release 4.6A, an explicitaddtobuffer command leaves the position of the entry unchanged, if the relevant transport request is already in the buffer. Only the status of the entry is changed:
Before you call this command and its options, consider the effects of changing the import sequence.
This deletes successfully imported change requests from the list of requests that are marked for import into the SAP System <SAPSID>. This function is contained in the commandstp import all <sapsid> and tp put <sapsid> .
If the specified request is marked for import into the specified SAP System, this flag is deleted from the import list.
Before you call this command, consider the effects of changing the import sequence.
As of Release 4.6A: If a transport request was only partially imported, you can delete this type of transport request from the buffer. However, if a deleted transport request is placed in the buffer (without having been initially or completely imported), the attributes of the old entry are reactivated. This means the return codes, the unconditional modes and tags of the deleted entry appear in the new entry.
If the list of requests marked for import into the specified SAP System contains a STOP mark, the mark is deleted.
This exports the complete request from the source system. This command starts the export of a request from the operating system level. Only use this command in exceptional cases. The SAP System uses the commandexpwbo to release requests from CTS transactions.
This automatically reformats the entire buffer.
As of Release 4.5A, there are 2 different formats for buffer entries. (As of Release 4.5A,tp can work with both formats, and with a puffer containing heterogeneous entries. As of Release 4.6A, tp can work with 3 formats.)
However, in certain cases entries with the old formatting have to be reformatted during the normal run oftp . In this case, the entire buffer is automatically reformatted.
If you use the optionsdowntorelease and Iagree for command reformatbuffer , you can format the buffer so that its formatting is compatible with an older release:
The commandreformatbuffer with this option formats the buffer so that the formatting corresponds to the one used in an old release. This is necessary if tp writes buffer entries to the buffer of another system, but uses a buffer format that the transport control programs does not understand in this system.
Since older formats cannot store the same amount of information as the newer ones, some information contained in the original buffer may not be stored in the unformatted buffer. This may lead to data loss.
To avoid data loss, the original buffer is stored. In addition, you have the following functions:
If you call
If you use the optiondowntorelease , you must also specify the option Iagree with yes or no . You cannot use the transport system until you decide to accept or reject the changes.
Here are the following values for this option:
yes( true )
Acceptthe change made by tp reformatbuffer <SID> downtorelease <rel>
In this case, tp deleted the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
no( false )
Rejectthe change made by tp reformatbuffer <SID> downtorelease <rel> In this case, tp copies the backup of the original buffer back and deletes the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
A special STOP mark is added to the list of requests registered for import into the specified SAP System. The commandstp import all <sapsid> and tp put <sapsid> only process the requests in front of this stop mark.
A STOP mark can only be placed at the end of the change requests that have already been marked. In addition, it can only be set if no other mark of the same kind already exists.
Thistp function displays which values the individual parameters of the transport profile have for the current SAP System.
This creates versions of the objects in the specified request. This transport step is contained in commandexport .
As of Release 4.5A, more actions that prepare the export are performed in this step.