The transport buffer file is a list of customer transport objects to be imported. The transport buffer file is based on the import queue of the Transport Management System (TMS) of the system that you want to update. Make sure that the system use Extended Transport Control.

You have two options to provide the file: Either you copy an existing buffer file to the SUM directory, where it can be consumed, or you use a wizard.

• If you want to copy the buffer file, change first to operating system level. Then go to the subdirectory buffer of the transport directory in the system that you want to upgrade. Copy the file <SID of the system to be upgraded> to the download directory of the Software Update Manager. The buffer file contains all transports, which are part of the import queue and to be integrated into the update procedure. Check carefully that you integrate only the wanted transports into the update procedure.

• If you want to use a wizard, you can use the Customer Transport Upgrade Integration Wizard. SAP Note 2450902 gives you more information on how to generate the buffer file, and on how to include the file into the update procedure.

In the transport buffer file, the customer transports are written in the correct order with client-specific CTC=1 format. The update procedure automatically sets the parameter CTC to 1 in the transport profiles (TPP files) of the tp phases for customer transport integration. This default parameter CTC=1 activates the client-specific transport control for all managed systems and enables the transport routing for multiple clients in the update procedure.

The parameter mainimp_proc must have the value 1.

• If you want to import your customer transport requests only without performing a standard update procedure, select the scenario category without stack configuration file and choose Customer Transport Integration only in the next dialog.

• If you want to import your customer transport requests during the update, select the scenario category with stack configuration file and specify the stack.xml file (name including path). In a further initial dialog concerning the additional parameters, select the Consider Customer Buffer File checkbox in the Customer Transport Integration section. A subsequent dialog prompts you to enter the path and the name of the buffer file that contains customer transports for the target release.

For more information, see Making Entries for Scenarios with Configuration File.

If you have chosen a scenario with stack configuration file and selected that SUM shall consider a customer buffer file, the dialog shows the already entered path and name of the transport buffer file. If necessary, you can change it.

Otherwise, provide here path and name of the transport buffer file, which contains the customer transports to be included.

For the transport profile, preselected values are taken over from the transport profile file. However, you can override the preset value of parameter VERS_AT_IMP by defining in this dialog that SUM creates the transport profile versions at import time. Note that this option can prolong the update procedure.

Your entries are validated later on in phase ADJUSTPRP. If the validation is successful, no further action is required. Otherwise, the corresponding dialogs are displayed.

If necessary, the dialogs for including SPDD or SPAU transport requests are displayed in the SUMASK_SPDD_SPAU phase.