Results for “cst_distribution_view”

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

Overview

The CST_DISTRIBUTION_VIEW is a single-organization reporting view owned by the APPS schema and delivered as part of the BOM (Bills of Material) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates transaction-level cost and accounting information for Work in Process (WIP) and inventory activity, exposing a unified picture of transaction value as recorded across the Material Transaction and WIP Transaction accounting tables. Its name reflects its purpose: to distribute—or present in a consumable form—cost values associated with material and resource transactions for downstream reporting.

The view draws its definition from the Cost Management (CST) domain, and its primary role is to support reporting and integration scenarios where a single, aggregated transaction value summary is required. Because it is a view rather than a table, it applies no data storage of its own; all content is materialized at query time from the underlying accounting and transaction tables. The metadata confirms a status of VALID, indicating the object is compiled and available for use.

Underlying Base Objects

The view is defined over six documented referenced objects:

• MTL_MATERIAL_TRANSACTIONS (synonym) — the core inventory material transaction source.
• MTL_TRANSACTION_ACCOUNTS (synonym) — the accounting distributions for material transactions.
• WIP_TRANSACTIONS (synonym) — WIP transaction header lines.
• WIP_TRANSACTION_ACCOUNTS (synonym) — accounting distributions for WIP transactions.
• MTL_SYSTEM_ITEMS_B (synonym) — item master details, providing the primary UOM code.
• MFG_LOOKUPS (view) — lookup values, specifically the CST_BASIS lookup type, used to resolve basis-type meaning.

The view text is a UNION of two query blocks: one over material transactions and one over WIP transactions, joined to the lookup view on the lookup type CST_BASIS. This basis-type linkage is directly responsive to the user query term cst_basis, since the view surfaces the decoded basis meaning alongside each transaction value.

Key Columns

The union exposes a consistent column set, including:

• TRANSACTION_SOURCE_ID / REPETITIVE_LINE_ID — originating source context for the transaction.
• ORGANIZATION_ID — the single inventory organization qualifying the row.
• ACCT_PERIOD_ID and TRANSACTION_DATE — period and date of the accounting event.
• TRANSACTION_TYPE_ID / TRANSACTION_TYPE — classification of the transaction.
• INVENTORY_ITEM_ID / RESOURCE_ID — the item or WIP resource affected.
• PRIMARY_QUANTITY and BASE_TRANSACTION_VALUE — quantity and the corresponding base currency value.
• PRIMARY_UOM_CODE / PRIMARY_UOM — unit of measure for the quantity.
• MEANING — the decoded CST_BASIS lookup meaning associated with the transaction.
• COST_ELEMENT_ID — the cost element to which the value is attributed.
• OPERATION_SEQ_NUM / RESOURCE_SEQ_NUM — routing sequence context for WIP rows.

The view also computes a derived unit value by dividing BASE_TRANSACTION_VALUE by the primary quantity, with DECODE logic guarding against zero and null quantities.

Common Use Cases and Queries

The view is typically used for cost distribution reporting, basis analysis, and reconciliation between material and WIP accounting. A common query filters by organization and period:

• Summarizing base transaction value by basis meaning and cost element for a given organization and accounting period.
• Comparing material versus WIP transaction values across transaction types.
• Reviewing the basis type (CST_BASIS) applied to each distribution line.

Sample query:

SELECT organization_id, acct_period_id, meaning, cost_element_id, SUM(base_transaction_value) total_value FROM cst_distribution_view WHERE organization_id = :org_id GROUP BY organization_id, acct_period_id, meaning, cost_element_id;

Because the view is single-org in scope, callers must always constrain by ORGANIZATION_ID to obtain meaningful, performant results.