Search Results decode_wsh_released_status




Overview
Explore in AI Chat

Overview

QA_ERES_PKG is a PL/SQL package owned by the APPS schema that provides the server-side data access and decoding layer for Oracle E-Business Suite's electronic records and electronic signatures (ERES) reporting infrastructure within the Quality Management (QA) module. ERES reporting is mandated for regulated industries that must comply with 21 CFR Part 11 and comparable electronic signature regulations, and this package supplies the column values, category descriptions, and coded-value translations that those reports and views require. The package is classified as OTHER, indicating it is a supporting utility rather than a formal public API. It exposes a set of helper functions that resolve denormalized lookups — category names, category descriptions, and decoded status codes — so that the ERES views and concurrent programs can present human-readable values instead of raw identifiers. It is referenced by several ERES views (QA_ERES_PLAN_CHAR_ACTIONS_V, QA_ERES_RCV_TRANS_INTERFACE_V, QA_ERES_SPECS_V, QA_ERES_WSH_DELIVERABLES_V) as well as by QA_SS_RESULTS, confirming its role as a shared dependency consumed by both views and other PL/SQL units.

Key Procedures and Functions

  • GET_CATEGORY_NAME — returns the display name of an item category, resolving the category identifier against the category key flexfield.
  • GET_CATEGORY_DESC — returns the description associated with an item category, supplementing the name lookup for reporting purposes.
  • GET_RESULT_COLUMN_VALUE — retrieves the value stored in a specified QA results column, used to expose result data dynamically to ERES reports.
  • GET_RESULT_COLUMN_NAME — returns the name of a QA results column, working in tandem with GET_RESULT_COLUMN_VALUE to support column-driven output.
  • DECODE_WSH_RELEASED_STATUS — translates the WSH (Shipping) released-status code into its textual meaning for ERES deliverables reporting.
  • DECODE_PO_HAZARD_CLASS — decodes a Purchasing hazard class code into its descriptive value.
  • DECODE_PO_UN_NUMBER — decodes a Purchasing United Nations (UN) number into its descriptive value.
  • COLLAPSE_MSG_TOKENS — consolidates or collapses message tokens, supporting message construction and formatting within the ERES output.

The eight documented helper functions, together with a ninth documented entry, form the package's public surface. All are utility-oriented and are designed to be called repeatedly from views and report logic.

Tables Accessed

  • MTL_SYSTEM_ITEMS — the item master, used to resolve item attributes referenced in ERES result and specification output.
  • MTL_CATEGORIES_KFV — the category key flexfield view, providing category names and descriptions for GET_CATEGORY_NAME and GET_CATEGORY_DESC.
  • MTL_CATEGORY_SETS_B — the category set definition table, used to establish the correct category set context for lookups.
  • QA_CHARS — the quality characteristics definition table, supplying characteristic metadata for results and specification displays.
  • QA_PLAN_CHARS — the quality plan characteristics table, linking characteristics to sampling plans for ERES plan reporting.
  • RCV_TRANSACTIONS_INTERFACE — the receiving transactions interface, accessed for inspection and receipt-related ERES output.
  • PO_LINES_ALL — purchasing order lines, accessed to supply hazard class and UN number data for the DECODE_PO_* functions.

Usage Notes

QA_ERES_PKG is an internal dependency rather than a standalone API. It is invoked primarily through the ERES views (QA_ERES_PLAN_CHAR_ACTIONS_V, QA_ERES_RCV_TRANS_INTERFACE_V, QA_ERES_SPECS_V, QA_ERES_WSH_DELIVERABLES_V), which call its lookup functions to render decoded, report-ready columns. QA_SS_RESULTS also references the package, so quality results processing relies on it. Custom ERES reports and concurrent programs can call the same functions when they need consistent decoding of status, hazard class, or UN number values. Because the package depends only on SYS.STANDARD and standard APPS synonyms, it carries no unusual compile-order constraints. It should be treated as controlled EBS code: gather statistics and run the standard dependency recompilation after patching, and avoid direct modification, since changes may affect the five referencing packages and the dependent views.