SAP Connector > Part II: SAP Connector Administration > SAP Connector administration > SAP ADSO Writer Connector administration
  

SAP ADSO Writer Connector administration

Before you can use an SAP ADSO Writer connection to load data into an ADSO, an SAP Administrator must perform the following tasks:
  1. 1. Verify if the required licences are enabled.
  2. 2. Verify the prerequisites in the SAP server.
  3. 3. Install the SAP ADSO Writer 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 ADSO Writer connection in mapping tasks.

Step 1. Verifying if the required licenses are available for SAP ADSO Writer

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

Step 2. Verifying the prerequisites for SAP server

SAP ADSO Writer Connector supports only the SAP BW/4HANA system.
The minimum version of the BW/4HANA system must be 2.0, and is identified through the SAP component DW4CORE, Release 200.

Step 3. Installing SAP ADSO Writer Connector transport files

Install the SAP ADSO Writer 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 load data to an SAP BW/4HANA ADSO object.
Data and Cofile Names
Required/Optional
Transport Request
Functionality
  • - K900105.B42
  • - R900105.B42
Required
  • - B42900105
Install the transports to write to an SAP ADSO.

Installing transport files

Install the transport files from a Secure Agent directory to write to a Unicode SAP BW/4HANA system. The transport files are for SAP BW/4HANA version 2.0 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\SAPBWADSOWriter
    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: <TR 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: ADSO_WRITER_R<TR 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 SAP BW/4HANA ADSO data.
The following table describes the required authorization to read from an SAP BW/4HANA ADSO:
Read Object Name
Required Authorization Values
Value
Activity
Design Time/Run Time
S_RFC
RFC_TYPE - Function Group
SYST
16
Both
RFC_TYPE - Function Module
RFCPING
Both
RFC_TYPE - Function Group
RFC1
Both
RFC_TYPE - Function Module
RFC_GET_FUNCTION_INTERFACE
Both
RFC_TYPE - Function Group
RFC_METADATA
Both
RFC_TYPE - Function Module
RFC_METADATA_GET
Both
RFC_TYPE - Function Group
RSDSO_UPDATE
Both
RFC_TYPE - Function Module
DDIF_FIELDINFO_GET
Both
RFC_TYPE - Function Module
BW4_FLP_NOTIFICATIONS_PUSH
Run Time
RFC_TYPE - Function Module
/INFADI/ADSO_LIST
Both
RFC_TYPE - Function Module
/INFADI/ADSO_METADATA
Both
RFC_TYPE - Function Module
/INFADI/RSDSO_WRITE_API_RFC
Run Time
S_RS_ADSO
Field Name - RSINFOAREA
*
23
Both
Field Name - RSOADSONM
*
Both
Field Name - RSOADSOPAR
Data, Definition
Both
Optional Authorization Object's
S_RS_AREA
RSINFOAREA
'INFO Area Name'
3
Both
S_ADMI_FCD
S_ADMI_FCD
PADM
N/A
Both

Step 5. Download and configure the SAP libraries

To read data froman SAP BW/4HANA ADSO, 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.