Search Results wo_offset_account_id

Overview

APPS.CST_XLA_AWO_HEADERS_V is an internal Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as BOM.CST_XLA_AWO_HEADERS_V. Its status is VALID. The view exposes header-level detail for Accounting Write-Off (AWO) events routed through the Subledger Accounting (XLA) engine, combining write-off records with event, currency, and ledger context required for accounting and transfer to General Ledger. In EBS 12.1.1 and 12.2.2, the view functions as a read-only reporting and integration surface beneath the standard Accounting Write-Off and SLA processes. Oracle marks the object as Oracle Internal Use Only and explicitly does not support direct access except from standard Oracle Applications programs. Consequently, it should be treated as a diagnostic and reporting aid rather than a supported extension point, and any query against it should be confined to read-only investigation.

Underlying Base Objects

The view is defined over the following documented base objects:

• CST_WRITE_OFFS (SYNONYM) — the primary source of write-off header rows, supplying identifiers such as WRITE_OFF_ID and related write-off amounts.
• XLA_EVENTS_GT (SYNONYM) — the Subledger Accounting events global temporary table supplying EVENT_ID and event-level linkage.
• GL_LEDGERS (SYNONYM) — the ledger definition source that resolves H_LEDGER_ID to a ledger for the header's primary accounting context.
• FND_CURRENCIES (SYNONYM) — the currency validation source used to describe the header currency (H_CURRENCY_CODE) and functional currency (FUNC_CURRENCY_CODE).

Because XLA_EVENTS_GT is a global temporary table, the event-related columns are only populated in the context of an active SLA process or session; the persistent write-off and ledger attributes derive from CST_WRITE_OFFS, GL_LEDGERS, and FND_CURRENCIES. The join pattern therefore ties each write-off to its XLA event, its ledger, and its currency definitions.

Key Columns

• EVENT_ID — identifier of the Subledger Accounting event associated with the write-off header.
• WRITE_OFF_ID — unique identifier of the accounting write-off record.
• TRANSACTION_DATE — accounting date of the write-off transaction.
• WO_TRANSACTION_TYPE_CODE — classification of the write-off transaction type.
• H_LEDGER_ID — the ledger identifier (joined to GL_LEDGERS) for the header's primary accounting context; this is the column most commonly searched by users.
• H_CURRENCY_CODE, H_CURRENCY_CONVERSION_DATE, H_CURRENCY_CONVERSION_RATE, H_CURRENCY_CONVERSION_TYPE — the header (entered) currency and its conversion attributes.
• H_ENTERED_AMOUNT and H_ACCOUNTED_AMOUNT — respectively the entered and accounted amounts of the header.
• WO_ERV_AMOUNT, TOTAL_ACCRUAL_AMOUNT — exchange rate variance and total accrual amounts.
• PO_DISTRIBUTION_ID, INVOICE_DISTRIBUTION_ID, INVENTORY_TRANSACTION_ID — linkage to purchasing, payables, and inventory transactions.
• WO_OFFSET_ACCOUNT_ID, WO_ACCRUAL_ACCOUNT_ID, WO_ERV_ACCOUNT_ID — account identifiers used by the write-off accounting entries.
• TRANSFER_TO_GL_INDICATOR — flag indicating whether the associated entry is transferred to General Ledger.
• OPERATING_UNIT_ID, INVENTORY_ITEM_ID, VENDOR_ID, DESTINATION_TYPE_CODE, DISTRIBUTION_TYPE — organizational and item/vendor context.

Common Use Cases and Queries

The view is typically used to reconcile Accounting Write-Off events with their ledger, currency, and account assignments, and to investigate why an expected write-off entry did or did not reach General Ledger. A frequent starting point is filtering by ledger, as in the following example:

• Locate headers for a specific ledger and date range: SELECT event_id, write_off_id, transaction_date, wo_transaction_type_code, h_ledger_id, h_currency_code, h_entered_amount, h_accounted_amount FROM apps.cst_xla_awo_headers_v WHERE h_ledger_id = :p_ledger_id AND transaction_date BETWEEN :p_from AND :p_to;
• Identify entries awaiting transfer to GL: filter on TRANSFER_TO_GL_INDICATOR and inspect the associated accounts.
• Trace an event back to its source transaction using PO_DISTRIBUTION_ID, INVOICE_DISTRIBUTION_ID, or INVENTORY_TRANSACTION_ID.
• Audit currency conversion behavior by reviewing the H_CURRENCY_* and FUNC_CURRENCY_* column families.

Given the internal-use designation, queries should be strictly read-only and used for reporting or diagnosis rather than as a dependency in custom code.