Search Results qa_audit_pkg




Overview
Explore in AI Chat

Overview

QA_AUDIT_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under Quality Management (QA) functionality. It is part of the Oracle Quality module and supports the audit and collection-planning features used to define inspections, capture results, and link quality plans to production activity. The package status is VALID in the ETRM repository for both Oracle EBS 12.1.1 and 12.2.2.

The primary purpose of QA_AUDIT_PKG is to provide programmatic logic for manipulating quality collection questions and associated audit data. Its documented API is exposed through a companion wrapper, QA_AUDIT_PKG_W, which follows the standard Oracle EBS convention of separating the core package from a wrapper used by forms and other client-side invocations. The package therefore acts as a server-side utility within the Quality schema, while QA_AUDIT_PKG_W provides the callable interface for user-facing transactions.

Consistent with its classification as an OTHER API (that is, not a formally published public API), QA_AUDIT_PKG is intended mainly for internal use by Oracle Quality components rather than for direct customer extension. This distinction is important because Oracle does not guarantee upward compatibility for non-public APIs, and customizations that call the core package directly may be affected by patching or upgrades.

Key Procedures and Functions

The ETRM metadata documents a single procedure in QA_AUDIT_PKG:

  • COPY_QUESTIONS — Copies quality collection questions from a source context to a target context. This supports the ability to replicate an existing quality collection plan, audit template, or question set so that repeat inspections can reuse standardized questions without manual re-entry. The procedure underpins the "copy" actions available within Quality collection plan maintenance and audit setup. Parameter lists are not published in the ETRM metadata and should not be assumed; callers should reference the wrapper package QA_AUDIT_PKG_W or the underlying package specification in the database for the exact signature.

No additional public functions or procedures are documented in the provided metadata. Internal/private program units may exist in the package body but are outside the scope of the ETRM record.

Tables Accessed

The package references the following tables through APPS synonyms, in addition to standard SYS constructs (STANDARD, DUAL, DBMS_SQL, PLITBLM):

  • QA_COLLECTION_ID_S — Sequence used to generate unique collection identifiers when new quality collections or question records are created.
  • QA_PC_PLAN_RELATIONSHIP — Stores relationships between quality collection plans and their parent plans, supporting plan hierarchies and question inheritance during copy operations.
  • QA_PLAN_CHARS — Holds the characteristics (questions) defined on a collection plan; the principal source and target for question copy logic.
  • QA_RESULTS — Contains collected quality results associated with plan characteristics; referenced when question definitions are validated against existing result data.
  • MTL_MATERIAL_TRANSACTIONS_S — Sequence for material transaction identifiers, used where quality collections are tied to inventory transactions.
  • DBMS_SQL / DUAL / PLITBLM — Utility references for dynamic SQL and PL/SQL table management.

Usage Notes

QA_AUDIT_PKG is typically invoked indirectly. In standard Oracle Quality flows, the Oracle Forms-based collection plan and audit setup screens call QA_AUDIT_PKG_W, which in turn delegates to QA_AUDIT_PKG. The metadata records that QA_AUDIT_PKG is referenced by QA_AUDIT_PKG_W (one dependent package), confirming this wrapper relationship.

Because the package is classified as OTHER, it is not recommended as a target for customer extensions. Where custom code must replicate question-copy behavior, the supported approach is to invoke the wrapper QA_AUDIT_PKG_W or to use the documented Quality public APIs. Any direct call to COPY_QUESTIONS should be validated against the package specification in the target EBS release (12.1.1 or 12.2.2), since signatures for non-public APIs can change between patch levels.