Search Results g_ota_installed

Overview

APPS.OE_GLOBALS is a foundational PL/SQL specification package in Oracle Order Management (OE) that centralizes global constants, session-scoped variables, and shared utility routines used throughout the order entry and order management modules. It is not a business-facing API in the traditional sense; rather, it functions as a common repository of entity name literals, validation level codes, and environment variables that other OE packages and forms reference to avoid hard-coding values across the schema. The package header is stamped with a source control revision from 2008 and carries explicitly-marked generated sections ("START GEN entities"), indicating that portions of the specification are produced by a generator utility and must not be modified manually.

The package exposes 11 documented procedures and functions and is referenced by approximately 302 other packages, confirming its role as a widely-depended-upon utility layer within the E-Business Suite. In ETRM terms it is classified as an "OTHER" object rather than a formal public API.

Key Procedures and Functions

• GET_ENTITIES_TBL — Reserved generator routine used to avoid overriding or duplicating existing entity constants. The source comment explicitly states "DO NOT MODIFY."
• GET_APPLICATION_ID — Returns the application identifier associated with the order management context.
• INIT_CONTROL_REC — Initializes a control record structure used by the package's internal state handling.
• EQUAL — A generic comparison helper.
• SET_CONTEXT — Establishes the session/context values (such as org and language) required by dependent routines.
• CHECK_PRODUCT_INSTALLED — Determines whether a given Oracle product or feature is installed. This is the routine most directly related to the search term g_ota_installed: the "OTA" reference relates to Oracle's ordering/telemarketing-style product installation checks, and this procedure provides the packaged logic for verifying installation status at runtime.
• GET_FORCE_CLEAR_UI_BLOCK and SET_FORCE_CLEAR_UI_BLOCK — Accessor pair governing a flag that controls whether a UI block should be forcibly cleared, typically used by Oracle Forms front-ends during navigation or reset events.
• IS_SAME_CREDIT_CARD — Compares credit card information to determine whether two cards are equivalent, supporting payment-related validation in the order flow.

Tables Accessed

The package references three objects via APPS synonyms:

• FND_RESPONSIBILITY — Read to resolve responsibility context, which determines whether specific features or product installation checks apply to the current user's session.
• IBY_CREDITCARD — Read by IS_SAME_CREDIT_CARD to compare stored credit card records during payment validation.
• PLITBLM — A generic PL/SQL table type used by the OTA/order-entry stack for in-memory table handling.

Usage Notes

OE_GLOBALS is typically referenced indirectly rather than invoked directly by end users. Oracle Forms modules in Order Management call the context and UI-block routines during form initialization and navigation. Concurrent programs and other OE packages consume the entity constants and validation level values to maintain consistency across the order object model (header, line, adjustments, price attributes, reservations, lot/serial, and payment entities). Custom code extending Order Management commonly references OE_GLOBALS for the same entity literals and installation checks, which is why the package has such a broad reference footprint. Because key sections are generator-maintained, developers should treat the specification as read-only and never alter the auto-generated entity constants, as doing so risks breaking the many dependent packages that rely on them.