Search Results asf_phone_contact_points_v
Overview
The ASF_PHONE_CONTACT_POINTS_V view belongs to the ASF – Sales Online product family within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It exposes telephone contact point records held in the Trading Community Architecture (TCA) contact point model, enriched with lookup meanings decoded from the Oracle Receivables lookup repository. The view is a reporting and integration construct rather than a transactional object; in the documented environment it is marked as "Not implemented in this database," which is a common status for ETRM catalog entries captured from a reference instance where the ASF module is not licensed or the view was not deployed.
Its primary role is to present phone-specific contact points with human-readable status and phone line type descriptions, allowing downstream reports, interfaces, and data extracts to consume phone data without repeatedly joining to the AR_LOOKUPS table for code decoding. Because the underlying HZ_CONTACT_POINTS table stores both status and line type as coded lookup values, the view provides immediate interpretive value to consumers.
Underlying Base Objects
The view is defined over three referenced objects:
- HZ_CONTACT_POINTS — the TCA base table storing all contact points (phone, email, URL, fax, etc.). The view aliases it as
PHONand filters toCONTACT_POINT_TYPE = 'PHONE'. - AR_LOOKUPS (aliased
COMMUNICATION_TYPE) — joined onLOOKUP_TYPE = 'PHONE_LINE_TYPE'to resolve the phone line type meaning. - AR_LOOKUPS (aliased
CODE_STATUS) — joined onLOOKUP_TYPE = 'CODE_STATUS'to resolve the status meaning. This join directly addresses the code_status search term, since the view filtersPHON.STATUS IN ('A','I')and translates those codes to their display meanings.
All three are inner-joined, so contact points whose status or line type lack an active lookup entry are excluded from the result set.
Key Columns
- ROW_ID — the physical row identifier of the underlying contact point row.
- CONTACT_POINT_ID — primary key of the contact point.
- CONTACT_POINT_TYPE — always 'PHONE' in this view.
- STATUS / STATUS_MEANING — the coded status ('A' active, 'I' inactive) and its decoded meaning from
CODE_STATUS. - OWNER_TABLE_NAME / OWNER_TABLE_ID — polymorphic reference identifying the owning entity (e.g., HZ_PARTIES, HZ_LOCATIONS).
- PHONE_LINE_TYPE / PHONE_LINE_TYPE_MEANING — line type code and decoded description (e.g., General, Mobile, Fax).
- PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PHONE_EXTENSION — the components of the phone number.
- PRIMARY_FLAG, DO_NOT_USE_FLAG, PHONE_PREFERRED_ORDER — flags controlling primary designation, suppression, and ordering.
- Audit and concurrency columns —
LAST_UPDATE_DATE,LAST_UPDATED_BY,CREATION_DATE,CREATED_BY,LAST_UPDATE_LOGIN,REQUEST_ID,PROGRAM_APPLICATION_ID,PROGRAM_ID,PROGRAM_UPDATE_DATE. - ORIG_SYSTEM_REFERENCE and ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 — the DFF context and descriptive flexfield columns.
Common Use Cases and Queries
Typical consumers include customer master extracts, 360-degree party reports, and integration staging loads where phone data must carry decoded meanings. Note that ASF-specific views in EBS 12.1.1 predate some TCA multi-org generalizations; in 12.2.2 ensure the correct operating unit context if referenced from subledger reports. Because inner joins exclude orphaned lookups, verify that CODE_STATUS and PHONE_LINE_TYPE lookups remain active before relying on complete record counts.
SELECT contact_point_id,
status,
status_meaning,
phone_line_type_meaning,
phone_country_code,
phone_area_code,
phone_number
FROM asf_phone_contact_points_v
WHERE status = 'A'
AND owner_table_name = 'HZ_PARTIES'
ORDER BY phone_preferred_order;
For reconciliation against raw TCA data, compare counts between HZ_CONTACT_POINTS (filtered to phones) and this view to detect records dropped by the lookup joins. For data-quality audits, query for rows where status_meaning is null or where do_not_use_flag = 'Y', since these indicate inactive or suppressed numbers still present in downstream extracts.
-
View: ASF_PHONE_CONTACT_POINTS_V
12.1.1
product: ASF - Sales Online , implementation_dba_data: Not implemented in this database ,
-
View: ASF_PHONE_CONTACT_POINTS_V
12.2.2
product: ASF - Sales Online , implementation_dba_data: Not implemented in this database ,
-
12.1.1 FND Design Data
12.1.1
-
12.2.2 FND Design Data
12.2.2