Get an element definition.

get

/hcmRestApi/resources/11.13.18.05/payrollElementDefinitionsLOV/{payrollElementDefinitionsLOVUniqID}

Request

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

    For example: payrollElementDefinitionsLOV?q=ElementTypeId=<value1>;EffectiveStartDate=<value2>;EffectiveEndDate=<value3>
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
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.

There's no request body for this operation.

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 : payrollElementDefinitionsLOV-item-response
Type: object
Show Source
  • Read Only: true
    Maximum Length: 30
    Name of the category used, by identifying the predefined questionnaire to create an element, such as Absence, Benefits, Involuntary Deduction, Retirement and Pension, Social Insurance Deduction, Standard, and Time card.
  • Title: Effective End Date
    Read Only: true
    Date at the end of the period during which the element is available for processing.
  • Title: Effective Start Date
    Read Only: true
    Date at the beginning of the period during which the element is available for processing.
  • Read Only: true
    Maximum Length: 80
    Name of the element.
  • Read Only: true
    System-generated unique identifier for the element.
  • Title: Input Currency
    Read Only: true
    Maximum Length: 15
    Currency code for those element entry input values that use money as the unit of measure.
  • Read Only: true
    Maximum Length: 30
    Code that indicates the legislation that the element definition belongs to. Applicable only for seeded records.
  • Read Only: true
    Unique identifier for the legislative data group.
  • Title: Name
    Read Only: true
    Maximum Length: 240
    Name of the legislative data group.
  • Links
  • Title: Priority
    Read Only: true
    Maximum Length: 15
    Currency code for those element entry result values that use money as the unit of measure.
  • System-generated unique identifier for the person.
  • Read Only: true
    Unique identifier for the element classification that groups elements with similar characteristics. It controls the order in which the elements are processed and the balances that are fed by them.
  • Title: Element Classification Name
    Read Only: true
    Maximum Length: 80
    Name of the element classification that groups elements with similar characteristics, such as earnings or involuntary deduction. It controls the order in which the elements are processed and the balances that are fed by them.
  • Title: Element Processing Type
    Read Only: true
    Maximum Length: 30
    Indicates whether an element entry is recurring or nonrecurring.
  • Title: Reporting Name
    Read Only: true
    Maximum Length: 80
    Name of the element that's displayed on reports and pay advices.
  • Read Only: true
    Unique identifier for the subordinate group of elements within a primary element classification.
  • Title: Element Classification Name
    Read Only: true
    Maximum Length: 80
    Name of the subordinate group of elements within a primary element classification.
  • Read Only: true
    Maximum Length: 30
    Indicates whether the element can be associated with only employee payroll assignment.
  • Read Only: true
    Maximum Length: 30
    Indicates whether the element can be associated with only employee payroll relationships.
Back to Top

Examples

The following example shows how to retrieve a payroll element definition using the element name by submitting a GET request on the REST resource using cURL.

curl -i -u "<username>:<password>" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -H "REST-Framework-Version: 4" -X GET "https://<host>:<port>/hcmRestApi/resources/11.13.18.05/payrollElementDefinitionsLOV?q=ElementName='A01_CHILD_SUPPORT'"

Example of Response Header

The following is an example of the response header.

Status: HTTP/1.1 200 OK
Content-Type: application/vnd.oracle.adf.resourceitem+json

Example of Response Body

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

{
  "items" : [ {
    "ElementTypeId" : 300100128817404,
    "EffectiveStartDate" : "2016-01-01",
    "EffectiveEndDate" : "4712-12-31",
    "ElementName" : "A01_CHILD_SUPPORT",
    "ReportingName" : "A01_CHILD_SUPPORT",
    "UseAtRelationshipLevel" : "Y",
    "UseAtAssignmentLevel" : "N",
    "ProcessingType" : "R",
    "LegislativeDataGroupId" : 300100001794247,
    "LegislationCode" : null,
    "InputCurrencyCode" : "USD",
    "OutputCurrencyCode" : "USD",
    "PrimaryClassificationName" : "Involuntary Deductions",
    "LegislativeDataGroupName" : "ZHRX_USVS_ST LDG One",
    "PrimaryClassificationId" : 100010032607677,
    "SecondaryClassificationId" : 100010026299330,
    "SecondaryClassificationName" : "Support Child",
    "PersonId" : null,
    "links" : [ 
		   {
		     ....}
	]
}
Back to Top