Search Results interpret_all_asgnmnt_changes




Overview
Explore in AI Chat

Overview

HRI_OPL_EVENT_CAPTURE is an Oracle EBS Human Resources Intelligence (HRMS Intelligence / Daily Business Intelligence) package that drives event capture for the HR intelligence warehouse. It is the primary mechanism by which the EBS application detects changes to HR transactional data and queues the corresponding events so that the HR Intelligence fact and dimension tables can be refreshed incrementally. The package is declared with AUTHID CURRENT_USER and resides in the APPS schema, executing with the privileges of the calling user.

The core design of the package is centered on the concept of an event group. A master event group tracks all changes that affect subordinate event groups, while separate sub event groups track specific subject areas: supervisor hierarchy changes, assignment event fact changes, and absence dimensional changes. Global package variables such as g_master_event_group_id, g_sprvsr_change_event_grp_id, g_assgnmnt_evnt_event_grp_id, and g_absence_dim_event_grp_id hold these identifiers during a run. These variables are deliberately public so that external PL/SQL scripts can inspect them for debugging. The g_capture_from_date variable defines the lower bound for event collection (typically the day after the last successful run, or the DBI global start date), while events are always collected through hr_general.end_of_time. The g_full_refresh_not_run flag allows the range cursor to operate in a clean failover mode until a full refresh has completed.

Key Procedures and Functions

  • GET_EVENT_GROUP_ID — Resolves and returns the event group identifier for a given logical event group. This is the procedure most directly relevant to callers searching on get_event_group_id, since it is the supported accessor for the IDs stored in the global variables.
  • RUN_FOR_BG — Executes event capture for a business group, driving the collection cycle across all applicable event groups.
  • RUN_FOR_ASG — Executes event capture scoped to assignment-level data.
  • INTERPRET_ALL_ASGNMNT_CHANGES — Interprets detected changes on assignments and translates them into the appropriate queued events.
  • FIND_SUB_EVENT_GROUP_EVENTS — Locates events belonging to sub event groups, linking subordinate changes back to the master group.
  • FULL_REFRESH — Performs a complete rebuild of captured events rather than an incremental capture; also clears the g_full_refresh_not_run condition on success.
  • PROCESS_RANGE — Processes a defined range of data, typically bounded by g_capture_from_date and end of time.
  • PRE_PROCESS and POST_PROCESS — Wrap the main capture logic with setup and cleanup operations.
  • PURGE_QUEUE — Removes obsolete entries from the event queues.
  • EMPTY_EVNTS_CPTR_REFRESH_LOG — Clears the event capture refresh log.
  • DBG — Debugging helper used to emit diagnostic output during capture runs.

Tables Accessed

The package reads and writes a wide set of HR Intelligence and related tables through APPS synonyms. Event queues include HRI_EQ_ASGN_EVNTS, HRI_EQ_SPRVSR_HRCHY_CHGS, HRI_EQ_SPRVSR_HSTRY_CHGS, HRI_EQ_UTL_ABSNC_DIM, HRI_EQ_WRKFC_EVT_MGRH, HRI_EQ_WRKFC_EVT_ORGH, and HRI_EQ_WRKFC_MNTH. Supporting control and log tables include BIS_REFRESH_LOG, FND_NEW_MESSAGES, HRI_ARCHIVE_EVENTS, and HRI_ADM_MTHD_ACTIONS. Change-tracking and collection tables read by the package include HRI_CS_MNGRSC_CT, HRI_CS_ORGH_CT, HRI_CS_SUPH, and HRI_MB_ASGN_EVENTS_CT. Together these support detection, queuing, logging, and archival of HR change events.

Usage Notes

HRI_OPL_EVENT_CAPTURE is normally invoked indirectly through HR Intelligence concurrent programs and collection processes rather than being called ad hoc. It is referenced by two other packages, indicating it forms part of a coordinated capture framework. Custom code should use GET_EVENT_GROUP_ID to obtain event group identifiers rather than querying underlying tables directly, and the public global variables may be read for diagnostics. Direct invocation is appropriate only for controlled full-refresh or debugging scenarios, since misuse of g_capture_from_date or g_full_refresh_not_run can cause missed or duplicated events.