1. Integration Playbooks for Procurement
  2. Set Up the Integration

Set Up the Integration

In Oracle Integration Cloud (OIC), use this procedure to set up the integration.

Create the Integration

  1. Select App Driven Orchestration.
  2. Enter a name and description for the integration.

Add the ERP Cloud Adapter as a Trigger

  1. From the Receive Business Event drop-down list, select Supplier Created.
  2. Provide an endpoint name and review payload structure.

Add Actions Within the Integration Flow

Complete these substeps, in sequence, as part of your integration design.

  1. (Optional) Retrieve supplier details from Oracle Supplier Model using the GET operation.
    Note: This step is optional and should be used only if the external data provider requires more supplier identifiers to uniquely identify the supplier.
    1. Add an invoke action using the ERP Cloud Adapter connection.
    2. In the data mapper, map SupplierId from the event payload to the REST API request.
    3. Configure this invoke to call the Suppliers REST API (for example, /fscmRestApi/resources/latest/suppliers/{SupplierId}) with the GET operation.

      The response will include attributes such as SupplierId, SupplierName, D-U-N-S Number, TaxpayerID, and other standard supplier fields.

  2. Retrieve enrichment data from the external data provider (API method, per specification).
    1. Add an invoke action using the REST Adapter connection that was created for the external data provider.
    2. Consult the external data provider’s API documentation to identify the appropriate operation to use (POST, GET). You then can design your OIC integration according to their guidance. The operation is based on whether data is retrieved synchronously or requires a follow-up call.
      • If data is returned synchronously, use a single invoke action (for example, POST or GET).
      • If data is retrieved asynchronously, implement a two-step flow (for example, an initial POST to start enrichment and then a follow-up GET to retrieve results).
    3. Map relevant supplier data (such as SupplierId, SupplierName, CustomerID, D-U-N-S Number, and TaxpayerID) into the external data provider request as required.

      Whether from the initial or a follow-up call, the response, when invoked successfully, will include the requested enrichment data (such as Risk Score, Credit Score, Days Payable Outstanding, Compliance Screening, and ESG Ranking Score) making these values available as output.

  3. Update the Supplier Profile with enrichment data using the PATCH operation.
    1. Add an invoke action using the ERP Cloud Adapter to update the supplier in Supplier Model.
    2. Configure the resource URI for PATCH. For example, /fscmRestApi/resources/latest/suppliers/{SupplierId}.
    3. In the data mapper, map the SupplierId and each enrichment field (for example, risk scores, and financial stability) from the external data provider response directly to their corresponding supplier attributes or descriptive flexfields (DFFs).
      Note: Ensure that DFF attribute codes are consistent with your Oracle Fusion Cloud Procurement configuration.
    4. Apply any necessary data transformations to meet payload or format requirements for the PATCH operation.
  4. Test and activate the integration.
    1. Test the flow to confirm event triggering, data retrieval, external data provider integration, and supplier enrichment work as expected.
    2. Activate the integration.