Jump to

• Request
• Response

Delete one business unit access entry for the purchase agreement

delete

/fscmRestApi/resources/11.13.18.05/supplierNegotiationPurchasingDocuments/{AuctionHeaderId}/child/purchasingDocuments/{purchasingDocumentsUniqID}/child/agreementBusinessUnitAccesses/{agreementBusinessUnitAccessesUniqID}

Request

Path Parameters

• AuctionHeaderId(required): integer(int64)
  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=
• agreementBusinessUnitAccessesUniqID(required): string
  This is the hash key of the attributes which make up the composite key--- BidNumber, POSequenceNumber and SequenceNumber ---for the Business Unit Access for Purchase Agreements resource and used to uniquely identify an instance of Business Unit Access for Purchase Agreements. The client should not generate the hash key value. Instead, the client should query on the Business Unit Access for Purchase Agreements collection resource with a filter on the primary key values in order to navigate to a specific instance of Business Unit Access for Purchase Agreements.
  
  For example: agreementBusinessUnitAccesses?q=BidNumber=<value1>;POSequenceNumber=<value2>;SequenceNumber=<value3>
• purchasingDocumentsUniqID(required): string
  This is the hash key of the attributes which make up the composite key--- ResponseNumber and SequenceNumber ---for the Purchasing Documents resource and used to uniquely identify an instance of Purchasing Documents. The client should not generate the hash key value. Instead, the client should query on the Purchasing Documents collection resource with a filter on the primary key values in order to navigate to a specific instance of Purchasing Documents.
  
  For example: purchasingDocuments?q=ResponseNumber=<value1>;SequenceNumber=<value2>

Header Parameters

• Metadata-Context: string
  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".
• REST-Framework-Version: string
  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.

There's no request body for this operation.

Back to Top

Response

Default Response

No Content. This task does not return elements in the response body.

Back to Top