Search Results qa_results_interface




Overview
Explore in AI Chat

Overview

QA_RESULTS_INTERFACE is a Quality (QA) module interface table in Oracle E-Business Suite, owned by the QA schema. Its documented purpose is as a "Quality Results Interface table for collection import." In practice, this is a staging and open-interface table that receives inbound quality collection result data — typically originating from outside EBS or from a feeder process — before the Quality Results Import concurrent program validates, transforms, and loads that data into the permanent QA collection results tables. The table is not a transactional results store; it is a transient landing zone whose rows carry a PROCESS_STATUS and VALIDATE_FLAG attribute and are subsequently purged or archived once the import completes successfully.

The object is unusually wide, with 309 documented columns in the ETRM 12.2.2 physical schema. That width reflects the table's role as a universal collection-attribute carrier: rather than defining a fixed column for every possible collection element, the design provides a large block of generic placeholder columns (CHARACTER1 through CHARACTER100, SEQUENCE1 through SEQUENCE15, COMMENT1 through COMMENT5) alongside strongly typed context columns for inventory, purchasing, WIP, service, projects, and process manufacturing.

Under a heuristic Data Vault classification mined from its foreign-key structure, QA_RESULTS_INTERFACE leans toward the satellite pattern, since it carries descriptive, contextual attributes keyed against multiple upstream entities rather than functioning as a pure many-to-many relationship (link) or a standalone business entity (hub). This should be treated as a modeling suggestion rather than a definitive classification.

Key Information Stored

The table's technical primary key is TRANSACTION_INTERFACE_ID, which uniquely identifies each inbound row. The principal business-key candidate for the import is COLLECTION_ID, which associates the staged row with a specific quality collection and is the primary lookup used by the import validation logic. GROUP_ID and SOURCE_CODE / SOURCE_LINE_ID provide the grouping and originating-source context for the batch.

Processing-control columns govern the interface lifecycle: PROCESS_STATUS, VALIDATE_FLAG, MARKER, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are similarly present, together with redundant QA_ variant audit columns such as QA_LAST_UPDATED_BY and QA_CREATED_BY.

Collection context columns include PLAN_ID / PLAN_NAME, SPEC_ID / SPEC_NAME, COLLECTION_ID, ORGANIZATION_ID, DEPARTMENT_ID, RESOURCE_ID, and TRANSACTION_DATE. Item and lot detail is captured through ITEM_ID, REVISION, UOM, QUANTITY, SUBINVENTORY, LOCATOR_ID, LOT_NUMBER, and SERIAL_NUMBER, with parallel COMP_ prefixed columns and TO_SUBINVENTORY / TO_LOCATOR describing the destination side of a movement or disposition.

The table further carries a large set of cross-module reference columns — including PO_NUMBER, PO_RELEASE_ID, RECEIPT_NUM, SALES_ORDER, WIP_ENTITY_ID, JOB_NAME, PROJECT_NUMBER, TASK_NUMBER, CUSTOMER_ID, VENDOR_ID, LICENSE_PLATE_NUMBER, and CONTRACT_NUMBER — allowing a single interface row to describe a collection taken in almost any EBS supply chain context. Nonconformance and disposition handling is supported by NONCONFORMANCE_CODE, NONCONFORMANCE_TYPE, DISPOSITION, DISPOSITION_ACTION, and DISPOSITION_STATUS.

Common Use Cases and Queries

Typical usage centers on monitoring and troubleshooting the Quality Results Import. A validation monitoring query counts rows by processing state:

SELECT PROCESS_STATUS, COUNT(*)
FROM   QA.QA_RESULTS_INTERFACE
GROUP  BY PROCESS_STATUS;

Rows that failed validation in a prior run can be isolated and inspected by their governing flag and request:

SELECT TRANSACTION_INTERFACE_ID, COLLECTION_ID, VALIDATE_FLAG,
       REQUEST_ID, ITEM, QUANTITY, MARKER
FROM   QA.QA_RESULTS_INTERFACE
WHERE  VALIDATE_FLAG = 'E';

Reporting scenarios include pre-import reconciliation of staged quality results against purchase receipts, work orders, or service repair orders, and comparing collection context (PLAN_NAME, SPEC_NAME) between the interface and the loaded results. Where large batches are submitted, operators commonly scope the query by GROUP_ID or REQUEST_ID to isolate a single import run, and by ORGANIZATION_ID to restrict to one inventory organization. Purging and archival routines periodically delete successfully processed rows from this table once the corresponding permanent collection results have been committed.

Related Objects

The documented foreign keys reveal the principal parent objects that constrain interface rows. Each relationship uses a specific join column:

In addition, the interface is consumed by the Quality Results Import concurrent program (identified through PROGRAM_ID / REQUEST_ID) and ultimately feeds the QA collection results tables, with cross-references into inventory transactions, WIP, and nonconformance records evidenced by columns such as MMT_TRANSACTION_ID, WIP_ENTITY_ID, and NONCONFORMANCE_CODE.