Search Results fps_header_proc




Overview
Explore in AI Chat

Overview

PAY_GB_RTI_FPS_OUTPUT is a United Kingdom–specific Oracle Payroll package that supports Real Time Information (RTI) reporting to HM Revenue & Customs. Its principal business function is to retrieve archived data produced by an RTI Full Payment Submission (FPS) process, transform that data into an XML structure, and merge the resulting XML with an associated EText template file to produce the statutory RTI FPS output file. In Oracle EBS 12.1.1 and 12.2.2, this package forms part of the payroll legislative compliance layer required for UK employers, enabling payroll administrators to generate the outbound submission files mandated under the RTI regime.

The package is defined with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than its owner, and it resides under the APPS schema. Its header carries the revision identifier pygbrtifpsop.pkh 120.0.12020000.1, dated 09-Mar-2013, and its creation history traces to 05-Apr-2012 via changelog entry 115.0 under bug reference 13918120.

Key Procedures and Functions

The package exposes five documented procedures, each aligned with a stage of the concurrent processing model used by Oracle Payroll archive and report generation.

  • RANGE_CURSOR — Defines the SQL statement used to obtain the range of assignment actions or records to be processed for a given payroll action. This supports chunk-based parallel processing of the RTI FPS output.
  • ACTION_CREATION — Creates the action records required for each processing chunk, establishing the units of work that the concurrent manager will execute.
  • FPS_HEADER_PROC — Generates the header portion of the FPS output, drawing on the transfer payroll action identifier retrieved through the package's header cursor.
  • FPS_EMPLOYEE_PROC — Produces the employee-level FPS data, iterating assignment actions selected against the transfer payroll action identifier.
  • END_OF_FILE — Handles end-of-file processing and finalises the merged output.

The package also declares three private cursors — fps_header, fps_employee, and fps_asg_actions — which retrieve parameter values such as TRANSFER_PAYROLL_ACTION_ID and TRANSFER_ACT_ID through PAY_MAGTAPE_GENERIC.GET_PARAMETER_VALUE. The fps_employee cursor selects assignment action and assignment identifiers from PAY_ASSIGNMENT_ACTIONS.

Tables Accessed

The package reads from several core Oracle Payroll tables via APPS synonyms:

  • PAY_ASSIGNMENT_ACTIONS and PAY_ASSIGNMENT_ACTIONS_S — supply assignment action and assignment identifiers used to build employee-level FPS records.
  • PAY_ACTION_INFORMATION — stores parameter values associated with the payroll action, including transfer identifiers.
  • PAY_PAYROLL_ACTIONS — provides context on the payroll action driving the RTI run.
  • PER_ALL_ASSIGNMENTS_F — supplies assignment-level details for the employees included in the submission.
  • DUAL — used by the header cursors to emit constant parameter tags.

Usage Notes

PAY_GB_RTI_FPS_OUTPUT is not intended for direct invocation by end users. It is typically called by the Oracle Payroll concurrent program infrastructure that generates the RTI FPS file, functioning as the output-generation stage after an RTI FPS archive process has populated the required data. Because the package performs XML transformation and EText merging, it depends on a correctly configured EText template for the FPS layout. No other packages reference it, as indicated by the ETRM metadata, so it should be treated as a terminal output component rather than a reusable API. Any modification, particularly to the cursors or the merge logic, risks producing non-compliant RTI files and should be tested against HMRC validation before deployment.