Search Results commit_qa_results

Overview

QA_RESULTS_API is a public PL/SQL package owned by the APPS schema that encapsulates the core business logic for creating, modifying, and finalizing quality results records in Oracle Quality. Quality results represent the captured measurement, specification, and collection data generated when an inspection, test, or data collection plan is executed against a material, lot, or transaction. Rather than allowing forms and other modules to write directly to the QA_RESULTS base table, this API provides a controlled, validated programmatic interface that enforces the integrity of the results model.

The package is classified as an API in the ETRM metadata and is recorded as VALID in the APPS schema. It depends on FND_GLOBAL for session context such as the responsible user and login, on QA_VALIDATION_API for specification and result validation, and on the STANDARD package from SYS for standard PL/SQL runtime services. Its presence in the Quality module makes it a foundational component for any extension, interface, or integration that must load or adjust quality results outside the standard Oracle Quality forms.

Key Procedures and Functions

• INSERT_ROW — Creates a new quality results record. This is the primary entry point for populating QA_RESULTS when results are generated programmatically, such as during data collection import or results migration.
• UPDATE_ROW — Modifies an existing quality results record. It applies permitted changes to result attributes while preserving the audit trail maintained through the results history table.
• ENABLE — Marks or activates a quality results record, controlling its visibility and participation in downstream Quality processing.
• ENABLE_AND_FIRE_ACTION — Combines activation of a results record with the firing of the associated Quality action, allowing business rules or alerts tied to the result to be triggered immediately.
• COMMIT_QA_RESULTS — Performs the commit of pending quality results changes. As with other EBS APIs, the caller controls transaction boundaries, and this procedure provides the standard commit point for the results API.

Tables Accessed

The package operates against the QA_RESULTS table, the central store of captured quality result data, and QA_RESULTS_UPDATE_HISTORY_S, which preserves the audit history of changes applied through the API. It also references QA_COLLECTION_ID_S and QA_OCCURRENCE_S, the sequences that supply primary keys for collection and occurrence records, and MTL_MATERIAL_TRANSACTIONS_S for material transaction identifiers where results are linked to inventory movements. DUAL is used for scalar lookups, DBMS_SQL supports dynamic SQL execution, and PLITBLM is the standard PL/SQL integer table type used internally for array-style processing.

Usage Notes

QA_RESULTS_API is normally invoked indirectly. The metadata shows it is referenced by QA_PARENT_CHILD_PKG, QA_RESULTS_PUB, QA_RESULT_GRP, and by itself, indicating that the public wrapper package QA_RESULTS_PUB and the results grouping package QA_RESULT_GRP route their processing through this API. Oracle Quality forms call the public layer rather than this package directly. Custom integrations, conversion scripts, and concurrent programs that must load quality results should follow the same pattern, invoking the documented procedures within an explicit transaction and issuing COMMIT_QA_RESULTS to finalize. Because the package relies on FND_GLOBAL, callers must ensure the correct application and user context is initialized before invocation. In EBS 12.1.1 and 12.2.2 the package remains schema-resident in APPS with the same calling contract.