Jump to

• Request
• Response

Delete an operation resource

delete

/fscmRestApi/resources/11.13.18.05/productionSchedulingPlans/{PlanId}/child/workOrders/{workOrdersUniqID}/child/operations/{operationsUniqID}/child/operationResources/{operationResourcesUniqID}

Request

Path Parameters

• PlanId(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=
• operationResourcesUniqID(required): string
  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=
• operationsUniqID(required): string
  This is the hash key of the attributes which make up the composite key--- PlanId, WorkOrderOperationId and ResourceSequenceNumber ---for the Work Order Operations resource and used to uniquely identify an instance of Work Order Operations. The client should not generate the hash key value. Instead, the client should query on the Work Order Operations collection resource with a filter on the primary key values in order to navigate to a specific instance of Work Order Operations.
  
  For example: operations?q=PlanId=<value1>;WorkOrderOperationId=<value2>;ResourceSequenceNumber=<value3>
• workOrdersUniqID(required): string
  This is the hash key of the attributes which make up the composite key--- PlanId and WorkOrderId ---for the Work Orders resource and used to uniquely identify an instance of Work Orders. The client should not generate the hash key value. Instead, the client should query on the Work Orders collection resource with a filter on the primary key values in order to navigate to a specific instance of Work Orders.
  
  For example: workOrders?q=PlanId=<value1>;WorkOrderId=<value2>

Header Parameters

• Metadata-Context:
  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:
  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