Search Results hr_assignment_extra_info_bk1




Overview
Explore in AI Chat

Overview

The APPS.HR_ASSIGNMENT_EXTRA_INFO_BK1 package is a private implementation detail of the Oracle E-Business Suite Human Resources (HR) module, residing in the APPS schema. Its name follows the standard Oracle naming convention for API "backing" packages: the _BK1 suffix denotes a supporting/backing unit that carries the physical implementation logic for a corresponding public API. In this case, the public interface is HR_ASSIGNMENT_EXTRA_INFO_API, which exposed the business functions of creating, updating, and deleting "extra information" (EIT — Extra Information Types) attached to assignments.

Extra Information Types are the Oracle EBS mechanism for storing customer-defined, flexfield-style attribute data against standard HR entities such as assignments, people, and positions. The HR_ASSIGNMENT_EXTRA_INFO_BK1 package therefore encapsulates the low-level insert, update, and delete logic required to persist EIT records for assignments. It exists so that the public API layer can enforce validation, security, and business rules before delegating to this backing package, which in turn performs the actual DML against the underlying EIT tables. The ETRM metadata confirms the package is VALID and classified as OTHER in API classification, consistent with its role as an internal supporting unit rather than a directly callable public API.

Key Procedures and Functions

The ETRM documentation records two documented procedures within this package:

  • CREATE_ASSIGNMENT_EXTRA_INFO_B — The "Before" procedure. In the standard Oracle API pattern, the _B (Before) procedure handles pre-processing: data validation, default derivation, and preparation of the record before it is written. It ensures the incoming EIT data satisfies integrity constraints before any database changes occur.
  • CREATE_ASSIGNMENT_EXTRA_INFO_A — The "After" procedure. The _A (After) procedure performs the actual DML, inserting the prepared record into the assignment extra information storage. Together, the _B and _A procedures form the canonical "Before/After" pairing used throughout Oracle HRMS APIs.

Only these two procedures are documented in the ETRM metadata. Neither parameter lists nor return signatures are published in the excerpt, so they are not reproduced here.

Tables Accessed

The ETRM excerpt does not enumerate specific tables referenced through APPS synonyms, listing the tables-referenced section as empty. However, by definition of its purpose, the package writes to the assignment extra information storage tables — principally HR_ASSIGNMENT_EXTRA_INFO (the current or "live" EIT data) and its associated date-tracked or _D / _T variants where the EIT is configured as date-tracked. The "After" procedure is the component responsible for these inserts and updates; the "Before" procedure validates against the assignment record itself, typically via the PER_ASSIGNMENTS_F entity, to confirm the parent assignment exists and is valid. Because the table list is not documented in the supplied metadata, exact table names beyond the canonical EIT storage should be confirmed against the actual package source in the customer environment.

Usage Notes

This package is not intended to be called directly by customer code. The ETRM dependency information states it is referenced by the HR_ASSIGNMENT_EXTRA_INFO_API package, meaning the public API invokes these _B and _A procedures as part of its internal execution path. Conversely, HR_ASSIGNMENT_EXTRA_INFO_BK1 itself references only the SYS STANDARD package, indicating a straightforward PL/SQL implementation with no external custom dependencies.

In practice, the package is invoked whenever an end user or concurrent process creates assignment-level extra information through the standard Oracle HRMS forms (for example, the Assignment Extra Information window in the People form) or through programmatic calls to the public API. It also executes during dataload, migration, and integration routines that leverage the HR assignment EIT API. Because the "Before/After" split exists to support Oracle's date-tracked data model, the procedures are called in sequence within a single API transaction so that validation and DML remain atomic. This object is relevant to EBS 12.1.1 and 12.2.2 alike; its presence and implementation are essentially unchanged across these releases, as the extra-information framework is stable within the HRMS data model.