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:
- HZ_PARTIES — the master TCA party record providing party identifiers, names, and person name components.
- FND_USER — application user accounts supplying USER_NAME, USER_ID, EMAIL_ADDRESS, EMPLOYEE_ID, and PERSON_PARTY_ID used in classification logic.
- HZ_RELATIONSHIPS — party relationships, supplying RELATIONSHIP_CODE and the related PARTY_ID used for contact point resolution.
- HZ_CONTACT_POINTS — email and phone contact points filtered by owner table, contact point type, active status, and primary flag.
- PER_ALL_PEOPLE_F — the HRMS employee datelist, used for email address, prefix, and current-employee validation (CURRENT_EMPLOYEE_FLAG / CURRENT_NPW_FLAG).
- PER_PHONES — telephone information for person records.
- HZ_CUST_ACCOUNTS — customer account context, contributing COMPANY_ID and COMPANY_NAME.
- PO_VENDORS (view) — vendor/supplier records that participate in party relationships.
- AR_LOOKUPS (view) — Receivables lookup values, resolving CONTACT_TITLE meanings from PERSON_PRE_NAME_ADJUNCT.
- AK_WEB_USER_SEC_ATTR_VALUES — web user security attribute values used in the catalog security model.
- DUAL — Oracle's single-row dummy table, used in the CASE expression to return literal strings.
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.
-
View: EGO_PEOPLE_V 12.1.1
This view contains the people information
APPS.EGO_PEOPLE_V·↳ AK_WEB_USER_SEC_ATTR_VALUES·↳ AR_LOOKUPS·↳ FND_USER·Explore EGO module →
-
VIEW: APPS.EGO_PEOPLE_V 12.1.1
-
VIEW: APPS.EGO_PEOPLE_V 12.2.2
-
View: EGO_PEOPLE_V 12.2.2
This view contains the people information
APPS.EGO_PEOPLE_V·↳ AK_WEB_USER_SEC_ATTR_VALUES·↳ AR_LOOKUPS·↳ FND_USER·Explore EGO module →
-
View: AHM_BILLING_INFO_V 12.1.1
This view gives the detail for the Party Billing Information like Billing Address, City, Country etc.
Not implemented in this database·Explore AHM module →
-
View: AHM_BILLING_INFO_V 12.2.2
This view gives the detail for the Party Billing Information like Billing Address, City, Country etc.
Not implemented in this database·Explore AHM module →
-
View: AMW_PERSON_COMPANY_V 12.2.2
View for person's company.
Not implemented in this database·Explore AMW module →
-
View: EGO_PERSON_COMPANY_V 12.2.2
View contains Person to Company information
APPS.EGO_PERSON_COMPANY_V·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore EGO module →
-
View: AMW_PERSON_COMPANY_V 12.1.1
View for person's company.
APPS.AMW_PERSON_COMPANY_V·↳ HZ_FORMAT_PUB·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore AMW module →
-
View: PA_XC_KEY_MEMBERS_V 12.1.1
View All Key Members
Not implemented in this database·Explore PA module →
-
View: PA_XC_PROJECT_PEOPLE_V 12.1.1
View List of People for a Specified Project
Not implemented in this database·Explore PA module →
-
View: PA_XC_KEY_MEMBERS_V 12.2.2
View All Key Members
Not implemented in this database·Explore PA module →
-
View: PV_PARTNER_CONTACTS_V 12.1.1
APPS.PV_PARTNER_CONTACTS_V·↳ HZ_ORG_CONTACTS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore PV module →
-
VIEW: APPS.AMS_ORG_EMPS_V 12.1.1
-
View: OKX_PARTY_CONTACTS_V 12.2.2
Party contacts
APPS.OKX_PARTY_CONTACTS_V·↳ HZ_ORG_CONTACTS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore OKX module →
-
View: EGO_PERSON_COMPANY_V 12.1.1
View contains Person to Company information
APPS.EGO_PERSON_COMPANY_V·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore EGO module →
-
View: PV_PARTNER_CONTACTS_V 12.2.2
APPS.PV_PARTNER_CONTACTS_V·↳ HZ_ORG_CONTACTS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore PV module →
-
Not implemented in this database·Explore PV module →
-
View: AHM_ADMIN_INFO_V 12.1.1
This view gives following Subscriber Adminstrator and contact information that is captured at the time of Registration.1. User Name2. First Name3. Last Name4. Title5. Email Address6. Phone Number7. Party Numberetc.
Not implemented in this database·Explore AHM module →
-
View: PA_XC_PROJECT_PEOPLE_V 12.2.2
View List of People for a Specified Project
Not implemented in this database·Explore PA module →