Search Results pay_formula_result_rules_v




Overview
Explore in AI Chat

Overview

The PAY_FORMULA_RESULT_RULES_V view is an APPS-owned, VALID database view within the Oracle E-Business Suite Payroll (PAY) module. According to the ETRM metadata, its purpose is "Used to support user interface," meaning it is not a standalone reporting object but rather a UI-support view that surfaces decoded, human-readable information for the Payroll forms and self-service pages that manage formula result rules.

In Oracle EBS 12.1.1 and 12.2.2, the view presents formula result rule definitions alongside the descriptive names of their associated lookups and translation records. It joins the base result-rules table to element type, input value, status processing rule, and lookup data, producing a single denormalized row per result rule that is directly consumable by the Oracle Forms-based Payroll configuration UI. Because it exposes ROWID as ROW_ID and includes effective dating columns, it also serves developers who perform EBS integration work or build ad hoc extractions that need the same decoded values the UI displays, without having to replicate the lookup decoding logic themselves.

Underlying Base Objects

The view is defined over the following documented base objects:

Most joins to translation tables are outer joins, with a DECODE clause substituting '1' when no translation row exists; the language filter resolves against USERENV('LANG'). The session constraint uses CURRENT_SESSION.SESSION_ID = USERENV('SESSIONID').

Key Columns

Common Use Cases and Queries

The view is commonly queried to inspect configured formula result rules alongside readable lookup values, to validate the mapping between elements, input values, and status processing rules, and to feed integration extracts that require decoded attributes.

Example — listing all rules for a legislation:

SELECT formula_result_rule_id,
       result_name,
       rule_type_name,
       severity_level_name,
       element_name,
       input_value_name
FROM   apps.pay_formula_result_rules_v
WHERE  legislation_code = 'US'
ORDER  BY element_name, result_name;

Example — retrieving rules for a specific element type:

SELECT result_name, rule_type_name, unit_of_measure
FROM   apps.pay_formula_result_rules_v
WHERE  element_type_id = :p_element_type_id;

Practitioners should note that the view enforces a current-session constraint; it should therefore be queried from within an active EBS session context rather than from a disconnected external tool, unless the session predicate is accounted for.