Search Results outside_min_action_code

Overview

GMD_TESTS_VL is a bilingual (VL-suffixed) view owned by the APPS schema in Oracle E-Business Suite, defined in the Process Manufacturing Product Development module (GMD). It presents the master definition of quality tests — referred to internally as assays — used throughout Oracle Process Manufacturing Quality Management. The view exposes the QC assay type identifier, the associated quality control unit, operational routing references, acceptance ranges, and the full set of descriptive flexfield (DFA) attribute columns. Because the view merges the transactional base table with its translation table, it returns language-specific test descriptions based on the session language of the querying user.

The view is the standard, supported access point for reporting and integration. Direct queries against GMD_TESTS_B bypass translation and do not supply a language-resolved ASSAY_DESC; GMD_TESTS_VL resolves this by joining the base and translation tables and filtering on USERENV('LANG'). It is marked VALID in the data dictionary and is available in both EBS 12.1.1 and 12.2.2, which share the same APPS schema object definitions for this component.

Underlying Base Objects

The view is defined over two synonyms that resolve to the following tables in the APPS schema:

• GMD_TESTS_B — the base table that stores the language-independent test definition, including operational references, specification limits, and flexfield data.
• GMD_TESTS_TL — the translation table that stores the language-dependent ASSAY_DESC (and related translated text), keyed by QCASSY_TYP_ID and LANGUAGE.

The join condition is B.QCASSY_TYP_ID = T.QCASSY_TYP_ID combined with T.LANGUAGE = USERENV('LANG'). This ensures a single row per assay type for the current session language, with the description translated where available. The view is read-only; DML must be directed to the base tables through the supported Process Manufacturing APIs.

Key Columns

The view returns the pseudocolumn ROW_ID (B.ROWID) plus the following functional columns:

• QCASSY_TYP_ID — primary key of the assay type; the join key to the translation table.
• ORGN_CODE — the organization that owns the test definition.
• ASSAY_CODE and ASSAY_DESC — the test code (from the base table) and its translated description (from the translation table). ASSAY_DESC is the reason the _VL variant exists.
• ASSAY_TYPE and ASSAY_CLASS — classify the test for grouping and validation purposes.
• TEST_PROVIDER_CODE — identifies the provider responsible for performing or supplying the test. This is the column most frequently referenced in integration and reporting, since it links a test definition to an external or internal laboratory/provider.
• QCUNIT_CODE — the unit of measure for the test result.
• TEST_OPRN_ID and TEST_OPRN_LINE_ID — link the test to a routing operation and operation line, indicating where in the process the test is applied.
• MIN_VALID and MAX_VALID — the valid numeric range for results.
• INSIDE_SPEC_MIN/MAX, OUTSIDE_SPEC_MIN/MAX — inner and outer specification boundaries used for pass/fail evaluation.
• ERROR_VAL_TYPE and the four action-code columns (INSIDE_MAX_ACTION_CODE, OUTSIDE_MIN_ACTION_CODE, OUTSIDE_MAX_ACTION_CODE, INSIDE_MIN_ACTION_CODE) — drive disposition behavior when readings fall outside limits.
• DELETE_MARK and IN_USE — soft-delete and active flags; row-level audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) track change history.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–30 — descriptive flexfield segments available for customer extension.

Common Use Cases and Queries

The view is commonly used to list active tests for a given organization, to resolve a translated description for display, and to locate all tests associated with a specific provider. A typical use case arises when the analyst searches on test_provider_code to audit which tests are performed by a particular provider.

Example: list active tests and providers for an organization.

• SELECT assay_code, assay_desc, test_provider_code, qcunit_code, min_valid, max_valid FROM gmd_tests_vl WHERE orgn_code = :org AND in_use = 1 AND delete_mark = 0 ORDER BY assay_code;

Example: retrieve all tests for a provider (the searched column).

• SELECT qcassy_typ_id, assay_code, assay_desc FROM gmd_tests_vl WHERE test_provider_code = :provider_code AND delete_mark = 0;

Example: inspect specification limits for a specific assay type.

• SELECT assay_code, inside_spec_min, inside_spec_max, outside_spec_min, outside_spec_max FROM gmd_tests_vl WHERE qcassy_typ_id = :qcassy_typ_id;

Because the view is a simple two-table join with a language filter, it performs well in reporting queries. When embedding it in inbound interfaces or extracts, always filter on DELETE_MARK and IN_USE to avoid returning retired or inactive test definitions, and join through QCASSY_TYP_ID when correlating with results stored in QC result tables such as GMD_QC_RESULTS.