Results for “oe_agreements_115_vl”

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

Overview

OE_AGREEMENTS_115_VL is a compatibility view owned by the APPS schema in Oracle E-Business Suite, residing in the Advanced Pricing (QP) product family. It exposes pricing agreement information and is retained specifically to provide backward compatibility for other applications that referenced the legacy 11.5 agreements interface. Rather than representing a current, actively maintained data model, the view presents a stable, fixed-shape projection of agreement header data so that dependent code and integrations written against earlier releases continue to function after upgrade to 12.1.1 or 12.2.2.

The _VL suffix indicates that the underlying object is a translated (multi-language) view, meaning name and description columns may be resolved against the session language. For reporting and integration purposes, OE_AGREEMENTS_115_VL behaves as a read-only interface to agreement headers, and it should not be treated as a target for DML.

Underlying Base Objects

The view is defined over a single documented base object: OE_AGREEMENTS_VL. The body of the view selects directly from that view, aliased as B, and passes through its columns. Several columns are surfaced only as positional placeholders — that is, the select list contains NULL literals with inline comments rather than references to base columns. Notably, REVISION, REVISION_DATE, REVISION_REASON_CODE, FREIGHT_TERMS_CODE, SHIP_METHOD_CODE, and COMMENTS are all emitted as NULL. This is the defining characteristic of the view: it preserves the legacy column footprint while deliberately not populating attributes that the current base object no longer maintains in the same form.

Because the view references a _VL object, it inherits translation behavior from that layer. There is no documented join to additional tables in the ETRM metadata; the projection is flat and depends entirely on OE_AGREEMENTS_VL.

Key Columns

• ROW_ID — The row identifier from the base view, typically used for row-level addressing.
• AGREEMENT_ID — Primary key of the pricing agreement header; the principal join key to agreement lines and related entities.
• AGREEMENT_NUM — User-visible agreement number.
• AGREEMENT_TYPE_CODE — Classifies the agreement (for example, pricing or sales agreement types).
• PRICE_LIST_ID / TERM_ID — References to the associated price list and payment term.
• REVISION, REVISION_DATE, REVISION_REASON_CODE — Exposed for footprint compatibility but returned as NULL. This is the column most relevant to the search term revision_reason_code; queries filtering or reporting on this column will always return no values through this view.
• CUSTOMER_ID, INVOICE_TO_SITE_USE_ID, SALESREP_ID — Party and site references for the agreement.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date range of the agreement.
• ATTRIBUTE1–15 and CONTEXT — Descriptive flexfield columns carried through from the base object.
• NAME, DESCRIPTION, AGREEMENT_SOURCE_CODE, ORIG_SYSTEM_AGR_ID — Identity and origin metadata, including the source system agreement identifier used in integration scenarios.

Common Use Cases and Queries

The view is typically used where legacy code expects the 11.5 agreements column set. A representative query retrieving active agreements is:

• SELECT agreement_id, agreement_num, agreement_type_code, start_date_active, end_date_active FROM oe_agreements_115_vl WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
• SELECT agreement_id, orig_system_agr_id, name, description FROM oe_agreements_115_vl WHERE agreement_source_code = :source;

Where a report or interface must filter on REVISION_REASON_CODE, the view cannot satisfy the requirement because the column is hard-coded to NULL. In such cases, the current QP agreement entities — or the base OE_AGREEMENTS_VL and its underlying tables — should be consulted directly. For any integration that consumes revision history, this view should be regarded as a compatibility shim only, not as an authoritative source of revision data.