Search Results qa_device_data_values_v

Overview

The view QA_DEVICE_DATA_VALUES_V is a reporting and integration object in the Oracle E-Business Suite Quality (QA) module, owned by the APPS schema and documented as VALID in both ETRM 12.1.1 and 12.2.2. Its primary function is to expose time-stamped, device-generated data values captured during quality data collection. The view is defined as a thin projection over its base object, converting the stored event time into a time zone-aware TIMESTAMP so that consumers receive a consistent, internationally comparable representation of when each device reading occurred.

Because QA is used to record inspection results, collection plan outputs, and specification measurements, device data values often originate from shop-floor instrumentation, gauges, or automated test equipment. The view normalizes these values for downstream reporting, dashboards, and integrations without requiring consumers to know the shape of the underlying synonym. It is a read-only, query-only object; all maintenance is performed against the base object.

Underlying Base Objects

The documented base object referenced by QA_DEVICE_DATA_VALUES_V is the synonym QA_DEVICE_DATA_VALUES. The synonym resolves to the physical device data values table in the APPS schema, which stores one row per captured device event or reading. The view definition is:

• SELECT TO_TIMESTAMP_TZ(EVENT_TIME) EVENT_TIME, EVENT_DATA EVENT_DATA, DEVICE_SOURCE DEVICE_SOURCE, DEVICE_NAME DEVICE_NAME, QUALITY_CODE QUALITY_CODE FROM QA_DEVICE_DATA_VALUES;
• The only transformation applied is the conversion of EVENT_TIME into a time zone-aware value via TO_TIMESTAMP_TZ. All remaining columns are passed through unchanged.
• The view does not alter cardinality, so the number of rows returned matches the qualifying rows in the base synonym.

This minimal layering means the view inherits the base table's row-level dependencies and any constraints or profile options governing device data capture in QA.

Key Columns

• EVENT_TIME — The time zone-aware timestamp of the device reading, produced by TO_TIMESTAMP_TZ over the stored EVENT_TIME. Enables correct ordering and comparison across sites in different time zones.
• EVENT_DATA — The payload of the device event, typically the measured value or a structured data string submitted by the device. This is the column most directly associated with the user's "event_data" search.
• DEVICE_SOURCE — Identifies the originating source or system from which the device data was collected.
• DEVICE_NAME — The name or identifier of the device that produced the reading.
• QUALITY_CODE — The QA quality code associated with the value, linking the reading to a quality classification, specification, or collection element.

Common Use Cases and Queries

The view supports traceability of automated quality measurements. Typical scenarios include reporting latest readings per device, auditing a quality code's incoming values, and feeding EVENT_DATA into analytics or integration layers.

• List recent readings for a device:

  SELECT EVENT_TIME, DEVICE_NAME, EVENT_DATA
  FROM   APPS.QA_DEVICE_DATA_VALUES_V
  WHERE  DEVICE_NAME = :device_name
  ORDER  BY EVENT_TIME DESC;

• Filter by quality code across a time window:

  SELECT QUALITY_CODE, DEVICE_SOURCE, EVENT_DATA
  FROM   APPS.QA_DEVICE_DATA_VALUES_V
  WHERE  QUALITY_CODE = :quality_code
  AND    EVENT_TIME BETWEEN :from_ts AND :to_ts;

• Aggregate reading counts by source:

  SELECT DEVICE_SOURCE, COUNT(*)
  FROM   APPS.QA_DEVICE_DATA_VALUES_V
  GROUP  BY DEVICE_SOURCE;

In each case the time zone-aware EVENT_TIME column removes ambiguity when interpreting when a device value was recorded, which is essential for quality audits and cross-region reporting.