Results for “pa_hr_agreements”

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

Overview

The PL/SQL package body APPS.PA_HR_AGREEMENTS is a utility package within the Oracle E-Business Suite Projects (PA) module. Its principal business function is to enforce referential integrity between Oracle HRMS (Human Resources) entities — specifically persons and jobs — and project agreement records stored in the Projects application. When a user attempts to remove, deactivate, or otherwise alter an HR person or job record, the system must first verify that no project agreement continues to reference that entity. PA_HR_AGREEMENTS supplies the validation logic that HR forms and related components invoke to perform this check before permitting the change.

A secondary business purpose is internationalization and user feedback: the package returns a message name (such as PA_HR_PER_AGREEMENT) that the calling form translates and presents to the user, explaining precisely why the deletion or modification is blocked. This keeps HR data consistent with downstream Projects commitments such as project agreements, which may be owned by or associated with a person.

Key Procedures and Functions

• CHECK_PERSON_REFERENCE — Determines whether a given person is referenced by any project agreement. It declares a cursor that queries PA_AGREEMENTS_ALL for rows whose OWNED_BY_PERSON_ID matches the supplied person identifier. If at least one such row is found, the procedure raises an internal reference_exists exception, sets the output Reference_Exist flag to 'Y', and populates Error_Message with the token PA_HR_PER_AGREEMENT. When no reference exists, it returns Reference_Exist as 'N' and clears the error message. Unexpected errors are re-raised to the caller.
• CHECK_JOB_REFERENCE — Provides the corresponding validation for a job identifier. In the documented release, this procedure is a stub: it unconditionally sets Reference_Exist to 'N' and Error_Message to NULL, effectively reporting that no job-level agreement reference exists. This indicates that job-based referential checking is either not enforced or is handled elsewhere in the application.

Tables Accessed

• PA_AGREEMENTS_ALL — The only table accessed by this package, referenced through an APPS synonym. The key column used by CHECK_PERSON_REFERENCE is OWNED_BY_PERSON_ID, which links an agreement to the HR person who owns it. The query structure (SELECT NULL ... WHERE OWNED_BY_PERSON_ID = ...) confirms that the package performs a read-only existence check and never inserts, updates, or deletes agreement data. This read pattern is deliberate: the package acts purely as an integrity gatekeeper, leaving all data maintenance to other Projects APIs and forms.

Usage Notes

This package is typically invoked from Oracle HRMS person and assignment forms, or from custom validation routines, at the point where a user attempts to delete or modify a person or job that may be tied to a project agreement. Because Oracle EBS provides no direct user-facing entry point for this package, it is almost always called programmatically, with the caller passing an entity identifier and inspecting the returned Reference_Exist and Error_Message outputs to decide whether to block the operation or display a translated error.

The package is referenced by two other database packages, indicating its role as a shared validation service rather than a standalone utility. When extending or customizing Projects-to-HRMS validation logic, developers should preserve the existing output-parameter contract, as calling packages depend on the exact 'Y'/'N' values and message tokens returned. The check_job_reference stub should be re-validated against current requirements if job-level agreement enforcement is ever introduced. Given that the package body carries a 2005 header revision, it should be treated as stable, legacy inherited code, and any modification should be regression-tested against the two dependent packages and the calling HR forms.