Results for “pay_formula_result_rules_x”

18 results




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

Overview

PAY_FORMULA_RESULT_RULES_X is a date-effective (effective-dated) view owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) product module. It is the "_X" style reporting companion to the base "_F" table, meaning it exposes only rows whose effective date range encompasses the current system date. In Oracle EBS this naming convention separates the physical, fully versioned entity table (PAY_FORMULA_RESULT_RULES_F) from a filtered view that always returns the single active version of each record as of the query execution time.

The view presents formula result rule definitions. A formula result rule binds a result produced by a payroll formula to processing behavior — such as whether a particular result name, result rule type, or severity level should trigger status processing, warning, or error handling during a payroll run. Because these rules evolve over time, effective dating is essential, and this view provides a convenient, always-current projection suitable for reporting, validation, and downstream integration without the caller having to filter on the effective dates manually.

Underlying Base Objects

Per the documented ETRM metadata, this view is defined over a single base object: the synonym PAY_FORMULA_RESULT_RULES_F, which resolves to the underlying APPS table. The view is a thin projection that restates the filter predicate in line with EBS date-effective conventions. Structurally the definition is:

The view itself is not a stored object; it resolves at runtime against the synonym, so any change to the base table's column set or effective-dating scheme immediately propagates. This relationship means the view is read-only — no DML should be issued against it. Because the filter uses TRUNC(SYSDATE), it is evaluated in the database server's session time zone, not the user's, which should be considered in globally distributed deployments. The view is registered as VALID in the data dictionary, indicating its definition compiles cleanly against the current schema.

Key Columns

Common Use Cases and Queries

Typical uses include auditing which formula result rules are currently in force, verifying the status processing behavior attached to element results, and extracting active rules for migration or reconciliation between environments. The following queries reflect common scenarios:

  • Active rules for a business group:
    SELECT FORMULA_RESULT_RULE_ID, RESULT_NAME, RESULT_RULE_TYPE,
           STATUS_PROCESSING_RULE_ID, SEVERITY_LEVEL
    FROM   APPS.PAY_FORMULA_RESULT_RULES_X
    WHERE  BUSINESS_GROUP_ID = :p_business_group_id;
  • Rules tied to a specific status processing rule:
    SELECT FORMULA_RESULT_RULE_ID, ELEMENT_TYPE_ID, RESULT_NAME
    FROM   APPS.PAY_FORMULA_RESULT_RULES_X
    WHERE  STATUS_PROCESSING_RULE_ID = :p_status_processing_rule_id;
  • Rules filtered by legislation:
    SELECT FORMULA_RESULT_RULE_ID, LEGISLATION_CODE, RESULT_NAME
    FROM   APPS.PAY_FORMULA_RESULT_RULES_X
    WHERE  LEGISLATION_CODE = :p_legislation_code;

When the full version history is required, query the base PAY_FORMULA_RESULT_RULES_F table directly and apply an explicit date predicate. For current-state reporting within Oracle EBS 12.1.1 and 12.2.2, PAY_FORMULA_RESULT_RULES_X is the preferred access path.