Results for “cst_margin_build”

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

Overview

CST_MARGIN_BUILD is a table owned by the BOM (Bills of Material) schema in Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. Its documented purpose is to store margin analysis load run parameters. In practice, this table acts as the header repository for the Margin Analysis process, which derives cost, price, and profitability information at the order or legal-entity level for reporting and analysis. Each row represents a single build (load run) definition, capturing the parameters that govern how margin data is selected, bounded, and processed.

Under the heuristic Data Vault classification derived from its foreign key structure, CST_MARGIN_BUILD is best modeled as a link entity. It sits at the intersection of several master and transactional references — sales order headers, cost types, inventory organizations, and legal entities — and is designed to record the association between a named build and the parameter context in which it executes. It is not a pure descriptive satellite of a single parent, nor a standalone hub; rather, it captures relationships plus run-level attributes.

Key Information Stored

The table contains 20 documented columns. The most significant are:

• BUILD_ID — surrogate primary key, enforced by CST_MARGIN_BUILD_PK and duplicated in unique index CST_MARGIN_BUILD_U1. It uniquely identifies each margin analysis load run.
• BUILD_NAME — business-key candidate, enforced by unique index CST_MARGIN_BUILD_U2. This is the user-facing identifier for the build.
• BUILD_DESCRIPTION — free-text description of the run's purpose.
• LEGAL_ENTITY_ID and LEGAL_ENTITY_NAME — the legal entity context for the margin analysis, with LEGAL_ENTITY_ID referencing FV_LEGAL_ENTITIES.
• ORGANIZATION_ID and ORG_ID — the inventory organization and operating unit context; ORGANIZATION_ID references MTL_PARAMETERS.
• COST_TYPE_ID — the cost type used in the analysis, referencing CST_COST_TYPES.
• HEADER_ID — sales order header reference, joining to SO_HEADERS_ALL.
• FROM_DATE and TO_DATE — the effective date range constraining the data included in the run.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE — concurrent program context identifying the job that created or last updated the row.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on identifying and auditing margin analysis runs, and on joining build parameters to their referenced masters for reporting. A frequent pattern retrieves the most recent builds for an organization:

• SELECT build_id, build_name, from_date, to_date FROM cst_margin_build WHERE organization_id = :org_id ORDER BY creation_date DESC;
• Join to CST_COST_TYPES on cost_type_id to display the cost type name alongside each build.
• Join to MTL_PARAMETERS on organization_id to resolve the organization code for cross-organization reporting.
• Join to FV_LEGAL_ENTITIES on legal_entity_id to report margin builds by legal entity.
• Filter by REQUEST_ID or PROGRAM_ID to trace a specific concurrent program execution.

These queries support cost accounting reconciliation, profitability reporting, and troubleshooting of margin load failures.

Related Objects

• SO_HEADERS_ALL — joined via CST_MARGIN_BUILD.HEADER_ID, providing the sales order context.
• CST_COST_TYPES — joined via CST_MARGIN_BUILD.COST_TYPE_ID, defining the costing method used.
• MTL_PARAMETERS — joined via CST_MARGIN_BUILD.ORGANIZATION_ID, supplying organization defaults.
• FV_LEGAL_ENTITIES — joined via CST_MARGIN_BUILD.LEGAL_ENTITY_ID, resolving legal entity identity.
• CST_MARGIN_BUILD_PK / CST_MARGIN_BUILD_U1 / CST_MARGIN_BUILD_U2 — the primary and unique indexes enforcing identity and business keys.