Search Results display_html




Overview
Explore in AI Chat

Overview

SYS.DBMS_FEATURE_USAGE_REPORT is an Oracle-supplied PL/SQL package that belongs to the SYS schema and is distributed as part of the core Oracle Database, not as an Oracle E-Business Suite product-specific API. Within the context of Oracle EBS 12.1.1 and 12.2.2, it functions as a reporting utility for the database Feature Usage and High Water Mark (HWM) statistics that Oracle collects automatically through the Automatic Workload Repository (AWR). Its principal role is to render the contents of the feature usage and HWM data gathered by the DBMS_FEATURE_USAGE_INTERNAL sampling infrastructure into a human-readable format, so that DBAs and EBS system administrators can determine which database features are actually being exercised by the EBS application tier.

In an EBS environment this information is significant because the EBS database schema — APPS, the product schemas, and the associated Oracle Homes — is large and long-lived, and Oracle licensing is feature-based. The package allows administrators to verify which options and features (for example, partitioning, advanced compression, or specific tuning packs) are in active use, supporting both license compliance reviews and upgrade or patching planning. The package metadata records a status of VALID and classifies the API under the OTHER category, confirming that it is not exposed as a documented EBS business API but as a database-level diagnostic utility.

Key Procedures and Functions

The ETRM documentation for this object records exactly two entry points:

  • DISPLAY_TEXT — Renders the feature usage and high water mark report content in plain-text form. This is the output mode suited to SQL*Plus, terminal sessions, and log files, and is the typical choice when the report is captured to a spool file or a concurrent request log during an EBS maintenance window.
  • DISPLAY_HTML — Renders the same report content as HTML. This form is intended for consumption in a browser or in a formatted report viewer, and it is the mode used when the output must be presented to a reviewer rather than parsed as text.

The parameter lists for these procedures are not enumerated in the ETRM metadata and should not be assumed; administrators should inspect the package specification directly in the target database with DBMS_METADATA or USER/ALL_SOURCE before invoking them from custom code.

Tables Accessed

The documented dependency information for the package does not list any application tables. Instead, DBMS_FEATURE_USAGE_REPORT depends on two Oracle-supplied collection types, SYS.AWRRPT_HTML_TYPE_TABLE and SYS.AWRRPT_TEXT_TYPE_TABLE, together with the STANDARD package. These are the AWR report formatting types used across Oracle's AWR report generation packages. The underlying feature usage and high water mark data is therefore sourced from the AWR repository rather than from any EBS product schema. No EBS application tables are read or written through APPS synonyms, and the package is not referenced by any other package, which confirms its role as a terminal, read-only reporting utility.

Usage Notes

The package is not invoked from any standard EBS form or concurrent program. It is called manually by DBAs and EBS system administrators, typically from SQL*Plus or SQL Developer connected as SYS or another privileged account, at the direction of Oracle Support or as part of an internal license and feature audit. Typical invocation points include quarterly licence reconciliation exercises, pre-upgrade assessments between EBS 12.1.1 and 12.2.2 where enabled database options must be confirmed, and any engagement where Oracle requires evidence of feature usage. Because the package is owned by SYS, it should be treated as read-only and never modified. Custom code that wraps it should grant the minimum privileges required and should not assume stability of its output format across database patch levels, since the AWR report types it relies upon are themselves versioned with the database release.