1. Integration Playbooks for SCM
  2. SOAP Service

SOAP Service

Use the SOAP service integration option to perform custom business processes during order processing flows.

SOAP service is an external service integration used for fulfillment processing. With the Oracle Fusion Cloud Order Management external interface layer, both inbound and outbound external integrations that use the orchestration engine are supported.

Key Features

  • Custom tasks let customers perform custom business functions by calling their external services.
  • The OrderFulfillmentResponse service lets customers send deferred responses from the external integration layer to Oracle Order Management to advance the process.
  • Provides custom business functions that can perform processing outside of the native order-processing flow.
  • Supports both synchronous and asynchronous automated integration between Oracle Order Management and external integrations.
  • Supports events-based integration.

Best Practices

  • Recommended for performing custom business processes during order processing flows. For example:
    • Compliance checks using an external system.
    • Calculate shipping charges and then return to loop back to Oracle Order Management.
    • Customer confirmation after shipment.
  • Use the asynchronous pattern if a business function has processing delays.
  • Use the synchronous pattern when processing is guaranteed to be completed within few seconds.
    Note: This method is best for minor updates or for triggering another processing unit with a simple confirmation. It's also best in cases where the final outcome of the external application's processing isn't pertinent or necessary.
  • An events-based approach is recommended when a feedback loop, such as FYI or fire-and-forget mode, isn't needed.
  • Oracle Order Management always recommends that customers read the delayed responses through the Oracle ADF-based OrderFulfillmentResponse service when called in asynchronous mode before performing the next Oracle Order Management operation.
  • Build a fault-tolerant integration. For example, one that would let customers perform multiple retries from Oracle Integration Cloud (OIC) custom integration layers to resend the request on Oracle Order Management when a transient failure is received.
    Note: In case of persistent failures, customers might need to correct the data set and resend or Contact Oracle Support.

Constraints

None.

Notes

  • Customers can choose to use their proprietary system to build these custom business functions.
  • Customers can choose to use Oracle Integration Cloud (OIC).
  • When building these services, it's required to conform to Oracle's abstract Web Services Description Language (WSDL), which guarantees the handshake contracts between Oracle Order Management and external systems. For specific information, see Connect Order Management to Your Fulfillment System, Step 13 in the Create Connection section.