File Naming Conventions for tp (SAP Library - Change and Transport System)

File Naming Conventions for tp

SAP designed tp taking into consideration that it has to run on many different operating systems. For this reason, tp requires restrictive file naming conventions. The naming restrictions ensure that file names are the same in different systems, allowing you to navigate more easily in heterogeneous networks.

Buffer Names

The buffer for the SAP System T11 is, for example, represented by a T11 file in the buffer directory.

Log File Names

All log files are located in the log directory. The name of a log file consists of the name of the change request, the executed step, and the SAP System in which the step was executed:

Possible values for <action> are:

A: Activate Dictionary

D: Import application-defined objects

E: R3trans export

G: Generate reports and screens

H: R3trans Dictionary import

I: R3trans main import

L: R3trans Import the command file

M: Activate enqueue modules

P: Test import

R: Execute XPRA programs after PUT (XPRA)

T: R3trans import of table entries

V: Set version flag

X: Export application-defined objects

There are also logs for the transport steps that are not executed for a special request. In this case, the log names follow another convention:

The date has the format YYMMDD. There are two positions each to define the year, month, and day. The following actions are affected by this:

C: Copying the SAP Kernel

DS: Distribution program flow

N: Structure conversion

O: Starting/stopping the database

P: Moving the nametabs

S: Starting/stopping the SAP System

Data File Names

All data files are located in the transport directory data . The name of a data file consists of the name of the change request, and a code letter. The code letter distinguishes between data files generated by R3trans or by application programs for application-specific development environment objects (ADOs):

R <6 digits>.<source system> R3trans

D <6 digits>.<source system> application programs

Change Request Information File

The change request information file contains information about a change request, including the transport type and the class of the objects to be transported. It also has information on the steps required for the change request, exit codes, and the time of execution.

The information file is located in the cofiles directory. The name is derived from the name of the change request:

K <6 digits>.<source system>