Search Results g_opr_create

Overview

EGO_GLOBALS is a specification-only package (a PL/SQL package without a body of executable business logic) that resides in the APPS schema and serves as the central declaration repository for the Oracle E-Business Suite Product Information Management (PIM) and Item Catalog module. Introduced during the initial 11.5.9/12.0 development cycle — the source header credits Rahul Chitko with initial creation in September 2002, with a minor revision by lkapoor in June 2005 — the package provides a single, consistent set of constants, exception definitions, record types, and session-level variables shared across the EGO (Engineering/Product Information Management) family of packages. Its classification in ETRM is "OTHER," reflecting that it is a utility/declaration package rather than a business API.

The core purpose of EGO_GLOBALS is to eliminate duplicated literals and ad-hoc exception handling across the many catalog and item business-object packages. By centralizing values such as operation codes ('CREATE', 'UPDATE', 'DELETE', 'LOCK', 'CANCEL'), record-found indicators, business-object identifiers ('ITM' for Item, 'CAT' for Catalog), and entity identifiers like 'ITEM_CATALOG_GROUP', EGO_GLOBALS enforces consistent semantics across the module.

Key Procedures and Functions

• SET_LANGUAGE_CODE — Stores the current session language code in a global variable so that subsequent calls within the same session use a consistent NLS setting.
• GET_LANGUAGE_CODE — Returns the language code previously established by SET_LANGUAGE_CODE.
• SET_USER_ID — Caches the current application user identifier for reference by other EGO packages.
• GET_USER_ID — Retrieves the cached user identifier.
• GET_BO_IDENTIFIER — Returns the business-object identifier (for example, ITM or CAT) associated with the current processing context, allowing generic code to distinguish between item and catalog operations.
• TRANSACTION_TYPE_VALIDITY — Evaluates whether a given transaction type is valid for the current business-object context, supporting the validation logic used by the import and catalog maintenance flows.

The specification additionally declares operation constants (G_OPR_CREATE, G_OPR_UPDATE, G_OPR_DELETE, G_OPR_LOCK, G_OPR_CANCEL, G_OPR_NONE), record-status constants (G_RECORD_FOUND, G_RECORD_NOT_FOUND), the entity constant G_ITEM_CATALOG_GROUP with level G_ITEM_CATALOG_GROUP_LEVEL, a suite of severity/skip exception declarations (G_EXC_SEV_QUIT_OBJECT, G_EXC_QUIT_IMPORT, G_EXC_FAT_QUIT_BRANCH, and related), shared catalog group record and table variables based on EGO_ITEM_CATALOG_PUB types, and the SYSTEM_INFORMATION_REC_TYPE record.

Tables Accessed

The ETRM metadata documents no direct table references for EGO_GLOBALS. As a declaration and session-state package, it does not perform DML against application tables; instead it holds in-memory record structures (G_CATALOG_GROUP_TBL, G_CATALOG_GROUP_REC, G_OLD_CATALOG_GROUP_REC) typed from the EGO_ITEM_CATALOG_PUB package. Any persistence occurs in the calling packages that consume these globals.

Usage Notes

EGO_GLOBALS is referenced by seven other packages within the EGO module and is not intended to be invoked directly from Oracle Forms or concurrent programs. Custom code extending PIM, item catalog, or item import functionality should reference its constants rather than hard-coding literals, and should call SET_USER_ID and SET_LANGUAGE_CODE early in the session to seed the globals expected by downstream EGO APIs. Because it is a specification-only package, it is not schema-specific in behavior and remains consistent across EBS 12.1.1 and 12.2.2.