Search Results terminate_apl_asg_a

Overview

HR_ASSIGNMENT_BKD is the date-tracked (business key date) package body specification associated with the Oracle E-Business Suite Human Resources assignment API surface. It is owned by the APPS schema and is classified under the generic OTHER API classification in the ETRM 12.2.2 repository. In Oracle EBS 12.1.1 and 12.2.2, the HR_ASSIGNMENT family of packages, including the _BKD suffix variants, supports the algorithmic maintenance of employee assignment records, in particular the termination of assignments through the date-tracked (datetrack) framework that governs effective-dated HR records.

The package serves the termination use case specifically. When an assignment must end — for example through a termination, a transfer that closes the prior assignment, or an end-dating scenario — the application requires both a pre-processing ("before") step and a post-processing ("after") step so that validation, user hooks, and derived record updates occur in the correct order relative to the underlying datetrack operation. HR_ASSIGNMENT_BKD encapsulates the private (business key) implementation side of that flow.

Key Procedures and Functions

The ETRM metadata documents two procedures in this package:

• TERMINATE_APL_ASG_B — The "before" procedure in the termination sequence. It accepts the effective date, the assignment identifier, and the object version number. Its role is to perform the pre-processing actions required before the assignment is end-dated, including validation and any preparatory work that must occur prior to the datetrack write.
• TERMINATE_APL_ASG_A — The "after" procedure in the termination sequence. It accepts the same core parameters plus the resolved effective start date and effective end date of the datetracked record. It performs post-processing logic after the assignment termination has been applied, such as propagating dependent data updates and returning the resulting date-tracked effective dates.

The naming convention (_B for before, _A for after) is standard across Oracle HRMS date-tracked APIs and indicates that these routines are intended to be called in tandem rather than independently. The parameter lists shown in the specification are limited to identifiers and dates; no functional return values are exposed.

Tables Accessed

The ETRM metadata does not enumerate any tables accessed through APPS synonyms for this package. Consistent with the broader HR_ASSIGNMENT_BKD implementation, the package operates against the core HR assignment datetrack table, PER_ALL_ASSIGNMENTS_F, and its associated datetrack infrastructure. Because the BKD package manipulates effective-dated assignment rows, it relies on the standard HR date-track framework rather than performing direct DML against unrelated tables. Any legacy or dependent record updates are handled by the framework and by the corresponding public API wrapper that invokes this package.

Usage Notes

This package is referenced by one other package in the ETRM repository, which is typical for the _BKD layer: the public-facing API package (such as HR_ASSIGNMENT_API) calls the BKD procedures to execute the business-key termination logic. Direct invocation from forms, concurrent programs, or custom code is not the documented pattern. Oracle's supported integration path is through the public HR_ASSIGNMENT_API or the corresponding business process (for example, terminating an assignment or processing a termination in Oracle HRMS), which in turn invokes the date-tracked BKD procedures.

When extending or diagnosing termination behavior in EBS 12.1.1 or 12.2.2, this package should be treated as internal implementation. Customers should not call TERMINATE_APL_ASG_B or TERMINATE_APL_ASG_A directly, as doing so may bypass object version checking and datetrack validation enforced by the public API layer. The package is relevant primarily for troubleshooting termination flows, understanding the before/after hook sequence, and reviewing standard Oracle date-tracked processing order.