Results for “agreement_type_code”

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

Overview

The APPS.AR_AGREEMENTS_S_V view is a shared extraction object within the Oracle E-Business Suite Receivables (AR) module. Its documented description, "agreement shared extract," indicates that it serves as a denormalized reporting and integration surface that joins agreement header information to Subledger Accounting (XLA) line extract data. The view is registered as VALID in the APPS schema and is available in both EBS 12.1.1 and 12.2.2. In practice it is used to correlate Receivables agreements with the accounting events and lines generated against them, supporting reconciliation, extract feeds, and diagnostic queries. Because it is a view rather than a table, it carries no storage of its own and always reflects the current state of its underlying base objects.

Underlying Base Objects

The documented view text defines AR_AGREEMENTS_S_V over two base objects, both accessed through synonyms owned by APPS:

• OE_AGREEMENTS_B (SYNONYM) — aliased as ABF in the view text. This is the Order Management agreements base table, supplying the agreement identifier, agreement number, and agreement type code.
• AR_XLA_LINES_EXTRACT (SYNONYM) — aliased as L. This is the Receivables Subledger Accounting lines extract, providing the accounting event, line number, and ledger context.

The two objects are joined on ABF.AGREEMENT_ID = L.AGREEMENT_ID. The view text carries an explicit optimizer hint, /*+INDEX (L AR_XLA_LINES_EXTRACT_N1)*/, directing the cost-based optimizer to use the AR_XLA_LINES_EXTRACT_N1 index on the extract table. The WHERE clause restricts rows to specific event class and level combinations: for EVENT_CLASS_CODE values INVOICE, DEBIT_MEMO, DEPOSIT, GUARANTEE, CHARGEBACK, and ADJUSTMENT, only header-level rows (LEVEL_FLAG = 'H') qualify; for CREDIT_MEMO and RECEIPT, only line-level rows (LEVEL_FLAG = 'L') with FROM_TO_FLAG = 'T' qualify. This filtering is central to the view's purpose, as it determines which accounting lines are surfaced alongside each agreement.

Key Columns

The view exposes six columns:

• AGREEMENT_ID — The unique identifier of the agreement, sourced from OE_AGREEMENTS_B. It is the join key to the XLA extract and the primary correlation column.
• AGREEMENT_NUM — The user-visible agreement number. This is the column most frequently used in searches and report filters; users searching for "agreement_num" are typically looking up this value against related accounting activity.
• AGREEMENT_TYPE_CODE — The code classifying the agreement type, drawn from the agreements base table.
• EVENT_ID — The Subledger Accounting event identifier from AR_XLA_LINES_EXTRACT, linking the agreement to its accounting event.
• LINE_NUMBER — The XLA line number within the event, providing line-level granularity for the returned accounting rows.
• LEDGER_ID — The ledger identifier associated with the extract line, enabling multi-ledger reporting and ledger-specific filtering.

Common Use Cases and Queries

The view is most commonly used to retrieve the accounting events and lines tied to a specific agreement, or to list all agreements that have generated qualifying accounting activity. A typical lookup by agreement number is:

• SELECT agreement_id, agreement_num, agreement_type_code, event_id, line_number, ledger_id FROM apps.ar_agreements_s_v WHERE agreement_num = :p_agreement_num;
• Joining to AR_XLA_LINES_EXTRACT or XLA_EVENTS for additional event detail, using EVENT_ID as the link.
• Filtering by LEDGER_ID to isolate activity for a single ledger in multi-ledger or reporting-curiosity scenarios.
• Feeding downstream extract or reconciliation processes that require agreement-to-accounting correlation without querying the base tables directly.

Because the view applies level-flag and event-class filtering internally, consumers should treat the row set as already scoped to the relevant header and line records described above, rather than as a complete accounting picture. Joins back to the base objects should preserve the AGREEMENT_ID and EVENT_ID keys to avoid row multiplication.