Search Results pager_phone

Overview

CS_IB_W_EMPLOYEES_V is an APPS-owned database view within the Service (CS) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. The suffix "IB_W" and the column naming convention indicate that this view serves the Interaction Blending / interaction center "W" (worker) data layer used by Oracle Advanced Inbound / Telephony and related service-agent search components. It presents a unified, denormalized record of employees as service resources, exposing identity, address, and telephone contact attributes in a single row per employee.

Its principal role is to make employee records consumable by service modules that require contact information without joining Human Resources tables directly. The most significant attribute in this context, and the term most frequently searched against this view, is WORK_PHONE. Rather than reading a phone column directly from a table, the view derives WORK_PHONE dynamically by calling CS_PARTIES_PKG.GET_PARTY_PHONE and resolving the phone type from the profile option CS_AR_WORK_PHONE_TYPE. This design lets the contact-center deployment expose the correct work number for each agent or resource, based on profile configuration rather than hard-coded data.

Underlying Base Objects

The view text joins HR_EMPLOYEES (aliased E) to PER_ADDRESSES (aliased A) on E.EMPLOYEE_ID = A.PERSON_ID (+), an outer join that preserves employees who have no address record. Because the join is outer, RESOURCE_ADDRESS may be null or contain concatenated null segments for such employees.

Documented referenced base objects for this view are:

• CS_PARTIES_PKG (PACKAGE) — supplies GET_PARTY_PHONE, GET_PARTY_EMAIL, and GET_PARTY_FAX, which resolve phone, pager, cell, home, email, and fax values by phone type.
• FND_PROFILE (PACKAGE) — used via FND_PROFILE.VALUE to obtain the profile options CS_AR_WORK_PHONE_TYPE, CS_AR_PAGER_PHONE_TYPE, CS_AR_CELL_PHONE_TYPE, and CS_AR_HOME_PHONE_TYPE at runtime.
• HR_EMPLOYEES (VIEW) — the primary employee source, contributing FULL_NAME, EMPLOYEE_NUM, and EMPLOYEE_ID.
• PER_ADDRESSES (SYNONYM) — supplies ADDRESS_LINE1 through ADDRESS_LINE3, TOWN_OR_CITY, REGION_2, POSTAL_CODE, and COUNTRY.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY (PACKAGEs) — referenced indirectly through the HR_EMPLOYEES view and its security/name resolution logic.

Key Columns

• RESOURCE_NAME — employee full name, sourced from HR_EMPLOYEES.FULL_NAME.
• RESOURCE_NUMBER — the employee number from HR_EMPLOYEES.EMPLOYEE_NUM.
• RESOURCE_ID — the employee identifier; also returned as ORIGINAL_RESOURCE_ID.
• RESOURCE_TYPE — literal 'EMPLOYEE', distinguishing this resource stream from other resource types.
• RESOURCE_ADDRESS — concatenated address line 1, line 2, line 3, town or city, region 2, postal code, and country.
• CONTACT_CATEGORY — literal 'EMPLOYEE'; SORT_ORDER — literal 'BBBB'.
• WORK_PHONE — resolved via CS_PARTIES_PKG.GET_PARTY_PHONE using the CS_AR_WORK_PHONE_TYPE profile option. This is the column most relevant to work_phone lookups.
• PAGER_PHONE, CELL_PHONE, HOME_PHONE — resolved through the same package using the pager, cell, and home phone type profile options respectively.
• EMAIL and FAX — resolved via CS_PARTIES_PKG.GET_PARTY_EMAIL and GET_PARTY_FAX.

Because WORK_PHONE and its siblings are function-derived, values depend entirely on contact point data existing for the employee and on the profile options being configured; otherwise the columns return null.

Common Use Cases and Queries

Typical use cases include populating agent selection lists in the interaction center, retrieving an employee's work number for outbound or callback processing, and building telephony or reporting extracts of service resources. The most direct work_phone query is:

• SELECT resource_name, resource_number, resource_id, work_phone, email, fax, cell_phone, pager_phone, home_phone FROM apps.cs_ib_w_employees_v WHERE work_phone IS NOT NULL;
• SELECT resource_name, work_phone FROM apps.cs_ib_w_employees_v WHERE resource_number = :employee_num;
• SELECT resource_id, resource_name, resource_address FROM apps.cs_ib_w_employees_v ORDER BY resource_name;

Because the view invokes PL/SQL functions for each phone and email column, queries returning many rows can incur function-call overhead; filtering on RESOURCE_ID or RESOURCE_NUMBER before projecting the contact columns is advisable. All access should be granted through the APPS schema, consistent with standard EBS view privileges.