Search Results pqp_utilities




Overview
Explore in AI Chat

Overview

PQP_UTILITIES is a shared PL/SQL utility package body owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Payroll (PAY) and Advanced Benefits / Payroll process family. It is an internal, non-API classified object — that is, it is not a public interface intended for direct customer invocation, but rather a foundational helper library consumed by the payroll and element-configuration layer. Its primary business function is to centralize the low-level data retrieval and formatting logic that other payroll packages need: reading configuration values, resolving descriptive flexfield and segment metadata, decoding element-type and extra-element information, translating lookup codes, formatting dates and numbers, and emitting debug trace output.

In ETRM 12.2.2 the package exposes 46 documented procedures and functions. It is referenced by 44 other packages and itself depends on a broad set of foundation and payroll objects. Notably, the metadata records that PQP_UTILITIES is not referenced by any database object and only references itself recursively, confirming its role as a leaf-level utility rather than a business-rule engine.

Key Procedures and Functions

  • GET_CONFIG_TYPE_VALUES — Retrieves the configured values associated with a PQP configuration type, providing the runtime parameterization used by payroll processing.
  • GET_COL_VALUE — Resolves and returns the value of a specified database column, used for dynamic, metadata-driven data access.
  • GET_DATA_TYPE — Determines the datatype of a referenced column or value so callers can apply correct conversion and comparison logic.
  • GET_DDF_VALUE / GET_DF_VALUE — Return descriptive flexfield values and flexfield attribute values respectively, supporting context-sensitive element information.
  • GET_SEGMENT_NAME — Returns the name of a key flexfield segment, used when constructing segment-qualified references.
  • PQP_GET_CONCAT_VALUE — Builds a concatenated value from component parts, commonly for composing derived element or identifier strings.
  • PQP_GET_EXTRA_ELEMENT_MULT — Returns multiplicity information for extra element entries.
  • PQP_GET_EXTRA_ELEMENT_INFO and _DET — Retrieve extra element information, with the _DET variant supplying the detailed record set.
  • PQP_GET_ELEMENT_EXTRA_INFO and _DET — Return extra information attributes associated with an element, again with a detailed form.
  • PQP_GET_ELE_TYPE_EXTRA_INFO_ID / PQP_GET_ELEMENT_TYPE_ID — Resolve surrogate identifiers for element-type extra information and element types.
  • PQP_GB_GET_TABLE_VALUE / PQP_GB_GET_TABLE_VALUE_ID — Global/date-tracked table value lookups used to resolve effective-dated values and their identifiers.
  • DEBUG, DEBUG_ENTER, DEBUG_EXIT, DEBUG_OTHERS — A complete debug tracing framework: entry/exit markers, general debug output, and an OTHERS exception handler that logs error context.

Tables Accessed

The package reads and writes across several functional domains. Configuration and setup data come from PQP_CONFIGURATION_VALUES, PQP_CONFIGURATION_TYPES, PAY_ELEMENT_TYPES_F, PAY_ELEMENT_TYPE_INFO_TYPES, PAY_EVENT_GROUPS and PAY_EVENT_UPDATES. Application-flexfield metadata is obtained from FND_COLUMNS, FND_DESCRIPTIVE_FLEXS, FND_TABLES, and FF_COMPILED_INFO_F / FF_FDI_USAGES_F, which the package uses to interpret compiled flexfield structures. User-defined element and table structures are accessed through PAY_USER_COLUMNS, PAY_USER_COLUMN_INSTANCES_F, PAY_USER_ROWS_F and PAY_USER_TABLES. Date-tracked and event data are read from PAY_DATETRACKED_EVENTS and PAY_DATED_TABLES. Messages and lookups are resolved via FND_NEW_MESSAGES, FND_MESSAGE and FND_LOOKUP_VALUES_VL. Element entries are read from PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_SET_MEMBERS, PAY_ELEMENT_TYPE_EXTRA_INFO, PAY_EVENT_GROUP_USAGES and PAY_PROCESS_EVENTS. Utility calls are made to DBMS_UTILITY, FND_DATE, FND_NUMBER, HR_API and HR_UTILITY.

Usage Notes

PQP_UTILITIES is invoked indirectly rather than directly. Because it is referenced by 44 other packages, it is most commonly reached during payroll element setup, element-type validation, extra-information resolution, and date-tracked value processing triggered from Oracle Payroll forms and concurrent programs. Its debug procedures are used when diagnostics are enabled to trace execution flow and capture exception context. The package should not be treated as a public API: customizations referencing PQP_UTILITIES directly risk breakage across patch levels, and Oracle does not guarantee its internal signatures. Where the documented procedures are needed in custom code, the appropriate supported APIs (for example HR_API wrappers) should be evaluated first. The behavior is consistent across EBS 12.1.1 and 12.2.2, though any patch that changes underlying flexfield or configuration table structures can affect dependent callers.