SAP Connector > Part II: SAP Connector Administration > SAP Connector administration > SAP ODP Extractor Connector administration
  

SAP ODP Extractor Connector administration

Before you can use an SAP ODP Extractor connection to extract data from an ODP, an SAP Administrator must perform the following tasks:
  1. 1. Verify if the required licences are enabled.
  2. 2. Verify and install the required SAP Notes in the SAP server.
  3. 3. Install the SAP ODP Extractor connection transport files.
  4. 4. Configure the SAP user authorization.
  5. 5. Download and configure the SAP libraries.
After the administrator has performed the configuration, you can set up and use an SAP ODP Extractor connection in mapping tasks.

Step 1. Verifying if the required licenses are available for SAP ODP Extractor Connector

You must verify if the required licenses for SAP ODP Extractor Connector are available before you create an SAP connection and extract data from ODPs.
    1. In the Data Integration home page, click the Administer tab.
    2. Under Connector Licences, verify if the SAP ODP Extractor Connector licence is enabled.

Step 2. Verifying and installing prerequisite SAP Notes in the SAP server

SAP ODP Extractor Connector uses the ODP Replication APIs version 2.0.
Before using SAP ODP Extractor Connector, verify that the following SAP Notes are available in the SAP server:

Step 3. Installing SAP ODP Extractor Connector transport files

Install the SAP ODP Extractor transport files on the SAP machines that you want to access. Before you install the transports on your production system, install and test the transports in a development system.
Install the following data file and cofile to read data from the SAP ODP object:
Data and Cofile Names
Required/Optional
Transport Request
Functionality
  • - K900426.IN7
  • - R900426.IN7
Required
IN7K900426
Install the transports only when you want to read from an SAP ODP that supports hierarchy.
You can use the SAP ODP Extractor Connector without installing the SAP ODP Extractor transport files for objects that do not support hierarchy.

Installing Transport Files

Install transport files from a Secure Agent directory to read from a Unicode SAP system. The transport files are for SAP version ERP 6.0 EHP7 system or later. To install transport files to write to an SAP system, contact Informatica Global Customer Support.
    1. Find the transport files in the following directory on the Secure Agent machine:
    <Informatica Secure Agent installation directory>\downloads\package-SAPConnector.350\package\rdtm\sap-transport\SAPODPReader
    2. Copy the cofile transport file to the Cofile directory in the SAP transport management directory on each SAP machine that you want to access.
    The cofile transport file uses the following naming convention: <number>.<sap system>.
    3. Copy the data transport file to the Data directory in the SAP transport management directory on each SAP machine that you want to access.
    The data transport file uses the following naming convention: <number>.<sap-system>.
    4. To import the transports to SAP, in the STMS, click Extras > Other Requests > Add and add the transport request to the system queue.
    5. In the Add Transport Request to Import Queue dialog box, enter the request number for the cofile transport.
    The request number inverts the order of the renamed cofile as follows: <sap-system><number>.
    6. In the Request area of the import queue, select the transport request number that you added, and click Import.
    7. If you are upgrading from a previous version of the Informatica Transports, select the Overwrite Originals option.

Step 4. Configure SAP user authorization

Configure the SAP user account to process the SAP ODP data.
The following table describes the required authorization to read from SAP ODPs:
Read Object Name
Required Authorization Values
Value
Activity
Design Time/Run Time
S_RFC
RFC_TYPE - Function Group(FUGR)
SYST
16
Both
RFC_TYPE - Function Module(FUGR)
RFC1
Both
RFC_TYPE - Function Module(FUNC)
RFCPING
Both
RFC_TYPE - Function Group(FUGR)
RFC_METADATA
Both
RFC_TYPE - Function Module(FUNC)
RFC_METADATA_GET
Both
RFC_TYPE - Function Module(FUNC)
RFC_GET_FUNCTION_INTERFACE
Both
RFC_TYPE - Function Module(FUNC)
RODPS_REPL_CONTEXT_GET_LIST
Both
RFC_TYPE - Function Module(FUNC)
RODPS_REPL_ODP_GET_DETAIL
Both
RFC_TYPE - Function Module(FUNC)
RODPS_REPL_ODP_GET_LIST
Both
RFC_TYPE - Function Module(FUNC)
RODPS_REPL_ODP_OPEN
Both
RFC_TYPE - Function Module(FUNC)
RODPS_REPL_ODP_CLOSE
Both
RFC_TYPE - Function Module(FUNC)
/INFADI/ODP_FETCH_XML
Run Time
RFC_TYPE - Function Module(FUNC)
RODPS_REPL_ODP_FETCH
Run Time
RFC_TYPE - Function Module(FUNC)
RODPS_REPL_ODP_FETCH_XML
Run Time
RFC_TYPE - Function Module(FUNC)
DDIF_FIELDINFO_GET
Both
S_BTCH_ADM
FIELD NAME - BTCADMIN
Y
N/A
Both
S_BTCH_JOB
FIELD NAME - JOBACTION
RELE
RELE(Release Jobs)
Both
FIELD NAME - JOBGROUP
' '
N/A
Both
S_RS_ODP_H
FIELD NAME - RSODPHNAME
*
3
Both
FIELD NAME - RSODPHPKG
*
Both
S_RO_OSOA
FIELD NAME - OLTPSOURCE
*
3
Both
FIELD NAME - OSOAAPCO
*
Both
FIELD NAME - OSOAPART
Data, Definition
Both
S_RS_HYBR
FIELD NAME - RSHYBRPROV
'*'
3
Both
FIELD NAME - RSHYBRPROJ
Definition
Both
S_RS_ICUBE
FIELD NAME - OLTPSOURCE
*
3
Both
FIELD NAME - OSOAAPCO
*
Both
FIELD NAME - OSOAPART
Data, Definition
Both
S_RS_IOMAD
FIELD NAME - RSINFOAREA
*
3
Both
FIELD NAME - RSAPPLNM
*
Both
FIELD NAME - RSIOBJNM
*
Both
S_RS_MPRO
FIELD NAME - RSINFOAREA
*
Both
FIELD NAME - RSMPRO
*
Both
FIELD NAME - RSMPROOBJ
Data
Both
S_RS_ODSO
FIELD NAME - RSINFOAREA
*
3
Both
FIELD NAME - RSODSOBJ
*
Both
FIELD NAME - RSODSPART
Data
Both
S_ADMI_FCD
FIELDNAME - S_ADMI_FCD
PADM
N/A
Both

Step 5. Download and configure the SAP libraries

To read data from SAP ODPs, you must download the SAP JCo libraries and configure them on the machine where the Secure Agent runs. Contact SAP Customer Support if you encounter any issues with downloading the libraries.
    1. Go to the SAP Service Marketplace: http://service.sap.com/connectors
    Note: You must have the SAP credentials to access the Service Marketplace.
    2. Download the 64-bit SAP JCo libraries based on the operating system on which the Secure Agent runs:
    Secure Agent System
    SAP File Name
    Windows
    sapjco3.jar
    sapjco3.dll
    Linux
    sapjco3.jar
    libsapjco3.so
    You must download the latest patch for the SAP JCo version 3.1.
    3. Copy the JCo libraries to the following directory: <Informatica Secure Agent installation directory>\apps\Data_Integration_Server\ext\deploy_to_main\bin\rdtm-extra\tpl\sap
    Create the deploy_to_main\bin\rdtm-extra\tpl\sap directory if it does not already exist.
    4. Configure the JAVA_LIBS property in Data Integration:
    1. a. Log in to Data Integration.
    2. b. Click Runtime Environments to access the Runtime Environments page.
    3. c. To the left of the agent name, click Edit Secure Agent.
    4. d. From the Service list, select Data Integration Server.
    5. e. From the Type list, select Tomcat JRE.
    6. f. Enter the JAVA_LIBS value based on the operating system on which the Secure Agent runs.
    7. Operating System
      Value
      Windows
      ../bin/rdtm-extra/tpl/sap/sapjco3.jar;../bin/rdtm/javalib/sap/sap-adapter-common.jar
      Linux
      ../bin/rdtm-extra/tpl/sap/sapjco3.jar:../bin/rdtm/javalib/sap/sap-adapter-common.jar
      Note: Copy the value to a text editor and make sure that the value you copied is not corrupted. If you copy the value directly from the table, the hyphens (-) in the value are incorrectly copied.
    8. g. From the Type list, select DTM.
    9. h. Enter the JVMClassPath value based on the operating system on which the Secure Agent runs.
    10. Operating System
      Value
      Windows
      pmserversdk.jar;../../bin/rdtm-extra/tpl/sap/sapjco3.jar;../../bin/rdtm/javalib/sap/sap-adapter-common.jar
      Linux
      pmserversdk.jar:../../bin/rdtm-extra/tpl/sap/sapjco3.jar:../../bin/rdtm/javalib/sap/sap-adapter-common.jar
      Note: Copy the value to a text editor and make sure that the value you copied is not corrupted. If you copy the value directly from the table, the hyphens (-) in the value are incorrectly copied.
    11. i. Click OK to save the changes.
    12. j. Repeat steps 2 through 7 on every machine where you installed the Secure Agent.
    5. Restart the Secure Agent.