Results for “err_msg_missing_uoms”

4 results




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

Overview

OPI_DBI_REP_UOM_PKG is an Oracle Application Object Library (APPS) owned PL/SQL package body that supports unit-of-measure (UOM) handling for the Oracle Process Manufacturing and Discrete Intelligence (DBI) reporting layer in Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal business function is to translate quantities between units of measure and to resolve the appropriate reporting UOM for a given item, transaction, or reporting context. The package bridges transactional UOM data held in Oracle Inventory's foundational tables with reporting-specific UOM definitions maintained by the DBI/OPI reporting schema. It is classified in ETRM as an OTHER API rather than a public or private interface, indicating that it is principally an internal utility invoked by other reporting packages rather than a supported external integration point. The package exposes nine documented program units and is referenced by five other packages, confirming its role as a shared service within the OPI DBI reporting stack.

Key Procedures and Functions

The documented program units fall into two categories: conversion and reporting UOM resolution functions, and diagnostic message helpers.

  • UOM_CONVERT — The central conversion routine. It converts a quantity expressed in a source UOM to a target UOM, resolving the UOM class of each code, deriving the base UOM for each class, and applying intra-class and inter-class conversion rates. It accepts an item identifier, a precision value, the source quantity, and the from/to UOM codes, and returns the converted quantity. Internally it employs the get_uom_class cursor, the base_uom_code cursor, and the inter_conversions cursor to obtain conversion factors, and returns negative sentinel values when input UOMs cannot be resolved.
  • GET_REPORTING_UOM — Resolves the reporting UOM applicable to a supplied context, allowing DBI reports to present quantities in a standardized reporting unit rather than the transactional unit.
  • GET_W, GET_V, and GET_D — Accessor functions that return specific reporting UOM or conversion attributes used by downstream reporting logic. These are abbreviated helper functions within the package's internal API surface.
  • ERR_MSG_HEADER, ERR_MSG_FOOTER, ERR_MSG_MISSING_UOMS, and ERR_MSG_HEADER_SPEC — Message-formatting procedures that construct standardized header, footer, and missing-UOM diagnostic text. These support consistent error reporting when conversion or UOM resolution fails, particularly the condition in which a UOM code cannot be found in the units-of-measure table.

Tables Accessed

The package operates against three documented tables, accessed through APPS synonyms.

  • MTL_UNITS_OF_MEASURE — The Oracle Inventory master UOM table. It is queried to obtain the UOM class for a given UOM code (via the get_uom_class cursor) and to identify the base UOM for a class through the base_uom_flag column (via the base_uom_code cursor).
  • OPI_DBI_UOM_CLASS_STD_CONV — The reporting conversion-rate table. It supplies inter-class conversion rates and from/to base UOM code pairs used when a conversion spans two different UOM classes.
  • OPI_DBI_REP_UOMS — The reporting UOM definition table, used to resolve reporting UOMs for the GET_REPORTING_UOM and associated accessor functions.

Usage Notes

OPI_DBI_REP_UOM_PKG is typically invoked from within other OPI DBI reporting packages rather than directly by end users or forms. Its documented reference by five other packages indicates that it is consumed programmatically by reporting logic that must normalize quantities to consistent reporting units. The UOM_CONVERT function is the most likely entry point for custom code requiring reliable conversion between Inventory UOMs, including cross-class conversions handled through OPI_DBI_UOM_CLASS_STD_CONV. Because the package depends on reporting-specific tables, callers must ensure that OPI_DBI_REP_UOMS and OPI_DBI_UOM_CLASS_STD_CONV are populated and current; the presence of ERR_MSG_MISSING_UOMS indicates that the package explicitly anticipates and reports missing UOM definitions. As an OTHER-classified API, it should be treated as an internal implementation detail: customizations should minimize direct dependency on it and prefer supported public APIs where equivalent conversion services exist.