Results for “person_name_suffix”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The EGO_CUSTOMER_PEOPLE_V view resides in the APPS schema and belongs to the EGO - Advanced Product Catalog product family. It presents a consolidated, flat representation of customer personnel — specifically, active person parties who are registered as Oracle E-Business Suite users and who hold an employee relationship with a customer organization. In the context of the Advanced Product Catalog, this view supplies the identity, contact, and organizational context required for customer-facing catalog and collaborative commerce features, where users affiliated with customer organizations must be resolved to a single row containing personal, communication, and company attributes.

The view spans data drawn from the Trading Community Architecture (TCA) model and Oracle Application Object Library. It joins party records, relationship records, contact points, and FND user accounts, filtering out employees (internal users) so that only external customer contacts are returned. This makes it suitable for reporting, LOV definitions, and integration mappings where a denormalized customer contact record is preferred over querying multiple HZ tables directly.

Underlying Base Objects

Per the documented view metadata (ETRM 12.2.2), the view is defined over the following base objects, all referenced through public synonyms:

Effective-dated and outer-joined conditions (STATUS(+), START_DATE(+), END_DATE(+)) preserve person rows even where relationship or contact records are absent.

Key Columns

Common Use Cases and Queries

Typical scenarios include building customer contact listings, populating catalog collaboration recipients, and validating external user identities. A basic query returning prefixed names for a given customer organization follows:

  • SELECT person_prefix, person_first_name, person_last_name, company_name, email_address FROM apps.ego_customer_people_v WHERE company_name = :company;
  • SELECT person_id, user_name, person_name FROM apps.ego_customer_people_v WHERE person_prefix = :prefix;
  • SELECT company_name, COUNT(*) FROM apps.ego_customer_people_v GROUP BY company_name;

Because the view filters on active users and SYSDATE-bounded date ranges, results reflect only currently valid customer personnel, which is appropriate for operational reporting and integration extracts.