Results for “get_eco_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

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:

• Initialization routines — INIT_SYSTEM_INFO_REC, INIT_CONTROL_REC, INIT_WHO_REC, INIT_WHO_REC_ENTITY_DETAILS, and INIT_PROCESS_NAME establish the cached global records (system information, control block context, WHO columns, and the active process name) at the start of an engineering session.
• Request queue management — ADD_REQUEST, GET_REQUEST_STATUS, GET_UNPROCESSED_REQUEST, and CLEAR_REQUEST_TABLE manage a transient request table used to stage and track ECO or revision processing work items.
• Approval and validation — CHECK_APPROVED_FOR_PROCESS, SET_REQUEST_FOR_APPROVAL, TRANSACTION_TYPE_VALIDITY, ECO_CANNOT_UPDATE, and GET_ECO_ASSEMBLY_TYPE enforce business rules governing whether a change order or assembly may proceed.
• Change type resolution — GET_PLM_OR_ERP_CHANGE distinguishes PLM-originated from ERP-originated change records.
• System information accessors — GET_SYSTEM_INFORMATION, SET_SYSTEM_INFORMATION, SET_BILL_SEQUENCE_ID, and GET_BILL_SEQUENCE_ID provide read/write access to cached parameters and bill sequence identifiers.
• Process name accessors — GET_PROCESS_NAME retrieves the process context established during initialization.

Tables Accessed

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

• Engineering change tables — ENG_ENGINEERING_CHANGES, ENG_CHANGE_ORDER_TYPES, ENG_CHANGE_TYPE_PROCESSES, ENG_REVISED_ITEMS, and ENG_REVISED_OPERATIONS support change order definition, type classification, and revised item/operation tracking.
• BOM and routing tables — BOM_OPERATIONAL_ROUTINGS, BOM_OPERATIONAL_ROUTINGS_S, BOM_OPERATION_RESOURCES, BOM_OPERATION_SEQUENCES, and BOM_SUB_OPERATION_RESOURCES are consulted when revised operations touch routing structures.
• Inventory and item tables — MTL_SYSTEM_ITEMS, MTL_PARAMETERS, and MTL_RTG_ITEM_REVISIONS provide item master and organization parameter context.
• Utility references — DUAL and PLITBLM are used for scalar evaluation and PL/SQL table handling.

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.