Knowledge Base > Automation Engine and Target Systems > SAP > Transporting the AE Interface

Transporting the Automation Engine Interface

General

In order to take advantage of the functionality of the AE interface, function modules must be transported to the SAP system.

Function modules are developed as ABAP development objects. These components are supplied with the "Correction & Transport System " package of the SAP System:

KNNNNNN.SID information file, for example K000046.T45
RNNNNNN.SID data file, for example R000046.T45
ENNNNNN.txt export protocol, for example E000046.txt

Name ranges are transported along with function modules in separate transport requests. A list of all currently valid transport requests is found in the file TRANSPRT.TXT. All transports must take place when a new installation is made. With an update installation, it is only the function modules (AE interface) because there is no change of the name ranges.

The names of the development objects are described in Terminology.

Throughout this document, the following codes are used:

NNNNNN for the transport job number of the delivery system and
SID for the system names of the delivery system.
TID is used for the system name of the target system (to which the function modules are imported).

File Names

SAP can be installed in various environments (UNIX, Windows...). Therefore, it is important to consider the specific features of the system when you name the files.

In this document, the file names that refer to a SAP environment are written in UNIX language ("/"). For Windows environments, the names are the same with the exception that thy use a "\" character.

Importing Function Modules in SAP

If the functionality of the AE interface is used, function modules must be transported to the SAP system.

Requirements:

All activities that concern the transport system must be made by a SAP administrator (SIDadm).

The transport system must be properly installed and set. This takes place during the installation of the SAP system.

In this case, importing requires that at least 2 batch work processes (BTC) are running.
Control: Tools - Administration - Monitor - System Control - System Overview (Transaction SM50).

To import development objects, the Transport demon must be planned for in client 000 (background job "RDDIMPDP") and cleared for the SAP system. Control: see below

The functionality can be checked as follows:
cd usr/sap/trans/bin........ Change to the SAP transport directory.
tp checkimpdp TID........... Verify that the Transport demon RDDIMDP is active in SAP.
tp connect TID.............. Test the connection to the SAP system.

The transport system is described in the SAP online documentation in the chapter BASIS - TRANSPORT CONTROL.

Note that the import process requires the option "Ignore Non-Matching Component Versions" to be set.

Procedure:

Import the supplied transport files to the SAP transport environment:

On the SAP computer:
Change to the appropriate subdirectory (for the SAP version) in IMAGE:AGENTS\SAP\_TRANS:
Copy the files from there to the following directory:
KNNNNNN.SID by /usr/sap/trans/cofiles
RNNNNNN.SID by /usr/sap/trans/data

If SAP is installed under UNIX, the files are usually transferred via FTP. Be sure to enter "bin" for binary transfers.

The file ENNNNNN.TXT on the CD contains the complete export log and can be used for analysis.

Importing the delivery into the SAP system:

On the SAP computer (use the SAP administrator (SIDadm) to register).
The imported transport files (RNNNNNN.SID and KNNNNNN.SID) must not be write protected (be careful when you copy them from the CD).
If needed, you can create a directory that includes all objects of the transport job:
cd usr/sap/trans/data....... Change to SAP transport directory.
r3trans -l RNNNNNN.SID...... Create a file trans.log (List of transported objects).

Create a buffer entry for the target system.
cd usr/sap/trans/bin........ Change to SAP transport directory.
tp addtobuffer SIDkNNNNNN TID [pf=<Profile name, Default TPPARAM>

If needed, you can check the buffer entry:
tp showbuffer TID [pf=<Profile name, Default TPPARAM>
Before you start to import, decide upon the unconditional modes (u) that should be used:

4....valid only for SAP Release 3.x: guarantees that the target system name (TID) that is used for the export does not correspond to the actual target system name. This mode must be used because the actual target system is not known.
1....must be entered when the import should be repeated.

Start the import using one of the following commands:
tp import SIDkNNNNNN TID u4 client123] [pf=<Profile name, default TPPARAM>] or
tp import SIDkNNNNNN TID u14 client123] [pf=<Profile name, default TPPARAM>]
The unconditional modes are distinguished by TP version and can be checked in the SAP Documentation if needed.
Note for the import process:

This process requires that at least 2 batch tasks are running.
Although the transport job does not include client-specific data, it can happen that a client is required. In this case, enter a valid client=nnn (client 010 is used for the export).
The import can take a few minutes, especially if the Transport demon RDDIMPDP is planned not to be event-triggered but rather time-controlled.
Message "no profile used ":
No profile is specified if you call an internal program on "sapevt". That is the reason why this message occurs with any call on sapevt. Usually, it can be ignored.
Other messages can occur. Only the return code is crucial (see below - Control).

Control:

Because of the SAP transport system's and the SAP environment's complexity, thorough error diagnosis and correction can only be handled by an expert who is familiar with installation environments.
A general assessment as to whether the import was successful should be possible for a non-expert with the following tips:

Importing creates logging files.
These are in the directory /usr/sap/trans/log and are called SIDsNNNNNN.TID
s means transport step:
G... Report and screen generation
H... R3TRANS import Dictionary
I... R3TRANS main import
In these three log files the exit code (=return code) has to be checked (it always occurs at the end of the file). It cannot exceed "4"!

The expert can also check the log files in the SAP system.