Search Results ego_validate_catalog_group




Overview
Explore in AI Chat

Overview

EGO_VALIDATE_CATALOG_GROUP is a PL/SQL validation package owned by the APPS schema in Oracle E-Business Suite. It belongs to the EGO (Electronic Commerce/Product Information Management) product family and is classified under the ETRM metadata as an "OTHER" API rather than a public or private interface. Its business purpose is to enforce the integrity of item catalog group definitions used by Oracle Product Information Management and Oracle iProcurement catalog administration. Catalog groups represent logical collections of items that share common attributes — for example, "Purchasing," "Order Entry," or user-defined groups — and are stored in the MTL_ITEM_CATALOG_GROUPS hierarchy. Before a catalog group can be created, updated, deleted, or referenced by item assignment, the requesting operation must be validated against business rules governing existence, access privileges, required attributes, and entity state. EGO_VALIDATE_CATALOG_GROUP provides that centralized validation layer, ensuring callers such as EGO_ITEM_CATALOG_PVT receive consistent error handling instead of duplicating checks across the EGO API surface. The package status is recorded as VALID in the current ETRM release.

Key Procedures and Functions

The documented package exposes six program units, all of which are validation routines rather than data-manipulation entry points:

  • CHECK_EXISTENCE — Confirms that a referenced catalog group record exists in the repository before downstream logic proceeds.
  • CHECK_ACCESS — Verifies that the calling context, user, or responsibility is permitted to operate on the specified catalog group.
  • CHECK_ATTRIBUTES — Validates attribute-level values supplied for a catalog group, ensuring they conform to permitted definitions.
  • CHECK_REQUIRED — Enforces that mandatory fields or relationships are populated for the catalog group being processed.
  • CHECK_ENTITY — Performs entity-level validation, typically on insert or update, confirming the overall catalog group entity satisfies structural rules.
  • CHECK_ENTITY_DELETE — Applies deletion-specific validation, confirming that the catalog group may be removed without violating referential or business constraints.

Each routine relies on the standard ERROR_HANDLER dependency for consistent error messaging, and parameter lists are deliberately withheld here because the ETRM metadata does not publish them.

Tables Accessed

The package operates against the following base tables, reached through APPS synonyms:

  • MTL_ITEM_CATALOG_GROUPS — the primary catalog group definition table; read for existence, attribute, and delete checks.
  • MTL_ITEM_CATALOG_GROUPS_B — the base (non-translated) catalog group table, consulted for canonical definitions.
  • MTL_SYSTEM_ITEMS_B — referenced to determine item membership and to enforce that deletion or modification does not break assigned items.
  • DUAL — a utility dependency used for lightweight PL/SQL evaluation patterns.

Usage Notes

EGO_VALIDATE_CATALOG_GROUP is an internal validator, not a user-facing API. It is invoked indirectly by EGO_ITEM_CATALOG_PVT, the primary item-to-catalog assignment API, and is also referenced by itself, indicating recursive or nested validation. This means it is triggered during catalog administration flows in Oracle iProcurement, Oracle Purchasing, and Product Information Management forms, as well as by any custom code that routes through EGO_ITEM_CATALOG_PVT. Because the package is APPS-owned and classified OTHER, Oracle does not guarantee its signature across patches or upgrades. Custom developers should not call EGO_VALIDATE_CATALOG_GROUP directly; instead they should invoke the higher-level EGO_ITEM_CATALOG_PVT API, which encapsulates these validation steps and preserves upgrade safety. This package provides no concurrent program entry point and should never be scheduled independently.