Search Results hzp_obj




Overview
Explore in AI Chat

Overview

APPS.CSC_GS_CUSTOMERS_GEN_V is a reporting view in the Oracle E-Business Suite Applications (APPS) schema that consolidates party, customer account, and contact point information into a single flattened result set. It is part of the CSC (Customer Care / Service) module family and is typically consumed by customer-facing search, telephony integration, and 360-degree customer views. The view exposes columns prefixed with obj_, indicating that the underlying record (party or customer account) is being presented as a generic "object" to the consuming UI or integration layer.

The object is catalogued in ETRM as a VIEW owned by APPS. In 12.1.1 and 12.2.2 the view definition is identical in structure, built against synonym references to the HZ (Trading Community Architecture) tables. It presents a denormalized, read-only projection suitable for lookup and display rather than for transactional updates.

Underlying Base Objects

ETRM documents three referenced base objects, all accessed through public synonyms in APPS:

  • HZ_PARTIES — aliased hzp_obj. Supplies the party identity: party_id, party_name, party_number, party_type, group_type, person name attributes, and address attributes (address1–address4, city, state, postal_code, province, country).
  • HZ_CUST_ACCOUNTS — aliased hzca_obj. Supplies the customer account identity: cust_account_id, account_number, account_name, and last_update_date.
  • HZ_CONTACT_POINTS — joined twice, aliased cont_ph (phone) and cont_em (email). Supplies contact_point_id, phone country/area code, phone number, extension, and line type, plus the respective last_update_date values.

The view therefore joins a party to its customer account and to its primary phone and email contact points, surfacing a single row per matching party/account combination.

Key Columns

  • obj_party_id, obj_party_name, obj_party_number, obj_party_type, obj_group_type — party identification and classification.
  • obj_cust_account_id, obj_account_number, obj_account_name — customer account identification.
  • obj_title, obj_first_name, obj_middle_name, obj_last_name, obj_full_name — person-name attributes; the full name is concatenated from first and last name.
  • obj_contact_point_id, obj_email_id — phone and email contact point identifiers.
  • obj_phone_country_code, obj_phone_area_code, obj_phone_number, obj_phone_extension, obj_phone_type, obj_area_code_phone_number — telephony attributes for dialing and display.
  • obj_address1–obj_address4, obj_city, obj_state, obj_postal_code, obj_province, obj_country, and obj_partial_address — a semicolon-delimited address assembly built with nested DECODE expressions.
  • obj_last_update_date, obj_cust_id_last_update_date, obj_cont_last_update_date, obj_email_last_update_date — audit timestamps used for synchronization and delta detection.

Common Use Cases and Queries

Typical scenarios include customer search and telephony screen-pop, where an agent is presented with a party, its account, and a dialable phone number; data-sync feeds that extract contact details and audit dates; and reporting on customer contact completeness.

SELECT obj_party_number,
       obj_party_name,
       obj_account_number,
       obj_full_name,
       obj_area_code_phone_number,
       obj_city,
       obj_country
  FROM apps.csc_gs_customers_gen_v
 WHERE obj_party_name LIKE :p_name
    OR obj_account_number = :p_acct;

For synchronization against a watermark, filter on the exposed update dates:

SELECT obj_party_id,
       obj_cust_account_id,
       obj_contact_point_id,
       obj_last_update_date
  FROM apps.csc_gs_customers_gen_v
 WHERE obj_last_update_date >= :p_since;

Because the view performs multiple joins and nested DECODE logic, queries should be constrained on indexed party or account columns where possible to avoid full scans.