Search Results create_catalog_group

Overview

EGO_ITEM_CATALOG_PUB is a public PL/SQL API package in the APPS schema that supports Oracle E-Business Suite's Product Information Management (PIM) item catalog functionality. Its principal business purpose is to manage the definition, creation, update, and structural validation of item catalog groups—the logical groupings that classify items so that catalog administrators, buyers, and self-service users can browse, search, and constrain items within a specific catalog structure. The package belongs to the EGO (Engineering/Product Information) module family and is classified as a PUB (public) API, meaning it is intended to be called from external code, concurrent programs, and forms rather than being an internal implementation detail.

The package is version-tolerant across EBS 12.1.1 and 12.2.2; the metadata confirms its object status as VALID and its ownership by the APPS schema. It is part of a broader ecosystem: nine other packages reference it (including EGO_CATALOG_GROUP_UTIL, EGO_DEFAULT_CATALOG_GROUP, EGO_UPLOAD_PUB, and EGO_VALIDATE_CATALOG_GROUP), while it in turn depends on FND_API and FND_FLEX_EXT as well as the SYS STANDARD package. This dependency graph places EGO_ITEM_CATALOG_PUB as a foundational catalog-group service consumed by higher-level catalog utilities and validation routines.

Key Procedures and Functions

The documented API surface contains six procedures/functions:

• PROCESS_CATALOG_GROUPS — the bulk-level entry point; drives processing of multiple catalog groups in a single invocation, typically used by concurrent request logic that must handle sets of groups at once.
• PROCESS_CATALOG_GROUP — the single-record counterpart that processes one catalog group instance end-to-end.
• CREATE_CATALOG_GROUP — inserts a new item catalog group definition, establishing the catalog structure and its associated attributes.
• UPDATE_CATALOG_GROUP — modifies an existing catalog group, including its descriptive and structural characteristics.
• CHECK_DELETE_ATTRGROUP_ASSOC — a validation routine that determines whether an attribute-group association may be deleted, enforcing referential and business-rule constraints before destructive action.
• LOCK_ROW — acquires a row-level lock on the relevant catalog group record to guarantee concurrency safety during creation and update operations.

Parameter lists are not documented in the ETRM excerpt and are not reproduced here; callers should consult the package specification source or integration documentation for signatures. The naming pattern follows Oracle's standard PUB API conventions: CREATE/UPDATE verbs for DML operations and CHECK/LOCK prefixes for validation and concurrency control. The presence of FND_API as a dependency indicates the package likely participates in a standard API error-handling and return-status model.

Tables Accessed

The package reads and writes several core PIM and Oracle common tables through APPS synonyms:

• MTL_ITEM_CATALOG_GROUPS_B and MTL_ITEM_CATALOG_GROUPS_TL — the base and translation tables holding the catalog group header definitions and their language-specific descriptions.
• EGO_MTL_CATALOG_GRP_VERS_B — stores catalog group version information, supporting revision-controlled catalog structures.
• EGO_CAT_GRP_TEMPLATES — catalog group templates supplying predefined structural layouts for new groups.
• EGO_PAGE_ENTRIES_B — page-entry metadata that governs how catalog content renders in the user interface.
• EGO_FND_DSC_FLX_CTX_EXT — descriptive flexfield context extensions used to attach catalog group attributes.
• FND_APPLICATION, FND_OBJECTS, and FND_NEW_MESSAGES — Oracle Application Object Library tables used for application registration, object metadata, and message resolution.

Usage Notes

EGO_ITEM_CATALOG_PUB is typically invoked from PIM catalog administration forms, from concurrent programs that bulk-create or refresh catalog groups, and from custom extensions that programmatically maintain catalog structures. Because it is a PUB package, it is the supported integration point—custom code should call these procedures rather than performing direct DML against MTL_ITEM_CATALOG_GROUPS_B or EGO_MTL_CATALOG_GRP_VERS_B. Callers should observe the standard FND_API commit/rollback contracts and should invoke LOCK_ROW before updates to avoid concurrency conflicts. In 12.2.2 the Online Patching (adop) model requires that any invocations respect editioning and should be routed through the standard runtime for the appropriate edition. Testing is strongly advised prior to deployment to production, and the row counts in the MTL and EGO catalog tables should be assessed for batch-sizing considerations.