Search Results obj_cust_id_last_update_date




Overview
Explore in AI Chat

Overview

CSC_GS_CUSTOMERS_ORG_V is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CSC (Customer Care) product family. Its documented status is VALID across the 12.1.1 and 12.2.2 releases. Per the ETRM metadata, the view exists to support the search operation on customer information within the Contact Center form, exposing a denormalized, flattened projection of party, customer account, and contact point data that the Customer Care UI can query directly rather than assembling joins at runtime.

Because it is a view and not a table, it carries no storage of its own and always reflects the current state of the underlying Oracle Trading Community Architecture (TCA) entities. This makes it suitable both for the interactive Contact Center search flow and for read-only reporting or integration queries that need customer identity, address, phone, and email attributes in a single row. The object name carries the CSC module prefix, indicating it is a Customer Care–specific construct rather than a general-purpose TCA view. The alias convention used in the view text, where party, account, and contact point columns are prefixed OBJ_, reflects the search block's naming convention in the form.

Underlying Base Objects

The documented referenced base objects are HZ_PARTIES, HZ_CUST_ACCOUNTS, and HZ_CONTACT_POINTS, each accessed through APPS synonyms. HZ_PARTIES supplies the party-level attributes, including PARTY_ID, PARTY_NAME, PARTY_NUMBER, PARTY_TYPE, GROUP_TYPE, the person-name components, and the address and location columns. HZ_CUST_ACCOUNTS supplies the account-level attributes, namely CUST_ACCOUNT_ID, ACCOUNT_NUMBER, and ACCOUNT_NAME. HZ_CONTACT_POINTS supplies the contact point identifiers used for phone and email, aliased as CONT_PH and CONT_EM respectively, together with phone country code, area code, number, extension, and line type.

The view aliases the party source as HZP_OBJ and the account source as HZCA_OBJ. Because all three sources are TCA entities, the view sits directly on the standardized customer model shared across Oracle EBS modules, which is why CSC can reuse it for the Contact Center search without maintaining a private copy of customer data.

Key Columns

The column set falls into three functional groups, each prefixed OBJ_. The user's search term, obj_party_id, corresponds to the first column in the view text, defined as HZP_OBJ.PARTY_ID OBJ_PARTY_ID, the primary identifier of the party record and the natural key for linking back to HZ_PARTIES.

OBJ_PARTIAL_ADDRESS is built with nested DECODE logic that concatenates ADDRESS1 through ADDRESS4 with semicolon separators, skipping null segments. The per-source LAST_UPDATE_DATE columns support incremental refresh or change-detection logic downstream.

Common Use Cases and Queries

The primary use case is the Contact Center search operation, where an agent enters partial customer data and the form queries the view. A representative lookup by party identifier is:

SELECT obj_party_id, obj_party_name, obj_party_number, obj_account_number, obj_city, obj_state FROM csc_gs_customers_org_v WHERE obj_party_id = :p_party_id;

Name-based search is equally common, using the concatenated full name or last name:

SELECT obj_party_id, obj_full_name, obj_account_number, obj_phone_number FROM csc_gs_customers_org_v WHERE UPPER(obj_full_name) LIKE UPPER(:p_search_name) || '%';

Because OBJ_PARTY_ID is the TCA party key, the view is frequently used to join search results back to other TCA or CSC objects, as in:

SELECT v.obj_party_id, v.obj_account_number FROM csc_gs_customers_org_v v WHERE v.obj_cust_account_id = :p_cust_account_id;

Reporting and integration scenarios leverage the same flattened projection to extract customer contact details without writing multi-table TCA joins. Queries should always filter on indexed underlying columns where possible, and callers should be aware that a single party may appear in multiple rows where multiple contact points exist.