Search Results count_and_get

Overview

EGO_UTIL_PK is a utility package body owned by the APPS schema in Oracle E-Business Suite. Its documented purpose is to provide shared helper routines for the EGO (Enterprise Governance / product information management) product family, specifically in the area of the Oracle "Publication Framework." The package encapsulates small, reusable wrappers around the Oracle Application Object Library (FND) message-handling APIs so that EGO PL/SQL code can push user-facing messages onto the FND message stack and later retrieve them in a consistent manner. It is classified in ETRM as an "OTHER" API, meaning it is a supporting utility package rather than a public or table-handler API, and is not intended as a formally supported extension point. The package header declares at least one custom PL/SQL collection type (token_tbl) and a defaulted constant (G_MISS_TOKEN_TBL), which are used to pass message tokens to the framework. The file header indicates a last revision in 2009 (120.0.12010000.1), consistent with the code lineage that ships in both 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents two procedures in the body:

• PUT_FND_STACK_MSG — Publishes a message to the FND message stack. It accepts an application short name, a message name, and an optional token collection. Internally it calls FND_MESSAGE.SET_NAME to bind the message, iterates the supplied token collection calling FND_MESSAGE.SET_TOKEN for each name/value pair, and finally calls FND_MSG_PUB.ADD to place the message on the stack. It is the standard "put a message" helper used by EGO Publication Framework code.
• COUNT_AND_GET — This is the procedure the user searched for. It is a thin wrapper over FND_MSG_PUB.COUNT_AND_GET. It declares two OUT NOCOPY parameters, a numeric message count and a VARCHAR2 message data buffer, and simply delegates to the FND API, returning the number of messages on the stack and their concatenated encoded data. It does not itself modify the MESSAGE table; it is a retrieval/read helper. Its value in EGO code is that it gives callers a single, product-local entry point for consuming FND messages, insulating them from direct FND_MSG_PUB calls.

Tables Accessed

The only table referenced through APPS synonyms is PLITBLM, the FND message storage table that backs the message dictionary and the message stack. Access to this table is not performed directly by EGO_UTIL_PK; it occurs indirectly through the FND_MESSAGE and FND_MSG_PUB calls that the two procedures invoke. PLITBLM is where FND stores the translated message text, tokens, and per-language message data that COUNT_AND_GET reads when assembling the p_msg_data output. Because the package performs no direct DML, no custom data model or EGO-owned table is touched by this utility.

Usage Notes

EGO_UTIL_PK is invoked from within EGO PL/SQL code rather than from the user interface directly. The publication framework routines call PUT_FND_STACK_MSG to record a message against the FND stack, then callers retrieve those messages using COUNT_AND_GET, typically at the end of a processing run to report warnings or errors. Because it is a public-synonym utility in the APPS schema, custom code may call APPS.EGO_UTIL_PK.COUNT_AND_GET, but as an "OTHER" classification API it carries no Oracle support commitment; standard practice is to prefer the underlying FND_MSG_PUB.COUNT_AND_GET directly in new custom development. The package is referenced by one other APPS package according to ETRM, confirming its role as a shared utility within the EGO module. In 12.1.1 and 12.2.2 the source is identical, so behavior is consistent across both releases, and no 12.2-specific online-patching changes affect these procedures.