Results for “qa_results_api”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.QA_RESULTS_API package body is the central PL/SQL application programming interface governing the creation and maintenance of quality results within Oracle E-Business Suite Quality Management. In Oracle EBS 12.1.1 and 12.2.2, this API encapsulates the business logic required to record the outcome of quality inspections against a collection plan, character, and occurrence. Rather than permitting direct DML against the underlying QA_RESULTS table, Oracle delivers this API so that validation, sequence generation, history tracking, and action firing occur consistently regardless of the entry channel. The package is classified as an API and holds a VALID status in the APPS schema. Its dependency list confirms that it orchestrates several subordinate quality APIs and utility packages, positioning it as a façade over the broader Quality module data model.

Key Procedures and Functions

• INSERT_ROW — Inserts a new quality result record into the QA_RESULTS table, accepting the identifying keys and measured values supplied by the calling process and applying the module's validation rules before persistence.
• UPDATE_ROW — Modifies an existing quality result, typically after re-inspection, correction, or recalculation, and records the change so that the audit trail remains intact.
• COMMIT_QA_RESULTS — Performs the transactional commit for pending result changes, allowing callers to batch multiple row operations and finalize them as a single unit of work.
• ENABLE — Enables the API for use, setting up any required session or attribute context needed before row-level operations proceed.
• ENABLE_AND_FIRE_ACTION — Combines the enablement step with the firing of post-result business actions, such as triggering occurrence or plan-element logic that responds to a completed inspection outcome.

The five documented procedures mirror the standard Oracle API pattern of enablement, row-level insert and update, and commit, with the added action-firing variant characteristic of Quality results processing.

Tables Accessed

• QA_RESULTS — The primary transactional table holding individual quality result rows; it is the principal insert and update target.
• QA_RESULTS_UPDATE_HISTORY_S — The update-history table whose sequence supplies identifiers used to log modifications to results, providing the audit trail that this API maintains.
• QA_COLLECTION_ID_S, QA_OCCURRENCE_S, and MTL_MATERIAL_TRANSACTIONS_S — Sequences used to generate surrogate keys for collections, occurrences, and associated material transactions.

The dependency metadata also lists DBMS_SQL, DUAL, and PLITBLM, which support dynamic SQL execution and date or time handling through the QLTDATE utility.

Usage Notes

QA_RESULTS_API is invoked from Quality Management entry forms, from concurrent programs that process or import inspection results, and from custom PL/SQL extensions that need to write quality results without bypassing module validation. It relies on FND_GLOBAL for session context and FND_REQUEST for concurrent request submission, and it delegates to QA_CHARS_API, QA_PLAN_ELEMENT_API, QA_SEQUENCE_API, and QA_VALIDATION_API to enforce character, plan-element, sequencing, and validation rules. The package is referenced by three other database objects, so changes to its behavior can propagate across the Quality module. Developers searching for qa_results_update_history_s should note that this sequence is written through QA_RESULTS_API rather than accessed directly.