Search Results eni_upgrade_vset




Overview
Explore in AI Chat

Overview

ENI_UPGRADE_VSET is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM API taxonomy as OTHER. Its header identifies it as part of the ENI module family, a legacy component associated with item categorization and value set upgrade operations. The package declaration uses AUTHID CURRENT_USER, meaning that its procedures and functions execute with the privileges of the invoking user rather than the definer, which is consistent with an administrative utility invoked under controlled upgrade conditions.

The business function of ENI_UPGRADE_VSET centers on migrating or rebuilding category set definitions from an existing value set hierarchy. In Oracle EBS, category sets govern how items are grouped for reporting, purchasing, and inventory purposes, while value sets and their hierarchies define valid values and parent-child relationships. The package provides the mechanism to translate a value set hierarchy into a category set structure, ensuring that categorization rules remain consistent after an upgrade or configuration change. Its presence in the 12.1.1 and 12.2.2 releases reflects the continued use of earlier ENI-era upgrade logic within the modern file system and Online Patching architecture.

Key Procedures and Functions

  • UPDATE_CATSET_FROM_VSET — The principal public procedure of the package. It performs the core operation of populating or refreshing category set data based on a specified value set hierarchy. Based on the metadata, it accepts parameters including a top node that scopes the portion of the hierarchy to process and a validation mode that controls how strictly the input is checked before updates are applied. It follows the standard concurrent program calling convention, returning an error buffer and return code so that it can be invoked from a concurrent manager or a batch script. It is the entry point used when category set definitions must be derived from value set structures during an upgrade or data migration.
  • ENI_VALIDATE_SETUP — A function that returns a numeric result. It validates the setup prerequisites required by UPDATE_CATSET_FROM_VSET, allowing callers to confirm that the environment is properly configured before attempting the heavier update operation. The numeric return typically encodes a success or failure status that invoking code can test.

No additional procedures or functions beyond these two are documented in the ETRM metadata, and the package references no other packages within APPS.

Tables Accessed

  • ENI_VSET_HRCHY_TEMP — A temporary staging table holding the value set hierarchy rows that serve as the source for the upgrade.
  • MTL_CATEGORIES_B — The base table for category definitions; category rows are created or updated here.
  • MTL_CATEGORY_SETS_B — Stores category set headers, which the procedure aligns with the incoming value set hierarchy.
  • MTL_CATEGORY_SET_VALID_CATS — Holds the association between a category set and its valid categories; this mapping is populated from the value set data.
  • MTL_ITEM_CATEGORIES — Assigns items to categories; referenced to maintain or verify item-to-category associations after the category set is rebuilt.
  • DUAL — Used for scalar evaluations and validation queries within the package logic.

Usage Notes

ENI_UPGRADE_VSET is a utility package rather than a general-purpose API. It is not referenced by any other package in APPS, indicating it is invoked directly — typically from a concurrent program registered during an upgrade or from a one-off SQL*Plus or custom script executed by a system administrator. The presence of errbuf and retcode parameters on UPDATE_CATSET_FROM_VSET confirms that the intended invocation path is a concurrent program, allowing the operation to be submitted, monitored, and logged through the standard concurrent manager framework. The ENI_VALIDATE_SETUP function should be called first to confirm that staging data and setup records are complete before the update procedure is run.

Because the package is classified as OTHER and carries a 2003 header, it should be treated as an internal, legacy utility. Direct invocation in a production 12.1.1 or 12.2.2 environment should be limited to controlled upgrade scenarios, preceded by a full backup of the affected category and item category tables, and ideally performed under an Oracle Support–approved migration plan.