Search Results current_concatenated_segments

Overview

APPS.BOM_IMPLOSIONS_V is a pre-built Oracle E-Business Suite view that exposes the results of a bill of materials implosion — that is, a "where-used" or upward traversal of the manufacturing structure. Where a conventional BOM explosion descends from a parent assembly into its components, an implosion ascends from a given item to the assemblies in which it is used, and continues recursively to the top-level end items. In Oracle EBS 12.1.1 and 12.2.2, this view is the presentation layer over the temporary structure populated by the BOM implosion engine (BOM_SMALL_IMPL_TEMP), decorated with descriptive attributes drawn from item master, organization, revision, and lookup tables.

The view plays a central role in reporting and integration scenarios that require multi-level where-used analysis: engineering change impact assessment, component shortage analysis, cost roll-up dependencies, and supply chain visibility. Because it joins descriptive columns such as item descriptions, organization codes, and revision labels, it is well suited to direct use in BI Publisher reports, OBIEE/OTBI federated queries, and custom concurrent programs without requiring callers to re-implement the many lookup joins themselves.

Underlying Base Objects

The view is owned by APPS and is defined over a combination of physical tables, synonyms, other views, and PL/SQL packages. The documented referenced base objects include:

• BOM_SMALL_IMPL_TEMP (SYNONYM) — the core implosion staging structure supplying T.SEQUENCE_ID, T.CURRENT_ITEM_ID, T.PARENT_ITEM_ID, T.CURRENT_LEVEL, T.COMPONENT_QUANTITY, and effectivity columns.
• MTL_SYSTEM_ITEMS_VL (VIEW) — aliased as MSIVL_PARENT and MSIVL_CURRENT, providing CONCATENATED_SEGMENTS, DESCRIPTION, PRIMARY_UOM_CODE, and INVENTORY_ITEM_STATUS_CODE for the parent and current items.
• MTL_ITEM_REVISIONS_B (SYNONYM) — used in scalar subqueries to translate revision identifiers into REVISION_LABEL values for both end-item effectivity and component revisions.
• MFG_LOOKUPS (VIEW) and FND_LOOKUP_VALUES (SYNONYM) — joined through FL_ITEM_TYPE and ML_BASIS_TYPE/ML_EFFECTIVITY_CONTROL to decode lookup codes into meanings.
• HR_ORGANIZATION_UNITS (VIEW) — supplies HOU.NAME for the ORG_NAME column.
• HR_GENERAL, HR_SECURITY, FND_GLOBAL, FND_FLEX_SERVER — security and context packages invoked during view evaluation.
• BOM_GLOBALS (PACKAGE) — supplies BOM profile option values that influence implosion behavior.
• Supporting objects including BOM_ALTERNATE_DESIGNATORS_TL, BOM_STRUCTURE_TYPES_VL, EGO_ITEMS_V, ENG_ENGINEERING_CHANGES, MTL_ITEM_CATALOG_GROUPS, and MTL_PARAMETERS.

Key Columns

• ORGANIZATION_ID / ORGANIZATION_CODE / ORG_NAME — the manufacturing organization context.
• LOWEST_ITEM_ID — the item from which the implosion was seeded; CURRENT_ITEM_ID — the item at the current node of the traversal.
• PARENT_ITEM_ID — the immediate assembly above the current item.
• CURRENT_LEVEL — depth of the node in the implosion hierarchy; zero denotes the seeded level.
• SEQUENCE_ID / SORT_CODE — ordering keys that preserve the traversal sequence.
• CONCATENATED_SEGMENTS / DESCRIPTION / CURRENT_DESCRIPTION — the flexfield-concatenated item number and item description for the parent and current items respectively.
• CURRENT_REVISION / REVISION_LABEL — revision identifiers resolved from MTL_ITEM_REVISIONS_B.
• COMPONENT_QUANTITY — usage quantity of the component per assembly.
• COMPONENT_EFFECTIVE_FROM / COMPONENT_EFFECTIVE_TO — decoded effectivity ranges, expressed as revision labels, unit numbers, or dates depending on EFFECTIVITY_CONTROL.
• ALTERNATE_DESIGNATOR / OPERATION_SEQ_NUM — the BOM alternate and routing operation to which the component is tied.
• CHANGE_NOTICE / IMPLEMENTED_FLAG / DISABLED_FLAG — engineering change and status attributes.

Common Use Cases and Queries

Typical usage is a where-used report seeded by a specific component. A representative query is:

• SELECT organization_code, current_concatENATED_segments, current_description, current_level, component_quantity FROM apps.bom_implosions_v WHERE lowest_item_id = :p_item AND organization_id = :p_org ORDER BY sequence_id;
• Impact analysis for engineering changes: filter on CHANGE_NOTICE or CURRENT_REVISION to identify affected assemblies.
• Cost and sourcing analysis: join COMPONENT_QUANTITY against MTL_SYSTEM_ITEMS_VL and cost tables to propagate component costs upward.
• Security-aware reporting: because HR_SECURITY and FND_GLOBAL are referenced, results are consistent with the responsibility's operating unit and organization security profile.