Search Results update_emp_asg

Overview

APPS.HR_ASSIGNMENT_BK2 is a generated API hook package body that belongs to the Oracle HRMS (Human Resources Management System) assignment APIs delivered with Oracle E-Business Suite. The _BK2 suffix identifies it as a backward-compatibility or bridge hook layer produced by the Oracle HRMS API Hook Pre-processor, as confirmed by the comment "Code generated by the Oracle HRMS API Hook Pre-processor" in the package header. Its principal business function is to support the update of employee assignment records through the business logic that underlies the standard HR assignment maintenance flows. Assignment data represents the relationship between a person and an organization, carrying attributes such as supervisor, assignment status, probation end date, working hours, payroll linkage, and the descriptive flexfield attribute columns used to capture customer-specific information.

The package is classified as OTHER in the documented API metadata and is not intended for direct customer invocation as a business API; it exists to expose controlled update entry points that the HRMS runtime can call when an assignment change is committed.

Key Procedures and Functions

The documented package exposes two procedures:

• UPDATE_EMP_ASG_A — The primary assignment update procedure. Its signature accepts an effective date, a datetrack update mode, the assignment identifier, and the object version number used for optimistic locking, together with a large set of assignment attributes covering supervisor, assignment number, change reason, assignment status type, comments, probation end date, default code combination, frequency, internal address line, manager flag, normal hours, performance and salary review periods, projected assignment end, set of books, source type, normal start and finish times, bargaining unit, labour union membership, and hourly/salaried status. It also accepts the assignment descriptive flexfield context (P_ASS_ATTRIBUTE_CATEGORY) and attribute columns P_ASS_ATTRIBUTE1 through P_ASS_ATTRIBUTE18. The _A suffix denotes the "after" or "actual" processing variant within the generated hook pattern.
• UPDATE_EMP_ASG_B — The corresponding "before" variant in the same hook pair. Together these two procedures bracket the core assignment update so that customer or product extensions can be injected before and after the standard validation and write logic without modifying the seeded HRMS code.

The paired naming convention _B / _A is characteristic of the generated hook framework and indicates that these routines are called by the standard assignment update process rather than being standalone public APIs.

Tables Accessed

The ETRM metadata for this object does not enumerate the base tables referenced through APPS synonyms. Consistent with the HRMS assignment update APIs, the update logic operates against the core assignment entity table, HR_ASSIGNMENT, with associated lookups such as assignment status types and the descriptive flexfield structure that backs the ASS_ATTRIBUTE columns. Changes are datetrack-enabled, meaning the procedures respect the effective dating mode supplied through P_DATETRACK_UPDATE_MODE and maintain the correction, update, insert, and future-change date-track rows managed by the HRMS date-tracked tables. The object version number parameter supports optimistic locking against the assignment row.

Usage Notes

This package is typically invoked indirectly. The standard entry point for assignment maintenance remains HR_ASSIGNMENT_API; the HR_ASSIGNMENT_BK2 hook procedures are called from within the API execution path as part of the pre- and post-processing sequence generated by the API Hook Pre-processor. In practice the package is reached from HRMS forms such as the Assignment and Termination forms, from concurrent programs performing mass assignment updates, and from custom PL/SQL that calls the standard assignment API rather than the hook procedures directly.

Because the code is auto-generated, it should not be manually modified: any upgrade or patch that regenerates the hook layer will overwrite custom edits. Customers requiring extensions should implement their logic through the supported hook mechanisms or by registering custom business logic against the assignment APIs. The header version string (peasgapi.pkb 120.20.12010000.4) indicates the file is shipped with the 12.1.1 code line and remains present in 12.2.2, so behaviour is consistent across both releases. The object is referenced by one other package, reflecting its role as a dependent component in the HRMS API call chain rather than a top-level interface.