Search Results extended_acctd_amount

Overview

The ARBPA_CUSTOMER_TRX_LINE view is an Oracle E-Business Suite database object owned by the APPS schema and registered under the FND – Application Object Library product. It presents a denormalized, reporting-oriented projection of accounts receivable transaction lines, combining columns from the RA_CUSTOMER_TRX_LINES and RA_CUSTOMER_TRX base entities together with supporting lookups for items, units of measure, inventory organizations, and tax lines. Its role is to consolidate the attributes most frequently required for invoice, debit memo, credit memo, and on-account line analysis into a single relational source, removing the need for consumers to repeatedly join the transaction header to its lines and auxiliary lookup tables.

The view is commonly used in Oracle Business Process Analysis or receivables reporting contexts, and in integration scenarios where external systems require a flattened representation of transaction line data. Because it references package-backed logic (AR_BPA_UTILS_PKG and AR_INVOICE_SQL_FUNC_PUB) and the FND_CURRENCY package, it may also return derived or formatted currency values in addition to raw stored columns. Notably, the view exposes a TRANSACTION_CURRENCY_CODE-type column, which is the element most frequently searched by developers attempting to determine the currency of a transaction line.

Underlying Base Objects

The documented base objects for this view are:

• RA_CUSTOMER_TRX (synonym) — the transaction header, supplying TRX_NUMBER, SET_OF_BOOKS_ID, transaction currency, and header-level attributes.
• RA_CUSTOMER_TRX_LINES (synonym) — the transaction line, supplying line number, line type, description, quantity, unit price, amounts, tax flags, and descriptive flexfield columns.
• ZX_LINES (synonym) — the E-Business Tax line repository, supplying tax rate, tax code, and printed tax name data.
• MTL_SYSTEM_ITEMS_KFV, MTL_UNITS_OF_MEASURE, and MTL_PARAMETERS (synonyms) — inventory item, unit of measure, and organization lookups.
• FND_CURRENCY (package) — currency formatting and validation logic.
• AR_BPA_UTILS_PKG and AR_INVOICE_SQL_FUNC_PUB (packages) — utility and invoice query functions used to derive computed values.

The view is not a table and cannot be updated directly; it exists to project the joined result set of these objects.

Key Columns

Columns exposed by the view include:

• CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID, LINE_NUMBER, TRANSACTION_LINE_NUM — identity and ordering keys for the header and line.
• LINE_TYPE, DESCRIPTION, QUANTITY, UNIT_OF_MEASURE_NAME, UOM_CODE, UNIT_PRICE, UNFORMATTED_UNIT_PRICE, EXTENDED_AMOUNT — commercial line detail.
• TRX_NUMBER, SALES_ORDER, SALES_ORDER_LINE, SALES_ORDER_DATE, SALES_ORDER_SOURCE — transaction and order references.
• SET_OF_BOOKS_ID, ORG_ID — ledger and operating unit context; ORG_ID is essential for Multi-Org filtering.
• TAX_EXISTS_FOR_THIS_LINE_FLAG, LINE_TAX_RATE, TAX_CODE, PRINTED_TAX_NAME, TAX_EXEMPT_FLAG, TAX_EXEMPT_NUMBER, TAX_EXEMPT_REASON_CODE, TAX_VENDOR_RETURN_CODE — tax determination and exemption data.
• INTERFACE_LINE_ATTRIBUTE1..15, INTERFACE_LINE_CONTEXT, ATTRIBUTE1..15, ATTRIBUTE_CATEGORY, and GLOBAL_ATTRIBUTE1..20, GLOBAL_ATTRIBUTE_CATEGORY — descriptive and global flexfield columns.
• REVENUE_AMOUNT, ACCOUNTING_RULE_DURATION, RULE_START_DATE, LAST_PERIOD_TO_CREDIT — revenue recognition attributes.
• EXTENDED_ACCTD_AMOUNT, MRC_EXTENDED_ACCTD_AMOUNT — accounted amounts for reporting currencies.
• DEFAULT_USSGL_TRANSACTION_CODE, DEFAULT_USSGL_TRX_CODE_CONTEXT — USSGL transaction code mapping.

The transaction currency of each line is derived from RA_CUSTOMER_TRX and surfaced through the FND_CURRENCY logic; queries searching for TRANSACTION_CURRENCY_CODE should join back to RA_CUSTOMER_TRX or rely on the formatted currency column provided by the view.

Common Use Cases and Queries

Typical scenarios include receivables line reporting, tax reconciliation, revenue recognition analysis, and data extraction for downstream ledgers. The view is frequently queried with a period or ledger predicate.

Sample SQL for transaction line currency and amount analysis:

• SELECT l.trx_number, l.line_number, l.line_type, l.unit_price, l.extended_amount FROM arbpa_customer_trx_line l WHERE l.org_id = :org_id AND l.trx_number = :trx_number ORDER BY l.line_number;
• SELECT t.transaction_currency_code, SUM(l.extended_amount) FROM arbpa_customer_trx_line l, ra_customer_trx t WHERE l.customer_trx_id = t.customer_trx_id AND l.org_id = :org_id GROUP BY t.transaction_currency_code;
• SELECT l.trx_number, l.line_number, l.tax_code, l.line_tax_rate, l.tax_exempt_flag FROM arbpa_customer_trx_line l WHERE l.tax_exists_for_this_line_flag = 'Y';

Because the view joins inventory and tax tables, queries should always be constrained by ORG_ID and, where possible, by transaction identifiers to avoid unnecessary full scans.