Search Results fii_message




Overview
Explore in AI Chat

Overview

The APPS.FII_MESSAGE package body is a utility package within the Oracle E-Business Suite Financial Intelligence (FII) product family. FII corresponds to the Enterprise Performance Foundation / Financial Intelligence application suite, which provides the analytical foundation and data warehouse structures consumed by Oracle Financial Analyzer, Oracle Demand Planning, and related planning and business intelligence modules. The FII_MESSAGE package exists to centralise the generation, expansion, and output of informational, warning, and error messages produced during the execution of FII batch processes, concurrent programs, and data-loading jobs.

Rather than embedding literal message strings throughout individual programs, FII routines call this package to retrieve dictionary-driven messages, substitute runtime tokens, and route the resulting text either to the concurrent managers log file or to the report output file. This design supports Oracle Application Object Library (AOL) message translations and maintains consistency of diagnostic output across the financial intelligence subsystem. The object is reported with a status of VALID in the ETRM repository for both Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package body exposes approximately thirteen documented program units. The principal ones are described below; parameter lists are intentionally not reproduced, as they are not part of the documented metadata.

  • GET_MESSAGE — Retrieves a message string, typically by message name, from the AOL message dictionary via FND_MESSAGE, returning the text for subsequent formatting or logging.
  • MSG_TKN_EXPAND — Expands token placeholders embedded in a retrieved message, substituting runtime values so that a single stored message can carry dynamic content such as object names or counts.
  • SET_LANGUAGE — Establishes or overrides the language context used when resolving translated messages.
  • WRITE_BUFFER — Accumulates or flushes message text into an internal buffer prior to final emission, allowing multi-line messages to be assembled and written coherently.
  • WRITE_LOG — Writes the composed message to the concurrent program log file, relying on FND_FILE.PUT_LINE for the physical write.
  • WRITE_OUTPUT — Writes the composed message to the concurrent program report output file, again through the FND_FILE interface.
  • FUNC_SUCC — Convenience routine signalling or logging a successful function outcome.
  • FUNC_FAIL — Convenience routine signalling or logging a failed function outcome.
  • FUNC_ENT — Convenience routine marking entry into a function or procedure, supporting trace-level diagnostics.

Tables Accessed

The only table documented as referenced through an APPS synonym is DUAL. DUAL is used for trivial single-row evaluations, for example to compute a default value, obtain SYSDATE, or drive a SELECT ... INTO for a constant. Notably, the package does not query FII business tables directly; message text originates from the AOL message dictionary accessed through the FND_MESSAGE API, which abstracts the underlying FND_MESSAGES and FND_MESSAGES_TL tables. This keeps FII_MESSAGE free of direct data-model dependencies.

Usage Notes

FII_MESSAGE is referenced by thirty-four other PL/SQL packages in the EBS schema, indicating that it functions as a shared messaging service rather than an application entry point. It is most commonly invoked from within concurrent programs and PL/SQL batch drivers belonging to the Financial Intelligence and Enterprise Performance Foundation modules, where developers require standardised, translatable diagnostics. Typical invocation patterns include retrieving a message with GET_MESSAGE, expanding it with MSG_TKN_EXPAND, and directing it to the log with WRITE_LOG or to the report with WRITE_OUTPUT. The FUNC_ENT, FUNC_SUCC, and FUNC_FAIL routines are used to bracket program units for consistent trace output. Because it is a utility rather than a forms-level API, custom code should call it only when producing FII-related diagnostics; for general AOL messaging, direct use of FND_MESSAGE and FND_FILE remains the standard approach. As the package is not referenced by any database object, its call graph flows outward only, and any modification carries a broad impact across the referencing packages.