Search Results invoice_contact_name




Overview
Explore in AI Chat

Overview

APPS.OEFV_CUSTOMER_AGREEMENTS is a customer-facing, internal Oracle E-Business Suite view that consolidates pricing agreement header data with associated customer, contact, site, and pricing attributes. In EBS 12.1.1 and 12.2.2 it is owned by the APPS schema and registered under both FND design data OE.OEFV_CUSTOMER_AGREEMENTS and ONT.OEFV_CUSTOMER_AGREEMENTS, confirming its role as a presentation-layer object in the Order Management (ONT) and Oracle Pricing (QP) functional family. The view carries a status of VALID and is documented with the standard Oracle restriction that access is unsupported except from standard Oracle Applications programs.

The view is significant to users searching for invoice_contact_name because it exposes invoice contact identification in three complementary forms: a formatted display value (INVOICE_CONTACT_NAME, VARCHAR2(184)), and its decomposed components INVOICE_CONTACT_FIRST_NAME and INVOICE_CONTACT_LAST_NAME (VARCHAR2(150) each). This makes the view a convenient single source for agreement reporting that must show who is to be invoiced, rather than requiring ad hoc joins across HZ_CUST_ACCOUNT_ROLES and HZ_PARTIES.

Underlying Base Objects

The view is defined over a mixture of synonyms and one package. Agreement header data originates from OE_AGREEMENTS_B and its translation table OE_AGREEMENTS_TL. Customer and contact data flow from the Trading Community Architecture (TCA) model: HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTY_SITES, HZ_PARTIES, and HZ_RELATIONSHIPS. The INVOICE_CONTACT_NAME column is resolved through these TCA relationships, with HZ_CUST_ACCOUNT_ROLES supplying the role assignment and HZ_PARTIES contributing the party name components.

Pricing, terms, and rules are sourced from QP_LIST_HEADERS_TL (price lists), RA_RULES (accounting and invoicing rules), and RA_TERMS_TL (payment terms). Lookup decoding is performed against AR_LOOKUPS. Salesperson information is derived from the OE_BIS_SALESPERSON package, which is why SALESREP_NAME is typed as VARCHAR2(4000) rather than a simple column width.

Key Columns

Common Use Cases and Queries

Typical usage includes agreement register reporting, invoice contact validation prior to billing, and integration extracts feeding downstream receivables or data warehouse processes. A representative query retrieving invoice contact detail is:

  • SELECT agreement_number, agreement_name, customer_name, invoice_contact_name, invoice_contact_first_name, invoice_contact_last_name, invoice_to_site_city, payment_terms_name FROM apps.oefv_customer_agreements WHERE UPPER(invoice_contact_name) LIKE '%SMITH%';
  • SELECT agreement_id, invoice_contact_id, invoice_contact_name, invoice_to_site_id FROM apps.oefv_customer_agreements WHERE customer_id = :p_customer_id AND SYSDATE BETWEEN start_date_changed AND end_date;

Because Oracle does not support direct access outside standard applications programs, any custom reporting should be evaluated against the supported Order Management and Pricing APIs, or restricted to read-only query use consistent with the documented warning.