Search Results pay_element_set_members




Overview
Explore in AI Chat

Overview

PAY_ELEMENT_SET_MEMBERS is an APPS-owned view in the Oracle E-Business Suite Payroll (PAY) product. Its documented purpose is to present the list of elements contained in each element set. Because element sets are the containers through which payroll runs, costing, and reporting processes determine which element types participate in a calculation, this view provides the resolution layer between a set definition and its constituent members.

In Oracle EBS 12.1.1 and 12.2.2, the view is most commonly reached during payroll debugging and data extraction tasks, particularly when a user needs to trace which ELEMENT_TYPE_ID values belong to a given ELEMENT_SET_ID. The view is defined as a UNION of two branches, reflecting the two distinct ways an element may be attached to a set: by classification rule, or by an explicit inclusion rule recorded on PAY_ELEMENT_TYPE_RULES. Elements explicitly excluded through an INCLUDE_OR_EXCLUDE = 'E' rule are filtered out by a NOT EXISTS clause, ensuring exclusion rules always take precedence.

Underlying Base Objects

The view is defined over the following documented objects: HR_LOOKUPS (VIEW), PAY_ELEMENT_TYPES (VIEW), PAY_ELEMENT_CLASSIFICATIONS (SYNONYM), PAY_ELEMENT_CLASSIFICATIONS_TL (SYNONYM), PAY_ELEMENT_SETS (SYNONYM), PAY_ELEMENT_TYPE_RULES (SYNONYM), PAY_ELE_CLASSIFICATION_RULES (SYNONYM), and PAY_INPUT_VALUES_F (SYNONYM). HR_API (PACKAGE) is also listed as a referenced base object.

PAY_ELEMENT_SET_MEMBERS is a view rather than a table, so the list it returns is derived at query time from the referenced structures. Each branch of the UNION joins PAY_ELEMENT_SETS to PAY_ELEMENT_TYPES, either through PAY_ELE_CLASSIFICATION_RULES (classification-driven membership) or through PAY_ELEMENT_TYPE_RULES with an inclusion indicator (explicit membership). PAY_ELEMENT_CLASSIFICATIONS and its translation table supply the classification name, while HR_LOOKUPS with LOOKUP_TYPE = 'PROCESSING_TYPE' decodes the processing type into a meaning.

A special condition applies to element sets of type 'D' (a legislative or "PAY VALUE" set type); the classification branch additionally requires the existence of an input value on PAY_INPUT_VALUES_F whose UOM is 'M' and whose name corresponds to the translated 'PAY VALUE' lookup. Sets of type 'R' or 'C' are not subject to that restriction.

Key Columns

  • ELEMENT_SET_ID — Identifier of the element set to which the member belongs. This is the primary join key back to PAY_ELEMENT_SETS.
  • ELEMENT_TYPE_ID — Identifier of the member element type. This is the column most frequently searched by users, and the effective primary key of the row alongside ELEMENT_SET_ID.
  • ELEMENT_NAME — Name of the element type.
  • CLASSIFICATION_ID and CLASSIFICATION_NAME — The classification of the element and its translated display name, drawn from PAY_ELEMENT_TYPES and PAY_ELEMENT_CLASSIFICATIONS_TL respectively.
  • PROCESSING_TYPE and PROCESSING_TYPE_MEANING — The processing type code and its decoded meaning from HR_LOOKUPS.
  • BUSINESS_GROUP_ID and LEGISLATION_CODE — Business group and legislation context of the element, useful for multi-business-group and multi-legislation filtering.

Common Use Cases and Queries

Typical uses include identifying the members of a specific element set, finding every set that contains a particular element type, and validating that an exclusion rule has correctly removed an element from a set.

List all members of a given element set:

  • SELECT element_set_id, element_type_id, element_name, classification_name, processing_type_meaning FROM apps.pay_element_set_members WHERE element_set_id = :set_id ORDER BY element_name;

Reverse lookup — find all element sets containing a given element type:

  • SELECT element_set_id, element_type_id, element_name FROM apps.pay_element_set_members WHERE element_type_id = :element_type_id;

Confirm eligibility of members for a specific legislation before running a payroll process:

  • SELECT element_set_id, element_type_id, element_name, classification_name FROM apps.pay_element_set_members WHERE legislation_code = :leg_code AND element_set_id = :set_id;

As the view is a query-time construct, performance depends on the underlying joins; filtering by ELEMENT_SET_ID or ELEMENT_TYPE_ID is recommended wherever possible.