Search Results select_clause




Overview
Explore in AI Chat

Overview

QA_RESULTS_INTERFACE_PKG is an Oracle Quality package body in the APPS schema that provides the programmatic interface for importing quality results into Oracle EBS Quality Management. Its central purpose is to accept externally sourced or internally generated result data, resolve the appropriate quality collection plan and plan elements, populate the required descriptive flexfield and character value structures, and persist the rows as quality results through the supported Quality APIs rather than through direct table inserts. The package also supports value query (VQR) resolution, meaning it can derive the correct collection plan and element values from a variety of originating business flows, including order management, shipping, assets, and outside processing. In release 12.1.1 and 12.2.2 this object remains a VALID, deployed package that bridges inbound data feeds to the Oracle Quality transactional model.

Key Procedures and Functions

The documented entry points fall into three functional groups. The import lifecycle procedures govern row processing: START_IMPORT_ROW initializes an import row and prepares it for the addition of element values, ADD_ELEMENT_VALUE registers an individual collection element and its value against the current row, and END_IMPORT_ROW finalizes the row so it can be staged or committed. The transaction control procedures COMMIT_ROWS and ROLLBACK_ROWS manage the persistence boundary for a set of staged import rows, allowing callers to commit successfully processed rows or discard a failed batch.

The VQR and SQL construction functions build the dynamic query logic used to identify the correct collection plan and element values based on the originating transaction context. BUILD_VQR_SQL serves as the general query builder, while BUILD_OM_VQR_SQL, BUILD_SHIPMENT_VQR_SQL, BUILD_OSP_VQR_SQL, and BUILD_ASSET_VQR_SQL provide the order management, shipping, outside processing, and asset-specific variants. GET_PLAN_VQR_SQL returns the value query SQL associated with a given plan. Finally, OEHEADER_TO_MTLSALES supports conversion or linkage between order management header identifiers and sales order references in the MTL_SALES_ORDERS structure.

Tables Accessed

The dependency list shows the package reads core Quality and foundation metadata. QA_PLANS, QA_PLAN_CHARS, and QA_CHARS supply the collection plan and character element definitions that drive validation and attribute mapping. QA_TXN_COLLECTION_TRIGGERS holds the trigger configuration that determines which transactions require quality collection. QA_PLAN_ELEMENT_API and QA_CORE_PKG provide the API layer through which results are ultimately written. On the source side, MTL_PARAMETERS resolves the current organization and its quality settings, while MTL_SALES_ORDERS, OE_ORDER_HEADERS_ALL, and OE_TRANSACTION_TYPES_TL supply the order management context needed to build order-linked value queries. FND_LANGUAGES and FND_PROFILE support multilingual translation and profile-option lookups, and PLITBLM is the PL/SQL table type declaration used for in-memory collections during row processing.

Usage Notes

QA_RESULTS_INTERFACE_PKG is not an end-user API and is typically invoked from concurrent programs, inbound interface programs, or custom PL/SQL that stages quality results for batch load. Because the documented entry points pair row initialization (START_IMPORT_ROW, ADD_ELEMENT_VALUE, END_IMPORT_ROW) with batch control (COMMIT_ROWS, ROLLBACK_ROWS), the standard calling pattern is to iterate source records, build each import row through the element-value calls, and then commit or roll back the batch. The VQR builder functions are used when the calling process needs to derive plan and element values from an order, shipment, asset, or outside processing transaction rather than from explicitly supplied values. Practitioners integrating with Oracle Quality should prefer these procedures over direct inserts into Quality results tables, since the package routes writes through the supported Quality APIs and honors the collection-trigger and plan-element configuration maintained in the EBS setup. Care should be taken with transactional scope: because COMMIT_ROWS and ROLLBACK_ROWS control the database transaction, embedding the package in a larger logical unit of work should account for those explicit commit and rollback boundaries.