1. Integration Playbooks for Procurement
  2. SOAP Services (Inbound)

SOAP Services (Inbound)

You can use SOAP services to create transactions in Oracle Purchasing.

Note: Oracle recommends using REST APIs rather than SOAP services.

Key Features

  • Perform data updates in real time (inbound).
  • Use the purchase request service to initiate requester changes.
  • Use the purchase order service to initiate buyer changes.
  • Use with Oracle Integration Cloud (OIC) to perform near real-time operations.

Best Practices

REST APIs versus SOAP Services

SOAP services aren't recommended if an equivalent REST API is available.

GET operation

When developing the integration, consider running the GET operation on an existing purchase order to help identify the values to use in the CREATE or CHANGE operations.

CREATE operation

  • When using the CREATE operation, don't provide any key attributes like PO Header ID, PO Line ID, Line Location ID, and PO Distribution ID in the payload because these values will be generated.
  • Provide either an ID or a name but not both. (For example, Payment Terms ID, Payment Terms.)
  • Provide either a code or a name but not both. (For example, Approval Action Code, Approval Action, Currency Code, Currency.)

CHANGE operation

For a CHANGE operation, the system (for example, PO Header ID) or business keys (for example, PO Number and Sold To LE) can be used to find the document.

Constraints

  • This option isn't suitable for importing large volumes of purchasing data.
  • Low in performance and scalability compared to REST APIs.
  • The CREATE and CHANGE operations of the Purchase Order Web Service only support payloads for purchasing documents no more than 200 lines.
    • Purchase order with 200 lines, one line with 10,000 schedules, one line with one schedule and 10,000 distributions.
    • These options are available for purchase orders with more than 200 lines:
      • Use the purchasing document's open interface or file-based data import (FBDI) to create the purchase orders.
      • Split the payload into multiple Purchase Order Web Service calls if more than 200 lines must be uploaded for a single purchase order.
  • To add attachments, use the ERP SOAP Object Attachment Service, which is a utility web service that uploads attachments to Oracle Purchasing purchase agreements and purchase orders. Use this service to upload attachments to documents at the level you want. The operation works only for purchasing documents created by import or by SOAP services.

Related Topics