Before you use an SAP ADSO Writer connection to load data into an ADSO, the SAP Administrator needs to verify the required licenses are enabled and perform prerequisite tasks.
1Verify the prerequisites in the SAP server.
2Install the SAP ADSO Writer connection transport files.
3Configure the SAP user authorization.
4Download and configure the SAP libraries.
After the administrator has performed the configuration, you can set up and use an SAP ADSO Writer connection in mappings and mapping tasks.
Verify 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.
Install 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.
Verify that you install the latest transport files to write to an SAP ADSO object.
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
- K900131.B42
- R900131.B42
Required
- B42900131
Install the transports to write to an SAP ADSO.
Installing transport files
Install the latest 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.
1 Find the transport files in the following directory on the Secure Agent machine:
2Copy 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>.
3Copy 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>.
4To import the transports to SAP, in the STMS, click Extras > Other Requests > Add and add the transport request to the system queue.
5In 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>.
6In the Request area of the import queue, select the transport request number that you added, and click Import.
7If you are upgrading from a previous version of the Informatica Transports, select the Overwrite Originals option.
Configure SAP user authorization
Configure the SAP user account in the SAP system to process SAP BW/4HANA ADSO data.
For more information about how to configure SAP user authorization in the SAP system, see SAP user authorizations.
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
16
Both
RFC_TYPE - Function Group
RFC1
16
Both
RFC_TYPE - Function Module
RFC_GET_FUNCTION_INTERFACE
16
Both
RFC_TYPE - Function Group
RFC_METADATA
16
Both
RFC_TYPE - Function Module
RFC_METADATA_GET
16
Both
RFC_TYPE - Function Group
RSDSO_UPDATE
16
Both
RFC_TYPE - Function Module
DDIF_FIELDINFO_GET
16
Both
RFC_TYPE - Function Module
BW4_FLP_NOTIFICATIONS_PUSH
16
Run Time
RFC_TYPE - Function Module
/INFADI/ADSO_LIST
16
Both
RFC_TYPE - Function Module
/INFADI/ADSO_METADATA
16
Both
RFC_TYPE - Function Module
/INFADI/RSDSO_WRITE_API_RFC
16
Run Time
S_RS_ADSO
Field Name - RSINFOAREA
*
23
Both
Field Name - RSOADSONM
*
23
Both
Field Name - RSOADSOPAR
Data, Definition
23
Both
The following table describes the optional authorization to read from an SAP BW/4HANA ADSO:
Read Object Name
Required Authorization Values
Value
Activity
Design Time/Run Time
S_RS_AREA
RSINFOAREA
'INFO Area Name'
3
Both
S_ADMI_FCD
S_ADMI_FCD
PADM
N/A
Both
Download and configure the SAP libraries
To read data from an SAP BW/4HANA ADSO, you need to download and configure the SAP JCo libraries on the Secure Agent machine. If you encounter any issues while you download libraries, contact SAP Customer Support.
Note: You need to have SAP credentials to access Software Downloads from the SAP Support Portal.
2 Download the 64-bit SAP JCo libraries based on the operating system on which the Secure Agent runs:
Secure Agent System
SAP JCo Libraries
Windows
sapjco3.jar
sapjco3.dll
Linux
sapjco3.jar
libsapjco3.so
Verify that you download the most recent version of the libraries.
3Copy 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.
4Configure the JAVA_LIBS property in Data Integration:
aLog in to Data Integration.
bClick Runtime Environments to access the Runtime Environments page.
cTo the left of the agent name, click Edit Secure Agent.
dFrom the Service list, select Data Integration Server.
eFrom the Type list, select Tomcat JRE.
f Enter the JAVA_LIBS value based on the operating system on which the Secure Agent runs.
Note: If you copy the value directly from the table, the hyphens (-) in the value are incorrectly copied. Copy the value to a text editor and make sure that the value you copied is not corrupted.
gFrom the Type list, select DTM.
hEnter the JVMClassPath value based on the operating system on which the Secure Agent runs.
Note: If you copy the value directly from the table, the hyphens (-) in the value are incorrectly copied. Copy the value to a text editor and make sure that the value you copied is not corrupted.
iClick OK to save the changes.
j Repeat steps 2 through 4 on every machine where you installed the Secure Agent.