Search Results developer_debug

Overview

APPS.EGO_UI_ITEM_PUB is a public PL/SQL package body that provides the programmatic backbone for the Oracle E-Business Suite item definition user interface, primarily within the Product Information Management (PIM) and Advanced Product Catalog modules. Its business purpose is to expose a set of callable APIs that drive the item lifecycle as presented to end users: creating items, updating items and their attribute extensions, copying items between contexts, and retrieving master organization and attribute control information. The package operates on the EGO_ITEM object name (G_OBJECT_NAME) and distinguishes its transactional modes through constants such as CREATE, UPDATE, and COPY. It relies on the FND_GLOBAL session context (user id and concurrent login id) and captures a single system date (G_Sysdate) at entry so that all comparisons, inserts, and updates within a transaction use a consistent timestamp. The header identifier EGOITUIB.pls and the version string indicate this is a long-standing component carried forward across EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes twelve documented procedures and functions, unified by the item lifecycle workflow:

• PROCESS_ITEM_LIFECYCLE — the primary entry point coordinating the overall item lifecycle operation.
• CREATE_ITEM_LIFECYCLE — drives the creation of a new item through its lifecycle stages.
• UPDATE_ITEM_LIFECYCLE — drives updates to an existing item across its lifecycle stages.
• UPDATE_ITEM_ATTR_EXT — updates extended item attribute values beyond the core item record.
• GET_MASTER_ORGANIZATION_ID — returns the master organization identifier for item definition purposes.
• GET_ITEM_ATTR_CONTROL_LEVEL — returns the control level governing a given item attribute.
• SET_DEBUG_PARAMETERS — configures debugging behavior; related to the developer_debug helper visible in the source and the msg_line_no variable used for developer tracing. This is directly relevant to the search term "developer_debug".
• PROCESS_ITEM — performs the underlying item processing invoked by the lifecycle procedures.
• GET_ITEM_COUNT — returns a count of items matching the supplied criteria.
• GET_CATEGORY_ITEM_COUNT — returns a count of items assigned within a category.
• GET_CATEGORY_HIERARCHY_NAMES — retrieves category hierarchy names for item categorization.

Tables Accessed

The package reads and writes a defined set of EBS item and catalog tables accessed through APPS synonyms. Item master data is handled through EGO_MTL_SY_ITEMS_EXT_B and EGO_MTL_SY_ITEMS_EXT_TL, supplemented by MTL_SYSTEM_ITEMS_B (referenced in the org_item_exists_cur cursor). Attribute and descriptive flexfield data are managed via MTL_ITEM_ATTRIBUTES, EGO_FND_DSC_FLX_CTX_EXT, FND_OBJECTS, and FND_APPLICATION. Categorization logic uses MTL_CATEGORIES_KFV, MTL_CATEGORY_SET_VALID_CATS, MTL_ITEM_CATEGORIES, and MTL_ITEM_CATALOG_GROUPS_B. Revision, template, and lifecycle-support data rely on MTL_ITEM_REVISIONS_B, MTL_ITEM_TEMPLATES, MTL_ITEM_TEMPL_ATTRIBUTES, MTL_PARAMETERS, and MTL_PENDING_ITEM_STATUS. Collectively these support item validation, attribute application, category assignment, and status tracking.

Usage Notes

EGO_UI_ITEM_PUB is typically invoked from the item definition forms and related PIM user interfaces, and can be called from concurrent programs or custom PL/SQL that must replicate standard item lifecycle behavior. Because it is classified as a PUBLIC API (PUB), it is a supported integration surface, though the ETRM record notes it is referenced by zero other packages, meaning it is generally consumed directly by forms or client code rather than by other APIs. For "developer_debug" investigations, SET_DEBUG_PARAMETERS together with the internal developer_debug routine and msg_line_no variable control diagnostic output; the source comments indicate debug line numbering should be disabled when the package is archived. All calls execute under the invoking session's FND_GLOBAL user and login context.