Search Results allowed_for_plan

Overview

QA_WEB_TXN_API is a public PL/SQL package owned by the APPS schema that serves as the application programming interface for Oracle Quality collection plan transaction processing in Oracle E-Business Suite. Its principal business purpose is to evaluate collection plans against an in-progress transaction context, determine which quality plans are applicable or mandatory, and persist collected results back into the Quality schema. The package bridges the Oracle Quality data model with the transaction-generating modules — most notably Oracle Work in Process, Oracle Enterprise Asset Management, and the Quality Workbench — by abstracting the logic that decides when a plan should fire, whether a mandatory plan remains unmet, and how results are written once collected.

The package is classified as an API in the ETRM documentation for 12.2.2 and is present as VALID in both 12.1.1 and 12.2.2. It has both a specification and a body, is dependent on the SQL STANDARD package, and is referenced by six other packages and one view.

Key Procedures and Functions

The package exposes ten documented procedures and functions:

• QUALITY_PLANS_APPLICABLE — Determines whether any collection plans are applicable to the current transaction context.
• QUALITY_MANDATORY_PLANS_REMAIN — Tests whether mandatory collection plans for the transaction remain outstanding, supporting enforcement of quality gating before a transaction is allowed to complete.
• BACKGROUND_PLAN — Identifies or initiates a background plan record associated with the transaction.
• ALLOWED_FOR_PLAN — Validates whether the current transaction is permitted under a given plan.
• PLAN_APPLIES — Evaluates applicability rules for a specific plan.
• QUALITY_POST_COMMIT_PROCESSING — Performs quality-related processing after the transaction commit, such as follow-on plan invocation.
• GET_MANDATORY_OPTIONAL_INFO — Returns mandatory/optional classification information for the plans attached to a transaction.
• POST_BACKGROUND_RESULTS — Writes background-collected results to the Quality tables.
• IS_WORKBENCH_TXN — Determines whether the current transaction originated from the Quality Workbench.
• GET_RESULT_ENTERED — Checks whether a result has already been entered for the transaction.

Tables Accessed

The package operates against the core Quality tables through APPS synonyms, including QA_PLANS, QA_CHARS, QA_PC_PLAN_RELATIONSHIP, QA_PLAN_COLLECTION_TRIGGERS, QA_PLAN_TRANSACTIONS, QA_TXN_COLLECTION_TRIGGERS, and QA_RESULTS. These support plan definition, characteristic definition, parent-child plan relationships, trigger evaluation, and result storage. It also reads WIP_ENTITIES to resolve the Work in Process entity context, FND_USER for session identity, and DUAL/PLITBLM for utility operations.

Usage Notes

QA_WEB_TXN_API is not invoked directly by end users; it is consumed by module-private packages. Its documented callers include EAM_ASSET_OPERATION_TXN_PVT, EAM_PROCESS_WO_PVT, and EAM_WORKORDERREP_PVT within Oracle Enterprise Asset Management, together with QA_AUDIT_PKG, QA_PARENT_CHILD_PKG, and the QA_RESULTS_QWB_V view. This dependency pattern confirms the package is the shared engine behind quality collection in EAM work orders, audits, and the web-based Quality Workbench. Customizations that need to determine plan applicability or post results during a transaction should call these documented APIs rather than manipulating QA tables directly, and should be aware that mandatory-plan enforcement delegates to QUALITY_MANDATORY_PLANS_REMAIN before commit.