Search Results pay_legislation_rules_pk
Overview
HR.PAY_LEGISLATION_RULES is a seed data table within the Oracle E-Business Suite Payroll (PAY) schema, owned by the HR schema and registered under FND Design Data as PAY.PAY_LEGISLATION_RULES. It holds legislation-specific rules that govern how the application behaves for each supported legislation. These rules drive configuration decisions such as time period dependency management, the start of the financial year, flexfield structures for specific legislations, and the level at which soft-coded legislation values are held — organization, payroll, or assignment. The table resides in the APPS_TS_SEED tablespace with PCT Free 10, consistent with its role as reference and seed data rather than transactional data.
From a Data Vault modeling perspective, the mined relationship metadata classifies this object as standalone, meaning it is not a foreign-key participant in a hub/link/satellite network. As a modeling suggestion, it is best treated as a reference or lookup table — effectively a code-and-meaning structure — rather than a true Data Vault hub, because its rows are seeded and its natural access path is by legislation code and rule type. It should not be confused with the PAXPAY_LEGISLATION_RULES synonym, which is a three-column payroll-specific setup of the same name convention with a different structure.
Key Information Stored
The documented physical schema comprises four columns. The following are significant:
- LEGISLATION_CODE (VARCHAR2, 30, mandatory) — Code identifying the legislation to which the rule applies. This is the discriminating business key that drives legislation-specific behavior across the payroll engine.
- RULE_TYPE (VARCHAR2, 30, mandatory) — The category of rule being defined, for example time period dependency management, financial year start, flexfield structure, or soft-coded legislation level.
- RULE_MODE (VARCHAR2, 30) — The identifier or value applied for the given legislation code and rule type; effectively the control value that the payroll engine reads.
- ZD_EDITION_NAME — Editioning column present in the 12.2.2 documented schema, supporting online patching and edition-based redefinition.
The primary key is PAY_LEGISLATION_RULES_PK, defined on the composite of LEGISLATION_CODE and RULE_TYPE. The unique index of the same name carries those two columns plus ZD_EDITION_NAME in the 12.2.2 edition. Because the table has no surrogate single-column key, the composite business key (LEGISLATION_CODE, RULE_TYPE) functions as the effective primary key and the natural candidate for joins and lookups.
Common Use Cases and Queries
Typical uses include verifying the configured rule mode for a legislation before running payroll, auditing which legislations define a particular rule type, and generating extracts of legislation setup for implementation or migration documentation.
A basic lookup by legislation and rule type follows the documented query text:
- SELECT LEGISLATION_CODE, RULE_TYPE, RULE_MODE FROM HR.PAY_LEGISATION_RULES WHERE LEGISLATION_CODE = :code;
- SELECT LEGISLATION_CODE, RULE_TYPE, RULE_MODE FROM HR.PAY_LEGISLATION_RULES WHERE RULE_TYPE = :rule_type;
Because there is no foreign key to other objects, joins are made on the natural business key. Coordinating with PAY_LEGISLATION_RULES_INSERT, the insert-only synonym, allows comparison of seeded values against user-modified values for change detection. In 12.2.2, restrict queries to the current edition by filtering ZD_EDITION_NAME where editioning is active.
Related Objects
The ETRM dependency data records that HR.PAY_LEGISLATION_RULES does not reference any database object, and is referenced by the following:
- APPS.PAY_LEGISLATION_RULES — the APPS synonym through which EBS code and concurrent programs resolve the table.
- APPS.PAY_LEGISLATION_RULES_INSERT — the insert-oriented synonym, used for seed loading.
- PUBLIC.PAY_LEGISLATION_RULES — a public synonym for direct SQL access.
Related configuration objects sharing the composite key pattern include PAY_LEGISLATION_RULES_INSERT and other PAY legislation setup tables.
-
TABLE: HR.PAY_LEGISLATION_RULES
12.1.1
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_LEGISLATION_RULES, object_name:PAY_LEGISLATION_RULES, status:VALID,
-
Table: PAY_LEGISLATION_RULES
12.1.1
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_LEGISLATION_RULES, object_name:PAY_LEGISLATION_RULES, status:VALID, product: PAY - Payroll , description: Legislation specific rules and structure identifiers. , implementation_dba_data: HR.PAY_LEGISLATION_RULES ,
-
INDEX: HR.PAY_LEGISLATION_RULES_PK
12.2.2
owner:HR, object_type:INDEX, object_name:PAY_LEGISLATION_RULES_PK, status:VALID,
-
Table: PAY_LEGISLATION_RULES
12.2.2
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_LEGISLATION_RULES, object_name:PAY_LEGISLATION_RULES, status:VALID, product: PAY - Payroll , description: Legislation specific rules and structure identifiers. , implementation_dba_data: HR.PAY_LEGISLATION_RULES ,
-
INDEX: HR.PAY_LEGISLATION_RULES_PK
12.1.1
owner:HR, object_type:INDEX, object_name:PAY_LEGISLATION_RULES_PK, status:VALID,
-
TABLE: HR.PAY_LEGISLATION_RULES
12.2.2
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_LEGISLATION_RULES, object_name:PAY_LEGISLATION_RULES, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
eTRM - PAY Tables and Views
12.2.2
description: Temporary table used to hold invalid location addresses. ,
-
eTRM - PAY Tables and Views
12.1.1
description: Temporary table used to hold invalid location addresses. ,
-
eTRM - PAY Tables and Views
12.1.1
description: Temporary table used to hold invalid location addresses. ,
-
eTRM - PAY Tables and Views
12.2.2
description: Temporary table used to hold invalid location addresses. ,