Search Results eng_globals




Overview
Explore in AI Chat

Overview

APPS.ENG_GLOBALS is a foundational PL/SQL package body within the Oracle E-Business Suite Engineering (ENG) module. It serves as the central runtime state manager and utility layer for Engineering Change Order (ECO) processing and engineering item revision handling. The package encapsulates session-level globals, system parameter caching, request queuing mechanics, and approval validation logic used throughout the engineering change workflow. Because it is classified as an OTHER API and is referenced by twenty-five other packages, ENG_GLOBALS functions less as a callable business API and more as an internal service package consumed by ECO forms, concurrent programs, and dependent PL/SQL units. It is documented as VALID in both the 12.1.1 and 12.2.2 releases, and the ETRM metadata confirms it is not referenced by any database object, indicating it is invoked strictly at the application layer.

Key Procedures and Functions

The package exposes seventy-four documented procedures and functions. Several groupings are evident from the naming conventions:

Tables Accessed

The package reads and writes through APPS synonyms across the engineering and bills-of-material schemas:

Usage Notes

ENG_GLOBALS is invoked internally rather than directly by end users. Typical invocation paths include:

  • Engineering change order forms — ECO and revised item forms call the initialization routines at form startup and use the validation and approval procedures during save and submit actions.
  • Concurrent programs — ECO mass processing and revision propagation concurrent requests use the request-table procedures to stage and consume work items.
  • Dependent packages — twenty-five packages reference ENG_GLOBALS, implying it acts as a shared state and utility provider across the engineering module.
  • Custom extensions — custom code extending ECO functionality should treat ENG_GLOBALS as a supporting layer, calling initialization routines explicitly and honoring the cached global records rather than duplicating them.

Because the package caches session state, callers should ensure INIT routines execute before dependent procedures are invoked, and request tables are cleared between processing cycles.