Search Results alternate_plan_name

Overview

The QA_SKIPLOT_PROCESS_PLANS_V view is a documented Oracle E-Business Suite object owned by the APPS schema within the QA (Quality) product family. It exposes configuration data for skip lot process plans — the rules that determine when a receiving or collection plan may reduce its inspection frequency for a supplier, item, or process. Skip lot processing is a core Oracle Quality capability that allows organizations to accept material less frequently when a supplier or item has demonstrated consistent conformance to specification, while automatically reverting to full inspection when a rejection or process exception occurs.

The view is most commonly referenced by reporting, integration, and troubleshooting scenarios rather than by end-user forms. Because it flattens the relationship between a primary collection plan and an optional alternate plan into a single row per process/plan assignment, it provides a convenient denormalized source for BI Publisher reports, custom concurrent programs, and analytics that need to resolve the alternate plan name without performing a separate join on QA_PLANS. This is precisely why searches for the alternate_plan_name column typically lead to this view; it is one of the few documented APPS objects that surfaces the alternate plan name as a named, query-ready column.

Underlying Base Objects

The view is defined over four referenced base objects as documented in the ETRM metadata:

• QA_SKIPLOT_PROCESS_PLANS (SYNONYM) — the primary driving table, aliased QSPP. It stores the association between a skip lot process and the collection plans (primary and alternate) assigned to it.
• QA_PLANS (SYNONYM) — joined twice (aliases QP1 and QP2) to resolve the primary and alternate plan identifiers into their user-visible names.
• FND_COMMON_LOOKUPS (VIEW) — joined twice (aliases FCL1 and FCL2) against the lookup type COLLECTION_PLAN_TYPE to translate plan type codes into descriptive meanings.
• FND_GLOBAL (PACKAGE) — referenced indirectly for the standard WHO columns (LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN).

All joins use Oracle outer-join syntax with the (+) operator, making the alternate plan and its lookup description optional for a given row.

Key Columns

• ROW_ID — the ROWID of the underlying QA_SKIPLOT_PROCESS_PLANS record.
• PROCESS_PLAN_ID — surrogate key of the process-plan association record.
• PROCESS_ID — the skip lot process to which the plan assignment belongs.
• PLAN_ID / PLAN_NAME / PLAN_TYPE — the primary collection plan identifier, its QA_PLANS name, and the translated collection plan type meaning.
• ALTERNATE_PLAN_ID / ALTERNATE_PLAN_NAME / ALT_PLAN_TYPE — the optional alternate collection plan, its QA_PLANS name, and translated plan type. ALTERNATE_PLAN_NAME is populated only when an alternate plan is configured.
• WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN for audit and change tracking.

Common Use Cases and Queries

Typical scenarios include listing all skip lot process plans and their alternates, auditing which processes lack an alternate plan, and feeding downstream reporting with the alternate plan name. A representative query follows.

SELECT process_id,
       plan_name,
       plan_type,
       alternate_plan_name,
       alt_plan_type
FROM   apps.qa_skiplot_process_plans_v
WHERE  alternate_plan_name IS NOT NULL
ORDER  BY process_id;

To identify processes with no alternate configured, invert the predicate using IS NULL. For change-audit reporting, filter on last_update_date. Because the view resolves both plan names and lookup meanings, it removes the need for custom joins in most skip lot reporting requirements.