Search Results hr_assignment_bk2




Overview
Explore in AI Chat

Overview

The APPS.HR_ASSIGNMENT_BK2 package is a private implementation package within the Oracle E-Business Suite Human Resources (HR) module. It is classified under the ETRM metadata as having an API classification of "OTHER," distinguishing it from the public, customer-callable APIs that Oracle publishes for external integration. The package resides in the APPS schema and carries a status of VALID in both Oracle EBS 12.1.1 and 12.2.2 environments.

In the Oracle HR architecture, packages suffixed with "_BK" (and its numbered variants such as "_BK2") conventionally represent the "body kernel" or internal business logic layer. This layer is deliberately separated from the public API surface. Rather than being invoked directly by customers or third-party integrations, the _BK packages are called by the public wrapper packages—in this case, HR_ASSIGNMENT_API—which apply validation, security, and business rule enforcement before delegating execution to the kernel.

The business function served by HR_ASSIGNMENT_BK2 is the actual manipulation of employee assignment records: the core database operations that create, maintain, and update the assignment data underpinning an employee's placement, organization, job, position, and payroll linkage. Because assignment data is central to HRMS, the kernel package forms part of the critical write path for one of the most heavily used data structures in the application.

Key Procedures and Functions

The documented procedures exposed by this package are:

  • UPDATE_EMP_ASG_B — the "Before" procedure. It is the pre-processing step invoked before the core update of an employee assignment record. Its role is to perform tasks that must precede the actual DML against the assignment tables, such as initializing internal state, capturing the pre-change values of the record, or preparing derived columns required for the update. The "B" suffix indicates it is called at the beginning of the update lifecycle.
  • UPDATE_EMP_ASG_A — the "After" procedure. It is executed following the main update DML. Its purpose covers post-processing activities: propagating the change to dependent or denormalized structures, triggering secondary operations, or performing consistency checks that require the assignment row to already reflect its new values. The "A" suffix indicates it runs after the update has occurred.

The _B/_A split is a standard Oracle HRMS pattern, allowing atomic wrapper logic (typically supplied by the public HR_ASSIGNMENT_API) to bracket the kernel update with consistent pre- and post-processing steps. This design preserves integrity without exposing the internal mechanics to callers.

Tables Accessed

The ETRM metadata for this object does not enumerate specific base tables accessed via APPS synonyms; the documented dependency information is limited to platform references (SYS, STANDARD) rather than application tables. Based on the package's identity as the update kernel for employee assignments and its relationship to HR_ASSIGNMENT_API, its operations center on the core HRMS assignment entities—principally the PER_ALL_ASSIGNMENTS_F table and its associated date-tracked structures—which hold the effective-dated assignment records for employees. The procedures described (pre- and post-update) read and write these records because they implement the state transitions that define an assignment's history. Because the assignment record drives downstream records (such as payroll, costing, and element entries), the kernel's changes propagate consequences across dependent HRMS data. Consult the "_show dependent code" view in the ETRM documentation for a definitive, instance-specific table list, as the metadata provided here does not enumerate them.

Usage Notes

HR_ASSIGNMENT_BK2 is not intended for direct invocation by customers, forms, or concurrent programs. It occupies an internal layer of the HRMS API stack. The typical invocation path is indirect: Oracle HR forms (Assignment, Employee, and related maintenance screens), public concurrent processes, and supported integration flows call the public package HR_ASSIGNMENT_API; that wrapper then calls the kernel procedures in this package to perform the actual update work. The documented dependency shows a one-way relationship—HR_ASSIGNMENT_BK2 is referenced by APPS.HR_ASSIGNMENT_API and by itself, but references only platform units (SYS.STANDARD).

Custom code should always target HR_ASSIGNMENT_API, never the _BK2 kernel, to preserve Oracle's validation and business-rule enforcement. Because kernel signatures and behavior are undocumented, internal, and subject to change during patching or upgrades, direct calls risk upgrade breakage. The package should be treated as a read-only reference when diagnosing assignment update behavior, and any modification attempts are unsupported.