Search Results oe_globals




Overview
Explore in AI Chat

Overview

The APPS.OE_GLOBALS package body is a foundational utility package within the Oracle E-Business Suite Order Management (OE) module. In Oracle EBS 12.1.1 and 12.2.2, it serves as a centralized repository for session-level global variables, environment initialization routines, and shared helper logic used throughout the Order Management application stack. The package abstracts access to frequently required context values — such as the application identifier, the current responsibility, and user-driven UI state — so that numerous dependent packages and forms do not each need to re-derive them independently. Its status is documented as VALID in the ETRM metadata, and it is classified as an OTHER API, indicating it is a supporting internal utility rather than a documented public business interface. Despite its utility role, its influence is extensive: the metadata records that OE_GLOBALS is referenced by 302 other database objects, making it one of the most widely depended-upon packages in the Order Management schema.

Key Procedures and Functions

The package exposes eleven documented procedures and functions. Their purposes are as follows:

  • GET_ENTITIES_TBL — Returns a collection of entity definitions used by Order Management processing logic.
  • GET_APPLICATION_ID — Retrieves the Oracle EBS application identifier, allowing callers to obtain the correct application context without hardcoding.
  • INIT_CONTROL_REC — Initializes the package's internal control record, establishing default global state at the start of a session or processing cycle.
  • EQUAL — Performs an equality comparison, typically used to validate whether two control or configuration records are equivalent.
  • SET_CONTEXT — Establishes the runtime context (application, responsibility, and related session attributes) required by dependent Order Management code.
  • CHECK_PRODUCT_INSTALLED — Determines whether a specific Oracle product or module is installed, enabling conditional logic across feature sets.
  • GET_FORCE_CLEAR_UI_BLOCK — Retrieves the flag governing whether a UI block should be forcibly cleared, supporting form behavior control.
  • SET_FORCE_CLEAR_UI_BLOCK — Sets that same flag, permitting forms to request that a block be cleared on the next interaction.
  • IS_SAME_CREDIT_CARD — Compares credit card data to determine whether two records refer to the same card, supporting payment validation logic.

These routines collectively manage context, configuration, UI state, and credit card comparison, reinforcing the package's role as shared infrastructure.

Tables Accessed

The ETRM metadata documents three tables accessed through APPS synonyms:

  • FND_RESPONSIBILITY — The Oracle Application Object Library responsibility definition table. It is read to resolve and validate the current responsibility and its associated application context during context initialization.
  • IBY_CREDITCARD — The Oracle Payments credit card table. It supports the IS_SAME_CREDIT_CARD comparison logic.
  • PLITBLM — A PL/SQL index-by table used as a bind/collection mechanism within the package body.

Usage Notes

OE_GLOBALS is invoked primarily from Order Management forms and from other Order Management PL/SQL packages, most notably through OE_MSG_PUB and OE_DEBUG_PUB debugging and messaging flows. The package declares dependencies on FND_API, FND_MESSAGE, MO_GLOBAL, IBY_SECURITY_PKG, and FND_INSTALLATION, confirming that it is designed to participate in the standard EBS context, messaging, and security frameworks. Because it is not referenced by any database object in return, it sits near the bottom of the dependency hierarchy and should be treated as a low-level utility. Custom code may call its initialization and context routines to align with standard Order Management behavior, but developers should be aware that its interface is not a documented public API and is subject to change across releases.