SAP Note 13719 - Preliminary transports to customers (note for customers)

Symptom:

An SAP consultant or support representative has made data available to the customers in the form of a note attachment (or - possible until January 2003 - on sapservX) for the import into the customer system (as described in the internal Note 11920).

Other terms

sapserv3 Walldorf
sapserv4 Foster City
sapserv5 Tokyo
sapserv6 Sydney
sapserv7 Singapore

Reason and Prerequisites

As of Release 3.0, preliminary transports (delivery of preliminary corrections) have been delivered in the form of Support Packages. There are also preliminary transports of developments that are imported using the manual procedure described here.

When importing requests from SAP systems, you must ensure that requests in area 900000 - 999999 (for example, Q30K90821), possibly collide with customized transports, especially if there are customer systems with the same name (in the example, this would be Q30). These jobs should be rejected if the names are the same.

In systems with Releases older than 4.6C the following is important: When you import jobs from SAP systems, note that jobs in the range 900000 - 999999 (for example Q30K900821) are treated as customer- specific transports. The transport objects are considered modified. Such jobs should therefore be rejected if the system is older than 4.6C. As of Release 4.6C, this restriction does not apply.

The transport properties will be imported with the transported objects. After the import the original system will therefore no longer be SAP but for example, P30 if the export was carried out in P30. As user DDIC, you can maintain this in Transaction SM31 in Table TADIR, and change it to SAP again. This is required if a system with the same name as the export system exists in your system landscape.

Solution

Two files are generated when exporting:

• The R3trans file which contains the actual data.

• The transport information file which contains the control-data for the transport.
  

This data has been made available to your either as a note attachment or directly on a sapservX host.

1. Situation: The data is available as a note attachment (procedure as of February 2003).

a) Download the data from the note dealing with preliminary transport, as described in Note 480180.

b) The data is contained either in a ZIP or in a SAR archive that you will need to unpack.

2. Situation: The data is available on sapservX and has to be transferred using ftp. You can find the data in directory general/R3server/abap/note.0012345.

The following describes the procedures for UNIX, WINDOWS, and OS/400.

a) UNIX:

The binary mode MUST be switched on for the data transfer, otherwise the R3trans file will be destroyed.
The customer calls ftp as follows:

cd /usr/sap/trans/tmp /* cd at customer site */
ftp sapservx /* Start file transfer program */
/* Enter 'ftp' as user and password */
cd general/R3server/abap/note.nnnnnnn /* directory */
bin /* Switch to binary mode */
get Rnnnnnn.xxx /* Fetch R3trans data file, name */
/* depends on the transport request.*/
get Dnnnnnn.xxx /* Fetch SDO file if it exists. */
get Knnnnnn.xxx /* Fetch the transport info file. */
bye /* End ftp. */
mv Rnnnnnn.xxx ../data /* Copy R3trans file into data dir. */
mv Dnnnnnn.xxx ../data /* SDO file into the data dir. */ mv Knnnnnn.xxx ../cofiles /* info file into cofiles dir. */

b) Windows
Since the text mode on WINDOWS is different from the text mode on UNIX, using ftp the text files (command files and buffer) have to be transferred in text mode and the data files in binary mode.
Example: Assuming that the transport request is called P21K000123, then the following files have to be transferred in the specified mode using ftp:

Name Contents Mode Target directory Exists
R000123.P21 data bin \usr\sap\trans\data always
K000123.P21 info ascii \usr\sap\trans\cofiles always
D000123.P21 data bin \usr\sap\trans\data only for ADO

It is essential to use the correct mode when transferring data, otherwise the import cannot be carried out successfully.
The customer calls up ftp as follows:
<>
cd \usr\sap\trans\tmp /* cd at the customer site */
ftp sapservX /* start file transfer program */
/* enter 'ftp' as user and password */
cd dist general/R3server/abap/note.0012345 /* directory */
bin /* switch to binary mode */
get Rnnnnnn.xxx /* fetch R3trans data file, name */
/* depends on the transport request */
get Dnnnnnn.xxx /* fetch SDO file, if it exists */
ascii /* switch to text mode */
get Knnnnnn.xxx /* fetch transport info file */
bye /* end ftp */
/* Copy..... */
move Rnnnnnn.xxx ..\data /*R3trans file to data dir. */
move Dnnnnnn.xxx ..\data /*SDO file to data directory */
move Knnnnnn.xxx ..\cofiles /*Info file to cofile directory*/

c) AS/400
Use command APYABFIX: APYABFIX SID() FROMHOST('sapserv3')
FROMDIR('general/R3server/abap/note.0012345')
TRANSPORT('*FROMDIR')
TPIMPORT(*YES)

Replace the place-holders , sapserv3 and note.0012345.
The parameter value TRANSPORT(*FROMDIR) controls the automatic determination of the transport request number while the system searches through the specified directory for transport files. The last parameter TPIMPORT initiates the calls tp 'addtobuffer ...' and tp 'import ...' for the transport request.
If the execution of this command causes the error 'Too many files found in directory' copy the files manually into your data and cofile directory using ftp.

<>
ftp sapservX /* start file transfer program */
/* enter 'ftp' as user and password */
cd dist general/R3server/abap/note.0012345
/* to change to the directory that */
/* contains the transport */
namefmt 1
/* to access the file system of AS/400 */
lcd '/usr/sap/trans/data'
/* change to the transport data directory locally*/
bin /* Switch to binary mode */
get Rnnnnnn.xxx /* fetch R3trans data file, name of */
/* file depends on transport request. */
get Dnnnnnn.xxx /* fetch SDO file if it exists. */
lcd '/usr/sap/trans/cofiles'
/* change to cofile directory locally */
ascii /* following transfer in text mode */
get Knnnnnn.xxx /* fetch transport info file. */
quit /* end ftp. */

Manual import of the transports:
Logon as OFR
tp 'pf= addtobuffer '
tp 'pf= import U26'

Starting the import:

• Start the import as follows:

a) UNIX:
as user adm:
/usr/sap//SYS/exe/run/tp addtobuffer \
pf=
/usr/sap//SYS/exe/run/tp import U26 \
pf=

Replace with the current SID, for example, C11.
Example:
/usr/sap/C11/SYS/exe/run/tp addtobuffer P21K000123 C11 pf=/usr/sap/trans
/bin/TP_DOMAINABC.PFL
/usr/sap/C11/SYS/exe/run/tp import P21K000123 C11 U26 pf=/usr/sap/trans
/bin/TP_DOMAINABC.PFL

b) Windows:
as user adm:
cd \usr\sap\trans\bin
\usr\sap\\SYS\exe\run\tp addtobuffer
\usr\sap\\SYS\exe\run\tp import U26
Replace by the current SID which is for example C11.
Example:
cd \usr\sap\trans\bin
\usr\sap\C11\SYS\exe\run\tp addtobuffer P21K000123 C11
usr\sap\C11\SYS\exe\run\tp tst P21K000123 C11
\usr\sap\C11\SYS\exe\run\tp import P21K000123 C11 U26

c) AS400: Already completed by the command above.

• A prerequisite for the import is that the periodic background job RDDIMPDP has been scheduled in the target system (see manual BC System Administration, Appendix D).

• Specifying unconditional modes 2 and 6 (u26) results in original objects and objects in unconfirmed repairs being overwritten as well. If the "tp tst" call (test import) ends with return code 8 as a result of such objects, we recommend the release of the open repairs before the import so that the corresponding versions of the modified objects will be generated in the version database.