Search Results collapse_msg_tokens




Overview
Explore in AI Chat

Overview

QA_ERES_PKG is a PL/SQL package body owned by the APPS schema that supports the Oracle Quality electronic records and electronic signatures (ERES) and results-reporting infrastructure in Oracle E-Business Suite. The package's documented API classification is OTHER, indicating that it is not a public, supported integration interface but an internal utility library consumed by other Quality modules and by dependent packages. Its responsibilities fall into three functional areas: post-processing of formatted Quality message strings, retrieval of descriptive attribute values (category names and descriptions and result column metadata), and translation of coded status or classification values into user-readable text for use in Quality result grids and reports. The header comment, dated 2004/05/11 at version 115.2, places the package's origin in the QA reporting layer, and the presence of private token-parsing helpers confirms that the message-handling routines were designed to support a templated, token-substitution style of message rendering used in Quality test and collection output.

Key Procedures and Functions

  • COLLAPSE_MSG_TOKENS — Reduces a message string in which token values have been expanded into numbered long forms back to a compact, human-readable representation. It relies on two private helpers: FIND_LONG_TOKEN, which locates the next token name eligible for expansion, and EXPANDED_TOKEN_STRING, which builds the search pattern for numeric token suffixes. The routine loops until no further tokens are found and returns the collapsed message.
  • GET_CATEGORY_NAME — Returns the descriptive name of an item category, resolving a category identifier within a specified category set.
  • GET_CATEGORY_DESC — Returns the descriptive text associated with a category, complementing the name lookup.
  • GET_RESULT_COLUMN_VALUE — Retrieves the value held in a designated Quality results column, used when rendering specification results.
  • GET_RESULT_COLUMN_NAME — Returns the display name of a results column, allowing generic result grids to label columns dynamically.
  • DECODE_WSH_RELEASED_STATUS — Converts the internal released-status code from Oracle Shipping Execution into a formatted, user-facing description.
  • DECODE_PO_HAZARD_CLASS — Converts the stored purchasing hazard classification code into readable hazard text.
  • DECODE_PO_UN_NUMBER — Converts a stored United Nations hazardous-material number into its formatted display value.

Tables Accessed

The package reads from the following tables through APPS synonyms. MTL_CATEGORIES_KFV and MTL_CATEGORY_SETS_B underpin the category name and description lookups, with the key flexfield view supplying the concatenated segment display value and the category set base table supplying the structure linkage. MTL_SYSTEM_ITEMS is referenced for item-level attribute resolution. PO_LINES_ALL is queried to obtain purchasing line attributes such as hazard class and UN number that the DECODE routines translate for display. QA_CHARS and QA_PLAN_CHARS supply Quality character and plan-character metadata used when assembling result column names and values. RCV_TRANSACTIONS_INTERFACE is consulted in connection with shipping released-status decoding, linking receipt transaction data to the decoded status text.

Usage Notes

QA_ERES_PKG is an internal dependency rather than a callable public API. ETRM records five other packages referencing it, so changes to its function signatures carry a measure of regression risk. The package is typically invoked from Oracle Quality forms and from concurrent programs that render test results, collection plans and specification reports, where the decode routines convert stored codes into labels and the collapse routine normalizes tokenized message text before display. Because COLLAPSE_MSG_TOKENS operates on VARCHAR2 input and returns a VARCHAR2 value, custom extensions that generate Quality messages in the same tokenized format can reuse it, but such use should be treated as unsupported. Implementations on 12.1.1 and 12.2.2 should verify the online documentation for the specific patch level in use, since the package body shows no evidence of ongoing functional change beyond the 2004 header revision.