Search Results g_no_user_name_to_validate

Overview

APPS.EGO_CHANGE_USER_ATTRS_PUB is a public PL/SQL package body in the Oracle E-Business Suite Applications schema that supports the Oracle Product Information Management (PIM) / Engineering module's extensibility framework. Specifically, it manages user-defined attribute (UDA) values associated with engineering change orders and engineering change lines. The package provides the programmatic interface through which descriptive flexfield-style attribute data tied to user attribute groups is validated, persisted, and purged in the context of change management records such as those held in ENG_ENGINEERING_CHANGES and ENG_CHANGE_LINES. Its classification as a PUB package indicates it is the externally callable layer, delegating detailed row and column manipulation to the underlying EGO_USER_ATTRS_DATA_PUB and EGO_USER_ATTRS_DATA_PVT private packages, while returning standardized API status codes through FND_API and raising messages via FND_MSG_PUB and ERROR_HANDLER.

Key Procedures and Functions

The documented package exposes five entry points:

• PROCESS_CHANGE_USER_ATTRS_DATA — Primary driver that processes the supplied set of user attribute name/value pairs for a change record, coordinating validation and persistence.
• GET_CURRENT_DATA_SET_ID — Retrieves the currently active data set identifier, which the search term "eng_cua_data_set_id_s" relates to via the ENG_CUA_DATA_SET_ID_S sequence. This is used to tag rows written to the change user attribute interface with a consistent dataset key.
• PROCESS_CHANGE_USER_ATTRS — Handles user attribute processing at the change header level, applying attribute group associations resolved through EGO_OBJ_ATTR_GRP_ASSOCS_V.
• PROCESS_CHANGE_LINE_USER_ATTRS — Performs the equivalent attribute processing for individual change lines, writing through the ENG_CHG_USR_ATR_INTERFACE staging structure.
• CHECK_DELETE_ASSOCIATIONS — Validates whether delete operations against existing attribute associations are permitted, guarding referential integrity before removal.

No parameter signatures are documented in the ETRM metadata, so callers should obtain arguments from the package specification rather than inferring them.

Tables Accessed

The package reads and writes several core tables. EGO_IUA_DATA_SET_ID_S and ENG_CUA_DATA_SET_ID_S are sequences providing unique dataset identifiers for the EGO and Engineering change user-attribute subsystems respectively. ENG_ENGINEERING_CHANGES and its translated view ENG_CHANGE_LINES_VL, together with ENG_CHANGE_LINES, supply the parent change order context. ENG_CHG_USR_ATR_INTERFACE is the interface staging table into which attribute rows are inserted before validation and transfer to the base attribute tables. FND_FORM_FUNCTIONS and FND_USER provide function security and user context, while MTL_PARAMETERS supplies organizational defaults and DUAL/PLITBLM serve utility purposes.

Usage Notes

EGO_CHANGE_USER_ATTRS_PUB is typically invoked from the Oracle Engineering change order forms and from concurrent programs that import or purge user attribute data. Because it depends on FND_GLOBAL for session context (user, responsibility, organization), it should be called only after the application context is initialized via FND_GLOBAL.APPS_INITIALIZE. The package is not referenced by any other database object in the documentation, indicating it is an entry-point API rather than a shared utility, so custom extensions should call it directly rather than modifying its internals. Error handling follows the standard FND_API convention: callers should check the returned status and inspect FND_MSG_PUB for message details before committing.