Search Results include_or_exclude_meaning




Overview
Explore in AI Chat

Overview

The APPS.PAY_ELEMENT_TYPE_RULES_V view is a reporting and integration object within the Oracle E-Business Suite Payroll (PAY) module. As documented in the ETRM repository for releases 12.1.1 and 12.2.2, it is a VALID view owned by the APPS schema whose stated purpose is "to support user interface" functionality. In practice, the view serves as a denormalized, user-friendly presentation of the PAY_ELEMENT_TYPE_RULES base table, which governs whether a given element type is included in or excluded from an element set for processing.

Unlike the raw rules table, which stores only numeric and coded identifiers, this view resolves foreign keys into descriptive, language-aware text. It joins element type translations, element classification translations, and Oracle HR lookups so that each rule row surfaces readable element names, processing types, classification names, and the decoded meaning of the INCLUDE_OR_EXCLUDE flag. This makes the view directly usable in concurrent program outputs, custom reports, OAF-based pages, and integration extracts without requiring downstream consumers to replicate the lookup logic themselves.

Underlying Base Objects

The view is defined over the following documented base objects:

  • PAY_ELEMENT_TYPE_RULES (synonym) — the primary transactional table holding include/exclude rules per element type and element set.
  • PAY_ELEMENT_TYPES_F / PAY_ELEMENT_TYPES_F_TL (synonyms) — the element type base and translation tables, supplying element names and processing type codes in the user's current session language.
  • PAY_ELEMENT_CLASSIFICATIONS / PAY_ELEMENT_CLASSIFICATIONS_TL (synonyms) — base and translated classification definitions, providing the classification name.
  • HR_LOOKUPS (view) — joined twice: once on lookup type INCLUDE_EXCLUDE to decode INCLUDE_OR_EXCLUDE, and once on lookup type PROCESSING_TYPE to decode the element's processing type.
  • FND_SESSIONS (synonym) — used to enforce effective dating, ensuring the element type is effective as of the session effective date.
  • HR_API (package) — referenced as part of the surrounding Payroll API surface that governs rule maintenance.

A key characteristic of the definition is its dependence on USERENV('LANG') for translated columns and USERENV('SESSIONID') via FND_SESSIONS for effective-date filtering. Consequently, results can vary by session language and effective date context, which must be accounted for when using the view in batch or integration logic.

Key Columns

  • ROW_ID — the ROWID of the underlying PAY_ELEMENT_TYPE_RULES row; useful as a unique identifier for updates or diagnostics.
  • ELEMENT_TYPE_ID — foreign key to the element type to which the rule applies.
  • ELEMENT_SET_ID — the element set within which the include/exclude rule operates.
  • INCLUDE_OR_EXCLUDE — the stored lookup code indicating whether the element is included in or excluded from the element set.
  • INCLUDE_OR_EXCLUDE_MEANING — the decoded, user-facing meaning of the include/exclude flag, resolved from the INCLUDE_EXCLUDE lookup type.
  • ELEMENT_NAME — the translated name of the element type, resolved in the session language.
  • PROCESSING_TYPE — the translated meaning of the element's processing type (for example, the standard processing category lookup values).
  • CLASSIFICATION_NAME — the translated element classification name.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE for change tracking and reconciliation.

Common Use Cases and Queries

Typical scenarios include validating element set configuration before a payroll run, auditing which elements are included or excluded for a given set, and feeding downstream integrations with human-readable rule data.

Retrieve all rules for a specific element set:

  • SELECT element_name, classification_name, include_or_exclude_meaning FROM pay_element_type_rules_v WHERE element_set_id = :p_element_set_id;

List excluded elements with their processing types for reconciliation:

  • SELECT element_name, processing_type, classification_name FROM pay_element_type_rules_v WHERE include_or_exclude_meaning = 'Exclude' ORDER BY element_name;

Because translated columns depend on USERENV('LANG') and effective dating on FND_SESSIONS, report logic should set the correct session context or join directly to the underlying base tables when language- and date-independent results are required.