Start of Content Area

Object documentation Log File ALOG  Locate the document in its SAP Library structure


This file contains individual return codes for all the transport steps performed in the transport directory.

The file ALOG resides in the log subdirectory of the transport directory. You can define the name in the transport profile (file in the bin subdirectory of the transport directory). The default value is ALOG$(syear)$(yweek) . Two characters refer to the current year and two characters to the current week.

For more information on naming conventions, see File Naming Conventions for tp.


The entries in the file are represented in the form of a table. All lines are subdivided into eight columns that are separated by a blank character.

Most transport steps are assigned to a particular change request. In this case, the change request is in this column. If a transport step cannot be assigned to a change request, ALL is always entered in this column.

Whenever the import command is called, the conversion program checks if one of the imported change requests contains a modification to the ABAP Dictionary that requires a table conversion. The table involved is then converted.

The name of the SAP System in which the transport step was performed is in this column.

With extended transport control (see parameter ctc in Global Parameters), the target of a transport step is a client in an SAP System and no longer just an SAP System. The combination of system and client is described here as a logical SAP System.

The value of this column can have 3 characters. In this case, the value specifies only the SAP System. If the value has 7 characters, a logical system in the form <SID>.<CLI> is given. <SID> is the system name and <CLI> the client name. If the transport step affected all the clients, the client can also have the value ALL .

Another possible form is <SID>:<CLI> . In this case (' :' instead of '.'as separator), the transport request contains client-specific objects that were handled in the specified client, and cross-client objects whose import affected all the clients.

Each transport step is uniquely identified by a character. This character is also included in the name of the complete log. For more information on naming conventions, see File Naming Conventions for tp.