Search Results test_result




Overview
Explore in AI Chat

Overview

APPS.GMD_QC_E_SAMPLE_RESULTS_V is a database view owned by the APPS schema in Oracle E-Business Suite, documented under FND Design Data as GMD.GMD_QC_E_SAMPLE_RESULTS_V. It exposes quality control sample result information drawn from the Oracle Process Manufacturing (OPM) Quality module, presenting a denormalized, read-oriented projection of sample headers, test definitions, and recorded results. The "E" prefix and the presence of UPDATE_INSTANCE_ID indicate that the view is oriented toward the e-records / e-signature feature set, allowing result data to be associated with an electronic signature instance identifier. The view is classified as Oracle Internal Use Only: Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. Its status is VALID. No database object references this view, so it functions strictly as a terminal, non-reusable reporting and integration surface rather than as a dependency for other database constructs.

Underlying Base Objects

The view is defined over five referenced base objects, each exposed through an APPS synonym: FND_USER, GMD_QC_TESTS_B, GMD_RESULTS, GMD_SAMPLES, and MTL_PARAMETERS. GMD_SAMPLES supplies the sample header attributes (SAMPLE_ID, SAMPLE_NO, SAMPLE_DESC). GMD_RESULTS contributes the result record identity and value columns (RESULT_ID, TEST_RESULT, RESULT_DATE, TEST_REPLICATE_CNT). GMD_QC_TESTS_B provides the test definition to which the result belongs (TEST_ID). FND_USER supplies the application user name associated with the recorded result (USER_NAME). MTL_PARAMETERS provides the inventory organization context, surfacing ORGANIZATION_CODE. The joins consolidate transactional quality data with reference and setup information into a single queryable structure.

Key Columns

  • SAMPLE_ID (NUMBER) — Unique sample identifier, described as db-seq.
  • SAMPLE_NO (VARCHAR2 80) — Sampling number.
  • SAMPLE_DESC (VARCHAR2 80) — Sampling description.
  • UPDATE_INSTANCE_ID (NUMBER) — Stores e-signature instance identification.
  • RESULT_ID (NUMBER) — Unique identifier of the result record.
  • TEST_ID (NUMBER) — The test performed for which results are recorded.
  • TEST_RESULT (VARCHAR2 80) — The recorded outcome of the test, matched by the search term "test_result".
  • TEST_UNIT (VARCHAR2 25) — Unit of measure associated with the test result.
  • RESULT_DATE (DATE) — Date the result was recorded.
  • USER_NAME (VARCHAR2 100) — User associated with the result, sourced from FND_USER.
  • ORGANIZATION_CODE (VARCHAR2) — Inventory organization code, sourced from MTL_PARAMETERS.
  • TEST_REPLICATE_CNT (NUMBER) — Number of test replicates.

Common Use Cases and Queries

Typical uses include quality result reporting, laboratory trending by test and organization, and e-signature audit extracts. A standard retrieval follows the documented query text exactly:

SELECT SAMPLE_ID, SAMPLE_NO, SAMPLE_DESC, UPDATE_INSTANCE_ID, RESULT_ID, TEST_ID, TEST_RESULT, TEST_UNIT, RESULT_DATE, USER_NAME, ORGANIZATION_CODE, TEST_REPLICATE_CNT FROM APPS.GMD_QC_E_SAMPLE_RESULTS_V;

Filtering by organization and date supports trend analysis: SELECT SAMPLE_NO, TEST_ID, TEST_RESULT, TEST_UNIT, RESULT_DATE FROM APPS.GMD_QC_E_SAMPLE_RESULTS_V WHERE ORGANIZATION_CODE = :org AND RESULT_DATE BETWEEN :from_date AND :to_date ORDER BY RESULT_DATE;

Because the vendor restricts supported access to standard Oracle Applications programs, direct ad hoc querying should be treated as read-only and used with caution in production environments.