Search Results get_column_value

Overview

APPS.PAY_GB_RTI_P60 is a UK-specific Oracle Payroll package that supports the Real Time Information (RTI) P60 end-of-year reporting process required by HM Revenue & Customs. Its stated purpose, per the package header, is to fetch live payroll data and archive it for the RTI P60 process. The package was created on 29 December 2012 (version 115.0, bug 14759137) and subsequently extended in January 2013 (version 115.1) with the addition of the GET_COLUMN_VALUE function, which was introduced specifically to be consumed by the PYGBRTIP60OP.xml report definition. The package is declared AUTHID CURRENT_USER, meaning its unqualified references resolve under the privileges of the invoking schema rather than the defining schema. It is classified under ETRM as an OTHER API type, indicating it is not a seeded business API in the conventional sense but rather a supporting utility package for the RTI P60 archival and reporting flow.

Key Procedures and Functions

The ETRM metadata documents six callable units, excluding the package-level act_info_rec record type declaration:

• RANGE_CURSOR — Returns a cursor (or ref cursor) that defines the population of assignments and payroll data to be processed for the RTI P60 run, providing the driving row set for subsequent archival steps.
• RTI_FPS_ACTION_CREATION — Creates the payroll action records required for the RTI P60 process, writing into the action information and assignment action structures used by the payroll engine.
• ARCHINIT — Initialises the archival process, establishing the working context, parameters, and any temporary state required before data is written to the archive.
• ARCHIVE_CODE — Performs the core archival logic, moving or persisting the live RTI P60 data into its archived form. The act_info_rec record type (with assignment_id, person_id, effective_date, action_info_category, and thirty act_info columns) exists explicitly as a transit variable to pass column values into the archive API.
• DEINITIALIZATION_CODE — Cleans up the session state and any temporary artifacts created during ARCHINIT and the archival run, ensuring the process terminates cleanly.
• GET_COLUMN_VALUE — Added in version 115.1 to supply individual column values to the PYGBRTIP60OP.xml report. This is the object most commonly located through a "get_column_value" search in the context of this package, and it serves as the bridge between the archived RTI P60 data and the printed/electronic P60 output layout.

Tables Accessed

The package accesses a broad set of APPS synonyms covering payroll, HR, and archive infrastructure: PAY_DEFINED_BALANCES, PAY_BALANCE_DIMENSIONS, PAY_ACTION_INFORMATION, PAY_ASSIGNMENT_ACTIONS, PAY_ASSIGNMENT_ACTIONS_S, PAY_ALL_PAYROLLS_F, and PAY_ACTION_INTERLOCKS provide the balance, action, and payroll data that constitutes the P60 figures and their associated payroll events. HR_ASSIGNMENT_SETS, HR_ASSIGNMENT_SET_AMENDMENTS, HR_ORGANIZATION_INFORMATION, and HR_SOFT_CODING_KEYFLEX supply assignment grouping and organisational context for selecting and reporting employees. FF_USER_ENTITIES and FF_ARCHIVE_ITEMS support the FastFormula archive framework used to persist the extracted data, while FND_CONCURRENT_REQUESTS and FND_TERRITORIES_TL provide concurrent request context and territory/legislative reference data.

Usage Notes

PAY_GB_RTI_P60 is invoked as part of the UK RTI P60 end-of-year processing rather than as an interactive form-level API. It is typically driven by the concurrent program and report infrastructure associated with RTI, with GET_COLUMN_VALUE consumed directly by the PYGBRTIP60OP.xml report template to retrieve formatted column values at report runtime. Because ETRM records zero packages referencing it, it is best treated as a top-level, report-oriented utility rather than an integration API. Customisations should avoid altering its behaviour, and any extension should respect the AUTHID CURRENT_USER semantics and the act_info_rec contract used to pass values into the archive API.