Search Results get_catalog_group_id

Overview

The APPS.EGO_ITEMCAT_VAL_TO_ID package is a shared value-to-ID conversion utility within the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 EGO (Item Catalog / Product Information Management) module. Its name reflects its core purpose: converting human-readable item catalog values or user-interface (UI) values into their corresponding internal numeric identifiers. The package is declared with AUTHID CURRENT_USER, meaning that it executes with the privileges of the invoking user, which requires careful attention to synonym and grant configuration in multi-schema environments.

According to the documented header comment, the package is explicitly described as a "Shared value-to-Id conversion package," confirming it as a reusable building block rather than a standalone business process driver. Its primary audience is internal EBS code such as validation routines and concurrent processing frameworks that must reconcile user-supplied catalog values against the underlying catalog definitions. The package was originally created in September 2002 by Rahul Chitko, with a later enhancement in October 2002 by Refai Farook adding the Get_Catalog_Group_Id procedure, indicating that the catalog group lookup was a subsequent and deliberated addition to the package's responsibilities.

The user search term "get_catalog_group_id" maps directly to the most prominent public function documented in this package, which is the entry point most developers and consultants encounter when working with it.

Key Procedures and Functions

The ETRM metadata documents three executable units within the package specification:

• EGO_ITEMCATALOG_UUI_TO_UI — This procedure supports conversion of an "unqualified/unique user interface" item catalog representation to the standard user-interface representation. It returns status information through an error-handling token table and a return status output, confirming that it participates in the standard EBS error-handling contract.
• EGO_ITEMCATALOG_VID — This procedure performs validation of item catalog data (VID denotes validation ID routine). It exposes the same x_Return_Status and x_Mesg_Token_Tbl output parameters used throughout the EGO API family to communicate success or failure and structured error messages.
• GET_CATALOG_GROUP_ID — This function accepts a catalog group name and an operation indicator, and returns a NUMBER. Per the documented header, it is used by entity validation procedures to perform duplicate checks. It converts the human-readable catalog group name into its internal unique identifier used as a foreign key elsewhere in the catalog schema.

The consistent use of Error_Handler.Mesg_Token_Tbl_Type across the output parameters demonstrates integration with the shared EBS error-handling framework.

Tables Accessed

The package reads from the following documented tables, accessed via APPS synonyms:

• MTL_ITEM_CATALOG_GROUPS_B — The base table storing item catalog group definitions. This is the primary source consulted by GET_CATALOG_GROUP_ID to resolve a name into an ID and to detect duplicates.
• MTL_ITEM_CATALOG_GROUPS_B_S — The corresponding sequence (or surrogate) object used to obtain or align surrogate keys for the base group table, supporting insert and identifier-generation logic.
• DUAL — The standard Oracle pseudo-table, used for scalar function evaluation and existence checks, typical in the duplicate-checking logic performed by the validation function.

Usage Notes

This package is typically invoked indirectly rather than called directly by end users. It is most commonly leveraged by entity validation logic inside the EGO catalog integration and PIM flows, and by custom code or concurrent programs that must resolve catalog group names to IDs before inserting data into catalog tables. Because it is referenced by at least one other package, care should be taken when modifying or replacing it, since dependency chains will be affected. The AUTHID CURRENT_USER declaration means the caller must have appropriate privileges on the referenced objects; custom callers should therefore ensure the necessary grants and synonyms exist. As with any EBS 12.2.2 API, it should not be modified directly, and its signature should be treated as stable across patches.