Search Results assignment_validations




Overview

The APPS.PAY_GB_RTI_FPS_VALIDATE_13 package is a validation component within the Oracle E-Business Suite UK Payroll legislative subsystem that supports Real Time Information (RTI) reporting to HM Revenue & Customs. RTI requires employers to submit payroll data to HMRC on or before each payment, and the Full Payment Submission (FPS) is the primary vehicle for that reporting. This package performs the field-level and record-level validation logic that must pass before an FPS submission can be archived and transmitted. In the ETRM classification it is recorded as an OTHER-owned PL/SQL package under the APPS schema, with status VALID in both 12.1.1 and 12.2.2 environments.

The package operates in close partnership with PAY_GB_RTI_FPS_ARCHIVE. ETRM shows a bidirectional dependency: PAY_GB_RTI_FPS_VALIDATE_13 references PAY_GB_RTI_FPS_ARCHIVE, and PAY_GB_RTI_FPS_ARCHIVE references PAY_GB_RTI_FPS_VALIDATE_13. This reciprocal relationship indicates that the archive package drives the validation routine and consumes its results when constructing the persisted FPS payload.

Key Procedures and Functions

Ten documented procedures are exposed by this package. Their names delineate distinct validation domains:

  • HEADER_VALIDATIONS — Validates the FPS submission header, covering employer and scheme identification data required for every submission.
  • PERSON_ADDRESS_VALIDATIONS and PERSON_ADDR_VALIDATIONS_AGGR — Validate individual address records and the aggregated address dataset; RTI demands accurate address data for each employee reported.
  • ASSIGNMENT_VALIDATIONS and ASSIGNMENT_VALIDATIONS_AGGR — Validate assignment-level payroll attributes and their aggregate form, ensuring employee/assignment relationships conform to RTI expectations.
  • NI_VALIDATIONS — Validates National Insurance number data, a mandatory RTI field.
  • FOOTER_VALIDATIONS — Validates the FPS footer, covering submission totals and counts that HMRC cross-checks.
  • ECON_VALIDATE — Performs economic or employer-consistency validation across the submission.
  • VALIDATE_INPUT — Acts as an input-level gate, confirming that required driving parameters and dataset structures are present before deeper validation proceeds.
  • DATE_VALIDATE — Validates date fields, including payment dates and reporting period boundaries.

No parameter lists are documented in ETRM, so callers should derive signatures from the installed source when integrating.

Tables Accessed

The package reads foundational HR and Payroll tables through APPS synonyms. Person and address validation draws on PER_ALL_PEOPLE_F and PER_ADDRESSES. Assignment validation uses PER_ALL_ASSIGNMENTS_F and PAY_ASSIGNMENT_ACTIONS. Payroll context is supplied by PAY_PAYROLL_ACTIONS, while PAY_MESSAGE_LINES and PAY_MESSAGE_LINES_S supply the message-line records that carry RTI submission detail. HR_ORGANIZATION_INFORMATION provides organisation-level attributes, such as employer and scheme identification used in header validation. Collectively these tables give the package the person, assignment, address, payroll action, and organisational data needed to prove an FPS submission against HMRC’s schema.

Usage Notes

PAY_GB_RTI_FPS_VALIDATE_13 is not typically invoked directly by end users. It is called programmatically by PAY_GB_RTI_FPS_ARCHIVE during the FPS archival cycle, and ETRM records that the package is referenced by exactly one other package. Practically, this means the validation routines execute as an internal step when the RTI FPS archive process runs, either from the Submit RTI Full Payment Submission flow or from the GB RTI concurrent programs shipped with UK Payroll. Because the package is owned by APPS and marked VALID, site-specific customisations should avoid modifying it directly lest Oracle patching overwrite changes. Custom code that needs equivalent validation should call the package rather than duplicating logic, and callers should inspect the ETRM dependency list before upgrades to confirm the interface remains intact.