1. REST API for Oracle Fusion Cloud HCM
  2. Tasks
  3. Calculation Entries
  4. Calculation Card Component
  5. Calculation Card Component Associations

Update a calculation card association

patch

/hcmRestApi/resources/11.13.18.05/calculationEntries/{DirCardId}/child/CIRComponent/{CIRComponentUniqID}/child/CIRComponentAssociation/{CIRComponentAssociationUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- DirRepCardId, EffectiveStartDate and EffectiveEndDate ---for the Calculation Card Component Associations resource and used to uniquely identify an instance of Calculation Card Component Associations. The client should not generate the hash key value. Instead, the client should query on the Calculation Card Component Associations collection resource with a filter on the primary key values in order to navigate to a specific instance of Calculation Card Component Associations.

    For example: CIRComponentAssociation?q=DirRepCardId=<value1>;EffectiveStartDate=<value2>;EffectiveEndDate=<value3>
  • This is the hash key of the attributes which make up the composite key--- EffectiveStartDate, EffectiveEndDate and DirCardCompId ---for the Calculation Card Component resource and used to uniquely identify an instance of Calculation Card Component. The client should not generate the hash key value. Instead, the client should query on the Calculation Card Component collection resource with a filter on the primary key values in order to navigate to a specific instance of Calculation Card Component.

    For example: CIRComponent?q=EffectiveStartDate=<value1>;EffectiveEndDate=<value2>;DirCardCompId=<value3>
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
Header Parameters
  • This header accepts a string value. The string is a semi-colon separated list of =. It is used to perform effective date range operations. The accepted parameters are RangeMode, RangeSpan, RangeStartDate, RangeEndDate, RangeStartSequence and RangeEndSequence. The parameter values are always strings. The possible values for RangeMode are SET_LOGICAL_START, SET_LOGICAL_END, END_DATE, SET_EFFECTIVE_START, SET_EFFECTIVE_END, REPLACE_CORRECTION, REPLACE_UPDATE, RECONCILE_CORRECTION, CORRECTION, RECONCILE_UPDATE, UPDATE, ZAP and DELETE_CHANGES. The possible values for RangeSpan are PHYSICAL_ROW_END_DATE and LOGICAL_ROW_END_DATE. The values for RangeStartDate and RangeEndDate have to be a string representation of a date in yyyy-MM-dd format. The value for RangeStartSequence and RangeEndSequence must be strings such that when parsed they yield positive integers.
  • 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
Nested Schema : Calculation Card Component Association Details
Type: array
Title: Calculation Card Component Association Details
The CIRComponentAssociationDetails resource returns details of the calculation card association.
Show Source
Nested 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 : calculationEntries-CIRComponent-CIRComponentAssociation-item-response
Type: object
Show Source
Nested Schema : Calculation Card Component Association Details
Type: array
Title: Calculation Card Component Association Details
The CIRComponentAssociationDetails resource returns details of the calculation card association.
Show Source
Nested Schema : calculationEntries-CIRComponent-CIRComponentAssociation-CIRComponentAssociationDetails-item-response
Type: object
Show Source
Links
CIRComponentAssociationDetails
Parameters:
  • CIRComponentAssociationUniqID: $request.path.CIRComponentAssociationUniqID
  • CIRComponentUniqID: $request.path.CIRComponentUniqID
  • DirCardId: $request.path.DirCardId
The CIRComponentAssociationDetails resource returns details of the calculation card association.
Back to Top