Search Results bom_rtg_globals




Overview
Explore in AI Chat

Overview

BOM_RTG_GLOBALS is a global state-management package body in the APPS schema that supports the Oracle Bills of Material and Engineering routing infrastructure. Its primary business function is to hold session-scoped routing context — organization, entity, user, login, concurrent program, and ECO identifiers — in PL/SQL package-level variables for the duration of a routing or ECO-processing transaction. This pattern allows multiple procedures across the BOM routing APIs to share consistent context without repeatedly re-querying the database or passing large parameter lists between calls.

In Oracle EBS 12.1.1 and 12.2.2, the package is classified as OTHER and is not an externally published API. It is an internal support package that is called by other BOM routing components rather than directly by end users.

Key Procedures and Functions

The documented interface exposes 93 procedures and functions. The most prominent are setters and getters organized around the session context:

Additional setter/getter pairs follow the same convention, exposing attributes such as program ID and other routing state. Together they form an in-memory context object scoped to the database session.

Tables Accessed

The package body references the following tables through APPS synonyms:

The dependencies list also shows calls into FND_API, FND_GLOBAL, FND_MSG_PUB, and ERROR_HANDLER, indicating that the package participates in the standard EBS API error-handling and messaging framework.

Usage Notes

BOM_RTG_GLOBALS is not intended for direct invocation by end users or forms. It is invoked indirectly by other BOM routing components: the ETRM documentation records that 35 other packages reference it, while it is not referenced by any database object itself, confirming its role as a shared internal utility. Typical callers include routing creation and update APIs, ECO processing routines, and concurrent programs that perform bulk routing maintenance. Custom code should avoid modifying package state unless it follows the standard setter/getter sequence, because the variables are session-persistent and can affect subsequent calls in the same session. All access should respect the organization and user context established by FND_GLOBAL.