Search Results ego_groups_v




Overview
Explore in AI Chat

Overview

EGO_GROUPS_V is a read-only view defined in the APPS schema within the EGO - Advanced Product Catalog product module of Oracle E-Business Suite. Its documented purpose is straightforward: it contains all the Groups. In EBS terminology, a "group" is a distinct party type stored in the Trading Community Architecture (TCA) model — an organizational or collaborative grouping of entities rather than an individual person. EGO uses these groups for product catalog collaboration, item security, and access control structures.

The view functions as a simplified, purpose-built projection over the TCA party registry. Rather than exposing the full and often unwieldy HZ_PARTIES record, it narrows the result set to active group-type parties and renames the relevant attributes into group-centric column aliases. This makes it a convenient reporting and integration surface for forms, concurrent programs, and third-party interfaces that need group identity data without navigating the broader TCA schema.

The view is marked VALID in the ETRM metadata, and the underlying structure is identical in Oracle EBS 12.1.1 and 12.2.2 — no version-specific differences are documented.

Underlying Base Objects

The view is defined over a single referenced base object: HZ_PARTIES, accessed through a SYNONYM in the APPS schema. HZ_PARTIES is the central registry of parties, party relationships, and party sites within Trading Community Architecture. Because EGO_GROUPS_V references only this one table, it is a straightforward single-table view with no joins, unions, or aggregations.

The defining query filters that table as follows:

  • GRP.PARTY_TYPE = 'GROUP' — restricts the result set to parties classified as groups.
  • GRP.STATUS = 'A' — restricts to active parties.
  • OR GRP.PARTY_ID = -1000 — a special-case inclusion of party ID -1000, a seeded/system-level identifier that is retained regardless of type or status. Note that because of SQL operator precedence, the OR clause applies after the AND, so the literal exception row is always returned.

The column names exposed by the view are renamed from their TCA equivalents, isolating consumers from TCA naming conventions and shielding them from broader HZ_PARTIES structure changes.

Key Columns

  • GROUP_ID — Sourced from GRP.PARTY_ID. The unique identifier for the group; used as the foreign key in related EGO and TCA objects.
  • GROUP_NAME — Sourced from GRP.PARTY_NAME. The display name of the group as registered in TCA.
  • GROUP_DESCRIPTION — Sourced from GRP.MISSION_STATEMENT. This is the column most relevant to users searching on "group_description." It carries free-text descriptive content about the group's purpose or mandate.
  • GROUP_EMAIL_ADDRESS — Sourced from GRP.EMAIL_ADDRESS. The group's contact email address as held in TCA.
  • GROUP_OBJECT_VERSION_NUMBER — Sourced from GRP.OBJECT_VERSION_NUMBER. The optimistic locking version token, used by APIs and forms to detect concurrent updates.

Common Use Cases and Queries

Typical scenarios include group list-of-values lookups in AP Catalog forms, group-based security reporting, and integration extracts that feed group data to external collaboration systems.

  • Group description lookup for a known group:
    SELECT group_id, group_name, group_description FROM apps.ego_groups_v WHERE group_id = :p_group_id;
  • Search groups by description keyword:
    SELECT group_id, group_name, group_description FROM apps.ego_groups_v WHERE UPPER(group_description) LIKE '%' || UPPER(:keyword) || '%';
  • Full active group listing with contact email:
    SELECT group_name, group_email_address FROM apps.ego_groups_v ORDER BY group_name;

Because the view is not filtered to a single operating unit or responsibility, security is inherited from the caller's access to HZ_PARTIES and any TCA party-level security policies in effect. Queries should be qualified accordingly in multi-org reporting contexts.