Search Results device_source

Overview

APPS.QA_DEVICE_DATA_VALUES_V is a lightweight reporting and integration view in the Oracle E-Business Suite Quality Management (QA) module. It exposes the raw contents of the device data values repository maintained by the QA device data collection infrastructure, which supports the capture of measurements and readings produced by shop-floor instruments, gauges, and other connected data-capture devices. The view is owned by the APPS schema, which is the standard convention for shared, cross-module database objects in EBS 12.1.1 and 12.2.2. Its principal role is to present device event records in a consistent, timestamp-aware form suitable for downstream queries, analytics, and integration interfaces without exposing the caller to the internal storage representation of the base synonym.

Because the view is defined in the ETRM repository and is referenced by name during development and support activities, it is frequently located by searches such as "quality_code", the column name that carries the data quality indicator for each captured reading.

Underlying Base Objects

The view is defined over a single documented base object: the synonym QA_DEVICE_DATA_VALUES. In an EBS environment a synonym of this kind typically resolves to the underlying QA device data table in the APPS schema. The view does not persist any data of its own; it is a pure projection over the base object and therefore inherits its commit-time visibility and any row-level security applied at the base table or synonym level.

The most significant transformation performed by the view is the application of the TO_TIMESTAMP_TZ conversion to the event time. The base object stores the event time in a form that must be cast to a timestamp-with-time-zone value; the view performs this conversion so that consumers receive a consistent, time-zone-aware representation. The remaining columns are passed through unchanged under their original names.

Key Columns

• EVENT_TIME — The timestamp of the device data event, converted via TO_TIMESTAMP_TZ so that the value is expressed as a time-zone-aware timestamp. This is the primary temporal key for ordering and filtering readings.
• EVENT_DATA — The payload captured by the device at the event; typically the measured value or reading produced by the instrument.
• DEVICE_SOURCE — Identifies the source system or origin of the device data, allowing readings from different capture environments to be distinguished.
• DEVICE_NAME — The name of the device or collection point that produced the reading, used to associate values with a specific instrument or station.
• QUALITY_CODE — The data quality indicator for the event. This code classifies the reliability or status of the captured reading and is the column most often queried when filtering for valid, suspect, or rejected measurements.

Common Use Cases and Queries

The view is used to report device measurement activity, to feed quality analytics, and to drive integration programs that must consume readings with time-zone-correct timestamps. A frequent pattern is to filter on the quality indicator while ordering by event time:

• Listing valid readings by device: SELECT device_name, event_time, event_data FROM apps.qa_device_data_values_v WHERE quality_code = 'VALID' ORDER BY event_time DESC;
• Auditing suspect or rejected data: SELECT device_source, device_name, quality_code, COUNT(*) FROM apps.qa_device_data_values_v GROUP BY device_source, device_name, quality_code;
• Time-bounded extraction for integration: SELECT * FROM apps.qa_device_data_values_v WHERE event_time >= SYSTIMESTAMP - INTERVAL '1' DAY;

Consultants should note that this view is read-oriented and should not be used for direct data maintenance; device data is written through the standard QA collection processes rather than through the view.