Scenario
This blog post is intended to serve as an end to end, step by step guide on how to replicate the Master data from S4 HANA to SAP Ariba (Procure to Order business process) through CIG direct connection. We will take an example of a company code in this case and will only be dealing with an outbound scenario. So there is no explanation of Cloud Connector as it will come into play for inbound only.
SAP has strategically placed CIG into the integration landscape for ARIBA integration and this blog is intended to show it by example how simple it is to use CIG (IaaS).
Existing methods of Master Data Integration
Master Data replication from S/4 to Ariba is typically done in the below ways.
1. Batch File transfer
a. ‘.csv” files are uploaded or downloaded via Https
b. Multiple records can be transferred in a single batch
c. Processes can be scheduled
2. SAP Direct Connectivity
a. Direct transfer of master data from SAP to SAP Ariba (discussed in this blog)
3. Web services
a. XML messages over Https
b. Only one record per message
c. A Middle ware application is needed to send/receive messages
d. Mappings are needed
e. Real time file processing
f. More responsibility on the customer to installation, modification and maintenance
Steps Involved
The basic steps involved in the end to end master data interface are
1. Configurations in S4 Hana (SPRO configurations)
2. Configurations in Ariba
3. Configurations in CIG
4. Testing of the scenario
Prerequisites
Below mentioned prerequisites are needed to be able to establish the master data interface successfully from S4 Hana to SAP Ariba. Please refer to the attached screenshots:
1. CIG add on to be installed on S4 to enable SPRO configurations and proceed with interface configurations
2. CIG enablement on ARIBA Realm
3. Cloud connector not needed for Outbound; only needed for Inbound
4. Get the partition and variant ID from ARIBA
5. Download the CIG certificate from CIG Integration Portal in Resources
6. Install the CIG certificate in the Integration Toolkit (ITK) on ARIBA (P2O) and also in S4 Hana
o The certificate downloaded in the above step has to be installed in the Ariba ITK in integration manager
o The certificate should also be installed in S/4.
Master Data Integration Architecture
The picture below details the basic integration architecture between S4 Hana and SAP Ariba via CIG. There is a direct connection for master data.
Depicting the Master Data Integration Architecture
Master Data interface flow for reference
Below figure gives only a reference of the master data interface flow and not an exhaustive list, there are other flows as well based on the business process involved.
S4 Configurations in SPRO Tcode
1) Global settings
2) Master Data integration
3) Ariba and CIG Configuration
After logging into S4, go to the Tcode – SPRO -> Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings
Below are the steps we need to follow for the configurations sequentially under Global settings:
Figure 4 – Global Settings
1.1 CIG Certificate Installation in S4 Hana
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings
Maintain Certificates
1.2 Create an RFC Destination
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings Create RFC Destination
Use the same P-User which is enabled in CIG (My Configurations -> Authorizations) for the login and security tab in the blow step
1.3 Create a Port
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings -> Create Port Definition (i.e. Port type is XML HTTP)
Make sure that the content type is selected as Text/XML and Soap protocol check box is ticked. Click save.
1.4 Create a Logical System
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings -> Create Logical System
Prerequisite: Client should be opened and is transportable
1.5 Configure the receiver Ports
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings -> Configure Receiver Port
1.6 Send SAP S4 Hana information to SAP Ariba CIG
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings -> Send SAP Information to SAP Ariba Cloud Integration Gateway -> Synchronize SAP Information with SAP Ariba Cloud Integration Gateway
Credentials should be P-User which is enabled in CIG
Once the above step is performed, a connection is established in CIG automatically under the Basic Data tab
1.7 Configure the Variant and Partition IDs
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings -> Map the Variant and Partition for SAP Ariba solutions (REALM ID’s for Partition and Variant are to be received from SAP Ariba Cloud APPS team)
2.1 Configure External Commands for Operating System
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Configure External Commands for Operating System
Note: Based on the Operating system the commands would have to be modified
2.2 Configure Ariba Incremental Extract Event
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Configure Ariba Incremental Extract Event (Click Execute to view the tables)
2.3 Configure Ariba Master Data Incremental Field Restrictions
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Configure Ariba Master Data Incremental Field Restrictions
2.4 Configure Ariba Event Linkages
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Configure Ariba Event Linkages
Prerequisite: Client should be opened
2.5 Maintain parameters for Master Data Integration
a) Cross application
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Maintain Parameters -> Cross Application
Prerequisite: The directories should have been created before this step
b) Procurement
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Procurement
Note: Based on the customer requirements the parameters might vary
2.6 Maintain Filters
a) Cross application
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Maintain Filters -> Cross Application
Note: Based on the customer requirements the parameters might vary (eg: Company_Code_Export from S4 to Ariba)
b) Procurement
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Procurement
2.7 Connection parameters
Add all the child and parent realms for procurement
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings Connection Parameters for Master Data
2.8 Maintain System ID for Master Data
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Maintain System ID for Master Data
2.9 Maintain Date Time Stamp for Master Data
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Maintain Date Time Stamp for Master Data
2.10 Maintain Field Map for Master Data and Catalog Upload Request
Even if there are no custom mapping fields, this step has to be performed from the golden client to the client on which we have to replicate the data
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> Enhancements -> Maintain Field Map for Master Data and Catalog Upload Request
1. The Change View "Table to maintain mapping of SAP to Buyer fields": Overview screen appears.
2. Click New Entries in the application toolbar to add new entries.
3. Enter the following details:
4. Solution: Select a solution from the list for which you are mapping the field.
5. Structure: Add a structure name. For example, ARBCIG_BP_LANG_STR
6. Field SAP: Add the SAP S/4 field name that you want to map. For example, BUDGETPDTX
7. Field Ariba: Add the Ariba solution field name to which you want to map. For example, Name
8. Click Save.
2.11 Interface set up for Master Data
This is done for establishing the direct connection from S4 to Ariba
o P user ID needed
o URL host needed
o Path prefix needed
After Execute – result is below
(It means that the web service is activated in SOA manager)
Go to the SOA manager transaction (to check the activated web service; no actions required in SOA manager as it is already done in the interface setup)
Searching the activated service from Interface setup via SPRO
3.1 Integration Configuration in Ariba
Go to the Integration manager transaction after logging into Ariba.
Select the Web service as we are importing via Web service
3.2 Certificate installation
Certificate Installation in ITK in Ariba for authentication and to load the data
3.3 Data definition
Data Definition table in Ariba – to know the details of the data
All the Ariba fields for company codes master data
Testing: Executing extraction program from S4 to Ariba replication of master data
S4 status:
Go to the Tcode - SE38
Program – ARBCIG_MASTER_DATA_EXPORT
Full load is run the first time and there on the incremental load can be executed by creating the variant and scheduling it in the background job.
FPC enables – when we want the data to be replicated to both the parent and child site in Ariba, we have to enable this. We have to get the site name from SAP Ariba Cloud team.
Populate the details as shown below which we configured in the above sections.
Click Execute to start replication
File generated in S4 – Archive folder in AL11 – this is to be replicated into SAP Ariba
Go to the Tcode – SRT_MONI – to check the message processing status
CIG Transaction tracker status:it will give the transaction status .
Below entry is displayed in the transaction tracker in CIG
Ariba status:
Login to Ariba integration manager -> Click on data import and export -> Search for the task Import Batch Data. There will be an entry with the completed transaction.
Go to the details tab; notice that the client type is mentioned a DirectConnect signifying the direct connection that we established. At the bottom of the page the “CpmpanyCode.csv” file is visible.
Search for the task – Company Code and export the company codes to the local machine to verify.
End result – This is how the “.csv” file exported from Ariba will look like
Conclusion
To conclude, this scenario outlines the ease with which we can replicate the master data from S/4 system to Ariba (parent and child site) using the seamless integration capabilities of Ariba CIG (using directconnect). This also eliminates the use of a middle ware in between S/4 and the target system.
Advantages of Using the Direct connectivity
1. Can leverage the integration toolkit in the customer landscape
2. Minimal system requirements to install
3. Coordinate timing with the S/4 for full load or incremental load
This blog post is intended to serve as an end to end, step by step guide on how to replicate the Master data from S4 HANA to SAP Ariba (Procure to Order business process) through CIG direct connection. We will take an example of a company code in this case and will only be dealing with an outbound scenario. So there is no explanation of Cloud Connector as it will come into play for inbound only.
SAP has strategically placed CIG into the integration landscape for ARIBA integration and this blog is intended to show it by example how simple it is to use CIG (IaaS).
Existing methods of Master Data Integration
Master Data replication from S/4 to Ariba is typically done in the below ways.
1. Batch File transfer
a. ‘.csv” files are uploaded or downloaded via Https
b. Multiple records can be transferred in a single batch
c. Processes can be scheduled
2. SAP Direct Connectivity
a. Direct transfer of master data from SAP to SAP Ariba (discussed in this blog)
3. Web services
a. XML messages over Https
b. Only one record per message
c. A Middle ware application is needed to send/receive messages
d. Mappings are needed
e. Real time file processing
f. More responsibility on the customer to installation, modification and maintenance
Steps Involved
The basic steps involved in the end to end master data interface are
1. Configurations in S4 Hana (SPRO configurations)
2. Configurations in Ariba
3. Configurations in CIG
4. Testing of the scenario
Prerequisites
Below mentioned prerequisites are needed to be able to establish the master data interface successfully from S4 Hana to SAP Ariba. Please refer to the attached screenshots:
1. CIG add on to be installed on S4 to enable SPRO configurations and proceed with interface configurations
2. CIG enablement on ARIBA Realm
3. Cloud connector not needed for Outbound; only needed for Inbound
4. Get the partition and variant ID from ARIBA
5. Download the CIG certificate from CIG Integration Portal in Resources
6. Install the CIG certificate in the Integration Toolkit (ITK) on ARIBA (P2O) and also in S4 Hana
o The certificate downloaded in the above step has to be installed in the Ariba ITK in integration manager
o The certificate should also be installed in S/4.
Master Data Integration Architecture
The picture below details the basic integration architecture between S4 Hana and SAP Ariba via CIG. There is a direct connection for master data.
Depicting the Master Data Integration Architecture
Master Data interface flow for reference
Below figure gives only a reference of the master data interface flow and not an exhaustive list, there are other flows as well based on the business process involved.
Configurations in S4 Hana
S4 Configurations in SPRO Tcode
1) Global settings
2) Master Data integration
3) Ariba and CIG Configuration
1 Global Settings
After logging into S4, go to the Tcode – SPRO -> Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings
Below are the steps we need to follow for the configurations sequentially under Global settings:
Figure 4 – Global Settings
1.1 CIG Certificate Installation in S4 Hana
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings
Maintain Certificates
1.2 Create an RFC Destination
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings Create RFC Destination
Use the same P-User which is enabled in CIG (My Configurations -> Authorizations) for the login and security tab in the blow step
1.3 Create a Port
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings -> Create Port Definition (i.e. Port type is XML HTTP)
Make sure that the content type is selected as Text/XML and Soap protocol check box is ticked. Click save.
1.4 Create a Logical System
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings -> Create Logical System
Prerequisite: Client should be opened and is transportable
1.5 Configure the receiver Ports
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings -> Configure Receiver Port
1.6 Send SAP S4 Hana information to SAP Ariba CIG
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings -> Send SAP Information to SAP Ariba Cloud Integration Gateway -> Synchronize SAP Information with SAP Ariba Cloud Integration Gateway
Credentials should be P-User which is enabled in CIG
Once the above step is performed, a connection is established in CIG automatically under the Basic Data tab
1.7 Configure the Variant and Partition IDs
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Ariba Network Integration -> Global Settings -> Map the Variant and Partition for SAP Ariba solutions (REALM ID’s for Partition and Variant are to be received from SAP Ariba Cloud APPS team)
2 Master Data integration
2.1 Configure External Commands for Operating System
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Configure External Commands for Operating System
Note: Based on the Operating system the commands would have to be modified
2.2 Configure Ariba Incremental Extract Event
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Configure Ariba Incremental Extract Event (Click Execute to view the tables)
2.3 Configure Ariba Master Data Incremental Field Restrictions
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Configure Ariba Master Data Incremental Field Restrictions
2.4 Configure Ariba Event Linkages
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Configure Ariba Event Linkages
Prerequisite: Client should be opened
2.5 Maintain parameters for Master Data Integration
a) Cross application
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Maintain Parameters -> Cross Application
Prerequisite: The directories should have been created before this step
b) Procurement
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Procurement
Note: Based on the customer requirements the parameters might vary
2.6 Maintain Filters
a) Cross application
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Maintain Filters -> Cross Application
Note: Based on the customer requirements the parameters might vary (eg: Company_Code_Export from S4 to Ariba)
b) Procurement
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Procurement
2.7 Connection parameters
Add all the child and parent realms for procurement
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings Connection Parameters for Master Data
2.8 Maintain System ID for Master Data
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Maintain System ID for Master Data
2.9 Maintain Date Time Stamp for Master Data
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> General Settings -> Maintain Date Time Stamp for Master Data
2.10 Maintain Field Map for Master Data and Catalog Upload Request
Even if there are no custom mapping fields, this step has to be performed from the golden client to the client on which we have to replicate the data
Navigate to Integration with Other SAP Components -> SAP Ariba Cloud Integration Gateway -> Master Data Integration -> Enhancements -> Maintain Field Map for Master Data and Catalog Upload Request
1. The Change View "Table to maintain mapping of SAP to Buyer fields": Overview screen appears.
2. Click New Entries in the application toolbar to add new entries.
3. Enter the following details:
4. Solution: Select a solution from the list for which you are mapping the field.
5. Structure: Add a structure name. For example, ARBCIG_BP_LANG_STR
6. Field SAP: Add the SAP S/4 field name that you want to map. For example, BUDGETPDTX
7. Field Ariba: Add the Ariba solution field name to which you want to map. For example, Name
8. Click Save.
2.11 Interface set up for Master Data
This is done for establishing the direct connection from S4 to Ariba
o P user ID needed
o URL host needed
o Path prefix needed
After Execute – result is below
(It means that the web service is activated in SOA manager)
Go to the SOA manager transaction (to check the activated web service; no actions required in SOA manager as it is already done in the interface setup)
Searching the activated service from Interface setup via SPRO
3.Configuration in Ariba
3.1 Integration Configuration in Ariba
Go to the Integration manager transaction after logging into Ariba.
Select the Web service as we are importing via Web service
3.2 Certificate installation
Certificate Installation in ITK in Ariba for authentication and to load the data
3.3 Data definition
Data Definition table in Ariba – to know the details of the data
All the Ariba fields for company codes master data
Testing
Testing: Executing extraction program from S4 to Ariba replication of master data
S4 status:
Go to the Tcode - SE38
Program – ARBCIG_MASTER_DATA_EXPORT
Full load is run the first time and there on the incremental load can be executed by creating the variant and scheduling it in the background job.
FPC enables – when we want the data to be replicated to both the parent and child site in Ariba, we have to enable this. We have to get the site name from SAP Ariba Cloud team.
Populate the details as shown below which we configured in the above sections.
Click Execute to start replication
File generated in S4 – Archive folder in AL11 – this is to be replicated into SAP Ariba
Go to the Tcode – SRT_MONI – to check the message processing status
CIG Transaction tracker status:it will give the transaction status .
Below entry is displayed in the transaction tracker in CIG
Ariba status:
Login to Ariba integration manager -> Click on data import and export -> Search for the task Import Batch Data. There will be an entry with the completed transaction.
Go to the details tab; notice that the client type is mentioned a DirectConnect signifying the direct connection that we established. At the bottom of the page the “CpmpanyCode.csv” file is visible.
Search for the task – Company Code and export the company codes to the local machine to verify.
End result – This is how the “.csv” file exported from Ariba will look like
Conclusion
To conclude, this scenario outlines the ease with which we can replicate the master data from S/4 system to Ariba (parent and child site) using the seamless integration capabilities of Ariba CIG (using directconnect). This also eliminates the use of a middle ware in between S/4 and the target system.
Advantages of Using the Direct connectivity
1. Can leverage the integration toolkit in the customer landscape
2. Minimal system requirements to install
3. Coordinate timing with the S/4 for full load or incremental load
- SAP Managed Tags:
22 Comments
