Search Results modifiable_name

Overview

CSF_PO_CONTACT_POINTS_V is an APPS-owned database view in Oracle E-Business Suite (validated in both 12.1.1 and 12.2.2) belonging to the CSF – Field Service product family. It presents a consolidated, denormalized read-only picture of the contact points associated with service requests (incidents) and their related parties. Because it joins the incidents header, the service-request contact-points table, HZ party/relationship data, and both AR and CS lookup tables, the view exposes human-readable representations of contact preference data—phone, e-mail, telex, web, and EDI identifiers—alongside the party relationship that owns each contact point.

In EBS reporting and integration contexts, the view is typically consumed as the reporting layer over the transactional CS_HZ_SR_CONTACT_POINTS table. Rather than re-implementing the relationship and lookup joins, report authors, OAF/ADF pages, and outbound interfaces query this view to obtain the "primary flag," contact type, contact name, and formatted communication preference in a single SELECT. It is the natural companion to CS_INCIDENTS_ALL_VL, the incidents base view, which appears prominently in its definition and is frequently the object users actually search for.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following objects: AR_LOOKUPS (VIEW), CS_HZ_SR_CONTACT_POINTS (SYNONYM, underlying the service request contact point records), CS_INCIDENTS_ALL_VL (VIEW), CS_LOOKUPS (VIEW), FND_GLOBAL (PACKAGE), HR_API (PACKAGE), HR_LOOKUPS (VIEW), HZ_CONTACT_POINTS (SYNONYM), HZ_PARTIES (SYNONYM), HZ_RELATIONSHIPS (SYNONYM), PER_ALL_ASSIGNMENTS_F (SYNONYM), PER_ALL_PEOPLE_F (SYNONYM), and PER_PHONES (SYNONYM).

The documented view text shows a UNION query. The first branch joins CS_INCIDENTS_ALL_VL to CS_HZ_SR_CONTACT_POINTS on INCIDENT_ID, restricts CONTACT_TYPE to 'PARTY_RELATIONSHIP', then joins HZ_RELATIONSHIPS (to resolve the subject party), HZ_PARTIES (to obtain the contact name), HZ_CONTACT_POINTS (outer-joined to supply the actual phone/e-mail/URL/EDI value), CS_LOOKUPS (for the CS_SR_CONTACT_TYPE meaning), and AR_LOOKUPS twice (COMMUNICATION_TYPE and PHONE_LINE_TYPE meanings). The second UNION branch extends coverage to employee-context contact points, which explains the presence of the HR and PER objects (HR_API, HR_LOOKUPS, PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_PHONES) in the dependency list.

Key Columns

• SR_CONTACT_POINT_ID – Primary key of the underlying service request contact point record.
• CONTACT_PARTY_ID / SUBJECT_PARTY_ID – Party identifiers for the contact and the relationship subject, respectively.
• INCIDENT_ID – Foreign key to the service request/incident header.
• CONTACT_POINT_TYPE / CONTACT_TYPE – Type of contact record; CONTACT_POINT_TYPE values include PHONE, EMAIL, TLX, WEB, and EDI.
• PRIMARY_FLAG / DISPLAY_PRIMARY_FLAG – Indicates the primary contact point ('Y'/'N'), with the display variant defaulting to 'N'.
• LOOKUP_MEANING – Decoded meaning from CS_LOOKUPS for CS_SR_CONTACT_TYPE.
• CONTACT_NAME – Concatenation of party name and person pre-name adjunct.
• CONTACT_COMM_PREF – Formatted communication preference, e.g. '(650)555-1212' or 'EMAIL:[email protected]', built through nested DECODE logic against AR_LOOKUPS meanings.
• RELATIONSHIP_ID – Identifier of the HZ relationship linking the contact to the customer.
• MODIFIABLE_TYPE / MODIFIABLE_NAME – Flags (hard-coded to 1) indicating the type and name are modifiable by the consuming UI.

Common Use Cases and Queries

Typical uses include service-request contact reports, notification/distribution lists, and integration extracts that require formatted contact details. A representative query lists active contacts for a given incident:

• SELECT incident_id, contact_name, lookup_meaning, contact_comm_pref, display_primary_flag FROM csf_po_contact_points_v WHERE incident_id = :p_incident_id AND display_primary_flag = 'Y';
• SELECT contact_party_id, contact_name, contact_point_type, contact_comm_pref FROM csf_po_contact_points_v WHERE incident_id = :p_incident_id ORDER BY display_primary_flag DESC, contact_point_type;
• SELECT incident_id, contact_point_type, contact_comm_pref FROM csf_po_contact_points_v WHERE contact_comm_pref LIKE 'EMAIL:%';

Because the view performs the HZ relationship resolution and AR/CS lookup decoding, it is preferred over direct joins to CS_HZ_SR_CONTACT_POINTS for read-only reporting; write operations must still target the underlying base tables and the CS APIs.