Create flexfields
/fscmRestApi/resources/11.13.18.05/operationTransactions/{operationTransactionsUniqID}/child/OperationTransactionDetail/{OperationTransactionDetailUniqID}/child/OperationTransactionDFF
Request
-
OperationTransactionDetailUniqID(required): string
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.
-
operationTransactionsUniqID(required): string
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.
-
Metadata-Context:
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".
-
REST-Framework-Version:
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.
- application/json
object
-
__FLEX_Context: string
Title:
Context Segment
Maximum Length:80
Descriptive flexfield context name for operation transactions. -
__FLEX_Context_DisplayValue: string
Title:
Context Segment
-
Discriminator: string
-
InterfaceRowId: integer
(int64)
Value that uniquely identifies the operation transaction detail 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 operation transaction detail.
Response
- application/json
Default Response
-
Metadata-Context(required):
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".
-
REST-Framework-Version(required):
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.
object
-
__FLEX_Context: string
Title:
Context Segment
Maximum Length:80
Descriptive flexfield context name for operation transactions. -
__FLEX_Context_DisplayValue: string
Title:
Context Segment
-
Discriminator: string
-
InterfaceRowId: integer
(int64)
Value that uniquely identifies the operation transaction detail 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 operation transaction detail.
-
links: array
Links
Title:
Links
The link relations associated with the resource instance.
array
Links
object
-
href: string
Title:
hyperlink reference
The URI to the related resource. -
kind: string
Title:
kind
Allowed Values:[ "collection", "item", "describe", "other" ]
The kind of the related resource. -
name: string
Title:
name
The name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relation
Allowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]
The name of the relation to the resource instance. Example: self.
object
-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
- LVVO_V___FLEX_Context
-
Parameters:
- finder:
ValidValuesFinder%3BBind_ApplicationId%3D10493%2CBind_DescriptiveFlexfieldCode%3DWIE_OPERATION_TRANSACTIONS
The following properties are defined on the LOV link relation:- Source Attribute: __FLEX_Context_DisplayValue; Target Attribute: Name
- Display Attribute: Name, Description
- finder:
- LVVO___FLEX_Context
-
Parameters:
- finder:
ValidValuesFinder%3BBind_ApplicationId%3D10493%2CBind_DescriptiveFlexfieldCode%3DWIE_OPERATION_TRANSACTIONS
Abbreviations that identify each descriptive flexfield that is defined for the operation transaction.
The following properties are defined on the LOV link relation:- Source Attribute: __FLEX_Context; Target Attribute: ContextCode
- Display Attribute: Name
- finder:
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, ... }