Results for “pqp_gb_tp_ext_process”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PQP_GB_TP_EXT_PROCESS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the UK (GB) pension auto-enrolment extract processing within the Oracle Advanced Benefits and Payroll legislative framework. Its name reflects its role as a third-party (TP) extract processor, generating and managing the extraction of pension-related employee and payroll data intended for transmission to pension providers or regulatory bodies. The package operates alongside the PQP_GB_T1_PENSION_EXTRACTS object, forming part of the UK-specific pension extract infrastructure. In EBS 12.1.1 and 12.2.2 it is documented as VALID, confirming that it compiles cleanly against the shipped dependencies. Its classification is OTHER, indicating it is an internal utility rather than a public, supported API.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions. Four are diagnostic helpers — DEBUG, DEBUG_ENTER, DEBUG_EXIT, and DEBUG_OTHERS — providing tracing and exception logging used throughout the extract process. GET_EXT_RSLT_FRM_REQ retrieves extract result records associated with a given concurrent request, while GET_EXT_RSLT_COUNT returns the count of such results. CREATE_EXTRACT_RESULTS creates the extract result rows, and COPY_EXTRACT_RESULTS duplicates existing extract result sets. COPY_EXTRACT_PROCESS handles copying at the level of the extract process itself. SET_CROSS_PERSON_RECORDS manages records that span multiple persons, addressing scenarios where extract data must be correlated across employees. TPA_EXTRACT_PROCESS is the principal driver, orchestrating the third-party extract workflow. No parameter lists are published in the metadata; the procedures are described by purpose only.

Tables Accessed

The package reads and writes a defined set of application tables through APPS synonyms. Extract result data is persisted in BEN_EXT_RSLT, with detail and error rows in BEN_EXT_RSLT_DTL and BEN_EXT_RSLT_ERR respectively. Extract definitions and records are held in BEN_EXT_DFN, BEN_EXT_RCD, and BEN_EXT_RCD_IN_FILE. Concurrent request context is obtained from FND_CONCURRENT_REQUESTS, and FND_NEW_MESSAGES and FND_LOOKUPS supply messaging and lookup values. Employee and location data come from PER_ALL_PEOPLE_F, HR_LOCATIONS_ALL, and HR_LOCATION_EXTRA_INFO. Flexible user-defined extraction structures are supported via PAY_USER_TABLES, PAY_USER_COLUMNS, PAY_USER_COLUMN_INSTANCES_F, and PAY_USER_ROWS_F. Supporting utilities include HR_UTILITY and PQP_GB_T1_PENSION_EXTRACTS.

Usage Notes

PQP_GB_TP_EXT_PROCESS is typically invoked indirectly through the UK pension extract concurrent programs rather than called directly by end users. A concurrent request is submitted, the extract definitions are evaluated, and TPA_EXTRACT_PROCESS drives creation of results, which are then queried by request ID using GET_EXT_RSLT_FRM_REQ and GET_EXT_RSLT_COUNT. The dependency listing shows the package referencing itself, indicating internal recursion or shared private routines. The metadata records no other packages referencing it, so it should be treated as a private implementation object. Customizations should avoid direct calls; extending behaviour is safer through the supported extract configuration tables (BEN_EXT_DFN, BEN_EXT_RCD, and the PAY_USER_* structures) rather than modifying package code, which would jeopardise the VALID status required for patching and support.