Search Results hzca_obj




Overview
Explore in AI Chat

Overview

CSC_GS_CUSTOMERS_ORG_V is an APPS-owned reporting view within the Oracle E-Business Suite database. It exposes a consolidated, denormalized projection of customer organizations by joining customer account, party, and contact point data into a single queryable structure. The view is designed to present the full identity of a customer entity — account, party, contact points, and address — in one row per customer contact combination, eliminating the need for report developers and integration specialists to construct the multi-table joins themselves.

In Oracle EBS 12.1.1 and 12.2.2, this view is commonly associated with Customer Relationship Management (CRM) and Field Service style reporting where customer organizations must be retrieved alongside primary contact and communication details. The naming prefix CSC reflects its heritage in the Customer Service / Service application family, while the GS segment generally denotes a "Get/Select" style work view used as a selection source for concurrent programs, Discoverer worksheets, OAF pages, and integration extracts.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 lists three referenced base objects, all accessed through APPS synonyms: HZ_CONTACT_POINTS, HZ_CUST_ACCOUNTS, and HZ_PARTIES. These correspond to the core TCA (Trading Community Architecture) model introduced in EBS 11.5.10 and used throughout 12.1.1 and 12.2.2.

  • HZ_PARTIES (aliased hzp_obj) — the master entity record. Supplies party_id, party_name, party_number, party_type, group_type, and the person-name attributes (pre-name adjunct, first, middle, last). It also supplies the address columns address1 through address4, city, state, postal_code, province, and country.
  • HZ_CUST_ACCOUNTS (aliased hzca_obj) — the customer account layer. Supplies cust_account_id, account_number, and account_name, which link the party to a specific bill-to or ship-to customer role definition.
  • HZ_CONTACT_POINTS — aliased twice, as cont_ph for phone contact points and cont_em for email contact points. Supplies contact_point_id, phone_country_code, phone_area_code, phone_number, phone_extension, and phone_line_type.

The view therefore joins party to customer account and to the appropriate contact point rows, producing an object-centric ("obj_") column set suitable for downstream consumption.

Key Columns

Columns follow a consistent obj_ naming convention indicating the "customer object" being described:

  • obj_party_id / obj_party_name / obj_party_number / obj_party_type — party-level identity.
  • obj_cust_account_id / obj_account_number / obj_account_name — customer account identity.
  • obj_group_type — party group classification (e.g., organization versus person).
  • obj_title, obj_first_name, obj_middle_name, obj_last_name, obj_full_name — person name components, with full name concatenated.
  • obj_contact_point_id / obj_email_id — identifiers of the phone and email contact points respectively.
  • obj_phone_country_code, obj_phone_area_code, obj_phone_number, obj_phone_extension, obj_phone_type, obj_area_code_phone_number — phone details including a pre-formatted combined number.
  • obj_address1..4, obj_city, obj_state, obj_postal_code, obj_province, obj_country, obj_partial_address — address data with a semicolon-delimited partial address derived via nested DECODE.
  • obj_last_update_date, obj_cust_id_last_update_date, obj_cont_last_update_date, obj_email_last_update_date — audit timestamps per source entity, useful for incremental extracts.

Common Use Cases and Queries

This view is typically used for customer extracts, CRM dashboards, contact list generation, and data migration scripts where a flattened customer record is required.

  • Extracting all customer organizations with their primary contact and communication details.
  • Populating external CRM or marketing systems via concurrent programs.
  • Building BI Publisher or Discoverer reports on customer phone and email contacts.
  • Incremental synchronization based on the obj_last_update_date columns.

Sample query:

SELECT obj_party_number,
       obj_account_number,
       obj_account_name,
       obj_full_name,
       obj_area_code_phone_number,
       obj_phone_type,
       obj_city,
       obj_country
  FROM apps.csc_gs_customers_org_v
 WHERE obj_group_type = 'ORGANIZATION'
   AND obj_last_update_date >= SYSDATE - 30;

Because the view performs the TCA joins internally, callers should avoid adding redundant joins to HZ_PARTIES or HZ_CUST_ACCOUNTS unless additional attributes are required, as doing so may multiply rows where multiple contact points exist for a single party.