Search Results build_csr_dt_updates




Overview
Explore in AI Chat

Overview

PAY_EVENTS_WRAPPER is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that provides a programmatic wrapper on top of the Payroll Events Model interpreter. Its principal business purpose is to support the summarisation collection programs, which exist to improve the query performance of the Daily Business Intelligence (DBI) portlets. Rather than requiring calling code to interact directly with the event model engine, the wrapper exposes a controlled set of entry points through which summarisation programs determine which assignments, element entries, supervisors and refresh periods are affected by payroll event activity.

The package is declared AUTHID DEFINER, so it executes with the privileges of its owner rather than the invoking user. The header file, pyevtwrp.pkh, carries a version history spanning 2002 to 2003, with the final documented revision 115.10 removing the "show errors" directive for GSCC. The package has no reverse dependencies: it is referenced by zero other packages, indicating it is consumed by forms, concurrent programs or external custom code rather than being embedded in a wider package hierarchy.

Key Procedures and Functions

The package documents twenty-one procedures and functions, with GET_EVENT_DETAILS being the object most closely associated with the search that led here.

  • GET_EVENT_DETAILS — returns the detailed event data required by summarisation processing. The change history records that an element_entry_id parameter was added to this routine, along with a corresponding addition to an assignment table type.
  • GET_SUMMARIES_AFFECTED, GET_ASSIGNMENTS_AFFECTED — identify the summaries and assignments impacted by detected payroll events, driving the scope of incremental refresh.
  • GET_REFRESH_PERIODS, DE_DUPE_REFRESH_PERIODS — determine the date range requiring recalculation and remove duplicate periods before processing. A later revision added refresh period start and end dates to these routines.
  • GET_EVENT_GROUP_ID, GET_ELEMENT_ENTRY_TABLE_ID, ALL_SUPERVISORS_ID, BLANK_LOCATION_ID — lookup helpers returning the identifiers used to qualify event group and element entry contexts, including sentinel values for supervisors and locations.
  • BUILD_CSR_DT_UPDATES — constructs the SQL used to update dated-tracked records, handling both supervisor corrections and date-track updates.
  • INIT_EVENT_GROUP_CACHE — primes the internal cache using the event group global ID rather than the group name, reflecting the change that removed event group name as a parameter to internal modules.
  • NEXT_RECORD, CURRENT_RECORD — cursor navigation routines used while iterating result sets, supported by cursors deliberately moved to package level for visibility.
  • GET_ELAPSED_TIME, GET_ELAPSED_TIME_TEXT — timing utilities for diagnostics.
  • SET_CLIENT_DEBUGGING, SET_CONCURRENT_LOGGING, SET_DEBUGGING, MSG, DBG — diagnostics and logging controls, allowing messages to be written to the concurrent manager log file in debugging mode.

Tables Accessed

Through APPS synonyms the package reads and writes the core payroll event and element entry structures: PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_PROCESS_EVENTS, PAY_EVENT_UPDATES, PAY_EVENT_GROUPS and PAY_DATETRACKED_EVENTS. It also references PER_ALL_ASSIGNMENTS_F and PER_PAY_BASES for assignment and pay basis context, and PAY_DATED_TABLES to identify date-tracked objects. Metadata inspection is performed through DBA_TAB_COLUMNS and USER_SYNONYMS. Utility packages DBMS_UTILITY and PLITBLM are referenced directly from the body.

Usage Notes

PAY_EVENTS_WRAPPER is not a general-purpose payroll API. It is invoked by the summarisation collection programs that maintain the aggregated data sets behind Daily Business Intelligence portlets, and it may equally be called from concurrent programs or custom PL/SQL that must reproduce the same incremental refresh logic. Developers diagnosing event-related refresh issues should enable SET_DEBUGGING and SET_CONCURRENT_LOGGING so that MSG and DBG output is captured in the concurrent manager log. Because the package is a wrapper rather than a documented public API, direct calls should be treated as version-sensitive; the header shows continuing evolution of parameter signatures, most notably the addition of element_entry_id to GET_EVENT_DETAILS.