Results for “cst_sc_bom_structures”

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

Overview

CST_SC_BOM_STRUCTURES is a Bills of Material module table owned by the BOM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores flattened, exploded supply chain bill of material structures used by Oracle's costing engine to roll up material and component costs across multi-level assemblies. Each row represents one component occurrence within an exploded structure rooted at a specific top-level inventory item and organization, ordered by a sort sequence that preserves the hierarchical traversal performed during rollup.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault model. Because no foreign key dependencies were mined from the physical schema, no hub, link, or satellite assignment is asserted; the table functions as a self-contained structure whose grain is defined by its primary key rather than by an external relationship graph.

Key Information Stored

The table contains 28 documented columns. The composite primary key CST_SC_BOM_STRUCTURES_PK consists of ROLLUP_ID, TOP_INVENTORY_ITEM_ID, TOP_ORGANIZATION_ID, and SORT_ORDER. The unique index CST_SC_BOM_STRUCTURES_U1 carries the identical column set, making it a business-key candidate that enforces one component occurrence per sort position within a given rollup and top-level item/organization combination.

• ROLLUP_ID — Identifier grouping the rows belonging to a single cost rollup run or structure definition.
• TOP_INVENTORY_ITEM_ID / TOP_ORGANIZATION_ID — The root assembly and its owning inventory organization.
• SORT_ORDER — Position of the row in the exploded hierarchy; part of the primary key.
• BOM_LEVEL — Depth of the component within the explosion.
• ASSEMBLY_ITEM_ID / ASSEMBLY_ORGANIZATION_ID — The parent assembly that directly contains the component.
• COMPONENT_ITEM_ID / COMPONENT_ORGANIZATION_ID — The component item and its organization.
• COMPONENT_SEQUENCE_ID — Reference to the BOM component line that generated the row.
• COMPONENT_QUANTITY / EXTENDED_QUANTITY — Per-assembly usage and the usage extended through all parent levels.
• INCLUDE_IN_COST_ROLLUP / EXTEND_COST_FLAG — Indicators controlling whether the component participates in costed quantities.
• PHANTOM_FLAG / PHANTOM_FACTOR — Phantom assembly treatment and the multiplier applied to phantom components.
• ERROR_CODE / ERROR_MESG — Diagnostics populated when rollup processing encounters structural problems.
• LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID and related audit columns — Standard concurrent-program and audit tracking.

Common Use Cases and Queries

Typical reporting identifies where an item appears in a rollup, reproduces the exploded structure in indented BOM reports, and diagnoses rollup failures.

• Retrieve all components for a top-level assembly: SELECT SORT_ORDER, BOM_LEVEL, COMPONENT_ITEM_ID, EXTENDED_QUANTITY FROM BOM.CST_SC_BOM_STRUCTURES WHERE ROLLUP_ID = :p_rollup AND TOP_INVENTORY_ITEM_ID = :p_item AND TOP_ORGANIZATION_ID = :p_org ORDER BY SORT_ORDER;
• Isolate failed structures using WHERE ERROR_CODE IS NOT NULL for concurrent request troubleshooting.
• Compare extended versus component quantity to validate quantity rollups across levels.
• Filter INCLUDE_IN_COST_ROLLUP = 'Y' for costed-only component lists, and inspect PHANTOM_FLAG rows when reconciling phantom assemblies.

Related Objects

The metadata reports no mined foreign keys, so relationships below are functional rather than enforced:

• BOM_BILL_OF_MATERIALS / BOM_INVENTORY_COMPONENTS — Source BOM definitions matched on COMPONENT_SEQUENCE_ID.
• MTL_SYSTEM_ITEMS_B — Item validation for TOP_INVENTORY_ITEM_ID, ASSEMBLY_ITEM_ID, and COMPONENT_ITEM_ID.
• MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — Organization validation for the *_ORGANIZATION_ID columns.
• CST_ITEM_COSTS — Item cost records consumed during rollup calculations.
• CST_SC_* interface and rollup tables — Companion supply chain costing structures sharing ROLLUP_ID.
• FND_CONCURRENT_REQUESTS — Joined on REQUEST_ID to trace the rollup program invocation.