Search Results bic_contact_points_v

Overview

The view BIC_CONTACT_POINTS_V belongs to the BIC (Customer Intelligence) product family within Oracle E-Business Suite releases 12.1.1 and 12.2.2. BIC is classified as an obsolete module within the EBS application stack, meaning it is retained for backwards compatibility and reference purposes but is not actively deployed in current implementations. The view exists primarily to expose contact point information from the Trading Community Architecture (TCA) model in a simplified, presentation-ready form for reporting and integration scenarios.

The view consolidates multiple contact mechanisms — phone, email, web, telex, and EDI — into a single denormalized structure, making it convenient for downstream reports and interfaces that need to present a unified contact identifier without joining to multiple lookup tables. The ETRM documentation explicitly notes that this object is not implemented in the reference database, which is consistent with its obsolete classification. Analysts searching for the term edi_id_number will encounter this view because the column is referenced directly within its defining query text.

Underlying Base Objects

BIC_CONTACT_POINTS_V is defined over a single base table: HZ_CONTACT_POINTS. There are no additional documented base objects, joins, or lookups. This single-table lineage simplifies lineage tracing and impact analysis, but it also means the view cannot resolve any information outside of what resides on the contact point record itself.

The view text wraps the table access in a WITH READ ONLY clause, preventing DML through the view. It is additionally constrained to a read-only cursor context, reinforcing its role as a reporting-only construct. Because the ETRM metadata lists none documented under referenced base objects at the 12.2.2 level, the HZ_CONTACT_POINTS dependency should be confirmed against the live data dictionary in any specific environment before relying upon it.

Key Columns

• CONTACT_POINT_ID — Primary identifier of the contact point record, inherited directly from HZ_CONTACT_POINTS.
• CONTACT_TYPE — An alias for CONTACT_POINT_TYPE, indicating the mechanism: PHONE, EMAIL, WEB, TLX, or EDI.
• OWNER_TABLE_NAME and OWNER_TABLE_ID — Identify the parent entity (for example, HZ_PARTIES or HZ_LOCATIONS) to which the contact point belongs.
• PRIMARY_FLAG — Indicates whether the contact point is the primary mechanism of its type for the owner.
• CONTACT_ID — A derived display string built via a DECODE expression. For EDI records, this concatenates EDI_ID_NUMBER, EDI_PAYMENT_METHOD, and EDI_PAYMENT_FORMAT. For phone records it builds a formatted phone string; for email it returns the address; for web the URL; and for telex the telex number.

The EDI_ID_NUMBER column only surfaces implicitly through the CONTACT_ID concatenation and is not exposed as a standalone column, a nuance that frequently surprises users searching for it by name.

Common Use Cases and Queries

Typical usage involves retrieving formatted contact data for a party or location, or isolating EDI trading partner identifiers.

• Listing all contact points for a given owner entity.
• Extracting EDI identifiers embedded in CONTACT_ID.
• Filtering primary contact mechanisms for customer communications.

Sample query isolating EDI contact data:

SELECT CONTACT_POINT_ID,
       OWNER_TABLE_NAME,
       OWNER_TABLE_ID,
       CONTACT_ID
FROM   BIC_CONTACT_POINTS_V
WHERE  CONTACT_TYPE = 'EDI';

Because the view is marked obsolete and not implemented in the reference database, verification against the target environment is advised before inclusion in production reporting or interface logic.