Search Results terminate_apl_asg




Overview

APPS.HR_ASSIGNMENT_BKD is a generated Oracle HRMS API hook package body that belongs to the assignment business process layer of Oracle E-Business Suite. Its primary purpose is to serve as the intermediary between the public HRMS assignment API and any customer-defined business rules implemented through the Oracle HRMS API Hook Pre-processor. The source header (peasgapi.pkb 120.37.12020000.11, dated 2013/02/28) and the generation timestamp confirm that the body is regenerated automatically by the API Hook Pre-processor, meaning that developers should never modify it directly. The package is relevant to the process of terminating an applicant assignment, exposed through the procedures prefixed with TERMINATE_APL_ASG. Within the ETRM 12.2.2 metadata the object is classified as OTHER, indicating that it is a supporting API rather than a primary business-facing API.

Key Procedures and Functions

Two procedures are documented for this package body:

  • TERMINATE_APL_ASG_A — the main hook procedure for terminating an applicant assignment. It accepts the effective date, assignment identifier, object version number, and effective start and end dates. The procedure records the current commit unit, checks the hr_api.call_app_hooks flag, and conditionally invokes the corresponding logic in HR_ASSIGNMENT_BED. It then closes the validation set through hr_multi_message.end_validation_set and verifies the commit unit against the TERMINATE_APL_ASG operation under the AP product. Location tracing is performed at entry and exit using hr_utility.set_location.
  • TERMINATE_APL_ASG_B — a companion hook procedure intended for the post-processing (after) phase of the same termination operation. In the shipped version the body contains only entry and exit tracing calls, serving as a placeholder for customer extensions. The absence of a commit-unit check reflects its role as a purely hook-driven procedure.

Tables Accessed

The ETRM metadata for this object does not list any tables accessed directly through APPS synonyms. Consistent with the role of a hook package, HR_ASSIGNMENT_BKD does not perform DML against HR tables itself. Any reads or writes against PER_ALL_ASSIGNMENTS_F or related assignment entities are performed by the underlying business logic in HR_ASSIGNMENT_BED, which this body delegates to when the application hook flag is enabled. Custom business rules added through the hook framework may, however, access other tables, and such access would be attributed to the customer's hook package rather than to this generated object.

Usage Notes

HR_ASSIGNMENT_BKD is never invoked directly by end users or by custom code. It is called by the public HRMS assignment API when a termination of an applicant assignment is requested, typically from the Assignment or Applicant forms, or from concurrent programs and interfaces that terminate applicant placements. The package checks hr_api.call_app_hooks so that customer-defined hooks (implemented in the corresponding business-event hook, for example the HR_ASSIGNMENT_BUS or a customer-specific hook package) are executed only when the hook framework is enabled. Because the body is regenerated by the API Hook Pre-processor whenever the underlying API definition changes, any direct customization would be overwritten during patching or upgrade. The metadata records that this package is referenced by one other package, confirming its position as a dependent API layer rather than an entry point. Developers integrating with Oracle HRMS should target the public assignment API or the supported hook mechanism rather than calling TERMINATE_APL_ASG_A or TERMINATE_APL_ASG_B directly.