Results for “base_element_set_name”

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

Overview

PAY_ELEMENT_SETS_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is part of the PAY (Payroll) product family and exposes element set definitions maintained through the Oracle Payroll application. An element set is a named grouping of payroll elements used for processing, reporting, and eligibility rules, such as defining which earnings and deductions apply to a specific payroll run, assignment set, or legislative context.

Because the view follows the standard Oracle Applications translation pattern, it joins the base (untranslated) table with its translation table and filters on the session language through USERENV('LANG'). This means a query against PAY_ELEMENT_SETS_VL automatically returns the element set name translated into the language of the current user session, provided a translation row exists. The view is marked VALID and is intended for concurrent programs, forms, OAF pages, and custom reports and interfaces that need language-appropriate element set names without managing translation joins themselves.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms:

• PAY_ELEMENT_SETS — stores the primary, language-independent attributes of each element set, including identifier, business group, legislation, comments, and audit columns. This is the driving table (aliased B in the view definition).
• PAY_ELEMENT_SETS_TL — the translation table holding the language-specific element set name. It is joined on ELEMENT_SET_ID, with the additional predicate TL.LANGUAGE = USERENV('LANG').

The join condition is B.ELEMENT_SET_ID = TL.ELEMENT_SET_ID. The view definition selects B.ROWID as ROW_ID, then the core driver columns, and finally TL.ELEMENT_SET_NAME (which is the translated value) in place of the base name. This structure is consistent with Oracle's standard VL view convention across EBS products.

Key Columns

• ROW_ID — the ROWID of the underlying row in PAY_ELEMENT_SETS; used by Oracle Forms for row-level identification.
• ELEMENT_SET_ID — the unique primary key of the element set. Use this for joins to related payroll tables.
• BUSINESS_GROUP_ID — identifies the business group (HR security group) that owns the element set.
• LEGISLATION_CODE — the legislation (for example, US, CA, GB) under which the element set is defined.
• ELEMENT_SET_NAME — the translated element set name returned from PAY_ELEMENT_SETS_TL for the session language. A BASE_ELEMENT_SET_NAME column is documented in the view column list.
• ELEMENT_SET_TYPE — the classification of the element set, which governs how the set is applied in payroll processing.
• COMMENTS — free-form descriptive text attached to the element set.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard Oracle audit columns.

Common Use Cases and Queries

Typical scenarios include resolving element set names for payroll run parameter listings, building LOVs for custom forms, and extracting element set definitions into reporting or data-warehouse layers. The view is preferred over the base tables whenever the display name must respect the user's language.

List element sets for a business group and legislation:

• SELECT element_set_id, element_set_name, element_set_type, legislation_code FROM apps.pay_element_sets_vl WHERE business_group_id = :p_bg_id AND legislation_code = 'US';

Retrieve a single element set by name for validation within a custom concurrent program:

• SELECT element_set_id, element_set_name FROM apps.pay_element_sets_vl WHERE element_set_name = :p_name;

Join to payroll element linkages to enumerate the elements contained in a set:

• SELECT es.element_set_name, pe.element_name FROM apps.pay_element_sets_vl es, apps.pay_element_set_elements ese, apps.pay_elements_vl pe WHERE es.element_set_id = ese.element_set_id AND ese.element_id = pe.element_id;

Because the language predicate is embedded in the view, callers should not add their own translation join; doing so risks duplicate rows. Queries should always be filtered by BUSINESS_GROUP_ID where applications are multi-organization, since element set names are only unique within a business group context.