Results for “employee_of”

50+ results




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

Overview

EGO_PEOPLE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the EGO — Advanced Product Catalog product family. As documented in the ETRM repository for releases 12.1.1 and 12.2.2, the view "contains the people information" and consolidates party, user, and contact records into a single denormalized rowset. Its principal purpose is to expose a unified directory of persons — internal employees, customers, and vendors — to Oracle Product Hub and other Advanced Product Catalog components that require consistent, cross-entity people data for ownership assignment, collaboration, item catalog administration, and workflow routing.

Within the EBS architecture, the view abstracts the complexity of Oracle's Trading Community Architecture (TCA) party model and Oracle HRMS person records, allowing callers to query a single object instead of joining HZ_PARTIES, FND_USER, HZ_RELATIONSHIPS, and PER_ALL_PEOPLE_F individually. Because EGO is a shared services product, this abstraction also insulates dependent forms, concurrent programs, and personalizations from underlying schema changes across 12.1.1 and 12.2.2.

Underlying Base Objects

The documented metadata lists the following referenced objects:

Several of these are surfaced as APPS synonyms (FND_USER, HZ_PARTIES, HZ_RELATIONSHIPS, HZ_CONTACT_POINTS, HZ_CUST_ACCOUNTS, PER_ALL_PEOPLE_F, PER_PHONES, AK_WEB_USER_SEC_ATTR_VALUES), while AR_LOOKUPS and PO_VENDORS are exposed as views.

Key Columns

  • PERSON_ID / PERSON_NAME — the TCA PARTY_ID and formatted party name for the person.
  • USER_NAME / USER_ID — the FND_USER credentials associated with the person, when an application account exists.
  • EMAIL_ADDRESS — derived by a CASE expression: HRMS email for internal employees, FND_USER email when no employee ID exists and the relationship defaults to EMPLOYEE_OF, otherwise the primary active HZ_CONTACT_POINTS email.
  • PERSON_TYPE — classifies the row as INTERNAL, CUSTOMER, or VENDOR based on employee ID, party match, and relationship code.
  • COMPANY_ID / COMPANY_NAME — the HZ_CUST_ACCOUNTS party context for the person's company.
  • PERSON_TITLE / PERSON_PREFIX — title resolved from AR_LOOKUPS CONTACT_TITLE, and prefix from PER_ALL_PEOPLE_F.
  • PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, PERSON_LAST_NAME, PERSON_NAME_SUFFIX — granular name attributes from HZ_PARTIES.
  • PHONE_COUNTRY_CODE — originating from PER_PHONES telephone data.

Common Use Cases and Queries

EGO_PEOPLE_V is typically used to populate people-of-interest lists in Product Hub, resolve collaboration recipients, and drive catalog security checks. A basic query retrieving all internal employees with email addresses is:

  • SELECT person_id, person_name, user_name, email_address FROM apps.ego_people_v WHERE person_type = 'INTERNAL';

To locate a person by login name or to confirm directory membership, query by USER_NAME or PERSON_NAME. Filtering on PERSON_TYPE = 'VENDOR' or 'CUSTOMER' is appropriate when building supplier or customer contact pickers. Because the view relies on effective-dated HRMS and TCA records, results are point-in-time as of SYSDATE, and rows may disappear if the employee or contact is no longer current. Join EGO_PEOPLE_V to HZ_PARTIES or FND_USER on PERSON_ID when additional party attributes are required, and avoid large unfiltered extracts, as the correlated subqueries against PER_ALL_PEOPLE_F and HZ_CONTACT_POINTS can be costly on high-volume TCA installations.