Search Results is_customized

Overview

FND_OAM_METVAL_VL is a read-only reporting view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the FND — Application Object Library product and is designated VALID in the enterprise technical reference model. The view exposes the metric values collected by the Oracle Applications Manager (OAM) monitoring framework, combining the transactional metric data stored in FND_OAM_METVAL with the translated display names and descriptions held in FND_OAM_METS_TL. Its suffix, "_VL", follows the EBS convention denoting a view that joins a base entity to its translation (TL) table and filters the translation rows to the session's active language, so consumers receive a single, language-appropriate row per metric. Because it presents both collected metric values and the alerting thresholds that govern them, the view is the primary reporting surface for administrators auditing system health, capacity, and notification configuration across application-tier nodes.

Underlying Base Objects

The view is defined over two documented base objects:

• FND_OAM_METVAL — the base metric value table, referenced through a synonym, providing the operational data such as collected values, node names, status codes, and threshold settings.
• FND_OAM_METS_TL — the translation table for metric definitions, also referenced through a synonym, supplying METRIC_DISPLAY_NAME and DESCRIPTION in the user's language.

The join condition links the two objects on METRIC_SHORT_NAME, with the translation side filtered by T.LANGUAGE = USERENV('LANG'). This guarantees that only the current session language's translation row is returned. The view text also surfaces B.ROWID as ROW_ID, although no updatable behavior is supported, as is typical for a _VL view.

Key Columns

The view projects columns from both base objects. The most significant include:

• METRIC_SHORT_NAME / METRIC_DISPLAY_NAME / DESCRIPTION — the internal metric identifier and its language-specific label and narrative.
• METRIC_VALUE — the value captured at the last collection interval for the metric on the associated node.
• THRESHOLD_OPERATOR and THRESHOLD_VALUE — the comparison operator and the numeric or textual limit against which METRIC_VALUE is evaluated to raise an alert. These columns are directly relevant to the search term "threshold_value".
• ALERT_ENABLED_FLAG / COLLECTION_ENABLED_FLAG — flags indicating whether alerting and periodic collection are active for the metric.
• STATUS_CODE, METRIC_TYPE, GROUP_ID, SEQUENCE, NODE_NAME — classification, ordering, and node context for the metric.
• LAST_COLLECTED_DATE, INTERVAL_COUNTER — collection timing and cadence information.
• IS_SUPPORTED, IS_CUSTOMIZED — flags distinguishing Oracle-supported versus customer-defined metrics.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include auditing configured alert thresholds, reviewing collected metric values against their thresholds, and identifying customized or unsupported metrics. The following example lists alerting metrics whose configured threshold is set:

SELECT metric_short_name, metric_display_name, threshold_operator,
       threshold_value, metric_value, alert_enabled_flag
  FROM apps.fnd_oam_metval_vl
 WHERE alert_enabled_flag = 'Y'
   AND threshold_value IS NOT NULL
 ORDER BY metric_short_name;

A second scenario reports the current value and threshold per node for capacity review:

SELECT node_name, metric_short_name, metric_value,
       threshold_operator, threshold_value, last_collected_date
  FROM apps.fnd_oam_metval_vl
 WHERE collection_enabled_flag = 'Y';

Because the view is language- and node-aware, it is suitable for both localized OAM dashboard reporting and downstream integration extracts that must reconcile collected values with the thresholds driving OAM alerts.