Search Results bix_dm_get_agent_refresh_date

Overview

BIX_UTIL_PKG is a utility package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Interaction Center / Call Center intelligence (BIX) module. It is declared AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking session rather than the package owner — an important consideration when it is called from restricted contexts. The package supplies a collection of shared helper routines used by the BIX reporting layer to render dashboard footers, resolve refresh timestamps, derive accounting periods, and format elapsed-time values. It is deliberately non-transactional: it holds no business tables of its own and performs no DML against transactional entities.

In the ETRM 12.1.1 metadata the package is classified as OTHER rather than as a public or private API, confirming it is an internal support library rather than a supported integration interface. Twelve other packages reference it, which indicates broad internal reuse across the BIX family of reports and the real-time agent and call-monitoring dashboards.

Key Procedures and Functions

The documented interface comprises twenty-four callable units grouped by purpose.

• Session and lookup helpers: GET_ICX_SESSION_ID returns the current ICX (Self-Service) session identifier as a number, and GET_NULL_LOOKUP returns a standard null-replacement string used when rendering report fields with no value.
• Duration formatting: GET_HRMISS_FRMT and GET_HRI_FRMT accept a duration in seconds and return formatted strings in hours/minutes/seconds and hours/minutes representations respectively, used for agent talk-time and wait-time display.
• Refresh-date functions: GET_UWQ_REFRESH_DATE and GET_CALLS_REFRESH_DATE, together with BIX_DM_GET_AGENT_REFRESH_DATE and BIX_DM_GET_CALL_REFRESH_DATE, return the last collection timestamp for the universal work queue and call summaries, with an optional context argument enabling per-context filtering.
• Period derivation: GET_START_DATE, GET_GROUP_BY, GET_PREV_PERIOD and GET_CURR_PERIOD translate a period set name, period type, reference date and number of periods into start dates, group-by expressions, and prior or current period boundaries. GET_TIME_RANGE resolves an internal time identifier into a from-date and to-date pair returned as OUT parameters.
• Footer builders: BIX_DM_GET_FOOTER, BIX_DM_GET_AGENT_FOOTER, BIX_DM_GET_CALL_FOOTER, BIX_REAL_GET_FOOTER, GET_UWQ_FOOTER, GET_UWQ_DURATION_FOOTER and GET_REALTIME_FOOTER assemble the standard footer text printed at the base of each dashboard and report variant, each tuned to a specific report family.

All header-rendering functions accept an optional p_context parameter defaulted to NULL, allowing a single function to serve several calling reports.

Tables Accessed

The package reads a small, well-defined set of objects through APPS synonyms.

• BIX_DM_AGENT_SUM, BIX_DM_CALL_SUM, BIX_DM_AGENT_CALL_SUM and BIX_DM_UWQ_AGENT_SUM — the pre-aggregated data-mart summary tables queried by the refresh-date and footer functions to establish when statistics were last populated.
• BIX_DM_COLLECT_LOG — the collection log consulted to determine the outcome and timestamp of the most recent data-mart load.
• GL_PERIODS — the General Ledger period definition table, used by GET_PREV_PERIOD, GET_CURR_PERIOD and the related date functions to translate period names into concrete start and end dates.
• DUAL — used for scalar evaluations such as the null lookup and session identifier retrieval.

No documented insert, update or delete operations are performed; the package is read-only with respect to these tables.

Usage Notes

BIX_UTIL_PKG is not exposed through a standard concurrent program submission form. It is invoked indirectly: report and dashboard templates call the footer and refresh-date functions during output generation, and other BIX packages call it internally — the metadata records twelve dependent packages. Because it is declared AUTHID CURRENT_USER, callers must hold direct privileges on the underlying synonyms; custom code that invokes it from a schema other than APPS should be tested accordingly. The most frequently searched entry point, GET_ICX_SESSION_ID, is typically used inside JSP or OAF-based Interaction Center pages to obtain the active ICX session number for logging and personalisation, and it relies on the ICX session context being initialised at the time of the call. All functions were last shipped at version 115.24 in November 2002 and have remained stable across 12.1.1 and 12.2.2.