Results for “ego_catalog_group_util”

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

Overview

EGO_CATALOG_GROUP_UTIL is a utility package owned by the APPS schema in Oracle E-Business Suite and classified in the ETRM repository as a UTIL (utility) object. Its functional scope is tied to the EGO product family, which supports the Catalog Management and item cataloging features of Oracle EBS, particularly the maintenance of item catalog groups used to classify and organize items for browsing and ordering. As a specification-only package (the ETRM excerpt reproduces the package spec, EGOUCAGS.pls), EGO_CATALOG_GROUP_UTIL exposes a small, focused set of entry points that orchestrate the query and write operations against the catalog group base and translation tables. The package header carries a header revision of 120.1 dated 2005/06/29, with initial creation attributed to Rahul Chitko on 20-SEP-2002, indicating that the utility has been a stable part of the EGO foundation since the earlier 11i releases and continues to be shipped in 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented specification exposes two procedures, both defined with standard EBS OUT parameters for error handling and status signaling. Neither procedure returns a value, and the metadata should be consulted rather than assumed for exact parameter lists.

• Query_Row — Populates the caller with the catalog group row data required for display or validation. It is intended for read access to the catalog group definition, returning the requested row together with the standard message token table and return status used across EGO utilities to communicate errors and warnings.
• Perform_Writes — Commits the create, update, or delete changes applied to the catalog group records. It is the write-side counterpart to Query_Row and likewise returns the standard message token table and return status for error handling.

Both procedures follow the EGO convention of declaring the message token table and return status as OUT NOCOPY parameters, allowing the caller to inspect the outcome after invocation without additional queries. No other procedures or functions are documented in the ETRM metadata for this package.

Tables Accessed

The package references three tables through APPS synonyms, each with a distinct role in the catalog group data model:

• MTL_ITEM_CATALOG_GROUPS_B — The base table holding the catalog group definition. Query_Row reads from it and Perform_Writes performs the corresponding inserts, updates, or deletes.
• MTL_ITEM_CATALOG_GROUPS_TL — The translation table storing language-specific catalog group names and descriptions. It supplies the user-facing text returned by Query_Row and receives translated values during Perform_Writes.
• FND_LANGUAGES — The Oracle Application Object Library table of installed languages, consulted to resolve the language context for the translated attributes and to align the returned text with the caller's session language.

Usage Notes

As a UTIL-classified package, EGO_CATALOG_GROUP_UTIL is not typically called directly by end users. It is invoked from higher-level EGO forms, concurrent programs, and other PL/SQL packages that manage catalog groups. The ETRM metadata records that the package is referenced by two other packages, confirming its role as a shared building block rather than a top-level API. The conventional invocation pattern is to call Query_Row to load the catalog group row, apply modifications in the calling layer, and then call Perform_Writes to persist them, with the returned message token table and return status used to drive error messages on the form or in the concurrent program log. Because the procedures are documented as passing OUT parameters, callers should treat the return status as the authoritative success indicator and inspect the message tokens when it indicates failure. Customizations that extend catalog group maintenance should reuse this utility rather than writing directly to the base and translation tables, so that language handling and error propagation remain consistent. Developers should verify the exact parameter signatures against the deployed package spec for the specific 12.1.1 or 12.2.2 instance, as the ETRM excerpt provides the structure of the spec rather than the full body.