Results for “cs_ar_cell_phone_type”
16 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.CS_IB_W_EMPLOYEES_V is a service-oriented view in Oracle E-Business Suite that exposes employee records in a "resource" shaped result set. It is intended for use by the Interaction Blending / CRM resource search and selection flows (the "IB" and "W" naming conventions reflect the Interaction Blending and Web/workspace contexts), where employees must be presented alongside other resource types such as parties, contacts, and resources. The view flattens an employee record into a standardized set of columns — resource_name, resource_number, resource_id, resource_type, resource_address, contact_category, and sort_order — and decorates it with communication channel values retrieved through the CS_PARTIES_PKG API.
Because the view returns the same column shape regardless of the underlying source, consumers can union it with equivalent party and contact views to present a unified resource picker. It is a reporting and integration convenience view rather than a transactional object, and it is owned by APPS.
Underlying Base Objects
The view is defined over two data sources joined in the FROM clause:
- HR_EMPLOYEES — the primary source of employee identity attributes (full_name, employee_num, employee_id). In ETRM this resolves through the HR security and name logic packages rather than as a raw table.
- PER_ADDRESSES (listed as a synonym) — outer-joined on e.employee_id = a.person_id (+) to supply the concatenated address string.
- CS_PARTIES_PKG — supplies work, pager, cell, home phone, email, and fax values via GET_PARTY_PHONE, GET_PARTY_EMAIL, and GET_PARTY_FAX.
- FND_PROFILE — resolves the profile options CS_AR_WORK_PHONE_TYPE, CS_AR_PAGER_PHONE_TYPE, CS_AR_CELL_PHONE_TYPE, and CS_AR_HOME_PHONE_TYPE, which map each phone slot to a phone type code.
- HR_GENERAL, HR_PERSON_NAME, HR_SECURITY — referenced indirectly through HR_EMPLOYEES for name formatting and row-level security enforcement.
Key Columns
- RESOURCE_ID / ORIGINAL_RESOURCE_ID — both set to employee_id, providing identity for the resource and a back-reference to the source record.
- RESOURCE_TYPE — literal 'EMPLOYEE', the discriminator used when blending multiple sources.
- RESOURCE_NAME / RESOURCE_NUMBER — full_name and employee_num for display.
- RESOURCE_ADDRESS — concatenation of address_line1..3, town_or_city, region_2, postal_code, and country.
- CONTACT_CATEGORY — literal 'EMPLOYEE'; SORT_ORDER — literal 'BBBB', a fixed ordering token.
- WORK_PHONE, PAGER_PHONE, CELL_PHONE, HOME_PHONE — phone numbers resolved by type from the profile-driven phone type codes.
- EMAIL, FAX — email address and fax number for the employee party.
Common Use Cases and Queries
A frequent driver for searching this view is retrieving an employee's work phone type configuration, referenced by the profile option CS_AR_WORK_PHONE_TYPE (the term "cs_ar_work_phone_type" in the user's query). Administrators typically query this value directly, then join to this view to confirm the resolved number.
- Look up an employee's resolved work phone:
SELECT resource_name, work_phone FROM apps.cs_ib_w_employees_v WHERE resource_number = :employee_num;
- Inspect the profile option that governs the work phone slot:
SELECT profile_option_name, profile_option_value FROM fnd_profile_option_values WHERE profile_option_name = 'CS_AR_WORK_PHONE_TYPE';
- Blend employees with other resource sources for a picker:
SELECT resource_id, resource_name, resource_type, work_phone FROM apps.cs_ib_w_employees_v WHERE UPPER(resource_name) LIKE UPPER('%'||:search||'%') ORDER BY resource_name; - Report contact channels for a department's employees:
SELECT resource_name, cell_phone, email, fax FROM apps.cs_ib_w_employees_v;
Because the view calls PL/SQL functions per row, query performance depends on the volume of employees scanned; predicates that restrict the employee set before the functions are evaluated produce the best response times.
-
Not implemented in this database·Explore CS module →
-
Not implemented in this database·Explore CS module →
-
View: CS_IB_W_EMPLOYEES_V 12.1.1
APPS.CS_IB_W_EMPLOYEES_V·↳ CS_PARTIES_PKG·↳ FND_PROFILE·↳ HR_EMPLOYEES·Explore CS module →
-
View: CS_IB_W_EMPLOYEES_V 12.2.2
APPS.CS_IB_W_EMPLOYEES_V·↳ CS_PARTIES_PKG·↳ FND_PROFILE·↳ HR_EMPLOYEES·Explore CS module →
-
View: CS_JTF_RESOURCES_V 12.2.2
Resource Details
APPS.CS_JTF_RESOURCES_V·↳ CS_PARTIES_PKG·↳ FND_PROFILE·↳ HR_GENERAL·Explore CS module →
-
View: CS_JTF_RESOURCES_V 12.1.1
Resource Details
APPS.CS_JTF_RESOURCES_V·↳ CS_PARTIES_PKG·↳ FND_PROFILE·↳ HR_GENERAL·Explore CS module →
-
VIEW: APPS.CSI_CONTACTS_V 12.1.1
-
VIEW: APPS.CSI_CONTACTS_V 12.2.2
-
View: CSI_CONTACTS_V 12.2.2
Backward Compatible : Customer Product Contacts (View for table CS_CONTACTS).
APPS.CSI_CONTACTS_V·↳ CSI_IPA_RELATION_TYPES·↳ CSI_I_PARTIES·↳ CSI_LOOKUPS·Explore CSI module →
-
View: CSI_CONTACTS_V 12.1.1
Backward Compatible : Customer Product Contacts (View for table CS_CONTACTS).
APPS.CSI_CONTACTS_V·↳ CSI_IPA_RELATION_TYPES·↳ CSI_I_PARTIES·↳ CSI_LOOKUPS·Explore CSI module →
-
View: CS_CONTACTS_V 12.2.2
Information regarding the Resources and their type of contacts in Installedbase
Not implemented in this database·Explore CS module →
-
View: CS_CONTACTS_V 12.1.1
Information regarding the Resources and their type of contacts in Installedbase
Not implemented in this database·Explore CS module →