| 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
| Parameter | Value |
|---|---|
| Application System (Source) | Syniti |
| Application System ( Target) | SAP Ariba Sourcing |
| 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 but without the CIG add-on installed thus the decision is to have this go through Syniti as well.
The middleware to be used to implement the end-to-end integration will be SCPI. This document will explain integration point of Syniti 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 | |
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
- Syniti is able to extract the required master data which are standard SAP data
- Syniti can zip the CSV files and send these to SCPI by calling a service
- SCPI uses CIG standard SOAP format both for connectivity and pushing the data to CIG
Dependencies
- System interface from Syniti to generate the Currency Converstion Rate csv file, zip it and call a service in SCPI.
- A scheduled job is created in SCPI to push the formatted data into 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 available.
Data Structure
Source Structure
The following fields will be used to provide the required information for this interface:
| Field | Description |
|---|---|
Target Structure
The following fields will be used to provide the required information for this interface:
| Field | Description |
|---|---|
Mapping and Calculation
Populate the table below to list the target / source data field mapping between the Source system and Target system
| Source Table | API or Portlet Name | Source Field | Required (Y/N) | Description | Target Field | API or Portlet Name | Target Field | Required (Y/N) | Description | Rule Type | Rule Instruction |
|---|---|---|---|---|---|---|---|---|---|---|---|
Processing Logic
Processing within Source
- Syniti prepares a zipped CSV files based on the target structure requirements and calls a service in SCPI to send the zip files to SCPI.
- 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://testacig.ariba.com/cxf/receiveERPMD
Production instance: https://acig.ariba.com/cxf/receiveERPMD - Basic Authorization - setup with CIG PUser and password
- Parameters:
- CIG endpoint URL for Master Data (EU Data Center):
| name | value | description |
|---|---|---|
| realm | 7452310-SS-T | 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 | 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 | Full load, all CSVs must contain all the active data that can be used for Sourcing |
| systemId | <Syniti_DEV> | This is the same ERP System ID - ECC or S4HANA setup in CIG and in Administratrion > Master Data Manager > External System Configuration |
| Solution | Sourcing | 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 | File type of the attachment |
| filename | <File name of the zipped CurrencyConversionRate.csv file> | |
| Content | Enccoded Base64 format of the attached zipped file |
- 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 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
Please describe any dependency to other interfaces, e.g. messages of interface x need to be processed before message processing of interface y can start.
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
Please describe delivery requirements driven by business. i.e. real time, batch, scheduled, synchronous, triggering requirement, push or pull, etc.
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
Provide volumetrics details: Initial load volumes, Number of Records, Expected Frequency, Expected Long term Growth)
Performance Consideration
Specify if there are any specific performance factors that need to be taken into consideration during development i.e. interface must be able to handle 100 posting per-hour, etc.
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 Syniti 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 for Syniti’s extraction.
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
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.
