Results for “entered_amount”

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

Overview

The view APPS.CST_XLA_AWO_LINES_V is a reporting and integration object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the APPS schema and shipped with a VALID status. It resides in the Bills of Material (BOM) product family, where it functions as a line-level extraction source for subledger accounting (XLA) events generated against accounting work orders (AWO). Its principal role is to expose the distribution-level monetary amounts, currency attributes, and ledger context associated with each accounting event, in a normalized format that downstream accounting, reconciliation, and reporting processes can consume directly. Because the view derives its content from a companion header view rather than raw base tables, it applies business filtering and line-numbering logic at query time, presenting a stable, pre-grained result set to the calling application or report.

Underlying Base Objects

According to the documented ETRM metadata for 12.2.2, the view references a single base object: CST_XLA_AWO_HEADERS_V, itself a view. The dependency is therefore a view-over-view construction, where the header view supplies the accounting event identifier, entered and accounted amounts, functional and entered currency details, conversion parameters, ledger identifier, and the corroborating distribution identifiers (PO distribution, inventory transaction, and invoice distribution). The view text is a UNION ALL of two branches. The first branch emits one row per header event with LINE_NUMBER equal to 1, carrying the header entered amount and a nested DECODE that resolves the appropriate accounted amount depending on which distribution identifiers are populated. The second branch emits LINE_NUMBER equal to 2 for header rows meeting the filter predicates WO_ERV_AMOUNT <> 0, INVOICE_DISTRIBUTION_ID IS NULL, PO_DISTRIBUTION_ID IS NOT NULL, and INVENTORY_TRANSACTION_ID IS NULL, contributing the work order encumbrance/receipt variance amount as a zero entered-amount line. This union yields a predictable two-line maximum structure for qualifying events.

Key Columns

• EVENT_ID — the subledger accounting event identifier; joins to XLA event tables and to the header view.
• LINE_NUMBER — synthetic line discriminator (1 or 2) distinguishing header-derived from variance-derived lines.
• ENTERED_AMOUNT — the transaction-currency amount; zero on line 2.
• ACCOUNTED_AMOUNT — the ledger-currency amount, resolved via nested DECODE logic based on distribution context.
• CURRENCY_CODE — the entered (header) currency code.
• CURRENCY_CONVERSION_DATE — the date used to convert entered to functional currency, propagated from the header view.
• CURRENCY_CONVERSION_RATE — the conversion rate, nulled via TO_NUMBER(NULL) when no entered currency exists or the entered currency equals the functional currency.
• CURRENCY_CONVERSION_TYPE — the rate type (for example, corporate or spot), similarly nulled for same-currency events.
• LEDGER_ID — the accounting ledger identifier for the event.

Common Use Cases and Queries

Typical use cases include subledger reconciliation of work order accruals and variances, currency conversion auditing, and feeds into custom XLA reporting. A common query filters by event and isolates the conversion metadata:

• SELECT event_id, line_number, entered_amount, accounted_amount, currency_code, currency_conversion_date, currency_conversion_rate, currency_conversion_type FROM cst_xla_awo_lines_v WHERE currency_conversion_date BETWEEN :start_date AND :end_date;
• SELECT event_id, SUM(accounted_amount) FROM cst_xla_awo_lines_v WHERE ledger_id = :ledger_id GROUP BY event_id;

Because the view is definition-only and carries no stored data, all filtering executes against the underlying header view at runtime; queries should therefore constrain EVENT_ID or date ranges to avoid full scans of the header source.