Search Results hzp_pty




Overview
Explore in AI Chat

Overview

APPS.CSC_GS_CUSTOMERS_V is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments that exposes a consolidated, denormalized picture of customer parties, their customer accounts, and associated contact points. The name follows the CSC_GS_ naming convention associated with the Customer Care / Service (CSC) schema, where "GS" views are typically built to support governed search, lookup, and integration scenarios across the Trading Community Architecture (TCA) model. Rather than forcing consumers to join HZ_PARTIES, HZ_CUST_ACCOUNTS, and contact-point tables manually, the view pre-joins them and prefixes derived columns with a pty_ alias to indicate party-level context. The searched term "hzp_pty" reflects the internal table alias applied to HZ_PARTIES within the view definition, from which party attributes such as party_id, party_name, and party_number are projected.

Underlying Base Objects

The documented ETRM metadata records the following referenced base objects:

  • HZ_PARTIES (SYNONYM) — aliased as hzp_pty; the primary source of party identity, name, type, and address attributes.
  • HZ_CUST_ACCOUNTS (SYNONYM) — aliased as hzca_pty; supplies customer account identifiers, account number, and account name.
  • HZ_RELATIONSHIPS (SYNONYM) — provides the relationship linkage used to associate parties with their customer account context.
  • CSC_GS_CONTACTS_V (VIEW) — aliased as cont_pty; contributes contact-point data such as email, phone, and telephone type.
  • AR_LOOKUPS (VIEW) — the standard Oracle Receivables lookup source, commonly joined to translate coded values such as phone type into meaningful display values.

Because the base objects are accessed through APPS synonyms, the view resolves to the underlying TCA tables (HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_RELATIONSHIPS) at runtime.

Key Columns

The view projects a wide set of party and account attributes. Notable columns include:

  • pty_party_id, pty_party_name, pty_party_number, pty_party_type, pty_group_type — core party identification and classification.
  • pty_cust_account_id, pty_account_number, pty_account_name — customer account context for the party.
  • pty_title, pty_first_name, pty_middle_name, pty_last_name, pty_full_name — person-name components, with pty_full_name concatenating first and last names.
  • pty_contact_point_id, pty_email_id, pty_phone_country_code, pty_phone_area_code, pty_phone_number, pty_phone_extension, pty_phone_type — contact-point details from CSC_GS_CONTACTS_V.
  • pty_area_code_phone_number — derived concatenation of area code and phone number.
  • pty_partial_address and pty_address1 through pty_address4, pty_city, pty_state, pty_postal_code, pty_province, pty_country — nested DECODE logic builds a semicolon-delimited partial address while retaining individual address elements.
  • pty_last_update_date, pty_cust_id_last_update_date, pty_cont_last_update_date, pty_email_last_update_date — audit timestamps supporting incremental extracts.

Common Use Cases and Queries

The view is typically used for customer master extracts, contact-list reporting, and integration feeds that require party, account, and contact data in a single result set.

  • Customer directory reporting: SELECT pty_party_name, pty_account_number, pty_full_name, pty_email_id, pty_phone_number FROM apps.csc_gs_customers_v ORDER BY pty_party_name;
  • Contact lookup by name: SELECT pty_party_id, pty_full_name, pty_partial_address FROM apps.csc_gs_customers_v WHERE UPPER(pty_full_name) LIKE '%SMITH%';
  • Incremental extract for integration: SELECT pty_party_id, pty_account_number, pty_last_update_date FROM apps.csc_gs_customers_v WHERE pty_last_update_date >= :last_run_date;

Because the view joins multiple TCA objects, queries returning large result sets should filter on indexed identifiers such as pty_party_id or pty_account_number and avoid unbounded scans.