The transport profile is a global parameter file for the program tp and is administrated by the SAP System using the Transport Management System (TMS).
The profile is in the transport directory bin.
The profile name corresponds to the convention TP_<domain>.PFL, where <domain> is the name of the transport domain configured in TMS. (You can find the domain in the initial screen of transaction STMS.)
You control the program tp using the transport profile.
Each time tp is started, it must know the location of the global parameter file. You can specify the location with pf=... (see Using a Special Transport Profile under tp Options).
tp pf=/usr/sap/trans/bin/TP_DOMAIN_PRD.PFL import all P11
tp pf=\\<HOST1>\sapmnt\trans\bin\TP_DOMAIN_PRD.PFL import all P11
IBM eServer iSeries:
tp ‘pf=/usr/sap/trans/bin/TP_DOMAIN_PRD.PFL import all P11’
If the transport profile is not specified in this way, tp searches for the transport profile in the current directory.
The transport profile contains the following information:
· Databases from various target systems
· Parameters describing the frequency of the transport
· Additional information for system maintenance
Every line in a transport profile that is not preceded by a # contains a parameter definition.
The various parameters in the transport profile have the following validity:
· Global (for all SAP Systems in your network)
· Local (only for one SAP System)
· Operating system-dependent
If a parameter does not have a specified value, the SAP System uses the default value. Global parameters override defaults. Local parameters override global parameters. You can therefore specify a parameter value for all but one SAP System and a different value for one special system.
Pure parameter definitions such as <parameter>=<value> are always evaluated. However, you can limit the validity of the SAP System parameters in different ways. You can set restrictions for a particular SAP System, an operating system or database system. tp reads transport profile from beginning to end and skips all the entries that are not relevant. If a parameter for the current environment (<SAPSID>, operating system, and database system) occurs more than once, the last value read is used.
If a parameter is preceded by an SAP System name, this assignment is only valid for this SAP system. The way in which the SAP system name is separated from the parameters indicates that the name used in the prefix is the name of an SAP system. SAP System names and parameters must be separated by /: <sapsid>/<parameter>=<value>
You can also restrict the use of a parameter value to a certain operating system. You must place an acronym for the name of the operating system in front of the parameter. The special separator in this case is |: <cpu>|<parameter>=<value>
Permitted acronyms for various operating systems are: aix, hp-ux, osf1, sinix, sunos, wnt (Windows), and as4 (iSeries).
To limit the use of the value to a particular database, an acronym for the name of the database system must be placed before the parameter. Here, the special separator is the “:” character.
Acronyms that are supported for the different database systems are:
ora (Oracle), inf (INFORMIX), ada (MaxDB), mss (Microsoft SQL-Server), db2 (DB2 for OS/390), db4 (DB2 UDB for iSeries), db6 (DB2 UDB for Unix and Windows).