B Additional Information for SAP ABAP ERP Adapter

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

This appendix contains the following sections:

B.1 SAP ABAP ERP Required Privileges

A SAP dialog user is required for connecting to the SAP system, for the RKM installation, and 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, a SAP RFC user is sufficient. The following sections list the privileges required for using SAP ERP Knowledge Modules:

B.1.1 Authorizations Required for RKM SAP ERP Setup

The authorizations listed in Table B-1 are required for setting up the configuration for the RKM SAP ERP and install the required RFC programs to retrieve the metadata about SAP tables.

Table B-1 RKM SAP ERP Setup Authorizations

Object Field Name Value

S_ADMI_FCD

S_ADMI_FCD

*

S_ADMI_FCD

S_ADMI_FCD

NADM

S_ADMI_FCD

S_ADMI_FCD

PADM

S_CTS_ADMI

CTS_ADMFCT

EPS1

S_CTS_ADMI

CTS_ADMFCT

EPS2

S_CTS_ADMI

CTS_ADMFCT

PROJ

S_C_FUNCT

ACTVT

16

S_C_FUNCT

CFUNCNAME

*

S_C_FUNCT

PROGRAM

*

S_CTS_ADMI

CTS_ADMFCT

TABL

S_TCODE

TCD

SU53

S_TCODE

TCD

SE38

S_TCODE

TCD

SE80

S_DATASET

ACTVT

6

S_DATASET

ACTVT

33

S_DATASET

ACTVT

34

S_DATASET

FILENAME

*

S_TCODE

TCD

SE91

S_TCODE

TCD

ST22

S_DATASET

PROGRAM

*

S_RFC

RFC_TYPE

*

S_RFC

RFC_NAME

*

S_RFC

ACTVT

16

S_DEVELOP

ACTVT

*

S_DEVELOP

DEVCLASS

*

S_DEVELOP

OBJNAME

*

S_DEVELOP

OBJTYPE

*

S_DEVELOP

P_GROUP

*

S_DOKU_AUT

DOKU_ACT

RAW_VERS

S_DOKU_AUT

DOKU_DEVCL

TEST

S_DOKU_AUT

DOKU_MODE

MAINTAIN

S_RFC_ADM

ACTVT

3

S_RFC_ADM

ICF_VALUE

*

S_RFC_ADM

RFCDEST

*

S_RFC_ADM

RFCTYPE

*

S_RZL_ADM

ACTVT

*

S_TABU_DIS

ACTVT

*

S_TABU_DIS

DICBERCLS

*

S_TCODE

TCD

AL11

S_TCODE

TCD

SE10

S_TCODE

TCD

SE11

S_TCODE

TCD

SE16

S_TCODE

TCD

SE37

S_TCODE

TCD

SM58

S_TCODE

TCD

SM59

S_TRANSPRT

ACTVT

1

S_TRANSPRT

ACTVT

2

S_TRANSPRT

ACTVT

3

S_TRANSPRT

ACTVT

5

S_TRANSPRT

ACTVT

6

S_TRANSPRT

ACTVT

23

S_TRANSPRT

ACTVT

43

S_TRANSPRT

ACTVT

65

S_TRANSPRT

ACTVT

78

S_TRANSPRT

ACTVT

90

S_TRANSPRT

TTYPE

CUST

S_TRANSPRT

TTYPE

DTRA

S_TRANSPRT

TTYPE

MOVE

S_TRANSPRT

TTYPE

PIEC

S_TRANSPRT

TTYPE

TASK

S_TRANSPRT

TTYPE

TRAN

Table B-2 lists the transaction codes.

Table B-2 Transaction Codes

SU53

SE38

SE80

SE91

ST22

AL11

SE10

SE11

SE16

SE37

SM58

SM59

B.1.2 Authorizations Required for RKM Execution

The authorizations listed in Table B-3 are required for running a reverse-engineering using the RKM SAP ERP.

Table B-3 Authorizations for RKM Execution

Object Field Name Value

S_ADMI_FCD

S_ADMI_FCD

*

S_ADMI_FCD

S_ADMI_FCD

NADM

S_ADMI_FCD

S_ADMI_FCD

PADM

S_CTS_ADMI

CTS_ADMFCT

EPS1

S_CTS_ADMI

CTS_ADMFCT

EPS2

S_CTS_ADMI

CTS_ADMFCT

PROJ

S_C_FUNCT

ACTVT

16

S_C_FUNCT

CFUNCNAME

*

S_C_FUNCT

PROGRAM

*

S_CTS_ADMI

CTS_ADMFCT

TABL

S_TCODE

TCD

SU53

S_TCODE

TCD

SE38

S_TCODE

TCD

SE80

S_DEVELOP

ACTVT

16

S_DATASET

ACTVT

33

S_DATASET

FILENAME

*

S_TCODE

TCD

SE91

S_TCODE

TCD

ST22

S_DATASET

PROGRAM

*

S_RFC

RFC_TYPE

*

S_RFC

RFC_NAME

*

S_RFC

ACTVT

16

S_DEVELOP

ACTVT

3

S_DEVELOP

DEVCLASS

*

S_DEVELOP

OBJNAME

*

S_DEVELOP

OBJTYPE

*

S_DEVELOP

P_GROUP

*

S_DOKU_AUT

DOKU_ACT

RAW_VERS

S_DOKU_AUT

DOKU_DEVCL

TEST

S_DOKU_AUT

DOKU_MODE

MAINTAIN

S_RFC_ADM

ACTVT

3

S_RFC_ADM

ICF_VALUE

*

S_RFC_ADM

RFCDEST

*

S_RFC_ADM

RFCTYPE

*

S_RZL_ADM

ACTVT

3

S_TABU_DIS

ACTVT

3

S_TABU_DIS

DICBERCLS

*

S_TCODE

TCD

AL11

S_TCODE

TCD

SE10

S_TCODE

TCD

SE11

S_TCODE

TCD

SE16

S_TCODE

TCD

SE37

S_TCODE

TCD

SM58

S_TCODE

TCD

SM59

S_TRANSPRT

ACTVT

3

S_TRANSPRT

TTYPE

CUST

S_TRANSPRT

TTYPE

DTRA

S_TRANSPRT

TTYPE

MOVE

S_TRANSPRT

TTYPE

PIEC

S_TRANSPRT

TTYPE

TASK

S_TRANSPRT

TTYPE

TRAN

B.1.3 Authorizations Required for LKM Execution

The authorizations listed in Table B-4 are required for using the LKM SAP ERP to Oracle (SQLLDR). This set of authorization is needed to install the ABAP code generated by the LKM and execute it.

Table B-4 Authorizations for LKM Execution

Object Field Name Value

S_ADMI_FCD

S_ADMI_FCD

*

S_ADMI_FCD

S_ADMI_FCD

NADM

S_ADMI_FCD

S_ADMI_FCD

PADM

S_CTS_ADMI

CTS_ADMFCT

EPS1

S_CTS_ADMI

CTS_ADMFCT

EPS2

S_CTS_ADMI

CTS_ADMFCT

PROJ

S_C_FUNCT

ACTVT

16

S_C_FUNCT

CFUNCNAME

*

S_C_FUNCT

PROGRAM

*

S_CTS_ADMI

CTS_ADMFCT

TABL

S_TCODE

TCD

SU53

S_TCODE

TCD

SE38

S_TCODE

TCD

SE80

S_DEVELOP

ACTVT

16

S_DATASET

ACTVT

33

S_DEVELOP

ACTVT

7

S_DATASET

FILENAME

*

S_DEVELOP

ACTVT

1

S_TCODE

TCD

SE91

S_TCODE

TCD

ST22

S_DEVELOP

ACTVT

40

S_DEVELOP

ACTVT

41

S_DATASET

ACTVT

34

S_DEVELOP

ACTVT

94

S_DEVELOP

ACTVT

2

S_TRANSPRT

ACTVT

2

S_TRANSPRT

ACTVT

1

S_TRANSPRT

ACTVT

60

S_TABU_DIS

ACTVT

2

S_RZL_ADM

ACTVT

1

S_DATASET

PROGRAM

*

S_RFC

RFC_TYPE

*

S_RFC

RFC_NAME

*

S_DEVELOP

ACTVT

*

S_DEVELOP

DEVCLASS

*

S_DEVELOP

OBJNAME

*

S_DEVELOP

OBJTYPE

*

S_DEVELOP

P_GROUP

*

S_DOKU_AUT

DOKU_ACT

RAW_VERS

S_DOKU_AUT

DOKU_DEVCL

TEST

S_DOKU_AUT

DOKU_MODE

MAINTAIN

S_RFC_ADM

ACTVT

3

S_RFC_ADM

ICF_VALUE

*

S_RFC_ADM

RFCDEST

*

S_RFC_ADM

RFCTYPE

*

S_RZL_ADM

ACTVT

3

S_TABU_DIS

ACTVT

3

S_TABU_DIS

DICBERCLS

*

S_TCODE

TCD

AL11

S_TCODE

TCD

SE10

S_TCODE

TCD

SE11

S_TCODE

TCD

SE16

S_TCODE

TCD

SE37

S_TCODE

TCD

SM58

S_TCODE

TCD

SM59

S_TRANSPRT

ACTVT

3

S_TRANSPRT

TTYPE

CUST

S_TRANSPRT

TTYPE

DTRA

S_TRANSPRT

TTYPE

MOVE

S_TRANSPRT

TTYPE

PIEC

S_TRANSPRT

TTYPE

TASK

S_TRANSPRT

TTYPE

TRAN

B.1.4 Authorizations Required for LKM Execution for Production

The authorizations listed in Table B-5 are required for using the LKM SAP ERP to Oracle (SQLLDR) in a production environment. In such environment, the ABAP code generated by the LKM is not installed by the LKM but simply executed.

Table B-5 Authorizations for LKM Execution for Production

Object Field Name Value

S_ADMI_FCD

S_ADMI_FCD

*

S_ADMI_FCD

S_ADMI_FCD

NADM

S_ADMI_FCD

S_ADMI_FCD

PADM

S_CTS_ADMI

CTS_ADMFCT

EPS1

S_CTS_ADMI

CTS_ADMFCT

EPS2

S_CTS_ADMI

CTS_ADMFCT

PROJ

S_C_FUNCT

ACTVT

*

S_C_FUNCT

CFUNCNAME

*

S_C_FUNCT

PROGRAM

*

S_CTS_ADMI

CTS_ADMFCT

TABL

S_TCODE

TCD

SU53

S_TCODE

TCD

SE38

S_TCODE

TCD

SE80

S_DEVELOP

ACTVT

16

S_DATASET

ACTVT

33

S_DATASET

FILENAME

*

S_TCODE

TCD

SE91

S_TCODE

TCD

ST22

S_DATASET

PROGRAM

*

S_RFC

RFC_TYPE

*

S_RFC

RFC_NAME

*

S_RFC

ACTVT

16

S_DEVELOP

ACTVT

3

S_DEVELOP

DEVCLASS

*

S_DEVELOP

OBJNAMEv

*

S_DEVELOP

OBJTYPE

*

S_DEVELOP

P_GROUP

*

S_DOKU_AUT

DOKU_ACT

RAW_VERS

S_DOKU_AUT

DOKU_DEVCL

TEST

S_DOKU_AUT

DOKU_MODE

MAINTAIN

S_RFC_ADM

ACTVT

3

S_RFC_ADM

ICF_VALUE

*

S_RFC_ADM

RFCDEST

*

S_RFC_ADM

RFCTYPE

*

S_RZL_ADM

ACTVT

3

S_TABU_DIS

ACTVT

3

S_TABU_DIS

DICBERCLS

*

S_TCODE

TCD

AL11

S_TCODE

TCD

SE10

S_TCODE

TCD

SE11

S_TCODE

TCD

SE16

S_TCODE

TCD

SE37

S_TCODE

TCD

SM58

S_TCODE

TCD

SM59

S_TRANSPRT

ACTVT

3

S_TRANSPRT

TTYPE

CUST

S_TRANSPRT

TTYPE

DTRA

S_TRANSPRT

TTYPE

MOVE

S_TRANSPRT

TTYPE

PIEC

S_TRANSPRT

TTYPE

TASK

S_TRANSPRT

TTYPE

TRAN

B.2 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:

  1. 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 Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

  2. In the Reverse tab of the SAP ERP Model, select the RKM SAP ERP Connect Test.

  3. Save the model.

  4. 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.

B.3 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_misc 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 sapjar3.jar and the sapjco3 library are in the <ODI_HOME>/odi_misc directory.

  5. Launch the utility using the following command:

    java –cp sapjarco3.jar;../oracledi/agent/lib/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_misc folder.

  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. These are installed during first execution of the RKM (UPLOAD_ABAP = Yes).

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

B.4 Uninstalling ODI SAP Components

In case of upgrading to a newer ODI SAP Connector release or for permanently removing ODI connectivity, please follow the steps described in this section.

Please note that this will delete ALL components including generated extractor programs.

To upgrade to a newer ODI SAP Connector release or to permanently remove the ODI connectivity:

  1. Start the SAP GUI.

  2. Connect to the SAP systems you want to uninstall.

  3. Go to the transaction SE80.

  4. Select the package or development class option from the drop down box.

  5. Enter ZODIBW_PCKG in the package or development class field.

  6. Expand the ZODIBW_PCKG package or class.

  7. Select the ZODI_FGR function group.

  8. Right-click and select delete ZODI_FGR.

  9. Confirm the question “Do you really want to delete function group ZODI_FGR” by selecting Yes.

  10. Select the ZODI_SAP_KM_FGRP function group.

  11. Right-click, select delete ZODI_SAP_KM_FGRP.

  12. Confirm the question “Do you really want to delete function group ZODI_SAP_KM_FGRP” by selecting Yes.

  13. Select ZODI_MSG message class.

  14. Right-click, select delete ZODI_MSG.

  15. Confirm the question “Do you really want to delete message class ZODI_MSG” by selecting Yes.

  16. Mark all structures.

  17. Right-click, select Delete.

  18. Confirm the question “Do you really want to delete structure ZRETURN” by clicking Delete All.

  19. If asked for new transport request, assign a new transport request number.

  20. All objects are deleted from ZODIBW_PCKG. Select ZODIBW_PCKG.

  21. Right-click, select Delete.

  22. Confirm the question “Do you really want to delete package ZODIBW_PCKG” by selecting Yes.