Search Results work_phone_number

Overview

The CSI_PARTY_CONTACT_DETAILS_V view is an APPS-owned database object within the CSI – Install Base product family. It consolidates party contact information associated with install base instances, exposing the relationship between a customer party, the install base instance it belongs to, and the contact points (phone numbers, email addresses) recorded against that party. The view carries a VALID status and is defined over synonyms and other views rather than a single table, which means it functions as a denormalized reporting and integration surface rather than a transactional entity. In Oracle EBS 12.1.1 and 12.2.2 environments, this view is typically consumed by Install Base service, depot repair, and customer service workflows where a technician or agent needs the current contact details of the party responsible for a given installed asset.

Underlying Base Objects

The view text draws primarily from CSI_I_PARTIES (aliased CIP), which provides the install base party relationship rows, and joins to HZ_PARTIES (HP) for party name and number. Contact points are sourced from HZ_CONTACT_POINTS, with three separate aliases (HCP_WP, HCP_HP, HCP_EM) used to resolve work phone, home phone, and email respectively. Relationship descriptions come from HZ_RELATIONSHIPS (CIR) and CSI_IPA_RELATION_TYPES. Lookup codes are resolved through CSI_LOOKUPS, and the documented base object list also references FND_GLOBAL, JTF_RS_GROUPS_VL, JTF_RS_TEAMS_VL, PER_ALL_PEOPLE_F, PER_PHONES, PO_VENDOR_CONTACTS, and PO_VENDOR_SITES_ALL, reflecting the view's role in resolving contacts across internal employees, resource teams, and vendor sites in addition to external party contacts.

Key Columns

• INSTANCE_PARTY_ID, INSTANCE_ID – identifiers linking the contact to a specific install base instance and its party role.
• PARTY_ID, PARTY_NAME, PARTY_NUMBER – the party owning or associated with the contact.
• PARTY_SOURCE_TABLE / PARTY_SOURCE_MEANING – decodes the origin of the party (for example, HZ or resource).
• RELATIONSHIP_TYPE_CODE, RELATIONSHIP_NAME, RELATIONSHIP_DESCR – describes how the party relates to the instance.
• CONTACT_FLAG, PREFERRED_FLAG, PRIMARY_FLAG – flags indicating whether the row is a contact and its preference/priority.
• WORK_PHONE_NUMBER, HOME_PHONE_NUMBER – formatted concatenations of country code, area code, number, and extension. The home phone is the column users search for as home_phone_number.
• EMAIL_ADDRESS – email contact point for the party.
• ACTIVE_START_DATE, ACTIVE_END_DATE – effective dating of the party relationship.
• Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER) and the DFF columns CONTEXT and ATTRIBUTE1–ATTRIBUTE15.

Common Use Cases and Queries

The most frequent usage is retrieving contact details for a party attached to an installed asset. Because the home_phone_number column is derived with DECODE formatting, queries should select the pre-formatted value directly rather than re-parsing source columns.

• Contact lookup by instance: SELECT instance_id, party_name, work_phone_number, home_phone_number, email_address FROM csi_party_contact_details_v WHERE instance_id = :p_instance_id AND contact_flag = 'Y';
• Preferred contact retrieval: filter on PREFERRED_FLAG = 'Y' and ACTIVE_END_DATE IS NULL to return the current preferred contact.
• Home phone reporting: SELECT party_number, party_name, home_phone_number FROM csi_party_contact_details_v WHERE home_phone_number IS NOT NULL;
• Integration feeds: external service or depot applications extract party contact rows keyed by INSTANCE_ID to synchronize technician-facing contact cards.

Because the view performs multiple outer joins and lookup decodes, performance in high-volume reporting is best served by constraining on INSTANCE_ID, PARTY_ID, or CONTACT_IP_ID, all of which are backed by indexes on the underlying CSI and HZ base tables.