Results for “purchase_order_number”

50+ results




Overview
Explore in AI Chat

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

Overview

OEBV_CUSTOMER_AGREEMENTS is a read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Order Entry (OE) product family and exposes customer agreement information maintained through the Order Management agreements functionality, which is used to capture negotiated pricing, payment terms, invoicing rules, and contact assignments against a specific customer. The view is marked VALID and carries the ETRM description annotation "- Retrofitted," indicating it was introduced or formalized during the R12 retrofit cycle to provide a stable, backward-compatible reporting surface.

The view is defined with the WITH READ ONLY clause, so it cannot be used for DML. Its principal role is to support reporting, custom concurrent programs, and integration extracts that need agreement header attributes without navigating the full normalized structure of the underlying Order Management agreement tables. The view joins agreement data with site-use data, allowing reporting tools to resolve the invoice-to site use and its related address in a single query.

Underlying Base Objects

The documented view text selects from two objects using an outer join: SO_AGREEMENTS (aliased as AGREEMENT) and RA_SITE_USES_ALL (aliased as SITE), joined on AGREEMENT.INVOICE_TO_SITE_USE_ID = SITE.SITE_USE_ID(+). Because the join to the site-use table is outer, agreement rows are retained even when no matching invoice-to site use exists.

The 12.2.2 ETRM metadata records the referenced base objects as synonyms: OE_AGREEMENTS_B, OE_AGREEMENTS_TL, and HZ_CUST_SITE_USES_ALL. OE_AGREEMENTS_B is the base table holding agreement identifiers, dates, financial defaults, and contact references; OE_AGREEMENTS_TL is the translation table supplying the agreement name (NAME) by language; and HZ_CUST_SITE_USES_ALL provides the customer site-use and address context. The synonym SO_AGREEMENTS resolves these agreement tables, while RA_SITE_USES_ALL resolves the site-use table.

Key Columns

Common Use Cases and Queries

Typical uses include identifying the contact assigned to a customer agreement, reconciling invoicing rules against agreement defaults, and extracting agreements for a customer or date range. The following sample locates agreements by contact:

  • SELECT agreement_number, agreement_name, customer_id, agreement_contact_id, invoice_contact_id FROM oebv_customer_agreements WHERE agreement_contact_id = :p_contact_id;
  • SELECT agreement_number, start_date_active, end_date_active, purchase_order_number FROM oebv_customer_agreements WHERE customer_id = :p_customer_id AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);
  • SELECT agreement_number, invoice_to_site_use_id, invoice_to_site_address_id FROM oebv_customer_agreements WHERE invoicing_rule_id IS NOT NULL;

Because the view is read-only and performs an outer join, queries returning site-use columns may produce nulls for agreements lacking a valid invoice-to site use. When the display columns with quoted names are required, they must be referenced exactly as defined. For 12.2.x environments, report authors should be aware that the underlying agreement tables are exposed through the documented synonyms, so the view continues to function consistently across 12.1.1 and 12.2.2.