Search Results contact_category_meaning

Overview

APPS.CSI_CONTACTS_V is a consolidated reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes contact information associated with parties, resources, and service-related entities managed within the CSI (Complex Service and Install Base) module. The object is registered under FND Design Data as CSI.CSI_CONTACTS_V, carries a status of VALID, and is classified as an internal view type. Oracle's standard warning applies: the view is designated for internal use only and is not supported for direct customer access except through standard Oracle Applications programs.

Functionally, the view normalizes contact details drawn from CRM and HR sources into a single row per contact-to-object relationship. It surfaces contact category values alongside their translated meanings, resource identifiers, address information, and multiple communication channels. This design makes it particularly useful whenever a report or integration must resolve a user search for contact_category_meaning — that is, displaying the descriptive label that corresponds to an internal lookup code without requiring a separate join to the lookup tables.

Underlying Base Objects

The view is defined over a documented set of base objects spanning multiple EBS schemas. The principal contact and party data originate from CSI_I_PARTIES and HZ_PARTIES, with relationship type context supplied by CSI_IPA_RELATION_TYPES. Resource-side attributes are resolved through JTF_RS_GROUPS_VL and JTF_RS_TEAMS_VL, while employee-oriented fields are drawn from HR_EMPLOYEES, HR_PERSON_NAME, and PER_ADDRESSES.

• CSI_I_PARTIES, HZ_PARTIES, CSI_IPA_RELATION_TYPES — contact/party relationships and role types.
• HR_EMPLOYEES, HR_PERSON_NAME, PER_ADDRESSES, HR_GENERAL — employee, name, and address resolution.
• JTF_RS_GROUPS_VL, JTF_RS_TEAMS_VL — resource group and team context.
• CSI_LOOKUPS — lookup code translation, including contact category meanings.
• CSI_PARTIES_PKG, FND_PROFILE, HR_SECURITY — supporting logic for security and profile options.

Because several of these references are synonyms or views rather than tables, the view is effectively a denormalized read layer over the CSI, HZ, HR, and JTF subsystems.

Key Columns

The column set is organized into identity, classification, activity, and resource-communication groups:

• CS_CONTACT_ID, CONTACT_ID, SOURCE_OBJECT_ID, SOURCE_OBJECT_CODE — the internal contact and source object identifiers that establish the relationship.
• CONTACT_TYPE, MEANING — the contact type code and its associated meaning.
• CONTACT_CATEGORY, CONTACT_CATEGORY_MEANING — the category code and its translated description. CONTACT_CATEGORY_MEANING is the column directly relevant to the user's search.
• PRIMARY_FLAG, PREFERRED_FLAG, SVC_PROVIDER_FLAG — flags indicating the primary contact, the preferred contact, and whether the contact is a service provider.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective-date range for the contact assignment.
• RESOURCE_ID, RESOURCE_NAME, RESOURCE_NUMBER, RESOURCE_CATEGORY — resource identity and classification.
• ADDRESS, WORK_PHONE_NUMBER, CELL_PHONE_NUMBER, PAGER_PHONE_NUMBER, EMAIL_ADDRESS, FAX_NUMBER, HOME_PHONE_NUMBER — mailing and communication attributes.
• LAST_UPDATE_DATE, CREATED_BY, OBJECT_VERSION_NUMBER, ATTRIBUTE1–15, CONTEXT — audit, concurrency, and descriptive flexfield columns.

Common Use Cases and Queries

The view is typically used in service and install-base reporting, contact-list generation, and interface extraction where a single, human-readable label for contact classification is required. A representative query retrieving the category meaning together with contact and resource details is:

SELECT cs_contact_id, contact_category, contact_category_meaning, resource_name, email_address, work_phone_number FROM apps.csi_contacts_v WHERE contact_category_meaning IS NOT NULL;

Filtering by relationship context — for example, restricting to primary service-provider contacts active as of the current date — can be accomplished with:

SELECT cs_contact_id, resource_number, contact_category_meaning FROM apps.csi_contacts_v WHERE primary_flag = 'Y' AND svc_provider_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

Because CONTACT_CATEGORY_MEANING is already resolved within the view, reports can present descriptive category values without additional joins to CSI_LOOKUPS. Analysts should nevertheless validate results against the effective-date and security logic implied by HR_SECURITY and FND_PROFILE, which govern row visibility for the calling user.