Search Results out_of_action_interval




Overview
Explore in AI Chat

Overview

APPS.PMIFV_QC_SPECIFICATIONS_V is a reporting and integration view in the Oracle E-Business Suite Process Manufacturing (OPM) module. In the ETRM 12.2.2 metadata it is registered under the FND Design Data name PMI.PMIFV_QC_SPECIFICATIONS_V, is owned by the APPS schema, and carries a status of VALID. The view consolidates quality control specification records — the rules that define acceptable assay values for items, lots, customers, and vendors — into a single denormalized projection. Because it joins specification header data to descriptive attributes of the customer, vendor, item, lot, and routing, it is well suited to ad hoc queries, custom reports, and interfaces that require specification context without navigating the underlying normalized OPM tables individually.

The user search term "out_of_action_interval" corresponds directly to the OUT_OF_ACTION_INTERVAL column. This numeric column works in conjunction with OUT_OF_ACTION_CODE to describe the action to take when a specification is violated — for example, how long a hold, quarantine, or re-test condition persists before the material is released or dispositioned. Reporting on this column is common in quality dashboards and deviation analyses.

Underlying Base Objects

The documented base objects underlying the view are FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), HZ_CUST_ACCOUNTS_ALL (SYNONYM), HZ_PARTIES (SYNONYM), IC_ITEM_MST (SYNONYM), IC_LOTS_MST (SYNONYM), PO_VEND_MST (SYNONYM), and QC_SPEC_MST (SYNONYM). The primary driving table is QC_SPEC_MST, the OPM quality control specification master. It is enriched with item data from IC_ITEM_MST, lot data from IC_LOTS_MST, vendor data from PO_VEND_MST, and customer data from the Oracle Receivables/Party model via HZ_CUST_ACCOUNTS_ALL and HZ_PARTIES. FND_LOOKUPS supplies translated lookup meanings, and FND_GLOBAL supplies session context such as the current organization and user.

Key Columns

The view exposes the specification identifier QUALITY_CONTROL_SPEC_ID and ASSAY_TYPE_ID, along with descriptive spec attributes: ASSAY_CODE, TEXT_SPEC, MIN_SPEC, MAX_SPEC, TARGET_SPEC, and QUALITY_CONTROL_UNIT_CODE. Validity windows are defined by FROM_DATE and TO_DATE. Quality action behavior is captured by OUT_OF_ACTION_CODE and OUT_OF_ACTION_INTERVAL, with PREFERENCE ranking competing specifications. Document and certification flags include DOCUMENT_TYPE, VENDOR_SPECIFICATION, VENDOR_CERTIFICATION, CUSTOMER_SPECIFICATION, CUSTOMER_CERTIFICATION, VENDOR_COA_REQUIRED, PRINT_COA_SHIPPED, and PRINT_COA_INVOICED. Context columns include ORGANIZATION_CODE, WAREHOUSE_CODE, LOCATION, ITEM_NUMBER, LOT_NUMBER, BATCH_NUMBER, ROUTING_NUMBER, and the customer and vendor identifiers and names.

Common Use Cases and Queries

Typical uses include identifying specifications that trigger a hold, auditing which customers have customer-specific specifications, and driving certificate-of-analysis printing logic. The following query lists active specifications with their out-of-action handling for a given item:

  • SELECT quality_control_spec_id, item_number, lot_number, assay_code, out_of_action_code, out_of_action_interval, min_spec, max_spec, target_spec, from_date, to_date FROM apps.pmifv_qc_specifications_v WHERE item_number = 'ITEM-1001' AND TRUNC(SYSDATE) BETWEEN from_date AND to_date;
  • Filter by ORGANIZATION_CODE to scope results to the current plant.
  • Filter by CUSTOMER_NUMBER or VENDOR_NUMBER for trading-partner-specific specifications.

Because the view already resolves lookup and party descriptions, it reduces the join effort required for specification reporting and is a practical foundation for custom quality reports and integration extracts in both 12.1.1 and 12.2.2.