High- Level Specification

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 2 sets of zip that needs to be prepared by Syniti

1^st set

• 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

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:

• Enable the parameter Application.AQS.EnableCurrencyConversionRateSetSync

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:

Target Structure

Refer to the links below for the target structure:

 Sourcing Master Data

Currency Conversion Rate

Mapping and Calculation

Processing Logic

Processing within Source

• Syniti prepares 2 sets of zipped CSV files based on the target structure requirements and calls a service in SCPI to send the zip files to SCPI.
  • 1^st set: 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)
    • 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. See the file in the Appendix section)

• • 2^nd The CSV filenames 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
• For 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.

• For the Currency Conversion Rates, 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

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.

For Currency Conversion Rates, the csv file will contain the delta. Though the operation in the SOAP message is full, 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

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

Test Considerations/Dependencies

Test data need to be available in ECC for Syniti’s extraction.

Other Information

Development Details

Package

Other Development Objects

Appendix

Schema.csv

See also

Change log