Resequence a maintenance work order operation

post

/fscmRestApi/resources/11.13.18.05/maintenanceWorkOrders/action/resequenceAsNextOperation

This option gives customers the ability to change the operation sequence for resequence-enabled operations for valid maintenance work orders in appropriate statuses.

Request

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/vnd.oracle.adf.action+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.
Body ()
Root Schema : schema
Type: object
Show Source
  • If the action completes successfully, then the operation sequence becomes the next operation in line for completion.
Back to Top