Search Results csc_customer_response_v




Overview
Explore in AI Chat

Overview

The CSC_CUSTOMER_RESPONSE_V view is a Customer Care (CSC) reporting and integration object owned by the APPS schema in Oracle E-Business Suite. In the ETRM metadata it is registered as a VALID VIEW within the CSC – Customer Care product family, and its stated purpose is to expose Relationship information together with Subject (Caller) and Object (Person/Group/Organization) information. In practice this means the view presents a denormalized, denormalized-by-design projection that joins a subject party to an object party through a relationship record, then decorates both sides of that relationship with the profile attributes of each party type.

For EBS 12.1.1 and 12.2.2, the Trading Community Architecture (TCA) model stores people, organizations, and groups as rows in HZ_PARTIES, while their extended attributes are held in HZ_PERSON_PROFILES and HZ_ORGANIZATION_PROFILES. Relationships between parties are stored in HZ_RELATIONSHIPS. The CSC view collapses these distinct TCA entities into a single consumable result set so that Customer Care screens, contact-center dashboards, and downstream integrations can retrieve "who is related to whom" without writing the multi-table join themselves.

Underlying Base Objects

The documented ETRM base objects referenced by the view are all TCA synonyms:

  • HZ_PARTIES – the master entity table for persons, organizations, and groups.
  • HZ_RELATIONSHIPS – the relationship bridge between a subject party and an object party, supplying SUBJECT_ID, OBJECT_ID, and PARTY_RELATIONSHIP_TYPE.
  • HZ_PERSON_PROFILES – person-specific attributes such as phonetic name and known-as values.
  • HZ_ORGANIZATION_PROFILES – organization attributes such as DUNS number, fiscal year end, employee count, and revenue estimates.
  • HZ_ORG_CONTACTS – organization contact attributes including job title, decision-maker flag, department, and managed-by information.

The view text aliases HZ_PARTIES as PARTY for the base side and as SUB_PARTY and OBJ_PARTY for the subject and object sides, joining each back through HZ_RELATIONSHIPS and the relevant profile table. This structure allows a single query to return both the caller and the related account or contact in one row.

Key Columns

Common Use Cases and Queries

Typical scenarios include contact-center agent screens that must display a caller alongside the organization they belong to, data-migration extracts of customer relationships, and integration feeds to CRM or analytics platforms. A representative query is:

  • SELECT party_id, party_number, party_name, subject_id, object_id, party_relationship_type FROM csc_customer_response_v WHERE party_relationship_type = 'CONTACT_OF';
  • SELECT party_name, obj_party_name, duns_number FROM csc_customer_response_v WHERE party_type = 'PERSON' AND group_type = 'ORGANIZATION';
  • SELECT subject_id, object_id, known_as, job_title FROM csc_customer_response_v WHERE object_id = :p_org_party_id;

Because the view is a synonym-backed APPS object, it should be queried with the APPS credentials or through a synonym granted to the reporting schema. Performance is dominated by the underlying joins across HZ_RELATIONSHIPS and the profile tables, so filtering on PARTY_ID, SUBJECT_ID, or OBJECT_ID is recommended.