GET action not supported

get

/fscmRestApi/resources/11.13.18.05/maintenanceOperationTransactions/{maintenanceOperationTransactionsUniqID}/child/OperationTransactionDetail

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Maintenance Work Order Operation Transactions resource and used to uniquely identify an instance of Maintenance Work Order Operation Transactions. The client should not generate the hash key value. Instead, the client should query on the Maintenance Work Order Operation Transactions collection resource in order to navigate to a specific instance of Maintenance Work Order Operation Transactions to get the hash key.
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • Used as a predefined finder to search the collection.

    Format: ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables:

    • PrimaryKey
      Finder Variables:
    • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
    • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

      Example:
      self,canonical
    • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
    • The resource item payload will be filtered in order to contain only data (no links section, for example).
    • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
    • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

      Format: ?q=expression1;expression2

      You can use these queryable attributes to filter this collection resource using the q query parameter:
      • ErrorMessageNames; string; Names of the error messages that occurred when processing the operation transaction. Each error message name corresponds to one text string that the ErrorMessages attribute contains. A comma ( , ) separates each message name.
      • ErrorMessages; string; Text of the error messages that occurred when processing the operation transaction. Each text string for each error message corresponds to one error message name that the ErrorMessageNames attribute contains. A double dollar sign ($$) separated each message.
      • FromDispatchState; string; Value that reflects the state of the operation in the maintenance work order before operation transaction. Valid values for maintenance operation from operation transaction perspective are READY and COMPLETE. A list of accepted values is defined in the lookup type ORA_WIE_DISPATCH_STATE.
      • OrganizationCode; string; Abbreviation that identifies the organization where the operation transaction is performed. This organization will be same as the maintenance work order organization.
      • SourceSystemCode; string; Abbreviation that identifies the source application that started this operation transaction. This code must be registered in Oracle Manufacturing Cloud. The application validates this value against the WIE_SOURCE_SYSTEMS_V database view.
      • ToDispatchState; string; Value that reflects the to be state of the operation in the maintenance work order post operation transaction. Valid values for maintenance operation are READY and COMPLETE. A list of accepted values is defined in the lookup type ORA_WIE_DISPATCH_STATE.
      • TransactionDate; string; Date an time when the operation transaction is performed. The valid date range is from the work order released date till the system date. Future date is not valid and the default value is system date.
      • TransactionNote; string; Text which reflects the details captured during the operation transaction. This is optional to perform the operation transaction.
      • WoOperationSequenceNumber; number; Number that uniquely identifies the operation within the maintenance work orders. An operation transaction is performed against the same in the maintenance work order.
      • WoOperationTransactionId; integer; The value that uniquely identifies the operation transaction performed against the maintenance work order. If the transaction is succesfull the value will be a number, otherwise the value will be 0. This attribute is included in the response payload.
      • WorkOrderNumber; string; Number uniquely identifies the maintenance work order. The operation transaction is performed against the operation within the maintenance work order.
    • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
    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

    Supported Media Types

    Default Response

    The following table describes the default response for this task.
    Headers
    • 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.
    Body ()
    Root Schema : maintenanceOperationTransactions-OperationTransactionDetail
    Type: object
    Show Source
    Nested Schema : Items
    Type: array
    Title: Items
    The items in the collection.
    Show Source
    Nested Schema : maintenanceOperationTransactions-OperationTransactionDetail-item-response
    Type: object
    Show Source
    • Read Only: true
      Maximum Length: 255
      Names of the error messages that occurred when processing the operation transaction. Each error message name corresponds to one text string that the ErrorMessages attribute contains. A comma ( , ) separates each message name.
    • Read Only: true
      Maximum Length: 2000
      Text of the error messages that occurred when processing the operation transaction. Each text string for each error message corresponds to one error message name that the ErrorMessageNames attribute contains. A double dollar sign ($$) separated each message.
    • Title: From Dispatch State
      Maximum Length: 30
      Value that reflects the state of the operation in the maintenance work order before operation transaction. Valid values for maintenance operation from operation transaction perspective are READY and COMPLETE. A list of accepted values is defined in the lookup type ORA_WIE_DISPATCH_STATE.
    • Links
    • Flexfields for Operation Transactions
      Title: Flexfields for Operation Transactions
      The Flexfields for Operation Transactions resource manages details about the descriptive flexfields that the maintenance operation transaction uses.
    • Title: Organization Code
      Maximum Length: 30
      Abbreviation that identifies the organization where the operation transaction is performed. This organization will be same as the maintenance work order organization.
    • Title: Source System Code
      Maximum Length: 30
      Abbreviation that identifies the source application that started this operation transaction. This code must be registered in Oracle Manufacturing Cloud. The application validates this value against the WIE_SOURCE_SYSTEMS_V database view.
    • Title: To Dispatch State
      Maximum Length: 30
      Value that reflects the to be state of the operation in the maintenance work order post operation transaction. Valid values for maintenance operation are READY and COMPLETE. A list of accepted values is defined in the lookup type ORA_WIE_DISPATCH_STATE.
    • Title: Transaction Date
      Date an time when the operation transaction is performed. The valid date range is from the work order released date till the system date. Future date is not valid and the default value is system date.
    • Title: Transaction Note
      Maximum Length: 4000
      Text which reflects the details captured during the operation transaction. This is optional to perform the operation transaction.
    • Title: Operation Sequence
      Number that uniquely identifies the operation within the maintenance work orders. An operation transaction is performed against the same in the maintenance work order.
    • The value that uniquely identifies the operation transaction performed against the maintenance work order. If the transaction is succesfull the value will be a number, otherwise the value will be 0. This attribute is included in the response payload.
    • Title: Work Order
      Maximum Length: 120
      Number uniquely identifies the maintenance work order. The operation transaction is performed against the operation within the maintenance work order.
    Nested Schema : Flexfields for Operation Transactions
    Type: array
    Title: Flexfields for Operation Transactions
    The Flexfields for Operation Transactions resource manages details about the descriptive flexfields that the maintenance operation transaction uses.
    Show Source
    Nested Schema : maintenanceOperationTransactions-OperationTransactionDetail-OperationTransactionDFF-item-response
    Type: object
    Show Source
    Back to Top