Search Results get_user_column_name




Overview

APPS.PQP_GB_CPX_EXTRACT_FUNCTIONS is a United Kingdom (GB) payroll extract utility package used by Oracle E-Business Suite Payroll and Oracle HRMS to assemble the pension and National Insurance (NI) data required for statutory financial reporting. The package name reflects its role: it supplies the extraction "functions" consumed by the Compensation and Pension Extract (CPX) process, the mechanism by which Oracle Payroll produces formatted outbound data files for pension providers, HM Revenue & Customs (HMRC) submissions, and other third-party interfaces.

The package operates with AUTHID CURRENT_USER, so it executes under the privileges of the invoking schema and inherits the caller's security context. It is fixed to GB legislation through the global g_legislation_code constant of 'GB' and relies heavily on a set of package-level globals—business group, effective date, extract type, and extract user-defined table (UDT) name—established once per run. The unit is primarily a helper library: it exposes the low-level lookups that higher-level extraction logic uses to resolve element entries, balances, input values, and UDT column definitions into the values written to the extract file.

Key Procedures and Functions

The package documents 63 procedures and functions. The principal entries include:

Parameter lists are intentionally not reproduced here; callers should confirm exact signatures against the deployed package specification.

Tables Accessed

The package reads and writes through APPS synonyms, including:

Usage Notes

PQP_GB_CPX_EXTRACT_FUNCTIONS is referenced by zero other packages in the ETRM metadata, indicating that it is invoked directly by the GB pension/CPX concurrent program or by custom extract wrappers rather than forming part of a shared API stack. It is not a public processing API; it is a component of the delivered GB payroll extract solution and is executed at extract run time, after the extract definition and UDT are selected. Customisations typically call individual functions to obtain specific values—most commonly GET_USER_COLUMN_NAME, GET_BALANCE_VALUE, and GET_ELE_ENTRY_VALUE—from within a bespoke extract formula or PL/SQL hook. Because behaviour depends on the package globals being populated, callers must ensure SET_EXTRACT_GLOBALS (or the equivalent initialisation path) has run before any getter is invoked. The package is classified as OTHER and is not supported for direct modification; extensions should be built against the documented functions only, with signatures verified against the target 12.1.1 or 12.2.2 instance, as the file header reflects a 2010 build (pqpgbcpx.pkh 120.8).