Results for “au_check_paye_ni_flags”

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

Overview

PER_PER_AGGR is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 release codelines. Its documented API classification is "OTHER," indicating that it is not part of the standard, externally-published HRMS application programming interface set, but rather an internally scoped aggregation package. The package header carries the source identifier pegbperhi.pkh, whose "hi" suffix conventionally denotes a header-only or internal helper artifact within the PER (Human Resources) product family. The package is declared AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the invoking schema rather than the definer, a property consistent with an internal utility that relies on the caller's access to the underlying HR tables.

The business function served by PER_PER_AGGR is the validation and maintenance of statutory payroll-related flags attached to a person record — specifically the PAYE (Pay As You Earn) and National Insurance (NI) indicators used by the UK and Irish payroll legislation. These flags govern whether an employee is subject to income tax withholding and social insurance contributions, and therefore they must be kept consistent with the person's employment and legislative data. The naming of the two documented procedures, prefixed "AI" and "AU," reflects the traditional Oracle HRMS convention of separating insert-time and update-time logic into distinct entry points, so that flag derivation occurs once on creation and is re-evaluated only when relevant attributes change.

Key Procedures and Functions

The ETRM documentation records two procedures in the package specification; both are annotated with a reference to Bug 8370225, the change request that introduced or modified them.

• AI_CHECK_PAYE_NI_FLAGS — The insert-time entry point. It accepts a person identifier and an effective date, and is responsible for establishing the initial PAYE and NI flag values for that person as of the supplied effective date. As an "AI" (after-insert) routine, it is intended to run following the creation of a person row so that the derived legislative flags are populated consistently with the newly created record.
• AU_CHECK_PAYE_NI_FLAGS — The update-time counterpart. In addition to the person identifier and effective date, it receives a datetrack mode and returns the current employee flag as an OUT parameter. The datetrack mode allows the procedure to honour Oracle HRMS date-tracked (effective-dated) update semantics — correction, update, insert, or end-date — so that flag validation remains consistent with the historical versioning of the person record. The outbound employee flag permits the calling process to inspect or propagate the resulting employment status.

No additional procedures or functions are documented in the metadata, and the parameter signatures should not be extended beyond what the specification above establishes.

Tables Accessed

The only table documented as referenced through APPS synonyms is PER_ALL_PEOPLE_F, the effective-dated core person table in Oracle HRMS. This is the expected access path: the PAYE and NI flags are attributes of the person record, and both procedures require the person's existing effective-dated rows in order to determine whether the flags are present, correct, or in need of refresh. Because the table is date-tracked, the p_effective_date parameter passed to each procedure is used to isolate the correct version of the person row for evaluation. Reads and writes against this table are the package's primary data interaction; no other application tables are documented for this object.

Usage Notes

PER_PER_AGGR is an internal aggregation package rather than a public API. The ETRM metadata records that it is referenced by two other packages, which is the principal mechanism by which it is invoked: those dependent packages call AI_CHECK_PAYE_NI_FLAGS and AU_CHECK_PAYE_NI_FLAGS from within their own person-maintenance flows, typically in the context of hire, rehire, or employee-record correction processing where statutory flags must be synchronized. Because the insert variant is tied to record creation and the update variant receives a date-track mode, the routines are best understood as lifecycle hooks rather than standalone services.

Typical invocation therefore occurs from server-side PL/SQL — datetracked DML logic, business process wrappers, or payroll-related validation packages — and not directly from a form or concurrent program. Customers maintaining customizations on the person record, or writing interfaces that insert into PER_ALL_PEOPLE_F via supported APIs, should be aware that this package exists and that the "AI"/"AU" naming signals the expected call ordering. Direct invocation of these procedures outside the owning HRMS flow is not supported, and any custom code that calls them must supply a valid effective date that corresponds to an existing person row version. The implementation is sourced from pegbperhi.pkh, a header-only internal artifact, which further confirms that the package is intended for consumption by Oracle's own HRMS code rather than by external integrators.