Results for “sales_order_source”

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

Overview

RA_CUST_TRX_LN_ALL_MRC_V is a multi-reporting-currency (MRC) view owned by the APPS schema in Oracle E-Business Suite Receivables. It exposes customer transaction line data across the reporting currencies enabled for a ledger, allowing reporting and integration logic to retrieve line-level amounts and attributes translated into a reporting currency rather than only the ledger's functional currency. The suffix _MRC_V indicates that the view is built on the Multiple Reporting Currencies architecture, in which a primary (functional-currency) row in RA_CUSTOMER_TRX_LINES_ALL is paired with one or more reporting-currency rows in RA_MC_CUSTOMER_TRX_LINES.

Because the view carries the full set of line attributes — including tax attributes, accounting flexfield references, interface line descriptive flexfield columns, and audit columns — it serves as a consolidated read model for MRC-aware inquiries, custom reports, and downstream interfaces that must reconcile transaction line amounts and descriptions in a reporting currency. In the context of the search term translated_description, the view supports multilingual reporting by exposing the translated description values associated with the underlying customer transaction line records.

Underlying Base Objects

The documented base objects referenced by RA_CUST_TRX_LN_ALL_MRC_V are:

• RA_CUSTOMER_TRX_LINES_ALL (SYNONYM) — the primary transaction lines table storing lines in the ledger's functional currency.
• RA_MC_CUSTOMER_TRX_LINES (SYNONYM) — the reporting-currency lines table holding the MRC-translated equivalents of each primary line.

In the view text, the primary table is aliased as PRIMARY, and its columns are selected directly. The join to RA_MC_CUSTOMER_TRX_LINES enables reporting-currency amounts and attributes to be presented alongside the functional-currency values. The view therefore behaves as a denormalized, MRC-enabled projection of the customer transaction lines, with ORG_ID and CUSTOMER_TRX_LINE_ID preserved for organization-level and line-level filtering.

Key Columns

The view exposes a broad set of line-level columns. Notable examples include:

• CUSTOMER_TRX_LINE_ID — primary key of the transaction line; the principal join key to other AR line objects.
• LINK_TO_CUST_TRX_LINE_ID and INITIAL_CUSTOMER_TRX_LINE_ID — lineage references used for credit memos, adjustments, and revenue linkage.
• EXTENDED_AMOUNT and REVENUE_AMOUNT — monetary line amounts subject to MRC translation.
• TAX_* columns (TAX_RATE, TAX_EXEMPT_FLAG, TAX_EXEMPT_NUMBER, TAX_EXEMPT_REASON_CODE, VAT_TAX_ID, SALES_TAX_ID, TAXABLE_FLAG) — tax determination and exemption attributes.
• UOM_CODE, MEMO_LINE_ID, MOVEMENT_ID, RULE_START_DATE, AUTORULE_* — inventory, memo line, and revenue scheduling attributes.
• ATTRIBUTE1–ATTRIBUTE15 and INTERFACE_LINE_ATTRIBUTE1–15 — descriptive and interface flexfield columns, including the context columns INTERFACE_LINE_CONTEXT and ITEM_CONTEXT.
• ORG_ID — operating unit identifier for multi-org security.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

For translated descriptions, the relevant descriptions are resolved through the underlying line rows and displayed according to the reporting language environment.

Common Use Cases and Queries

Typical uses include MRC-aware line reporting, reconciliation between functional and reporting currency, and extraction into custom interfaces. A basic query filtering by operating unit and line is:

• SELECT customer_trx_line_id, org_id, extended_amount, revenue_amount, taxable_flag
• FROM apps.ra_cust_trx_ln_all_mrc_v
• WHERE org_id = :p_org_id
• AND customer_trx_line_id = :p_line_id;

For translated descriptions, a join to the corresponding transaction header or descriptive flexfield translation table is commonly applied, using CUSTOMER_TRX_LINE_ID or the parent CUSTOMER_TRX_ID as the linking key. Because the view is MRC-specific, queries that do not require reporting-currency values may instead use RA_CUST_TRX_LINES_ALL directly for better performance.