Search Results cst_xla_awo_headers_v




Overview

CST_XLA_AWO_HEADERS_V is an APPS-owned view in Oracle E-Business Suite that exposes Work in Process write-off accounting header information in the Subledger Accounting (XLA) event format. It belongs primarily to the BOM – Bills of Material product family and is used within the Cost Management write-off flow, where manufacturing and inventory write-off transactions are accounted through Subledger Accounting and ultimately transferred to General Ledger. The view's central purpose is to present one row per accounting event header, joining the write-off record to its corresponding XLA event so that downstream accounting, transfer-to-GL, and reporting processes can consume consistent event-level data. It surfaces critical monetary and currency attributes — most notably the value exposed as H_CURRENCY_CODE (mapped from CWO.CURRENCY_CODE) — alongside conversion date, rate, and type, enabling multi-currency write-off accounting.

Underlying Base Objects

The view is defined over the following documented base objects in the APPS schema:

The join logic links CWO.WRITE_OFF_ID to XEG.SOURCE_ID_INT_1, GL.LEDGER_ID to XEG.LEDGER_ID, and FC.CURRENCY_CODE to GL.CURRENCY_CODE. The view therefore sits at the intersection of cost write-off data and the Subledger Accounting event model.

Key Columns

Common Use Cases and Queries

Typical uses include auditing write-off accounting entries, reconciling entered versus accounted amounts across currencies, and feeding custom Subledger Accounting reports. A representative query filtering by the currency column follows:

  • List write-offs in a given currency with amounts and ledger context.
SELECT event_id,
       write_off_id,
       h_currency_code,
       h_entered_amount,
       h_accounted_amount,
       h_ledger_id,
       transaction_date
FROM   apps.cst_xla_awo_headers_v
WHERE  h_currency_code = 'USD';
  • Ideal for currency-conversion reconciliation, using the conversion rate and type columns joined to the functional currency.
  • Useful for extracting XLA event headers for a specific item or vendor when reconciling manufacturing write-offs against GL balances.

Because the view depends on XLA_EVENTS_GT, queries should run in a context where the XLA event population is active, ensuring the temporary event data is available for the join.