Search Results inv_txn_basis_type

Overview

CST_XLA_INV_LINES_V is a seeded Oracle E-Business Suite view owned by the APPS schema that exposes Inventory transaction accounting lines in the format required by Subledger Accounting (XLA). It functions as the Inventory application's line-level data source to the Create Accounting process, presenting costing information from MTL_TRANSACTION_ACCOUNTS as SLA-compatible accounting lines with event identifiers, amounts, currency attributes, and balancing segment attributes. The view is not a general-purpose reporting object; it is an internal integration view consumed by the XLA accounting engine, though it is frequently queried during costing and accounting diagnostics in both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over a set of documented base objects that fall into three functional groups:

• MTL_MATERIAL_TRANSACTIONS (synonym) — supplies the transaction header context, including transaction date, primary quantity, currency conversion information, and the header subinventory and transfer subinventory codes.
• MTL_TRANSACTION_ACCOUNTS (synonym) — the core costing distributions table, supplying reference_account, transaction_value, base_transaction_value, accounting_line_type, resource_id, cost_element_id, rate_or_amount, and basis_type. The view text carries the hint INDEX(MTA MTL_TRANSACTION_ACCOUNTS_N1), confirming that the MTL_TRANSACTION_ACCOUNTS_N1 index is the intended access path for the accounting lines.
• CST_XLA_INV_HEADERS_V — the companion header view that provides the XLA event_id and the transaction action that drives the subinventory DECODE logic.
• Supporting objects — CSTPSCHK (package), GL_LEDGERS, MTL_PARAMETERS, and XLA_EVENTS_GT, which supply ledger currency, inventory organization parameters, and event context respectively.

Key Columns

• event_id — the XLA event identifier linking the line to its accounting event header.
• line_number — generated via ROW_NUMBER() partitioned by event_id, providing the sequential line ordering SLA requires.
• code_combination_id — derived from mta.reference_account, the account to which the distribution posts.
• entered_amount — NVL(mta.transaction_value, mta.base_transaction_value), the transaction-currency amount.
• accounted_amount — mta.base_transaction_value, the ledger-currency amount.
• accounting_line_type_code — from mta.accounting_line_type, distinguishing debit, credit, and related line roles.
• currency_code, currency_conversion_date, currency_conversion_rate, currency_conversion_type — resolved through DECODE logic that prefers transaction-level currency data, falling back to the ledger currency and to the material transaction's conversion attributes.
• material_overhead_id — mta.resource_id, identifying the resource that generated a material overhead charge.
• cost_element_id — the cost element classification of the distribution.
• inv_txn_basis_type — mta.basis_type, indicating the basis on which the amount was derived.
• subinventory_code — computed with DECODE on transaction_action_id (2, 5, 28, 55) and SIGN comparisons between the accounting line quantity and header quantity, to resolve the correct from/to subinventory for transfers.

Common Use Cases and Queries

The view is most often queried during period-close and costing reconciliation, where distributions must be traced from transactions to their XLA events and final journal entries. It is also useful for isolating lines that use a specific index access path or for auditing currency conversion behavior on inventory accounting lines.

SELECT event_id, line_number, code_combination_id,
       entered_amount, accounted_amount,
       accounting_line_type_code, currency_code
FROM   apps.cst_xla_inv_lines_v
WHERE  event_id = :event_id
ORDER  BY line_number;

To review material overhead and cost element detail for a period:

SELECT v.event_id, v.material_overhead_id, v.cost_element_id,
       v.subinventory_code, v.accounted_amount
FROM   apps.cst_xla_inv_lines_v v
WHERE  v.inv_txn_basis_type IS NOT NULL;

Because the view text pins MTL_TRANSACTION_ACCOUNTS_N1, query plans for these statements typically drive from XLA_EVENTS_GT through the accounting lines and then to the header view, making the view efficient for event-by-event extraction during Create Accounting runs.