Results for “qa_eres_spec_status”

24 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.QA_SPEC_CHARS_VAL_V is an Oracle EBS Quality Management (QA) view that presents the characteristic-level specification values defined against QA specification headers. It consolidates rows from QA_SPEC_CHARS (the specification-to-characteristic assignment and limit values) together with descriptive detail from QA_CHARS (characteristic definition) and header information from QA_SPECS (specification name, effective dates, and status). The view additionally joins MFG_LOOKUPS twice to resolve lookup meanings for the enabled flag and specification status.

Its role in reporting and integration is to provide a flattened, denormalised projection of specification limits and characteristic attributes suitable for concurrent programs, XML/BI Publisher reports, OBIEE/OTBI extracts, and inbound/outbound interfaces that need to evaluate whether a characteristic value falls within defined limits. Because it resolves the QA_ERES_SPEC_STATUS lookup meaning inline, the view is a common access point for electronic records and electronic signatures (ERES) reporting, where the current status of a specification must be rendered as a user-facing meaning rather than a raw code. The _VAL suffix indicates that the view is scoped to characteristic validation values rather than the full specification definition.

Underlying Base Objects

The view is owned by APPS and is defined over the following documented objects:

  • QA_SPEC_CHARS (SYNONYM) — the driving table, providing per-characteristic limit values, UOM, enabled flag, and the DFF attribute columns.
  • QA_SPECS (SYNONYM) — the specification header, supplying SPEC_ID, SPEC_NAME, effective dates, and SPEC_STATUS.
  • QA_CHARS (SYNONYM) — the characteristic master, supplying name, datatype, decimal precision, and default UOM.
  • MFG_LOOKUPS (VIEW) — joined twice: ML2 resolves the SYS_YES_NO meaning for the enabled flag; ML3 resolves the QA_ERES_SPEC_STATUS meaning for the specification status.

Joins are performed on CHAR_ID, SPEC_ID (matched to QS.COMMON_SPEC_ID), and lookup code. The lookup joins use outer-join syntax (ML3 is outer-joined via the (+) operator), so rows survive when no QA_ERES_SPEC_STATUS lookup value exists. The enabled flag is filtered so that only rows with NVL(QSC.ENABLED_FLAG,-1)=1 are returned; ML2 is joined through a DECODE that maps 1 to 1 and any other value to 2.

Key Columns

Common Use Cases and Queries

Typical scenarios include listing all enabled characteristics for a specification together with their limits and status meaning, and validating results against limits in integration routines.

SELECT spec_name, char_name, target_value,
       lower_spec_limit, upper_spec_limit, uom_code,
       spec_status, meaning
FROM   apps.qa_spec_chars_val_v
WHERE  spec_id = :p_spec_id
ORDER  BY char_name;

To report specification status using the QA_ERES_SPEC_STATUS lookup — the term most users search on — filter or display the MEANING column, which carries the decoded status:

SELECT spec_name, spec_status, meaning
FROM   apps.qa_spec_chars_val_v
WHERE  spec_status IS NOT NULL
  AND  TRUNC(SYSDATE) BETWEEN effective_from AND NVL(effective_to, SYSDATE);

Other uses include generating limit-compliance extracts for LIMS interfaces, producing effective-date-driven specification reports, and querying DFF attribute values for custom characteristic classification.