Search Results enable_qa_results

Overview

QA_RESULT_GRP is a public PL/SQL group API in the Oracle EBS Quality Management module, owned by the APPS schema and classified as a Group (GRP) API. It provides the supported programmatic interface for bulk lifecycle operations against Quality Results records in Oracle Quality. Specifically, the package performs deletion, enabling (activation), and status management of quality results that are associated with a given collection identifier. The API abstracts the underlying base-table manipulation and validation required to move results between their disabled and enabled states, and it is also the mechanism through which result-related workflow actions can be fired. The package declaration carries the AUTHID CURRENT_USER directive, meaning it executes with the privileges of the calling user rather than the definer, and the header comment identifies the current version as 1.0. In EBS 12.1.1 and 12.2.2, this package functions as the standard integration point for custom code and concurrent processing that must purge, enable, or otherwise manage quality results without directly touching the QA base tables.

Key Procedures and Functions

The documented API exposes eight procedures and functions. Their purposes, as recorded in the ETRM metadata, are as follows:

• PURGE — Deletes Quality Results for a given collection identifier. This is the entry point for clearing results that are no longer required.
• ENABLE — Enables Quality Results for a given collection identifier by updating result status.
• ENABLE_QA_RESULTS — The functional variant of the enable operation, applying the enabling logic to quality results associated with the collection.
• ENABLE_AND_FIRE_ACTION — Enables results and additionally triggers the associated Oracle Workflow or Quality action, so that downstream processing is initiated in the same call.
• GET_QA_RESULTS_ERECORDS — Retrieves the result e-records (electronic records) associated with the given context.
• ENABLE_RESULTS_ERECORDS — Enables the results and their corresponding e-records as a combined operation.
• PURGE_RESULTS_ERECORDS — Purges results together with their associated e-records.
• PURGE_INVALID_RESULTS — Removes results that failed validation or are otherwise considered invalid, supporting cleanup of rejected data.

The procedures follow Oracle Application Object Library API conventions, returning a status indicator with values such as S (success), E (error), and U (unexpected error), alongside message count and message data outputs for error reporting. Callers are expected to pass an API version number and to honour the commit and validation-level parameters.

Tables Accessed

The package operates against several base and supporting tables through APPS synonyms. QA_RESULTS is the primary table, holding the Quality Results that are enabled or purged. QA_PC_RESULTS_RELATIONSHIP links results to the collection context that the API parameters reference. QA_ACTION_LOG records the actions fired when workflow-enabled enablement is requested. EDR_PSIG_DOCUMENTS and the related e-record handling support the electronic signature and electronic record requirements referenced by the ENABLE_RESULTS_ERECORDS and PURGE_RESULTS_ERECORDS procedures. MTL_MATERIAL_TRANSACTIONS_TEMP is referenced in support of results tied to pending inventory transactions. The package also uses DBMS_SQL for dynamic SQL and PLITBLM for PL/SQL index-by table management used in bulk processing.

Usage Notes

QA_RESULT_GRP is typically invoked from Oracle Quality forms, from concurrent programs that mass-enable or purge results, and from custom PL/SQL that must manage results for a collection without direct DML against QA_RESULTS. Because the package is referenced by eleven other packages, changes to it can affect a wide surface area of Quality functionality, and custom callers should always check the returned p_return_status rather than assuming success. The ENABLE_AND_FIRE_ACTION variant should be used whenever downstream actions must accompany enablement. In 12.1.1 and 12.2.2, the online form behaviour relies on this API, so direct table updates are neither supported nor recommended.