Search Results max_value_char

Overview

PMITS_QC_SPEC_TESTS_V is an APPS-owned database view in Oracle E-Business Suite that exposes quality control specification tests along with their associated reference information. It belongs to the Process Manufacturing Intelligence (PMI) product family, which is documented as obsolete in the ETRM repository, and it is marked with a status of VALID in the APPS schema. The view is designed so that a user can access the tests associated with a given specification and, in the same row set, retrieve reference data defined against each test, such as the test method code, test type description, priority meaning, precision settings, and out-of-specification action details.

The defining characteristic of this view is its decoding logic. Several specification attributes are stored in the underlying tables in parallel numeric and character forms, and the view resolves which form to return according to the test type held on the quality test definition. Booleans such as OPTIONAL_IND are converted into their lookup meanings rather than the raw Y/N flags, and this pattern repeats for RETEST_LOT_EXPIRY_IND, PRINT_SPEC_IND, and PRINT_RESULT_IND. Because the product line is obsolete, the view is primarily of interest for legacy reporting, upgrade analysis, and integration work on pre-existing EBS instances rather than for new development.

Underlying Base Objects

The documented view metadata records only DUAL, exposed through a synonym, as a referenced base object. This reflects the way ETRM captures a limited subset of the dependency chain rather than the true data model. In practice, the view text shows that it joins quality specification and test definition tables in the GME/GQP family. The aliases GSTS, GTMS, GQTS, GAS, FLY, FLN, TEST_TYPES, TEST_PRIORITY, and EXP_ERROR_TYPE correspond to specification test records, test method definitions, quality test definitions, out-of-specification action definitions, and the standard lookup views used for meaning resolution. The DECODE against TEST_TYPE ('T', 'E', 'N', 'L') and the parallel MIN, TARGET, and MAX columns indicate that the view reconciles numeric specifications with text and enumerated specifications into a single consumable projection.

Key Columns

• SPEC_ID, TEST_ID, TEST_METHOD_ID, SEQ — primary identifiers that link a specification to its tests, method, and ordering.
• TEST_METHOD_CODE, TEST_CODE, TEST_DESC, TEST_UNIT, TEST_TYPE, TEST_TYPE_DESC — reference information describing the test itself, including its type meaning.
• SPEC_MIN_VALUE, SPEC_TARGET_VALUE, SPEC_MAX_VALUE — type-resolved specification limits returned from either the numeric or character storage columns.
• MIN_VALUE_NUM / TARGET_VALUE_NUM / MAX_VALUE_NUM and their CHAR counterparts — the raw underlying values retained for callers that need the untranslated form.
• OPTIONAL_IND — decodes the stored flag to a lookup meaning, indicating whether the test is optional for the specification. This is the column most often sought when users search on OPTIONAL_IND.
• BELOW_SPEC_MIN, ABOVE_SPEC_MIN, BELOW_SPEC_MAX, ABOVE_SPEC_MAX and the corresponding ACTION_CODE columns — tolerance boundaries and attributed actions.
• DISPLAY_PRECISION, REPORT_PRECISION, TEST_PRIORITY, OUT_OF_SPEC_ACTION, OUT_OF_SPEC_ACTION_DESC, OUT_OF_SPEC_ACTION_INTERVAL — presentation and escalation attributes.
• RETEST_LOT_EXPIRY_IND, PRINT_SPEC_IND, PRINT_RESULT_IND, EXP_ERROR_TYPE — behaviour flags exposed as meanings.

Common Use Cases and Queries

Typical usage is reporting on specification test configuration, particularly to list the tests attached to a specification and identify which are optional, or to extract specification limits for a downstream quality or integration process. A representative query is:

SELECT spec_id, test_id, test_code, test_desc, test_type_desc, spec_min_value, spec_target_value, spec_max_value, optional_ind FROM apps.pmits_qc_spec_tests_v WHERE spec_id = :spec_id ORDER BY seq;

Filtering on OPTIONAL_IND is equally common:

SELECT spec_id, test_id, test_code, optional_ind FROM apps.pmits_qc_spec_tests_v WHERE optional_ind = 'Yes' ORDER BY spec_id, seq;

Because the view resolves specification values according to test type, it should be preferred over direct joins to the underlying tables when the requirement is to present limits in a consistent, type-appropriate form. Given the obsolete PMI status, queries should be validated against the specific 12.1.1 or 12.2.2 instance before being embedded in long-lived reporting objects.