In this section: Reference: |
The Server requires the SAP RFC SDK to communicate with the SAP Application Server. The location of the RFC SDK depends on the platform specific search path.
Environment variable LIBPATH.
Environment variable LIBPATH.
Environment variable LD_LIBRARY_PATH.
If the server does not start, and indicates that some NLS libraries cannot be found, try:
EXPORT NLSUI_7BIT_FALLBACK=YES
You can create synonyms for IDOCs using the method described below. However, while the adapter can read an external file that represents an IDOC, users are responsible for generating the external file and providing the DCB attributes associated with that external file. For information on specifying DCB attributes for a flat file representation of an IDOC, see the FILEDEF Command Under UNIX, Windows, IBMÂ i, z/OS, and OpenVMS topic in the Stored Procedures Reference manual.
To create a synonym for SAP/R3 IDOC, a stored procedure (FOCEXEC) is supported, as shown in the following example:
CREATE SYNONYM i47_idocs/MATMAS03_edioff FOR MATMAS03 IDOC EDIOFF DBMS SQLSAP AT I47 DROP END
You will use SAP GUI to logon to SAP and prepare the environment.
A Developer Key is required for the SAP user ID of the administrator. (The system prompts for the Developer Key if it has not been entered previously.)
USER IDs are required for authorization, with variations in privilege assignments based on the nature of the users responsibilities. Basic privileges are assigned to users who only need to execute procedures (focexecs). Administrative privileges are assigned to users who need to perform a variety of administrative functions for the Adapter for SAP. For example, the Adapter for SAP generates ABAP/4 programs dynamically at run time. This is done using adapter components uploaded into the SAP system during the configuration of the adapter, a task that requires administrative privileges.
For related information, refer to the following lists of processing objects: List of Authorization Objects, Fields, and Required Values for USER and List of Authorization Objects for Background Processing .
The following charts reflect any differences that apply for basic users and adapter administrators.
S_RFC: Authorization check for RFC access
Field |
Value |
---|---|
ACTVT (Activity) |
16 (Execute) |
RFC_NAME (Name of RFC to be protected) |
For administrators: AQRC, SDTX, SLST, SUTL, SYST, Z*** For basic users: SYST, Z*** |
RFC_TYPE (Type of RFC object to be protected) |
FUGR (function group) |
S_TCODE: Authorization check for Transaction Start
Field |
Value |
---|---|
TCD (Transaction code) |
For administrators: S001, SE09, SE11, SE11_OLD, SE13, SE37, SE38, SE80, SU53 For basic users: S001, SE37, SE38, SU53 |
S_ADMI_FCD: System Authorizations
Field |
Value |
---|---|
S_ADMI_FCD (System administration functions) |
For administrators: MEMO |
S_C_FUNCT: C Calls in ABAP Programs
Field |
Value |
---|---|
ACTVT (Activity) |
For administrators: 16 (Execute) |
CFUNCNAME (Name of a CALLable C routine) |
For administrators: SYSTEM |
PROGRAM (ABAP program name) |
For administrators: SAPLSTRF, SAPLSTRI |
S_DATASET: Authorization for File Access
Field |
Value |
---|---|
ACTVT (Activity) |
For administrators: 33, 34, A6 |
FILENAME (Physical file name) |
For administrators: * |
PROGRAM (ABAP program name) |
For administrators: * |
S_TABU_DIS: Table Maintenance (via standard tools such as SM30)
Field |
Value |
---|---|
ACTVT (Activity) |
For administrators: 03 |
DICBERCLS (Authorization group) |
For administrators: SS, &NC& |
S_DEVELOP: ABAP Workbench
Field |
Value |
---|---|
ACTVT (Activity) |
For administrators: 01, 02, 03, 07, 16, 40 |
DEVCLASS: Development class for transport system |
For administrators: * |
OBJNAME: Object name |
For administrators: * |
OBJTYPE: Object type |
For administrators: DEVC, FUGR, PROG, TABL, TABT |
P_GROUP: Authorization group with ABAP programs |
For administrators: * |
S_TRANSPORT: Transport Organizer
Field |
Value |
---|---|
ACTVT (Activity) |
For administrators: 01 |
TTYPE (Request type (Change and Transport System)) |
For administrators: DTRA, TASK |
Field |
Value |
---|---|
S_BTCH_ADM |
N (unless you want the user to have administrative rights for Background jobs) |
S_BTCH_JOB |
RELE |
How to:
Reference: |
The Adapter for SAP generates ABAP/4 programs dynamically at run time. This is done using adapter components uploaded into the SAP system during the configuration of the adapter. Prior to uploading the components, the SAP system has to be prepared.
To prepare the SAP environment for the adapter components, perform the following steps:
If the list is empty, create a new entry.
In the Application Server field, type either the SAP application server network name or IP address.
Click OK to create a new entry on the Logon list.
A logon page prompting for a user ID and password appears. Logon to the system. Note that if the user ID is being used for the first time, the system will ask for the password to be changed.
Note: If you are using Release 4.7, create a Package instead of a Development Class.
Note: The Development Class or Package name can be a maximum of 14 characters and must follow SAP naming conventions for customer objects.
The system responds: Development Class or Package ZIBI does not exist.
The system generates a unique Change and Transport System (CTS) request #.
The system responds: Function Group ZIBI does not exist.
This procedure applies only to SAP Release 4.7.
The object window shows an open folder with the name of the function group and a closed folder named Includes.
The object window shows an open folder with the name of the function group and a closed folder named Includes.
A new window lists all inactive objects. Note that the object name now begins with SAPL.
Make sure the object for the function group ZIBI is selected.
You should get a report with 0 errors, 0 warnings, and 0 messages.
Note: If you encounter errors or warnings during this step, resolve them at the SAP layer before continuing with the installation of the Adapter for SAP.
The SAP environment is now prepared for the next step of function module upload from the Web Console.
During the installation of the SAP adapter, a set of function modules, including some temporary objects like ZXXXBTCH and ZXXXREPTS, are uploaded and registered in the SAP repository. In preparation for the transport from the QA to DEV to PROD application servers, the ZXXXBTCH object must be assigned to the ZXXX development class. Otherwise, ZXXXBTCH will be assigned to the development class $TMP or remain unassigned, either of which can cause the transport to fail.
SAP provides a transport control program (tp) to handle release upgrades and transports among SAP systems. The transport control program:
During an export, the objects to be transported are extracted from the database of the source system and stored in files of the operating system.
During the import, the objects are added to the database of the target system (according to the transport function recorded in the task).
Note: For detailed technical background, refer to http://help.sap.com.
iWay Software |