Results for “g_from_date”

25 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIX_AGENT_CLASS_P is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle Interaction Center / Telephony (BIX) agent reporting subsystem and is classified as OTHER in the ETRM metadata, reflecting that it is not exposed as a formally published public API but instead serves internal report-generation logic. Its principal business function is to assemble a dynamically constructed SQL statement that populates the BIX_DM_REPORT temporary reporting table with agent-level and class-level call-handling metrics. These metrics underpin the Agent Class Report, which summarizes inbound call activity grouped by agent group, resource (agent), and classification over a caller-selected time range.

The package declares a set of session-scoped globals that hold the runtime parameters of the report. Among these is g_from_date, a DATE variable holding the starting date of the reporting period. It sits alongside g_from_time, g_to_date, g_to_time, g_time_range, g_period_ind, g_class, g_site, and related identifiers. The presence of these globals indicates the package follows the classic Oracle Forms / Reports pattern in which report criteria are stored in package state and then consumed by the SQL-building routine.

Key Procedures and Functions

The ETRM metadata documents a single procedure: POPULATE. This is the entry point for report data generation. Its role is to establish the session context, evaluate the date and time globals — including g_from_date — and drive the SQL statement assembly and execution that inserts rows into the reporting table. The actual SQL construction is performed by the internal helper form_rs_sqlstmt, which builds an INSERT ... SELECT statement against BIX_DM_REPORT. The helper branches on the p_total_row_ind argument, producing different column projections depending on whether the report is a detail listing or a class summary.

No parameter lists are documented for POPULATE in the ETRM metadata, and none are asserted here. The header comment ($Header: bixxabcb.pls 115.31 2001/10/26 ...$) confirms the file is an original, long-standing component of the BIX code line. The SQL text uses a PARALLEL(tr,2) hint, indicating the design anticipates large result sets in high-volume call-center environments.

Tables Accessed

The documented tables referenced through APPS synonyms are:

  • BIX_DM_REPORT — the reporting staging table that receives inserted rows via the dynamically generated INSERT statement.
  • BIX_DM_AGENT_CALL_SUM — the agent call summary source from which aggregated call measures (for example, calls handled) are drawn.
  • CCT_CLASSIFICATIONS — supplies classification definitions used when the report is run in class summary mode.
  • JTF_RS_GROUP_MEMBERS — provides resource group membership, used to resolve agent-to-group relationships.
  • DUAL — used for single-row expression evaluation during statement construction.

Usage Notes

BIX_AGENT_CLASS_P is invoked internally by the BIX agent reporting flow rather than through direct customer calls. Typical invocation occurs from Oracle Forms or Reports when a user launches the Agent Class Report, passing date and time criteria that populate the package globals such as g_from_date. The metadata records zero packages referencing it and one documented procedure, confirming it is a leaf-level report generator. In 12.1.1 and 12.2.2, the package remains an APPS-owned, internal object; customization should be limited to report criteria or output, as the underlying schema and globals are version-controlled and may change between releases.