Search Results pty_postal_code




Overview
Explore in AI Chat

Overview

APPS.CSC_GS_CUSTOMERS_ORG_ADV_V is a Customer Care (CSC) module database view in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to support the search operation on customer information within the Contact Center form, providing a flattened, denormalized projection of TCA (Trading Community Architecture) party, customer account, contact point, and address data that the Contact Center search UI consumes in a single query.

Functionally, the view consolidates registry data held in HZ_PARTIES and HZ_CUST_ACCOUNTS with contact information from CSC_GS_CONTACTS_V and relationship data from HZ_RELATIONSHIPS, translating coded values through AR_LOOKUPS. Because the Contact Center operator typically searches by name, account number, or contact details, a single view that returns all relevant attributes reduces the round trips otherwise required against multiple TCA tables. The view is marked VALID and is owned by APPS, consistent with standard EBS seeded objects. Users searching for sub_party_id will find that the view exposes party and account identifiers (PTY_PARTY_ID, PTY_CUST_ACCOUNT_ID) rather than a column literally named SUB_PARTY_ID; the sub-party concept maps through HZ_RELATIONSHIPS and CSC_GS_CONTACTS_V, where a contact or related party is linked to the primary party.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced objects:

  • HZ_PARTIES (synonym) — the registry of parties; supplies party name, number, type, group type, person name components, and address attributes.
  • HZ_CUST_ACCOUNTS (synonym) — customer account header; supplies CUST_ACCOUNT_ID, ACCOUNT_NUMBER, and ACCOUNT_NAME.
  • HZ_RELATIONSHIPS (synonym) — party-to-party and party-to-account relationships, which underlie the sub-party linkage used by Contact Center search.
  • CSC_GS_CONTACTS_V (view) — the Customer Care contacts view supplying contact point IDs, email, and phone attributes.
  • AR_LOOKUPS (view) — Receivables lookup values used to decode coded columns such as phone line type and party/account classifications.

These objects are joined on party and account identifiers, producing an outer, search-oriented result set rather than a normalized relational model.

Key Columns

Common Use Cases and Queries

Typical usage includes Contact Center agent search, customer 360 reporting, and integration feeds that require party, account, and contact data in one row. A representative query follows:

  • SELECT PTY_PARTY_ID, PTY_PARTY_NAME, PTY_ACCOUNT_NUMBER, PTY_FULL_NAME, PTY_AREA_CODE_PHONE_NUMBER FROM APPS.CSC_GS_CUSTOMERS_ORG_ADV_V WHERE UPPER(PTY_PARTY_NAME) LIKE :search_term;
  • SELECT PTY_CUST_ACCOUNT_ID, PTY_ACCOUNT_NAME FROM APPS.CSC_GS_CUSTOMERS_ORG_ADV_V WHERE PTY_ACCOUNT_NUMBER = :acct_no;
  • Incremental extraction based on PTY_LAST_UPDATE_DATE or PTY_CUST_ID_LAST_UPDATE_DATE.

When a search requires the sub-party association explicitly, join the view to HZ_RELATIONSHIPS on HZP_PTY.PARTY_ID to resolve subordinate or related party identifiers.