Results for “paybv_element_link”

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

Overview

PAYBV_ELEMENT_LINK is a Business Intelligence (BI) view in the Oracle E-Business Suite Payroll (PAY) module, owned by the APPS schema and valid across releases 12.1.1 and 12.2.2. It exposes a presentation-ready projection of element link definitions maintained in the core HR/Payroll tables. Element links determine how an element (such as a salary, deduction, or benefit) is attached to a payroll, an organisation, a job, a position, a grade, a location, or a people group, and the criteria that must be satisfied for the element to be processed.

The view's distinguishing characteristic is that it presents coded values in their decoded, user-facing form. Rather than returning raw lookup codes, PAYBV_ELEMENT_LINK calls HR_BIS.BIS_DECODE_LOOKUP to translate columns such as COSTABLE_TYPE, LINK_TO_ALL_PAYROLLS_FLAG, MULTIPLY_VALUE_FLAG, STANDARD_LINK_FLAG, TRANSFER_TO_GL_FLAG, EMPLOYMENT_CATEGORY, and QUALIFYING_UNITS into their displayed meanings. It also retains the original codes in parallel "_CODE" columns, allowing reports to display descriptions while still supporting joins or filters on the underlying values. This dual-column pattern is typical of Oracle HRMS BI views used by Oracle Business Intelligence Applications and by custom reporting on the PAY schema.

Underlying Base Objects

The ETRM metadata documents two referenced base objects: the package HR_BIS and the synonym PAY_ELEMENT_LINKS_F, which resolves to the base table PAY_ELEMENT_LINKS_F (the "_F" suffix indicates the date-tracked, effective-dated table).

The view selects exclusively from this table, aliased PEL, and applies the HR_BIS.BIS_DECODE_LOOKUP function to selected columns. Two lookup types drive the decoding: 'COSTABLE_TYPE' for COSTABLE_TYPE and a range of 'YES_NO' lookups for the flag columns, with 'EMP_CAT' and 'QUALIFYING_UNITS' handling employment category and qualifying units respectively. The view also injects a literal value, '_DF:PAY:PAY_ELEMENT_LINKS:PEL', which functions as a descriptive flexfield context marker for downstream BI tooling.

Because PAY_ELEMENT_LINKS_F is effective-dated, the view surfaces EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, preserving date-tracked history for point-in-time reporting. The view performs no joins to other transaction tables; it is a thin, single-source projection designed for direct consumption by reporting layers. No filter predicates are applied in the view text, so date-range restriction is the responsibility of the consuming query.

Key Columns

• COSTABLE_TYPE / COSTABLE_TYPE_CODE — Decoded and raw forms of the costable classification, indicating whether costs associated with the link are costed. The search term "costable_type" maps directly to this pair of columns.
• LINK_TO_ALL_PAYROLLS_FLAG / _CODE — Yes/No indicator that the link applies to all payrolls rather than a specific payroll.
• MULTIPLY_VALUE_FLAG / _CODE — Indicates whether the element value is multiplied when the link criteria are met multiple times.
• STANDARD_LINK_FLAG / _CODE — Identifies the link as a seeded, standard link.
• TRANSFER_TO_GL_FLAG / _CODE — Controls whether resulting costs are transferred to the General Ledger.
• EMPLOYMENT_CATEGORY / _CODE and QUALIFYING_UNITS / _CODE — Decoded employment category and the unit of measure for qualifying length of service.
• QUALIFYING_AGE and QUALIFYING_LENGTH_OF_SERVICE — Numeric eligibility thresholds.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-tracked validity window of the link definition.
• Foreign-key identifiers — ELEMENT_LINK_ID, PAYROLL_ID, JOB_ID, POSITION_ID, PEOPLE_GROUP_ID, ORGANIZATION_ID, ELEMENT_TYPE_ID, LOCATION_ID, GRADE_ID, ELEMENT_SET_ID, PAY_BASIS_ID, BUSINESS_GROUP_ID, plus COST_ALLOCATION_KEYFLEX_ID and BALANCING_KEYFLEX_ID for costing and balancing flexfield references.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — Descriptive flexfield segments carried through for extensibility.

Common Use Cases and Queries

The view is principally used to report on link configuration without writing lookup-decode logic. A typical query retrieves current links for a business group:

SELECT element_link_id, element_type_id, payroll_id, costable_type, transfer_to_gl_flag, employment_category FROM apps.paybv_element_link WHERE business_group_id = :p_bg_id AND SYSDATE BETWEEN effective_start_date AND effective_end_date;

Because both decoded and coded columns are available, reports can filter on codes while displaying descriptions — for example, restricting to costable links using COSTABLE_TYPE_CODE and presenting COSTABLE_TYPE. A second common pattern inventories links that transfer to GL:

SELECT element_link_id, costable_type, transfer_to_gl_flag FROM apps.paybv_element_link WHERE transfer_to_gl_flag_code = 'Y' AND SYSDATE BETWEEN effective_start_date AND effective_end_date;

A third scenario compares current and historical link definitions by selecting without a date predicate and ordering by ELEMENT_LINK_ID and EFFECTIVE_START_DATE. Note that date-effective logic must be applied by the caller; the view itself returns all versions. Users should also be aware that decoding depends on HR_BIS lookup data, so lookup values must be present for meaningful output.