Search Results customer_contact_email

Overview

APPS.OEFV_ORDER_HEADERS is a reporting view in the Oracle Order Management (ONT) module of Oracle E-Business Suite. In ETRM design data it is registered under FND Design Data as ONT.OEFV_ORDER_HEADERS, is owned by the APPS schema, and carries a status of VALID. The view presents a denormalized, human-readable projection of order header information: rather than exposing raw foreign keys alone, it resolves identifiers into descriptive text such as customer name, contact email, ship-to and bill-to addresses, price list, payment terms, agreement, salesperson, and order source. This makes it well suited to ad hoc inquiry, discoverer-style reporting, and integration extracts where a flat, descriptive row per order header is preferable to joining the normalized Ontario base tables manually.

Oracle classifies the object with an "Oracle Internal Use Only" warning, stating that Oracle Corporation does not support access to applications data using this object except from standard Oracle Applications programs. The view type is documented as Internal. Consequently, custom code depending on it should treat the column list as potentially subject to change across point releases, even though the object is VALID in both 12.1.1 and 12.2.2.

Underlying Base Objects

OEFV_ORDER_HEADERS is defined over a mix of Order Management and Oracle Receivables/Human Resources foundation objects. The transactional anchor is OE_ORDER_HEADERS_ALL, which supplies the header identifier and core order attributes. Descriptive data is drawn from reference and setup objects including OE_TRANSACTION_TYPES_TL, OE_ORDER_SOURCES, OE_AGREEMENTS_TL, QP_LIST_HEADERS_TL, RA_TERMS, RA_RULES, FND_CURRENCIES, FND_USER (used by the OE_BIS_SALESPERSON package), and AR_LOOKUPS for the "_LA:" descriptive-flex style lookup columns.

Customer and party information is resolved through the Oracle Trading Community Architecture (TCA) hierarchy: HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_PARTIES, HZ_RELATIONSHIPS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_CONTACT_POINTS. Contact email and phone values, including CUSTOMER_CONTACT_EMAIL, are derived from HZ_CONTACT_POINTS via the contact identifier exposed on the header. Inventory organization information comes from MTL_PARAMETERS via the sold-from organization.

Key Columns

The view exposes identifiers alongside their resolved descriptions. Principal columns include:

• HEADER_ID, ORG_ID, ORDER_TYPE_ID, SOLD_FROM_ORG_ID — surrogate keys linking back to OE_ORDER_HEADERS_ALL and inventory organizations.
• ORDER_NUMBER, ORDER_TYPE, ORDER_SOURCE, DATE_ORDERED, CUSTOMER_PO_NUMBER — core order identification attributes.
• CUSTOMER_NUMBER, CUSTOMER — the TCA account number and party/account name.
• CUSTOMER_CONTACT, CUSTOMER_CONTACT_ID, CUSTOMER_CONTACT_EMAIL, CUSTOMER_CONTACT_PHONE_NUMBER, CUSTOMER_CONTACT_PHONE_EXT — contact identity and communication details resolved from TCA contact points; CUSTOMER_CONTACT_EMAIL is VARCHAR2(2000).
• SHIP_TO_LOCATION, SHIP_TO_ADDRESS1-4, SHIP_TO_CTY_ST_ZIP_CTRY, SHIP_TO_CONTACT, SHIP_TO_CUSTOMER — ship-to party site and address elements.
• BILL_TO_LOCATION, BILL_TO_ADDRESS1-4, BILL_TO_CTY_ST_ZIP_CTRY, BILL_TO_CONTACT — bill-to address and contact.
• AGREEMENT, PRICE_LIST, PAYMENT_TERMS, INVOICING_RULE, CURRENCY, SALESPERSON — commercial terms and ownership.
• _LA:SALES_CHANNEL, _LA:STATUS, _LA:TAX_EXEMPTED, _LA:FREIGHT_TERMS, _LA:BOOKED_FLAG, _LA:CANCELLED_FLAG — lookup-decoded attributes.

Common Use Cases and Queries

The view is frequently used for customer-facing order extracts, contact lookups, and shipment documentation where a single descriptive row per order is required. A typical query retrieving contact email information is:

• SELECT order_number, customer, customer_contact, customer_contact_email FROM apps.oefv_order_headers WHERE date_ordered >= :p_from_date;
• SELECT order_number, ship_to_address1, ship_to_cty_st_zip_ctry FROM apps.oefv_order_headers WHERE org_id = :p_org_id;
• SELECT order_number, price_list, payment_terms, currency FROM apps.oefv_order_headers WHERE order_type = :p_order_type;

Because the view is documented as internal and unsupported for direct access, production integrations should generally prefer supported Order Management APIs or public views. Where this view is used for reporting, it should be treated defensively, with column availability validated against the target release.