Results for “qualifying_unit_name”

14 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_ELEMENT_LINKS_V is a view owned by the APPS schema within the PAY (Payroll) product module. In Oracle EBS 12.1.1 and 12.2.2 it is a VALID, dictionary-maintained object whose documented purpose is "Used to support user interface." It is not a transactional interface table; rather, it is a denormalized read-only projection that flattens the element-link configuration data held in PAY_ELEMENT_LINKS_F together with the descriptive names of the many attributes a link can reference. The view therefore serves reporting, personalization, and integration use cases in which a developer needs to display or extract an element link alongside human-readable values for payroll, job, position, organization, location, grade, employment category, qualifying units, element names, classification, and — directly relevant to the user's search term "pay_basis_name" — the pay basis attached to the link. Because it is a view and not a table, it exposes no DML surface; consumers must write to the base tables through the supported payroll APIs.

Underlying Base Objects

The documented view text shows that PAY_ELEMENT_LINKS_V is defined primarily over PAY_ELEMENT_LINKS_F (exposed through the APPS synonym LINK), which supplies the link identity, effective dating, and all foreign-key columns. That base is outer-joined or joined to a series of descriptive objects: PAY_ALL_PAYROLLS_F for the payroll name, PER_JOBS_TL for the job name, HR_ALL_POSITIONS_F_TL for the position name, HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL for organization names, HR_LOCATIONS_ALL_TL for the location code, PER_GRADES_TL for the grade name, PAY_ELEMENT_TYPES_F and PAY_ELEMENT_TYPES_F_TL for element name and description, PAY_ELEMENT_SETS for the element set name, BEN_BENEFIT_CLASSIFICATIONS and PAY_ELEMENT_CLASSIFICATIONS for classification attributes, and PER_PAY_BASES for the pay basis name. Lookups such as HR_LOOKUPS supply the meaning of the employment category and qualifying units, while packages including HR_API, HR_GENERAL, and PAY_BATCH_OBJECT_STATUS_PKG and views such as HR_LOCATIONS_NO_JOIN participate in resolving secured or derived values. The ETRM metadata for 12.2.2 lists these base objects as the documented referenced set.

Key Columns

The primary key of the link is ELEMENT_LINK_ID, paired with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE for date-tracked retrieval. Foreign-key columns include PAYROLL_ID, JOB_ID, POSITION_ID, PEOPLE_GROUP_ID, ORGANIZATION_ID, LOCATION_ID, GRADE_ID, ELEMENT_TYPE_ID, ELEMENT_SET_ID, BALANCING_KEYFLEX_ID, COST_ALLOCATION_KEYFLEX_ID, and the column central to the user's search, PAY_BASIS_ID. The view pairs each of these with a resolved name: PAYROLL_NAME, JOB_NAME, POSITION_NAME, ORGANIZATION_NAME, LOCATION_CODE, GRADE_NAME, ELEMENT_NAME, ELEMENT_SET_NAME, and PAY_BASIS_NAME (derived from PAY_BASIS.NAME). Configuration flags exposed include MULTIPLE_ENTRIES_ALLOWED_FLAG, COSTABLE_TYPE, LINK_TO_ALL_PAYROLLS_FLAG, MULTIPLY_VALUE_FLAG, STANDARD_LINK_FLAG (also surfaced as OLD_STANDARD_LINK_FLAG), and TRANSFER_TO_GL_FLAG. Qualifying criteria appear as QUALIFYING_AGE, QUALIFYING_LENGTH_OF_SERVICE, QUALIFYING_UNITS, and QUALIFYING_UNIT_NAME. Employment categories are given both the coded value EMPLOYMENT_CATEGORY and its meaning EMPLOYMENT_CATEGORY_NAME. Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE) and ATTRIBUTE1 through ATTRIBUTE20 complete the projection.

Common Use Cases and Queries

Typical uses include element-link configuration reports, data migration extracts, and UI-driven personalizations that must show a link in business terms. A common query filters by pay basis:

  • SELECT element_link_id, element_name, payroll_name, pay_basis_name, standard_link_flag FROM apps.pay_element_links_v WHERE pay_basis_name = '&basis' AND SYSDATE BETWEEN effective_start_date AND effective_end_date;
  • SELECT el.element_name, el.organization_name, el.grade_name, el.costable_type FROM apps.pay_element_links_v el WHERE el.element_type_id = :element_type_id ORDER BY el.effective_start_date;
  • SELECT DISTINCT pay_basis_id, pay_basis_name FROM apps.pay_element_links_v;

When querying, always constrain by effective dates to avoid returning historical link versions, and filter by BUSINESS_GROUP_ID where multi-organization data is present. Because the view is user-interface oriented and joins several secured objects, performance tuning should begin by confirming that the caller is not triggering row-level security unexpectedly.