Results for “qa_ss_results”

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

Overview

QA_SS_RESULTS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as an "OTHER" API within the ETRM repository for releases 12.1.1 and 12.2.2. Its primary business function is to manage the posting, updating, and persistence of quality results generated by Oracle Quality collection plans and related inspection, receiving, and shop-floor transactions. The package acts as the transactional core that writes validated result rows into the QA_RESULTS table and its supporting relationship and temporary tables, translating in-memory validation structures into permanent quality records.

The package is registered as VALID in the ETRM dependency model and forms a key node in the Oracle Quality results architecture. It both depends on and is invoked by QA_VALIDATION_API, indicating a close working relationship between validation logic and result persistence. The presence of the SSQR_ prefixed procedures (SSQR_POST_RESULT, SSQR_UPDATE_RESULT, SSQR_LOCK_ROW, SSQR_VALIDATE_ROW) indicates specialized support for shop-floor or "SS" quick results handling, where results are captured outside the standard collection plan entry flow.

Key Procedures and Functions

• POST_RESULT and NONTXN_POST_RESULT — Insert a single quality result. The transactional variant participates in the caller's transaction, while the non-transactional variant supports cases where results are posted independently of the calling transaction context.
• SSQR_POST_RESULT and SSQR_UPDATE_RESULT — Shop-floor quick result equivalents for posting and updating results in the SSQR flow.
• UPDATE_RESULT and DELETE_RESULT / DELETE_RESULTS / DELETE_ROW — Maintain and remove existing result rows, including bulk deletion of a result set and low-level single-row deletion.
• SSQR_LOCK_ROW and SSQR_VALIDATE_ROW — Concurrency control and row-level validation within the shop-floor quick result path.
• VALIDATE_ESIG_FOR_UPDATE and VALIDATE_ESIG_FOR_INSERT — Enforce electronic signature (e-signature) requirements before permitting result modifications or insertions.
• COMMIT_RESULTS — Commit pending result changes.
• GET_COLLECTION_ID — Retrieve the collection identifier associated with a result context.
• GET_ERROR_MESSAGES, POST_ERROR_MESSAGES, and WRAPPER_FIRE_ACTION — Error handling, message surfacing, and wrapper logic that fires the appropriate plan char action triggers.

Tables Accessed

• QA_RESULTS — The primary result storage table; all POST, UPDATE, and DELETE operations target it.
• QA_PC_RESULTS_RELATIONSHIP and QA_PC_PLAN_RELATIONSHIP — Maintain the links between results, collection plans, and plan characteristics.
• QA_CHARS, QA_PLAN_CHARS, QA_PLAN_CHAR_ACTIONS, and QA_PLAN_CHAR_ACTION_TRIGGERS — Provide characteristic definitions and drive the action firing logic executed by WRAPPER_FIRE_ACTION.
• QA_PERFORMANCE_TEMP — Temporary staging for performance-related result processing.
• QA_COLLECTION_ID_S — Sequence source for collection identifiers used by GET_COLLECTION_ID.
• DBMS_SQL, DUAL, and PLITBLM — Used for dynamic SQL construction, scalar evaluation, and PL/SQL index-by table handling during bulk result operations.

Usage Notes

QA_SS_RESULTS is not intended for direct end-user invocation. It is called programmatically by Oracle Quality forms, concurrent programs, and other Quality APIs whenever results must be persisted or modified. The documented reference list identifies eight dependent packages, including AHL_COMPLETIONS_PVT, AHL_PRD_MTLTXN_PVT, AHL_QA_RESULTS_PVT, QA_MQA_RESULTS, QA_QWB_WRAPPER_PKG, QA_RESULTS_PUB, QA_TXN_GRP, and QA_VALIDATION_API, confirming that the package is a shared persistence utility across Quality, Quality Workbench, and Oracle Advanced Product Catalog (AHL) flows.

Custom code extending Oracle Quality should call the public posting and update entries rather than write directly to QA_RESULTS, ensuring e-signature validation, action triggers, and relationship maintenance are honored. In 12.1.1 and 12.2.2 the package remains VALID and unchanged in ownership; the SSQR-prefixed procedures should be considered specialized internal entry points for shop-floor quick results and are generally reserved for the standard Quick Results user interface paths.