GET action not supported

get

/fscmRestApi/resources/11.13.18.05/maintenanceMaterialTransactions/{InterfaceBatchId}/child/MaterialTransactionDetail/{MaterialTransactionDetailUniqID}/child/TransactionSerial/{TransactionSerialUniqID}

Request

Path Parameters
  • Value that uniquely identifies the interface batch.
  • This is the hash key of the attributes which make up the composite key for the Details resource and used to uniquely identify an instance of Details. The client should not generate the hash key value. Instead, the client should query on the Details collection resource in order to navigate to a specific instance of Details to get the hash key.
  • This is the hash key of the attributes which make up the composite key for the Transaction Serials resource and used to uniquely identify an instance of Transaction Serials. The client should not generate the hash key value. Instead, the client should query on the Transaction Serials collection resource in order to navigate to a specific instance of Transaction Serials 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
  • 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
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
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 : maintenanceMaterialTransactions-MaterialTransactionDetail-TransactionSerial-item-response
Type: object
Show Source
  • Read Only: true
    Maximum Length: 255
    Names of the error messages that occurred when processing the transaction serial. Each text string in the ErrorMessages attribute corresponds to one error message name in the ErrorMessageNames attribute. A comma ( , ) separates each message name.
  • Read Only: true
    Maximum Length: 2000
    Text of the error messages that occurred when processing this transaction serial. Each text string in the ErrorMessages attribute corresponds to one error message name in the ErrorMessageNames attribute. A double dollar sign ($$) separates each message.
  • Links
  • Title: Lot Number
    Maximum Length: 18
    Number that identifies the lot number of the serial controlled component item being issued or returned from a maintenance work order.
  • Title: Serial Number
    Maximum Length: 80
    Number that identifies the serial number of the component item being issued or returned from a maintenance work order.
  • Title: To Serial Number
    Maximum Length: 80
    Number that indicates the last serial number of the component items being issued or returned from a maintenance work order.
  • Flexfields for Transaction Serials
    Title: Flexfields for Transaction Serials
    The Flexfields for Transaction Serials resource manages descriptive flexfields that contain details about the serial component transaction.
Nested Schema : Flexfields for Transaction Serials
Type: array
Title: Flexfields for Transaction Serials
The Flexfields for Transaction Serials resource manages descriptive flexfields that contain details about the serial component transaction.
Show Source
Nested Schema : maintenanceMaterialTransactions-MaterialTransactionDetail-TransactionSerial-TransactionSerialDFF-item-response
Type: object
Show Source
  • Title: Context Value
    Maximum Length: 30
    Descriptive flexfield context name for the serial component transaction.
  • Title: Context Value
  • This is a transient attribute. The value of this attribute will always be null. Ignore this attribute.
  • Primary key of the serial component transaction that references a descriptive flexfield. It is recommended that you not include this attribute in the request payload. The response payload contains the primary key of the serial component transaction that references the descriptive flexfield.
  • Links
Back to Top