Updates the allocated award quantity for a given line and response.

patch

/fscmRestApi/resources/11.13.18.05/supplierNegotiationPurchasingDocuments/{AuctionHeaderId}/child/lineAllocationsSummary/{lineAllocationsSummaryUniqID}/child/lineAllocationsByResponse/{lineAllocationsByResponseUniqID}

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
  • This is the hash key of the attributes which make up the composite key--- BidNumber, BidLineNumber and RequisitionLineId ---for the Line Allocations by Supplier Response resource and used to uniquely identify an instance of Line Allocations by Supplier Response. The client should not generate the hash key value. Instead, the client should query on the Line Allocations by Supplier Response collection resource with a filter on the primary key values in order to navigate to a specific instance of Line Allocations by Supplier Response.

    For example: lineAllocationsByResponse?q=BidNumber=<value1>;BidLineNumber=<value2>;RequisitionLineId=<value3>
  • This is the hash key of the attributes which make up the composite key--- AuctionHeaderId and LineNumber ---for the Line Allocations Summary resource and used to uniquely identify an instance of Line Allocations Summary. The client should not generate the hash key value. Instead, the client should query on the Line Allocations Summary collection resource with a filter on the primary key values in order to navigate to a specific instance of Line Allocations Summary.

    For example: lineAllocationsSummary?q=AuctionHeaderId=<value1>;LineNumber=<value2>
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
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 : supplierNegotiationPurchasingDocuments-lineAllocationsSummary-lineAllocationsByResponse-item-response
Type: object
Show Source
Back to Top