High-Level Specification

Functional Overview

Currently, Icertis syncs Supplier Master Data with SAP Ariba Sourcing, capturing supplier names and details. However, SAP Ariba Sourcing does not store Purchasing Organization or Supplier Preferred Currency information. This creates a gap because:

• Purchasing Organization is essential for filtering suppliers and for passing accurate data to SAP ECC/S4 when creating an Outline Agreement.
• Supplier Currency is required for invoicing purposes and must be consistently maintained across systems.

To bridge this gap, an interface will be built where Syniti sends updated Supplier details (including Purchasing Organization and Supplier Preferred Currency) to SAP CPI, which then forwards the data to Icertis using the Bulk Master Data API for Supplier Master.

Scope and Objectives

• Enable Icertis to receive and store Purchasing Organization and Supplier Preferred Currency for each supplier.
• Ensure consistency of supplier master data across systems.
• Support full load during initial sync and delta updates daily.
• Syniti will generate and send an Excel file to CPI daily which will be sent to Icertis for further processing.

Sequence Diagram

{
    "Data": {
        "JobItems": [
            {
                "SysId": "96c08d87-3c89-4b7d-b075-e360bb41db07",
                "UseExternalId": "false",
                "NextState": "",
                "EndPointVersion": "3",
                "RequestIdentifier": "1",
                "RequestBody": {
                    "ICMFromCurrency": "USD",
                    "ICMRate": "0.8700000000",
                    "Name": "USD:EUR",
                    "ICMToCurrency": "EUR"
                }
            },
            {
                "SysId": "5449222c-3d3a-4044-baae-a17165381ed1",
                "UseExternalId": "false",
                "NextState": "",
                "EndPointVersion": "3",
                "RequestIdentifier": "2",
                "RequestBody": {
                    "ICMFromCurrency": "SGD",
                    "ICMRate": "0.6600000000",
                    "Name": "SGD:EUR",
                    "ICMToCurrency": "EUR"
                }
            }
        ],
        "HasMoreData": "false",
        "ContractTypeName": "ICMCurrencyExchangeRate"
    }
}

Assumptions

• Supplier ID is unique and consistent across SAP and Icertis.
• Multiple purchase org values will be sent for a single supplier

Dependencies

• In Icertis, within Supplier Masterdata, Purchase Org field should be configured as multiselect. 

Security, Integrity and Controls

• Secure authentication mechanisms are in place at middleware for access to Icertis systems:
• Secure HTTPS protocol is used for all data transfers between the middleware and Icertis, ensuring encrypted communication and protection against unauthorized access.
• OAuth 2.0 authentication is implemented for accessing Icertis APIs via an Azure-registered application, providing token-based security and controlled access
• Audit logging captures all integration transactions, including timestamps, request/response metadata, and error details for traceability and compliance.

Configuration Requirements

Technical Configuration

• Azure Application Registration

  • Since Icertis relies on Azure Active Directory as its identity provider (IdP), an application must be registered in Azure to enable OAuth 2.0 token generation and validation. This establishes trusted access between the middleware and the Icertis APIs.

  • The application registration includes defining the client ID, client secret, scope, and API permissions required to access the Icertis endpoints.

Functional Configuration

• Supplier Masterdata Configuration
  • Add Purchasing Organization multi select field lookup on Purchasing Organization Masterdata.
  • Add Supplier Preferred Currency string field

Special Requirements

• Not Applicable

Design Rationale

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

Processing Logic

Processing within Source

Processing within Middleware

Processing within Target

Interface Dependency

Interface Constraints

Delivery Requirements

Sequencing

Delta or Full Load Requirements

Interface Alert & Monitoring

Interface Reporting

Language Requirements

User Interface Requirements

Volumetrics

Performance Consideration

Error Handling

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Change log