Search Results final_process_cwk_asg_b

Overview

APPS.HR_ASSIGNMENT_BKH is a PL/SQL package in Oracle E-Business Suite 12.1.1 and 12.2.2 that belongs to the Oracle Human Resources (HR) product family. Its name follows the standard Oracle EBS API conventions: the _BKH suffix identifies the package as the pre-processing (before) and post-processing (after) layer associated with a business API, while the corresponding _BH, _B, and _A packages implement the actual wrapper, pre-process, and post-process logic. In this case the underlying business function relates to the "Final Process for a Contingent Worker Assignment," which is the HR process that terminates or completes a contingent worker (CWK) assignment and updates the associated assignment records with a final process date. The package therefore provides the extension points that customers can customize so that site-specific logic runs before and after the core final-process operation, without modifying Oracle's shipped code. Although the user search term "bhn jobs" does not correspond to a documented object in this metadata, the _BKH suffix is the standard Oracle naming pattern for such hooks, and the contents confirm that this is the before/after hook package for the assignment final-processing API.

Key Procedures and Functions

The ETRM metadata documents two procedures within the package:

• FINAL_PROCESS_CWK_ASG_B — the "before" (pre-process) procedure. Its name follows the Oracle _B convention and is invoked prior to the core final-process logic. It accepts the assignment identifier, the object version number, and the final process date as inputs. Because the _B variant is defined with IN parameters only, it represents the entry point where validation or preparatory logic can be added before the assignment is finalized.
• FINAL_PROCESS_CWK_ASG_A — the "after" (post-process) procedure. It receives the same three input parameters as the _B procedure, plus the effective start date, effective end date, and three warning flags: p_org_now_no_manager_warning, p_asg_future_changes_warning, and p_entries_changed_warning. These outputs allow the core logic to communicate back to the caller whether organizational, future-dated, or entry-level conditions were detected during processing. As the after-process hook, this procedure is where site-specific post-processing, auditing, or notification logic is typically placed.

No additional procedures or functions are documented for this package in the ETRM 12.2.2 metadata.

Tables Accessed

The ETRM extract does not list any tables referenced via APPS synonyms for this package. The package's procedures operate exclusively on parameters passed by the calling business API rather than querying or updating tables directly within the hook layer itself. This is consistent with the design of _BKH hook packages, which are intended to be thin extension points: the actual DML against HR assignment tables (such as PER_ALL_ASSIGNMENTS_F and related entities) is performed by the corresponding business API, while the hook package provides the interface through which custom code can read or influence the values passed in and out. Implementers adding custom logic to these hooks would reference the HR tables as needed within their own code, but that behavior is not part of the documented package metadata.

Usage Notes

This package is not intended to be called directly by end users or by custom applications. It is invoked automatically by the Oracle HR business API stack when a contingent worker assignment is finalized. The documented fact that the package is "referenced by 1 other package" confirms this dependency: the caller is the associated business API package that drives the final-process operation, which in turn calls FINAL_PROCESS_CWK_ASG_B before the core processing and FINAL_PROCESS_CWK_ASG_A afterward.

Typical usage scenarios include:

• Extending standard contingent worker termination processing through Oracle's supported customization mechanism, rather than modifying seeded code.
• Adding validations, defaulting, or supplementary updates in the before hook, and post-processing actions such as notifications, audit logging, or downstream integrations in the after hook.
• Diagnosing final-process behavior when warning flags such as p_org_now_no_manager_warning or p_asg_future_changes_warning are raised during the finalization of a contingent worker assignment.

Because the package is classified as OTHER rather than as a public API in ETRM, it should be treated as an internal Oracle object. Custom code should not call its procedures directly; instead, customizations belong inside the hook bodies, preserving upgrade safety across EBS 12.1.1 and 12.2.2.