Create flexfields

post

/fscmRestApi/resources/11.13.18.05/materialTransactions/{materialTransactionsUniqID}/child/MaterialTransactionDetail/{MaterialTransactionDetailUniqID}/child/TransactionSerial/{TransactionSerialUniqID}/child/TransactionSerialDFF

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Material Transaction Details resource and used to uniquely identify an instance of Material Transaction Details. The client should not generate the hash key value. Instead, the client should query on the Material Transaction Details collection resource in order to navigate to a specific instance of Material Transaction 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.
  • This is the hash key of the attributes which make up the composite key for the Work Order Material Transactions resource and used to uniquely identify an instance of Work Order Material Transactions. The client should not generate the hash key value. Instead, the client should query on the Work Order Material Transactions collection resource in order to navigate to a specific instance of Work Order Material 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 transactions serials.
  • Title: Context Value
    Descriptive flexfield context display value for transactions serials.
  • This is a transient attribute. The value of this attribute will always be null. Ignore this attribute.
  • Value that uniquely identifies the transaction lot that a descriptive flexfield references. This attribute should not be included in the request payload. The value of this attribute in 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 : materialTransactions-MaterialTransactionDetail-TransactionSerial-TransactionSerialDFF-item-response
Type: object
Show Source
  • Title: Context Value
    Maximum Length: 30
    Descriptive flexfield context name for transactions serials.
  • Title: Context Value
    Descriptive flexfield context display value for transactions serials.
  • This is a transient attribute. The value of this attribute will always be null. Ignore this attribute.
  • Value that uniquely identifies the transaction lot that a descriptive flexfield references. This attribute should not be included in the request payload. The value of this attribute in the response payload includes the primary key of the transaction lot.
  • Links
Back to Top