| 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 |
| Implementing System | Syniti |
|---|---|
| Invokes | ERP-104 |
| Business Process Reference |
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 Syniti to SCPI.
Required Master Data
Listed below are the required Master Data for Ariba Guided Sourcing that need to be interfaced. There will be a set of CSVs that needs to be prepared by Syniti.
Please refer to Appendix for the sample CSV files.
Process Flow Diagram

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 |
Assumptions
System interface from Syniti to generate the csv files, zipped and call a service in SCPI.
The following are the Security and Authorization considerations for this interface:
For Supplemental Realm:
External System ID | External System Name | Type |
<Syniti_DEV> | <Syniti_DEV> | SAP ECC |
Not applicable
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.
Populate the type of the API use in this section. Will the API be Consumed or Provided.
Refer to the links below for the target structure:
Sourcing Master Data
| Parent | Field | Description | Mandatory (Y/N) | Data Type |
|---|---|---|---|---|
| Parent | Field | Rule Type | Rule Instruction |
|---|---|---|---|
Delta or Full Load Requirements
These 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:
Not Applicable
Not Applicable
There are no specific performance requirements or considerations related to this interface.
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:
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 | |
Sourcing MD files in the request do not include the ItemCategoryDescriptionLang.csv and IncoTermsDescriptionLang.csv | The request will be completed in CIG but the status of the payload request will be Rejected with error “Dependencies ariba.masterdata.xDescriptionLang are missing for type ariba.masterdata.x.” |
Test data need to be available in ECC for Syniti’s extraction.
| Package Name | Parent Package |
|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
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.
