Results for “asf_contact_points_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ASF_CONTACT_POINTS_V is a reporting view within the ASF – Sales Online product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes contact point records maintained in the Oracle Receivables/HZ (Trading Community Architecture) data model, filtered to the telephone, facsimile, and electronic mail contact point types. The view is implemented as a database view rather than a stored application object; the ETRM metadata records it as "Not implemented in this database," meaning no deployed instance was detected in the reference environment at documentation time. As a result, it carries no documented owner and no documented base-table inventory in the 12.2.2 metadata set.

Functionally, the view serves as a denormalized read interface over contact point data, joining lookup codes so that consumers receive human-readable meanings alongside the raw coded values. It presents the same information that the Sales Online forms display, allowing integrators and report authors to retrieve phone, fax, and email records without reconstructing the multi-table lookup joins themselves.

Underlying Base Objects

The view text defines two base sources. The primary source is HZ_CONTACT_POINTS (aliased CNT), the TCA table that stores all contact point records regardless of channel. The view restricts this table with a predicate on CONTACT_POINT_TYPE limited to the values 'PHONE', 'FAX', and 'EMAIL'.

Two outer-joined references to AR_LOOKUPS supply the decoded meanings. The alias COMMUNICATION_TYPE is joined on CNT.PHONE_LINE_TYPE = COMMUNICATION_TYPE.LOOKUP_CODE with LOOKUP_TYPE = 'COMMUNICATION_TYPE', producing the PHONE_LINE_TYPE_MEANING column. The alias CODE_STATUS is joined on CNT.STATUS = CODE_STATUS.LOOKUP_CODE with LOOKUP_TYPE = 'CODE_STATUS', producing STATUS_MEANING. Both joins are outer joins, so contact points with unmatched lookup codes remain visible. The view additionally filters status to 'A' (active) and 'I' (inactive).

Key Columns

Because the user searched for "communication_type," the most relevant column is PHONE_LINE_TYPE, decoded by the COMMUNICATION_TYPE lookup as PHONE_LINE_TYPE_MEANING. This pair distinguishes, for example, a business phone from a mobile or alternate number. Other significant columns include:

• CONTACT_POINT_ID — primary identifier for the contact point record.
• CONTACT_POINT_TYPE — channel type: PHONE, FAX, or EMAIL.
• STATUS / STATUS_MEANING — 'A' or 'I', decoded from the CODE_STATUS lookup.
• OWNER_TABLE_NAME / OWNER_TABLE_ID — the entity (for example, a party or customer account) that owns the contact point.
• EMAIL_FORMAT and EMAIL_ADDRESS — email channel attributes.
• PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PHONE_EXTENSION — telephone channel attributes.
• PRIMARY_FLAG, DO_NOT_USE_FLAG, PHONE_PREFERRED_ORDER — usage and ranking indicators.
• ORIG_SYSTEM_REFERENCE — the source-system key for integration reconciliation.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the standard EBS descriptive flexfield columns, mostly truncated in the documented column list.

Common Use Cases and Queries

Typical uses include customer contact audits, telephony/CTI feed extraction, deduplication checks, and integration staging. A representative query filters by communication type:

SELECT CONTACT_POINT_ID, OWNER_TABLE_NAME, OWNER_TABLE_ID, PHONE_LINE_TYPE, PHONE_LINE_TYPE_MEANING, PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PRIMARY_FLAG FROM ASF_CONTACT_POINTS_V WHERE CONTACT_POINT_TYPE = 'PHONE' AND PHONE_LINE_TYPE = 'BUSINESS' AND STATUS = 'A' ORDER BY OWNER_TABLE_ID, PHONE_PREFERRED_ORDER;

For email exports, substitute CONTACT_POINT_TYPE = 'EMAIL' and select EMAIL_ADDRESS. Because the view is not documented as implemented in the reference database, deployment should be verified against the target instance before dependence in production reports.