Results for “text_spec”

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

Overview

PMIBV_QC_SPECIFICATIONS_V is an APPS-owned database view in Oracle E-Business Suite, catalogued as a "QC Specifications Base View" under the product family PMI — Process Manufacturing Intelligence. In ETRM 12.2.2 the object is marked VALID, while PMI itself is flagged as obsolete; the view therefore survives principally as a legacy reporting and integration surface rather than as an actively enhanced component. Its purpose is to flatten the master quality-control specification record (QC_SPEC_MST) into a single denormalized row that carries the specification limits, the associated assay or quality-control unit, and the resolved descriptive attributes of the customer, item, vendor, and lot to which the specification applies.

Because the view resolves surrogate identifiers into human-readable values — customer number and name instead of CUST_ID, item number and description instead of ITEM_ID, vendor number and name, and lookup meanings for indicator flags — it is well suited to ad hoc queries, concurrent-program extracts, and inbound/outbound interface staging where a specification must be presented in business terms. The presence of the alias ROUTING_STEP_NUMBER (sourced from QC_SPEC_MST.ROUTINGSTEP_NO), which directly matches the search term "routing_step_number," makes this view relevant when tracing QC specifications that are tied to a specific routing step.

Underlying Base Objects

The view is defined over QC_SPEC_MST, the master specification table, which supplies the core specification attributes and the CUST_ID and LOT_ID foreign keys. HZ_CUST_ACCOUNTS_ALL and HZ_PARTIES are outer-joined to resolve the customer account and party details. IC_ITEM_MST supplies item number and description, IC_LOTS_MST supplies lot and sub-lot numbers, and PO_VEND_MST supplies vendor identity. FND_LOOKUPS is referenced twice (aliased COALKUP and ACTIVELKUP) to translate the vendor certificate-of-analysis requirement and the effective-status flag into their display meanings. Documented referenced objects include the FND_GLOBAL package, together with synonyms for HZ_CUST_ACCOUNTS_ALL, HZ_PARTIES, IC_ITEM_MST, IC_LOTS_MST, PO_VEND_MST, and QC_SPEC_MST. All joins to the descriptive entities are outer joins (the (+) notation), so a specification row is retained even when customer, lot, item, or vendor data is missing.

Key Columns

• QUALITY_CONTROL_SPEC_ID, ASSAY_TYPE_ID, ASSAY_CODE — the specification identifier and its associated assay.
• ROUTING_STEP_NUMBER — the routing step to which the specification is attached.
• ORGANIZATION_CODE, WAREHOUSE_CODE, LOCATION — the organizational scope of the specification.
• MIN_SPEC, MAX_SPEC, TARGET_SPEC, TEXT_SPEC — specification limits and textual instructions.
• QUALITY_CONTROL_UNIT_CODE — the unit of measure for the limits above.
• FROM_DATE, TO_DATE, EFFECTIVE — validity window and active status.
• VENDOR_SPECIFICATION, VENDOR_CERTIFICATION, CUSTOMER_SPECIFICATION, CUSTOMER_CERTIFICATION, VENDOR_COA_REQUIRED — specification/ certification flags.
• CUSTOMER_NUMBER, CUSTOMER_NAME, ITEM_NUMBER, ITEM_DESCRIPTION, VENDOR_NUMBER, VENDOR_NAME, LOT_NUMBER, SUB_LOT_NUMBER — resolved descriptive attributes.
• Placeholder columns (FORMULA_NUMBER, BATCH_NUMBER, ROUTING_NUMBER, OPERATION_NUMBER) are hard-coded constants, not real data.

Common Use Cases and Queries

The view is typically used to list specifications for a given item or customer, to audit limits in force on a given date, and to identify specifications bound to routing steps.

SELECT quality_control_spec_id, item_number, routing_step_number,
       min_spec, max_spec, target_spec, effective
FROM   apps.pmibv_qc_specifications_v
WHERE  item_number = :item
AND    effective = 'Y';

Because PMI is obsolete, consumers should validate the view on the target release and pin queries to the documented column list.