Search Results get_inception_inv_balance




Overview
Explore in AI Chat

Overview

OPI_DBI_INV_VALUE_INIT_PKG is an Oracle Application Object Library (APPS) PL/SQL package that supports the initial data load and valuation setup for the Oracle Process Manufacturing (OPM) inventory value reporting solution within the Oracle Daily Business Intelligence (DBI) / Enterprise Resource Planning (ERP) analytics framework. Its primary business purpose is to establish the inception inventory balances and the underlying cost and valuation foundations required before the OPM Inventory Value dashboards and reports can present meaningful results. Because DBI reporting depends on pre-aggregated and historically anchored data sets, this initialization package bridges the transactional world of Oracle Inventory and OPM costing tables with the reporting schema used by the inventory value subject area.

The package is classified as an OTHER API in the ETRM metadata, meaning it is not a public, supported business API for general integration use. It is an internal initialization utility whose procedures are intended to be executed as part of controlled setup or first-run ETL cycles rather than by end-user application logic.

Key Procedures and Functions

  • GET_INCEPTION_INV_BALANCE — Establishes the opening, or inception, inventory balance snapshot. This procedure seeds the historical starting point from which subsequent periodic inventory value movements are tracked, ensuring the reporting layer has a baseline quantity and value per item and organization.
  • RUN_FIRST_ETL — The main driver procedure for the initial extract, transform, and load cycle. It carries the standard concurrent program signature (errbuf, retcode) along with an inbound degree-of-parallelism parameter, indicating that it is designed to be launched as a concurrent program and to run its extraction work in parallel workers.
  • INTRANSIT_SETUP — Accepts a mode parameter and configures in-transit inventory handling so that goods moving between organizations are correctly reflected in valuation reporting rather than being dropped or double-counted during the initialization window.
  • GET_OPM_ITEM_COST — A function that returns the cost for a specific item within a given organization and as of a given transaction date. It is invoked by the loading routines to value transactions and layers using the correct point-in-time item cost.

Tables Accessed

The package reads and references a broad set of inventory, costing, and process manufacturing tables through APPS synonyms. Transactional and balance data is drawn from MTL_MATERIAL_TRANSACTIONS, MTL_TRANSACTION_ACCOUNTS, MTL_SUPPLY, MTL_SYSTEM_ITEMS, and MTL_INTERORG_PARAMETERS, with MTL_PARAMETERS supplying organization-level inventory controls. Costing information is sourced from CST_ITEM_COSTS, CST_STANDARD_COSTS, and CST_QUANTITY_LAYERS, which together provide the item cost and layer valuations needed to compute inception balances. Process manufacturing valuation data flows from GMF_TRANSACTION_VALUATION, GME_BATCH_HEADER, and GME_MATERIAL_DETAILS. Master configuration such as cost methods, components, and analyses is drawn from CM_MTHD_MST, CM_CMPT_MST, and CM_ALYS_MST. These accesses confirm the package's role as an integration point between Oracle Inventory, OPM costing, and the DBI valuation reporting schema.

Usage Notes

OPI_DBI_INV_VALUE_INIT_PKG is typically invoked during the initial deployment or implementation of the OPM inventory value reporting feature, most commonly by submitting the RUN_FIRST_ETL procedure as a concurrent program with an appropriate parallel degree. GET_INCEPTION_INV_BALANCE and INTRANSIT_SETUP form part of the mandatory one-time setup sequence and should be executed in the prescribed order before standard incremental ETL processes begin. GET_OPM_ITEM_COST is called internally by the loading logic and is not normally executed directly.

Because the metadata identifies the package as referenced by two other packages, it is also invoked programmatically from higher-level DBI or OPM reporting packages that coordinate the initialization workload. The absence of a formal public API classification indicates that custom code should avoid calling these procedures outside vendor-supported concurrent program invocations, and that any direct use should be validated against the specific EBS release (12.1.1 or 12.2.2) in a non-production environment first.