Search Results obj_city




Overview
Explore in AI Chat

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, APPS.CSC_GS_CUSTOMERS_GEN_V is a Customer Care (CSC) module view that provides a denormalized, search-oriented projection of customer (party) and customer account information. Its documented purpose is to support the customer search operation performed within the Contact Center form. Rather than requiring the form or a downstream report to join party, account, and contact point tables at runtime, the view pre-assembles the most commonly searched and displayed attributes into a single flattened result set.

The view is flagged as VALID and is owned by the APPS schema, which is consistent with ETRM standards for seed data objects shipped with the Customer Care product. The prefixes in the column aliases — OBJ_ for the primary customer/party entity and CONT_ for contact points — reflect a generic "object" abstraction used by the Contact Center framework to present heterogeneous searchable entities through a common interface. The result set is therefore consumed primarily by the Contact Center UI and any custom inquiry screens or reports that need a fast, wide customer lookup.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over three documented base objects, all exposed as APPS synonyms:

  • HZ_PARTIES — the TCA (Trading Community Architecture) master table for parties: persons, organizations, and groups. In the view text this is aliased HZP_OBJ.
  • HZ_CUST_ACCOUNTS — the TCA customer account table linking a party to one or more customer accounts. Aliased HZCA_OBJ.
  • HZ_CONTACT_POINTS — the TCA contact point table storing phone, email, and other contact mechanisms. Referenced twice in the view text, aliased CONT_PH (phone/contact point) and CONT_EM (email contact point), so that phone and email attributes can be selected side-by-side.

Because these are TCA tables, the view inherits TCA semantics for party and account identity, and remains consistent with the 12.1.1 / 12.2.2 data model. The synonyms resolve to the underlying HZ tables in the APPS schema, with no intermediate custom tables introduced.

Key Columns

The view exposes a wide set of columns. Notable groups include:

The OBJ_PARTY_NUMBER column in particular surfaces the TCA party number and is the field relevant to callers searching on obj_party_number.

Common Use Cases and Queries

The primary use case is Contact Center customer search and the resulting display of a matched customer. A typical lookup filters on party number or name:

  • Search by party number: SELECT obj_party_id, obj_party_name, obj_party_number, obj_account_number, obj_full_name FROM csc_gs_customers_gen_v WHERE obj_party_number = :p_party_number;
  • Search by partial name: SELECT obj_party_id, obj_full_name, obj_account_number, obj_phone_number FROM csc_gs_customers_gen_v WHERE obj_party_name LIKE :p_name || '%';
  • Display contact details for a selected account: SELECT obj_full_name, obj_email_id, obj_country_code, obj_phone_number, obj_partial_address FROM csc_gs_customers_gen_v WHERE obj_cust_account_id = :p_cust_account_id;
  • Inquiry/reporting freshness check: SELECT obj_party_number, obj_last_update_date, obj_cont_last_update_date FROM csc_gs_customers_gen_v WHERE obj_party_id = :p_party_id;

Because the view is not unique on party, it may return one row per matching account/contact-point combination; consumers should expect effective duplicates for multi-account or multi-phone parties and de-duplicate on OBJ_PARTY_ID or OBJ_CUST_ACCOUNT_ID as appropriate. Extensive ad hoc querying against the full view should be bounded with selective predicates, since the underlying joins across HZ_PARTIES, HZ_CUST_ACCOUNTS, and HZ_CONTACT_POINTS can generate large intermediate result sets.