Create details

post

/fscmRestApi/resources/11.13.18.05/operationTransactions/{operationTransactionsUniqID}/child/OperationTransactionDetail/{OperationTransactionDetailUniqID}/child/TransactionLot/{TransactionLotUniqID}/child/TransactionLotDFF

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Operation Transaction Details resource and used to uniquely identify an instance of Operation Transaction Details. The client should not generate the hash key value. Instead, the client should query on the Operation Transaction Details collection resource in order to navigate to a specific instance of Operation Transaction Details to get the hash key.
  • This is the hash key of the attributes which make up the composite key for the Transaction Lots resource and used to uniquely identify an instance of Transaction Lots. The client should not generate the hash key value. Instead, the client should query on the Transaction Lots collection resource in order to navigate to a specific instance of Transaction Lots to get the hash key.
  • This is the hash key of the attributes which make up the composite key for the Work Order Operation Transactions resource and used to uniquely identify an instance of Work Order Operation Transactions. The client should not generate the hash key value. Instead, the client should query on the Work Order Operation Transactions collection resource in order to navigate to a specific instance of Work Order Operation Transactions 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
  • Title: Context Value
    Maximum Length: 30
    Descriptive flexfield context name for transaction lots.
  • Title: Context Value
    Descriptive flexfield context display value for transaction lots.
  • Value that uniquely identifies the transaction lot that uses the descriptive flexfields. Make sure your request payload does not include a value for this attribute. The response payload includes the primary key of the transaction lot.
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 : operationTransactions-OperationTransactionDetail-TransactionLot-TransactionLotDFF-item-response
Type: object
Show Source
  • Title: Context Value
    Maximum Length: 30
    Descriptive flexfield context name for transaction lots.
  • Title: Context Value
    Descriptive flexfield context display value for transaction lots.
  • Value that uniquely identifies the transaction lot that uses the descriptive flexfields. Make sure your request payload does not include a value for this attribute. The response payload includes the primary key of the transaction lot.
  • Links
Back to Top