Search Results rti_fps_action_creation




Overview
Explore in AI Chat

Overview

PAY_GB_RTI_FPS_ARCHIVE is a UK-specific Oracle Payroll package that supports Real Time Information (RTI) reporting under HM Revenue & Customs (HMRC) requirements. Its documented purpose is to fetch live payroll data and archive it for the RTI Full Payment Submission (FPS) process. RTI obliges UK employers to report payroll payments to HMRC electronically on or before each payment date; the FPS is the primary submission carrying employee-level pay, tax, and National Insurance details. Before an FPS submission is generated or transmitted, the relevant data must be captured in a stable form so that it is not altered by subsequent payroll processing, corrections, or retroactive changes.

This package addresses that requirement: it isolates and stores the data set destined for submission in an archive structure, providing a reproducible snapshot that supports audit, reconciliation, and resubmission. Because it is an APPS-owned PL/SQL package declared with AUTHID CURRENT_USER, it executes with the privileges of the invoking schema. The header history records the creation of the package in December 2012, coinciding with the RTI programme's introduction in UK payroll legislation.

Key Procedures and Functions

The package exposes five documented procedures and functions, each of which performs a distinct role in the archival lifecycle.

  • RANGE_CURSOR — establishes the cursor or driving query that selects the population of payroll records to be processed within the archive run, thereby scoping which assignment actions and related data are eligible for archiving.
  • RTI_FPS_ACTION_CREATION — creates the action entries required for the RTI FPS process. This is the procedure associated with the user's search term rti_fps_action_creation and represents the point at which the archive operation is initiated: action records, populated from the act_info_rec record type and the action_info_table collection declared in the package specification, are passed to the archive API for processing.
  • ARCHINIT — initialises the archive run, performing the preparatory setup needed before archival activities commence.
  • ARCHIVE_CODE — contains the core archival logic that writes the fetched live data into the archive destination.
  • DEINITIALIZATION_CODE — performs the orderly wind-down of the archive run, releasing resources and finalising the operation.

The package specification defines a record type, act_info_rec, which carries assignment, person, effective date, action information category, and up to thirty generic act_info attributes, along with a table type indexed by BINARY_INTEGER to channel this data into the archive API.

Tables Accessed

The package operates across a broad set of payroll and HR tables referenced through APPS synonyms. Core payroll tables include PAY_ASSIGNMENT_ACTIONS and PAY_ASSIGNMENT_ACTIONS_S, which record the payroll actions performed for each assignment, and PAY_ACTION_INFORMATION, which holds the information lines attached to those actions. PAY_ACTION_CLASSIFICATIONS and PAY_ACTION_INTERLOCKS govern how actions are classified and synchronised. PAY_ALL_PAYROLLS_F and PAY_DEFINED_BALANCES provide payroll definition and balance context, while PAY_BALANCE_TYPES and PAY_BALANCE_DIMENSIONS describe the balance structures being reported. Fast Formula detail is drawn from FF_FUNCTIONS. HR tables supply the worker and organisational context: HR_ORGANIZATION_INFORMATION, HR_SOFT_CODING_KEYFLEX, HR_DOCUMENT_TYPES, and HR_DOCUMENT_EXTRA_INFO. FND_CONCURRENT_REQUESTS is referenced to reflect the concurrent request in which the process executes.

Usage Notes

The package is typically invoked from the concurrent program associated with the RTI FPS process, executed within a payroll run context in Oracle EBS 12.1.1 or 12.2.2. It is intended to be called through standard Oracle Payroll flows rather than directly from a form. The FND_CONCURRENT_REQUESTS reference confirms that processing is request-driven, and the sequencing of RANGE_CURSOR, RTI_FPS_ACTION_CREATION, ARCHINIT, ARCHIVE_CODE, and DEINITIALIZATION_CODE suggests that the procedures are called in order within a single archive cycle. Because it is referenced by two other packages, it forms part of a wider RTI dependency chain. Customisations should avoid direct invocation and instead rely on the documented RTI FPS programs.