You can use a SAP Table Connector to integrate SAP ECC and SAP S/4HANA with Supplier 360 and read SAP data.
1To configure a SAP Table Connector, perform the following steps:
aVerify whether the required licenses are available for SAP Table Connector.
bIf you host the Secure Agent on a Windows machine, download and install the Microsoft Visual C++ Redistributable package on the machine that hosts the Secure Agent.
cDownload and configure the SAP libraries on the Secure Agent machine to read from and write to SAP tables.
dTo enable the Secure Agent to connect to the SAP system as a Remote Function Call (RFC) client, create and configure the sapnwrfc.ini file on the machines that host the Secure Agent.
eConfigure the SAP user account to access the SAP table data.
fInstall the SAP Table connection transport files on the SAP machines that you want to access.
gTo connect to SAP through HTTPS and read SAP table sources, configure the machine that hosts the Secure Agent and the machine that hosts the SAP system.
DEST entry that you specified in the sapnwrfc.ini file for the SAP application server. Use all uppercase letters for the destination. If you enter the directory of the sapnwrfc.ini file in this field, you don't need to enter the host name or IP address and system number of the SAP application server in the Application Server and System Number fields.
Port Range
HTTP port range. The SAP Table connection uses the specified port numbers for connecting to SAP tables using the HTTP protocol. Default range is 10000-65535.
Enter a range in the default range, for example, 10000-20000. If a range is outside the default range, the connection uses the default range.
Test Streaming
Tests the connection. When selected, tests the connection using both RFC and HTTP protocol. When not selected, tests connection using RFC protocol.
Https Connection
When selected, connects to SAP through HTTPS protocol. To successfully connect to SAP through HTTPS, verify that an administrator has configured the machines that host the Secure Agent and the SAP system.
Keystore Location
Absolute path and file name of the keystore file required for the SAP connection.
Specify both the directory and file name in the following format:
<Directory>/<Keystore file name>.jks
Keystore Password
The destination password to access the keystore file.
Private Key Password
The export password that you specify for the .P12 file.
3Test the connections, and ensure that the connections are successful.
4If the SAP instance and the Secure Agent are installed in the same Virtual Private Cloud (VPC) network, perform the following steps:
aConfigure the Secure Agent host to use the private IP address for accessing the SAP instance.
aOpen the following file on the Secure Agent:
▪ On Windows. \Windows\System32\drivers\etc\hosts
▪ On Linux. /etc/hosts
bAdd an entry for the SAP instance in the following format:
<SAP Hostname> <Private IP address of the SAP host>
cRepeat step 4.a.ii for all the SAP instances available in VPC as the Secure Agent host.
bFor communication between the SAP instance and the Secure Agent, add a custom DTM configuration property to use the private IP address of the Secure Agent host.
aIn Administrator, click Runtime Environments.
bExpand the Actions menu for the Secure Agent, and select Edit Secure Agent.
cIn the Custom Configuration Details section, enter the following details:
Field Name
Value
Services
Data Integration Server
Type
DTM
Name
SapTableReaderNatIpAddress
Value
<Private IP address of Secure Agent host>
dClick Save.
The Secure Agent restarts automatically within 10 minutes. To apply the properties immediately, you can restart manually. To avoid failure of any running task, ensure that no tasks run .
c Test the connection to verify the connectivity between the SAP instance and the Secure Agent.
If the connection test is unsuccessful, disable the firewall to resolve the issue.