Release Notes > Summer 2016 - June > SAP Connector
  

SAP Connector

After You Upgrade

After you upgrade the SAP Connector, you must perform the following tasks:

Download and Install the SAP NetWeaver RFC SDK 7.20 Libraries

After you upgrade SAP Connector, you must download and install the SAP NetWeaver RFC SDK 7.20 libraries to perform the following tasks:
Before you download and install the SAP NetWeaver RFC SDK 7.20 libraries, you must remove the classic SAP RFC SDK 7.20 libraries.

Create and Configure the sapnwrfc.ini File

After you upgrade SAP Connector, you must create the sapnwrfc.ini file to configure RFC-specific parameters and connection information.
When you read data from SAP tables, if you define the path and file name of the saprfc.ini file in the SAP connection, the Secure Agent will use the saprfc.ini file. However, if you only define the path of the saprfc.ini file in the connection, the Secure Agent will first verify if an sapnwrfc.ini file exists in the specified path. If the sapnwrfc.ini file exists, the Secure Agent will use the sapnwrfc.ini file. Otherwise, it will use the saprfc.ini file.
Informatica will deprecate the saprfc.ini file in a future release. Therefore, Informatica recommends that you create and use an sapnwrfc.ini file instead of the saprfc.ini file.
To process data through RFC/BAPIs, read IDocs, write IDocs, and write data to SAP tables, you cannot use the saprfc.ini file. You must create and configure the sapnwrfc.ini file.

Update the SAP Libraries Directory

After you upgrade SAP Connector, you must copy the sapjco3.jar file to the following directory:
<Informatica Secure Agent installation directory>\main\bin\rdtm-extra\tpl\sap
Before you copy the jar file, you must create the tpl\sap directory within the rdtm-extra directory if the tpl\sap directory does not already exist.
If you had created the 300620 and 447900 plugin folders earlier, you must delete the sapjco3.jar file from both the plugin folders after you upgrade SAP Connector. The 300620 and 447900 folders will contain the tpl.properties file. You must retain the tpl.properties file in both the plugin folders.

Configure the JAVA_LIBS Property

After you upgrade SAP Connector and copy the sapjco3.jar file, you must configure the JAVA_LIBS property in Informatica Cloud.
Perform the following steps to configure the JAVA_LIBS property:
  1. 1. Log in to Informatica Cloud.
  2. 2. Click Configure > Runtime Environments to access the Runtime Environments page.
  3. 3. To the left of the agent name, click Edit Secure Agent.
  4. 4. From the Type list, select Tomcat JRE.
  5. 5. Enter the JAVA_LIBS value based on the operating system on which the Secure Agent runs.
    6. 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
  6. 6. Click OK to save the changes.
  7. 7. Restart the Secure Agent.
  8. 8. Repeat steps 1 through 7 on every machine where you installed the Secure Agent.

Install the SAP Table Transport File

The SAP Connector transport contains a set of ABAP objects that can be imported into SAP systems through an STMS transaction. The objects included in the transport are critical for the SAP Table Connector run-time tasks.
Important: All existing SAP table reader customers must mandatorily import the latest transport into the SAP systems. If you do not import the transport, the existing SAP table reader jobs will fail after the upgrade. Make sure that you import the SAP transport when you upgrade the Secure Agent.
Verify that an SAP system administrator updates the latest transport into the SAP systems that you want to access by using an SAP table connection.
The latest transport file, TABLE_READER_K900721.G00, is available in the following directory on the Secure Agent machine: <Secure Agent Installation Directory>\main\bin\rdtm\sap-transport\SAPTableReader

SAP Connector Fixed Limitations

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
CR
Description
CON-3128
If you run a mapping that contains a BAPI mapplet and the mapplet has a table with the / character in a field name, the mapping fails.
CON-2835
When you read data from an SAP table and use an advanced filter with the $LastRunDate and $LastRunTime variables, the Secure Agent passes incorrect variable values.
CON-2758
After you upgrade the SAP table connector, lookup transformations return incorrect results if there are multiple matching records in the SAP table.
CON-182
Data preview and run-time tasks fail for SAP tables that contain DEC fields with large lengths. For example, DEC[31,5].
ICS-449
When you write data to an SAP target, you cannot select an IDoc Writer connection from the target connections list in the task wizard.
Workaround: Parameterize the connection.

SAP Connector Known Limitations

The following table describes known limitations:
CR
Description
CON-3000
If you read data from non-Unicode SAP BW sources, you might encounter random issues.
CON-2999
If you use a load balancing connection to read data from SAP BW sources, you might encounter random issues.
CON-2998
If you configure https streaming to read data from SAP BW sources, you might encounter random issues.
CON-2833
Data corruption occurs when you perform a lookup on an SAP table and the data contains the pipe (|) character.
CON-569
Data corruption occurs when you read data from an SAP table and use a non-Unicode Japanese system.
CON-501
A data synchronization task or mapping fails when SAP table names or alias names in a join condition are not unique.