Search Results collection_plan_type




Overview
Explore in AI Chat

Overview

APPS.QA_SKIPLOT_PROCESS_PLANS_V is a reporting and integration view in Oracle E-Business Suite that exposes the relationship between skip-lot process definitions and their associated collection plans. Skip-lot processing is a quality sampling technique in which, after a defined number of conforming lots, inspection frequency is reduced. The underlying table QA_SKIPLOT_PROCESS_PLANS stores the assignment of a primary collection plan and an optional alternate collection plan to a given skip-lot process, and this view enriches those rows with the plan names and the decoded plan type meanings.

The view is significant because it resolves the numeric type codes held on QA_PLANS into human-readable meanings drawn from FND_COMMON_LOOKUPS under the lookup type COLLECTION_PLAN_TYPE. The user search term "collection_plan_type" maps directly to this decode: the view joins to FND_COMMON_LOOKUPS twice, once for the primary plan and once for the alternate, exposing the meanings as PLAN_TYPE and ALT_PLAN_TYPE respectively. This makes the view suitable for operational reports, dashboards, and interface programs that must present skip-lot plan assignments without embedding lookup logic themselves.

The view is owned by APPS and is available in both EBS 12.1.1 and 12.2.2. Note that the view text references FND_GLOBAL as a package, reflecting the standard EBS practice of deriving auditing context (such as LAST_UPDATED_BY and CREATED_BY) through global session values.

Underlying Base Objects

The documented base objects underlying this view are:

  • QA_SKIPLOT_PROCESS_PLANS (synonym) — the driving table, aliased QSPP, holding the process-to-plan assignment records.
  • QA_PLANS (synonym) — referenced twice, as QP1 for the primary plan and QP2 for the alternate plan, supplying plan names and plan type codes.
  • FND_COMMON_LOOKUPS (view) — referenced twice, as FCL1 and FCL2, supplying decoded meanings for the COLLECTION_PLAN_TYPE lookup.
  • FND_GLOBAL (package) — the session context package used in the EBS auditing model.

The join structure is a standard outer-join pattern: QSPP.PLAN_ID = QP1.PLAN_ID is an inner join because a primary plan is mandatory, whereas QSPP.ALTERNATE_PLAN_ID = QP2.PLAN_ID (+) and the associated lookup join on FCL2 are outer joins because the alternate plan is optional. Similarly, FCL1.LOOKUP_TYPE = 'COLLECTION_PLAN_TYPE' and FCL2.LOOKUP_TYPE (+) = 'COLLECTION_PLAN_TYPE' constrain the lookup joins, with QP1.PLAN_TYPE_CODE = FCL1.LOOKUP_CODE and QP2.PLAN_TYPE_CODE = FCL2.LOOKUP_CODE (+) completing the decode. The PLAN_TYPE_CODE on QA_PLANS therefore drives the meaning returned.

Key Columns

  • ROW_ID — the rowid of the underlying QA_SKIPLOT_PROCESS_PLANS row, exposed for updateable-view and tooling purposes.
  • PROCESS_PLAN_ID — primary key identifying the specific process-to-plan assignment.
  • PROCESS_ID — the skip-lot process to which the plan assignment belongs.
  • PLAN_ID / PLAN_NAME / PLAN_TYPE — the primary collection plan identifier, its name, and the decoded COLLECTION_PLAN_TYPE meaning.
  • ALTERNATE_PLAN_ID / ALTERNATE_PLAN_NAME / ALT_PLAN_TYPE — the optional alternate plan and its decoded type; these are null when no alternate plan is defined.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns supporting change tracking and conformance reporting.

Common Use Cases and Queries

Typical uses include reporting all plans assigned to a skip-lot process, verifying that alternate plans are configured, and filtering assignments by plan type. The view removes the need to hand-code the COLLECTION_PLAN_TYPE decode.

Example: list all skip-lot process plan assignments with decoded types.

SELECT process_id, process_plan_id, plan_name, plan_type, alternate_plan_name, alt_plan_type FROM apps.qa_skiplot_process_plans_v ORDER BY process_id;

Example: retrieve only processes that use a specific plan type, using the user's search term.

SELECT process_id, plan_id, plan_name, plan_type FROM apps.qa_skiplot_process_plans_v WHERE plan_type = 'Sampling' OR alt_plan_type = 'Sampling';

Example: identify processes lacking an alternate plan.

SELECT process_id, plan_name FROM apps.qa_skiplot_process_plans_v WHERE alternate_plan_id IS NULL;

Because the view joins through FND_COMMON_LOOKUPS, any modification to the COLLECTION_PLAN_TYPE lookup meanings is reflected automatically, ensuring reports remain aligned with setup configuration.