Search Results ego_upgrade_user_attr_val_pub




Overview
Explore in AI Chat

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

Overview

The APPS.EGO_UPGRADE_USER_ATTR_VAL_PUB package is a public (PUB-classified) PL/SQL API belonging to the Oracle E-Business Suite extensibility and attribute-management layer, commonly associated with the Product Information Management (PIM) and Item Catalog functionality within Oracle EBS 12.1.1 and 12.2.2. Its primary business purpose is to support upgrade and post-installation data migration activities that establish default user-defined attribute values across item categories. Specifically, the package provides a mechanism to seed or default attribute values for all categories that belong to the default category set of a given functional area, ensuring that previously defined or newly introduced user attributes are consistently populated following an upgrade or patch application.

The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the package owner, so callers must possess the appropriate privileges on the underlying catalog and attribute tables.

Key Procedures and Functions

The package exposes a single documented public procedure:

  • UPGRADE_CAT_USER_ATTRS_DATA — Performs the defaulting of attribute values for all categories within the default category set of a functional area. The procedure accepts parameters that identify the functional area whose default category set is being processed (p_functional_area_id), the attribute group type to process, and the specific attribute group name. When the attribute group name is passed as NULL, the procedure processes all attribute groups associated with the specified attribute group type. Standard API-style OUT parameters report the outcome of the call, including return status, error code, message count, and message data, and an API version parameter defaults to 1.0.

The procedure operates in bulk across all relevant categories rather than on a single category, making it suited to upgrade-driven mass defaulting rather than transactional maintenance.

Tables Accessed

The package reads and writes data across several documented catalog tables, referenced through APPS synonyms:

  • MTL_DEFAULT_CATEGORY_SETS — identifies the default category set associated with the functional area supplied to the procedure.
  • MTL_CATEGORY_SETS_B — supplies the base definition of the category set being processed.
  • MTL_CATEGORY_SET_VALID_CATS — provides the list of valid categories belonging to that category set, which drives the set of categories for which attribute values are defaulted.
  • EGO_PRODUCT_CAT_SET_EXT — the extensibility table holding category-set-related attribute metadata used to determine which user attributes require defaulting.

Together these tables allow the procedure to resolve the target categories and the attribute definitions before applying the defaulted values.

Usage Notes

This API is intended for controlled upgrade and data-seeding scenarios rather than day-to-day user transactions. It is typically invoked by upgrade driver scripts, patch routines, or concurrent programs that run automatically after the attribute framework and category structures have been migrated. Custom code may call it when implementing its own upgrade logic or when re-establishing default user attribute values after structural changes to categories or attribute groups. Because it affects all categories in a functional area's default category set, it should be executed during planned maintenance windows with proper validation of the functional area identifier and attribute group filters. Callers should always inspect the returned status and message data to confirm successful completion, and the procedure should be tested in a non-production environment before being applied to critical catalogs.