Search Results test_priority




Overview
Explore in AI Chat

Overview

GMD_QC_E_SPEC_TESTS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered as part of the GMD – Process Manufacturing Product Development module. It presents quality specification test data in a form intended for external consumption, most notably by the Oracle Quality interface used by Process Manufacturing (formerly OPM) when transferring specification tests between applications. The view combines rows from GMD_SPEC_TESTS with descriptive attributes from GMD_QC_TESTS, GMD_TEST_METHODS, and the FND_LOOKUP_VALUES_VL lookup table, producing a denormalized, report-friendly result set.

The view is a key component of ETRM (Enterprise Technical Reference Manual) documentation for Release 12.1.1 and 12.2.2, and it appears as a VALID object in the APPS schema in both releases. Its name includes the "_E_" segment, indicating its use in the external-facing specification test interface rather than internal processing.

Underlying Base Objects

The view is defined over the following documented base objects:

Because most of these are synonyms over the GMD schema objects, the view effectively joins specification-test records to test definitions, test methods, lookup meanings, and action descriptions in a single layer.

Key Columns

  • SPEC_ID / TEST_ID – the specification and test identifiers forming the primary key context of each row.
  • SPEC_MIN_VALUE, SPEC_TARGET_VALUE, SPEC_MAX_VALUE – decoded columns that return character or numeric limits depending on TEST_TYPE ('T' for text, 'E' for enumeration, 'N' for numeric, 'L' for list). This decode logic is central to the view's purpose: it produces a unified, type-consistent set of limit columns.
  • OPTIONAL_IND – the Y/N flag indicating whether the test is optional for the specification; the view replaces the raw flag with its lookup meaning (FLY.MEANING for 'Y', FLN.MEANING for 'N').
  • TEST_TYPE & TEST_TYPE_DESC – the raw test-type code and its translated description.
  • BELOW_SPEC_MIN, ABOVE_SPEC_MIN, BELOW_SPEC_MAX, ABOVE_SPEC_MAX – action codes applied when a result falls outside each boundary.
  • OUT_OF_SPEC_ACTION / OUT_OF_SPEC_ACTION_DESC – the action taken for an out-of-specification result, with its description.
  • DISPLAY_PRECISION / REPORT_PRECISION – decimal precision settings for on-screen and reported values.
  • TEST_PRIORITY – the translated priority of the test.

Common Use Cases and Queries

Typical uses include reporting specification test limits, generating external quality interface extracts, and validating optional versus mandatory tests on a specification. A simple query to list all tests for a specification, including whether each is optional, is:

SELECT SPEC_ID, TEST_ID, TEST_CODE, TEST_DESC,
       SPEC_MIN_VALUE, SPEC_TARGET_VALUE, SPEC_MAX_VALUE,
       OPTIONAL_IND, TEST_TYPE_DESC
FROM   APPS.GMD_QC_E_SPEC_TESTS_V
WHERE  SPEC_ID = :p_spec_id
ORDER  BY SEQ;

To identify optional tests only:

SELECT TEST_ID, TEST_CODE, SPEC_TARGET_VALUE
FROM   APPS.GMD_QC_E_SPEC_TESTS_V
WHERE  SPEC_ID = :p_spec_id
AND    OPTIONAL_IND = (SELECT MEANING FROM FND_LOOKUP_VALUES
                       WHERE LOOKUP_TYPE = 'YES_NO' AND LOOKUP_CODE = 'Y');

Because OPTIONAL_IND is already translated to a lookup meaning rather than the raw 'Y'/'N' character, consumers should filter using the lookup meaning value. The view's elimination of decode logic from the caller's SQL makes it suitable for external integration and reporting layers that expect uniform column semantics.