Search Results resource_category

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:

• CSI_I_PARTIES (synonym) — the primary source. Supplies instance party rows, relationship type, party identifiers, primary/preferred flags, effective dates, and the DFF attribute columns.
• CSI_IPA_RELATION_TYPES (synonym) — joined via CIRT to translate RELATIONSHIP_TYPE_CODE into a meaningful contact type description (MEANING).
• CSI_LOOKUPS (view) — resolves the lookup meaning used for CONTACT_CATEGORY.
• CSI_PARTIES_PKG (package) — provides the PL/SQL functions GET_PARTY_PHONE, GET_PARTY_EMAIL, and GET_PARTY_FAX used to derive phone, email, and fax values.
• FND_PROFILE (package) — supplies profile-option values (CS_AR_WORK_PHONE_TYPE, CS_AR_CELL_PHONE_TYPE, CS_AR_PAGER_PHONE_TYPE) that determine which contact point type is returned for each phone column.
• HZ_PARTIES, HR_EMPLOYEES, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, PER_ADDRESSES, JTF_RS_GROUPS_VL, and JTF_RS_TEAMS_VL — joined through the resource subquery to expose resource identifiers, names, addresses, and contact categories for service resources referenced on contact records.

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

• CS_CONTACT_ID — mapped from INSTANCE_PARTY_ID; the unique identifier of the contact record within the install base context.
• SOURCE_OBJECT_ID / SOURCE_OBJECT_CODE — the instance identifier and the hard-coded code 'CP' (customer product), indicating the contact is attached to an installed base instance.
• CONTACT_TYPE / MEANING — the relationship type code and its decoded description from CSI_IPA_RELATION_TYPES.
• CONTACT_ID — the HZ_PARTIES party identifier of the contact.
• CONTACT_CATEGORY / CONTACT_CATEGORY_MEANING — the party source table value and its lookup meaning from CSI_LOOKUPS. This pair is the object most often queried when users search for "contact_category," because it distinguishes the origin or classification of the contact (for example employee versus customer contact).
• PRIMARY_FLAG / PREFERRED_FLAG — indicate the primary and preferred contact for the instance. SVC_PROVIDER_FLAG is returned as NULL in this view.
• ACTIVE_START_DATE / ACTIVE_END_DATE — effective dating for the contact relationship.
• WORK_PHONE_NUMBER, CELL_PHONE_NUMBER, PAGER_PHONE_NUMBER, EMAIL_ADDRESS, FAX_NUMBER — derived through CSI_PARTIES_PKG and profile options; these are function-call columns and can be costly on large result sets.
• RESOURCE_ID, RESOURCE_NAME, RESOURCE_NUMBER, ADDRESS, RESOURCE_CATEGORY — service resource attributes associated with the contact.
• ATTRIBUTE1 through ATTRIBUTE15, CONTEXT — descriptive flexfield columns carried through from CSI_I_PARTIES.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.

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.