Create flexfields

post

/fscmRestApi/resources/11.13.18.05/operationTransactions/{operationTransactionsUniqID}/child/OperationTransactionDetail/{OperationTransactionDetailUniqID}/child/OperationTransactionDFF

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 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
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-OperationTransactionDFF-item-response
Type: object
Show Source
Back to Top

Examples

This example describes how to create one descriptive flexfield in one operation transaction detail in one operation transaction.

Example cURL Command

Use the following cURL command to submit a request on the REST resource:

curl -u username:password -X POST -H "Content-Type:application/vnd.oracle.adf.action+json" -d 'request payload' "https://servername/fscmRestApi/resources/version/operationTransactions"

Note that you use the action for the parent resource in the cURL command. You specify child details in the request payload. For example, you use a POST on the parent operationTransactions, and specify details for child OperationTransactionDFF in the request payload.

Example Request Body

The following example includes the contents of the request body in JSON format. You replace the request payload in the cURL command with the contents of the Example Request Body. The request payload specifies attribute values that the command will use in the record that it creates.

{

"SourceSystemCode" : "SAP",
"OperationTransactionDetail" : [ {
        "SourceSystemCode" : "SAP",
        "OrganizationCode" : "M1",
        "WorkOrderNumber" : "M1-1136",
        "WoOperationSequenceNumber" : 10,
        "FromDispatchState" : "READY",
        "ToDispatchState" : "COMPLETE",
        "TransactionQuantity" : 1,
        "TransactionUnitOfMeasure" : "Each",
        "ComplSubinventoryCode" : null,
        "CompletionLocator" : null,
        "ReasonCode" : null,
        "TransactionNote" : null,
        "PONumber" : null,
        "POLineNumber" : null,
        "SoldToLegalEntityName" : null,
        "OperationTransactionDFF": [{
        "off" : 1
        }]
   }]
}

Example Response Body

The following example includes the contents of the response body in JSON format:

{
"SourceSystemType": "EXTERNAL",
"SourceSystemCode": "SAP",
"ErrorsExistFlag": "false",
"OperationTransactionDetail": [
  
{
"WoOperationTransactionId": 51649,
"SourceSystemCode": "SAP",
"OrganizationCode": "M1",
"WorkOrderNumber": "M1-1136",
"WoOperationSequenceNumber": 10,
"TransactionDate": "2017-10-15T05:44:18.053+00:00",
"FromDispatchState": "READY",
"ToDispatchState": "COMPLETE",
"TransactionQuantity": 1,
"TransactionUOMCode": null,
"TransactionUnitOfMeasure": "Each",
"ComplSubinventoryCode": null,
"ReasonCode": null,
"TransactionNote": null,
"PONumber": null,
"POLineNumber": null,
"SoldToLegalEntityName": null,
"CompletionLocator": null,
"ErrorMessages": "",
"ErrorMessageNames": "",
"InspectionEventId": null,
"OperationTransactionDFF": [
  
{
"InterfaceRowId": 300100124132542,
"off": 1,
"__FLEX_Context": null,
"__FLEX_Context_DisplayValue": null,
...
}
Back to Top