Update one order preference

patch

/fscmRestApi/resources/11.13.18.05/salesOrdersForOrderHubRequests/{OrderKey}/child/orderPreferences/{orderPreferencesUniqID}

Request

Path Parameters
  • Value that uniquely identifies the sales order. This value is derived by concatenating the value of SourceOrderSystem, a colon, and the value of SourceOrderId. For orders created through the Oracle Order Management Cloud work area, the SourceOrderId is same as the HeaderId. For example, if SourceOrderSystem is LEG and SourceOrderId is R13_Sample_Order, the value of this attribute is LEG:R13_Sample_Order.
  • This is the hash key of the attributes which make up the composite key for the Order Preferences resource and used to uniquely identify an instance of Order Preferences. The client should not generate the hash key value. Instead, the client should query on the Order Preferences collection resource in order to navigate to a specific instance of Order Preferences to get the hash key.
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Maximum Length: 1
    Contains one of the following values: true or false. If true, then the application creates the customer related information even if the customer, site, or contacts don't exist in the customer model while creating the order. If false, then the application doesn't create the customer related information if there is no matching customer, site, or contact and order validation will fail. The default value is false.
  • Maximum Length: 1
    Contains one of the following values: true or false. If true, then the application validates and submits the sales order. If false, then the application doesn't validate and submit and the sales order is in the draft status. The default value is false.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : salesOrdersForOrderHubRequests-orderPreferences-item-response
Type: object
Show Source
  • Maximum Length: 1
    Contains one of the following values: true or false. If true, then the application creates the customer related information even if the customer, site, or contacts don't exist in the customer model while creating the order. If false, then the application doesn't create the customer related information if there is no matching customer, site, or contact and order validation will fail. The default value is false.
  • Links
  • Maximum Length: 1
    Contains one of the following values: true or false. If true, then the application validates and submits the sales order. If false, then the application doesn't validate and submit and the sales order is in the draft status. The default value is false.
Back to Top