Results for “hr_person_bk1”

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

Overview

HR_PERSON_BK1 is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the "BK" (Before/After) category of helper packages that Oracle's public APIs delegate to internally. In the Oracle HRMS architecture, public APIs such as HR_PERSON_API expose logical business operations, while the corresponding _BK1 package encapsulates the low-level row-level work — the pre-processing "before" logic and the post-processing "after" logic that bracket the main DML against the person record set. This separation allows Oracle to maintain a stable, documented public interface (HR_PERSON_API) while isolating internal implementation detail, version-specific logic, and row handler code inside the BK1 package. The package is classified as "OTHER" in the ETRM metadata because it is not itself a public API; it is a supporting component of the Person business object layer. Its status is VALID, and it depends only on the SYS schema's STANDARD package (the PL/SQL default package providing standard types and the standard exception handling constructs), confirming that it does not directly reference other application schemas at the package specification level. The package is referenced by exactly one other package object: HR_PERSON_API, and it is self-referencing, indicating recursive or internal invocation within the same unit.

Key Procedures and Functions

The ETRM documentation records two procedures in HR_PERSON_BK1, both following the standard Oracle API naming convention:

• UPDATE_PERSON_B — the "before" procedure invoked to perform validation or precondition processing immediately prior to the update of a person record. In the Oracle HRMS API pattern, the _B procedure typically carries out checks, defaulting, and setup steps that must succeed before the main update body executes.
• UPDATE_PERSON_A — the "after" procedure invoked after the main update has completed. The _A procedure typically handles post-update logic such as denormalization, dependent record maintenance, or additional processing driven by the changed person data.

No exported functions are documented, and parameter lists are intentionally omitted here because the ETRM metadata does not publish them; the procedures are described by purpose only, consistent with their role as internal handlers within the update flow.

Tables Accessed

The ETRM metadata for HR_PERSON_BK1 does not enumerate specific base tables referenced through APPS synonyms. The package operates on behalf of the Person business object, so its DML is logically targeted at the PER_ALL_PEOPLE_F entity and related person-level structures managed by the HR_PERSON_API update operation. Because the documented dependency list shows only SYS.STANDARD, any table access occurs indirectly, either through synonyms resolved at runtime in the APPS schema or through calls to other program units. The absence of explicit table references in the metadata indicates that table-level behavior must be confirmed by inspecting the package body rather than the published dependency report.

Usage Notes

HR_PERSON_BK1 is not intended for direct invocation by customer code. It is called internally by HR_PERSON_API when the public update person operation executes. Typical calling contexts include HRMS forms that submit person updates, PL/SQL programs and concurrent programs that call HR_PERSON_API.UPDATE_PERSON, and custom integrations that use the supported public API and thereby cause the BK1 procedures to run as part of the transaction. Developers customizing or debugging person-related behavior should reference HR_PERSON_API as the supported entry point; HR_PERSON_BK1 should be treated as an internal implementation detail whose contents may change across releases or patches. Any direct dependency on its procedures would be unsupported and could break after an upgrade or patch application.