Results for “get_entity_message”

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

Overview

APPS.BOM_INVOKE_RTG_BO is a PL/SQL package in the Oracle E-Business Suite Applications schema that serves as a Business Object (BO) wrapper for the routing functionality of Oracle Bills of Material. Its name follows the standard Oracle "invoke/BO" naming convention, indicating that it provides a controlled, API-mediated entry point through which routing-related business logic is executed on behalf of higher-level callers such as forms, concurrent programs, and other APIs. The package is classified as OTHER within the documented API taxonomy and carries a VALID status, confirming it is a supported, compiled object in the ETRM repository for both 12.1.1 and 12.2.2.

Functionally, BOM_INVOKE_RTG_BO sits between the user interface or calling program and the underlying public routing API, BOM_RTG_PUB. Rather than allowing direct access to the public API, the Business Object layer centralizes invocation, message accumulation, and error handling, so that routing operations are performed consistently and any diagnostics are captured in a single place for subsequent retrieval.

Key Procedures and Functions

The package exposes twelve documented procedures, which fall into three logical groups:

• Business processing: PROCESS_RTG is the principal entry point that drives routing-related business activity. It coordinates the call into BOM_RTG_PUB and captures the outcome for the caller.
• Lifecycle and initialization: INITIALIZE, APPS_INITIALIZE, and RESET prepare the package's internal state before a business call and clear it afterwards, ensuring each invocation starts from a clean context.
• Message handling: GET_MESSAGE_LIST, GET_ENTITY_MESSAGE, DELETE_MESSAGE, GET_MESSAGE, GET_MESSAGE_COUNT, and DUMP_MESSAGE_LIST form a message-management subsystem. These procedures let a caller retrieve accumulated messages, obtain the message associated with a particular entity, delete individual messages, count messages, and dump the full message list for logging or display. Together they support the standard Oracle pattern in which an API call returns a status while the detailed diagnostics are collected and read separately.

No parameter signatures are asserted here; the descriptions reflect the documented procedure names and their evident roles.

Tables Accessed

The ETRM metadata records no direct table references through APPS synonyms for this package. This is consistent with its role as an invocation wrapper: persistence of routing data is delegated to BOM_RTG_PUB and its subordinate routines, which in turn operate on the Bills of Material routing tables. BOM_INVOKE_RTG_BO therefore does not itself issue direct DML against routing tables; its documented dependencies are limited to BOM_RTG_PUB, the ERROR_HANDLER package, and the SYS.STANDARD package used for standard PL/SQL types.

Usage Notes

BOM_INVOKE_RTG_BO is referenced only by itself according to the dependency report, and no other package is documented as referencing it. This indicates that it is invoked directly by external callers rather than being nested within other PL/SQL APIs. Typical invocation channels include Oracle Forms-based routing maintenance windows, concurrent programs, and custom extensions that need to create, update, or validate routing information through a supported interface.

Callers should follow the standard BO contract: invoke INITIALIZE (or APPS_INITIALIZE) to set up the session context, call PROCESS_RTG to perform the business operation, then use the GET_* procedures to read status and error messages before calling RESET to release state. Because ERROR_HANDLER is a documented dependency, error conditions raised during processing are expected to be trapped and surfaced through the message list rather than propagated as unhandled exceptions. The package is valid in both EBS 12.1.1 and 12.2.2, and Oracle's legal notices mark the underlying documentation as proprietary and confidential.