Search Results pay_legislative_field_info_pk

Overview

The PAY_LEGISLATIVE_FIELD_INFO table is a Payroll (PAY) module data object owned by the HR schema. Its documented purpose is to control legislative rules on individual form fields within Oracle E-Business Suite. In practice, this table drives country-specific validation, prompts, rule modes, and message text that appear on payroll and related forms, allowing legislation-specific behavior to be configured declaratively rather than hard-coded. It is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2.

From a data modeling perspective, the ETRM metadata classifies this object heuristically as standalone under the Data Vault classification scheme. This suggests it functions as a reference or configuration table rather than participating in a hub-and-link relationship, and no foreign-key dependencies are documented for it in the supplied metadata. The business key is defined by the combination of FIELD_NAME, LEGISLATION_CODE, and RULE_TYPE.

Key Information Stored

The table contains 14 documented columns. The most significant columns and their roles are summarized below.

• FIELD_NAME — Identifies the individual form field to which the legislative rule applies. Part of the business key.
• LEGISLATION_CODE — The country or legislative context that governs the rule. Part of the business key.
• RULE_TYPE — Defines the category of rule applied to the field. Part of the business key.
• RULE_MODE — Controls how the rule behaves at runtime (for example, enforcement mode).
• VALIDATION_NAME and VALIDATION_TYPE — Identify and classify the validation applied to the field.
• TARGET_LOCATION — Specifies where the rule or prompt is targeted.
• PROMPT — The display label presented for the field.
• PROMPT_MESSAGE, IN_LINE_MESSAGE, QUICK_TIP_MESSAGE, BUBBLE_TIP_MESSAGE — Provide user-facing message text at various display locations.
• CATEGORY — Groups related field information entries.
• ZD_EDITION_NAME — Editioning column supporting online patching in 12.2.x.

The documented physical primary key is PAY_LEGISLATIVE_FIELD_INFO_PK, defined on the business-key columns. A separate unique index is documented that spans TARGET_LOCATION, VALIDATION_NAME, FIELD_NAME, LEGISLATION_CODE, RULE_TYPE, and ZD_EDITION_NAME, representing an additional business-key candidate.

Common Use Cases and Queries

This table is most commonly queried to determine which legislative rules and prompts apply to a given payroll form field for a specific country. Typical scenarios include auditing field-level configuration, troubleshooting validation messages, and documenting localization behavior for a legislation.

A representative query retrieves all rules for a given legislation and field:

• SELECT field_name, rule_type, rule_mode, validation_name, prompt
• FROM pay_legislative_field_info
• WHERE legislation_code = 'US' AND field_name = :field_name;

Reporting use cases include inventorying available prompts and messages by category, and comparing rule modes across legislations to identify configuration drift. Because ZD_EDITION_NAME participates in editioning, queries in 12.2.x should account for the active edition when filtering.

Related Objects

The supplied metadata documents PAY_LEGISLATIVE_FIELD_INFO as standalone, with no explicit foreign keys. Related objects are therefore identified by shared legislative and field-level configuration context within the Payroll module.

• PAY_LEGISLATIVE_FIELDS — Defines the legislative fields referenced by FIELD_NAME.
• FND_FORM_FUNCTIONS — Form-level metadata aligned to the fields governed by this table.
• FND_LOOKUP_VALUES — Frequently stores enumerations for values such as RULE_TYPE and RULE_MODE.
• PAY_LEG_FIELD_INFO — Related legislative field information definitions.
• HR_ALL_ORGANIZATION_UNITS — Organizational context for payroll configuration.

Because no foreign keys are documented, joins to these objects should be validated against the actual environment before being relied upon in production reporting.