High- Level Specification

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

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.

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

• Enable the parameter Application.AQS.EnableCurrencyConversionRateSetSync when interfacing Currency Conversion rate into Ariba Procurement solution and make it available for use in Ariba Sourcing solution,  for suite-integrated sites. 

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

The following fields will be used to provide the required information for this interface:

Mapping and Calculation

Populate the table below to list the target / source data field mapping between the Source system and Target system

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
  • 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

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

Detail how errors will be handled: Notification, Restart/ Recovery and Re-Processing Procedures

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

Test Considerations/Dependencies

List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.

Other Information

Development Details

Package

Other Development Objects

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.

Change log