Search Results input_value_uom

Overview

APPS.PAYBV_ELEMENT_LINK_DETAIL_V is a Business Intelligence (BI) system view in the Oracle E-Business Suite Payroll (PAY) module. It is owned by the APPS schema, carries the FND Design Data reference PAY.PAYBV_ELEMENT_LINK_DETAIL_V, and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. The view exposes descriptive detail about payroll element links — the rules that determine which assignments, payrolls, and people groups an element is associated with, and the input values that flow into those links.

The "BV" naming convention identifies the object as part of the Oracle BI/Discoverer business views layer, a set of denormalized, presentation-oriented views designed to simplify reporting on Payroll setup and transactional data. Rather than requiring report authors to join the many underlying _F and _TL tables, the view surfaces element link attributes such as processing type, standard link flag, age and service criteria, costing and balancing configuration, and link-level input value defaults in a single queryable object. This makes it valuable for HRMS audits, element setup reviews, and downstream integration extracts.

Underlying Base Objects

The view is defined over a documented set of base objects spanning element types, links, input values, payrolls, classifications, and security. These include:

• PAY_ELEMENT_LINKS_F — the core table holding element link records.
• PAY_ELEMENT_TYPES_F and PAY_ELEMENT_TYPES_F_TL — element type definitions and translations.
• PAY_ELEMENT_CLASSIFICATIONS and PAY_ELEMENT_CLASSIFICATIONS_TL — classification names and translations used in the CLASSIFICATION_NAME column.
• PAY_INPUT_VALUES_F and PAY_INPUT_VALUES_F_TL — input value definitions and translations.
• PAY_LINK_INPUT_VALUES_F — the link-input-value association used for INPUT_VALUE_DEFAULT.
• PAY_ELEMENT_SETS, PAY_COST_ALLOCATION_KEYFLEX, and PAY_PAYROLLS_F — supporting element set, costing key flexfield, and payroll definitions.
• HR_BIS, HR_GENERAL, and HR_SECURITY packages — used for security-aware lookups and BI helper logic (reflected via BG_SECURITY_FLAG_CODE).

These base objects are joined to derive human-readable names and decoded meaning alongside the underlying numeric IDs.

Key Columns

The view exposes both decoded (name/meaning) and technical key columns. Notable columns include:

• CLASSIFICATION_NAME, ELEMENT_NAME — element classification and element name.
• PROCESSING_TYPE / PROCESSING_TYPE_M — raw and decoded processing type (e.g., recurring/one-time).
• STANDARD_LINK / STANDARD_LINK_M — raw and decoded standard link indicator.
• AGE_CRITERIA, SERVICE_CRITERIA — numeric age and length-of-service qualification criteria for the link.
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — datetracked validity of the link definition.
• LINK_START_DATE, LINK_END_DATE — the actual link availability window.
• COST_ALLOCATION_KEYFLEX_ID, BALANCING_KEYFLEX_ID, COSTING, BALANCING — costing and balancing configuration.
• PAYROLL_NAME, PEOPLE_GROUP_NAME — payroll and people group the link targets.
• ORGANIZATION_NAME, JOB_NAME, POSITION_NAME, GRADE_NAME, PAY_BASIS_NAME, LOCATION_NAME — eligibility criteria dimensions.
• INPUT_VALUE_NAME, INPUT_VALUE_DEFAULT, INPUT_VALUE_UOM — link-level input value defaults.
• ELEMENT_LINK_ID, ELEMENT_TYPE_ID, PAYROLL_ID, PEOPLE_GROUP_ID, BUSINESS_GROUP_ID — primary and foreign keys.
• BG_SECURITY_FLAG_CODE — business group security indicator used for row-level access control.
• QUALIFYING_UNITS / QUALIFYING_UNITS_M — qualifying unit raw and decoded values.

Common Use Cases and Queries

Typical uses include auditing element link eligibility, confirming service/age criteria, and extracting input value defaults for an element. A representative query filtering on service criteria is:

SELECT element_name,
       classification_name,
       service_criteria,
       age_criteria,
       payroll_name,
       effective_start_date,
       effective_end_date
FROM   apps.paybv_element_link_detail_v
WHERE  NVL(bg_security_flag_code,'Y') = 'Y'
AND    service_criteria IS NOT NULL
ORDER BY element_name;

Report authors commonly join the view to PER_ALL_ASSIGNMENTS_F or use it standalone for setup documentation, taking advantage of the decoded _M columns to avoid additional lookups. The presence of EFFECTIVE_START_DATE and EFFECTIVE_END_DATE supports date-tracked reporting, and BG_SECURITY_FLAG_CODE aligns with Oracle HRMS business group security.