Results for “ar_agreements_s_vl”

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

Overview

AR_AGREEMENTS_S_VL is a shared Multi-Language Support (MLS) extraction view owned by the APPS schema within the Oracle Receivables (AR) product family. It exposes agreement-level descriptive information alongside transaction event identifiers drawn from the Subledger Accounting (XLA) lines extract, presenting a denormalized, reporting-friendly projection of Receivables agreement data joined to accounting event lines. The view is defined to supply the agreement name in the caller's session language while linking that agreement to specific event and line attributes, which makes it valuable for reconciliation, audit, and integration scenarios where Receivables activity must be traced back to a customer agreement.

Because the view is documented against both 12.1.1 and 12.2.2, it is used consistently across these releases. Its role is primarily as a read-only reporting and extraction layer; it is not a transaction entry object. The view carries an internal index hint on the AR_XLA_LINES_EXTRACT table, reflecting that it is optimized for querying large volumes of subledger accounting extract lines that have been restricted to the relevant agreement and event class combinations.

Underlying Base Objects

The view is defined over two referenced objects: AR_XLA_LINES_EXTRACT (accessed through a synonym) and OE_AGREEMENTS_TL (also accessed through a synonym), the latter aliased in the view text as SO_AGREEMENTS_TL. OE_AGREEMENTS_TL is the translated (MLS) agreements table, supplying the AGREEMENT_NAME and LANGUAGE columns, and is the source of the multilingual extraction behavior referenced in the object description. AR_XLA_LINES_EXTRACT supplies EVENT_ID, LINE_NUMBER, LEDGER_ID, AGREEMENT_ID, EVENT_CLASS_CODE, LEVEL_FLAG, and FROM_TO_FLAG. The join predicate is SOATLF.AGREEMENT_ID = L.AGREEMENT_ID.

The WHERE clause further restricts the result set. Header-level lines are included for the event classes INVOICE, DEBIT_MEMO, DEPOSIT, GUARANTEE, CHARGEBACK, and ADJUSTMENT where LEVEL_FLAG = 'H'. Line-level lines are included for CREDIT_MEMO and RECEIPT where LEVEL_FLAG = 'L' and FROM_TO_FLAG = 'T'. This construction scopes the view to economically meaningful agreement-linked events.

Key Columns

• AGREEMENT_NAME — The translated name of the agreement from OE_AGREEMENTS_TL, presented in the LANGUAGE of the returned row.
• EVENT_ID — Identifier of the subledger accounting event line in AR_XLA_LINES_EXTRACT, linking the agreement to its accounting representation.
• LINE_NUMBER — The line number within the source extract row, used to distinguish multiple lines within an event.
• LANGUAGE — The MLS language of the agreement name, supporting multilingual reporting environments.
• LEDGER_ID — The ledger associated with the event line, enabling ledger-level segmentation of agreement activity.

Common Use Cases and Queries

This view is commonly used to associate Receivables debit memo and other event activity with the underlying customer agreement, particularly during subledger accounting analysis and multilingual reporting. A representative query returning debit memo header events with their agreement names is:

• SELECT agreement_name, event_id, line_number, ledger_id FROM ar_agreements_s_vl WHERE event_id IN (SELECT event_id FROM ar_xla_lines_extract WHERE event_class_code = 'DEBIT_MEMO') ORDER BY agreement_name, event_id;
• SELECT agreement_name, language, COUNT(*) FROM ar_agreements_s_vl GROUP BY agreement_name, language ORDER BY agreement_name;
• SELECT a.agreement_name, a.ledger_id, a.event_id FROM ar_agreements_s_vl a WHERE a.language = USERENV('LANG');

Typical scenarios include audit reconciliation of debit memo and credit memo activity against agreements, building ledger-segmented extracts, and feeding downstream integration or data warehouse processes where agreement naming must respect the report language. Because the view applies fixed filtering logic by event class, level, and from/to flags, consumers should treat the result set as pre-scoped and query it directly rather than re-deriving the same restrictions.