Search Results build_description




Overview
Explore in AI Chat

Overview

APPS.ICX_CST_MARGIN_BUILD_V is a reporting view in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the APPS schema. Its purpose is to expose a single, current record from the margin build infrastructure used by Oracle Cost Management. Unlike a standard join or aggregation view, ICX_CST_MARGIN_BUILD_V is defined with a self-restricting predicate that returns only the most recent build row based on the maximum BUILD_ID present in the base table. The view therefore presents the latest margin build definition—its name, description, effective date range, operating unit scope (ORG_ID), and associated header—without requiring the caller to compute the maximum identifier. This makes it a convenience view for Oracle iProcurement, iSupplier, and other ICX-family integrations that need a stable reference to the active margin build configuration.

Underlying Base Objects

The view is defined entirely over a single base table, CST_MARGIN_BUILD. The documented view text is:

No additional referenced base objects are documented in the ETRM metadata; the view is a straightforward projection over CST_MARGIN_BUILD with an inline subquery acting as a filter. CST_MARGIN_BUILD is the Cost Management table that stores margin build definitions, each uniquely identified by BUILD_ID. Because the WHERE clause uses the MAX(BUILD_ID) subquery with no correlated ORG_ID or date restriction, the view returns exactly one row across the entire table—the row with the highest BUILD_ID, which corresponds to the most recently created margin build. It does not return one row per organization or per effective period.

Key Columns

The view exposes nine columns, all passed through directly from CST_MARGIN_BUILD:

  • BUILD_ID — Primary identifier of the margin build; the basis for the MAX() filter that selects the current row.
  • BUILD_NAME — User-defined name of the margin build, typically used as the display label in ICX applications.
  • BUILD_DESCRIPTION — Descriptive text for the build; this is the column most commonly searched by users and report developers seeking the latest build definition.
  • FROM_DATE / TO_DATE — Effective start and end dates of the margin build, defining the period over which the build applies.
  • ORG_ID — Operating unit (organization) identifier to which the build belongs, supporting multi-org filtering.
  • HEADER_ID — Foreign key reference to the associated margin header record.
  • CREATION_DATE / CREATED_BY — Standard audit columns indicating when and by whom the build record was created.

Common Use Cases and Queries

The view is most useful when an application needs the latest margin build without embedding MAX() logic. A typical query retrieves the current build for validation or display:

  • SELECT BUILD_ID, BUILD_NAME, BUILD_DESCRIPTION, FROM_DATE, TO_DATE FROM APPS.ICX_CST_MARGIN_BUILD_V;
  • SELECT BUILD_NAME, BUILD_DESCRIPTION FROM APPS.ICX_CST_MARGIN_BUILD_V WHERE ORG_ID = :p_org_id;

Because only one row is returned, callers should be aware that filtering by ORG_ID may yield no rows if the most recent build belongs to a different operating unit. For consumers needing the latest build per organization, querying CST_MARGIN_BUILD directly with an analytic function or correlated MAX() on ORG_ID is preferable. ICX-based pages in iProcurement and related modules may reference this view to display the active margin build description alongside cost or pricing information. Report developers should treat it as a single-row convenience object rather than a complete listing of margin builds, and should verify ORG_ID and date-range applicability before using its output for calculations.