1. Application Adapters Guide for Oracle Data Integrator
  2. Additional Information for SAP ABAP BW Adapter

A Additional Information for SAP ABAP BW 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 BW KMs, see Connectivity and Knowledge Modules Guide for Oracle Data Integrator Developer's Guide.

SAP ABAP BW Required Privileges

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

This user has to 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.

Later for RKM execution and LKM execution in production a SAP RFC user is sufficient.

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

Table A-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

Testing ODI Generated Extraction RFCs

SAP Dialog user or SAP RFC user

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

Important points to consider

Consider the following points while configuring the SAP privileges:

  • 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 BW 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 (BI 7.0) Value (BI 7.5)

S_RFC

ACTVT

16

16

S_RFC

RFC_NAME

RFC1, RSAB, RSB3RD, SDIFRUNTIME, SUTL, SYST, SYSU, ZODI*

RFC1, RSAB, RSB3RD, SDIFRUNTIME, SUTL, SYST, SYSU, ZODI*, RSBAPI_IOBJ

S_RFC

RFC_TYPE

FUGR

FUGR

S_RFCRAIAR

RFC_RAIAR

NR

16

S_TCODE

TCD

SU53, SE38

SU53, SE38

S_ADMI_FCD

S_ADMI_FCD

RFCA

RFCA

S_CTS_ADMI

CTS_ADMFCT

TABL

TABL

S_DATASET

ACTVT

06,33,34

06,33,34,A7

S_DATASET

FILENAME

*

*

S_DATASET

PROGRAM

SAPLSLOG, SAPLSTRF, SAPLZODI*

*

S_TABU_DIS

ACTVT

3

2,3

S_TABU_DIS

DICBERCLS

*

*

S_DEVELOP

ACTVT

01,02,03,06,07,16,70,MA

01,02,03,06,07,16,70,MA

S_DEVELOP

DEVCLASS

$TMP,ZODI_LKM_PCKG,ZODI_RKM_PCKG,RSS,ZODI*

$TMP,ZODI_LKM_PCKG,ZODI_RKM_PCKG,RSS,ZODI*

S_DEVELOP

OBJNAME

*

*

S_DEVELOP

OBJTYPE

FUGR,PROG,DEVC,DEBUG

*

S_DEVELOP

P_GROUP

*

*

S_TRANSPRT

ACTVT

01,02,03

01,02,03

S_TRANSPRT

TTYPE

DTRA, TASK

DTRA, TASK

S_RS_ADMWB

ACTVT

03,16

03,16

S_RS_ADMWB

RSADMWBOBJ

INFOOBJECT

INFOOBJECT

S_RS_ICUBE

ACTVT

03

03

S_RS_ICUBE

RSICUBEOBJ

*

*

S_RS_ICUBE

RSINFOAREA

*

*

S_RS_ICUBE

RSINFOCUBE

*

*

S_RS_IOBJ

ACTVT

03

03

S_RS_IOBJ

RSIOBJ

*

*

S_RS_IOBJ

RSIOBJCAT

*

*

S_RS_IOBJ

RSIOBJPART

DEFINITION

DEFINITION

S_RS_ODSO

ACTVT

03

03

S_RS_ODSO

RSINFOAREA

*

*

S_RS_ODSO

RSODSOBJ

*

*

S_RS_ODSO

RSODSPART

DATA,DEFINITION

DATA,DEFINITION

Authorizations Required for RKM SAP BW Execution

The following authorizations are required for RKM SAP BW execution.

Object Field Name Value (BI 7.0) Value (BI 7.5)

S_RFC

ACTVT

16

16

S_RFC

RFC_NAME

RFC1, RSAB, RSB3RD, SDIFRUNTIME, SUTL, SYST, SYSU, ZODI*

RFC1, RSAB, RSB3RD, SDIFRUNTIME, SUTL, SYST, SYSU, ZODI*, RSBAPI_IOBJ

S_RFC

RFC_TYPE

FUGR

FUGR

S_TCODE

TCD

SU53

SU53

S_DATASET

ACTVT

06, 33, 34

06, 33, 34

S_DATASET

FILENAME

*

*

S_DATASET

PROGRAM

SAPLSTRF, SAPLSLOG, SAPLZODI*

SAPLSTRF, SAPLSLOG, SAPLZODI*

S_TABU_DIS

ACTVT

03

03

S_TABU_DIS

DICBERCLS

*

*

S_TRANSPRT

ACTVT

01, 02, 03

01, 02, 03

S_TRANSPRT

TTYPE

DTRA, TASK

DTRA, TASK

S_RS_ADMWB

ACTVT

03,16

03,16

S_RS_ADMWB

RSADMWBOBJ

*

*

S_RS_ICUBE

ACTVT

03

03

S_RS_ICUBE

RSICUBEOBJ

DATA, DEFINITION

DATA, DEFINITION

S_RS_ICUBE

RSINFOAREA

*

*

S_RS_ICUBE

RSINFOCUBE

*

*

S_RS_IOBJ

ACTVT

03

03

S_RS_IOBJ

RSIOBJ

*

*

S_RS_IOBJ

RSIOBJCAT

*

*

S_RS_IOBJ

RSIOBJPART

DEFINITION

DEFINITION

S_RS_ODSO

ACTVT

03

03

S_RS_ODSO

RSINFOAREA

*

*

S_RS_ODSO

RSODSOBJ

*

*

S_RS_ODSO

RSODSPART

DATA, DEFINITION

DATA, DEFINITION

S_RS_AUTH

BIAUTH

0*

0*

Authorizations Required for LKM SAP BW Upload (Background & Foreground)

The following authorizations are required for LKM SAP BW execution in a SAP development environment.

Note:

Developer Key is required in this authorization.

This section contains authorizations for both background and foreground executions.

Object Field Name Value (BI 7.0) Value (BI 7.5)

S_RFC

ACTVT

16

16

S_RFC

RFC_NAME

RFC1, SDIFRUNTIME, SLST, SYST, ZODI*

RFC1, SDIFRUNTIME, SLST, SYST, ZODI*

S_RFC

RFC_TYPE

FUGR

FUGR

S_TCODE

TCD

SE38,SU53

SE38,SU53

S_DEVELOP

ACTVT

1, 2, 3, 6, 7, 16

1, 2, 3, 6, 7, 16

S_DEVELOP

DEVCLASS

*

*

S_DEVELOP

OBJNAME

*

*

S_DEVELOP

OBJTYPE

FUGR, FUNC, PROG*, SUSO

FUGR, FUNC, PROG*, SUSO

S_DEVELOP

P_GROUP

NR

NR

S_PROGRAM

P_ACTION

BTCSUBMIT, SUBMIT, VARIANT

BTCSUBMIT, SUBMIT, VARIANT

S_PROGRAM

P_GROUP

NR

NR

S_TRANSPRT

ACTVT

1, 2, 43

1, 2, 43

S_TRANSPRT

TTYPE

DTRA,TASK

DTRA,TASK

S_TABU_DIS

ACTVT

3

3

S_TABU_DIS

DICBERCLS

*

*

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

*

*

S_RS_AUTH

BIAUTH

*

*

S_RS_ICUBE

ACTVT

3, 6

3, 6

S_RS_ICUBE

RSICUBEOBJ

DATA, DEFINITION

DATA, DEFINITION

S_RS_ICUBE

RSINFOAREA

*

*

S_RS_ICUBE

RSINFOCUBE

*

*

S_RS_IOBJ

ACTVT

3

3

S_RS_IOBJ

RSIOBJ

*

*

S_RS_IOBJ

RSIOBJCAT

*

*

S_RS_IOBJ

RSIOBJPART

DATA, DEFINITION

DATA, DEFINITION

S_RS_ODSO

ACTVT

3

3

S_RS_ODSO

RSINFOAREA

*

*

S_RS_ODSO

RSODSOBJ

*

*

S_RS_ODSO

RSODSPART

DATA, DEFINITION

DATA, DEFINITION

S_APPLOG

ACTVT

03, 06

03, 06

S_APPLOG

ALG_OBJECT

*

*

S_APPLOG

ALG_SUBOBJ

*

*

Authorizations Required for LKM SAP BW Execution (Background & Foreground)

The following authorizations are required for LKM SAP BW execution in a SAP production environment.

This section contains authorizations for both background and foreground executions.

Object Field Name Value (BI 7.0) Value (BI 7.5)

S_RFC

ACTVT

16

16

S_RFC

RFC_NAME

RFC1, SDIFRUNTIME, SLST, SYST, ZODI_FGR_PROD*

RFC1, SDIFRUNTIME, SLST, SYST, ZODI_FGR_PROD*

S_RFC

RFC_TYPE

FUGR

FUGR

S_TCODE

TCD

SU53

SU53

S_TABU_DIS

ACTVT

3

3

S_TABU_DIS

DICBERCLS

*

*

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

*

*

S_TRANSPRT

ACTVT

1, 2, 43

1, 2, 43

S_TRANSPRT

TTYPE

DTRA, TASK

DTRA, TASK

S_RS_AUTH

BIAUTH

*

*

S_RS_ICUBE

ACTVT

3, 6

3, 6, 23, 63, 66

S_RS_ICUBE

RSICUBEOBJ

*

*

S_RS_ICUBE

RSINFOAREA

*

*

S_RS_ICUBE

RSINFOCUBE

*

*

S_RS_IOBJ

ACTVT

3

3

S_RS_IOBJ

RSIOBJ

*

*

S_RS_IOBJ

RSIOBJCAT

*

*

S_RS_IOBJ

RSIOBJPART

DATA, DEFINITION

DATA, DEFINITION

S_RS_ODSO

ACTVT

3

3

S_RS_ODSO

RSINFOAREA

*

*

S_RS_ODSO

RSODSOBJ

*

*

S_RS_ODSO

RSODSPART

DATA, DEFINITION

DATA, DEFINITION

S_APPLOG

ACTVT

03, 06

03, 06

S_APPLOG

ALG_OBJECT

*

*

S_APPLOG

ALG_SUBOBJ

*

*

SAP Stand-Alone Connection Test

In addition to the Connection Testing described in the Getting Started with SAP ABAP BW Adapter for Oracle Data Integrator, a test can be performed outside of ODI using a standalone java utility. This test is the same for SAP ERP and SAP BW.

See SAP Connection Test for more information.

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:

  1. Open a command window.
  2. Go to the <ODI_HOME>/odi/sdk/lib directory.
  3. Make sure that JAVA_HOME points to a supported JVM.
  4. 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.
  5. 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 BW Adapter for Oracle Data Integrator.

  6. 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>
  7. Enter you SAP connection information, which you have received from your SAP administrator.
  8. 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.

  9. Delete the ODI_SAP_CON_POOL.jcoDestination file after execution, as it contains the SAP login credentials.