Search Results ar_memo_lines_all_vl




Overview
Explore in AI Chat

Overview

AR_MEMO_LINES_ALL_VL is a multilingual (ML) validation view in the Oracle E-Business Suite Receivables (AR) module, owned by the APPS schema. It exposes memo line records — the reusable line definitions used in credit memos, debit memos, and other Receivables memo transactions — joined with their translated name and description. In releases 12.1.1 and 12.2.2, this object is a core reference view for reporting, integration, and localization-aware queries. The "_VL" suffix denotes a bilingual view that combines the underlying transactional base table with its translation table, filtering translations to the session language via USERENV('LANG'). Because memo lines carry pricing and tax attributes such as UNIT_STD_PRICE, the view is frequently queried in pricing, tax, and intercompany reporting contexts, and it is a documented target when the search term is unit_std_price, since that column is exposed directly here.

Underlying Base Objects

The view is defined over two base objects, both referenced through APPS synonyms:

  • AR_MEMO_LINES_ALL_B — the transactional base table holding language-independent memo line attributes (alias B).
  • AR_MEMO_LINES_ALL_TL — the translation table holding NAME and DESCRIPTION per language (alias T).

The join predicate links records on MEMO_LINE_ID and on a null-safe ORG_ID comparison: NVL(B.ORG_ID, -99) = NVL(T.ORG_ID, -99), and restricts translations to T.LANGUAGE = USERENV('LANG'). This design ensures each memo line returns exactly one translated row matching the current session language, keeping multi-org and multilingual behavior consistent. The view is reported as VALID under the AR product in ETRM metadata.

Key Columns

  • MEMO_LINE_ID — primary key linking the base and translation records.
  • UNIT_STD_PRICE — the unit standard price assigned to the memo line, central to pricing and valuation reporting.
  • LINE_TYPE — classification of the memo line (for example, charges, freight, or tax lines).
  • TAX_CODE / UOM_CODE — tax classification and unit of measure for the line.
  • START_DATE / END_DATE — effective date range controlling when the line definition is active.
  • INVOICING_RULE_ID / ACCOUNTING_RULE_ID — references to billing and revenue recognition rules.
  • ORG_ID / SET_OF_BOOKS_ID — multi-org and ledger context for the record.
  • NAME / DESCRIPTION — translated descriptive fields sourced from the TL table.
  • ATTRIBUTE1–15 and GLOBAL_ATTRIBUTE1–20 — descriptive flexfield segments available for reporting extensions.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and ROW_ID.

Common Use Cases and Queries

Typical scenarios include extracting active memo line prices for a given ledger, validating translated names for localization, and joining memo lines to invoice or memo transactions for pricing reconciliation. The following example retrieves active lines with their standard price for the session's language:

SELECT m.memo_line_id,
       m.name,
       m.line_type,
       m.unit_std_price,
       m.uom_code,
       m.tax_code
FROM   apps.ar_memo_lines_all_vl m
WHERE  m.org_id = :org_id
AND    SYSDATE BETWEEN m.start_date AND NVL(m.end_date, SYSDATE)
ORDER BY m.name;

A second query localized to a specific reporting context narrows by set of books and returns pricing detail alongside the translated description, which is useful for audit and tax reporting packs. In all cases, queries should filter by ORG_ID and effective dates to avoid ambiguous results across operating units.