High- Level Specification

Functional Overview

CIG add-on provides standard integration program to integrate some master data from SAP ERP system into Ariba.

However, for the Currency Conversion Rates, the source will be the ECC but without the CIG add-on installed thus the decision is to have this go through Syniti as wellcustom code as this data is also required for other sources.

The middleware to be used to implement the end-to-end integration will be SCPI.  This document will explain integration point of Syniti ECC to SCPI.

Scope and Objectives

Below is the required Master Data for Ariba Guided Sourcing that need to be interfaced.  

• CurrencyConversionRate.csv

Process Flow Diagram

           

draw.io Diagram
border true diagramName Untitled Diagram-1762235379283 simpleViewer false width links auto tbstyle top lbox true diagramWidth 491 height 61 revision 1

Image Removed

Step	Description	Comment
1	The execution of the interface is triggered as per the defined job schedule - once daily in ECC (batch job) ECC generates an outbound data flow using rules/logic setout in ERP-110
2	SCPI then maps, zips and base64 encodes the data into a payload and adds additional segments required for success in CIG processing
3	2	Syniti will generate the CurrencyConversionRate.csv files with correct filename based on the structure required by Ariba Sourcing and zipped this	3	Syniti will call a service in SCPI to send the zipped CSV file to SCPI	4	SCPI will then push the zipped CSV file embedded on the SOAP message based on the required structure/parameters to the CIG endpoint	5	CIG will push the payload request to the Ariba Parent endpoint	6	, The data in the CSV file get uploaded into Ariba Parent and replicated to Ariba Sourcing realm

Assumptions

• SCPI uses CIG standard SOAP format both for connectivity and pushing the data to CIG 

Dependencies

• System interface from

• ECC to generate the Currency Converstion Rate

• proxy.
• A scheduled job which will run once daily, is created in ECC to push the formatted data into SCPI → Ariba CIG

Security, Integrity and Controls

The following are the Security and Authorization considerations for this interface:

• Define a Web Services Security certificate and/or the shared secret key to use to secure the End Point connection.
• Access to interface parameters in SAP Ariba Sourcing are being addressed by Ariba standard security controls. Only authorized person with Ariba administrator’s role can access/ change interface parameters.
• Web service security configuration allows secure communications protocol provides a means for applying security to Web services.

Configuration Requirements

• When interfacing Currency Conversion

• Rates into Ariba Procurement solution (Buying realm) and make it available for use in Ariba Sourcing solution,

• for suite-integrated sites

• :
  • Enable the parameter Application.AQS.EnableCurrencyConversionRateSetSync
  • Enable SAP Integration Suite, managed gateway for spend management and SAP Business Network (Europe Data Center) or CIG in SAP Ariba > Core Administration > Integration Manager > Managed Gateway for Spend&Network 

Special Requirements

Not applicable

Design Rationale

Since there is no S/4HANA system for R2, it is needed to use another system as source. ECC can be used but this solution will use Syniti as the source because Syniti has the cleansed data availablein a non-standard iflow integration to allow for additional systems like icertis to leverage the flow of data at the same time .

Data Structure

Source Structure

The following fields will be used to provide the required information for this interface:

Source Structure is based on the following XSD ExchangeRateSchemaECC.xsd

Target Structure

The following fields will be used to provide the required information for this interface:

The target Structure is CSV in the payload with additional XML elements wrapping

Mapping and Calculation

Processing Logic

Processing within Source

Processing within Source

• Extract and transform creating the base data required by Ariba/Icertis

Processing within Middleware

• SCPI will receive the XML from ECC
• The CSV filename should be followed as shown below. The zip filename can be anything but the recommendation is to have a date stamp (CurrencyConversionRate_07222025.zip)
  • CurrencyConversionRate.csv

Processing within Middleware

• • SCPI will receive the zipped CSV files from Syniti
• SCPI will embed the zipped CSV files in base64 to CIG via the CIG endpoint URL (as stated below) following the standard SOAP message structure
  • CIG endpoint URL for Master Data (EU Data Center):
    Test instance: https://test-integration.eu.managedgateway.cloud.sap/cxf/receiveERPMD (NEW URL should be used) ; https://testacig.ariba.com/cxf/receiveERPMD (OLD, to be decommissioned on Jan 31, 2026)
    Production instance: https://integration.eu.managedgateway.cloud.sap/cxf/receiveERPMD (NEW URL should be used); https://acig.ariba.com/cxf/receiveERPMDFor the Sourcing MD, below is the example payload request. Note that the value for the realm parameter will change based on the Ariba realm where the master data will be interfaced to (OLD, to be decommissioned on Jan 31, 2026)
  • Basic Authorization - setup with CIG PUser and password
  • Parameters:  

• Below is the sample payload request of Currency Conversion Rate interfaced to Sourcing realm as well as the zipped CSV file embedded on the payload.

• For

  To upload the Currency Conversion Rates into Ariba Buying solution, the soap message will be the same for the Sourcing MD except for some differences as stated below:

  • • The Ariba event name to be called is Import Batch Data
    • Value for the Solution parameter will be Buyer
  • There is only 1 system ID parameter
  • There is no operation parameter as this will already be covered by the fullload parameter

    

  Image Removed

    

  Image Added

• Below is the sample payload request of Currency Conversion Rate interfaced to Buying realm, same zipped CSV file used on the Sourcing sample above.  

• SCPI will trigger the scheduled job (once daily) to send the formatted data to Ariba 

Processing within Target

Ariba Master Data Import tasks enables exchange of data between SAP ERP and SAP Ariba Sourcing using SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network.

Interface Dependency

Interface Constraints

The maximum file size for a CSV or ZIP that is imported via the Ariba Administration area is 40MB, this applies to all Ariba solutions. 

The same "Import Master Batch Data" event is triggered for the other master data below, which should be considered during batch job scheduling if they will be interfaced and will be zipped separately. 

Image RemovedImage Added

Delivery Requirements

The job to trigger this interface will be scheduled to run once daily, in SCPI after it receives the file from Syniti system

Delta or Full Load Requirements

The CSV file will contain the delta. The way Ariba loads these rates are technically in delta mode.

Interface Alert & Monitoring

The following should be monitored:

• Interface is active (both inbound, process and outbound component)
• Failures on inbound, processing and outbound side need to be handled (restart, if still failure; skip and communicate)
• Messages are processed in reasonable time (XX elapse time)

Interface Reporting

There are no specific reporting requirements for this interface.

Language Requirements

Not Applicable

User Interface Requirements

Not Applicable

Volumetrics

Once per day - assuming no failures

Number of records in each individual execution is setup in the ECC system interface - ERP-110

Performance Consideration

No specific considerations given the small volume of data and non-urgent nature

Error Handling

The interfaces are based on standard integration content, mainly standard data mapping, so errors are unlikely but there are still foreseeable error scenarios related to data selection, data content, or data mapping.

Administrators can check errors using the following methods:

• Configure email notification alerts on the SAP Ariba application system to receive notification when an error occurs. This enables the administrator to log in to the SAP Ariba application to check the details of the errors.
• Directly log in to the SAP Ariba application, go to Administration or Core Administration > Integration Manager > CIG (Managed Gateway for Spend&Network) > 
  Visit the SAP Integration Suite, managed gateway for spend management and SAP Business Network (Europe Data Center) and check the details of the error.
• Directly log in to the SAP Ariba application, go to Administration or Core Administration > Integration Manager or Site Manager > Import (Import Master Data Batch Pull) and check the details of the errors.
• To correct the error, the administrator must ensure that the data inconsistency is resolved in the ECC system and then must rerun the tasks for the Master Data again from the source system.

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Test data need to be available in ECC.

Other Information

Development Details

Package

Other Development Objects

Logic Flow

1. Map from Proxy (ECC) XML to CIG compatible CSV - UTF-8 header and column headers.
2. ZIP and Base64 the content 
3. Generate UUID required for Ariba Upload
4. Set various system variables like ECC SID, Ariba Realm
5. Generate XML with specific values and tags to trigger CIG correctly
6. Post to Ariba/CIG

Image Added

Configuration Requirements

Image AddedImage Added 

Appendix

See also

Change log