Search Results agreement_revision




Overview
Explore in AI Chat

Overview

APPS.OEBV_CUSTOMER_AGREEMENTS is a Business Intelligence System (BIS) view in the Oracle E-Business Suite Order Management (ONT) and Order Entry (OE) schema. It exposes customer agreement data — the commercial arrangements that predefine terms such as price lists, purchase order numbers, invoicing rules, and accounting rules to be applied to any sales order placed under the agreement. Because it is a BIS view rather than a transactional base table, it is intended for reporting, extraction, and downstream integration rather than for direct DML. The view is registered in FND Design Data under both the OE and ONT product codes (OE.OEBV_CUSTOMER_AGREEMENTS and ONT.OEBV_CUSTOMER_AGREEMENTS), is documented as VALID, and carries a status consistent across Oracle EBS 12.1.1 and 12.2.2. Its primary value lies in presenting a denormalized, human-readable projection of agreements, including translated and user-facing attributes, so that reports and interfaces do not need to join the underlying header, translation, and site-use tables directly. The AGREEMENT_REVISION column, which is the term the user searched for, surfaces the revision identifier associated with each agreement, enabling consumers to distinguish successive revisions of the same agreement.

Underlying Base Objects

The view is defined over three documented base objects, each accessed through APPS synonyms:

  • OE_AGREEMENTS_B — the base table holding the core agreement attributes: agreement identifiers, customer, dates, PO number, price list, term, salesrep, and the AGREEMENT_REVISION value.
  • OE_AGREEMENTS_TL — the translation table supplying the language-dependent AGREEMENT_NAME (and related descriptive columns) for the agreement.
  • HZ_CUST_SITE_USES_ALL — the Receivables/customer site-uses table, which provides invoice-to organization and site context used to resolve where invoicing occurs for the agreement.

ETRM documentation records that OEBV_CUSTOMER_AGREEMENTS references these objects but is not itself referenced by any database object, confirming its role as a terminal read-only reporting layer. The view is owned by APPS and is intentionally decoupled from transactional code paths.

Key Columns

The view projects agreement identifiers and descriptive attributes alongside foreign keys to related master data. Notable columns include:

Common Use Cases and Queries

Typical uses include agreement master reporting, price-list and term defaulting validation, revision tracking, and data extraction into BI or data-warehouse layers. The following sample SQL retrieves active agreements with their revisions and defaulted pricing/terms:

SELECT agreement_number,
       agreement_name,
       agreement_revision,
       start_date,
       end_date,
       purchase_order_number,
       price_list_id,
       term_id
FROM   apps.oebv_customer_agreements
WHERE  SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1)
ORDER  BY agreement_number, agreement_revision;

Because the view resolves translated names and lookup meanings, it is well suited for direct report output without additional joins. Note that in 12.1.1 and 12.2.2 the view structure is consistent; the AGREEMENT_REVISION column is available in both releases despite differing underlying table versions. Check ETRM for release-specific base table column changes when extending queries.