Search Results offer_apl_asg

Overview

APPS.HR_ASSIGNMENT_BK9 is a generated PL/SQL package body belonging to the Oracle E-Business Suite Human Resources (HRMS) API layer. It forms part of the HR Assignment API architecture, where the naming convention suffix BK designates a "before" hook or pre-processor stub that precedes the corresponding business logic package. The package exists to provide an obligation point in the assignment API chain so that customers and integrators can attach custom application logic (hooks) to the standard assignment update flow without modifying Oracle-owned code.

The business function addressed by the package centers on the offer_apl_asg operation — the assignment-side processing associated with offering or applying an assignment change, including status type modifications and effective-dated datetrack updates. Within EBS 12.1.1 and 12.2.2, such generated hook packages are produced automatically by the Oracle HRMS API Hook Pre-processor, as evidenced by the header comment referencing peasgapi.pkb and the generation timestamp. The package is owned by APPS and classified as OTHER in the ETRM documentation set.

Key Procedures and Functions

The package body exposes two documented procedures:

• OFFER_APL_ASG_A — The primary hook procedure for the offer/apply assignment operation. It accepts the effective date, datetrack update mode, assignment identifier, object version number, assignment status type identifier, change reason, and effective start/end dates. Its body establishes a commit unit via hr_api.return_commit_unit, conditionally delegates to the corresponding business logic procedure hr_assignment_be9.OFFER_APL_ASG_A when hr_api.call_app_hooks returns true, terminates the multi-message validation set, and validates the commit unit under the identifier 'OFFER_APL_ASG' with the 'AP' context.
• OFFER_APL_ASG_B — A companion hook procedure for the same operation. It accepts a reduced parameter set (effective date, datetrack update mode, assignment identifier, object version number, assignment status type, and change reason) and, as generated, contains only location tracing markers with no substantive processing logic. It is retained to preserve the hook signature expected by the API framework.

Tables Accessed

The ETRM metadata documents no direct table references through APPS synonyms for this package. This is consistent with its role as a thin hook wrapper: the procedures perform no SQL of their own, instead invoking hr_assignment_be9, which is the layer that performs the actual DML against the HR assignment and assignment status tables (for example, PER_ASSIGNMENTS_F and related datetracked entities). Any data modification is therefore attributable to the underlying business package, not to HR_ASSIGNMENT_BK9 itself.

Usage Notes

HR_ASSIGNMENT_BK9 is not intended to be called directly by end users. It is invoked internally by the HRMS assignment API chain when an assignment offer/apply operation is submitted — typically from the Assignment form in the Oracle HRMS responsibility or from concurrent programs and custom code that call the public assignment APIs. Because the package is listed as referenced by one other package, it participates in a layered call sequence where public API entries route through generated before-hooks of this kind.

Customers extending assignment behavior should place custom logic in the corresponding CUSTOM hook packages rather than editing this file, since it is regenerated by the HRMS API Hook Pre-processor during patching or upgrades. Any modification made directly to the Oracle-shipped body risks being overwritten, and the hr_api.call_app_hooks guard exists precisely to allow supported extension without altering base behavior.