Results for “iv_er”

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

Overview

APPS.PAY_ELEMENT_TYPES_V2 is a reporting view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 application schema. It presents a specialized projection of payroll element definitions that are restricted to elements of processing type 'R' (regular) and that are linked to benefit classification records carrying a CONTRIBUTIONS_USED = 'Y' flag. The view joins element type definitions to their translated name/description rows, element classifications, benefit carrier information, and — critically — the PAY_INPUT_VALUES_F row whose name is 'ER CONTR' (employer contribution). Because of this last constraint, the view effectively exposes payroll elements that carry an employer-contribution input value, which is the identifying characteristic used by benefits and pension integrations.

Its principal role is to serve as the data source for benefits-related payroll and contribution processing reports and interfaces. Rather than exposing all element types, it narrows the result set to those elements whose benefit classification is marked as contribution-bearing, providing downstream consumers with a clean list of employer-contribution-capable elements.

Underlying Base Objects

The view is defined over the following documented objects, all resolved through APPS synonyms unless noted:

• PAY_ELEMENT_TYPES_F and PAY_ELEMENT_TYPES_F_TL — the core element type definition (ET) and its translated name/description rows (ETTL), joined on element_type_id and the session language.
• PAY_ELEMENT_CLASSIFICATIONS and PAY_ELEMENT_CLASSIFICATIONS_TL — element classification (EC/ECTL), supplying the classification name.
• BEN_BENEFIT_CLASSIFICATIONS — benefit classification (BC), the source of the benefit classification name, dependents-allowed flag, COBRA flag, and the contributions-used constraint.
• PAY_INPUT_VALUES_F — input values (IV_ER), filtered to the 'ER CONTR' input value, supplying the ER_UOM and ER_CONTR_INPUT_VALUE_ID columns.
• HR_BENEFITS_CARRIERS_V — a view supplying the carrier name (BCV), outer-joined on element_information5.
• FND_SESSIONS — used to obtain the current session effective date for date-effective (datetrack) filtering.

The ETRM metadata also lists HR_GENERAL and HR_SECURITY packages as referenced objects, reflecting the security and utility logic applied through the base synonyms.

Key Columns

• ELEMENT_TYPE_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — primary identifier and datetrack boundaries.
• BUSINESS_GROUP_ID, LEGISLATION_CODE — ownership and legislative context.
• ELEMENT_NAME, ELEMENT_DESCRIPTION — translated element text.
• CURRENCY_CODE — from the element's input currency.
• PAYROLL_CLASSIFICATION_NAME, BENEFIT_CLASSIFICATION_NAME — classification context.
• CARRIER — benefit carrier name.
• PERIOD_TYPE — derived from element_information4.
• DEPENDENT_ALLOWED_FLAG, COBRA_FLAG — defaulted to 'N' via NVL.
• ER_UOM, ER_CONTR_INPUT_VALUE_ID — employer-contribution unit of measure and input value identifier.

Common Use Cases and Queries

Typical usage includes validating employer-contribution elements for a business group, reconciling benefit classification setup, and feeding integration extracts.

Example query:

• SELECT element_name, benefit_classification_name, carrier, er_uom, currency_code
• FROM apps.pay_element_types_v2
• WHERE business_group_id = :p_bg_id
• AND legislation_code = :p_leg
• AND SYSDATE BETWEEN effective_start_date AND effective_end_date;

Because the view filters on session effective date and language via USERENV, callers should initialize FND_SESSIONS context appropriately; otherwise results may return unexpectedly empty.