Search Results get_msg3

Overview

APPS.FII_MSG is a PL/SQL package body belonging to the FII (Financial Intelligence) product family within Oracle E-Business Suite. Its primary business function is to resolve and return period-type label strings that drive the display of time-based financial reporting pages. The package provides a set of small helper functions that translate internal period-type codes into human-readable labels such as "YTD", "QTD", "MTD", and "WTD", or into localized equivalents retrieved from the Oracle Forms message repository. These labels are consumed by the FII Daily Business Intelligence portal and related Financial Intelligence pages, where the period context of a report must be communicated clearly to the end user.

The package is classified as OTHER in the documented API metadata, meaning it is not published as a formal public API. It is nonetheless a stable internal utility, owned by APPS and referenced internally within the FII schema. The source header indicates the original creation date of 22-JUN-2002 (corresponding to an early FII release cycle).

Key Procedures and Functions

The package exposes ten documented functions, most of which are lightweight label-resolution helpers. Their purposes are as follows:

• GET_MSG — Returns a short period-label string such as "YTD", "QTD", "MTD", or "WTD" depending on the current page period type. When the internal manager identifier is not the sentinel value, it delegates to BIS_PMV_PORTAL_UTIL_PUB.getTimeLevelLabel to obtain the portal-level time label.
• GET_MSG1 — Similar to GET_MSG, but prefixes the result with a message string retrieved via FND_MESSAGE.GET_STRING for the FII application, typically the FII_GL_PMV message. This produces fully qualified labels such as "<product label> YTD".
• GET_MSG2 — A further variant in the message-resolution family, following the same pattern of returning a period label with or without a message-repository prefix.
• GET_MSG3 — The function specifically referenced by the searched term "get_msg3". It belongs to the same family of period-label helpers and is used to supply an appropriately formatted time-level label for display on FII reporting pages.
• GET_CURR — Returns the current period or currency context label used by the FII pages.
• GET_MANAGER — Resolves the manager identifier, closely tied to the g_mgr_id sentinel logic used across the other functions.
• GET_DBI_PARAMS — Retrieves Daily Business Intelligence parameter values required for page rendering.
• GET_CURR_LABEL — Returns the label for the current period context.
• GET_PRIOR_LABEL — Returns the label for the prior period context, enabling side-by-side comparisons.
• GET_MARGIN_LABEL — Returns the label describing margin (variance) calculations between compared periods.

Tables Accessed

The package operates primarily against a small set of time-entity reference tables exposed through APPS synonyms. The documented tables are FII_TIME_ENT_PERIOD, FII_TIME_ENT_QTR, FII_TIME_ENT_YEAR, and FII_TIME_WEEK. These tables define the canonical period buckets used by Financial Intelligence reporting. FII_TIME_ENT_YEAR backs the "YTD" context, FII_TIME_ENT_QTR the "QTD" context, FII_TIME_ENT_PERIOD the "MTD" context, and FII_TIME_WEEK the "WTD" context. The package references these tables to resolve the correct period semantics before constructing the returned label string. Access is read-only; no inserts, updates, or deletes are performed.

Usage Notes

FII_MSG is invoked from within the FII Financial Intelligence JSP and portal rendering layers rather than from Oracle Forms directly, as its messages are formatted through FND_MESSAGE and the BIS_PMV_PORTAL_UTIL_PUB utility. The package is not referenced by any other documented package (Referenced by 0 other packages), so its callers are expected to be page-level or view-level components rather than shared PL/SQL APIs. The global variables g_mgr_id and g_page_period_type in FII_GL_UTIL_PKG act as the controlling state that determines which branch of each function executes, meaning FII_GL_UTIL_PKG must be initialized before FII_MSG functions are called. Customizations should treat the label strings as presentation-only and avoid dependence on their exact text, since translations supplied through FND_MESSAGE may vary by language and patch level.