Search Results pqp_configuration_types_u1

Overview

PQP_CONFIGURATION_TYPES is a configuration metadata table owned by the HR schema within the PQP (Public Sector Payroll) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The table serves as the registry of information types — referred to as configuration types — that belong to each functional module recorded in PQP_CONFIGURATION_MODULES. Each row defines exactly one configuration type, and the corresponding data values entered against that type are persisted in PQP_CONFIGURATION_VALUES. In this sense the table acts as a dictionary layer that gives semantic meaning to the configuration values captured for a module.

The object is recorded as VALID and is described in the ETRM 12.2.2 physical schema as having 19 columns. Its heuristic Data Vault classification, mined from the foreign key structure, is standalone. From a modeling perspective this suggests the entity functions as an independent reference or lookup construct rather than as a hub, link, or satellite participating in an explicit FK-driven integration network. The classification is heuristic and should be treated as a design suggestion rather than a declared constraint.

Key Information Stored

The table’s most significant columns fall into three groups: identifying keys, type attributes, and standard EBS audit/control columns.

• MODULE_ID — Identifies the parent module from PQP_CONFIGURATION_MODULES to which the configuration type belongs.
• LEGISLATION_CODE — Scopes the configuration type to a specific legislative context, allowing the same module to present different configuration types per country or legislation.
• CONFIGURATION_TYPE — The business name of the information type being defined.
• DESCRIPTION — Human-readable text explaining the purpose of the configuration type.
• ACTIVE_INACTIVE_FLAG — Controls whether the configuration type is currently available for use.
• MULTIPLE_OCCURENCES_FLAG — Indicates whether more than one value may be stored against this type in PQP_CONFIGURATION_VALUES.
• PROTECTED_FLAG — Marks the type as protected from modification or deletion.
• TOTAL_UNIQUE_COLUMNS — Metadata describing the number of unique columns applicable to the type’s value set.
• ZD_EDITION_NAME — Editioning column supporting EBS 12.2 online patching and edition-based redefinition.

The documented primary key, PQP_CONFIGURATION_TYPES_U1, is the composite (MODULE_ID, LEGISLATION_CODE, CONFIGURATION_TYPE). A unique index, PQP_CONFIGURATION_TYPES_UI1 (MODULE_ID, CONFIGURATION_TYPE, LEGISLATION_CODE, ZD_EDITION_NAME), provides the edition-aware business-key candidate. Remaining columns are standard EBS concurrency and audit attributes: OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage revolves around discovering which configuration types exist for a module and legislation, verifying whether a type permits multiple values, and joining to the value table for reporting.

• Enumerate active configuration types for a module:
  SELECT configuration_type, description FROM hr.pqp_configuration_types WHERE module_id = :mod AND legislation_code = :leg AND active_inactive_flag = 'Y';
• Identify types permitting multiple occurrences:
  SELECT configuration_type FROM hr.pqp_configuration_types WHERE multiple_occurences_flag = 'Y';
• Report configuration types and their stored values:
  SELECT t.configuration_type, v.* FROM hr.pqp_configuration_types t, hr.pqp_configuration_values v WHERE t.module_id = v.module_id AND t.legislation_code = v.legislation_code AND t.configuration_type = v.configuration_type;
• Audit changes to configuration definitions using LAST_UPDATE_DATE, LAST_UPDATED_BY, and PROGRAM_ID.

Related Objects

• PQP_CONFIGURATION_MODULES — Parent module registry; join on MODULE_ID.
• PQP_CONFIGURATION_VALUES — Stores the actual values for each configuration type; join on MODULE_ID, LEGISLATION_CODE, and CONFIGURATION_TYPE.
• FND_APPLICATION / FND_PROGRAM — Reference PROGRAM_APPLICATION_ID and PROGRAM_ID for concurrent program context.
• HR_ALL_ORGANIZATION_UNITS / legislative reference tables — Context for LEGISLATION_CODE values.
• FND_LOOKUPS — Frequently supplies valid values for flag and type attributes.