Search Results cst_bis_margin_summary




Overview
Explore in AI Chat

Overview

CST_BIS_MARGIN_SUMMARY is a reporting table owned by the BOM schema in Oracle E-Business Suite, documented as part of the Bills of Material product family. Its documented description identifies it as a "margin analysis summary table for reporting purposes," indicating that it serves as a pre-aggregated or denormalized data store that supports margin and profitability reporting rather than transactional order entry. The table contains 77 documented columns and is classified as VALID in ETRM 12.2.2, with the same structure expected in the 12.1.1 environment.

The object carries no foreign-key dependencies to transactional child tables and is mined from the FK structure as standalone under the heuristic Data Vault classification. In Data Vault modeling terms, this suggests treating CST_BIS_MARGIN_SUMMARY as a self-contained artifact that behaves most like a reporting satellite or flat summary mart rather than a hub or link. Because its foreign keys point outward to reference and transactional masters (legal entities, order types, RMA lines), it is best modeled as a dependent reporting construct, not a source of business keys.

Key Information Stored

The table stores margin, cost, and revenue metrics at the invoice and order line level, enriched with organizational, customer, and period attributes. The most significant columns are:

Common Use Cases and Queries

The principal use case is margin and profitability analysis by period, customer, item, and geography. Typical queries aggregate MARGIN and MARGIN_PCT across period and organizational dimensions:

  • Monthly margin trend by legal entity: SELECT PERIOD_NAME_MONTH, LEGAL_ENTITY_ID, SUM(MARGIN), AVG(MARGIN_PCT) FROM CST_BIS_MARGIN_SUMMARY GROUP BY PERIOD_NAME_MONTH, LEGAL_ENTITY_ID;
  • Margin by customer and region: join CUSTOMER_ID and REGION_NAME to produce a customer profitability matrix.
  • Return impact analysis: filter on RETURN_REFERENCE_TYPE_CODE to isolate RMA-driven margin erosion.
  • Invoice reconciliation: join CUSTOMER_TRX_ID/CUSTOMER_TRX_LINE_ID back to AR to validate summarized INVOICED_AMOUNT against posted invoice lines.

Because the table is a summary construct, it is well suited to BI Publisher reports and Oracle Discoverer/Essbase extracts without touching high-volume transactional tables.

Related Objects

The documented FK relationships identify the following significant related objects:

Additional dependencies are implied through the business columns rather than declared FKs, including RA_CUSTOMER_TRX_ALL/RA_CUSTOMER_TRX_LINES_ALL (via CUSTOMER_TRX_ID and CUSTOMER_TRX_LINE_ID), OE_ORDER_HEADERS_ALL/OE_ORDER_LINES_ALL (via HEADER_ID and LINE_ID), MTL_SYSTEM_ITEMS_B (via INVENTORY_ITEM_ID), and the GL period tables underlying the PERIOD_* columns.