Search Results update_valueset_from_category

Overview

ENI_PROD_VALUESET is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, present in both 12.1.1 and 12.2.2 environments. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking session rather than the package owner, a common pattern for utility code that must respect the calling user's security context. Its header comment ($Header: ENIVSTPS.pls 115.0 2003/09/10) dates the source to 2003 and marks it "noship," indicating it was not shipped as part of the standard product line and is likely a customer-specific or internal extension. The documented API classification is OTHER, reflecting that it is not a registered Open Interface, public API, or concurrent-program entry point in the strict ETRM sense.

The package addresses a specific gap in Oracle's standard Oracle General Ledger and Inventory flexfield infrastructure: synchronizing an existing value set with values derived from product categories. Its single documented procedure, UPDATE_VALUESET_FROM_CATEGORY, rebuilds or refreshes value set content from MTL category data so that key flexfield segments used in inventory or product-related contexts remain aligned with category definitions.

Key Procedures and Functions

The ETRM metadata documents one procedure in this package:

• UPDATE_VALUESET_FROM_CATEGORY — the package's sole documented entry point. It carries the standard concurrent-program parameter signature (errbuf and retcode, both defined as OUT NOCOPY VARCHAR2), indicating it is designed to be registered and executed as a concurrent program or invoked by a host program expecting that calling convention. Its purpose is to populate or refresh a key flexfield value set from category data, bridging the Inventory category model and the General Ledger / Application Object Library value set model. No additional parameters are documented, so callers should not assume any input arguments beyond the standard concurrent request pair.

No functions or additional procedures are exposed in the documented metadata. The package specification is therefore narrow in scope and appears purpose-built for a single administrative task rather than general-purpose reuse.

Tables Accessed

The package operates across two functional areas, as evidenced by the tables referenced through APPS synonyms:

• Inventory category model: MTL_CATEGORIES_KFV (the key flexfield view over categories), MTL_CATEGORY_SETS_B (category set definitions), and MTL_CATEGORY_SET_VALID_CATS (the valid categories assigned to each category set). These supply the source values that drive the update.
• Flexfield value set model: FND_FLEX_VALUE_SETS, FND_FLEX_VALUES, FND_FLEX_VALUES_TL (the translatable value descriptions), FND_FLEX_VALUE_NORM_HIERARCHY, and FND_ID_FLEX_SEGMENTS (segment definitions). These identify the target value set, its existing values, their translated descriptions, and the segment to which the value set is attached.
• Staging: ENI_VSET_HRCHY_TEMP is a custom temporary table, presumably used to hold the derived value set hierarchy or a comparison set before it is applied to FND_FLEX_VALUES.
• Utilities: DBMS_UTILITY is referenced, commonly for COMMIT or formatting helpers during batch processing.

Usage Notes

Because UPDATE_VALUESET_FROM_CATEGORY uses the errbuf/retcode convention, the most likely invocation path is as a concurrent program registered in Application Object Library and submitted from the Inventory or General Ledger responsibility, or scheduled to run after category maintenance. It may also be called directly from custom PL/SQL that declares the two OUT parameters and checks retcode for success. The metadata records zero dependent packages, so removal or recompilation carries limited downstream risk.

Given the AUTHID CURRENT_USER declaration and the "noship" header, administrators should treat this package as an environment-specific extension: it exists in the ETRM-documented 12.2.2 metadata but is not a standard Oracle-delivered API, and its behavior depends on the category sets and value sets present in the target instance.