Search Results hr_assignment_bk8




Overview
Explore in AI Chat

Overview

HR_ASSIGNMENT_BK8 is a private PL/SQL package in the APPS schema that forms part of the Oracle Human Resources assignment API infrastructure in Oracle E-Business Suite 12.1.1 and 12.2.2. It is not a standalone business component exposed to end users; rather, it is a supporting "BK" (backing) package whose procedures are invoked by the higher-level HR_ASSIGNMENT_API wrapper. Its specific purpose is to handle the creation of secondary assignment application records, that is, the rows that link a worker to an application or assignment context when a secondary assignment is defined. In the Oracle HRMS data model, secondary assignments extend primary assignments, and their apl (application) linkages must be created with the same date-tracked, business-group-aware logic used across HR APIs. HR_ASSIGNMENT_BK8 encapsulates that logic so the public API can call a single, well-tested entry point.

The documented ETRM metadata classifies the package with an API classification of OTHER and confirms it is VALID in the target instance. The package body references the SYS-owned STANDARD package, which supplies the standard PL/SQL constructs used for cursor and error handling. The package is referenced by one other package, HR_ASSIGNMENT_API, and references itself through the dependent-code mechanism.

Key Procedures and Functions

The ETRM documentation records two public procedures:

  • CREATE_SECONDARY_APL_ASG_B — the "B" procedure is the initial, business-logic phase of the secondary assignment application creation. It performs the core validation and derivation work: checking the incoming assignment context, enforcing the HR business-group and date-track rules, and preparing the database changes required to establish the secondary assignment linkage.
  • CREATE_SECONDARY_APL_ASG_A — the "A" procedure is the corresponding final phase. It commits or finalises the work initiated by the "B" procedure, completing the insert/update of the secondary assignment application record and returning the outcome to the calling API.

This B/A two-phase naming convention is standard throughout Oracle HRMS APIs. The "_B" procedure runs before the main DML and the "_A" procedure runs after, allowing the caller to control transaction boundaries and to interleave additional processing. The precise parameter lists are not reproduced in the ETRM excerpt and should be confirmed from the deployed package specification. Neither procedure is documented as returning a value in the available metadata.

Tables Accessed

The ETRM excerpt for HR_ASSIGNMENT_BK8 does not enumerate specific base tables accessed via APPS synonyms. The package operates on the application/assignment linkage data that underpins secondary assignments, and the documented dependency on the SYS.STANDARD package confirms standard PL/SQL runtime constructs. Because this is a backing package, the tables it touches are those of the HR assignment and application data model; the authoritative list can be obtained from the package body source or from the database dictionary. No table-level facts beyond the SYS.STANDARD dependency are asserted in the supplied metadata.

Usage Notes

HR_ASSIGNMENT_BK8 is intended for internal use by HR_ASSIGNMENT_API. The documented dependency list shows HR_ASSIGNMENT_API referencing HR_ASSIGNMENT_BK8, and no other package referencing it besides itself. Developers should therefore invoke HR_ASSIGNMENT_API rather than calling HR_ASSIGNMENT_BK8 procedures directly, since the higher-level API manages validation, locking, and error propagation in the supported sequence.

Typical invocation paths include Oracle Forms-based assignment maintenance in the HRMS professional user interface, concurrent programs that mass-create or update assignments, and custom PL/SQL integrations that call the public HR_ASSIGNMENT_API. Because this package is not designated as a public API and is classified as OTHER, direct calls are discouraged and may be unsupported across patches or upgrades from 12.1.1 to 12.2.2. Customisations should always target HR_ASSIGNMENT_API and treat HR_ASSIGNMENT_BK8 as an implementation detail.