Results for “cst_xla_inv_cu_v”

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

Overview

CST_XLA_INV_CU_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and validated for both release 12.1.1 and 12.2.2. Although it is catalogued under the BOM (Bills of Material) product family in the ETRM metadata, the view serves the Cost Management and Subledger Accounting (XLA) reporting domain. Its name encodes its purpose: CST for Costing, XLA for Subledger Accounting, INV for Inventory, and CU for Cost Update. The view presents inventory material transactions that are associated with cost update activity, joining transaction detail to cost group and cost update definitions so that adjustments arising from standard cost revaluation can be reported and reconciled.

The view functions as a denormalized, read-only presentation layer. Rather than requiring report authors to reconstruct the multi-table join between material transactions and cost updates, it delivers a single row per qualifying transaction with human-readable identifiers instead of internal numeric keys, making it suitable for BI Publisher reports, Blitz Report extracts, and XLA reconciliation queries.

Underlying Base Objects

The view is defined over seven base objects, all referenced through APPS synonyms: MTL_MATERIAL_TRANSACTIONS, MTL_PARAMETERS, MTL_SYSTEM_ITEMS_KFV, MTL_TRANSACTION_TYPES, MTL_TRANSACTION_REASONS, CST_COST_GROUPS, and CST_COST_UPDATES.

The driving table is MTL_MATERIAL_TRANSACTIONS (MMT), which is joined to MTL_PARAMETERS on ORGANIZATION_ID to resolve the inventory organization, to MTL_SYSTEM_ITEMS_KFV on ORGANIZATION_ID and INVENTORY_ITEM_ID to resolve the concatenated item segment string, and to MTL_TRANSACTION_TYPES on TRANSACTION_TYPE_ID to obtain the transaction type name. Two outer joins are applied: MTL_TRANSACTION_REASONS is joined on REASON_ID, and CST_COST_GROUPS is joined on COST_GROUP_ID with an additional NVL-based predicate ensuring the cost group organization matches the transaction organization. The critical link to cost update information is the outer join of MMT.TRANSACTION_SOURCE_ID to CST_COST_UPDATES.COST_UPDATE_ID, which is the join that gives the view its cost-update character. Because the cost group and cost update joins are outer, transactions without a matching cost grouping still appear.

Key Columns

• ITEM_NAME — the concatenated segment string from MTL_SYSTEM_ITEMS_KFV, providing the report-ready item identifier.
• PRIMARY_QUANTITY — the quantity of the material transaction in the item's primary unit of measure.
• SUBINVENTORY_CODE — the subinventory in which the transaction occurred.
• COST_GROUP — the cost group description associated with the transaction's cost group identifier.
• ORGANIZATION_CODE — the inventory organization code from MTL_PARAMETERS.
• TRANSACTION_TYPE — the descriptive name of the transaction type from MTL_TRANSACTION_TYPES.
• COST_UPDATE — the description of the cost update record from CST_COST_UPDATES; this is the column most directly associated with the user's search term "cost_update."
• TRANSACTION_DATE — the effective date of the material transaction.
• REASON_NAME — the descriptive reason name, if a transaction reason was recorded.
• TRANSACTION_REFERENCE, TRANSACTION_ID, TRANSACTION_SOURCE_TYPE_ID, ORGANIZATION_ID — technical identifiers supporting drill-down and integration with other XLA or costing views.

Common Use Cases and Queries

The view is typically used to audit cost update transactions, trace revaluation impact by organization and item, and feed Subledger Accounting reconciliation reports. A representative query returning recent cost update activity for a given organization is:

SELECT item_name, organization_code, transaction_type, cost_update, primary_quantity, transaction_date FROM cst_xla_inv_cu_v WHERE organization_id = :org_id AND cost_update IS NOT NULL ORDER BY transaction_date DESC;

A second common pattern restricts output to a specific accounting period or item range for cost adjustment analysis:

SELECT item_name, subinventory_code, cost_group, cost_update, transaction_reference FROM cst_xla_inv_cu_v WHERE transaction_date BETWEEN :start_date AND :end_date AND item_name LIKE :item_pattern;

Because several joins are outer joins, reports should anticipate null values in COST_GROUP, REASON_NAME, and COST_UPDATE for transactions lacking those attributes. Filtering on COST_UPDATE IS NOT NULL isolates the population that is genuinely tied to cost update events.