Search Results qa_device_info_u1

Overview

The QA_DEVICE_INFO table, owned by the QA schema, stores device setup information for Oracle E-Business Suite's Quality (QA) module. It defines the measurement and data-collection devices registered within a quality inspection environment, including their sensor aliases, polling behavior, and enablement status. This enables the Quality module to acquire readings from external hardware such as gauges, sensors, and automated data-collection instruments and associate them with inspection results. In 12.1.1 and 12.2.2, the table's physical schema is documented with 13 columns and two unique keys, and it is classified as VALID in the dictionary.

The heuristic Data Vault classification for QA_DEVICE_INFO is standalone. In Data Vault terms, this suggests modeling the table as a standalone hub keyed on DEVICE_ID rather than as a link or satellite, reflecting its lack of documented foreign-key dependencies. This should be treated as a modeling recommendation only, not a documented constraint.

Key Information Stored

The table's most significant columns include:

• DEVICE_ID — surrogate primary key, enforced by unique index QA_DEVICE_INFO_U1. Uniquely identifies each registered device.
• DEVICE_NAME — business-key candidate, enforced by unique index QA_DEVICE_INFO_U2. Human-readable device identifier.
• SENSOR_ALIAS — alias used to resolve the physical sensor or channel the device reads from; also part of the QA_DEVICE_INFO_U2 unique index.
• DESCRIPTION — free-text description of the device.
• PULL_FREQUENCY — interval controlling how often the device is polled for readings.
• ELAPSED_TIME — timing value associated with device acquisition or timeout behavior.
• OVERRIDE_FLAG — indicates whether manual override is permitted for this device.
• ENABLED_FLAG — controls whether the device is active and available for use.
• CREATED_BY, CREATION_DATE — audit columns recording who created the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit trail columns capturing the most recent change and session.

The distinction between the surrogate key (DEVICE_ID) and the business-key attributes (DEVICE_NAME, SENSOR_ALIAS) follows Oracle EBS referential conventions.

Common Use Cases and Queries

Typical scenarios include listing all enabled devices for a quality lab, auditing device configuration changes, and reporting on polling frequency for performance tuning. A representative query listing active devices:

• SELECT device_id, device_name, sensor_alias, pull_frequency FROM qa.qa_device_info WHERE enabled_flag = 'Y' ORDER BY device_name;
• To trace recent changes: SELECT device_name, last_updated_by, last_update_date FROM qa.qa_device_info WHERE last_update_date > SYSDATE - 30;
• To find devices with override enabled: SELECT device_id, device_name FROM qa.qa_device_info WHERE override_flag = 'Y';

Related Objects

Because QA_DEVICE_INFO is classified as standalone with no documented FK relationships, it functions as an independent setup/master table. Related objects are therefore inferred from the QA module's device-driven data-collection architecture:

• QA results/inspection tables (referencing DEVICE_ID) — link captured readings back to the originating device.
• QA collection element and plan tables — define what each device measures during inspection.
• QA specifications and results tables — consume device readings for pass/fail evaluation.
• FND audit and concurrent request views — surface the CREATED_BY/LAST_UPDATED_BY audit columns.
• QA device setup forms/APIs — the UI layer that maintains rows in this table via the integrity constraints QA_DEVICE_INFO_U1 and QA_DEVICE_INFO_U2.

Consult the QA schema data model for exact join columns, since the documented metadata does not expose foreign keys.