Search Results ar_memo_lines_all_tl




Overview
Explore in AI Chat

Overview

AR_MEMO_LINES_ALL_TL is a table in the Oracle Receivables (AR) schema that provides multilingual support (MLS) for standard memo lines. In Oracle EBS 12.1.1 and 12.2.2, memo lines represent reusable, pre-defined annotations or remarks that can be attached automatically to transactions such as invoices, credit memos, debit memos, and deposits. Because Receivables must support global deployments with multiple operating languages, the translatable attributes of these memo lines are stored in this MLS table rather than the base table.

The object is documented as valid in the ETRM repository with owner AR and a physical schema of twelve columns. From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. It is therefore best modelled as an independent satellite-like structure keyed by memo line, language, and operating unit, without documented link dependencies to other hubs. This classification is a modeling suggestion only, derived from the documented key structure.

Key Information Stored

The table stores the translated text and the language context for each memo line. The most significant columns documented in the ETRM metadata are:

  • MEMO_LINE_ID — The surrogate identifier of the memo line; it is the primary business identifier of the parent entity and forms part of the primary key.
  • LANGUAGE — The language code for the translated row; part of the primary key and the driver of MLS behaviour.
  • ORG_ID — The operating unit identifier, included in the primary key to support multi-org partitioning (originally used by Multi-Org, retained for Multi-Org Access Control in Release 12).
  • NAME — The translated short name of the memo line; a documented business-key candidate via unique index AR_MEMO_LINES_ALL_TL_U2.
  • DESCRIPTION — The translated long description or text of the memo line.
  • SOURCE_LANG — The language of the source (base) row from which translations were derived.
  • ZD_EDITION_NAME — The edition name column associated with the editioning/online patching model introduced in EBS 12.2; it appears in both unique indexes, so uniqueness is scoped by edition.
  • Audit columns — LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard WHO audit tracking.

The documented primary key is AR_MEMO_LINES_ALL_TL_UK on (MEMO_LINE_ID, LANGUAGE, ORG_ID). This distinguishes the surrogate identity of the row from the business-key candidates captured by unique indexes AR_MEMO_LINES_ALL_TL_U1 (MEMO_LINE_ID, LANGUAGE, ORG_ID, ZD_EDITION_NAME) and AR_MEMO_LINES_ALL_TL_U2 (NAME, ORG_ID, LANGUAGE, ZD_EDITION_NAME), the latter enforcing uniqueness of the translated name within an operating unit and language.

Common Use Cases and Queries

Typical scenarios include listing available memo lines in the user's session language, reporting on translated memo text for statutory documents, and verifying that translations exist for every supported language.

  • Retrieve memo lines in a specific language: SELECT memo_line_id, name, description FROM ar_memo_lines_all_tl WHERE language = USERENV('LANG') AND org_id = :p_org_id;
  • Join to the base table: SELECT b.memo_line_id, t.name, t.description FROM ar_memo_lines_all_b b, ar_memo_lines_all_tl t WHERE b.memo_line_id = t.memo_line_id AND b.org_id = t.org_id AND t.language = USERENV('LANG');
  • Detect missing translations: compare the language set in FND_LANGUAGES against rows in this table for each memo_line_id and org_id.
  • Reporting: embed translated memo text on printed invoices or statements by joining on memo_line_id and org_id, filtering to the printing language rather than the session language.

Because this is an MLS table, queries should always constrain LANGUAGE to avoid returning duplicate-looking rows for the same memo line.

Related Objects

The following objects are most significant when working with AR_MEMO_LINES_ALL_TL:

  • AR_MEMO_LINES_ALL_B — the base (non-translatable) table; joined on MEMO_LINE_ID and ORG_ID to obtain non-translated attributes.
  • AR_MEMO_LINES_ALL_VL — the MLS view that automatically joins the _B and _TL tables, typically the preferred query object.
  • FND_LANGUAGES — the installed-language repository; used to validate the LANGUAGE value.
  • AR_MEMO_LINES_ALL — the legacy pre-MLS synonym/view retained for backward compatibility in older code paths.
  • RA_CUSTOMER_TRX_LINES_ALL and RA_CUSTOMER_TRX_LINES — transaction lines that can reference memo lines, linking MEMO_LINE_ID where memo text is applied to a transaction.
  • AR_STANDARD_TEXT / AR_MEMO_LINES_TL patterns and the Receivables AutoInvoice interfaces, which accept memo line identifiers during transaction import.

These relationships are driven by the documented key columns MEMO_LINE_ID, ORG_ID, and LANGUAGE, ensuring consistent multi-org, multilingual retrieval across the Receivables application stack.