Search Results spec_max_value




Overview
Explore in AI Chat

Overview

APPS.PMITS_QC_RESULTS_V is a database view registered in the Oracle E-Business Suite Applications (APPS) schema, associated with the Process Manufacturing (OPM) Quality module. In the context of Oracle EBS 12.1.1 and 12.2.2, views of this naming family are exposed to support quality results reporting, integration, and inquiry screens within Process Manufacturing. The object carries the PMITS prefix, which is characteristic of Process Manufacturing Intelligence and quality-related object families.

The view presents a flattened, denormalized projection of quality result data, including test results, specification limits, and a status flag identified by the column RSLT_DELETE_MARK. The term "rslt_delete_mark" in the user query maps directly to the RSLT_DELETE_MARK column exposed by this view, indicating that the user is likely investigating how deletion or soft-delete status is tracked on quality results records.

Underlying Base Objects

The documented ETRM metadata for this view identifies a single referenced base object: the DUAL synonym, owned effectively by the SYS schema and exposed through the standard Oracle data dictionary construct. In Oracle EBS, DUAL is the canonical one-row, one-column pseudo-table used to return expressions, constants, or SYSDATE without referencing a physical application table.

Because the documented view text selects entirely literal and generated values (numeric constants, string literals, and SYSDATE) from DUAL, the metadata indicates this object functions as a placeholder, stub, or seeded definition rather than a view that directly reads application tables at definition time. In practice, such EBS views are often superseded at runtime by synonyms pointing to the true underlying PM quality tables, or they serve as view templates within the Process Manufacturing Intelligence schema. The metadata confirms that DUAL is the only referenced base object, and that the view definition is composed of constant expressions.

Key Columns

The view exposes a large number of columns derived from the literal SELECT list. Notable documented column names include ADDITIONAL_TEST_IND, RESULT_MEANING, TEST_RESULT, RSLT_DELETE_MARK, SPEC_MIN_VALUE, SPEC_TARGET_VALUE, SPEC_MAX_VALUE, and OPTIONAL_IND. The ORDER of these columns in the SELECT list follows the typical quality result payload: identifiers, test attributes, result values, specification limits, and status indicators.

  • RSLT_DELETE_MARK — the deletion or soft-delete indicator for a quality result record. This is the primary column the user searched for, and it is used to determine whether a result row is logically deleted.
  • TEST_RESULT — holds the measured or observed value returned for a given quality test.
  • RESULT_MEANING — provides the descriptive or coded meaning associated with the test result.
  • SPEC_MIN_VALUE / SPEC_TARGET_VALUE / SPEC_MAX_VALUE — specification limits against which the test result is evaluated for pass/fail determination.
  • ADDITIONAL_TEST_IND — indicates whether the test is an additional (non-mandatory) test.
  • OPTIONAL_IND — flags attributes or tests that are optional in the quality specification setup.

Common Use Cases and Queries

The primary use case is querying quality results while filtering out logically deleted records using the RSLT_DELETE_MARK column. Typical SQL might take the following form:

  • SELECT TEST_RESULT, RESULT_MEANING, SPEC_MIN_VALUE, SPEC_TARGET_VALUE, SPEC_MAX_VALUE FROM APPS.PMITS_QC_RESULTS_V WHERE RSLT_DELETE_MARK = 'N';
  • SELECT * FROM APPS.PMITS_QC_RESULTS_V WHERE RSLT_DELETE_MARK IS NULL;

Because the documented definition is composed of literals from DUAL, developers should validate the view's runtime behavior in their specific environment before relying on it for production reporting. In many EBS instances the actual PM quality result data originates from OPM quality tables such as QA_RESULTS and related specification tables, which are frequently surfaced through the synonym layer. Querying the view with a filter on RSLT_DELETE_MARK remains a valid pattern for applications that treat soft deletion as a status flag rather than a physical delete.