Results for “debit_memo”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.AR_AGREEMENTS_S_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 view that correlates Oracle Order Management agreements with Oracle Receivables Subledger Accounting (SLA) extract lines. The view supplies a consolidated listing of agreements alongside the XLA extract events, line numbers, and ledgers associated with each agreement. Its principal role in EBS reporting and integration is to expose agreement-to-XLA relationships that support upstream accounting, revenue, and receivables processing where Subledger Accounting events must be traced back to the originating agreement. Because it surfaces debit memo events among its event classes, the view is frequently referenced by users searching for "debit_memo" in the context of agreement-driven XLA extract diagnostics.

Underlying Base Objects

The view is defined with two referenced objects:

• AR_XLA_LINES_EXTRACT (SYNONYM) — the Receivables Subledger Accounting lines extract, aliased as L, which supplies event identifiers, line numbers, ledger identifiers, event class codes, and level/from-to flags.
• OE_AGREEMENTS_B (SYNONYM) — the Order Management agreements base table, aliased as ABF, which supplies the agreement identifier, agreement number, and agreement type code.

The join is expressed as abf.agreement_id = l.agreement_id, meaning the view returns a row for every agreement that has matching XLA extract lines. The view carries a hint, /*+INDEX (l ar_xla_lines_extract_n1)*/, directing the optimizer to use index AR_XLA_LINES_EXTRACT_N1 when accessing the extract table, which reflects the intended access path for high-volume queries.

Key Columns

• AGREEMENT_ID — Identifies the agreement from OE_AGREEMENTS_B; the join key to the XLA extract lines.
• AGREEMENT_NUM — The user-visible agreement number.
• AGREEMENT_TYPE_CODE — Classifies the agreement type.
• EVENT_ID — The Subledger Accounting event identifier for the extract line.
• LINE_NUMBER — The XLA extract line number.
• LEDGER_ID — The ledger under which the accounting event was recorded.

Common Use Cases and Queries

The view is used to reconcile agreements against their generated Subledger Accounting extract lines, to investigate debit memo events tied to agreements, and to support diagnostics of XLA extract processing for Receivables and Order Management flows. The WHERE clause applies a documented filter:

• Event classes INVOICE, DEBIT_MEMO, DEPOSIT, GUARANTEE, CHARGEBACK, ADJUSTMENT with LEVEL_FLAG = 'H' (header-level lines); or
• Event classes CREDIT_MEMO, RECEIPT with LEVEL_FLAG = 'L' and FROM_TO_FLAG = 'T'.

A representative query filtering for debit memo activity is:

SELECT agreement_id, agreement_num, agreement_type_code, event_id, line_number, ledger_id
FROM apps.ar_agreements_s_v
WHERE agreement_num = :agreement_num;

Because the DEBIT_MEMO event class is included in the header-level branch of the view predicate, filtering by agreement_id or agreement_num returns the associated debit memo XLA lines alongside the agreement metadata, providing a direct path from an Order Management agreement to its Receivables accounting events.