Search Results create_collection_plan

Overview

QA_PLANS_PUB is a public PL/SQL API package in the Oracle E-Business Suite Quality Management (QA) module, owned by the APPS schema. It exposes the core business logic used to create, maintain, and process collection plans and their associated plan elements. Collection plans in Oracle Quality define the specification of what data is to be collected, from which organizations, items, and resources, and under which conditions results are recorded. The package serves as the canonical programmatic entry point for working with these plans, shielding callers from the underlying tables and validation logic. Based on the ETRM metadata for 12.2.2, QA_PLANS_PUB is classified as a PUB (public) API, meaning it is intended for use by other application modules and by customer extensions. It depends on the FND_API utility package, indicating consistent use of Oracle Application Object Library error and message handling conventions such as the standard API error stack.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions within QA_PLANS_PUB:

• CREATE_COLLECTION_PLAN — Creates a new collection plan with its defining attributes and associated setup.
• ADD_PLAN_ELEMENT — Adds an element (characteristic, action, or similar component) to an existing collection plan.
• COMPLETE_PLAN_PROCESSING — Finalizes processing of a collection plan, committing related records and completing the transaction cycle.
• DELETE_COLLECTION_PLAN — Removes a collection plan and its related definition from the system.
• DELETE_PLAN_ELEMENT — Removes a single element from a collection plan definition.
• COPY_COLLECTION_PLAN — Duplicates an existing collection plan into a new plan, preserving its structure and elements.
• GET_PLAN_TYPE — Retrieves the type classification of a collection plan.
• GET_PLAN_VIEW_NAME — Returns the database view name associated with a plan, used for dynamic data retrieval against collected results.
• GET_IMPORT_VIEW_NAME — Returns the view name used when importing collection plan data.

No parameter lists are documented in the ETRM excerpt; callers should reference the package specification for exact signatures.

Tables Accessed

The package reads and writes several base and seed tables via APPS synonyms. QA_PLANS and its shadow table QA_PLANS_S store the primary collection plan definitions. QA_PLAN_CHARS holds the characteristic-level detail for each plan. QA_CHAR_INDEXES and QA_DEVICE_INFO support index and device-related plan configuration. The package also interacts with the Oracle Alert infrastructure through ALR_ACTIONS, ALR_ACTIONS_S, ALR_ACTION_SETS, ALR_ACTION_SETS_S, and ALR_ACTION_SET_MEMBERS and ALR_ACTION_SET_MEMBERS_S, reflecting the tight integration between collection plans and action-driven alerting. The QA-owned name tables QA_ALR_ACTION_NAME_S and QA_ALR_ACTION_SET_NAME_S store customer-defined action and action-set names. FND_LOOKUP_VALUES and FND_USER provide standard lookup and user validation.

Usage Notes

QA_PLANS_PUB is typically invoked from Oracle Quality forms (such as the Collection Plans setup forms), from concurrent programs performing bulk plan maintenance or copying, and from custom extensions that need to provision collection plans programmatically. Because it is a PUB-classified API, it is the supported interface for external callers, and direct DML against QA_PLANS or QA_PLAN_CHARS should be avoided in favor of these procedures. The dependency on FND_API means callers should inspect the standard API error messages after each invocation. It is also referenced by QA_PARENT_CHILD_COPY_PKG, reflecting its role in parent-child plan copy operations, and it calls itself for internal recursion or shared logic.