Resequences the next operation
post
/fscmRestApi/resources/11.13.18.05/processWorkOrders/action/resequenceAsNextOperation
Resequences the next operation for execution. To resequence the operation, the client sends the work order operation ID or a combination of work order number, operation sequence number, or organization code attributes to uniquely identify the operation. The application then resequences the execution sequence of the operations and reschedules the work order based on the changed execution sequence.
Request
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.
Supported Media Types
- application/vnd.oracle.adf.action+json
Root Schema : schema
Type:
Show Source
object
-
OperationSequenceNumber: number
Sequence of operations as defined in the work order operation.
-
OrganizationCode: string
Abbreviation that identifies the inventory organization that's enabled for manufacturing.
-
WorkOrderNumber: string
Number that identifies the work order. This number is unique in the manufacturing organization. The user can manually assign the number when the user creates the work order, or the user can allow the application to create a unique number from the numbering scheme defined by these plant parameters: Work Order Prefix or Work Order Starting Number.
-
WorkOrderOperationId: number
Value that uniquely identifies the work order operation.
Response
Supported Media Types
- application/json
- application/vnd.oracle.adf.actionresult+json
Default Response
The following table describes the default response for this task.
Root Schema : schema
Type:
Show Source
object
-
result(required): string
If the action completes successfully, then it returns a success message.
Examples
This example describes an action on how to resequence the next operation for execution.
Example cURL Command
Use the following cURL command to submit a request on the REST resource.
curl -u username:password -X POST -H "Content-Type:application/vnd.oracle.adf.action+json" -d 'request payload' "https://servername/fscmRestApi/resources/version/processWorkOrders"
Example Request Body
The following example includes the contents of the request body in JSON format. You replace the
request payload in the CURL command with the contents of the Example Request Body. The request payload specifies attribute values that the command uses in the record that it creates.
{ "name": "resequenceAsNextOperation", "parameters": [ {"WorkOrderNumber": "MFGP-1003"}, {"OperationSequenceNumber": 25}, {"OrganizationCode": "MFGP"} ] } OR { "name": "resequenceAsNextOperation", "parameters": [ {"WorkOrderOperationId": 300100548601279} ] }
Example Response Body
The following example includes the contents of the response body in JSON format:
{ "result" : "Operation sequence 25 was resequenced as the next operation for execution." }