Delete one row

delete

/fscmRestApi/resources/11.13.18.05/itemsV2/{itemsV2UniqID}/child/ItemSupplierAssociation/{ItemSupplierAssociationUniqID}/child/ItemSupplierEffCategory/{ItemSupplierEffCategoryUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- ItemId, OrganizationId, SupplierId, SupplierSiteId, AcdType, ChangeLineId, VersionId, OrganizationId1 and InventoryItemId ---for the Item-Supplier Associations resource and used to uniquely identify an instance of Item-Supplier Associations. The client should not generate the hash key value. Instead, the client should query on the Item-Supplier Associations collection resource with a filter on the primary key values in order to navigate to a specific instance of Item-Supplier Associations.

    For example: ItemSupplierAssociation?q=ItemId=<value1>;OrganizationId=<value2>;SupplierId=<value3>;SupplierSiteId=<value4>;AcdType=<value5>;ChangeLineId=<value6>;VersionId=<value7>;OrganizationId1=<value8>;InventoryItemId=<value9>
  • This is the hash key of the attributes which make up the composite key for the Extensible Flexfields for Item-Supplier Associations resource and used to uniquely identify an instance of Extensible Flexfields for Item-Supplier Associations. The client should not generate the hash key value. Instead, the client should query on the Extensible Flexfields for Item-Supplier Associations collection resource in order to navigate to a specific instance of Extensible Flexfields for Item-Supplier Associations to get the hash key.
  • This is the hash key of the attributes which make up the composite key for the Items Version 2 resource and used to uniquely identify an instance of Items Version 2. The client should not generate the hash key value. Instead, the client should query on the Items Version 2 collection resource in order to navigate to a specific instance of Items Version 2 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.

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