Search Results cst_bis_margin_build




Overview
Explore in AI Chat

Overview

CST_BIS_MARGIN_BUILD is a table owned by the BOM (Bills of Material) schema in Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. Its documented purpose is to store margin analysis load run parameters. In practical terms, it functions as a control and audit record for the Business Intelligence System (BIS) margin analysis loading process, capturing the inputs, scope, and execution context under which a margin analysis build was initiated. Each row represents a single build request submitted against a defined legal entity, operating unit, inventory organization, and cost type, bounded by a from/to date range.

The ETRM metadata assigns this table a heuristic Data Vault classification of "standalone," meaning it is modeled as neither a strict hub, link, nor satellite based on its mined foreign key structure. This classification should be treated as a modeling suggestion rather than a definitive architectural statement. The table's two documented foreign keys — to FV_LEGAL_ENTITIES and CST_COST_TYPES — indicate that a hub-and-satellite treatment could also be applied if the table were used in a Data Vault implementation, with LEGAL_ENTITY_ID and COST_TYPE_ID acting as reference dimensions.

Key Information Stored

The documented physical schema for 12.2.2 contains 20 columns. The most significant include:

BUILD_ID serves as the surrogate primary key, while BUILD_NAME and the combination of LEGAL_ENTITY_ID with COST_TYPE_ID and the date range are natural business-key candidates, though no unique index is documented in the provided metadata.

Common Use Cases and Queries

Typical scenarios involve auditing which margin analysis builds have run, verifying their scope, and reproducing a build. A common query filters builds by legal entity and cost type:

  • SELECT build_id, build_name, from_date, to_date, cost_type_id FROM cst_bis_margin_build WHERE legal_entity_id = :entity_id AND cost_type_id = :cost_type ORDER BY creation_date DESC;
  • Joining to CST_COST_TYPES to resolve cost type names for reporting.
  • Correlating REQUEST_ID with FND_CONCURRENT_REQUESTS to inspect the submitting concurrent program and its status.
  • Reporting builds by organization and operating unit for month-end margin analysis reconciliation.

Related Objects

The most significant related objects, grounded in the documented foreign keys, are:

  • FV_LEGAL_ENTITIES — joined on LEGAL_ENTITY_ID to resolve legal entity details.
  • CST_COST_TYPES — joined on COST_TYPE_ID to obtain cost type names and attributes.
  • FND_CONCURRENT_REQUESTS — correlated on REQUEST_ID to trace program execution.
  • FND_PROGRAM / FND_APPLICATION — resolved via PROGRAM_ID and PROGRAM_APPLICATION_ID.
  • HR_OPERATING_UNITS and ORG_ORGANIZATION_DEFINITIONS — for ORG_ID and ORGANIZATION_ID context.
  • CST_BIS_MARGIN_BUILD-dependent margin analysis tables referenced through HEADER_ID.