Results for “mutually_exclusive_options”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BOM_PLM_EXPLOSION_TEMP is a read-only view owned by the APPS schema in Oracle E-Business Suite (validated across 12.1.1 and 12.2.2). Within the Bills of Material module, it functions as the PLM-facing projection of the bill explosion staging area. Where BOM_EXPLOSION_TEMP holds the raw, session-scoped rows produced when an engineer performs an indented or summarized explosion, BOM_PLM_EXPLOSION_TEMP re-presents those rows in a shape suitable for Product Lifecycle Management consumers — engineering workbench screens, change-order impact analysis, and external integration feeds.

The view does not transform the data; it exposes the complete column set of the underlying temporary object, including the multi-level hierarchy identifiers (TOP_BILL_SEQUENCE_ID, BILL_SEQUENCE_ID, COMPONENT_SEQUENCE_ID), the planning identifiers (PLAN_LEVEL, SORT_ORDER, PARENT_SORT_ORDER), revision/effectivity structures, and the descriptive flexfield segment columns ATTRIBUTE1 through ATTRIBUTE15. Because it is defined only over a single synonym, it is a simple column-projection view rather than a join-based reporting view.

Underlying Base Objects

The view is defined exclusively over the synonym BOM_EXPLOSION_TEMP, which resolves within APPS to the temporary table populated by the bill explosion program (the row source that also feeds the standard indented bill report). The relationship is one-to-one and column-preserving: every row the explosion process writes to the temporary structure is visible through this view with identical cardinality and ordering semantics.

As a temporary, session-private staging object, BOM_EXPLOSION_TEMP is only meaningful immediately after an explosion call populates it for the current session. Consequently, BOM_PLM_EXPLOSION_TEMP inherits that lifecycle: it is a transient reporting surface, not a persistent warehouse source.

Key Columns

• TOP_BILL_SEQUENCE_ID / BILL_SEQUENCE_ID / COMMON_BILL_SEQUENCE_ID — Link back to the top-level bill and each exploded level, enabling reconstruction of parent-child hierarchy.
• TOP_ALTERNATE_DESIGNATOR — The alternate BOM designator applied at the top of the explosion; the column most commonly requested by users searching "top_alternate_designator," since it distinguishes an alternate-component explosion from the primary bill.
• COMPONENT_ITEM_ID / TOP_ITEM_ID / ASSEMBLY_ITEM_ID — Component, top assembly, and immediate parent assembly identifiers.
• COMPONENT_QUANTITY / EXTENDED_QUANTITY / PLANNING_FACTOR / COMPONENT_YIELD_FACTOR — Per-level and rolled-up usage quantities.
• PLAN_LEVEL / SORT_ORDER / PARENT_SORT_ORDER — Level number and display ordering for indented presentation.
• ALTERNATE_BOM_DESIGNATOR — Alternate designator at the component level.
• EFFECTIVITY_DATE / DISABLE_DATE / REVISION_LABEL / REVISION_ID / CURRENT_REVISION — Date-effectivity and revision context.
• COMPONENT_CODE / NEW_COMPONENT_CODE / WIP_SUPPLY_TYPE / INCLUDE_IN_ROLLUP_FLAG / LOOP_FLAG — Explosion control and classification flags.
• ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield segments.

Common Use Cases and Queries

Typical use is within the same session that invoked the explosion, generally for validating an alternate bill, reporting structure, or exporting to PLM. A representative query isolating the top alternate designator follows:

SELECT TOP_BILL_SEQUENCE_ID, BILL_SEQUENCE_ID, TOP_ALTERNATE_DESIGNATOR, PLAN_LEVEL, COMPONENT_ITEM_ID, COMPONENT_QUANTITY, EXTENDED_QUANTITY, REVISION_LABEL FROM APPS.BOM_PLM_EXPLOSION_TEMP ORDER BY TOP_BILL_SEQUENCE_ID, PLAN_LEVEL, SORT_ORDER;

Because rows are transient, queries should be executed immediately after the explosion program populates the temporary object within the same database session.