Search Results is_master_org

Overview

INV_EBI_UTIL is a utility package in the APPS schema that supports the Oracle E-Business Suite product information management and bill of materials integration layer, commonly known as the EBI (Enterprise Business Intelligence) or item management integration infrastructure. Classified as a UTIL package within the ETRM documentation, it provides shared helper routines consumed by other packages rather than exposing an end-user-facing API. Its principal responsibilities include determining whether the Product Information Management (PIM) module is installed, resolving master organization context, transforming user-defined attribute (UDA) data between the interface structures used by Oracle Inventory and the attribute tables used by item and structure management, reading configuration parameters, and centralizing error and debug handling.

The package declares a suite of constants that identify the object model it participates in: EGO_ITEMMGMT_GROUP, ENG_CHANGEMGMT_GROUP, BOM_STRUCTUREMGMT_GROUP, and BOM_COMPONENTMGMT_GROUP, along with level identifiers such as CHANGE_LEVEL, STRUCTURES_LEVEL, and COMPONENTS_LEVEL. These values tie the package directly to the item, engineering change, BOM structure, and BOM component management workflows. The reference to BOM_COMPONENTS as an object name (G_BOM_COMPONENTS_OBJ_NAME) is directly relevant to searches for "bom_components," indicating that this package participates in the component-level processing of bill of materials structures.

Because it is declared with AUTHID CURRENT_USER, the package executes with the privileges of the calling schema, an important consideration for customizations that invoke it from outside APPS.

Key Procedures and Functions

• IS_PIM_INSTALLED — Boolean function that reports whether the Product Information Management module is installed, allowing callers to conditionally enable PIM-dependent logic.
• IS_MASTER_ORG — Overloaded VARCHAR function that validates whether a given organization, identified by either organization ID or organization code, is a master organization.
• GET_MASTER_ORGANIZATION — Returns the master organization identifier corresponding to a supplied organization ID.
• TRANSFORM_UDA — Converts an inv_ebi_uda_input_obj into the EGO user attribute row and data tables, supporting UDA propagation into item and structure management.
• TRANSFORM_ATTR_ROWDATA_UDA — Performs the inverse transformation, rebuilding an inv_ebi_uda_input_obj from EGO attribute row and data tables.
• GET_CONFIG_PARAM_VALUE — Retrieves a configuration parameter value from a supplied name/value table.
• GET_ERROR_TABLE and GET_ERROR_TABLE_MSGTXT — Return the error table name and its associated message text, supporting standardized error reporting.
• GET_APPLICATION_ID — Resolves the application identifier used to scope concurrent or profile context.
• PUT_NAMES — Populates name information, typically for message or context construction.
• DEBUG_LINE — Emits debug output governed by the module-level G_DEBUG flag.
• SETUP and WRAPUP — Establish and tear down the FND message and context environment surrounding a processing call.
• SET_APPS_CONTEXT — Sets the APPS session context required for correct multi-organization and security behavior.

Tables Accessed

The package reads reference and setup data through APPS synonyms: FND_APPLICATION resolves application IDs; FND_PROFILE_OPTION_VALUES supplies profile values such as the master organization; FND_USER and FND_RESPONSIBILITY_TL provide user and responsibility names used in messaging; MTL_PARAMETERS provides inventory organization parameters, including the master organization flag; EGO_FND_DSC_FLX_CTX_EXT supports descriptive flexfield context handling for UDA transformation; and PLITBLM is the standard FND message table used for error text.

Usage Notes

INV_EBI_UTIL is referenced by six other packages and is not normally called directly. It is invoked from within the item management, engineering change, BOM structure, and BOM component management flows, where callers use SETUP, perform transformations and master-organization checks, then call WRAPUP. Custom code should use it only for master-organization resolution, UDA transformation between the INV_EBI and EGO structures, and consistent error or debug formatting. The package is present in both 12.1.1 and 12.2.2; the header revision (120.7.12010000.4, dated 2009) indicates that its core logic is stable across these releases.