Search Results customer_cmpy

Overview

APPS.EGO_CUSTOMER_PEOPLE_V is a reporting and integration view in Oracle E-Business Suite that presents a consolidated, flattened picture of individual (person-type) customers who are linked to an FND application user and to a customer organization. It joins party, relationship, contact point, and user data so that downstream consumers — concurrent programs, Oracle Trading Community Architecture (TCA) inquiries, and custom integrations — do not have to reconstruct the multiplicity of joins themselves.

The view is particularly relevant to searches such as fax_contact: it is one of the few TCA-facing views that explicitly exposes the fax contact point attributes (country code, area code, number, and extension) alongside the corresponding telephone attributes. This makes it a convenient source for producing customer contact directories that include fax routing information.

Underlying Base Objects

Per the ETRM metadata, the view is owned by APPS and is defined over five referenced base objects, all accessed through public synonyms:

• FND_USER — supplies the application user identity, user name, e-mail address, user ID, and the person-to-party linkage.
• HZ_PARTIES — used twice, aliased as CUSTOMER_USER (the person party) and CUSTOMER (the organization party).
• HZ_RELATIONSHIPS — the EMPLOYEE_OF relationship between the person and the organization.
• HZ_CONTACT_POINTS — used twice, aliased as phone_contact and fax_contact, to retrieve telephone and fax data.
• HZ_CUST_ACCOUNTS — referenced through an EXISTS subquery to restrict the organization to active customer accounts.

Key Columns

The projection maps directly to the aliased source tables. The principal columns are:

• person_id / company_id — the party_id of the person and of the associated customer organization.
• user_name, user_id, email_address — from FND_USER, identifying the associated application user.
• person_name, company_name — the party names for the individual and the organization.
• person_title, person_prefix, person_first_name, person_middle_name, person_last_name, person_name_suffix — the decomposed person name components and title.
• phone_country_code, phone_area_code, phone_number, phone_extension — the telephone contact point attributes.
• fax_country_code, fax_area_code, fax_number, fax_extension — the fax contact point attributes, which are the columns most directly relevant to a fax_contact search.

Common Use Cases and Queries

A typical use case is extracting customer personnel with their fax details for a contact directory or a mass-fax integration. A representative query is:

• SELECT person_name, company_name, fax_country_code, fax_area_code, fax_number, fax_extension FROM apps.ego_customer_people_v WHERE fax_number IS NOT NULL;

Other common patterns include joining the view to FND_USER or HZ_CUST_ACCOUNTS for security and account-level filtering, or restricting by company_name to produce organization-specific contact lists. Because the view enforces person party type, active status, an active EMPLOYEE_OF relationship, an active customer account, and a valid FND user date range, results are already scoped to active, current associations. This built-in filtering simplifies query construction but also means the view cannot be used to retrieve historical or inactive relationships without querying the base tables directly.