Search Results is_ego_installed

Overview

EGO_COMMON_PVT is a private PL/SQL utility package in the APPS schema that supports the Oracle E-Business Suite product information and change management infrastructure. It is classified as a PVT (private) API, meaning it is intended for internal use by other EGO-family packages rather than as a public integration interface. The package consolidates several cross-cutting helper routines that are shared across the Product Information Management (PIM) and change management modules, including product installation detection, product schema resolution, user organization context profile handling, and change-order cleanup when inventory items are deleted. Because it is bound with AUTHID CURRENT_USER, the package executes with the privileges of the calling session, so callers must possess the appropriate grants on the underlying EGO and FND objects. In EBS 12.1.1 and 12.2.2 the package remains a foundational, low-level component invoked implicitly by higher-level APIs such as BOM_DELETE_GROUPS_API, and it is referenced by nine other packages in the ETRM metadata.

Key Procedures and Functions

The documented API surface consists of six routines:

• IS_EGO_INSTALLED — A function that verifies whether the EGO (product information) module is installed in the current environment, returning a status indicator as a VARCHAR2.
• GET_PROD_SCHEMA — A function that resolves and returns the database schema name associated with a given product name.
• SAVE_USR_ORG_CTX_PROF_VAL — A procedure that updates the profile value EGO_USER_ORGANIZATION_CONTEXT for the current user. It returns S on success and U on failure, with an accompanying message describing any error; it only operates against the expected profile option identifier.
• CANCEL_NIR_FOR_DELETE_ITEM — A procedure that invokes the change management process to cancel any New Item Request (NIR) associated with an item being deleted. It is designed to be called from BOM_DELETE_GROUPS_API.INVOKE_EVENTS.
• GET_OPTION_VALUE — A function that retrieves a configuration option value from the EGO default options store. This is the routine most relevant to the user's search and is the canonical internal accessor for EGO option settings.
• WRITE_DIAGNOSTIC — A utility procedure used to emit diagnostic information, typically for debugging and logging during package execution.

Tables Accessed

The package reads and writes three documented tables through APPS synonyms:

• EGO_DEFAULT_OPTIONS — Stores default option values for the EGO product; read by GET_OPTION_VALUE to supply configuration settings to dependent code.
• FND_PRODUCT_INSTALLATIONS — The standard Applications installation registry; queried by IS_EGO_INSTALLED and GET_PROD_SCHEMA to determine installation status and owning schema.
• FND_PROFILE_OPTIONS — The profile option definition table; used by SAVE_USR_ORG_CTX_PROF_VAL to validate the profile option identifier before persisting the user's organization context value.

Usage Notes

As a private package, EGO_COMMON_PVT is not exposed through standard EBS forms or concurrent programs directly. It is invoked from within other server-side PL/SQL, notably change management and bill-of-materials deletion flows. Developers writing custom extensions who need to read EGO option settings or check EGO installation status may call these routines, but should treat them as internal interfaces subject to change across releases. Because execution is subject to the caller's privileges (AUTHID CURRENT_USER), grants on EGO_DEFAULT_OPTIONS, FND_PRODUCT_INSTALLATIONS, and FND_PROFILE_OPTIONS are prerequisites. Custom code should not assume the profile-handling routine writes arbitrary profile options; it is scoped to the EGO user organization context only. In 12.1.1 and 12.2.2, the behavior described above is consistent, though the header indicates an earlier baseline release, so callers should confirm signature compatibility against the target instance.