Results for “get_mfg_lookups_meaning”

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

Overview

QA_ERES_UTIL is a utility package in the APPS schema that supports Oracle E-Business Suite's electronic signature (e-signature) and electronic records functionality for the Quality Management (QA) module. It is classified as a UTIL package in the ETRM 12.2.2 metadata, indicating that it provides reusable helper logic rather than a business transaction interface. Its principal role is to underpin e-signature (ERES) processing for quality results, plan characteristics, and shipping-related records, and to assemble XML payloads that carry QA result data to downstream consumers.

The package is a leaf-level utility in the QA dependency chain: it is referenced by several higher-level packages, including QA_CHART_HEADERS_PKG, QA_CHART_HISTOGRAM_PKG, QA_CHART_TREND_PKG, QA_ERES_SHIPPING, QA_SS_RESULTS, and by itself. The ETRM dependency listing shows QA_ERES_UTIL depends only on SYS.STANDARD, confirming it is a self-contained helper that does not call other APPS business packages directly.

Key Procedures and Functions

The documented interface exposes nine procedures and functions. Their names map to four functional groupings:

• Hierarchy resolution: FIND_TOPMOST_PARENT walks a parent relationship to the root of a characteristic hierarchy, typically used when determining the governing signature context for a child plan characteristic.
• Electronic signature status: GET_RESULT_ESIG_STATUS returns the current e-signature status of a QA result. IS_DEF_SIG_ENABLED determines whether the default signature is enabled for the applicable context. IS_ESIG_STATUS_PENDING evaluates whether an e-signature status represents a pending state. ADD_ESIG_STATUS inserts a new e-signature status record, advancing the signature lifecycle.
• Lookup services: GET_MFG_LOOKUPS_MEANING resolves a manufacturing lookup code to its display meaning, providing user-facing text for codes used in signature and results processing.
• XML generation: GENERATE_XML, GENERATE_XML_FOR_PLAN, and GET_XML_FOR_ROW build XML documents representing QA result or plan data. GENERATE_XML_FOR_PLAN scopes output to a plan, while GET_XML_FOR_ROW produces the XML fragment for an individual row; GENERATE_XML serves as the general entry point.

Tables Accessed

The package accesses the following tables through APPS synonyms:

• QA_RESULTS — the primary source of quality result rows for signature status evaluation and XML generation.
• QA_CHARS — characteristic definitions, read to resolve hierarchy and display information.
• QA_PLAN_CHARS — characteristic assignments at the plan level, supporting plan-scoped XML and hierarchy lookups.
• QA_PC_RESULTS_RELATIONSHIP — relationship data linking plan characteristics to results, used when walking hierarchy and assembling signatures.
• QA_PLAN_CHAR_ACTIONS, QA_PLAN_CHAR_ACTIONS_S, QA_PLAN_CHAR_ACTION_TRIGGERS, QA_PLAN_CHAR_ACTION_TRIGGERS_S — action and trigger definitions (and their translation tables) that determine when e-signatures are required and what status transitions apply.
• DBMS_LOB and DUAL — used as a LOB utility for XML handling and as a single-row source for scalar lookups, respectively.

Usage Notes

QA_ERES_UTIL is not intended for direct end-user invocation. It is called by the QA e-signature and charting packages listed in its dependency report, which in turn are invoked from Oracle Quality forms (such as results entry and plan characteristic maintenance) and from concurrent programs that produce result or plan XML extracts. Custom extensions that require QA e-signature status checks, default-signature enablement tests, hierarchy resolution, or QA result XML should call this package rather than re-implementing the logic, since it centralizes the e-signature lifecycle and XML construction rules. Because the package is marked VALID across both Oracle EBS 12.1.1 and 12.2.2, its interface should be treated as stable within those releases.