Search Results cst_margin_temp

Overview

The view ICX_CST_MARGIN_TEMP_V belongs to the Oracle iProcurement (ICX) product family within Oracle E-Business Suite. Per the ETRM documentation metadata for release 12.1.1 and 12.2.2, the view is explicitly flagged as Obsolete and is not implemented in this database. Its presence in the data dictionary is therefore historical rather than functional: it represents a legacy construct that once supported margin analysis and cost reporting surfaces in earlier iProcurement or Cost Management flows, but it is not shipped or instantiated in current installations.

The view was designed to expose a filtered, single-build snapshot of margin-related transactional data drawn from the temporary margin staging structures. Its defining characteristic is a restriction to the latest build identifier and to a rolling 90-day window relative to the build's "to date," which made it suitable for point-in-time margin reporting rather than for permanent storage of financial results.

Underlying Base Objects

The ETRM metadata does not document any referenced base objects, but the view text itself is definitive. The view is defined over two source objects:

• CST_MARGIN_TEMP (aliased CMT) — a temporary/staging table holding the granular margin detail rows, keyed by BUILD_ID.
• CST_MARGIN_BUILD (aliased CMB) — the build header table recording each margin extraction run and its boundary date (TO_DATE).

The join conditions link CMT.BUILD_ID = CMB.BUILD_ID, restrict rows to CMT.GL_DATE >= CMB.TO_DATE - 90, and further constrain the result to the maximum build identifier via a correlated subquery: CMT.BUILD_ID = (SELECT MAX(CMT.BUILD_ID) FROM CST_MARGIN_TEMP). The result is that only the most recent margin build, limited to the trailing 90 days of GL activity, is surfaced.

Key Columns

The projected column list is extensive and spans order, invoice, cost, and margin dimensions. Notable columns include:

• Build and source context: BUILD_ID, SOURCE, ROW_TYPE, ORIGIN, INVOICE_SOURCE, PARENT_ROWID.
• Order identifiers: ORDER_NUMBER, HEADER_ID, ORDER_TYPE_ID, LINE_ID, LINE_NUMBER, LINE_TYPE_CODE, PARENT_LINE_ID, PARENT_LINE_NUMBER.
• Customer and party data: CUSTOMER_ID, SOLD_TO_CUSTOMER_NAME, SHIP_TO_CUSTOMER_NAME, BILL_TO_CUSTOMER_NAME, CUSTOMER_CLASS_CODE, PRIMARY_SALESREP_ID, SALES_CHANNEL_CODE, TERRITORY_ID.
• Item and organization context: INVENTORY_ITEM_ID, ORGANIZATION_ID, PARENT_INVENTORY_ITEM_ID, PARENT_ORGANIZATION_ID, PARENT_ITEM_TYPE_CODE, PARENT_ATO_FLAG.
• Invoice and accounting: CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID, ORIGINAL_GL_DATE, GL_DATE, INVOICED_AMOUNT, COGS_AMOUNT, SALES_ACCOUNT, COGS_ACCOUNT.
• Quantity and margin measures: ORDER_LINE_QUANTITY, SHIP_QUANTITY, INVOICE_QUANTITY, INVOICE_LINE_QUANTITY, and the derived MARGIN and MARGIN_PCT.
• Returns/RMA linkage: RETURN_REFERENCE_TYPE_CODE, RETURN_REFERENCE_ID, LINK_TO_LINE_ID, RMA_HEADER_ID, RMA_NUMBER, RMA_LINE_ID, RMA_LINE_NUMBER, RMA_ORGANIZATION_ID, RMA_LINE_TYPE_CODE, RMA_SHIP_TO_SITE_USE_ID, RMA_INVOICE_INVENTORY_ITEM_ID, CR_TRX_ID, CR_TRX_LINE_ID.

Together these columns allow reconciliation of sold quantities, invoiced amounts, and cost of goods sold against the resulting margin at both the line and return-document level.

Common Use Cases and Queries

Because the view is marked Obsolete and not implemented, it should not appear in any production query path in 12.1.1 or 12.2.2. Historical references to it typically originate from legacy customizations, older margin-reporting extensions, or migration artifacts. In environments where the underlying CST_MARGIN_TEMP and CST_MARGIN_BUILD structures still exist, a query against the view would logically resemble:

• Margin summary by customer class: SELECT CUSTOMER_CLASS_CODE, SUM(INVOICED_AMOUNT), SUM(COGS_AMOUNT), SUM(MARGIN) FROM ICX_CST_MARGIN_TEMP_V GROUP BY CUSTOMER_CLASS_CODE;
• Top-margin orders: SELECT ORDER_NUMBER, MARGIN_PCT FROM ICX_CST_MARGIN_TEMP_V WHERE MARGIN_PCT > 25 ORDER BY MARGIN_PCT DESC;
• Returns impact analysis: SELECT RMA_NUMBER, SUM(MARGIN) FROM ICX_CST_MARGIN_TEMP_V GROUP BY RMA_NUMBER;

These queries are illustrative. In supported releases, equivalent margin analysis is delivered through Oracle Cost Management and Receivables reporting rather than through this obsolete view. Organizations encountering it should treat it as a documentation remnant and validate any dependent interface before relying on it.