Results for “pay_gb_rep”

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

Overview

PAY_GB_REP is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM (E-Business Suite Technical Reference Manual) taxonomy as OTHER. The package name and its documented procedures identify it as a United Kingdom (GB) localization reporting utility within the Oracle Payroll module. Its role is to generate statutory reports required by United Kingdom payroll legislation, specifically reports dealing with arrears notifications to the National Insurance (NI) authorities and the reporting of issued P45 forms for active assignments.

Because the object is a PACKAGE rather than a standalone report or concurrent program, PAY_GB_REP encapsulates the PL/SQL logic that queries Oracle Payroll and Oracle Human Resources base tables, assembles the report output rows, and returns them to the calling layer. The ETRM record confirms the package status is VALID and that it references only SYS.STANDARD at the compilation level, indicating that all business-table access is performed through APPS synonyms rather than through direct schema-qualified references.

Key Procedures and Functions

The ETRM metadata documents two procedures/functions within PAY_GB_REP:

• NI_ARREARS_REPORT — Produces the National Insurance arrears report for GB payrolls. This report supports the statutory obligation to notify HM Revenue & Customs of National Insurance contributions that have fallen into arrears, typically as a result of retroactive payroll adjustments, late processing, or corrected contribution calculations.
• P45_ISSUED_ACTIVE_ASG_REPORT — Produces a report of P45 forms issued against assignments that remain active. Under UK payroll practice a P45 is normally issued on cessation of employment, so the issuance of a P45 for an assignment still recorded as active indicates a data discrepancy or a leaver that was not terminated correctly. This report is used to detect and reconcile those exceptions.

As is standard for ETRM object-level documentation, no parameter signatures are published. Procedure invocation therefore requires inspection of the package specification in the target environment or reference to Oracle Support documentation.

Tables Accessed

PAY_GB_REP accesses the following tables through APPS synonyms:

• PAY_PAYROLL_ACTIONS and PAY_ASSIGNMENT_ACTIONS — the core payroll run and assignment-level action records used to identify the payroll periods and assignments in scope for each report.
• PAY_ACTION_INTERLOCKS — the interlock records that associate payroll actions with the assignment actions and other processing steps, used here to trace the actions relevant to NI contributions.
• PAY_ALL_PAYROLLS_F — the payroll definition table, providing the payroll name and legislative parameters for the GB payrolls being reported on.
• PER_ALL_ASSIGNMENTS_F — the dated assignment records, used to determine assignment status and effective dates for both reports.
• PER_ALL_PEOPLE_F — the person records supplying employee identification details required on the NI arrears and P45 outputs.
• PER_ASSIGNMENT_STATUS_TYPES — the assignment status lookup, used by P45_ISSUED_ACTIVE_ASG_REPORT to identify assignments that are still active at the time a P45 was issued.
• PER_PERSON_TYPES — the person type definitions, used to filter or classify the population included in the reports.

Usage Notes

PAY_GB_REP is a report-support package. It is not exposed as a form-level API and is not designed to be called by customer-written PL/SQL. In a standard Oracle Payroll GB implementation it is invoked by the concurrent program framework when the associated UK statutory reports — the NI arrears report and the P45 issued for active assignment report — are submitted from the Submit Requests window or from a payroll responsibility menu. The ETRM dependency data records that PAY_GB_REP is referenced by no other packages, which confirms it sits at the top of its own call stack rather than being a shared utility.

Because the package queries _F (date-tracked) tables, results depend on the effective date supplied by the concurrent program at run time. When troubleshooting missing or inconsistent report output in release 12.1.1 or 12.2.2, verify that the assignment and payroll action records exist for the reported effective date and that the payroll carries the correct GB legislation. Direct execution of the packaged procedures is not supported, and any modification should be treated as an upgrade risk. Oracle's standard recommendation applies: patch and clone the file system carefully, since the package body may be regenerated by application of payroll legislative patches.