Search Results global_start_date_null




Overview
Explore in AI Chat

Overview

The APPS.OPI_DBI_REP_UOM_STD_CONV_PKG package is a PL/SQL ETL construct within the Oracle E-Business Suite Discrete Business Intelligence (DBI) reporting schema. Its purpose is to extract, transform, and load unit-of-measure (UOM) standard conversion rates from the core Inventory application into the DBI reporting layer, where they support downstream analytical reporting on measures, conversions, and inter-class or intra-class UOM relationships. The package header identifies the unit as REP_UOM and establishes a fixed conversion precision of five decimal places, matching the precision enforced by the core OLTP Inventory application.

The package is significant in the context of the search term global_setup_missing because the UOM standard conversion data it populates depends on global setup artifacts — specifically the OPI_DBI_UOM_MEASURE_TYPE lookup type in FND_LOOKUPS. When that lookup, or the associated measure class and UOM class setup, is absent or incomplete, the package cannot classify conversions correctly and reporting failures consistent with a "global setup missing" condition are surfaced. The package constants C_MEASURE_LOOKUP_TYPE, C_INTRA_CONV_TYPE, and C_INTER_CONV_TYPE define the classification semantics used during load.

Key Procedures and Functions

Two documented procedures are exposed by this package:

  • POPULATE_REP_UOM_STD_CONV_INIT — Performs the initial (full) load of UOM standard conversion data into the reporting staging and fact structures. It is designed to run from a very early baseline, reflected by the C_START_RUN_DATE constant of 01-January-1950, which allows the initial extract to capture the complete historical set of conversion records regardless of transaction age. It reads source UOM and conversion data, applies intra-class classification, and writes staged rows tagged with the standard-rate item identifier.
  • POPULATE_REP_UOM_STD_CONV_INCR — Performs the incremental load, capturing only conversion records changed or created since the last successful run. This supports the recurring refresh cycle of the DBI reporting schema and depends on log entries written to OPI_DBI_CONC_PROG_RUN_LOG to determine the processing window.

Both procedures follow the package's return-code convention: C_SUCCESS (0), C_WARNING (1), and C_ERROR (-1), with a 300-character error buffer for message propagation to the concurrent manager. Success yields the message "Successful Termination."

Tables Accessed

  • MTL_UNITS_OF_MEASURE — the core Inventory UOM definition table, read to obtain UOM codes, base/non-base flags (C_IS_BASE_UOM, C_NOT_BASE_UOM), and class membership.
  • OPI_DBI_UOM_CLASS_STD_CONV — holds UOM class standard conversion relationships used to derive intra-class conversion factors.
  • OPI_DBI_REP_UOMS — the reporting-dimension table of UOMs populated or referenced during the load.
  • OPI_DBI_REP_UOM_CONV_STG — the staging table into which extracted conversion rows are written prior to fact table load. Standard rates are staged under the synthetic item identifier C_STD_RATE_ITEM_ID (0).
  • OPI_DBI_REP_UOM_STD_CONV_F — the target fact table for standard UOM conversions.
  • OPI_DBI_CONC_PROG_RUN_LOG — the ETL run log, written to record REP_UOM execution metadata and read to establish incremental high-water marks.

Usage Notes

The package is not referenced by any other documented package, indicating it is invoked directly rather than through a wrapper API. In typical DBI deployments it is executed from a concurrent program registered against the POPULATE_REP_UOM_STD_CONV_INIT or POPULATE_REP_UOM_STD_CONV_INCR entry points, with the INIT program run once during initial warehouse build and the INCR program scheduled on the standard ETL refresh cadence. It may also be called from custom PL/SQL during a data-warehouse bootstrap or a re-collection of UOM setup. Because output is governed by global setup such as the OPI_DBI_UOM_MEASURE_TYPE lookup and class definitions, administrators encountering a global_setup_missing condition should verify that lookup seed data and UOM class standard conversions are loaded and committed before rerunning the INIT procedure. Execution status should be checked in OPI_DBI_CONC_PROG_RUN_LOG for warning or error return codes.