Search Results get_item_attr_control_level

Overview

APPS.EGO_UI_ITEM_PUB is a public PL/SQL package in Oracle E-Business Suite that serves as the item-definition API layer for the EGO (Product Information Management / Engineering) module. Declared with AUTHID CURRENT_USER and carrying the identifier G_BO_Identifier := 'EGO_ITEM', it exposes the business-object interface through which forms, concurrent programs, and custom code create, update, and query inventory items and their lifecycle information. The package adheres to the standard Oracle Application Object Library API conventions, reusing FND_API.g_RET_STS_SUCCESS, G_RET_STS_ERROR, G_RET_STS_UNEXP_ERROR, and the G_MISS_NUM/G_MISS_CHAR/G_MISS_DATE sentinel constants, so callers can use uniform return-status and missing-value handling.

Key Procedures and Functions

The package documents twelve public procedures and functions spanning lifecycle maintenance, item maintenance, and lookup utilities.

• PROCESS_ITEM — the primary entry point for creating or updating an item, dispatching to the appropriate lifecycle and attribute logic.
• PROCESS_ITEM_LIFECYCLE — updates the lifecycle and lifecycle phase of an existing item.
• CREATE_ITEM_LIFECYCLE — establishes lifecycle data for a newly created item.
• UPDATE_ITEM_LIFECYCLE — modifies lifecycle assignments on an existing item.
• UPDATE_ITEM_ATTR_EXT — updates extended (flexfield/attribute) item data for the EGO item entity.
• GET_MASTER_ORGANIZATION_ID — returns the master organization identifier used as the item-definition context.
• GET_ITEM_ATTR_CONTROL_LEVEL — retrieves the attribute control level governing where a given item attribute may be maintained.
• GET_ITEM_COUNT — returns a count of items matching the supplied criteria.
• GET_CATEGORY_ITEM_COUNT — the function relevant to the search term, returning the count of items assigned to a specified category. It is the API counterpart to the category-item count surfaced in the item-catalog user interface.
• GET_CATEGORY_HIERARCHY_NAMES — returns hierarchy names for one or more categories.
• SET_DEBUG_PARAMETERS — configures debug/logging behavior for subsequent API calls.

Tables Accessed

The package reads and writes through APPS synonyms. Item base and translated data reside in EGO_MTL_SY_ITEMS_EXT_B and EGO_MTL_SY_ITEMS_EXT_TL; flexfield context data resides in EGO_FND_DSC_FLX_CTX_EXT. Attribute values and templates are handled through MTL_ITEM_ATTRIBUTES, MTL_ITEM_TEMPLATES, and MTL_ITEM_TEMPL_ATTRIBUTES. Categorization logic relies on MTL_ITEM_CATEGORIES, MTL_CATEGORIES_KFV, MTL_CATEGORY_SET_VALID_CATS, and MTL_ITEM_CATALOG_GROUPS_B — the tables behind GET_CATEGORY_ITEM_COUNT and GET_CATEGORY_HIERARCHY_NAMES. Organization-level setup is read from MTL_PARAMETERS, revisions from MTL_ITEM_REVISIONS_B, and pending statuses from MTL_PENDING_ITEM_STATUS. Metadata about applications and business objects is obtained from FND_APPLICATION and FND_OBJECTS.

Usage Notes

Because this is a PUB-classified API, it is the supported integration point for external and custom code; direct DML against the underlying EGO and MTL tables is not recommended. The package is invoked primarily from the Product Information Management item-definition forms, but it is equally callable from concurrent programs, Oracle Workflow, and custom PL/SQL. Callers should pass a valid P_API_VERSION, honor the P_INIT_MSG_LIST and P_COMMIT flags, and branch on the returned status constants. ETRM records no dependent packages referencing this API, so its callers are external to the PL/SQL package layer — typically forms and custom extensions. DbLink-based or cross-schema calls are supported by the AUTHID CURRENT_USER declaration.