Search Results fii_util




Overview

FII_UTIL is a utility package in the APPS schema of Oracle E-Business Suite, classified in the ETRM repository as an API of type UTIL. It provides shared technical infrastructure for the FII product family, which supports financial intelligence and reporting functionality within EBS. In the 12.1.1 and 12.2.2 releases the object is documented as VALID and the package body carries fourteen procedures and functions covering initialization, diagnostics, timing, schema resolution, file-system handling, and output generation.

The package deliberately concentrates on low-level, non-business plumbing rather than transactional logic. It depends on FND_FILE, FND_INSTALLATION, FND_ORACLE_USERID, FND_PROFILE, PUBLIC.V$PARAMETER and STANDARD, and it is referenced by 76 other packages, confirming its role as a foundational helper consumed across the FII codebase.

Key Procedures and Functions

The documented entry points divide into functional groups:

  • INITIALIZE — establishes package-level context and state before other routines are called.
  • DEBUG_LINE, PUT_LINE, PUT_TIMESTAMP, WRITE_LOG, WRITE_OUTPUT — output and logging primitives. PUT_LINE and DEBUG_LINE emit formatted text, PUT_TIMESTAMP prepends temporal context, and WRITE_LOG and WRITE_OUTPUT direct diagnostic or user-facing text to the appropriate destinations.
  • START_TIMER, STOP_TIMER, PRINT_TIMER — performance instrumentation. START_TIMER and STOP_TIMER bracket a measured interval, and PRINT_TIMER emits the elapsed result for diagnostics.
  • GET_SCHEMA_NAME, GET_APPS_SCHEMA_NAME — resolve the appropriate Oracle schema names at runtime, which is essential in environments where the APPS and product schemas are separated or consolidated.
  • TRUNCATE_TABLE, DROP_TABLE — administrative DDL helpers used to clear or remove staging and temporary structures.
  • GET_UTL_FILE_DIR — retrieves the permitted UTL_FILE directory configuration, allowing the package to write server-side files safely.

Tables Accessed

The documented dependencies name two underlying objects, both reached through APPS synonyms. FND_ORACLE_USERID supplies credentials or user identity information used when resolving schema and database account context, particularly for GET_SCHEMA_NAME and GET_APPS_SCHEMA_NAME. PUBLIC.V$PARAMETER, the dynamic performance view of initialization parameters, supports discovery of database-level settings such as UTL_FILE_DIR and related configuration values consumed by GET_UTL_FILE_DIR and the logging routines. No application transaction tables are documented as direct dependencies, which is consistent with the utility classification.

Usage Notes

FII_UTIL is not a business API that end users call directly. It is invoked from other PL/SQL units — the 76 referencing packages — and from concurrent programs and forms-based flows that need consistent logging, timing, or schema resolution. A typical invocation begins with INITIALIZE, followed by START_TIMER, business processing, STOP_TIMER and PRINT_TIMER, with PUT_LINE or WRITE_LOG capturing messages and GET_UTL_FILE_DIR used when file output is required.

Because TRUNCATE_TABLE and DROP_TABLE perform DDL, callers should restrict their use to staging or temporary objects and avoid them against transactional data. Debug output is normally gated by profile settings read through FND_PROFILE, so production executions remain quiet unless diagnostics are enabled. When troubleshooting the FII module, this package is a useful first stop: its logging and timing routines frequently reveal where a concurrent request or form session failed.