Results for “rule_type”

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

Overview

PAY_LEGISLATION_RULES is a configuration table in the Oracle E-Business Suite Payroll (PAY) module, owned by the HR schema. It stores legislation-specific rules and structure identifiers that govern how payroll processing behaves for a given country or regulatory jurisdiction. Each row associates a legislation code with a rule type and the mode in which that rule operates, effectively acting as a control table consulted by the payroll engine during calculations, validations, and reporting.

Within the context of Oracle EBS 12.1.1 and 12.2.2, the table is documented as VALID and contains four physical columns. The heuristic Data Vault classification mined from the foreign key structure is standalone, meaning the table does not participate as a link between major business entities. From a modeling perspective, this classification suggests treating the object as a reference or lookup structure rather than a transactional hub; its rows are largely static configuration data maintained by legislation administrators rather than high-volume transaction records.

Key Information Stored

The documented physical schema exposes a compact set of four columns, with the primary key composed of two business-identifying attributes:

• LEGISLATION_CODE — The country or regulatory jurisdiction code (for example, US, GB, CA) that the rule applies to. This is the leading component of the primary key and the primary partitioning dimension for the data.
• RULE_TYPE — The category or kind of legislation rule being defined. Combined with LEGISLATION_CODE, it forms the compound business key PAY_LEGISLATION_RULES_PK.
• RULE_MODE — Indicates the operational mode or behavior of the rule, controlling how the payroll engine interprets or enforces the rule for the given legislation and type.
• ZD_EDITION_NAME — A editioning column associated with Oracle Edition-Based Redefinition (EBR), used in 12.2.x to manage edition-aware access. It appears in the unique index PAY_LEGISLATION_RULES_PK, which is documented as LEGISLATION_CODE, RULE_TYPE, ZD_EDITION_NAME.

The surrogate primary key is represented by the PAY_LEGISLATION_RULES_PK constraint. There is no separate single-column surrogate such as a system-generated ID; instead, the business key (LEGISLATION_CODE plus RULE_TYPE, extended by ZD_EDITION_NAME in the documented index) serves as the unique identifier. This reinforces the table's role as a static reference object.

Common Use Cases and Queries

Typical use cases center on determining which rules are active for a jurisdiction and how they are evaluated during payroll runs. Report developers and payroll administrators query the table to audit legislation configuration, validate that required rule types exist for a country, and diagnose payroll processing behavior.

A representative query to list all rules for a given legislation is:

• SELECT legislation_code, rule_type, rule_mode FROM pay_legislation_rules WHERE legislation_code = :p_legislation ORDER BY rule_type;
• SELECT rule_mode, COUNT(*) FROM pay_legislation_rules WHERE legislation_code = 'US' GROUP BY rule_mode;

Common reporting scenarios include verifying configuration completeness during implementations, comparing rule modes across legislations when globalizing payroll, and diagnosing unexpected payroll results by confirming the governing rule mode. Because the table is edition-aware in 12.2.x, edition-qualified queries should account for ZD_EDITION_NAME when run in environments using EBR.

Related Objects

The documented relationship data classifies this object as standalone, indicating no outgoing foreign keys to other business entities. Dependencies are therefore mostly inbound (other logic or views referencing legislation rules) rather than strict FK-driven. Significant related objects include:

• PAY_LEGISLATION_RULES_PK — the primary key constraint that enforces uniqueness on LEGISLATION_CODE and RULE_TYPE.
• PAY_LEGISLATION_RULES_PK (unique index) — documented as LEGISLATION_CODE, RULE_TYPE, ZD_EDITION_NAME, supporting edition-aware lookups.
• Other PAY legislation-level configuration tables that reference LEGISLATION_CODE as a shared jurisdiction key, allowing joins across regulatory setup objects.
• Payroll processing and calculation logic that consults RULE_TYPE and RULE_MODE at runtime, rather than through a declared foreign key.
• Legislation setup and administrative forms within the Payroll module where this configuration is maintained.

Given the limited documented FK footprint, joins to related legislation tables should be constructed explicitly on LEGISLATION_CODE rather than assumed through declared constraints.