Results for “severity_level”

50+ results




Overview
Explore in AI Chat

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

Overview

The PAY_ITERATIVE_RULES_X view is a dated, effective-dated database object owned by the APPS schema within the PAY (Payroll) product module of Oracle E-Business Suite. It is available in both 12.1.1 and 12.2.2 and holds a status of VALID. The view surfaces configuration records that govern iterative rules used during payroll processing, specifically the rules that drive repeated recalculation of an element's results until a defined condition or severity threshold is satisfied.

The "_X" suffix follows Oracle EBS naming convention and signals that this is the effective-dated (transactional) view of the underlying base entity. Whereas the "_F" (foundation) table stores all historical versions of a row, the "_X" view filters to only those rows currently in force, i.e., where the system date falls between the effective start and end dates. This makes PAY_ITERATIVE_RULES_X the appropriate source for runtime payroll processing, for validation reports, and for integration queries that require the active configuration rather than archived history. The column ITERATIVE_RULE_TYPE, which the user searched for, is exposed directly here and classifies the nature of each iterative rule.

Underlying Base Objects

The view is defined over a single documented base object, PAY_ITERATIVE_RULES_F, referenced through a synonym. The complete view definition is:

The critical behavioral distinction is the predicate TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE. This date-range filter means the view returns exactly one version of each iterative rule per effective period, eliminating the historical rows that persist in the foundation table. Because the filter is evaluated against the database server's current system date, the view's result set changes automatically over time as effective dates elapse. Queries against _X therefore always reflect the configuration that payroll would use on the day of execution.

Key Columns

  • ITERATIVE_RULE_ID — Primary identifier for the iterative rule record.
  • ELEMENT_TYPE_ID — Foreign key to the element type to which the rule applies.
  • ITERATIVE_RULE_TYPE — Classification of the iterative rule, distinguishing how the recalculation loop is governed.
  • RESULT_NAME — The name of the result value that the rule monitors or evaluates.
  • INPUT_VALUE_ID — Identifier of the input value associated with the rule.
  • SEVERITY_LEVEL — The severity assigned when the rule condition is triggered.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date bounds that define the rule's validity window.
  • BUSINESS_GROUP_ID — Business group that owns the rule, supporting multi-tenancy.
  • LEGISLATION_CODE — The legislative context in which the rule operates.

Common Use Cases and Queries

Typical scenarios include auditing active iterative rules, diagnosing payroll processing loops, and extracting configuration for migration or testing. Because the "_X" view is date-filtered, it is preferable to the "_F" table whenever current-state data is required.

  • List all active iterative rules by legislation: SELECT ITERATIVE_RULE_ID, ITERATIVE_RULE_TYPE, RESULT_NAME, SEVERITY_LEVEL FROM PAY_ITERATIVE_RULES_X WHERE LEGISLATION_CODE = 'US';
  • Find rules tied to a specific element type: SELECT * FROM PAY_ITERATIVE_RULES_X WHERE ELEMENT_TYPE_ID = :element_type_id;
  • Filter by rule type: SELECT RESULT_NAME, INPUT_VALUE_ID FROM PAY_ITERATIVE_RULES_X WHERE ITERATIVE_RULE_TYPE = :rule_type;
  • Inspect rules scoped to a business group alongside their effective dates.

Joining ITERATIVE_RULE_ID to the foundation table reveals historical changes, while querying the view alone yields only the configuration in force today.