Search Results hr_assignment_extra_info_bk3

Overview

HR_ASSIGNMENT_EXTRA_INFO_BK3 is a generated PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. Its header comment (peaeiapi.pkb 115.4) and the reference to the Oracle HRMS API Hook Pre-processor identify it as part of the HRMS API hook framework that surrounds the Assignment Extra Information business object. The suffix "BK3" denotes a backward-compatibility hook package: Oracle generates these wrappers so that customer extensions, forms, and legacy custom code continue to call predictable entry points while the underlying base API (PEAEIAPI, the Assignment Extra Information API) evolves across releases.

The package does not itself contain business logic. Its body is deliberately skeletal. Each procedure opens with a call to HR_UTILITY.SET_LOCATION on entry and a matching call on exit, producing the instrumentation that appears in HRMS debug traces and in the FND logging output. This makes the package a tracing and dispatch shell rather than a data-manipulation unit, consistent with its ETRM classification of OTHER rather than a public or private API.

Key Procedures and Functions

ETRM documents two procedures, both with the same two IN parameters: P_ASSIGNMENT_EXTRA_INFO_ID (NUMBER) and P_OBJECT_VERSION_NUMBER (NUMBER). These identify a single Assignment Extra Information row and support optimistic locking on delete.

• DELETE_ASSIGNMENT_EXTRA_INFO_A — the "before" (A) hook fired prior to the deletion of an Assignment Extra Information record. Its body contains only SET_LOCATION tracing calls at line markers 10 and 20.
• DELETE_ASSIGNMENT_EXTRA_INFO_B — the "after" (B) hook fired following the deletion of the same record. It mirrors the A version and likewise contains only SET_LOCATION tracing.

Neither procedure implements a WHERE clause, DML, or error handling in the shipped source; they are extension seams. Customers are expected to copy or wrap these hooks to insert their own validation or post-delete processing without modifying Oracle's base API code.

Tables Accessed

The ETRM metadata records no tables referenced directly through APPS synonyms by this package body. This is consistent with the source: because the procedures perform no SELECT, INSERT, UPDATE, or DELETE, there is no static SQL dependency. The row targeted by the two parameters is the one maintained in the Assignment Extra Information base table (PA_ASSIGNMENT_EXTRA_INFO) by the parent API; the hook package only observes the event and does not touch the table itself. The HR_UTILITY package provides the debug instrumentation, not a data table access.

Usage Notes

These procedures are not invoked directly by end users. They are called by the Oracle HRMS API Hook Pre-processor framework at the appropriate points inside the Assignment Extra Information delete flow, which in turn is driven by Oracle Forms (Assignment Extra Information window) or by concurrent and custom PL/SQL programs that call the PEAEIAPI delete routine. ETRM records one inbound reference from another package, confirming that a peer HRMS object invokes HR_ASSIGNMENT_EXTRA_INFO_BK3 rather than the reverse.

Because the hook bodies are empty apart from tracing, production impact is limited to debug overhead when HR_UTILITY logging is enabled. The presence of the package in 12.1.1 and 12.2.2 is identical in behaviour; the file header version 115.4 has been shipped unchanged for many releases. Developers extending Assignment Extra Information deletion behaviour should treat BK3 as the supported extension point rather than altering the base API, and should preserve the SET_LOCATION calls to retain traceability. Any customisations wrapped around these hooks must be re-applied after patching, since Oracle regeneration of the hook package will overwrite the generated body.