Results for “cst_xla_move_txn_ref_v”

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

Overview

CST_XLA_MOVE_TRANSACTION_REF_V is an Oracle E-Business Suite view owned by the APPS schema and defined within the Bills of Material (BOM) product family. It exposes move transaction information originating in Work in Process (WIP) so that it can be consumed by the Subledger Accounting (XLA) and Cost Management (CST) engines for accounting event generation and cost processor reference. The naming convention — CST (Cost Management), XLA (Subledger Accounting), MOVE_TXN (move transaction), REF (reference), _V (view) — reflects its purpose: it provides a stabilized, renamed projection of WIP move transaction data that downstream XLA accounting programs use when constructing journal entries for material moves on the shop floor.

The view is important in EBS 12.1.1 and 12.2.2 because WIP move transactions generate material and resource accounting entries through the Create Accounting process. Rather than reading WIP_MOVE_TRANSACTIONS directly, the SLA/CST integration layer references this view, which standardizes column naming and exposes the transaction quantity, UOM, primary quantity, and DFF attributes needed to derive accounting rules. The view is read-only and presents one row per move transaction.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over a single base object:

• WIP_MOVE_TRANSACTIONS (referenced via a SYNONYM) — the WIP table that stores move transactions executed against discrete jobs and repetitive schedules.

Although the view text is documented as selecting from WIP_MOVE_TRANSACTIONS, note that the actual view text shipped in the ETRM documentation shows an intermediate projection with source column names such as TRANSACTION_ID, TRANSACTION_DATE, TRANSACTION_QUANTITY, TRANSACTION_UOM, PRIMARY_QUANTITY, PRIMARY_UOM, and ATTRIBUTE1..ATTRIBUTE15, which the view then re-labels with the MOVE_TRANSACTION_ID / MOVE_TXN_* aliases listed in the Columns section. There is a direct one-to-one lineage between each exposed column and its WIP_MOVE_TRANSACTIONS source column (for example, MOVE_TRANSACTION_ID maps to TRANSACTION_ID, and MOVE_TXN_TXN_QTY maps to TRANSACTION_QUANTITY). No other base table, synonym, or join is documented for this view.

Key Columns

• MOVE_TRANSACTION_ID — The unique identifier of the WIP move transaction (aliased from TRANSACTION_ID). This is the primary key used to correlate the move with its WIP job, accounting event, and cost records.
• MOVE_TRANSACTION_DATE — The date the move transaction was performed (aliased from TRANSACTION_DATE); used for period and accounting-date derivation.
• MOVE_TXN_TXN_QTY / MOVE_TXN_TXN_UOM — The quantity moved in the transaction's own unit of measure, and that UOM.
• MOVE_TXN_PRIMARY_QTY / MOVE_TXN_PRIMARY_UOM — The quantity expressed in the item's primary UOM, enabling consistent cost and valuation processing.
• MOVE_TXN_ATTRIBUTE_CATEGORY and MOVE_TXN_ATTRIBUTE1 … MOVE_TXN_ATTRIBUTE15 — The descriptive flexfield (DFF) context and segment columns carried from WIP_MOVE_TRANSACTIONS, frequently used for accounting rule mapping and reporting.

Common Use Cases and Queries

Typical uses include reconciliation of WIP moves to SLA journal entries, reporting of moved quantities by job, and supplying move transaction references to custom XLA or cost reporting. Because the view is a thin projection of WIP_MOVE_TRANSACTIONS, queries are straightforward. A sample lookup by move transaction identifier:

• SELECT MOVE_TRANSACTION_ID, MOVE_TRANSACTION_DATE, MOVE_TXN_TXN_QTY, MOVE_TXN_TXN_UOM, MOVE_TXN_PRIMARY_QTY, MOVE_TXN_PRIMARY_UOM FROM APPS.CST_XLA_MOVE_TXN_REF_V WHERE MOVE_TRANSACTION_ID = :move_transaction_id;
• SELECT MOVE_TRANSACTION_ID, MOVE_TXN_PRIMARY_QTY, MOVE_TXN_ATTRIBUTE_CATEGORY FROM APPS.CST_XLA_MOVE_TXN_REF_V WHERE MOVE_TRANSACTION_DATE BETWEEN :start_date AND :end_date;

These queries support accounting reconciliation, DFF-based reporting, and integration extracts while keeping consumers insulated from the underlying WIP_MOVE_TRANSACTIONS structure.