Search Results convert_to_cwk

Overview

HR_CONTINGENT_WORKER_BK2 is an Oracle HRMS API Hook Pre-Processor package body owned by the APPS schema. It is auto-generated, as indicated by the header comment "Code generated by the Oracle HRMS API Hook Pre-processor," and was created on 2012/11/27. The package belongs to the Oracle E-Business Suite HRMS contingent worker API layer and provides the "BK2" (before-process, second-level) hook implementation for the Convert to Contingent Worker business transaction. In ETRM classification it is registered as an OTHER API, and it operates alongside the corresponding BE2 (business entity) package, HR_CONTINGENT_WORKER_BE2, which performs the substantive business logic.

The functional purpose of this package is to expose the CONVERT_TO_CWK business event through the standard HRMS API hook framework, allowing Oracle or customer-defined logic to be invoked before the core conversion of a person to a contingent worker is executed. This is part of the multi-tiered API architecture in Oracle EBS 12.1.1 and 12.2.2, where hook packages (BK, BK2, AK, etc.) interleave with the business entity layer to allow extensibility without modifying seeded code.

Key Procedures and Functions

The package documents two public procedures:

• CONVERT_TO_CWK_A — The primary hook procedure invoked during the convert-to-contingent-worker flow. It sets a location marker for tracing, captures the current commit unit via HR_API.RETURN_COMMIT_UNIT, and conditionally calls HR_CONTINGENT_WORKER_BE2.CONVERT_TO_CWK_A when HR_API.CALL_APP_HOOKS returns true. It subsequently calls HR_MULTI_MESSAGE.END_VALIDATION_SET and HR_API.VALIDATE_COMMIT_UNIT, passing the transaction identifier 'CONVERT_TO_CWK' and the API type code 'AP'. The procedure accepts parameters covering the effective date, person, object version numbers, NPW number, projected placement end, person type, datetrack update mode, person effective dates, and assignment-related identifiers (assignment ID, assignment object version number, and assignment sequence). The "_A" suffix denotes it as the primary (first) hook entry point in the generated chain.
• CONVERT_TO_CWK_B — The secondary hook procedure, following the same generated pattern as CONVERT_TO_CWK_A. It represents the second hook slot in the pre-processor chain and is invoked in sequence with the "_A" variant to allow layered before-process customizations. Like CONVERT_TO_CWK_A, it ultimately delegates to the BE2 layer for the core business operation.

Tables Accessed

The excerpted source for HR_CONTINGENT_WORKER_BK2 does not directly reference any application tables. All data manipulation is delegated through the call to HR_CONTINGENT_WORKER_BE2.CONVERT_TO_CWK_A. The ETRM metadata lists no tables referenced via APPS synonyms for this hook package. The underlying conversion logic in the business entity layer will write to HR person, assignment, and contingent worker tables (such as PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and related contingent worker entities), but that access occurs in HR_CONTINGENT_WORKER_BE2, not in this BK2 hook package. The only database interactions visible in the hook are calls to HR_API, HR_MULTI_MESSAGE, and HR_UTILITY, which are PL/SQL utility packages rather than application data tables.

Usage Notes

HR_CONTINGENT_WORKER_BK2 is not typically invoked directly by end users, forms, or concurrent programs. It is called by the HRMS API hook pre-processor framework when the Convert to Contingent Worker transaction is executed through the supported API entry points, such as HR_CONTINGENT_WORKER_API.CONVERT_TO_CWK. The BK2 layer sits in the "before-process" chain and is designed for extension: customers can add custom logic in the corresponding hook slots without altering seeded packages.

Because it is generated code with a fixed "generated ship" header, it should not be modified manually. The ETRM metadata notes that it is referenced by one other package, reflecting its position in the API call chain. When troubleshooting convert_to_cwk behavior in Oracle EBS 12.1.1 or 12.2.2, developers should verify whether HR_API.CALL_APP_HOOKS is enabled, since the BE2 call in CONVERT_TO_CWK_A is gated on that condition; if hooks are disabled, this BK2 procedure performs only the location tracing and validation-set/commit-unit housekeeping before returning.