Search Results ar_memo_lines_vl




Overview

AR_MEMO_LINES_VL is a seeded, VALID view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) product family and exposes the translated, multi-language representation of credit memo and debit memo lines. In Oracle EBS naming conventions, the "_VL" suffix denotes a view that joins a base ("_B") table with its translation ("_TL") table and applies multilingual and operating-unit security filtering. The view therefore presents memo line data in the session language of the querying user, with descriptive name and description fields resolved from the translation layer.

Because memo lines are the transactional detail underlying Receivables credit and debit memos, AR_MEMO_LINES_VL is a principal source for reporting on memo-based adjustments, revenue corrections and customer account activity. It is also a common target for inbound and outbound integrations that must read memo line attributes without querying the underlying base tables directly.

Underlying Base Objects

The view definition joins two base objects and references a security package:

  • AR_MEMO_LINES_B (synonym) — the base table holding the non-translatable, language-independent attributes of each memo line. It supplies MEMO_LINE_ID, the primary key, together with all descriptive flexfield, global descriptive flexfield, date, tax and pricing columns.
  • AR_MEMO_LINES_TL (synonym) — the translation table holding language-specific text, namely NAME and DESCRIPTION. The join is made on MEMO_LINE_ID and on NVL(ORG_ID, -99) for both tables, so that lines are matched with the correct operating unit context.
  • MO_GLOBAL (package) — the Multi-Org access control package. The view filters with MO_GLOBAL.CHECK_ACCESS(B.ORG_ID) = 'Y' so that only memo lines belonging to operating units the current user may access are returned. The translation is restricted by T.LANGUAGE = USERENV('LANG'), returning rows in the user's current session language.

Key Columns

The view exposes a ROW_ID (rowid of the base table row) plus the following significant columns:

Common Use Cases and Queries

Typical uses include extracting memo lines for tax reconciliation, reporting on credit memo activity by operating unit, and joining memo lines to their parent memo headers or to tax lines. Because the view already enforces both language and operating-unit access, it is the preferred reporting source over the raw _B and _TL tables.

A representative query retrieving memo lines for a specific operating unit in the current language:

  • SELECT memo_line_id, line_type, tax_code, tax_product_category, uom_code, unit_std_price, name, description FROM ar_memo_lines_vl WHERE org_id = :p_org_id;
  • SELECT m.memo_line_id, m.name, m.tax_product_category, m.unit_std_price FROM ar_memo_lines_vl m WHERE m.tax_product_category = :p_category AND m.set_of_books_id = :p_sob;
  • SELECT line_type, COUNT(*) FROM ar_memo_lines_vl GROUP BY line_type;

All such queries automatically inherit session-language translation and Multi-Org access restrictions imposed by MO_GLOBAL.CHECK_ACCESS, requiring no additional security predicate from the caller.