Search Results pager_phone_number




Overview
Explore in AI Chat

Overview

The CS_CONTACTS_V view is a Service (CS) module object in Oracle E-Business Suite 12.1.1 and 12.2.2 that presents contact information for resources maintained within Oracle Installed Base. It is a reporting and integration-oriented view that consolidates contact records stored against Installed Base entities with related resource details and — importantly for the inquiry at hand — denormalized telephone and email attributes sourced from Oracle HRMS / People tables. The view is useful when applications or custom reports require a single, flattened row per contact that includes the resource name, resource number, contact type meaning, and derived contact methods such as work phone, cell phone, pager, fax, and email. It surfaces the CELL_PHONE_NUMBER attribute, which is the term users most frequently search for against this object, alongside its peer telephony columns.

Underlying Base Objects

The view is defined primarily over the CS_CONTACTS table (aliased CC), which stores the core contact relationships, with a lookup joined from CS_LOOKUPS (CSL) to resolve the CONTACT_TYPE code into its MEANING. Resource-level attributes are joined from a resource source aliased CE, exposing RESOURCE_ID, RESOURCE_NAME, RESOURCE_NUMBER, RESOURCE_ADDRESS, and RESOURCE_CATEGORY. Additional scalar subqueries reference HR_EMPLOYEES and PER_PHONES (via HE and PP) to derive phone numbers by PHONE_TYPE, and HR_EMPLOYEES again to derive EMAIL_ADDRESS. The documentation notes that no base objects are formally registered in the ETRM metadata and that the object is "Not implemented in this database," meaning the definition is retained for reference rather than deployed in the queried environment. Its relationship to the bases is therefore a straightforward parent/child and lookup join model layered with correlated HR subqueries.

Key Columns

Common Use Cases and Queries

A typical reporting requirement is retrieving the mobile number for contacts of a given Installed Base resource. Because CELL_PHONE_NUMBER is derived through a correlated subquery against PER_PHONES, results depend on HR data availability and return at most one phone per contact (ROWNUM < 2).

SELECT resource_name,
       resource_number,
       contact_type,
       meaning,
       cell_phone_number,
       work_phone_number,
       email_address
  FROM cs_contacts_v
 WHERE cell_phone_number IS NOT NULL
   AND primary_flag = 'Y';

Integration use cases include exporting contact channels to external service or CRM systems, building Installed Base contact directories, and reconciling Service contacts against HRMS phone records. Analysts should note the FIRST_ROWS hint, the row-per-contact cardinality, and the effective dating columns when filtering active contacts.