Search Results activate_apl_asg_b

Overview

The APPS.HR_ASSIGNMENT_BKC package is a Business Key Compatibility (BKC) layer routine within the Oracle E-Business Suite Human Resources (HR) module. Its designation as a BKC package indicates that it provides backward-compatible entry points that shield dependent code from changes in the underlying business logic, particularly the assignment API family (HR_ASSIGNMENT_API). In Oracle EBS 12.1.1 and 12.2.2, the BKC layer maintains stable callable signatures so that legacy forms, concurrent programs, and third-party extensions continue to function after core API refactoring.

The specific business function addressed here is the activation of an applicant assignment. When a candidate is hired or an applicant record is converted into an active employee assignment, the assignment must be transitioned to a valid status. This package encapsulates the pre-processing and post-processing logic required to perform that status transition against the assignment record while preserving the datetrack history of the underlying HR tables. The $Header line (peasgapi.pkh, version 120.11) confirms it belongs to the assignment API generation set.

Key Procedures and Functions

The package exposes two documented procedures, following the standard Oracle API "B/A" (before/after) pattern:

• activate_apl_asg_b — The "before" procedure. It executes validation and prep logic prior to the actual activation of the applicant assignment. It accepts the effective date, datetrack update mode, assignment identifier, object version number, assignment status type identifier, and change reason, and is invoked before the core activation logic runs so that business rules and datetrack constraints can be enforced up front.
• activate_apl_asg_a — The "after" procedure. It runs once the assignment activation has been applied, and additionally returns the effective start and end dates that resulted from the datetrack operation. This allows callers to reconcile the record's effective period after the status change.

Both procedures mirror the corresponding entry points in the main HR_ASSIGNMENT_API and are intended to be called in sequence as part of an atomic activation transaction. No standalone function is documented for this package.

Tables Accessed

The ETRM metadata for this object does not enumerate specific base tables referenced through APPS synonyms. Functionally, a BKC wrapper of this nature operates against the core HR assignment and applicant assignment tables — namely PER_ALL_ASSIGNMENTS_F (the datetracked assignment record), PER_ASSIGNMENT_STATUS_TYPES (resolving the status type identifier to a valid status), and related applicant/hire staging structures. The procedures write the new assignment status and adjust the effective start/end dates on the datetracked assignment row, while the "before" procedure performs read-oriented validation against those same structures. Any table access is performed via APPS synonyms under the standard EBS naming and grants model.

Usage Notes

This package is not intended to be invoked directly by end users. It is typically called in the following situations:

• As a lower-level dependency of the HR assignment API stack, invoked automatically when a hire or applicant-conversion transaction activates an assignment.
• By Oracle Forms or OA Framework pages within the HR and iRecruitment products that manage applicant and assignment status transitions.
• By concurrent programs responsible for mass hire or assignment maintenance processing.
• By custom PL/SQL extensions that must activate assignments with backward-compatible behavior across 12.1.1 and 12.2.2.

The ETRM metadata records that this package is referenced by one other package, confirming it is a supporting dependency rather than a top-level entry point. Developers should always supply a valid object version number and perform the call within a properly datetracked transaction, since the "after" procedure returns the resulting effective dates used for downstream reconciliation. Because it is an OTHER-classified API and not a documented public interface, customizations relying on it should be validated against Oracle's support policy for each release.