Results for “bom_copy_explosions_v”
32 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BOM_COPY_EXPLOSIONS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered as VALID in both release 12.1.1 and 12.2.2. It belongs to the Bills of Material (BOM) product family and is documented in ETRM as a "View for Multi level copy structure." Its purpose is to expose the exploded, multi-level structure of a bill of material in a denormalized form suitable for the Copy Bill of Material and Copy Structure processes, where an engineer or planner copies an entire indented assembly from a source organization to a destination organization.
The view does not store data; it is a presentation layer over the BOM_EXPLOSIONS_ALL synonym and the BOM_EXPLODER_PUB PL/SQL package. It therefore returns dynamically derived revision, alternate, and effectivity information rather than a simple projection of a base table. In reporting and integration terms, it is most often consumed by custom reports, conversion scripts, and interface programs that need an indented structure without calling the BOM exploder API directly.
Underlying Base Objects
The documented references for this view are:
- BOM_EXPLODER_PUB (PACKAGE) — supplies revision and revision label derivation through functions such as GET_COMPONENT_REVISION, GET_COMPONENT_REVISION_LABEL, and GET_COMPONENT_REVISION_ID.
- BOM_EXPLOSIONS_ALL (SYNONYM) — aliased as BE in the view text and provides the exploded structure rows, including sequence identifiers, quantities, and effectivity columns.
- BOM_GLOBALS (PACKAGE) — supplies GET_ALTERNATE, used to populate the alternate BOM designator.
- MTL_ITEM_REVISIONS_B (SYNONYM) — referenced for revision control.
- MTL_SYSTEM_ITEMS_B_KFV (VIEW) — key flexfield view joined as MSIBK to return CONCATENATED_SEGMENTS for the component item.
Because BOM_EXPLOSIONS_ALL is a synonym over the BOM_EXPLOSIONS table, the view inherits the organization-specific data stored there and combines it with real-time package calls to resolve current revision metadata at query time.
Key Columns
- TOP_BILL_SEQUENCE_ID, BILL_SEQUENCE_ID, COMPONENT_SEQUENCE_ID — identify the top-level assembly, the parent bill, and each component occurrence within the explosion.
- ORGANIZATION_ID, TOP_ITEM_ID, COMPONENT_ITEM_ID, ASSEMBLY_ITEM_ID — the organizational and item context; COMPONENT_ITEM_ID is wrapped in NVL(...,-1).
- COMPONENT_QUANTITY — the usage quantity per assembly.
- PLAN_LEVEL, SORT_ORDER, PARENT_SORT_ORDER — indentation and ordering attributes for presenting the multi-level structure.
- EXPLOSION_TYPE, BOM_ITEM_TYPE, PARENT_BOM_ITEM_TYPE — indicate the nature of the structure and item types.
- EFFECTIVITY_DATE, DISABLE_DATE, IMPLEMENTATION_DATE — date-based effectivity of the component.
- CURRENT_REVISION, REVISION_LABEL, REVISION_CODE, REVISION_ID — derived via BOM_EXPLODER_PUB from the component sequence.
- ALT_BOM_DESIG — the alternate BOM designator returned by BOM_GLOBALS.GET_ALTERNATE.
- CONCATENATED_SEGMENTS — the concatenated key flexfield of the component item from MTL_SYSTEM_ITEMS_B_KFV.
- CHANGE_NOTICE, CHANGE_ID — engineering change context.
- LOOP_FLAG — indicates whether the explosion encountered a loop.
- PICK_COMPONENTS_FLAG, REPLENISH_TO_ORDER_FLAG — supply and planning attributes.
Common Use Cases and Queries
The principal use case is supporting the Copy Structure function, where the exploded rows for a top assembly are read, inspected, and then re-created under a new parent. It is also used for structure comparison reports, cost rollup validation, and data migration of multi-level bills between organizations.
A typical query retrieves the indented structure for a given top item in an organization:
- SELECT bill_sequence_id, component_sequence_id, plan_level, component_item_id, component_quantity, concatenated_segments, current_revision FROM bom_copy_explosions_v WHERE organization_id = :org_id AND top_item_id = :top_item_id ORDER BY plan_level, sort_order;
To isolate components still effective on a given date:
- SELECT component_item_id, component_quantity, effectivity_date, disable_date FROM bom_copy_explosions_v WHERE bill_sequence_id = :bill_seq_id AND :check_date BETWEEN effectivity_date AND NVL(disable_date, :check_date);
Because revision and alternate values are resolved through PL/SQL calls, large extractions should be filtered aggressively on ORGANIZATION_ID or TOP_BILL_SEQUENCE_ID to limit the number of package invocations. The view should be treated as read-only; all maintenance is performed through the BOM copy and exploder APIs rather than against this object.
-
View: BOM_COPY_EXPLOSIONS_V 12.2.2
View for Multi level copy structure
APPS.BOM_COPY_EXPLOSIONS_V·↳ BOM_EXPLODER_PUB·↳ BOM_EXPLOSIONS_ALL·↳ BOM_GLOBALS·Explore BOM module →
-
View: BOM_COPY_EXPLOSIONS_V 12.1.1
View for Multi level copy structure
APPS.BOM_COPY_EXPLOSIONS_V·↳ BOM_EXPLODER_PUB·↳ BOM_EXPLOSIONS_ALL·↳ BOM_GLOBALS·Explore BOM module →
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
PACKAGE: APPS.BOM_COPY_BILL 12.2.2
-
PACKAGE: APPS.BOM_COPY_BILL 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - BOM Tables and Views 12.2.2
Table to map wip transactions to their corresponding event types.
-
eTRM - BOM Tables and Views 12.1.1
Table to map wip transactions to their corresponding event types.
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - BOM Tables and Views 12.2.2
Table to map wip transactions to their corresponding event types.
-
eTRM - BOM Tables and Views 12.1.1
Table to map wip transactions to their corresponding event types.
-
eTRM - INV Tables and Views 12.1.1