Skip to main content
← Web Service Payloads & REST API Examples

REST · Supply Chain — Order Management

What is the REST API payload to create a sales order in Oracle Fusion?

POST /salesOrdersForOrderHub — REST payload to create a sales order

REST APIOracle Fusion · Supply Chain · Order ManagementHigh confidenceCurated

The Order Import (Order Hub) REST resource creates a sales order in Order Management. Identify the order with SourceTransactionNumber / SourceTransactionSystem / SourceTransactionId, set the requesting business unit and buying party, and add a lines child array — each line needs its own SourceTransactionLineId and SourceTransactionScheduleId, a product, quantity and UOM.

Endpoint

POSThttps://<your-fusion-host>/fscmRestApi/resources/11.13.18.05/salesOrdersForOrderHub

Purpose

Submit a sales order through Order Import. HTTP POST, Content-Type application/json. The order is created and progresses through orchestration; the response returns the generated OrderNumber and HeaderId.

Parameters

SourceTransactionNumberrequiredYour system's order number — with SourceTransactionSystem, the idempotency key.
SourceTransactionSystemrequiredRegistered source system code (Manage Trading Community Source Systems), e.g. GPR.
SourceTransactionIdrequiredYour system's unique id for the order (often same as SourceTransactionNumber).
TransactionalCurrencyCoderequiredOrder currency, e.g. USD.
RequestingBusinessUnitNamerequiredName of the requesting business unit.
BuyingPartyNumberrequiredCustomer account/party number (or BuyingPartyName).
linesrequiredChild array — one object per line with SourceTransactionLineId, SourceTransactionScheduleId, ProductNumber, OrderedQuantity, OrderedUOMCode.

Example request

Request
{
  "SourceTransactionNumber": "SO-2026-0042",
  "SourceTransactionSystem": "GPR",
  "SourceTransactionId": "SO-2026-0042",
  "TransactionalCurrencyCode": "USD",
  "TransactionTypeCode": "STD",
  "RequestingBusinessUnitName": "US1 Business Unit",
  "BuyingPartyName": "Computer Service and Rentals",
  "BuyingPartyNumber": "1006",
  "lines": [
    {
      "SourceTransactionLineNumber": "1",
      "SourceTransactionLineId": "1",
      "SourceTransactionScheduleId": "1",
      "ProductNumber": "AS54888",
      "OrderedQuantity": 5,
      "OrderedUOMCode": "Ea",
      "RequestedFulfillmentOrganizationCode": "M1",
      "RequestedShipDate": "2026-09-01T00:00:00+00:00"
    }
  ]
}

Example response

Response
{
  "OrderNumber": "509123",
  "HeaderId": 300000246813579,
  "SourceTransactionNumber": "SO-2026-0042",
  "SourceTransactionSystem": "GPR",
  "StatusCode": "DRAFT",
  "TransactionalCurrencyCode": "USD",
  "links": [
    { "rel": "self", "href": ".../salesOrdersForOrderHub/300000246813579" },
    { "rel": "child", "name": "lines", "href": ".../salesOrdersForOrderHub/300000246813579/child/lines" }
  ]
}

Call lifecycle

  1. 01

    Basic auth or OAuth 2.0 bearer token.

    • User needs the Order Entry Specialist / create-order privilege
  2. 02
  3. 03
  4. 04

Related questions

GroundingCurated

Retrieved from the curated Oracle knowledge layer — table metadata, joins and process flows.

Need a variation, or a different service?

Continue in Ask Oracle AI