Search Results accept_apl_asg

Overview

GHR_ASSIGNMENT_API is a PL/SQL package body owned by the APPS schema that forms part of the Oracle Human Resources (GHR) family of APIs in Oracle E-Business Suite. Its principal responsibility is to serve as a public wrapper around the core HR assignment API, exposing functionality for accepting an assignment that has been placed in an applicant or applicant-type status and transitioning it to a standard employee assignment state. In practice, this package supports the business process of converting or finalising an applicant assignment so that it becomes an active, usable assignment record within Oracle HRMS.

The package is classified as an API, meaning it is intended for programmatic invocation by forms, other APIs, concurrent programs, or custom code rather than for direct end-user execution. The version header embedded in the source (ghasgapi.pkb 120.0) reflects the standard Oracle EBS patch lineage that applies to both the 12.1.1 and 12.2.2 release levels. Notably, the ETRM metadata records no inbound dependencies from other packages, indicating that GHR_ASSIGNMENT_API is a leaf-level or terminal wrapper rather than a shared utility consumed broadly across the application.

Key Procedures and Functions

The ETRM documentation lists a single documented procedure for this package: ACCEPT_APL_ASG.

• ACCEPT_APL_ASG — Accepts an applicant assignment and drives the datetracked transition of that assignment into its accepted state. The procedure accepts a validate-only flag, an effective date, a datetrack update mode, and the target assignment identifier, and returns an object version number together with effective start and end dates for the resulting record. It also allows an assignment status type and a change reason to be supplied, defaulting to the standard HR API sentinel values when omitted. Internally, the routine takes a savepoint when running in validation-only mode so that trial executions can be rolled back cleanly, initialises a local object version number, sets session context variables via GHR_SESSION, and then delegates the substantive work to HR_ASSIGNMENT_API.ACCEPT_APL_ASG. This delegation pattern means GHR_ASSIGNMENT_API contributes GHR-specific session setup and validation behaviour on top of the core HR logic rather than reimplementing it.

Tables Accessed

The ETRM metadata for this object does not enumerate any directly referenced tables or APPS synonyms. The package does, however, visibly operate against the PER_ASSIGNMENTS_F table, since its local variable l_object_version_number is anchored to per_assignments_f.object_version_number%type. Because the declaration is anchored rather than explicitly joined, the underlying DML is performed by the delegated call to HR_ASSIGNMENT_API.ACCEPT_APL_ASG. PER_ASSIGNMENTS_F stores the datetracked assignment records for employees and applicants, and the object version number is the concurrency-control token that must be passed in and returned on any datetracked update. Callers should therefore treat this package as an indirect writer to PER_ASSIGNMENTS_F through the core HR assignment API.

Usage Notes

GHR_ASSIGNMENT_API.ACCEPT_APL_ASG is typically invoked in three contexts. First, from Oracle HRMS forms that present applicant assignment data and provide an accept action, where the form passes the assignment identifier and current object version number. Second, from other APIs or PL/SQL routines performing applicant-to-employee conversion during a hire or rehire flow. Third, from custom code and concurrent programs that mass-process applicant assignments, in which case the validate-only mode is useful for pre-checking without committing changes. Callers must supply a valid effective date and datetrack update mode, must pass the current object version number and retain the returned value for any subsequent update to the same row, and should handle the HR API exceptions raised on validation failure. Because the procedure updates session context before delegation, it should be called within a controlled session where applicant processing context is expected, and any enclosing transaction should be aware that savepoints are used internally.