Search Results email_format




Overview
Explore in AI Chat

Overview

AR_PHONES_V is a Receivables (AR) view owned by the APPS schema that exposes contact point information held in the Oracle E-Business Suite foundation tables. The ETRM metadata labels the object with the description "(Release 115 Only)," indicating that its documented lineage originates with the earlier AR phone model predating the HZ (Trading Community Architecture) contact infrastructure. In practice the view is retained in EBS 12.1.1 and 12.2.2 for backward compatibility, allowing legacy Receivables reports, concurrent programs, and custom extensions to continue referencing phone, telex, email, and web contact points without being rewritten against the newer HZ_CONTACT_POINTS API.

Its principal role is a flattened, reporting-oriented projection of contact points. Rather than requiring a caller to decode lookup codes, resolve line types, and reconcile owner table context, AR_PHONES_V joins the contact point rows to AR_LOOKUPS twice or more so that lookup meanings for phone line type, email format, and contact point purpose are presented as readable values. For integration purposes the view is read-only; all maintenance must occur against the underlying HZ contact point entities.

Underlying Base Objects

The documented base objects for AR_PHONES_V are AR_LOOKUPS, which is itself a view, and HZ_CONTACT_POINTS, accessed through a synonym. The view is a simple equi-join projection over these objects, with outer joins applied for the email format and purpose lookups so that contact points lacking those attributes are not excluded.

Contact points are filtered to exclude CONTACT_POINT_TYPE values of 'EDI'. The communication type join derives from NVL(PHON.PHONE_LINE_TYPE, PHON.CONTACT_POINT_TYPE) matched against AR_LOOKUPS.LOOKUP_CODE where the lookup type is either 'COMMUNICATION_TYPE' (restricted to PHONE, TLX, EMAIL, and WEB) or 'PHONE_LINE_TYPE'. Because the driving table is the synonym over HZ_CONTACT_POINTS, every row returned corresponds to a single contact point record identified by CONTACT_POINT_ID, and the ROWID pseudo-column is carried through for legacy positional updates in older code paths.

Key Columns

  • CONTACT_POINT_ID — primary identifier of the contact point row in the HZ model; the true foreign key for downstream joins.
  • CUST_CONTACT_POINT_ID — present in the view text as a NULL placeholder, reflecting the obsolete Release 115 customer contact point key. It carries no data in current releases and is preserved only so legacy code referencing the column parses and executes.
  • Phone number columns — a DECODE expression returns TELEX_NUMBER when the contact point type is 'TLX', otherwise PHONE_NUMBER. PHONE_COUNTRY_CODE, PHONE_AREA_CODE, and PHONE_EXTENSION accompany it.
  • Status and type columns — STATUS indicates the contact point state; CONTACT_POINT_TYPE and the NVL-based line type, plus TELEPHONE_TYPE, classify the communication channel.
  • MEANING columns — lookup meanings for line type, email format, and contact point purpose, derived from the AR_LOOKUPS joins.
  • Email and web columns — EMAIL_ADDRESS, EMAIL_FORMAT, URL, and WEB_TYPE support electronic contact points.
  • Ownership and audit columns — OWNER_TABLE_NAME, OWNER_TABLE_ID, ORIG_SYSTEM_REFERENCE, PRIMARY_FLAG, PRIMARY_BY_PURPOSE, and the standard WHO columns.
  • ATTRIBUTE1 through ATTRIBUTE20 — descriptive flexfield segments and related free-format attributes.

Common Use Cases and Queries

Typical usage includes verifying that a phone number was created correctly after a customer or contact load, listing all communication channels for a party, and identifying primary phone numbers for outbound correspondence. A representative query retrieves phone points for a given contact point identifier:

  • SELECT contact_point_id, phone_country_code, phone_area_code, phone_number FROM ar_phones_v WHERE contact_point_id = :p_id;
  • SELECT contact_point_id, phone_number, meaning FROM ar_phones_v WHERE contact_point_type = 'PHONE' AND primary_flag = 'Y';
  • SELECT contact_point_id, email_address, email_format FROM ar_phones_v WHERE email_address IS NOT NULL;

When joining the view to customer or site data, use CONTACT_POINT_ID rather than CUST_CONTACT_POINT_ID, since the latter is a NULL placeholder. Because the view depends on HZ_CONTACT_POINTS and AR_LOOKUPS, any query benefits from predicates that restrict contact point type and purpose so the optimizer does not scan unnecessary lookup rows.