Search Results pqp_configuration_modules




Overview
Explore in AI Chat

Overview

The PQP_CONFIGURATION_MODULES table resides in the HR schema and belongs to the PQP – Public Sector Payroll product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to keep track of the modules for which configuration values have been set up. In practice, this table acts as a registry or control list that identifies which functional modules participate in the PQP configuration framework, allowing the application to determine which configuration records are relevant for a given business group, legislation, and module combination.

The ETRM metadata classifies the object, heuristically derived from its foreign-key structure, as standalone. In Data Vault modeling terms this suggests the table behaves as an independent hub-like or reference construct rather than as a link or satellite; it does not appear to be a dependent child of another table through a documented foreign key. Because the table is owned by HR and carries an APPLICATION_ID, it also participates in the standard Oracle EBS application registration model, and its inclusion of ZD_EDITION_NAME indicates it is edition-enabled for the 12.2 online patching architecture.

Key Information Stored

The table documents thirteen columns, of which the following are the most significant:

  • MODULE_ID – Surrogate primary key, defined by the unique index PQP_CONFIGURATION_MODULES_PK. It uniquely identifies each configured module record.
  • ZD_EDITION_NAME – Edition identifier used by the 12.2 online patching framework. Combined with MODULE_ID, it forms the business-key candidate documented in the unique index PQP_CONFIGURATION_MODULES_PK (MODULE_ID, ZD_EDITION_NAME).
  • MODULE_NAME – Descriptive or internal name of the configuration module being tracked.
  • BUSINESS_GROUP_ID – Identifies the business group (operating unit / HR security group) to which the module configuration belongs.
  • LEGISLATION_CODE – Country or legislative context for the module configuration, relevant for public sector payroll localization.
  • APPLICATION_ID – References the Oracle EBS application that owns or consumes the module configuration.
  • DESCRIPTION – Free-text description of the module's purpose or scope.
  • OBJECT_VERSION_NUMBER – Optimistic locking column used by the Oracle Application Framework (OAF) and PL/SQL APIs to detect concurrent updates.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard who-columns recording the audit trail of the most recent modification.
  • CREATED_BY, CREATION_DATE – Standard who-columns recording record creation.

The surrogate key MODULE_ID should be distinguished from the composite business key of MODULE_ID and ZD_EDITION_NAME, which enforces edition uniqueness.

Common Use Cases and Queries

Typical use cases include identifying which modules are configured for a business group or legislation, auditing configuration completeness, and joining configuration detail tables back to this registry. Representative SQL patterns follow.

  • List configured modules for a business group: SELECT MODULE_ID, MODULE_NAME, LEGISLATION_CODE FROM HR.PQP_CONFIGURATION_MODULES WHERE BUSINESS_GROUP_ID = :p_bg_id;
  • Resolve the module registry for reporting: join PQP_CONFIGURATION_MODULES to configuration detail tables on MODULE_ID to enrich detail rows with module names and legislation context.
  • Edition-aware lookups in 12.2: SELECT * FROM HR.PQP_CONFIGURATION_MODULES WHERE ZD_EDITION_NAME = 'ORA$BASE'; to retrieve the run-edition records.
  • Audit recent changes: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to monitor configuration activity.

Reporting extracts commonly join to FND_APPLICATION via APPLICATION_ID to display the owning application name.

Related Objects

The documented relationship data classifies this object as standalone, so few hard foreign keys are recorded. The following objects are the most significant associated or dependent references:

  • PQP_CONFIGURATION_MODULES_PK – The primary/unique index enforcing MODULE_ID and ZD_EDITION_NAME uniqueness.
  • FND_APPLICATION – Referenced indirectly through APPLICATION_ID for application registration and name resolution.
  • HR business group / PER_BUSINESS_GROUPS – Linked through BUSINESS_GROUP_ID for organizational context.
  • FND_LEGAL_ENTITIES / legislation reference tables – Associated through LEGISLATION_CODE.
  • Other HR.PQP_CONFIGURATION_* detail tables – Dependent configuration tables that join on MODULE_ID.
  • FND_STANDARD_DATE / FND_WHO columns – Standard audit infrastructure supporting the who-columns.