In order to take advantage of the functionality of the AE interface, functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… 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 " packageA Package is an instance (a version, a revision, a tag, …) of your application and defines the content which you want to deploy. Here you decide, if you want to deploy the entire application or just a few specified components. of the SAP System:
Name ranges are transported along with function modules in separate transport requests. A listShows entities in a grid view 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:
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 environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications. are written in UNIX language ("/"). For Windows environments, the names are the same with the exception that thy use a "\" character.
If the functionality of the AE interface is used, function modules must be transported to the SAP system.
All activitiesDeployment-related 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 OverviewThe UserInterface window that contains information about the Automation Engine system.
(Transaction SM50).
To import development objects, the Transport demon must be planned for in clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type. 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.
Import the supplied transport files to the SAP transport environment:
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.
Importing the delivery into the SAP system:
cd
usr/sap/trans/data....... Change to SAP transport directory.
r3trans -l RNNNNNN.SID...... Create a file trans.log
(List of transported objects).
cd
usr/sap/trans/bin........ Change to SAP transport directory.
tp addtobuffer SIDkNNNNNN TID
[pf=<Profile
name, Default TPPARAM>
tp showbuffer TID [pf=<Profile name, Default TPPARAM>
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.
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.
Control:
G...
Report and screen generation
H... R3TRANS import Dictionary
I... R3TRANS main import
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |