High- Level Specification
| Parameter | Value |
|---|---|
| Application System (Source) | Syniti |
| Application System ( Target) | SAP Ariba Sourcing |
| Business Process Reference |
Functional Overview
Some Master Data that are required to construct sourcing events in Ariba Guided Sourcing can only be interfaced and there is no option to upload these manually in Ariba Guided Sourcing. CIG add-on provides standard integration program to integrate these master data from an SAP ERP system.
However, for this implementation, data from ECC systems need to be cleansed using Syniti so the source of the data will be technically Syniti and not ECC. With that, the standard CIG add-on cannot be used and thus, custom interface needs to be built.
The middleware to be used to implement the end-to-end integration will be SCPI. This document will explain integration point of SCPI to CIG.
Scope and Objectives
Required Master Data
Listed below are the required Master Data for Ariba Guided Sourcing that need to be interfaced. There will be one set of zip file that needs to be prepared by Syniti:
- CompanyCode.csv
- PurchaseOrg.csv
- PurchaseGroup.csv
- Plant.csv
- PlantPurchaseOrgCombo.csv
- PaymentTerms.csv
- IncoTerms.csv
- IncoTermsDescriptionLang.csv
- ERPCommodityCode.csv
- ItemCategory.csv
- ItemCategoryDescriptionLang.csv
- Schema.csv
Process Flow Diagram
Sourcing Master Data
Step | Description | Comment |
|---|---|---|
1 | The execution of the interface is triggered manually | Sourcing Masterdata are not frequently changing, data transfer will be ran as needed. |
2 | Syniti will generate the Sourcing Master Data CSV files with correct filenames based on the structure required by Ariba Sourcing and zipped these | |
3 | Syniti will call a service in SCPI to send the zipped CSV files to SCPI | |
5 | SCPI will then push the zipped CSV file embedded on the SOAP message based on the required structure/parameters to the CIG endpoint | |
6 | CIG will push the payload request to the Ariba Sourcing endpoint | |
7 | The data in the CSV files get uploaded into Ariba Sourcing |
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
Dependencies
System interface from Syniti to generate the csv files, zipped and call a service in SCPI.
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
- Ariba provide integration tasks requires an External System Configuration for the logical communication channel used when the task is initiated by the SAP ERP using Managed Gateway system.
For Supplemental Realm:
External System ID | External System Name | Type |
<Syniti_DEV> | <Syniti_DEV> | <SAP ECC> |
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
Refer to the links below for the target structure:
Sourcing Master Data
| Field | Description |
|---|---|
Mapping and Calculation
| 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 set of zipped CSV files based on the target structure requirements and calls a service in SCPI to send the zip files to SCPI.
- The CSV filenames should be followed as shown below. The zip filename can be anything but the recommendation is to have a date stamp (SourcingMD_07222025.zip). See the sample files in the Appendix section.
- CompanyCode.csv
- PurchaseOrg.csv
- PurchaseGroup.csv
- Plant.csv
- PlantPurchaseOrgCombo.csv
- PaymentTerms.csv
- IncoTerms.csv
- IncoTermsDescriptionLang.csv
- ERPCommodityCode.csv
- ItemCategory.csv
- ItemCategoryDescriptionLang.csv
- Schema.csv (the content of this file will be constant)
- The CSV filenames should be followed as shown below. The zip filename can be anything but the recommendation is to have a date stamp (SourcingMD_07222025.zip). See the sample files in the Appendix section.
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 | Constant Task or Event Name that triggers the Masterdata load in Ariba Sourcing realm |
| 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 | |
| contentType | application.zip | |
| filename | <Sourcing Masterdata zip filename embedded on the soap message> | |
| Content | Enccoded Base64 format of the attached zipped file |
- 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.
https://drive.google.com/file/d/1iVmJmrxCW9wFLS_fiH8E_vNFSK4NboyT/view?usp=drive_link
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
Delivery Requirements
Delta or Full Load Requirements
For Sourcing MD, the data will always be required to be in Full Load so the content of the CSV files should be the full data.
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
Performance Consideration
There are no specific performance requirements or considerations related to this interface.
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 and check the details of the errors. To correct the error, the administrator must ensure that the data inconsistency is resolved in the SAP ERP system and then must rerun the tasks for the Master Data again from the source SAP ERP system.
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Results |
|---|---|---|
| Sourcing MD files valid and complete | Data will be loaded in Ariba Sourcing | |
| Sourcing MD files in the request do not include the Schema.csv | The request will be completed in CIG but the status of the payload request will be Rejected with error “Schema file not found in payload.” | |
| New records included in the Sourcing MD full files are posted | New records will be loaded in Ariba Sourcing | |
| Some records were removed from the full files | Specific records that were removed will be deactivated in 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 |
|---|---|
| Syniti and Ariba - Master Data Integration | Base |
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
| Integration Flow | Syniti and Ariba - Master Data Integration | Base64 ZIP file send to CIG | |