Search Results bom_small_impl_temp




Overview
Explore in AI Chat

Overview

BOM.BOM_SMALL_IMPL_TEMP is a transient staging table in the Oracle E-Business Suite Bills of Material module. It is owned by the BOM schema and is classified as VALID in ETRM for releases 12.1.1 and 12.2.2, where its documented physical schema contains 70 columns. The table exists to hold temporary data used to render the View Item Usage window, which is the inquiry form that displays the upward or downward where-used and implosion relationships of an item. Rows are populated at runtime by the form or its underlying logic, consumed for display, and then discarded or refreshed for each new inquiry.

Although the object is documented as a table, it functions as a session- or request-scoped work area rather than a durable transactional store. Its columns support hierarchical traversal of a bill of material from a top assembly down to its lowest components, retaining parent, current, and lowest level context on each row. Because the object is instantiated and cleaned on demand, its contents are not suitable as a permanent audit or history source.

From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as standalone. That classification reflects the absence of a durable parent hub relationship at the physical level; the foreign keys it declares point to reference data rather than to a persistent business entity. Analysts should treat the standalone designation as a modeling suggestion only. If the table were materialized as a permanent construct, its natural role would be that of a link or satellite recording the traversal path between assemblies and components, with an effective dating dimension provided by the effectivity columns.

Key Information Stored

The column list defines the structure of each traversal row. The most significant columns are as follows:

Two foreign keys are documented: REVISED_ITEM_SEQUENCE_ID references ENG_REVISED_ITEMS, and STRUCTURE_TYPE_ID references BOM_STRUCTURE_TYPES_B. These provide the engineering revision and structure type context for each row. Standard concurrent program context columns such as REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE are also present, confirming that the table is populated by a request-driven process.

Common Use Cases and Queries

The principal scenario is the View Item Usage inquiry in the Bills of Material module, where a planner or engineer views where a component is used and through which paths. Diagnosing an unexpectedly missing or duplicated row in that window is the most common support investigation involving this table.

Reporting and diagnostics typically take the form of a join back to the master item tables to resolve IDs into names, for example selecting CURRENT_ITEM_ID, PARENT_ITEM_ID, and CURRENT_LEVEL from BOM_SMALL_IMPL_TEMP where ORGANIZATION_ID equals a given organization and TOP_ITEM_FLAG equals 'Y'. A second pattern filters on ALTERNATE_DESIGNATOR to confirm which alternate bill was traversed, and a third verifies effectivity by restricting on EFFECTIVITY_DATE and DISABLE_DATE. Because the table is temporary, queries should assume a short-lived and request-specific result set, and should not be used for historical trending.

Related Objects

The following objects are most significant in relation to BOM_SMALL_IMPL_TEMP: