Results for “cm_line_cur_code”

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

Overview

AR_CM_LINES_BASE_V is a public Oracle E-Business Suite view owned by the APPS schema and assigned to the Receivables (AR) product family. Its documented purpose is to serve as a credit memo line base extract. In practical terms, the view projects credit memo accounting line data into a flattened, subledger-facing structure that conforms to the column layout expected by Oracle Subledger Accounting (SLA) and the XLA extract framework. It is registered as a VALID object in both release 12.1.1 and 12.2.2, and it is not end-user facing in the sense of a data-entry form or a seeded concurrent program output; rather it acts as an internal interface view consumed by accounting extraction logic and by custom reporting that needs credit memo line level accounting detail.

The view is named with the _BASE_V suffix, consistent with the EBS convention for base extract views that feed SLA event processing. Because it is a view rather than a table, it holds no data of its own and returns rows only as permitted by the underlying source tables at query time.

Underlying Base Objects

The ETRM metadata for 12.2.2 documents four referenced base objects, all exposed through APPS synonyms:

• AR_XLA_LINES_EXTRACT — the core subledger accounting line extract table that stores event-level accounting attributes, including amounts, currency, exchange rate information, ledger, and posting entity.
• RA_CUST_TRX_LINE_GL_DIST_ALL — the Receivables distribution table that holds the GL distribution lines generated for transactions.
• RA_CUSTOMER_TRX_ALL — the transaction header table, used here primarily to obtain the invoice currency for gain/loss determination.
• AR_DISTRIBUTIONS_ALL — the AR distributions table referenced by the second branch of the UNION.

The view definition is a UNION of two SELECT statements. The first branch joins AR_XLA_LINES_EXTRACT to RA_CUST_TRX_LINE_GL_DIST_ALL and RA_CUSTOMER_TRX_ALL, filtering on POSTING_ENTITY = 'CTLGD' and event types CM_CREATE and CM_UPDATE. The second branch joins AR_XLA_LINES_EXTRACT to RA_CUSTOMER_TRX_ALL with POSTING_ENTITY = 'APP'. Both branches restrict the extract to line-level rows via LEVEL_FLAG = 'L'. Both branches are driven by an index hint on AR_XLA_LINES_EXTRACT_N1, and an INDEX(HE AR_XLA_LINES_EXTRACT_N1) hint appears inline, indicating the view is optimized for large extraction volumes.

Key Columns

The view publishes a uniform set of column aliases across both UNION branches, which is essential because the extract consumer expects one consistent shape. Notable columns include:

• EVENT_ID — the SLA event identifier, the primary key for the accounting event.
• LINE_ID — the accounting line identifier within the event.
• CM_LINE_CUR_CODE, CM_LINE_CUR_CONVERSION_TYPE, CM_LINE_CUR_CONVERSION_DATE, CM_LINE_CUR_CONVERSION_RATE — the currency, rate type, conversion date, and conversion rate applicable to the credit memo line.
• CM_LINE_ACCTD_AMT — the accounted amount, in the ledger currency.
• LINE_NUMBER, LANGUAGE, LEDGER_ID — the line sequence, language for message reporting, and target ledger.
• CM_DIST_TYPE — a literal discriminator, returning either RA_CUST_TRX_LINE_GL_DIST_ALL or AR_DISTRIBUTIONS_ALL depending on the UNION branch.
• CM_DIST_IDENTIFER — the distribution identifier (note the documented spelling), mapping to the source distribution record.
• GAIN_LOSS_AMT and GAIN_LOSS_SIGN — both returned as NULL in the documented text, indicating they are not populated by this extract definition.
• GAIN_LOSS_REF — populated only when the transaction invoice currency equals the base currency, using a DECODE over CT.INVOICE_CURRENCY_CODE.

Common Use Cases and Queries

Typical usage falls into three categories: SLA/subledger accounting reconciliation, custom credit memo accounting reporting, and data extraction for downstream warehouses or audit tools.

A straightforward query retrieving credit memo accounting lines in a given ledger and period:

SELECT event_id, line_id, line_number, ledger_id,
       cm_line_cur_code, cm_line_acctd_amt, cm_dist_type
FROM   apps.ar_cm_lines_base_v
WHERE  ledger_id = :ledger
ORDER BY event_id, line_number;

A second common pattern isolates the distribution source by branch, which is useful when reconciling against either the GL distribution table or the AR distributions table:

SELECT cm_dist_type, cm_dist_identifer, SUM(cm_line_acctd_amt)
FROM   apps.ar_cm_lines_base_v
GROUP BY cm_dist_type, cm_dist_identifer;

Because the view performs a UNION over potentially large extracts, queries should always filter on EVENT_ID, LEDGER_ID, or another leading column of AR_XLA_LINES_EXTRACT_N1 wherever possible. Avoid joining the view to itself or to wide tables without indexed predicates, since the inline hint cannot compensate for unbounded result sets.