Search Results pay_legislation_contexts_pk




Overview

PAY_LEGISLATION_CONTEXTS is a reference and mapping table in the Oracle E-Business Suite Payroll (PAY) module, owned by the HR schema. Its documented purpose is to map core contexts to legislative names. In practical terms, the table associates a legislative code — the identifier for a country or regional payroll legislation — with the internal context identifiers that drive legislative-specific behavior, and it carries the corresponding legislation name and input value name for each mapping. The table is classified as VALID and contains five documented columns in the ETRM 12.2.2 physical schema.

From a data modeling perspective, the heuristic Data Vault classification derived from the foreign key structure is standalone. This suggests the object functions as a self-contained reference or lookup table rather than as a hub, link, or satellite within a larger integration model. Because it holds relatively static legislative configuration data, it is best treated as a reference dimension that supports context resolution across payroll processing, costing, and reporting.

Key Information Stored

The table stores a compact set of mapping attributes. The most significant documented columns are:

  • LEGISLATION_CODE — The legislative identifier (for example, a country or territory code) that scopes the mapping to a specific payroll legislation.
  • CONTEXT_ID — The internal context identifier being mapped to the legislative name; this links the row to the broader context model used by the payroll engine.
  • LEGISLATION_NAME — The human-readable name of the legislation, used for display and reporting.
  • INPUT_VALUE_NAME — The name associated with the input value for the context, supporting user-facing and validation logic.
  • ZD_EDITION_NAME — The editioning column introduced by the EBS online patching infrastructure in Release 12.2, used to isolate edition-specific data during patching cycles.

The documented primary key is PAY_LEGISLATION_CONTEXTS_PK. The ETRM metadata lists the primary key as (LEGISLATION_CODE, CONTEXT_ID), while the unique index definition for the same constraint includes (LEGISLATION_CODE, CONTEXT_ID, ZD_EDITION_NAME). The unique index therefore constitutes the business-key candidate, with ZD_EDITION_NAME participating in Release 12.2 to support editioning. There is no separate surrogate key column documented; the composite natural key serves as the primary identifier.

Common Use Cases and Queries

This table is typically queried to resolve the legislative name and input value name for a given context, or to enumerate all contexts belonging to a specific legislation. Typical reporting and configuration scenarios include validating that contexts are correctly mapped for a legislation being implemented, and joining the table to context-driven payroll data to present legislation names in user-friendly output.

  • Retrieving mappings for a legislation: SELECT context_id, legislation_name, input_value_name FROM pay_legislation_contexts WHERE legislation_code = :p_legislation_code;
  • Resolving a specific context: SELECT legislation_name, input_value_name FROM pay_legislation_contexts WHERE legislation_code = :p_code AND context_id = :p_context_id;
  • Reporting distinct legislations: SELECT DISTINCT legislation_code, legislation_name FROM pay_legislation_contexts ORDER BY legislation_code;

When querying in a Release 12.2 environment, analysts should be mindful of the ZD_EDITION_NAME column and, where appropriate, restrict results to the current edition using the standard editioning predicates available through the EBS patching infrastructure.

Related Objects

The metadata identifies this object as standalone, with no FK relationships documented beyond its own primary key. Related objects are therefore inferred from the shared payroll context and legislation model:

  • PAY_LEGISLATION_CONTEXTS_PK — the primary key constraint enforcing uniqueness on (LEGISLATION_CODE, CONTEXT_ID, ZD_EDITION_NAME).
  • FND_CONTEXT / context definition objects — supply the CONTEXT_ID domain referenced by this table.
  • PAY_LEGAL_ENTITIES — legislative entities joined via LEGISLATION_CODE for organization-level reporting.
  • HR_ORGANIZATION_UNITS / HR_ALL_ORGANIZATION_UNITS — organizations associated with a legislation for payroll processing.
  • PAY_INPUT_VALUES_F — input values referenced conceptually by INPUT_VALUE_NAME.
  • PAY_ELEMENT_TYPES_F — element definitions resolved by legislation context.
  • FND_LOOKUP_VALUES — lookup definitions that frequently echo legislation codes and names.