3684543 - Process Intelligence OData Connector cannot connect to SAP Ariba because no OData Service Root is available

When configuring the SAP Signavio Process Intelligence (PINT) OData Connector, users attempt to connect to SAP Ariba or SAP Field Service Management (FSM).

The connector prompts for:

• OAuth Client ID
• OAuth Client Secret
• OAuth Access Token URL
• Service Root

Although SAP Ariba exposes REST APIs and OAuth credentials, there is no Service Root URL that works with the PINT OData Connector. Attempts to use Ariba or FSM API endpoints result in connection failures, as the PINT OData Connector does not accept the URLs.

• Users expect the OData connector to work because some Signavio accelerators (e.g., Start Cross Mining for Procure to Pay in SAP S/4HANA and SAP Ariba) contain Ariba scenarios.

1. Ariba and FSM cannot be connected to PINT using the OData Connector

• The PINT OData Connector only supports true OData services.
• SAP Ariba does not expose OData services; it exposes REST APIs with different payloads and structure.
• Because Ariba is not OData-compliant, there is no valid "Service Root" for the connector.
• FSM follows a similar pattern and also does not provide an OData endpoint compatible with PINT.

2. Why the connector cannot use Ariba’s REST APIs

• The connector cannot interpret Ariba’s REST payload formats.
• No automatic mapping or transformation exists in PINT.
• Even if authentication succeeds, the connector cannot process the data model.

3. How Ariba-based accelerators work

• Ariba accelerators rely on a BTP integration application, not direct OData connectivity.
• This integration layer handles:
  • Calling Ariba REST APIs
  • Authentication
  • Data extraction
  • Data transformation
  • Mapping into the PINT Ingestion API format

4. Supported methods to load Ariba or FSM data into PINT

• To bring Ariba or FSM data into Process Intelligence, customers must use one of the following:
  • A. Services-Led Integration (Recommended)
    • SAP Services deploy a BTP middleware application that extracts and transforms data from Ariba or FSM.
    • Required for customers using accelerators or complex integrations.
  • B. Bring-Your-Own Integration (Ingestion API)
    • Customers can create their own middleware to:
      • Call Ariba/FSM REST APIs
      • Transform the data
      • Push it into PINT via the Ingestion API

5. Summary

• No valid Ariba or FSM “Service Root” exists for the OData Connector.
• Only Services-led or custom Ingestion API-based integration paths are supported.

PINT; Process Intelligence; OData; Service Root; Ariba; FSM; API; REST API; ingestion API; BTP integration; accelerators; data extraction; middleware; P2P accelerator; OAuth;  , KBA , BPI-SIG-PI-DS , Data Source (CSV, Connector) , Problem