Search Results get_grade_desc




Overview
Explore in AI Chat

Overview

GMI_ERES_UTILS is a Process Manufacturing (OPM/GMI) utility package owned by APPS within Oracle E-Business Suite 12.1.1 and 12.2.2. Its header identifies it as GMIERESB.pls, version 115.7, last modified in October 2003, indicating a shared library that has remained stable across releases. The package serves as a technical helper layer for the e-Records and e-Signatures (ERES) functionality and reporting associated with OPM transactions, particularly inventory, lot, quality, and journal processing. Rather than implementing business rules itself, it provides a set of narrowly scoped lookup and resolution routines that translate internal identifiers into the human-readable values required on printed documents, forms, and audit records. Its API classification is recorded as OTHER, meaning it is not a formalized public API but an internal supporting package. Because it is referenced by zero other documented packages, it is best understood as a consumer of core GMI master data rather than a component of a layered application programming stack.

Key Procedures and Functions

The package exposes 24 documented procedures and functions. Its resolution routines follow a consistent pattern: each accepts an internal identifier and returns the corresponding descriptive attribute, defaulting to a space when no row is found.

  • Item attribute lookups: GET_ITEM_NO, GET_ITEM_UM, and GET_ITEM_DESC resolve an item identifier to its item number, primary unit of measure, and description respectively from the item master. GET_ITEM_UOM_AND_TYPE combines unit of measure and unit of measure type retrieval in a single call, reducing round trips when both values are needed.
  • Unit of measure resolution: GET_UM_TYPE returns the unit of measure type for a given unit of measure code, while GET_BASE_UOM returns the base (standard) unit of measure for a given unit of measure type.
  • Lot and sublot lookups: GET_LOT_NO, GET_SUBLOT_NO, and GET_LOT_DESC resolve lot-related identifiers into lot number, sublot number, and lot description values used in OPM lot tracking documents.
  • Descriptive and lookup resolution: GET_LOOKUP_VALUE returns a lookup code value; GET_GRADE_DESC, GET_STATUS_DESC, GET_REASON_DESC, and GET_WHSE_DESC return the descriptions for quality grades, statuses, reasons, and warehouses respectively.
  • Vendor lookups: GET_VENDOR_NO and GET_VENDOR_DESC resolve supplier identifiers to vendor number and vendor name.
  • Journal support: GET_JOURNAL_NO returns the journal number and GET_JRNL_COMMENT retrieves the comment text associated with a journal entry, both of which are directly relevant to the searched term "get_jrnl_comment".
  • Other utilities: PAD_LANGUAGE performs language string padding, and ACTIVATE_ITEM performs the package's only write-oriented action, activating an item record.

Tables Accessed

The package reads from the following tables through APPS synonyms. IC_ITEM_MST and IC_ITEM_MST_B supply item attributes, units of measure, and item activation data. IC_LOTS_MST, IC_LOTS_CPG, and IC_LOTS_STS provide lot, sublot, grade, and lot status information. IC_JRNL_MST is the source for journal numbers and journal comments. MTL_CATEGORIES is accessed for category resolution. PO_VEND_MST supplies vendor number and description. QC_GRAD_MST provides quality grade descriptions. SY_REAS_CDS supplies reason code descriptions, SY_UOMS_MST provides unit of measure type information, SY_UOMS_TYP provides the base unit of measure, and IC_WHSE_MST and GME_BATCH_HEADER supply warehouse and batch context. Most access is read-only; writes are limited to item activation through ACTIVATE_ITEM.

Usage Notes

GMI_ERES_UTILS is typically invoked from OPM forms, ERES-enabled reports, and concurrent programs that require resolved descriptive values rather than internal identifiers. A report or form triggers these routines to populate item, lot, vendor, quality, and journal fields before display or printing. The GET_JRNL_COMMENT procedure in particular is called when journal documentation must include the comment text held in IC_JRNL_MST, and it should be treated as a single-value retrieval that returns a space when the requested journal record has no comment or does not exist. Because callers rely on the blank-space default rather than an exception, no explicit NO_DATA_FOUND handling is required. Custom code may invoke these procedures freely, but developers should note the OTHER classification: the package is not a supported public API, signatures are not guaranteed across patches, and direct table access may be preferable where equivalent data is already joined in the calling query. Given the package's age and the absence of dependent documented packages, it should be viewed as a shared convenience library whose contract is defined by the existing production code that consumes it.