Search Results agreement_source_code




Overview
Explore in AI Chat

Overview

OE_AGREEMENTS_V is an APPS-owned database view in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. The ETRM metadata categorizes this object under the QP — Advanced Pricing product, with a documented status of VALID and a description of "Obsolete." The view presents a curated projection of Oracle Order Management agreement data, exposing a denormalized set of columns drawn from the OE_AGREEMENTS base object. In practice, the view renames several columns during projection — for example, AGR.TERM_ID is exposed as PAYMENT_TERM_ID, AGR.PURCHASE_ORDER_NUM as CUST_PO_NUMBER, and AGR.INVOICE_CONTACT_ID as INVOICE_TO_CONTACT_ID — providing consumers with more descriptive labels than the underlying table names.

Because the object is documented as obsolete, it is best regarded as a legacy compatibility view rather than an actively extended interface. Reporting and integration layers that predate newer pricing and order capture APIs may still reference it. Its role is primarily read-only exposure of agreement header attributes for queries, extracts, and dependent program logic.

Underlying Base Objects

The documented referenced base object is OE_AGREEMENTS (SYNONYM). The view text confirms a single-table projection:

SELECT ... FROM OE_AGREEMENTS AGR

No joins, unions, aggregations, or inline views are present in the documented definition. Consequently, OE_AGREEMENTS_V inherits the cardinality of OE_AGREEMENTS directly: one row per agreement record, without filtering, and without the row-multiplying or row-reducing effects that a join-based view would introduce. Every column that appears in the view originates from the OE_AGREEMENTS synonym, resolved in the APPS schema.

Key Columns

Common Use Cases and Queries

The principal use case is lookup of agreement header data, particularly the invoice-to contact, when that identifier is not conveniently exposed elsewhere in a reporting or integration path. A typical query is:

SELECT agreement_id, agreement_num, name, invoice_to_contact_id, invoice_to_org_id, sold_to_org_id, payment_term_id, start_date_active, end_date_active FROM apps.oe_agreements_v WHERE invoice_to_contact_id = :p_contact_id;

Other scenarios include validating that an agreement carries the expected pricing and payment configuration before downstream invoicing, and joining the view to contact or party tables using INVOICE_TO_CONTACT_ID or AGREEMENT_CONTACT_ID to resolve contact names. Because the view passes through the DESCRIPTIVE flexfield columns, it also supports reporting on agreement-level descriptive attributes without querying OE_AGREEMENTS directly. Given its obsolete designation, new development should favor current Order Management and Advanced Pricing interfaces, and any dependency on this view should be reviewed during upgrade and remediation efforts.