Additional Information for SAP ABAP ERP Adapter

B Additional Information for SAP ABAP ERP Adapter

For connecting to the SAP system, you need to configure certain privileges. Also, it is possible to test the connection outside of ODI using a standalone java utility.

This appendix includes the following sections:

For more information about the SAP ERP KMs, see Connectivity and Knowledge Modules Guide for Oracle Data Integrator Developer's Guide.

SAP ABAP ERP Required Privileges

An SAP dialog user is required for connecting to the SAP system, for the LKM execution during development. A SAP RFC user is not sufficient.

During development, this user must have a developer license key. License keys can be retrieved from http://service.sap.com. Any execution attempts without this developer license key will lead to failure and may cause the need for clean-up operations.

For RKM and LKM execution in production, an SAP RFC user is sufficient.

These SAP user types can be used for the following operations:

Table B-1 Required SAP User Types

Operation	Required SAP User Type
RKM: Setup	SAP Dialog user
RKM: Reverse Engineering	SAP Dialog user or SAP RFC user
LKM: Development	SAP Dialog user or SAP RFC user
LKM: Production	SAP Dialog user or SAP RFC user

Authorizations for ECC6 Servers

The following tables list the privileges required for using SAP ABAP Knowledge Modules:

Important points to consider

Consider the following points while configuring the SAP privilieges:

S_DATASET is an authorization object that controls access to physical file, so you need to provide access to SAP directories & folder mounted path. The values provided here are sample paths, you need to provide your landscape directories path or provide *(all).
NR or (NR) means NOT REQUIRED.

Authorizations Required for RKM SAP ERP Upload

The following SAP authorizations are required only in rare cases, when explicitly requested by Oracle product support. For standard installations, these authorizations are not required.

Note:

Developer key is required in this authorization.

Object	Field Name	Value (ECC6-EHP3)	Value (ECC6-EHP7)
`S_RFC`	`ACTVT`	`16`	`16`
`S_RFC`	`RFC_NAME`	`RFC1, SDIFRUNTIME, SUTL, SYST, ZODI_FGR_PROD*, ZODI_FGR`	`RFC1, SDIFRUNTIME, SUTL, SYST, ZODI_FGR_PROD*, ZODI_FGR`
`S_RFC`	`RFC_TYPE`	`FUGR`	`FUGR`
`S_TCODE`	`TCD`	`SU53,SE38`	`SE38, WE30, SU53`
`S_ADMI_FCD`	`S_ADMI_FCD`	`NR`	`RFCA`
`S_CTS_ADMI`	`CTS_ADMFCT`	`TABL`	`TABL`
`S_CTS_SADM`	`CTS_ADMFCT`	`NR`	`TABL`
`S_CTS_SADM`	`DESTSYS`	`NR`	`*`
`S_CTS_SADM`	`DOMAIN`	`NR`	`*`
`S_DATASET`	`ACTVT`	`34`	`33, 34`
`S_DATASET`	`FILENAME`	`*`	`*`
`S_DATASET`	`PROGRAM`	`SAPLSTRF`	`*`
`S_TABU_DIS`	`ACTVT`	`03`	`02, 03`
`S_TABU_DIS`	`DICBERCLS`	`*`	`*`
`S_TABU_NAM`	`ACTVT`	`NR`	`02, 03`
`S_TABU_NAM`	`TABLE`	`NR`	`*`
`S_DEVELOP`	`ACTVT`	`01, 02, 03`	`01, 02, 03, 06`
`S_DEVELOP`	`DEVCLASS`	`$TMP, ZODI_LKM_PCKG, ZODI_RKM_PCKG`	`$TMP, ZODI_LKM_PCKG, ZODI_RKM_PCKG`
`S_DEVELOP`	`OBJNAME`	`Z$$$XRFC, ZODI*`	`Z$$$XRFC, ZODI*`
`S_DEVELOP`	`OBJTYPE`	`DEVC, FUGR, FUNC, PROG`	`DEVC, FUGR, FUNC, PROG`
`S_DEVELOP`	`P_GROUP`		`''`
`S_PROGRAM`	`P_ACTION`	`NR`	`BTCSUBMIT, SUBMIT, VARIANT`
`S_PROGRAM`	`P_GROUP`	`NR`	`*`
`S_SYS_RWBO`	`ACTVT`	`NR`	`01, 02, 03, 05, 06, 23`
`S_SYS_RWBO`	`DESTSYS`	`NR`	`*`
`S_SYS_RWBO`	`DOMAIN`	`NR`	`''`
`S_SYS_RWBO`	`TTYPE`	`NR`	`DTRA`
`S_TRANSPRT`	`ACTVT`	`01,03`	`01, 02, 03, 06`
`S_TRANSPRT`	`TTYPE`	`DTRA,TASK`	`*`
`S_IDOCDEFT`	`ACTVT`	`NR`	`03`
`S_IDOCDEFT`	`EDI_CIM`	`NR`
`S_IDOCDEFT`	`EDI_DOC`	`NR`
`S_IDOCDEFT`	`EDI_TCD`	`NR`

Authorizations Required for RKM SAP ERP Execution

The following SAP authorizations are required for reverse engineering the SAP models using RKM SAP ERP.

Object	Field Name	Value (ECC6–EHP3)	Value (ECC6–EHP7)
`S_RFC`	`ACTVT`	`16`	`16`
`S_RFC`	`RFC_NAME`	`RFC1, SDIFRUNTIME, SUTL, SYST, ZODI_FGR_PROD*, ZODI_FGR`	`RFC1, SDIFRUNTIME, SUTL, SYST, ZODI_FGR_PROD*, ZODI_FGR`
`S_RFC`	`RFC_TYPE`	`FUGR`	`FUGR`
`S_TCODE`	`TCD`	`SU53, SE38`	`SU53, SE38`
`S_CTS_ADMI`	`CTS_ADMFCT`	`NR`	`TABL`
`S_DATASET`	`ACTVT`	`NR`	`34`
`S_DATASET`	`FILENAME`	`NR`	`*`
`S_DATASET`	`PROGRAM`	`NR`	`SAPLSTRF`
`S_TABU_DIS`	`ACTVT`	`03`	`02, 03`
`S_TABU_DIS`	`DICBERCLS`	`*`	`*`
`S_TABU_NAM`	`ACTVT`	`NR`	`02, 03`
`S_TABU_NAM`	`TABLE`	`NR`	`*`
`S_TRANSPRT`	`ACTVT`	`01, 03`	`01, 03`
`S_TRANSPRT`	`TTYPE`	`DTRA, TASK`	`DTRA, TASK`

Authorizations Required for LKM SAP ERP Upload

The following SAP authorizations are required for running mappings using the SAP ERP LKMs in SAP development environment, with Upload ABAP Option Enabled.

Note:

Developer Key is required in this authorization.

Object	Field Name	Value (ECC6-EHP3)	Value (ECC6-EHP7)
`S_RFC`	`ACTVT`	`16`	`16`
`S_RFC`	`RFC_NAME`	`RFC1, SDIFRUNTIME, SYST, ZODI_FGR, ZODI_FGR_PROD_*`	`RFC1, SDIFRUNTIME, SYST, ZODI_FGR, ZODI_FGR_PROD_*`
`S_RFC`	`RFC_TYPE`	`FUGR`	`FUGR`
`S_TCODE`	`TCD`	`SE38, SU53`	`SE38, SU53`
`S_ADMI_FCD`	`S_ADMI_FCD`	`RFCA, SFTP`	`RFCA, SFTP`
`S_BTCH_ADM`	`BTCADMIN`	`Y`	`Y`
`S_BTCH_JOB`	`JOBACTION`	`RELE`	`RELE`
`S_BTCH_JOB`	`JOBGROUP`	`' '`	`' '`
`S_CTS_ADMI`	`CTS_ADMFCT`	`TABL`	`TABL`
`S_DATASET`	`ACTVT`	`06,33,34`	`06,33,34`
`S_DATASET`	`FILENAME`	`*`	`*`
`S_DATASET`	`PROGRAM`	`*`	`SAPLSLOG, SAPLSTRF, SAPLZ, ZODI`
`S_DEVELOP`	`ACTVT`	`1`	`1`
`S_DEVELOP`	`DEVCLASS`	`*`	`*`
`S_DEVELOP`	`OBJNAME`	`ZODI*`	`ZODI*`
`S_DEVELOP`	`OBJTYPE`	`FUGR, FUNC`	`FUGR, FUNC`
`S_DEVELOP`	`P_GROUP`	`NR`
`S_TRANSPRT`	`ACTVT`	`01, 02`	`01, 02`
`S_TRANSPRT`	`TTYPE`	`DTRA,TASK`	`DTRA,TASK`
`S_APPL_LOG`	`ACTVT`	`6`	`6`
`S_APPL_LOG`	`ALG_OBJECT`	`ZODI_APPOBJ`	`ZODI_APPOBJ`
`S_APPL_LOG`	`ALG_SUBOBJ`	`ZODI_SUBOBJ`	`ZODI_SUBOBJ`
`S_TABU_DIS`	`ACTVT`	`3`	`3`
`S_TABU_DIS`	`DICBERCLS`	`*`	`*`

Authorizations Required for LKM SAP ERP Execution

The following SAP authorizations are required for running mappings using the SAP ERP LKMs in a SAP production environment, when LKM option Upload Abap Code is disabled (QA or Production).

Object	Field Name	Value (ECC6-EHP3)	Value (ECC6-EHP7)
`S_RFC`	`ACTVT`	`16`	`16`
`S_RFC`	`RFC_NAME`	`RFC1, SDIFRUNTIME, SYST, ZODI_FGR_PROD*`	`RFC1, SDIFRUNTIME, SYST, ZODI_FGR_PROD*`
`S_RFC`	`RFC_TYPE`	`FUGR`	`FUGR`
`S_ADMI_FCD`	`S_ADMI_FCD`	`SFTP`	`SFTP`
`S_BTCH_ADM`	`BTCADMIN`	`Y`	`Y`
`S_BTCH_JOB`	`JOBACTION`	`RELE`	`RELE`
`S_BTCH_JOB`	`JOBGROUP`	`' '`	`' '`
`S_DATASET`	`ACTVT`	`06,33,34`	`06,33,34`
`S_DATASET`	`FILENAME`	`*`	`*`
`S_DATASET`	`PROGRAM`	`SAPLSLOG, SAPLSTRF, SAPLZODI, ZODI, SAPLZODI_FGR_PROD*`	`SAPLSLOG, SAPLSTRF, SAPLZODI, SAPLZODI_FGR_PROD, ZODI*`
`S_TRANSPRT`	`ACTVT`	`01, 02`	`01, 02`
`S_TRANSPRT`	`TTYPE`	`DTRA, TASK`	`DTRA, TASK`
`S_APPL_LOG`	`ACTVT`	`6`	`6`
`S_APPL_LOG`	`ALG_OBJECT`	`ZODI_APPOBJ`	`ZODI_APPOBJ`
`S_APPL_LOG`	`ALG_SUBOBJ`	`ZODI_SUBOBJ`	`ZODI_SUBOBJ`

SAP Connection Test

This connection test should be performed after configuring the SAP ABAP data server in the topology.

This test preforms the following operations:

It establishes a test connection to the configured SAP system.
It validates the proper setup of SAP JCo by displaying the About dialog.

This test is performed using an RKM called RKM SAP ERP Connection Test. This KM does not perform any reverse operation. It simply runs the connection test.

To run the connection test:

Create an SAP ERP Model based on the SAP ABAP technology and on the SAP ABAP logical schema using the standard procedure, as described in Creating a Model of the Developing Integration Projects with Oracle Data Integrator.
In the Reverse Engineer tab of the SAP ERP Model, select the RKM SAP ERP Connect Test.
Save the model.
Click Reverse-Engineer to start the reverse.

Within a few seconds, the SAP JCo About dialog should appear. If not, review the session execution log in the Operator Navigator. Please verify that the output of task "Test SAP Connection" contains Successfully connected to SAP System. If not, the connection test has failed and the connection problem must be analyzed.

SAP Stand-Alone Connection Test

In addition to the Connection Testing, a test can be performed outside of ODI using a standalone java utility. This utility is available with the Standalone agent.

To use a standalone java utility to test the connection:

Open a command window.
Go to the <ODI_HOME>/odi/sdk/lib directory.
Make sure that JAVA_HOME points to a supported JVM.
Make sure that you have installed SAP Java Connector and that the sapjco3.jar and the sapjco3 library are in the <ODI_HOME>/odi/sdk/lib directory.
Launch the utility using the following command:

On Windows:

java -cp sapjco3.jar;odi-sap.jar oracle.odi.sap.km.test.JCoTest

On Linux/UNIX:

java -cp sapjco3.jar:odi-sap.jar oracle.odi.sap.km.test.JCoTest

This command generates a ODI_SAP_CON_POOL.jcoDestination file in the folder <ODI_HOME>/odi/sdk/lib folder.

For more information, see Appendix C, SAP Stand-Alone Connection Test in the Getting Started with SAP ABAP ERP Adapter for Oracle Data Integrator.

Use a text editor to open the ODI_SAP_CON_POOL.jcoDestination file. This file should look as follows:

#for tests only!
jco.client.lang=EN
jco.destination.peak_limit=10
jco.client.client=800
jco.client.passwd=<SAP Password>
jco.client.user=<SAP User>
jco.client.sysnr=00
jco.destination.pool_capacity=5
jco.client.ashost=<SAP Application Server>

Enter you SAP connection information, which you have received from your SAP administrator.
Launch the utility using the same command. The utility uses the file that you have edited, and outputs the test results or the possible issues.

In addition to just testing the SAP connection, the utility will also validate the existence of certain Function Modules required for the RKM.
Delete the ODI_SAP_CON_POOL.jcoDestination file after execution, as it contains the SAP login credentials.