Results for “cobra_flag”

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

Overview

PAY_ELEMENT_TYPES_V2 is a denormalized view owned by the APPS schema in Oracle E-Business Suite, residing in the PAY (Payroll) product. It is defined over PAY_ELEMENT_TYPES_F and its related translated, classification, benefit, and input-value tables, and is documented as being used by US legislation-specific forms modules. Unlike PAY_ELEMENT_TYPES_F, which stores element type definitions in a normalized, effective-dated form, this view flattens the element records together with payroll classification, benefit classification, carrier, and input-value attributes so that consuming forms and reports can retrieve a single-row representation of a payroll element without performing the underlying joins themselves.

Because the view filters on PROCESSING_TYPE = 'R' and joins against FND_SESSIONS using the session effective date, it returns only those element types effective for the current session date. This makes it well suited to forms and concurrent programs that must resolve the "as-of-today" definition of an element rather than its full historical set of date-tracked rows.

Underlying Base Objects

The view is built from the following documented base objects: PAY_ELEMENT_TYPES_F and PAY_ELEMENT_TYPES_F_TL (the element type definition and its translation table, aliased ETTL); PAY_ELEMENT_CLASSIFICATIONS and PAY_ELEMENT_CLASSIFICATIONS_TL (classification and translation, aliased ECTL); BEN_BENEFIT_CLASSIFICATIONS (aliased BC); HR_BENEFITS_CARRIERS_V (aliased BCV, an outer-joined view); PAY_INPUT_VALUES_F (aliased IV_ER); and FND_SESSIONS (aliased S). The 12.2.2 ETRM metadata additionally lists HR_GENERAL and HR_SECURITY packages as referenced objects, reflecting the security and date-tracking logic applied through the underlying definitions.

Key join predicates include ELEMENT_TYPE_ID between ET and ETTL, CLASSIFICATION_ID between EC and ECTL, and BENEFIT_CLASSIFICATION_ID between BC and ET. Both the element type and input value joins are date-bounded against S.EFFECTIVE_DATE BETWEEN the row's effective start and end dates, and both the element and classification names are restricted to the user's session language via USERENV('LANG').

Key Columns

• ELEMENT_TYPE_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, BUSINESS_GROUP_ID, LEGISLATION_CODE — Core element identifiers and effective-dating attributes carried from PAY_ELEMENT_TYPES_F.
• ELEMENT_NAME, ELEMENT_DESCRIPTION — Translated element name and description from PAY_ELEMENT_TYPES_F_TL.
• BENEFIT_CLASSIFICATION_NAME — The benefit classification name from BEN_BENEFIT_CLASSIFICATIONS; the object referenced by the "benefit_classification_name" search term. This drives US benefit-related element behavior and is only populated where a valid benefit classification with CONTRIBUTIONS_USED = 'Y' exists.
• PAYROLL_CLASSIFICATION_NAME — Classification name from PAY_ELEMENT_CLASSIFICATIONS_TL.
• CARRIER — Carrier name from HR_BENEFITS_CARRIERS_V, outer-joined on ORGANIZATION_ID(+) = ET.ELEMENT_INFORMATION5.
• CURRENCY_CODE, PERIOD_TYPE, DEPENDENT_ALLOWED_FLAG, COBRA_FLAG, ER_UOM, ER_CONTR_INPUT_VALUE_ID, ROW_ID — Input currency, element information4 period type, statutory flags (defaulted to 'N' via NVL), employer-contribution UOM, and the ER CONTR input value identifier.

Common Use Cases and Queries

This view is typically queried to surface benefit-classified employer-contribution elements for US legislation forms. A representative query lists element names alongside their benefit classification and carrier:

SELECT element_name,
       benefit_classification_name,
       carrier,
       currency_code,
       period_type
FROM   apps.pay_element_types_v2
WHERE  legislation_code = 'US'
AND    benefit_classification_name IS NOT NULL
ORDER BY element_name;

Because the view filters to PROCESSING_TYPE = 'R' and the current session date, callers must run it within an APPS-initiated session that has set FND_SESSIONS; direct SQL from outside such a session may return no rows. The outer join to HR_BENEFITS_CARRIERS_V ensures elements without a carrier still appear, and the NVL defaulting on the dependent-allowed and COBRA flags prevents nulls from reaching downstream logic.