Search Results formula_result_message_level




Overview
Explore in AI Chat

Overview

The view APPS.PAY_FORMULA_RESULT_RULES_D provides a denormalized, translation-aware representation of the formula result rules defined in Oracle Payroll. It is the descriptive ("_D") companion to the base table PAY_FORMULA_RESULT_RULES_F, joining rule definitions to their human-readable lookup meanings, element names, input value names, units of measure, and the identity of the last user who modified each record. In Oracle EBS 12.1.1 and 12.2.2, this view is used primarily for reporting, data extraction, and integration where consumers require resolved descriptive text rather than raw lookup codes and IDs.

Formula result rules govern how a formula's outcome is interpreted—for example, which result name a rule targets, how severity is classified, and which element or input value the rule applies to. The _D view surfaces these relationships in a single queryable object, allowing report developers and integrators to avoid re-implementing the lookup decoding logic themselves.

Underlying Base Objects

The view is constructed from the following documented base objects:

The joins apply USERENV('LANG') against translated (TL) tables so that the returned element and input value names match the session language. Effective-date predicates on the element type and input value are applied so that the joined descriptions align with the rule's own EFFECTIVE_START_DATE.

Key Columns

  • FORMULA_RESULT_RULE_ID — primary identifier of the rule.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-tracked validity of the rule.
  • RESULT_NAME — the named result the rule applies to.
  • MEANING (from RESULT_RULE_TYPE lookup) — decoded rule type, e.g., fixed or variable handling.
  • ELEMENT_NAME — translated name of the associated element type.
  • NAME (from input values) — translated name of the associated input value.
  • MEANING (from UNITS lookup) — decoded unit of measure for the input value.
  • MEANING (from FORMULA_RESULT_MESSAGE_LEVEL lookup) — the decoded severity/message level. This is the column a user searching for formula_result_message_level would consult, since the underlying lookup type carries that name.
  • LAST_UPDATE_DATE and USER_NAME — audit trail showing when and by whom the rule was last maintained.

Common Use Cases and Queries

Typical uses include auditing which result rules exist per element, verifying configured severity levels, and feeding downstream reporting extracts. A representative query:

  • SELECT FORMULA_RESULT_RULE_ID, RESULT_NAME, ELEMENT_NAME, NAME, MEANING, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE FROM APPS.PAY_FORMULA_RESULT_RULES_D WHERE EFFECTIVE_START_DATE <= SYSDATE AND NVL(EFFECTIVE_END_DATE, SYSDATE+1) > SYSDATE;
  • Filtering severity via the message level column conceptually maps to the FORMULA_RESULT_MESSAGE_LEVEL lookup, useful when isolating high-severity rules.
  • Joining to FND_USER-derived USER_NAME for change-audit reports.

Because the view respects translated tables and session language, it should be queried in a session whose LANG is set appropriately to obtain accurate element and input value names.