| Status | |
|---|---|
| Owner | The person responsible for driving this decision and documenting it. Type @ to mention people by name |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
| Jira Request ID | |
| Jira Development ID |
High- Level Specification
| Application System (Source) | Syniti |
|---|---|
| Application System ( Target) | SAP Ariba Sourcing |
| Source System Interface | ERP-110 |
| Target System Interface | Standard Integration with Ariba Sourcing via CIG |
| Business Process Reference |
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 custom 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 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
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 | CIG will push the payload request to the Ariba Parent endpoint, 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 in 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
| Field | Description |
|---|---|
| FromCurrency | ISO Currency |
| ToCurrency | ISO Currency |
| RateIdentifier | concatenation of source destination with a : |
| ValidFrom | start date of rate |
| Rate |
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
| Field | Description | TYPE | |
|---|---|---|---|
| realm | 7452310-SS-T | Configuration | Sourcing realm ID in Supplemental site, a different realm ID would be used for Sourcing realm Test and Production sites |
| event | Import External System Master Data | Constant | Value for event parameter for Ariba Sourcing realm is Import External System Master Data. But when interfacing the same file to Procurement (Buying realm), event value should be set to Import Batch Data. |
| operation | Load And Delete | Constant | Full load, all CSVs must contain all the active data that can be used for Sourcing |
| systemId | <Syniti_DEV> | Configuration | This is the same ERP System ID - ECC or S4HANA setup in CIG and in Administratrion > Master Data Manager > External System Configuration |
| Solution | Sourcing | Constant | When interfacing the Currency Conversion Rates into Sourcing realm, solution value should be Sourcing. But when interfacing the same file to Procurement (Buying realm), solution value should be Buyer. |
| contentType | application.zip | Constant | File type of the attachment |
| filename | <File name of the zipped CurrencyConversionRate.csv file> | Constant | |
| Content | Enccoded Base64 format of the attached zipped file | Mapping and Constants | UTF-8 FromCurrency,UniqueName,ToCurrency,Rate,Date "source.FromCurrency","source.RateIdentifier","source.ToCurrency","source.Rate","sourse.ValidFrom" ← repeated per line in inbound data |
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
- 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/receiveERPMD (OLD, to be decommissioned on Jan 31, 2026) - Basic Authorization - setup with CIG PUser and password
- Parameters:
- CIG endpoint URL for Master Data (EU Data Center):
- 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.
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
- 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.
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
Please provide some guidance and/or test data to help the developer unit test the interface. Please include both positive and negative testing (to validate error situations handling)
The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again, or explain how to create new input data to the test. In particular, the developer will need logons for test users representing the various roles within the approval process.
Test Conditions and Expected Results
| ID | Condition | Expected Results |
|---|---|---|
| Currency Conversion Rates are valid and complete | Data will be loaded to Ariba Parent realm and replicated to Ariba Sourcing | |
| Rates for specific currency is updated | Updated rate is loaded to Ariba Parent and replicated to Ariba Sourcing |
Test Considerations/Dependencies
Test data need to be available in ECC.
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
| Currency Conversion Distribution |
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
| Integration Flow | Currency Exchange to Ariba | ZIP and convert into Base64 send to CIG embedded in XML | |
| Integration Flow | Currency Exchange ECC to All | split to all receiving systems | Multicast supporting IFLOW |
Logic Flow
Configuration Requirements
Appendix
See also
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.
