Results for “hr_s_formula_result_rules_f”

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

Overview

The table HR.HR_S_FORMULA_RESULT_RULES_F is a Human Resources (PER product) validation and rules configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definitions that govern how payroll and element formula results are evaluated, categorized, and acted upon during payroll processing and element calculation. The "_F" suffix indicates that the table is date-tracked ("F" for the date-effective "F" schema object) and its rows are governed by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns, allowing the same business rule to change over time without losing historical configuration.

Per the ETRM metadata, the object is described as "- Retrofitted," reflecting that the table was introduced or reconstructed as part of the date-effective table retrofit architecture, consolidating validation logic that may previously have been held elsewhere. Its documented Data Vault classification (heuristic, mined from the FK structure) is standalone. In Data Vault modeling terms, this suggests treating the object as a standalone satellite attached to a parent hub (the related PAY_SHADOW_FORMULA_RULES entity) rather than as a link table, since no dependent foreign keys to downstream tables are documented.

Key Information Stored

Each row defines one result-processing rule. The most significant columns documented in the physical schema are:

• FORMULA_RESULT_RULE_ID — the surrogate primary key. The documented FK maps this column to PAY_SHADOW_FORMULA_RULES, indicating the rule is anchored to a formula ruleset record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective control dates; the business-key candidate for a rule version is effectively the rule ID combined with the start date.
• BUSINESS_GROUP_ID — the enterprise/business group partition, a standard multi-tenancy key in HR tables.
• LEGISLATION_CODE and LEGISLATION_SUBGROUP — identify the country and statutory subgroup to which the rule applies.
• ELEMENT_TYPE_ID — the payroll element type whose result is being governed.
• RESULT_NAME — the name of the formula result being validated or classified.
• RESULT_RULE_TYPE — the kind of rule applied to that result (for example, severity-driven handling).
• STATUS_PROCESSING_RULE_ID and SEVERITY_LEVEL — control how an out-of-range or flagged result is processed and how severe the condition is deemed.
• INPUT_VALUE_ID — ties the rule to an input value definition when the condition depends on input data.
• Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER — the standard WHO columns plus optimistic-locking version number.

Common Use Cases and Queries

Typical scenarios include auditing which severity handling applies to a given element result, extracting legislation-specific rule sets for migration or comparison, and tracing changes over time using the effective dates. A representative query joining the rule to its parent formula ruleset is:

SELECT r.FORMULA_RESULT_RULE_ID, r.ELEMENT_TYPE_ID, r.RESULT_NAME, r.RESULT_RULE_TYPE, r.SEVERITY_LEVEL, r.EFFECTIVE_START_DATE
FROM HR.HR_S_FORMULA_RESULT_RULES_F r
WHERE r.BUSINESS_GROUP_ID = :p_bg_id
AND :p_effective_date BETWEEN r.EFFECTIVE_START_DATE AND r.EFFECTIVE_END_DATE;

Date-effective queries should always constrain the effective date against the start and end dates. Reporting tools such as Oracle Business Intelligence or custom Fast Formulas often reference this table indirectly when troubleshooting payroll run validation messages.

Related Objects

• PAY_SHADOW_FORMULA_RULES — referenced through HR_S_FORMULA_RESULT_RULES_F.FORMULA_RESULT_RULE_ID, the primary relationship path.
• PAY_ELEMENT_TYPES_F — joined on ELEMENT_TYPE_ID to resolve element attributes.
• PAY_INPUT_VALUES_F — joined on INPUT_VALUE_ID for input-driven conditions.
• FND_ID_FLEX_STRUCTURES / business-group lookups — resolved via BUSINESS_GROUP_ID.
• Legislation lookup views — resolved via LEGISLATION_CODE.
• The concurrent manager and payroll run APIs that consume these rules during element processing.