Search Results enable_and_fire_actions

Overview

QA_RESULTS_PUB is a public PL/SQL package in the APPS schema that provides the externalized application programming interface for Oracle Quality results processing within Oracle E-Business Suite. While the companion specification defines the callable surface, the package body (APPS.QA_RESULTS_PUB, status VALID) contains the implementation that bridges generic callers — Oracle Forms, concurrent programs, and custom extensions — to the underlying Quality results infrastructure. It encapsulates the creation and modification of quality results records, wraps validation and action-firing logic, and exposes explicit commit semantics to callers.

Functionally the package serves as a thin but authoritative layer over QA_RESULTS_API and the related Quality APIs. Its body is documented as depending on FND_API (the standard EBS API framework providing return-status and message-stack conventions), FND_MESSAGE and FND_MSG_PUB (message retrieval and publication), FND_GLOBAL (session context such as user and responsibility), QA_PLAN_ELEMENT_API, QA_VALIDATION_API, and QA_SS_RESULTS. This dependency set confirms that results insertion, update, validation, and action firing are orchestrated here rather than left to individual consumers.

Key Procedures and Functions

The ETRM metadata documents four callable entry points on this package:

• INSERT_ROW — Inserts a quality results record. This is the primary creation entry point for results data and is the routine most commonly invoked by forms and external integrations when new result rows must be persisted.
• UPDATE_ROW — Modifies an existing quality results record, allowing attribute changes to previously created results while preserving the package's validation and messaging conventions.
• ENABLE_AND_FIRE_ACTION — Enables and executes the action associated with a quality result, delegating to the Quality action/validation infrastructure. This supports the Quality module's business rule that result values can trigger configured actions.
• COMMIT_QA_RESULTS — Provides an explicit commit boundary for results processing, giving callers controlled transaction finalization consistent with the FND_API convention of separating API invocation from commit.

All four procedures follow the standard EBS API pattern of returning status and reporting errors through the FND message stack; parameter lists are intentionally not reproduced here.

Tables Accessed

The documented table reference for this package body is PLITBLM, accessed via an APPS synonym. PLITBLM is a standard Oracle-supplied PL/SQL index-table support object rather than an application table. No direct application-level DML against Quality base tables is documented for this body; persistence of results is performed indirectly through QA_RESULTS_API, consistent with the layering visible in the dependency list. Consumers requiring knowledge of the physical results tables should consult QA_RESULTS_API and its own dependencies.

Usage Notes

QA_RESULTS_PUB is an API-classified public package and is referenced by six other database objects, indicating it is a shared integration point rather than an internal implementation detail. Typical invocation paths include Oracle Quality forms and concurrent programs that record or amend results, and custom code or interfaces that need to create results programmatically. Because the package relies on FND_API messaging and exposes COMMIT_QA_RESULTS, callers should invoke the row-level procedures first and commit explicitly, checking the returned status and inspecting the FND message stack on error. The package is documented as not referenced by any database object in the dependency sense, meaning it is a top-level callable surface intended for external consumers. Behavior is consistent across 12.1.1 and 12.2.2, with no 12.2-specific changes documented in the metadata.