SOAP Services

Use the Simple Object Access Protocol (SOAP) web services to create requisitions.

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

Key Features

• Use these operations to create requisitions:
  • createRequisition
  • populateInterfaceTable
  • submitImportRequisition

• Use this operation to cancel requisitions:

  • changePurchaseRequestAsync

• Use this operation to hold or release hold requisitions:
  • controlPurchaseRequestAsync

Best Practices

• The same file-based data import (FBDI) best practices still apply to SOAP.
• Considerations for the create requisitions operations:
  • createRequisition: The createRequisition operation writes attributes into a requisition interface table and then starts the requisition import process to create a requisition. Each call with this operation will create one requisition or more, depending on the requisition headers.
  • populateInterfaceTable and submitImportRequisition: Large requisitions calling applications first loads the interface table using the populateInterfaceTable operation. Once all data is loaded into the interface table, the application calls the Purchase Request Web Service with the submitImportRequisition operation to initiate the requisition import process to create requisitions.
• Considerations for hold and release hold operations:
  • Applications can request a hold for requisition lines to prevent buyers from adding these lines to purchase orders. Once the requisition line has a hold, the application can request either a cancellation of the line or a release hold so buyers can process it. This feature is available only via SOAP and for externally managed requisitions.
• REST APIs versus SOAP services:
  • Given the deprecation plans of the SOAP services, it's recommended that you use REST APIs rather than SOAP services to create or update requisitions.

Constraints

• Event subscription isn't supported for requisitions.
• To update or cancel requisitions, consider using REST APIs.
• Importing legacy data isn't supported. The requisition import via SOAP is to create requisitions that will be placed on purchase orders after the approvals are complete.
• There's no option to re-process requisition import for a batch that failed validation. You must re-submit the request to create the requisition.
• There's no option to purge the requisition interface tables.
• Importing requisitions for internal material transfers, maintenance work orders, and those with one-time locations isn't supported.