Results for “pay_ele_classification_rules_v”

28 results




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

Overview

The PAY_ELE_CLASSIFICATION_RULES_V view is a user-interface support object within the Oracle E-Business Suite Payroll (PAY) module, owned by the APPS schema and documented as VALID in both release 12.1.1 and 12.2.2. It exposes element classification rules alongside descriptive information for the classification and its associated debit or credit indicator. The view is defined in ETRM documentation as "Used to support user interface," meaning it primarily serves Oracle Forms-based payroll configuration screens, such as the Element Classification Rules window, rather than being designed as a stand-alone reporting interface. Even so, it is commonly referenced by developers and technical consultants as a convenient denormalized access point to classification-rule data, since it joins the descriptive classification name and the debit/credit meaning in a single query. Because the view is owned by APPS, it is accessible to any user or concurrent program that has been granted the standard APPS synonyms.

Underlying Base Objects

The view text joins three principal sources. The driving table is PAY_ELE_CLASSIFICATION_RULES, the base table that stores the rule rows linking an element set to a classification. PAY_ELEMENT_CLASSIFICATIONS supplies the classification identity and the COSTING_DEBIT_OR_CREDIT lookup code, while its translation table PAY_ELEMENT_CLASSIFICATIONS_TL provides the language-specific CLASSIFICATION_NAME, filtered by USERENV('LANG') so that the session language determines the displayed name. The debit/credit meaning is resolved through HR_LOOKUPS, restricted to LOOKUP_TYPE = 'DEBIT_CREDIT' and joined with an outer-join (+) so that classifications without a costing debit/credit value are still returned with a null meaning. The documented dependency list also includes HR_API (PACKAGE), which is referenced for supporting logic rather than as a direct join source. In ETRM the base objects are recorded as synonyms (PAY_ELEMENT_CLASSIFICATIONS, PAY_ELEMENT_CLASSIFICATIONS_TL, PAY_ELE_CLASSIFICATION_RULES) plus the HR_LOOKUPS view.

Key Columns

  • ROW_ID — the ROWID of the underlying PAY_ELE_CLASSIFICATION_RULES row, exposed for Forms row identification.
  • ELEMENT_SET_ID — identifies the element set to which the rule applies.
  • CLASSIFICATION_ID — the classification key linking the rule to its definition.
  • CLASSIFICATION_NAME — the translated classification description from the TL table.
  • DEBIT_OR_CREDIT — the lookup meaning for the classification's costing debit/credit indicator (for example, Debit or Credit).
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard audit columns inherited from the rule table.

Note that the view does not expose the raw COSTING_DEBIT_OR_CREDIT lookup code; only its decoded meaning is presented.

Common Use Cases and Queries

The view is typically used to list classification rules for a given element set together with their costing direction, or to validate which classifications carry a debit versus credit indicator. A representative query is:

  • SELECT element_set_id, classification_id, classification_name, debit_or_credit FROM apps.pay_ele_classification_rules_v ORDER BY element_set_id, classification_name;
  • Filtering for a specific element set: ... WHERE element_set_id = :p_element_set_id;
  • Isolating debit-coded classifications: ... WHERE debit_or_credit = 'Debit';

Because the view is documented purely as user-interface support, it should not be treated as a substitute for a controlled reporting view or a public API; where stable, supported extraction is required, referencing the base tables directly or using the corresponding payroll APIs is preferable. That said, for ad hoc queries and for reconciling what the Element Classification Rules form displays, PAY_ELE_CLASSIFICATION_RULES_V remains the most direct and readable source.