Update one serial attribute flexfield

patch

/fscmRestApi/resources/11.13.18.05/inventoryStagedTransactions/{TransactionInterfaceId}/child/lots/{lotsUniqID}/child/lotSerials/{lotSerialsUniqID}/child/serialAttributeDFFs/{serialAttributeDFFsUniqID}

Request

Path Parameters
  • Value that uniquely identifies the transaction.
  • This is the hash key of the attributes which make up the composite key--- TransactionInterfaceId and FmSerialNumber ---for the Lot Serials resource and used to uniquely identify an instance of Lot Serials. The client should not generate the hash key value. Instead, the client should query on the Lot Serials collection resource with a filter on the primary key values in order to navigate to a specific instance of Lot Serials.

    For example: lotSerials?q=TransactionInterfaceId=<value1>;FmSerialNumber=<value2>
  • This is the hash key of the attributes which make up the composite key--- TransactionInterfaceId and LotNumber ---for the Lots resource and used to uniquely identify an instance of Lots. The client should not generate the hash key value. Instead, the client should query on the Lots collection resource with a filter on the primary key values in order to navigate to a specific instance of Lots.

    For example: lots?q=TransactionInterfaceId=<value1>;LotNumber=<value2>
  • This is the hash key of the attributes which make up the composite key for the Flexfields for Serial Attributes resource and used to uniquely identify an instance of Flexfields for Serial Attributes. The client should not generate the hash key value. Instead, the client should query on the Flexfields for Serial Attributes collection resource in order to navigate to a specific instance of Flexfields for Serial Attributes to get the hash key.
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/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.
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 : inventoryStagedTransactions-lots-lotSerials-serialAttributeDFFs-item-response
Type: object
Show Source
Back to Top