Search Results raw_phone_number

Overview

The view APPS.OKL_CS_PARTY_CONTACTS_UV is a customer-facing (UV, or "user view") database object shipped with the Oracle E-Business Suite product OKL – Leasing and Finance Management. It exposes contact information for persons who are related to organizations as contacts, drawing almost entirely on the Oracle Trading Community Architecture (TCA) registry and relationship model. The view joins organization contact records, contact roles, party relationships, party names, and contact points so that a single row returns a person, the organization they belong to, and their reachable communication channels.

Because it consolidates party relationship and contact point data, the view is typically used in OKL reporting extracts, correspondence generation, notifications, and integration feeds that require a flattened, denormalized view of a party contact. It avoids the caller having to navigate the multi-table TCA relationship graph directly, providing a stable read-only interface whose shape is documented by Oracle.

The description column in the definition is derived from CP.CONTACT_POINT_TYPE, meaning the view intentionally labels each contact point row with the type of contact point (for example, phone, email, telex) so consumers can filter or branch on the channel without additional lookups.

Underlying Base Objects

The documented base objects referenced by the view are:

• HZ_PARTIES (referenced twice, as P for the person and PA for the organization) – supplies party identifiers, party names, and person first/last name attributes.
• HZ_RELATIONSHIPS – the relationship graph linking a subject person to an object organization under the CONTACT_OF relationship code, with DIRECTIONAL_FLAG = 'F'.
• HZ_ORG_CONTACTS – organization contact assignments, providing DEPARTMENT and RANK.
• HZ_ORG_CONTACT_ROLES – joined via ORG_CONTACT_ID so that contact role context is available.
• HZ_CONTACT_POINTS – outer-joined contact point rows carrying RAW_PHONE_NUMBER, EMAIL_ADDRESS, TELEX_NUMBER, LAST_CONTACT_DT_TIME, and PRIMARY_FLAG.

The contact point join is an outer join on SUBJECT_ID = CP.OWNER_TABLE_ID and CP.OWNER_TABLE_NAME = 'HZ_PARTIES', so a person with no contact points still appears, with null contact point columns. All base objects are referenced through APPS synonyms.

Key Columns

• PARTY_ID – the organization party identifier (R.OBJECT_ID).
• PERSON_PARTY_ID – the person party identifier (P.PARTY_ID).
• PARTY_NAME / PERSON_FIRST_NAME / PERSON_LAST_NAME – organization name and person name components.
• DEPARTMENT / TITLE / RANK – org-contact context; TITLE comes from PERSON_TITLE.
• CONTACT_POINT_TYPE – the channel type for the contact point.
• RAW_PHONE_NUMBER – the unformatted phone number stored on HZ_CONTACT_POINTS; this is the column surfaced by the "raw_phone_number" search. It is the raw value prior to any country- or format-specific masking.
• EMAIL_ADDRESS / TELEX_NUMBER – additional contact points.
• DATE_NOTIFIED – aliased from CP.LAST_CONTACT_DT_TIME, the last contact timestamp.
• PRIMARY_FLAG – indicates the primary contact point for its type.
• DETAILS – also aliased from CONTACT_POINT_TYPE.

Common Use Cases and Queries

Typical uses include locating phone numbers for organization contacts, building contact directories, and driving correspondence or notification jobs. A basic lookup by person name and phone follows:

• SELECT person_party_id, person_first_name, person_last_name, raw_phone_number, contact_point_type FROM apps.okl_cs_party_contacts_uv WHERE party_name = :org_name AND contact_point_type = 'PHONE';
• SELECT party_id, party_name, person_last_name, raw_phone_number, primary_flag FROM apps.okl_cs_party_contacts_uv ORDER BY party_name, person_last_name;
• SELECT person_party_id, email_address FROM apps.okl_cs_party_contacts_uv WHERE contact_point_type = 'EMAIL' AND primary_flag = 'Y';

When searching specifically on raw_phone_number, note that the value is unformatted and the join is an outer join, so null results indicate a missing contact point rather than a filtering error. Because only the CONTACT_OF relationship with DIRECTIONAL_FLAG = 'F' is included, contacts outside that relationship pattern will not appear.