Search Results csi_contacts_v




Overview
Explore in AI Chat

Overview

CSI_CONTACTS_V is a backward-compatibility view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is part of the CSI – Install Base product family and exposes customer product contacts that were historically maintained in the CS_CONTACTS table. The view preserves the column names and semantics of that legacy table so that custom reports, concurrent programs, forms, and integrations written against CS_CONTACTS continue to function without modification after the Install Base data model was migrated to the CSI schema objects (principally CSI_I_PARTIES).

Functionally, the view answers the question "who is associated with a given installed base instance, and in what capacity?" It is primarily a reporting and integration surface rather than a maintenance surface. Because the view is not key-preserved in all cases and includes function-call columns, it is intended for query access, not for INSERT, UPDATE, or DELETE DML performed directly against it.

Underlying Base Objects

The view is defined over a set of documented base objects spanning Install Base, Service, and Oracle Common Modules:

The resource-side columns are derived through a subquery aliased RS, which returns RESOURCE_ID, ADDRESS, RESOURCE_NAME, RESOURCE_NUMBER, and RESOURCE_CATEGORY. The NVL on RESOURCE_CATEGORY falls back to the party source table when the resource category is null.

Key Columns

Common Use Cases and Queries

Typical uses include install base contact listings for service dashboards, extraction feeds into CRM or third-party systems, and reconciliation reports comparing legacy CS_CONTACTS expectations with the current CSI model.

Listing contacts for a specific instance:

SELECT cs_contact_id, contact_id, contact_type, meaning,
       contact_category, contact_category_meaning,
       primary_flag, preferred_flag
FROM   apps.csi_contacts_v
WHERE  source_object_id = :instance_id
AND    active_end_date IS NULL;

Filtering by contact category, which is the search that motivated this query:

SELECT source_object_id, cs_contact_id, contact_id,
       contact_category, contact_category_meaning
FROM   apps.csi_contacts_v
WHERE  contact_category = :category_code
ORDER  BY source_object_id;

Retrieving the primary contact with resource details:

SELECT source_object_id, contact_id, resource_name,
       resource_number, work_phone_number, email_address
FROM   apps.csi_contacts_v
WHERE  primary_flag = 'Y'
AND    active_end_date IS NULL;

Reports that join large numbers of contact rows should avoid selecting the phone, email, and fax columns unless required, since each invocation of CSI_PARTIES_PKG and FND_PROFILE adds overhead. Applying predicates on the base columns (SOURCE_OBJECT_ID, CONTACT_CATEGORY, PRIMARY_FLAG) first allows the optimizer to reduce the row set before the function-call columns are evaluated.