Search Results appl_inst_bom




Overview

INV_ITEM_UTIL is a utility package in the APPS schema that supports the Oracle Inventory item master and the Oracle Product Information Management (PIM) data model. Its primary purpose is to determine and validate the application installation status of the Oracle E-Business Suite modules to which an item can be assigned or associated. In the Oracle Inventory architecture, several item-level attributes and relationships are application-specific, meaning they are only meaningful when the corresponding module (such as Purchasing, Bills of Material, Order Entry, or Work in Process) is installed. INV_ITEM_UTIL centralizes the logic required to interrogate the installation status of those modules, so that catalog views, table APIs, and item validation routines can conditionally expose or enforce attribute behavior.

The package is classified as a UTIL API, indicating that it is intended primarily as an internal building block rather than a public, directly-called interface. It is referenced by numerous other packages and views, including INV_ITEM_PVT, INV_ITEM_EVENTS_PVT, EGO_ITEM_ORG_ASSIGN_PVT, INV_ENI_ITEMS_STAR_PKG, and VPD-enabled synonym views such as MTL_SYSTEM_ITEMS_TL_TA_IBE, MTL_CATEGORIES_B_TA_IBE, and MTL_ITEM_CATEGORIES_TA_IBE. Because the user search referenced MTL_SYSTEM_ITEMS_TL_TA_IBE, it is relevant to note that this view depends on INV_ITEM_UTIL, so the package's behavior directly influences what the translated item description view can resolve.

Key Procedures and Functions

The documented program units center on the APPL_INSTALL family, which answers the question: "Is a given Oracle application installed in this environment?" The following units are documented in the ETRM metadata:

  • APPL_INSTALL — the controlling routine that determines whether a specific application is installed.
  • APPL_INST_STATUS — returns the installation status of an application, supporting the decision logic used by the APPL_INSTALL checks.
  • APPL_INST_INV — installation check specific to Oracle Inventory.
  • APPL_INST_PO — installation check for Oracle Purchasing.
  • APPL_INST_BOM — installation check for Oracle Bills of Material.
  • APPL_INST_ENG — installation check for Oracle Engineering.
  • APPL_INST_CS — installation check for Oracle Customer Service / Service.
  • APPL_INST_AR — installation check for Oracle Receivables.
  • APPL_INST_MRP — installation check for Oracle Material Requirements Planning.
  • APPL_INST_OE — installation check for Oracle Order Entry.
  • APPL_INST_ONT — installation check for Oracle Order Management.
  • APPL_INST_QP — installation check for Oracle Advanced Pricing / Quick Pricing.
  • APPL_INST_WIP — installation check for Oracle Work in Process.
  • APPL_INST_FA — installation check for Oracle Fixed Assets.
  • APPL_INST_JL — installation check for Oracle General Ledger (Japanese localization context).
  • APPL_INST_WMS — installation check for Oracle Warehouse Management.
  • APPL_INST_CSP — installation check for Oracle Spares Management (field service).
  • APPL_INST_CSS — installation check for Oracle Service (CSS).
  • APPL_INST_OKS — installation check for Oracle Contracts.
  • APPL_INST_AMS — installation check for Oracle Marketing.

In total, 41 documented procedures and functions are associated with the package, of which the APPL_INSTALL and APPL_INST_* routines constitute the dominant family. Each routine encapsulates a discrete installed-module test so callers need not repeat the underlying catalog queries.

Tables Accessed

The package reads dictionary and metadata tables exposed through APPS synonyms:

  • AD_DDL — the Applications DDL / installation metadata table, used to determine whether an application is registered and installed.
  • ALL_OBJECTS — used to verify the existence of database objects associated with a given application, providing a secondary installation signal.
  • USER_OBJECTS — used to confirm object presence in the current schema context.

These reads are read-only and support the installation-status logic. INV_ITEM_UTIL does not maintain transactional item data; instead, it supplies the environment awareness that item-related views and table APIs require.

Usage Notes

INV_ITEM_UTIL is normally invoked indirectly. Item master views such as MTL_SYSTEM_ITEMS_TL_TA_IBE, MTL_SYSTEM_ITEMS_B_T2_IBE, MTL_SYSTEM_ITEMS_B_T3_IBE, and related VPD synonym views reference the package to decide which item attributes to expose based on installed modules. Table APIs including INV_ITEM_PVT, INV_ITEM_EVENTS_PVT, MTL_CATEGORIES_PKG, and MTL_DEFAULT_CATEGORY_SETS_PKG call it during item validation, category assignment, and defaulting. Concurrent programs and forms that process item attributes across multiple modules also rely on these installation checks. Because the package is a UTIL API and is referenced by 21 other packages, custom code should call the APPL_INST_* routines rather than replicate installation logic. Direct modification is not supported, and behavior is consistent across 12.1.1 and 12.2.2.