Search Results get_header_system_element

Overview

PACKAGE APPS.PQP_GB_TP_PENSION_EXTRACTS is a United Kingdom–specific Oracle HRMS Payroll (PQP) package that supports the statutory Teachers' Pension (TP) pension extract process for Great Britain. Its primary responsibility is to assemble, validate, and format the data items required for periodic and event-driven pension reporting to the Teachers' Pension scheme administrator. The package encapsulates the business rules that translate Oracle E-Business Suite payroll and assignment data into the terminology, categorisation, and reference-number conventions demanded by the TP4 return and related extract formats.

The package header, source version pqpgbtp4.pkh 120.1.12010000.2, establishes a set of global variables that govern extract execution: the legislation code is fixed to GB, an effective date drives date-effective lookups, and globals such as the LEA number, establishment number, originator's title, and header system element are resolved before record processing begins. Flags including g_multi_lea_exist and g_warn_no_location control warning generation, for example when multiple Local Education Authorities share a labour establishment number or when no location exists for a given LEA. The package also carries a parent request ID to associate threaded concurrent processing with its originating run.

Key Procedures and Functions

The package exposes 34 documented procedures and functions. The user-searched routine, GET_TRANSLATE_ASG_EMP_CAT_CODE, translates an assignment's employment category into the code the pension extract expects, ensuring the value reported matches TP scheme definitions rather than internal lookup values. GET_TP4_EMPLOYMENT_CATEGORY similarly derives the TP4 reporting category for an assignment.

Several functions resolve statutory identifiers and descriptive header values: GET_LEA_NUMBER, GET_ESTB_NUMBER, GET_ORIGINATORS_TITLE, and GET_HEADER_SYSTEM_ELEMENT. Teacher-specific eligibility logic is handled by CHK_TP4_IS_TEACHER_NEW_STARTER, while GET_TP4_START_DATE and GET_TP4_SALARY_SCALE extract the relevant start date and salary scale for the return. GET_DFEE_REFERENCE_NUMBER supplies the Department for Education and Employment reference.

Flexfield and value-set resolution is provided through GET_DFLEX_VALUE, GET_KFLEX_VALUE, and GET_FLEX_SEGMENT_VALUE, which retrieve the appropriate descriptive flexfield, key flexfield, and segment values. Operational control procedures include SET_EXTRACT_GLOBALS, SET_RUN_EFFECTIVE_DATES, SET_PAY_PROC_EVENTS_TO_PROCESS, GET_EXTRACT_UDT_INFO, and GET_TOTAL_NUMBER_DATA_RECORDS, which together initialise the run context, determine the payroll events and date ranges in scope, and report record counts. DEBUG and DEBUG_ENTER provide diagnostic tracing.

Tables Accessed

The package draws on Oracle HRMS and payroll base tables through APPS synonyms. Assignment and location data come from PER_ALL_ASSIGNMENTS_F, HR_LOCATIONS_ALL, and HR_LOCATION_EXTRA_INFO, with organisation attributes from HR_ORGANIZATION_INFORMATION. Payroll element configuration is read from PAY_ELEMENT_TYPES_F, PAY_ELEMENT_TYPE_EXTRA_INFO, PAY_ELEMENT_LINKS_F, and PAY_ELEMENT_ENTRIES_F, with PAY_GRADE_RULES_F supplying grade rules and PAY_EVENT_GROUPS defining the payroll events processed. User-defined extract criteria are resolved via PAY_USER_TABLES and PAY_USER_COLUMN_INSTANCES_F. Extract output and results are written to or read from BEN_EXT_RCD, BEN_EXT_RSLT, and BEN_EXT_RSLT_DTL.

Usage Notes

The package is normally invoked indirectly through the GB Teachers' Pension extract concurrent program or the associated extract-processing framework rather than called directly by end users. It supports threaded processing, using the parent request ID to link child threads to the originating request. Customisations should call the documented functions only for read purposes, as the globals are designed to be initialised by SET_EXTRACT_GLOBALS before any dependent routine executes. Because the package is referenced by three other packages, changes to its public signatures can have downstream impact, and regression testing of the full extract chain is advisable after any modification.