Search Results ar_memo_lines_all_b_pk

Overview

AR_MEMO_LINES_ALL_B is a core Receivables table in Oracle E-Business Suite 12.1.1 and 12.2.2, owned by the AR schema. It stores the standard memo lines that back debit memos, on-account credits, debit memo reversals, and chargebacks. Whereas RA_CUSTOMER_TRX_LINES_ALL holds the operational transaction lines for every Receivables document, AR_MEMO_LINES_ALL_B persists the reusable memo-line definition that those transaction lines can point to through the MEMO_LINE_ID column. The table therefore acts as a repository of standard, pre-defined memo content that receivable transactions consume rather than redefine on each occurrence.

The table carries 56 columns and is multi-organization enabled through ORG_ID, with the unique index AR_MEMO_LINES_ALL_B_U1 spanning MEMO_LINE_ID, ORG_ID, and ZD_EDITION_NAME. From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning: the surgical business key is MEMO_LINE_ID, while descriptive attributes such as LINE_TYPE, SET_OF_BOOKS_ID, taxing data, and rule references behave as dependent satellite attributes rather than as an independent hub. This classification is a modeling suggestion derived from the foreign-key topology, not a physically enforced construct.

Key Information Stored

The surrogate primary key is MEMO_LINE_ID, defined by constraint AR_MEMO_LINES_ALL_B_PK. The unique index AR_MEMO_LINES_ALL_B_U1(MEMO_LINE_ID, ORG_ID, ZD_EDITION_NAME) demonstrates the business-key candidate in a multi-org and multi-edition environment, ensuring a memo line is unique per operating unit and edition.

• MEMO_LINE_ID — surrogate identifier and the join key consumed by downstream transaction and interface tables.
• ORG_ID — operating unit that owns the memo line; central to multi-org security and reporting.
• SET_OF_BOOKS_ID — foreign key to GL_SETS_OF_BOOKS_11I, tying the memo line to a ledger.
• LINE_TYPE — classifies the memo line as debit memo, on-account credit, debit memo reversal, or chargeback.
• INVOICING_RULE_ID and ACCOUNTING_RULE_ID — foreign keys to RA_RULES controlling invoicing and revenue recognition behavior.
• START_DATE and END_DATE — effective-dating window governing when the memo line is usable.
• UNIT_STD_PRICE, UOM_CODE, and TAX_CODE — pricing, unit of measure, and tax determinants for the line.
• GL_ID_REV — reversal/GL identifier linkage.
• TAX_PRODUCT_CATEGORY — E-Business Tax product category used in tax determination.
• ATTRIBUTE1–ATTRIBUTE15 and GLOBAL_ATTRIBUTE1–GLOBAL_ATTRIBUTE20 — descriptive flexfield and global descriptive flexfield segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ZD_EDITION_NAME — editioning support associated with 12.2 online patching.

Common Use Cases and Queries

Typical usage centers on resolving memo-line detail for a transaction line, validating effective-dated memo definitions per ledger, and feeding interface processing. A representative join resolving transaction lines to their memo definition:

• SELECT m.memo_line_id, m.line_type, m.set_of_books_id, m.start_date, m.end_date FROM ar.ar_memo_lines_all_b m WHERE m.org_id = :org_id AND m.line_type = :line_type;
• Join to consumers: SELECT t.customer_trx_line_id, t.memo_line_id, m.line_type, m.unit_std_price FROM ra_customer_trx_lines_all t, ar_memo_lines_all_b m WHERE t.memo_line_id = m.memo_line_id;
• Effective-date validity check: ... WHERE TRUNC(SYSDATE) BETWEEN m.start_date AND NVL(m.end_date, TRUNC(SYSDATE));
• Reporting by rule reference: aggregate memo lines grouped by invoicing_rule_id or accounting_rule_id joined to RA_RULES.

Reporting use cases include memo-line inventory by operating unit and ledger, aging-style analysis of expired versus active memo definitions, and reconciliation of interface rejects referencing MEMO_LINE_ID.

Related Objects

The most significant related objects, based on documented foreign-key relationships, are:

• RA_CUSTOMER_TRX_LINES_ALL — references AR_MEMO_LINES_ALL_B.MEMO_LINE_ID; the operational transaction line that consumes the memo definition.
• RA_INTERFACE_LINES_ALL — AutoInvoice interface lines carrying MEMO_LINE_ID into Receivables.
• GL_SETS_OF_BOOKS_11I — parent via SET_OF_BOOKS_ID.
• RA_RULES — parent via INVOICING_RULE_ID and ACCOUNTING_RULE_ID.
• AR_TRX_LINES_GT and AR_TRX_LINES_TMP_GT — transaction-line staging tables referencing MEMO_LINE_ID.
• AR_RDR_PARAMETERS_GT, FUN_TRX_TYPE_AR_MAPS, JG_ZZ_AR_TMP_ACCOUNT, and PON_EMD_FIN_PARAMETERS_ALL — additional dependent objects sharing the MEMO_LINE_ID foreign key.

These relationships confirm the table's role as a reference or satellite-style repository whose key is propagated outward to transaction, interface, and auxiliary processing structures throughout Receivables and adjacent modules.