Search Results lot_optional_on_sample

Overview

The APPS.PMITS_QC_ALL_SPEC_VRS_V view belongs to the Process Manufacturing Intelligence (PMI) product family within Oracle E-Business Suite, a module classified as obsolete in release 12.1.1 and 12.2.2. It exposes information about Specification Validity Rules defined in the Oracle Process Manufacturing (OPM) Quality Control module. Specification validity rules govern the time-bounded applicability of a specification version to a given item, grade, lot, sublot, warehouse, or location, and they carry a substantial set of control flags that determine sampling behaviour, certificate of analysis (COA) generation, and lot attribute handling.

The view is a denormalised reporting construct. Rather than requiring report authors to resolve meaning codes, decode indicator flags, and join multiple QC and Oracle master tables individually, the view performs the joins and the DECODE translations internally. Each indicator column that stores a single-character flag (Y or N) is presented alongside a companion _DISP column that returns the corresponding lookup meaning. Typical users are OPM QC analysts, quality managers, and developers building PMI dashboards, extracts, or interface programs that must present validity-rule configuration in human-readable form.

Underlying Base Objects

The ETRM metadata for release 12.2.2 documents the referenced base objects for this view as DUAL (a synonym), which reflects only the minimal object dependency recorded in the dictionary extract and does not represent the true data lineage. The view text itself references the validity-rule source table through the alias GASV (the OPM QC specification validity/specification table, e.g. GMD_SPEC_VALIDITY_RULES and its related specification tables in the GMD schema), together with lookup and seed-data sources referenced by aliases such as QC_SOURCE, FLY, FLN, and COA_IND. The FLY and FLN aliases supply the "Yes" and "No" lookup meanings used by the DECODE expressions, while QC_SOURCE resolves the specification type and COA_IND resolves the COA type.

Because the view draws on OPM QC tables owned by the GMD schema and lookups maintained in the Application Object Library, its availability is contingent on the OPM QC and PMI schemas being installed and on the relevant lookup types being populated. Organizations that have not licensed or implemented OPM QC will find the view empty or the source objects absent.

Key Columns

• SPEC_VR_ID, SPEC_ID, SPEC_NAME, SPEC_VERS, SPEC_TYPE, SPEC_TYPE_DISP — identity and classification of the specification version and its validity rule.
• ORGN_CODE, ITEM_ID, ITEM_NO, GRADE, LOT_ID, LOT_NO, SUBLOT_NO, WHSE_CODE, LOCATION — the scope to which the rule applies.
• SPEC_STATUS, SPEC_STATUS_DESC, SPEC_VR_STATUS, SPEC_VR_STATUS_DESC, START_DATE, END_DATE — lifecycle state and effective dating of the specification and its validity rule.
• SAMPLING_PLAN_ID — the sampling plan associated with the rule.
• SAMPLE_INV_TRANS_IND and SAMPLE_INV_TRANS_IND_DISP — the indicator controlling whether a sample triggers an inventory transaction, and its decoded Yes/No display value. This column pair is the object of the search term sample_inv_trans_ind_disp.
• CONTROL_LOT_ATTRIB_IND/_DISP, CONTROL_BATCH_STEP_IND/_DISP, LOT_OPTIONAL_ON_SAMPLE — lot and batch control behaviour flags.
• OUT_OF_SPEC_LOT_STATUS, IN_SPEC_LOT_STATUS — lot status codes applied when a result is out of specification or in specification.
• COA_TYPE/COA_TYPE_DISP, COA_AT_SHIP_IND/_DISP, COA_AT_INVOICE_IND/_DISP, COA_REQ_FROM_SUPL_IND/_DISP — certificate of analysis configuration and its decoded display values.
• BATCH_ID, RECIPE_ID/RECIPE_NO/RECIPE_VERSION, FORMULA_ID/FORMULALINE_ID/FORMULA_NO/FORMULA_VERS, ROUTING_ID, STEP_ID, OPRN_ID, CHARGE — process manufacturing context linking the rule to batch, recipe, formula, routing, and operation.
• CUST_ID, ORDER_ID, ORDER_LINE, ORDER_LINE_ID, SHIP_TO_SITE_ID, SUPPLIER_ID, SUPPLIER_SITE_ID, PO_HEADER_ID, PO_LINE_ID, ORG_ID — commercial and multi-org context for customer orders and supplier purchase orders.

Common Use Cases and Queries

The principal use case is reporting on specification validity rule configuration, particularly the sampling and inventory transaction behaviour controlled by SAMPLE_INV_TRANS_IND. A quality analyst may wish to identify every item for which sampling generates an inventory transaction.

• Retrieve rules that create inventory transactions on sampling:
  SELECT item_no, spec_name, spec_vers, sample_inv_trans_ind_disp FROM apps.pmits_qc_all_spec_vrs_v WHERE sample_inv_trans_ind = 'Y' AND orgn_code = :org;
• List currently effective validity rules for a lot:
  SELECT spec_name, spec_vers, spec_vr_status_desc, start_date, end_date FROM apps.pmits_qc_all_spec_vrs_v WHERE lot_no = :lot AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE);
• Report COA configuration across specifications:
  SELECT spec_name, coa_type_disp, coa_at_ship_ind_disp, coa_at_invoice_ind_disp FROM apps.pmits_qc_all_spec_vrs_v ORDER BY spec_name;

Because the view exposes ORG_ID and ORGN_CODE, queries should be filtered by operating unit in a multi-org environment to avoid cross-organisation data leakage. Given the obsolete status of PMI in 12.1.1 and 12.2.2, organizations migrating off PMI should treat this view as a read-only reporting artifact and redirect any downstream integration to the underlying OPM QC tables or to supported replacement functionality.