Search Results bis_query_attributes




Overview
Explore in AI Chat

Overview

APPS.BIX_PMV_EMC_CLASS_RPT_PKG is a PL/SQL package body in the Oracle E-Business Suite Applications (APPS) schema. It belongs to the Oracle Business Intelligence (BIX) family of database objects and is associated with the Process Manufacturing / Enterprise Manufacturing Intelligence (PMV/EMC) reporting layer. Its purpose is to generate the SQL statement used to drive a class-based report, most likely a "Class Report" used within the EMC (Enterprise Manufacturing Intelligence / E-Business Intelligence) analytical reporting framework. The package status is VALID in both Oracle EBS 12.1.1 and 12.2.2, which indicates it remains compilable and supported across these releases without requiring source remediation between them.

Functionally, the package sits in the metadata-driven reporting tier. Rather than storing a fixed SQL text, it dynamically builds the retrieval query based on query definitions and page parameters held in the Business Intelligence System (BIS) metadata tables. This design allows report content, columns, and filters to be configured at runtime instead of being hard-coded.

Key Procedures and Functions

The documented package exposes a single program unit:

  • GET_SQL — The central procedure/function of the package. Its role is to construct and return the SQL statement that the Class Report uses to retrieve its result set. GET_SQL assembles this query by consuming the query attribute definitions and page parameter input supplied through the BIS metadata tables (see below). No parameter list is documented in the ETRM metadata; the procedure name and its purpose should be treated as the authoritative description. Callers pass the report context (page/parameter identifiers) and receive the dynamically assembled SQL text for execution by the reporting engine.

Because the metadata lists only one documented procedure, the package is narrow and single-purpose: it exists to provide the query text that other components execute.

Tables Accessed

The package references the following objects, all resolved through APPS synonyms:

  • BIS_QUERY_ATTRIBUTES — The core definition table holding individual query attribute (column/field) metadata. This is the table most relevant to a search for "bis_query_attributes," and it is the primary source from which GET_SQL derives the select list and associated attribute properties.
  • BIS_QUERY_ATTRIBUTES_TBL — The PL/SQL collection type counterpart used to hold query attribute records in memory. GET_SQL uses it to pass and manipulate sets of attribute definitions while assembling the SQL text.
  • BIS_PMV_PAGE_PARAMETER_TBL — A PL/SQL nested table type carrying page-level parameters. These values provide the runtime filtering context (such as the class or page selections) that shapes the generated query.

Additionally, the package body depends on the SYS.STANDARD package for baseline PL/SQL functionality. The combination of these three BIS objects confirms that GET_SQL is a metadata-driven query builder rather than a direct table-access routine.

Usage Notes

BIX_PMV_EMC_CLASS_RPT_PKG is not referenced by any other database object, and it references no APPS tables directly beyond the BIS metadata constructs. This indicates it is invoked as a top-level report generator — typically called from the EMC/BIS reporting UI or the concurrent processing framework rather than from within another PL/SQL package.

Typical invocation scenarios include:

  • Online analytical report pages where GET_SQL supplies the query executed to render the Class Report results.
  • Concurrent program execution where the generated SQL is run and output is written to a report file.
  • Custom extensions that require the same dynamically assembled query text for a given page parameter set.

Administrators and developers troubleshooting a Class Report should verify that the relevant rows exist in BIS_QUERY_ATTRIBUTES for the targeted page, since missing or incomplete attribute definitions will produce an incomplete or failing SQL statement. The package metadata is otherwise stable and valid in both 12.1.1 and 12.2.2, so no release-specific behavior changes are documented.