Search Results input_data_type

Overview

APPS.PAY_FORMULA_RESULT_RULES_V is a reporting view in the Oracle E-Business Suite (EBS) HRMS/Payroll schema, present in both 12.1.1 and 12.2.2. It presents configuration data from the Formula Result Rules entity, which determines how the results returned by an Oracle FastFormula are processed after the formula executes. A formula result rule associates a specific result name from a formula with a status processing rule, a severity level, and optionally an input value, so that the payroll or element processing engine knows how to interpret, validate, or act on the returned value.

The view exists primarily to denormalize and decode the underlying foreign keys into human-readable descriptions. Rather than requiring a report author or integration developer to resolve lookup codes and translation rows manually, the view combines the base result-rule row with translated element names, translated input-value names, decoded lookup meanings, and unit-of-measure information. This makes it suitable for dataloads, extracts, audit reports, and configuration queries. The presence of the RULE_TYPE_NAME column, which the user searched for, is one of the primary reasons this view is referenced: it exposes the decoded RULE_TYPE_NAME value derived from the RESULT_RULE_TYPE lookup.

Underlying Base Objects

The view is defined over the following documented objects:

• PAY_FORMULA_RESULT_RULES_F — the primary base table, aliased RESULT_RULE, holding the formula result rule definitions.
• PAY_INPUT_VALUES_F and PAY_INPUT_VALUES_F_TL — supply the input value and its translated name (VALUETL.NAME, aliased INPUT_VALUE_NAME).
• PAY_STATUS_PROCESSING_RULES_F (SPR) — the status processing rule joined on STATUS_PROCESSING_RULE_ID.
• PAY_ELEMENT_TYPES_F and PAY_ELEMENT_TYPES_F_TL — provide the element type and its translated name (ELEMENTTL.ELEMENT_NAME).
• FND_SESSIONS (CURRENT_SESSION) — constrains the view to the current session’s effective date.
• HR_GENERAL (PACKAGE) — provides the decode_lookup function used to resolve lookup meanings.

Outer joins (+) are applied to the translation tables and, in places, to the base tables, so that rows survive where a translated or optional value is absent. The translation joins filter on USERENV('LANG') to return only the current language row.

Key Columns

• FORMULA_RESULT_RULE_ID — primary identifier of the result rule.
• RESULT_RULE_TYPE — the raw lookup code; RULE_TYPE_NAME is its decoded meaning via HR_GENERAL.DECODE_LOOKUP('RESULT_RULE_TYPE', …).
• SEVERITY_LEVEL and SEVERITY_LEVEL_NAME — raw and decoded message severity (lookup FORMULA_RESULT_MESSAGE_LEVEL).
• INPUT_VALUE_ID, INPUT_VALUE_NAME, INPUT_DATA_TYPE, UNIT_OF_MEASURE — the associated input value, its translated name, its UOM data type, and the decoded UNIT_OF_MEASURE.
• ELEMENT_TYPE_ID, ELEMENT_NAME, LEGISLATION_CODE, LEGISLATION_SUBGROUP, BUSINESS_GROUP_ID — element and legislative context.
• RESULT_NAME — the formula result this rule governs.
• STATUS_PROCESSING_RULE_ID — the linked status processing rule.
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — date-effective bounds.
• ROW_ID and audit columns (LAST_UPDATE_DATE, CREATED_BY, etc.) — row identity and audit trail.

Common Use Cases and Queries

Typical uses include auditing result rules per element, extracting configuration for migration, and joining to status processing rules to trace how a formula result drives a status change. A representative query follows:

• SELECT formula_result_rule_id, result_name, rule_type_name, severity_level_name, element_name, input_value_name, unit_of_measure FROM apps.pay_formula_result_rules_v WHERE legislation_code = :p_leg ORDER BY element_name, result_name;
• SELECT result_name, rule_type_name, input_value_name, unit_of_measure FROM apps.pay_formula_result_rules_v WHERE element_type_id = :p_element AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
• SELECT rule_type_name, COUNT(*) FROM apps.pay_formula_result_rules_v GROUP BY rule_type_name;

Because the view enforces the current FND session effective date, results reflect the active date-effective record for the session context, which must be accounted for when querying from external tools.