Results for “pay_element_types_v”

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

Overview

PAY_ELEMENT_TYPES_V is a valid, APPS-owned database view within the Oracle E-Business Suite Payroll (PAY) product module. Per the ETRM documentation, its stated purpose is "to support user interface" — that is, it is an interface-support view rather than a transactional or standalone reporting table. It presents element type definitions in a denormalized, user-friendly form by joining base element type tables to their translation tables, classification tables, and lookup tables, resolving internal identifiers and codes into descriptive names and meanings.

Because the view joins across multiple base objects and applies language and session-date filters, it presents a single, ready-to-consume row per element type appropriate for a given user session. This makes it valuable for reporting, integrations, and custom queries where human-readable element names, classifications, and lookup meanings are required without manually reproducing the EBS translation and effective-dating logic.

Underlying Base Objects

The documented view text defines PAY_ELEMENT_TYPES_V over the following base objects:

• PAY_ELEMENT_TYPES_F — the base (non-translated) element types table, supplying element type identity, currency codes, business group, legislation, processing type, classification, and effective dates.
• PAY_ELEMENT_TYPES_F_TL — the translated table supplying language-specific ELEMENT_NAME and DESCRIPTION.
• PAY_ELEMENT_CLASSIFICATIONS — the classifications table linking classification identifiers to element types.
• PAY_ELEMENT_CLASSIFICATIONS_TL — the translated classifications table supplying language-specific CLASSIFICATION_NAME.
• HR_LOOKUPS — a lookup view used to resolve the PROCESSING_TYPE code into a descriptive MEANING, filtered on LOOKUP_TYPE = 'PROCESSING_TYPE'.
• FND_SESSIONS — referenced as a synonym for session context; supplies the effective date used to enforce the effective-dating window on element types.

The ETRM metadata also lists HR_API (PACKAGE) among referenced objects. The view text additionally uses key joins: ELEMENT_TYPE_ID between PAY_ELEMENT_TYPES_F and its TL table, CLASSIFICATION_ID between PAY_ELEMENT_TYPES_F and PAY_ELEMENT_CLASSIFICATIONS, and LOOKUP_CODE against PROCESSING_TYPE for the lookup meaning.

Key Columns

• ELEMENT_TYPE_ID — surrogate primary key identifying the element type.
• ELEMENT_NAME — the language-specific name from PAY_ELEMENT_TYPES_F_TL.
• CLASSIFICATION_NAME — the language-specific classification name from PAY_ELEMENT_CLASSIFICATIONS_TL (for example, Earnings, Deductions).
• MEANING — the lookup meaning for the element's PROCESSING_TYPE (for example, Recurring, Nonrecurring).
• DESCRIPTION — the language-specific description from the TL table.
• INPUT_CURRENCY_CODE — the currency applied to element input values.
• OUTPUT_CURRENCY_CODE — the currency applied to element output values.
• BUSINESS_GROUP_ID — the business group that owns the element type.
• LEGISLATION_CODE — the legislation under which the element type is defined.

Common Use Cases and Queries

PAY_ELEMENT_TYPES_V is typically queried to list element types with readable attributes, to drive LOVs and interface screens, and to support reporting over payroll element configurations. A representative query retrieves all element types for the current session:

SELECT element_type_id, element_name, classification_name, meaning, description, legislation_code FROM apps.pay_element_types_v ORDER BY element_name;

To filter to recurring earnings elements within a legislation:

SELECT element_type_id, element_name, input_currency_code FROM apps.pay_element_types_v WHERE classification_name = 'Earnings' AND meaning = 'Recurring' AND legislation_code = 'US';

Because the view enforces language via USERENV('LANG') and effective dating via FND_SESSIONS, correct results depend on a valid EBS session context; direct SQL outside an application session may return restricted rows. Consumers should treat it as a read-only presentation view and not attempt DML against it.