Update a descriptive flex field

patch

/fscmRestApi/resources/11.13.18.05/planComponents/{planComponentsUniqID}/child/planComponentsDFF/{planComponentsDFFUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- PlanComponentId and OrgId ---for the Plan Component Descriptive Flex Fields resource and used to uniquely identify an instance of Plan Component Descriptive Flex Fields. The client should not generate the hash key value. Instead, the client should query on the Plan Component Descriptive Flex Fields collection resource with a filter on the primary key values in order to navigate to a specific instance of Plan Component Descriptive Flex Fields.

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

    For example: planComponents?q=PlanComponentId=<value1>;OrgId=<value2>
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 Segment
    Maximum Length: 30
    This field represents the flex context segment code for the plan component. It determines which context-sensitive segments are displayed.
  • Title: Context Segment
    This field represents the flex context segment display name for the plan component. It determines which context-sensitive segments are displayed.
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 : planComponents-planComponentsDFF-item-response
Type: object
Show Source
  • Title: Context Segment
    Maximum Length: 30
    This field represents the flex context segment code for the plan component. It determines which context-sensitive segments are displayed.
  • Title: Context Segment
    This field represents the flex context segment display name for the plan component. It determines which context-sensitive segments are displayed.
  • Links
  • Title: Business Unit
    The unique identifier of the business unit organisation.
  • The unique identifier for the plan component record within a business unit.
Back to Top

Examples

The following example shows how to update a descriptive flex field by submitting a PATCH request on the REST resource using cURL.

cURL Command

curl -u <username:password> \ -X PATCH -d @example_request_payload.json https://servername.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/planComponents/00020000000EACED00057708000110F07F4ABECA0000000EACED0005770800000000000000CC/child/planComponentsDFF/00020000000EACED00057708000110F07F4ABECA0000000EACED0005770800000000000000CC

Example of Request Body

The following example shows the contents of the request body in JSON format.

{ 
"Plan__Component__DFF" : "Only valid for key sales reps"
}

Example of Response Body

The following example shows the contents of the response body in JSON format.

{
  "PlanComponentId": 300100090511050,
  "OrgId": 204,
  "_Plan__Component__DFF": "Only valid for key sales reps",
  "usage": "Incentive",
  "status": null,
  "newDfff": null,
  "newDfffNumber": null,
  "newDfffDate": null,
  "newDfffWithNewFile": null,
  "newDff25april": null,
  "dffPc170520122852885": null,
  "dffPc170529142616148": null,
  "dffPc170606120644026": null,
  "__FLEX_Context": null,
  "__FLEX_Context_DisplayValue": null,
  "links": [
    ...
  ]
}
Back to Top