Results for “plan_list_frames”

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

Overview

QA_SS_CORE is a core PL/SQL package in the Oracle EBS Quality Management (QA) application, residing in the APPS schema. Its name and dependency structure indicate that it serves as the central engine for the Supplier Scheduling (SS) quality data collection and results entry framework. The package provides the shared library of routines used to render the supplier-scheduling quality data entry user interface — including HTML frames, input fields, prompts, buttons, and value query regions — and to process the results that users enter against applicable quality plans. In effect, QA_SS_CORE bridges the Quality module's plan-and-characteristic model with the Supplier Scheduling workflow, allowing quality results to be captured at the point where supplier shipments, releases, and receipts are managed.

The package is classified as OTHER (not a public API) in the ETRM 12.2.2 metadata, which is consistent with its role as an internal implementation component rather than a documented integration point. It is referenced by four other packages (QA_SS_LOV, QA_SS_OSP, QA_SS_SHIP, and QA_TXN_GRP) as well as by itself, confirming its position as a foundational dependency within the QA supplier-scheduling package family.

Key Procedures and Functions

The package exposes thirty documented procedures and functions. Because the ETRM metadata records names only, no parameter lists are asserted here.

• Results entry: ENTER_RESULTS processes quality results captured through the supplier-scheduling UI; DEFAULT_IN_VALUES populates default values into the entry region; EVALUATE_TRIGGERS assesses collection trigger conditions to determine which actions fire.
• UI rendering: DRAW_TABLE, DRAW_FRAMES, DRAW_DISPLAY_FIELD, DRAW_INPUT_FIELD, DRAW_PROMPT, and DRAW_HTML_BUTTON use the HTF/HTP (OWA) toolkit to emit the HTML structure of the data entry page. GENERATE_EQR_JAVASCRIPT produces the client-side scripting associated with that page.
• Plan and list handling: LIST_PLANS, PLAN_LIST_FRAMES, and LIST_PLANS-related LOV logic (IS_LOV_NEEDED, IS_EMPTY_ROW) manage the plans presented for selection and suppress empty list rows. ANY_APPLICABLE_PLANS and ALL_APPLICABLE_PLANS determine whether one or all quality plans apply to a transaction.
• Value query and buttons: VQR and VQR_FRAMES implement value query region behavior; QLT_BUTTONS and CXE support the on-screen quality action buttons and related UI events.

Tables Accessed

QA_SS_CORE reads and writes through APPS synonyms rather than direct schema objects. It references QA_PLANS and QA_PLAN_CHARS to resolve which plans and characteristics apply, QA_CHARS for characteristic definitions, and QA_PLAN_COLLECTION_TRIGGERS and QA_TXN_COLLECTION_TRIGGERS to evaluate when results collection is triggered. QA_PLAN_TRANSACTIONS records the transaction-to-plan association. Inventory and item context are drawn from MTL_ITEM_CATEGORIES and MTL_CATEGORIES_KFV, while WIP_ENTITIES provides work-in-process context. Purchasing context comes from PO_HEADERS_ALL and PO_RELEASES_ALL, establishing the supplier-scheduling linkage. Dynamic SQL is executed via DBMS_SQL, and output is generated through HTF, HTP, and OWA_UTIL.

Usage Notes

QA_SS_CORE is invoked indirectly. Users do not call it; they reach it through the supplier-scheduling quality data entry pages and the packages that wrap it: QA_SS_LOV supplies list-of-values handling, QA_SS_OSP and QA_SS_SHIP support order/shipment and shipping flows, and QA_TXN_GRP groups transaction processing. Custom code should treat QA_SS_CORE as an internal package, since it is classified as OTHER and carries no public API guarantee. Form personalizations, OAF extensions, or custom concurrent programs that need quality results entry should follow the documented calling packages rather than calling QA_SS_CORE routines directly, to preserve upgrade safety across EBS 12.1.1 and 12.2.2. The package is VALID in the ETRM, indicating no compilation issues in the documented environment.