Search Results target_value_num

Overview

GMD_SPEC_TESTS_VL is a language-enabled (VL) view owned by the APPS schema in Oracle E-Business Suite, defined within the GMD product family — Process Manufacturing Product Development. It presents the specification test definitions that govern quality control and product conformance checks in Oracle Process Manufacturing (OPM). A specification test associates a specific test or test method with a quality specification, and defines the acceptance criteria — target, minimum, and maximum values — that a manufactured lot or batch must satisfy. The view serves as the primary reporting and integration access point for this data, exposing both the numeric and character-based limit columns, action codes, precision settings, and descriptive attributes that OPM Quality relies upon. Because it is a VL view, it joins the base (_B) table with the translation (_TL) table so that the test display text is returned in the session language. The metadata confirms a Status of VALID, indicating the view is compiled and available for query in the EBS 12.1.1 and 12.2.2 environments.

Underlying Base Objects

The view is defined over two documented base objects:

• GMD_SPEC_TESTS_B — the base table holding language-independent specification test data such as specification ID, test ID, sequence, limits, action codes, and descriptive flexfield attributes.
• GMD_SPEC_TESTS_TL — the translation table supplying language-dependent text, notably the TEST_DISPLAY column.

The join predicate is: B.SPEC_ID = T.SPEC_ID AND B.TEST_ID = T.TEST_ID AND T.LANGUAGE = USERENV('LANG'). This restricts translation rows to the current session language, ensuring each test appears once with the appropriate display text. Both base objects are referenced through synonyms in the APPS schema. The view text additionally exposes B.ROWID as ROW_ID, which is useful for identifying distinct base rows in certain update or integration scenarios.

Key Columns

• SPEC_ID / TEST_ID — Composite identifier linking each test to its parent specification.
• TEST_METHOD_ID — The test method executed to produce a result.
• SEQ — Ordering of the test within the specification.
• MIN_VALUE_NUM, TARGET_VALUE_NUM, MAX_VALUE_NUM — Numeric acceptance limits. The user's search term, max_value_num, corresponds directly to this column and is the upper numeric bound for a test result.
• MIN_VALUE_CHAR, TARGET_VALUE_CHAR, MAX_VALUE_CHAR — Character equivalents for qualitative or text-based specifications.
• BELOW_SPEC_MIN, ABOVE_SPEC_MIN, BELOW_SPEC_MAX, ABOVE_SPEC_MAX — Tolerance flags indicating acceptable deviation bands around the limits.
• OUT_OF_SPEC_ACTION, EXP_ERROR_TYPE — Behavior and error classification when results fall outside limits.
• TEST_QTY, TEST_QTY_UOM — Sample quantity required and its unit of measure.
• PRINT_ON_COA_IND, PRINT_SPEC_IND, PRINT_RESULT_IND — Output flags controlling printing on certificates of analysis and specification reports.
• TEST_DISPLAY — Language-specific test name sourced from the translation table.
• ATTRIBUTE1 through ATTRIBUTE30 — Descriptive flexfield segments.

Common Use Cases and Queries

Typical uses include building specification test listings, validating limit configurations, and feeding external quality systems. A common query retrieves all tests for a specification with their numeric limits:

SELECT spec_id, test_id, seq, test_display,
       min_value_num, target_value_num, max_value_num
  FROM apps.gmd_spec_tests_vl
 WHERE spec_id = :p_spec_id
 ORDER BY seq;

To locate tests with a specific upper bound, referencing the searched column:

SELECT spec_id, test_id, test_display, max_value_num
  FROM apps.gmd_spec_tests_vl
 WHERE max_value_num IS NOT NULL;

Because the view is language-sensitive, deterministic results require a defined USERENV('LANG') value, and joins to GMD_SPECIFICATIONS_B on SPEC_ID provide specification headers. Given that GMD_SPEC_TESTS_VL is a non-key-preserved view containing a ROWID pseudocolumn, it should be treated as read-only for reporting and integration purposes.