Search Results gmd_sample_status

Overview

APPS.PMIBV_QCRESULT_V is a reporting view in the Oracle E-Business Suite Process Manufacturing (OPM) Quality module. It consolidates quality control (QC) result data with the associated sample, specification, assay type, item, lot, customer, and vendor information, presenting a single denormalized record for each QC result. The view is owned by the APPS schema and is intended primarily for reporting, integration, and analytical queries rather than for transactional data entry.

The view joins the QC results master table to its governing specification, the originating sample, the assay type definition, and various master data entities. Because the base tables reside in the Process Manufacturing schema and are exposed through synonyms, the view provides a convenient, fully joined projection that shields consumers from the underlying normalization. This makes it well suited to quality reporting, certificate of analysis (COA) generation, and downstream integrations. The user search term gmd_sample_status is directly relevant: the view exposes SAMPLE_STATUS as a raw code and also decodes it into a meaningful description via the GMD_SAMPLE_STATUS lookup, which is the standard lookup type used to interpret sample status values.

Underlying Base Objects

The view is defined over the following documented objects:

• QC_RSLT_MST — the QC results master table, the driving table of the join, aliased QCresult in the view text.
• QC_SPEC_MST — the QC specification master, aliased QCspec, joined with an outer join (+).
• QC_SMPL_MST — the QC sample master, aliased QCSMPLMST, providing sample number, description, and status.
• QC_ASSY_TYP — the assay type definition, aliased QCASSYTYP, supplying the assay description.
• IC_ITEM_MST — the item master, aliased item, providing item number, description, and units of measure.
• IC_LOTS_MST — the lot master, aliased lot, providing lot and sublot numbers.
• HZ_CUST_ACCOUNTS_ALL and HZ_PARTIES — customer account and party data, aliased cust_acct and party, supplying party number and name.
• PO_VEND_MST — the vendor master, aliased VENDOR, supplying vendor number and name.
• PMI_COST_ANALZ_PACK — a package used in the SELECT list to resolve the GMD_SAMPLE_STATUS lookup meaning.
• PMI_SECURITY_PKG and SY_ORGN_MST — referenced in the view's join and organization security context.

The core join links each QC result to its specification and item, then bridges to sample, assay type, lot, customer, and vendor master data to produce the full projection.

Key Columns

• QC_RESULT_ID, QC_SPEC_ID, SAMPLE_ID — primary keys linking results, specifications, and samples.
• RESULT_DATE, NUM_RESULT, TEXT_RESULT — the result value and date; the SELECT list decodes to NUM_RESULT when present, otherwise TEXT_RESULT.
• SAMPLE_NO, SAMPLE_DESC, SAMPLE_STATUS — sample identity and the raw status code, with a decoded meaning derived from GMD_SAMPLE_STATUS.
• ASSAY_CODE, ASSAY_DESC, QCASSY_TYP_ID — assay classification.
• ITEM_ID, ITEM_NO, ITEM_DESC1, ITEM_UM, ITEM_UM2 — item context for the tested material.
• LOT_ID, LOT_NO, SUBLOT_NO — lot traceability.
• TARGET_SPEC, MIN_SPEC, MAX_SPEC, TEXT_SPEC — specification limits.
• ACCEPT_ANYWAY, FINAL_MARK, ASSAY_RETEST, WF_RESPONSE — disposition and workflow-related flags.
• PARTY_NUMBER, PARTY_NAME, VENDOR_NO, VENDOR_NAME — customer and vendor context.

Common Use Cases and Queries

Typical uses include quality result reporting, sample status tracking, and COA data extraction. To retrieve results with decoded sample status:

• SELECT sample_no, sample_desc, sample_status, item_no, assay_code, num_result, result_date FROM apps.pmibv_qcresult_v WHERE sample_status = :status;
• SELECT sample_no, item_no, mini_spec FROM apps.pmibv_qcresult_v WHERE final_mark = 'Y' ORDER BY result_date DESC;
• Join to lookups for reporting on GMD_SAMPLE_STATUS meanings, or filter by ORGN_CODE for organization-level security.