A Additional Information for SAP ABAP BW Adapter

This appendix describes the privileges that are required for connecting to SAP System, and how you can test the connection outside of ODI using a standalone java utility.

This appendix includes the following sections:

Section A.1, "SAP ABAP BW Required Privileges"
Section A.2, "SAP Stand-Alone Connection Test"

For more information about the SAP BW KMs see Connectivity and Knowledge Modules Guide for Oracle Data Integrator.

A.1 SAP ABAP BW Required Privileges

For connecting to the SAP system a SAP dialog user is required for RKM installation and 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:

Authorizations Required for RKM SAP BW Setup
Authorizations Required for RKM SAP BW Execution
Authorizations Required for LKM SAP BW Execution
Authorizations Required for LKM SAP BW Execution in Production
Authorizations Required for LKM SAP BW Execution as Background Process
Authorizations Required for LKM SAP BW Execution as Background Process in Production

A.1.1 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.

A.1.2 Authorizations Required for RKM SAP BW Setup

The following authorizations are required for RKM SAP BW setup.

Note:

Developer Key is required in this authorization.

Object	Field Name	Value (BW 3.5)	Value (BI 7.0)
`S_RFC`	`ACTVT`	`16`	`16`
	`RFC_NAME`	`RFC1, RSAB, RSB3RD, SDIFRUNTIME, SUTL, SYST, SYSU, ZODI_FGR`	`RFC1, RSAB, RSB3RD, SDIFRUNTIME, SUTL, SYST, ZODI_*`
	`RFC_TYPE`	`FUGR`	`FUGR`
`S_TCODE`	`TCD`	`SU53, SE38`	`SU53, SE38`
	`S_ADMI_FCD`		`MEMO`
`S_CTS_ADMI`	`CTS_ADMFCT`	`TABL`	`TABL`
`S_DATASET`	`ACTVT`	`34`	`06,33,34`
	`FILENAME`	`*`	`*`
	`PROGRAM`	`SAPLSTRF`	`SAPLSLOG, SAPLSTRF, SAPLZODI*`
`S_TABU_DIS`	`ACTVT`		`03`
	`DICBERCLS`		`*`
`S_DEVELOP`	`ACTVT`	`01,02,03,06`	`01,02,03,06,07,16`
	`DEVCLAS`	`$TMP, ZODI_LKM_PCKG, ZODI_RKM_PCKG`	`$TMP, RSS, ZODI_LKM_PCKG, ZODI_RKM_PCKG`
	`OBJNAME`	`Z$$$XRFC, ZODI_FGR, ZODI_FGR_PROD, ZODI_LKM_PCKG, ZODI_RKM_PCKG`	`Z$$$XRFC, RSSB, ZODI_FGR, ZODI_FGR_PROD, ZODI_LKM_PCKG, ZODI_RKM_PCKG`
	`OBJTYPE`	`DEVC, FUGR, PROG`	`DEVC, FUGR, PROG`
	`P_GROUP`		`*`
`S_TRANSPRT`	`ACTVT`	`01,02,03,06`	`01,02,03`
	`TTYPE`	`DTRA, TASK`	`DTRA, TASK`
`S_RS_ADMWB`	`ACTVT`	`03,16`	`03,16`
	`RSADMWBOBJ`	`INFOOBJECT`	`INFOOBJECT`
`S_RS_ICUBE`	`ACTVT`	`03`	`03`
	`RSICUBEOBJ`	`*`	`*`
	`RSINFOAREA`	`*`	`*`
	`RSINFOCUBE`	`*`	`*`
`S_RS_IOBJ`	`ACTVT`	`03`	`03`
	`RSIOBJ`	`*`	`*`
	`RSIOBJCAT`	`*`	`*`
	`RSIOBJPART`	`DEFINITION`	`DEFINITION`
`S_RS_ODSO`	`ACTVT`	`03`	`03`
	`RSINFOAREA`	`*`	`*`
	`RSODSOBJ`	`*`	`*`
	`RSODSPART`	`DATA,DEFINITION`	`DATA,DEFINITION`

A.1.3 Authorizations Required for RKM SAP BW Execution

The following authorizations are required for RKM SAP BW execution.

Object	Field Name	Value (BW 3.5)	Value (BI 7.0)
`S_RFC`	`ACTVT`	`16`	`16`
	`RFC_NAME`	`RFC1, RSB3RD, SDIFRUNTIME, SYST, ZODI_FGR, RSAB`	`RFC1, RSB3RD, SDIFRUNTIME, SYST, ZODI_*`
	`RFC_TYPE`	`FUGR`	`FUGR`
`S_TCODE`	`TCD`	`SU53`	`SU53, SE38`
`S_TABU_DIS`	`ACTVT`	`03`	`03`
	`DICBERCLS`	`*`	`MA,SC`
`S_RS_ADMWB`	`ACTVT`	`03,16`	`03`
	`RSADMWBOBJ`	`INFOOBJECT`	`INFOOBJECT`
`S_RS_ICUBE`	`ACTVT`	`03`	`03`
	`RSICUBEOBJ`	`*`	`*`
	`RSINFOAREA`	`*`	`*`
	`RSINFOCUBE`	`*`	`*`
`S_RS_IOBJ`	`ACTVT`	`03`	`03`
	`RSIOBJ`	`*`	`0*`
	`RSIOBJCAT`	`*`	`0*`
	`RSIOBJPART`	`DEFINITION`	`DEFINITION`
`S_RS_ODSO`	`ACTVT`	`03`	`03`
	`RSINFOAREA`	`*`	`0, T, Z*`
	`RSODSOBJ`	`*`	`0, U, Z*`
	`RSODSPART`	`DATA,DEFINITION`	`DATA, DEFINITION`

A.1.4 Authorizations Required for LKM SAP BW Execution

The following authorizations are required for LKM SAP BW execution.

Note:

Developer Key is required in this authorization.

Object	Field Name	Value (BW 3.5)	Value (BI 7.0)
`S_RFC`	`ACTVT`	`16`	`16`
	`RFC_NAME`	`RFC1, RSAB, SDIF, SYSU, SDIFRUNTIME, SYST, ZODI_FGR, ZODI_FGR_PROD*`	`RFC1, SDIFRUNTIME, SYST, ZODI_FGR, ZODI_FGR_PROD*`
	`RFC_TYPE`	`FUGR`	`FUGR`
`S_TCODE`	`TCD`	`SE38,SU53`	`SE38,SU53`
`S_CTS_ADMI`	`CTS_ADMFCT`	`TABL`	`TABL`
`S_DATASET`	`ACTVT`	`06,33,34`	`06,33,34`
	`FILENAME`	`\\DEL-7TMK2BS\odiagentbox, \\DEL-7TMK2BS\odiagentbox`	`\\10.30.0.201\ODI_SAPTEST, \\10.30.0.201\ODI_SAPTEST\ZODI_233030*`
	`PROGRAM`	`SAPLSLOG, SAPLSTRF, SAPLZODI*`	`SAPLSLOG, SAPLSTRF, SAPLZODI*`
`S_DEVELOP`	`ACTVT`	`01,02,03,06`	`01,02,03,06`
	`DEVCLASS`
	`OBJNAME`	`ZODI_FGR_PROD*`	`ZODI_FGR_PROD*`
	`OBJTYPE`	`FUGR,PROG`	`FUGR,PROG`
	`P_GROUP`
`S_PROGRAM`	`P_ACTION`		`EDIT,SUBMIT,VARIANT`
	`P_GROUP`
`S_TRANSPRT`	`ACTVT`	`01`	`01`
	`TTYPE`	`DTRA,TASK`	`DTRA,TASK`
`S_RS_AUTH`	`BIAUTH`		`0*`
`S_RS_ICUBE`	`ACTVT`	`03`
	`RSICUBEOBJ`	`DATA,DEFINITION`
	`RSINFOAREA`	`NODESNOTCONNECTED`
	`RSINFOCUBE`	`0,Z`

A.1.5 Authorizations Required for LKM SAP BW Execution in Production

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

Object	Field Name	Value (BW 3.5)	Value (BI 7.0)
`S_RFC`	`ACTVT`	`16`	`16`
	`RFC_NAME`	`RFC1, SDIFRUNTIME, SYST, ZODI_FGR_PROD*`	`RFC1, SDIFRUNTIME, SYST, ZODI_FRG, ZODI_FGR_PROD`
	`RFC_TYPE`	`FUGR`	`FUGR`
`S_TCODE`	`TCD`	`SU53`	`SU53`
`S_DATASET`	`ACTVT`	`06,33,34`	`06, 33, 34`
	`FILENAME`	`\\DEL-7TMK2BS\odiagentbox, \\DEL-7TMK2BS\odiagentbox`	`\\10.30.0.201\ODI_SAPTEST,` `\\10.30.0.201\ODI_SAPTEST\ZODI_233030*`
	`PROGRAM`	`SAPLSLOG, SAPLSTRF, SAPLZODI*`	`SAPLSLOG, SAPLSTRF, SAPLZODI*`
`S_RS_AUTH`	`BIAUTH`		`0*`
`S_RS_ICUBE`	`ACTVT`	`03`	`03`
	`RSICUBEOBJ`	`DATA,DEFINITION`	`DEFINITION`
	`RSINFOARE`	`NODESNOTCONNECTED`
	`RSINFOCUBE`	`0,Z`
`S_RS_IOBJ`	`ACTVT`		`03`
	`RSIOBJ`
	`RSIOBJCAT`
	`RSIOBJPART`		`DEFINITION`
`S_RS_ODSO`	`ACTVT`		`03`
	`RSINFOAREA`
	`RSODSOBJ`
	`RSODSPART`		`DEFINITION`

A.1.6 Authorizations Required for LKM SAP BW Execution as Background Process

The following authorizations are required for LKM SAP BW execution as background process.

Note:

Developer Key is required in this authorization.

Object	Field Name	Value (BW 3.5)	Value (BI 7.0)
`S_RFC`	`ACTVT`	`16`	`16`
	`RFC_NAME`	`RFC1, SDIFRUNTIME, RSAB, SYSU, SLST, SYST, ZODI_FGR, ZODI_FGR_PROD*`	`RFC1, SDIFRUNTIME, SLST, SYST, ZODI_FGR, ZODI_FGR_PROD*`
	`RFC_TYPE`	`FUGR`	`FUGR`
`S_TCODE`	`TCD`	`SE38,SU53`	`SE38,SU53`
`S_BTCH_ADM`	`BTCADMIN`	`Y`	`Y`
`S_BTCH_JOB`	`JOBACTION`	`RELE`	`RELE`
	`JOBGROUP`	`'`	`'`
`S_CTS_ADMI`	`CTS_ADMFCT`	`TABL`	`TABL`
`S_DATASET`	`ACTVT`	`06,33,34`	`06,33,34`
	`FILENAME`	`\\DEL-7TMK2BS\odiagentbox, \\DEL-7TMK2BS\odiagentbox, \\DELRC6\sapmnt*`	`\\10.30.0.201\ODI_SAPTEST,` `\\10.30.0.201\ODI_SAPTEST\ZODI_233030*`
	`PROGRAM`	`SAPLSLOG,SAPLSTRF,SAPLZODI,ZODI`	`SAPLSLOG,SAPLSTRF,SAPLZODI,ZODI`
`S_DEVELOP`	`ACTVT`	`01`	`01,02,03,06,16`
	`DEVCLASS`
	`OBJNAME`	`ZODI_FGR_PROD*`	`ZODI_FGR_PROD*`
	`OBJTYPE`	`FUGR`	`FUGR,PROG`
	`P_GROUP`
`S_PROGRAM`	`P_ACTION`		`EDIT,SUMMIT,VARIANT`
	`P_GROUP`
`S_TRANSPRT`	`ACTVT`	`01,02,03`	`01,02`
	`TTYPE`	`DTRA,TASK`	`DTRA,TASK`
`S_RS_AUTH`	`BIAUTH`		`0*`
`S_RS_ICUBE`	`ACTVT`	`03,06`
	`RSICUBEOBJ`	`DATA,DEFINITION`
	`RSINFOAREA`	`NODESNOTCONNECTED`
	`RSINFOCUBE`	`0,Z`
`S_APP_LOG`	`ACTVT`	`03,06`	`03,06`
	`ALG_OBJ`	`ZODI_APPOBJ`	`ZODI_APPOBJ`
	`ALG_SUBOBJ`	`ZODI_SUBOBJ`	`ZODI_SUBOBJ`

A.1.7 Authorizations Required for LKM SAP BW Execution as Background Process in Production

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

Object	Field Name	Value (BW 3.5)	Value (BI 7.0)
`S_RFC`	`ACTVT`	`16`	`16`
	`RFC_NAME`	`RFC1, SDIFRUNTIME, SYSU, SLST, SYST, ZODI*`	`RFC1, SDIFRUNTIME, SLST, SYST, ZODI*`
	`RFC_TYPE`	`FUGR`	`FUGR`
`S_TCODE`	`TCD`	`SU53`	`SU53`
`S_BTCH_ADM`	`BTCADMIN`	`Y`	`Y`
`S_BTCH_JOB`	`JOBACTION`	`RELE`	`RELE`
	`JOBGROUP`	`''`	`''`
`S_DATASET`	`ACTVT`	`06,33,34`	`06,33,34`
	`FILENAME`	`\\10.30.0.201\ODI_SAPTEST, \\DEL-7TMK2BS\odiagentbox,` `\\DELRC6\sapmnt*`	`\\10.30.0.201\ODI_SAPTEST, \\DEL-7TMK2BS\odiagentbox, \\DELRC6\sapmnt*`
	`PROGRAM`	`SAPLSTRF, ZODI*`	`ZODI*`
`S_DEVELOP`	`ACTVT`		`01, 02, 03, 06, 07, 16`
	`DEVCLASS`
	`OBJNAME`		`S_TCODE`
	`OBJTYPE`		`SUSO`
	`P_GROUP`
`S_RS_AUTH`	`BIAUTH`		`0*`
`S_RS_ICUBE`	`ACTVT`	`03`	`03`
	`RSICUBEOB`	`DATA,DEFINITION`	`DATA,DEFINITION`
	`RSINFOAREA`	`NODESNOTCONNECTED`	`0,Z`
	`RSINFOCUBE`	`0,Z`	`0,Z`
`S_APPL_LOG`	`ACTVT`		`03,06`
	`ALG_OBJECT`		`ZODI_APPOBJ`
	`ALG_SUBOBJ`		`ZODI_SUBOBJ`

A.2 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 Section B.2, "SAP Connection Test" for more information.

A.2.1 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 BW 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.