1. REST API for Oracle Fusion Cloud SCM
  2. Tasks
  3. Supply Chain Planning
  4. Collaboration Customer Demand Measure Quantities

Update a measure quantity

patch

/fscmRestApi/resources/11.13.18.05/collaborationCustomerDemandMeasureQuantities

Update a measure quantity

Request

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/vnd.oracle.adf.resourceitem+json ()
Root Schema : schema
Type: array
Show Source
Nested Schema : collaborationCustomerDemandMeasureQuantitiesBulk-item
Type: object
Show Source
Request Body - application/json ()
Root Schema : schema
Type: array
Show Source
Nested Schema : collaborationCustomerDemandMeasureQuantitiesBulk-item
Type: object
Show Source
Request Body - application/batch+json ()
Root Schema : schema
Type: array
Show Source
Nested Schema : collaborationCustomerDemandMeasureQuantitiesBulk-item
Type: object
Show Source
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 : collaborationCustomerDemandMeasureQuantitiesBulk-item-response
Match All
Show Source
Nested Schema : ItemsBulkProperties
Type: object
Show Source
Nested Schema : count
Type: object
Show Source
  • Title: count
    The number of resource instances returned in the current range.
Nested Schema : collaborationCustomerDemandMeasureQuantitiesBulk-item-response-allOf[2]
Type: object
Nested Schema : Items
Type: array
Title: Items
The item relations associated with the resource instance.
Show Source
Nested Schema : bulk-post-item
Type: object
Show Source
  • Value that uniquely identifies associated consolidated orders.
  • Title: Firm Date
    Date when supply is due. This attribute is a fixed value that can't be rescheduled by planning and is only populated when the firm status is firm.
  • Title: Firm Quantity
    Fixed quantity of supply. This attribute value can't be changed by planning and is only populated when the firm status is firm.
  • Title: Implement Date
    Date when the order is released.
  • Title: Implement Dock Date
    Date when the material should be on the receiving dock when the order is released.
  • Title: Implement Firm
    Value that indicates whether the order is firm or not. Valid values are 1: Firm and 2: Not Firm. A list of accepted values is defined in the lookup type MSC_YES_NO.
  • Title: Implement Quantity
    Quantity of the order that's released.
  • Title: Implement Ship Date
    Date when the order is shipped.
  • Value that uniquely identifies the item associated with the supply.
  • Title: Mark For Release Option
    Value that indicates the release status of the order. Valid values are 1: Marked For Release or 2: Not Marked For Release. When marking or not marking orders for release, the request body must include only the MarkForReleaseOption attribute.
  • Title: Object Version Number
    Number of times the supply row was updated. This attribute is used to implement optimistic locking. This number is incremented every time the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried.
  • Title: Order Type
    Type??of??order??such??as??planned??order,??purchase??order,??or??purchase??requisition.??A??list??of??accepted??values??is??defined??in??the??lookup??type??MSC_ORDER_TYPE.
  • Value that uniquely identifies the organization associated with the order.
  • Value that uniquely identifies the order based on planId, transactionID and a system generated part key.
  • Value that uniquely identifies the plan.
  • Title: Price Savings
    Value that indicates the amount of savings realized from actions taken against the order in buyer planning.
  • Title: Release Group Code
    Abbreviation??that??identifies??a??custom??grouping??created??in??buyer??planning??used??by??procurement??in??the??purchase??order??creation??process.
  • Title: Release Status
    Value that indicates the release status of the order. A list of accepted values is defined in the lookup type ORA_MSC_ORDER_RELEASE_STATUS.
  • Title: Release Status Code
    Release status of the order such as ready for release, marked for release or released. A list of accepted values is defined in the lookup type ORA_MSC_BP_RELEASE_STATUS.
  • Value that uniquely identifies the source supplier.
  • Value that uniquely identifies the specific supplier site from where the item is being sourced.
  • Value that uniquely identifies the supply transaction. This value is internally generated by the application.
Back to Top