Search Results g_bo_level

Overview

The APPS.BOM_RTG_ERROR_HANDLER package is a specialized error-handling utility within the Oracle E-Business Suite Bills of Material (BOM) and Routing application modules. Its primary business function is to decouple the Routing (RTG) business object from the broader BOM business object by providing a dedicated, self-contained mechanism for capturing, classifying, and reporting errors that arise during routing-related operations. As documented in the package header comments, the LOG_ERROR procedure for the Routing business object was deliberately migrated out of the general ERROR_HANDLER package into this standalone unit, so that routing business logic could be maintained independently of BOM logic while still delegating underlying error-handling work to the shared Error Handler functions.

The package was originally authored in January 1999 (Masanori Kimizuka) and carries a header revision identifier reflecting maintenance through 2002. It remains a component of the routing business object API stack in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents a single public procedure:

• LOG_ERROR — The central error-logging entry point for the Routing business object. It records an error condition encountered during routing processing and delegates the actual persistence and message resolution to the shared Error Handler package functions. It is the procedure users reach when searching for "log_error" in this context, and it is the mechanism by which routing operations register warnings, errors, and fatal conditions.

Although not enumerated as callable APIs in the documented procedure list, the package specification defines an extensive set of named constants that drive LOG_ERROR behavior. These include business-object level constants (for example, the BOM level, ECO level, revision level, routing-item level, routing-component levels, standard-operation level, routing level, operation level, resource level, standard-resource level, and network level), status codes (W warning, U unexpected, E error, F fatal, N not picked), and scope indicators (A all, R record, S siblings, C children). These constants let callers identify precisely where in the routing hierarchy an error originated and how broadly it should be treated.

Tables Accessed

The documented table reference for this package is the synonym PLITBLM. This is the PL/SQL internal message table used by the EBS error-handling framework to resolve and store message text. LOG_ERROR writes the diagnostic content associated with a logged error into this structure so that messages can be retrieved and displayed to the user or consumed by downstream processing. No routing master or bill-of-material base tables are referenced directly by this package; persistence of the business error is handled through the Error Handler delegation described in the header notes.

Usage Notes

BOM_RTG_ERROR_HANDLER is an internal infrastructure package rather than a user-facing API. It is not invoked from standard forms menus or from concurrent program definitions directly. Instead, it is called programmatically by the Routing business object procedures whenever those procedures detect an exception, validation failure, or unexpected condition and need to register the error with a consistent status and scope.

The ETRM metadata indicates the package is referenced by four other packages, confirming its role as a shared dependency in the routing PL/SQL call graph. Because it is declared AUTHID CURRENT_USER, it executes with the privileges of the invoking schema, so callers must hold appropriate grants on the underlying message table. Customizations that extend routing error handling should call this package rather than duplicating logic, and developers should rely exclusively on the defined status and level constants to preserve compatibility with the Error Handler framework across EBS 12.1.1 and 12.2.2.