Search Results ar_memo_lines_tl




Overview
Explore in AI Chat

Overview

APPS.AR_MEMO_LINES_VL is a language-specific (MLS) validation view in Oracle Receivables that presents translated receivables memo line information. Memo lines in Oracle EBS correspond to the line-level detail of credit memos, debit memos, and on-account credit transactions generated through AutoInvoice or manual entry. The view exists primarily to support Oracle Forms, concurrent programs, and integration code that need to retrieve memo line data together with its translated Name and Description in the session language, rather than accessing the underlying _B and _TL tables separately.

The "_VL" suffix indicates a "view language" join: it combines the descriptive columns of the base (_B) table with the translation (_TL) table, restricting output to the current user's language via userenv('LANG'). Because it exposes the ROWID of the base table, the view is updatable for Forms-based maintenance. It also enforces Multi-Org access through mo_global.check_access.

Underlying Base Objects

The view is defined over three documented base objects:

The join condition is B.MEMO_LINE_ID = T.MEMO_LINE_ID, with an ORG_ID match (NVL to -99 to accommodate lines without an operating unit) and a language filter T.LANGUAGE = userenv('LANG'). Access is restricted by mo_global.check_access(B.ORG_ID) = 'Y'.

Key Columns

  • ROW_ID — ROWID of AR_MEMO_LINES_B, enabling positional updates.
  • MEMO_LINE_ID — primary key identifying the memo line.
  • NAME / DESCRIPTION — translated attributes from AR_MEMO_LINES_TL, retrieved in the session language.
  • LINE_TYPE — classification of the memo line (for example, LINE, TAX, FREIGHT, or CHARGES).
  • START_DATE / END_DATE — effective dates governing when the line applies.
  • GL_ID_REV — revenue account generator reference associated with the line.
  • TAX_CODE, TAX_PRODUCT_CATEGORY — tax-related attributes used during tax calculation and reporting.
  • UOM_CODE, UNIT_STD_PRICE — unit of measure and standard price for the memo line.
  • INVOICING_RULE_ID, ACCOUNTING_RULE_ID — rule references for revenue scheduling and invoicing.
  • SET_OF_BOOKS_ID, ORG_ID — ledger and operating unit context; ORG_ID participates in Multi-Org access checks.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–15, GLOBAL_ATTRIBUTE_CATEGORY, GLOBAL_ATTRIBUTE1–20 — descriptive flexfield and global descriptive flexfield columns.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Developers and reporting analysts commonly query this view when a business requirement references the historical table name ar_memo_lines_tl but the intended result set is the translated, Multi-Org-secured view. Typical scenarios include printing memo line descriptions on customer-facing documents, exporting memo line detail for reconciliation, and validating tax and revenue rule assignments on memo lines.

Sample query retrieving translated memo line detail:

  • SELECT memo_line_id, name, description, line_type, unit_std_price, tax_code FROM apps.ar_memo_lines_vl WHERE org_id = :p_org_id ORDER BY memo_line_id;

Sample join to header information for reporting:

  • SELECT ml.memo_line_id, ml.name, ml.description, ml.start_date, ml.end_date FROM apps.ar_memo_lines_vl ml WHERE ml.set_of_books_id = :p_sob_id AND NVL(ml.org_id,-99) = NVL(:p_org_id,-99);

Because the view applies mo_global.check_access and the session language filter, callers should initialize the MO security context (via mo_global.init or FND_GLOBAL) and ensure the user's language has a corresponding translation row before relying on NAME and DESCRIPTION values. Where no translation exists, the base description is not returned; integration code should therefore treat NAME and DESCRIPTION as nullable.