Results for “cst_xla_inv_wip_v”

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

Overview

CST_XLA_INV_WIP_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, catalogued under the Bills of Material (BOM) product family. It presents a denormalised, human-readable projection of work in process (WIP) and inventory material transactions, joining transactional facts from MTL_MATERIAL_TRANSACTIONS to descriptive reference data such as item concatenated segments, transaction types, reasons, cost groups, inventory organisations, and WIP entities. Its principal function is to support the Oracle Subledger Accounting (XLA) and Cost Management reporting layers, where inventory and WIP transaction activity must be extracted and explained in business terms rather than raw identifiers.

The view exposes a stable, read-only interface for reconciliation, audit, and custom reporting. Because it materialises foreign-key relationships at query time, consumers avoid reconstructing the joins across seven base objects. The view text originates from ETRM metadata for release 12.2.2 and remains valid in the 12.1.1 lineage, with the underlying tables structurally consistent across both releases.

Underlying Base Objects

The documented base objects referenced by the view are:

• CST_COST_GROUPS (synonym) — joined with an outer (+) operator on COST_GROUP_ID and ORG, supplying the cost group descriptor.
• MTL_MATERIAL_TRANSACTIONS (synonym) — the driving fact table; provides quantity, transaction date, subinventory, source, and reference columns.
• MTL_PARAMETERS (synonym) — supplies ORGANIZATION_CODE for the inventory organisation.
• MTL_SYSTEM_ITEMS_KFV (synonym) — the key Flexfield view returning CONCATENATED_SEGMENTS as ITEM_NAME.
• MTL_TRANSACTION_REASONS (synonym) — outer-joined to yield REASON_NAME where a reason is recorded.
• MTL_TRANSACTION_TYPES (synonym) — provides TRANSACTION_TYPE_NAME.
• WIP_ENTITIES (synonym) — joined on ORGANIZATION_ID and TRANSACTION_SOURCE_ID = WIP_ENTITY_ID to return WIP_ENTITY_NAME.

All references are synonyms pointing to the underlying APPS base tables. The joins are inner except for CST_COST_GROUPS and MTL_TRANSACTION_REASONS, which are outer-joined so that transactions lacking a cost group or reason are not excluded.

Key Columns

• ITEM_NAME — the concatenated item Flexfield segment, the user-facing item identifier.
• PRIMARY_QUANTITY — transaction quantity in the item's primary unit of measure.
• SUBINVENTORY_CODE — the subinventory affected by the transaction.
• COST_GROUP — the cost group assigned to the organisation/item combination, when present.
• ORGANIZATION_CODE — the three-character inventory organisation code.
• TRANSACTION_TYPE — the descriptive transaction type name (for example, WIP issue or completion).
• WIP_ENTITY — the WIP entity name referenced by the transaction source, central to the "wip_entity" search term.
• TRANSACTION_DATE — the effective accounting/transaction date.
• REASON_NAME — reason description for the transaction, when supplied.
• TRANSACTION_REFERENCE, TRANSACTION_ID, TRANSACTION_SOURCE_TYPE_ID, ORGANIZATION_ID — identifiers and foreign keys supporting drill-down and joins.

Common Use Cases and Queries

Typical usage includes reconciling WIP material issues and completions to the general ledger, auditing transaction volumes by organisation, and building custom WIP cost reports. Because the view already resolves the WIP entity name, it is frequently filtered on WIP_ENTITY.

Sample SQL:

• SELECT wip_entity, item_name, transaction_type, primary_quantity, transaction_date FROM cst_xla_inv_wip_v WHERE wip_entity = :p_wip_entity ORDER BY transaction_date;
• SELECT organization_code, transaction_type, SUM(primary_quantity) FROM cst_xla_inv_wip_v WHERE transaction_date BETWEEN :start_date AND :end_date GROUP BY organization_code, transaction_type;
• SELECT transaction_id, item_name, subinventory_code, cost_group, reason_name FROM cst_xla_inv_wip_v WHERE organization_id = :org_id AND transaction_source_type_id = :src_type;