Search Results log_mesg

Overview

FV_UTILITY is a shared PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Federal Financials (FV) product family and provides low-level helper routines consumed throughout the FV modules rather than exposing a single business transaction of its own. Its role is comparable to a common services library: it abstracts recurring operations such as message logging, debug tracing, profile and context retrieval, ledger and period interrogation, key flexfield account derivation, and temporary-table maintenance into one reusable body.

The package is heavily relied upon across the application. ETRM records that FV_UTILITY is referenced by 85 other database objects while depending on fewer than thirty, confirming its position as a foundational dependency rather than a leaf component. All documented routines reside in the package body; the specification is not separately enumerated in the metadata excerpt.

Key Procedures and Functions

The ETRM metadata documents 21 procedures and functions, classified generically as OTHER (non-API). The principal groups are:

• Logging and messaging: LOG_MESG, DEBUG_MESG, MESSAGE, and TIN provide message generation and diagnostic output, typically writing through FND_FILE, FND_LOG, and FND_MESSAGE.
• Context and environment: GET_CONTEXT, GET_ORG_INFO, GET_REPORT_INFO, GET_LEDGER_INFO, and TIME_STAMP return runtime attributes such as organizational unit, concurrent request context, ledger identity, and timestamps.
• Accounting period handling: GL_GET_FIRST_PERIOD and GET_PERIOD_YEAR resolve period names and fiscal years against the General Ledger period calendar.
• Key flexfield and account derivation: GET_SEGMENT_COL_NAMES, CALC_CHILD_FLEX_VALUE, CALC_CONCAT_ACCTS, and GET_ACCRUAL_ACCOUNT support account generation, parent/child value rollup, and accrual account determination using FND_FLEX_APIS and the flexfield views.
• Temporary-table and data maintenance: DELETE_FV_BC_ORPHAN, FV_CLEANUP_XLA_GT, and GET_FUND_INFORMATION clear orphaned rows and clean up Subledger Accounting global temporary tables, while GET_FUND_INFORMATION returns fund-related attributes.

Parameter signatures are not disclosed in the metadata and should be confirmed by inspecting the package specification in the target instance.

Tables Accessed

The package reads and writes a documented set of APPS synonyms. Reference data comes from GL_LEDGERS (and GL_SETS_OF_BOOKS, GL_LEDGER_LE_V, GL_LEDGERS_PUBLIC_V), GL_PERIODS, GL_PERIOD_STATUSES, FND_ID_FLEX_SEGMENTS_VL, FND_FLEX_VALUES_VL, FND_FLEX_VALUE_CHILDREN_V, FND_SEGMENT_ATTRIBUTE_VALUES, FND_APPLICATION_VL, FND_RESPONSIBILITY_VL, and PER_ALL_PEOPLE_F. Execution context is drawn from FND_CONCURRENT_REQUESTS, FND_PROFILE, and FND_GLOBAL. Transactional and staging data involves FV_BE_TRX_DTLS, PO_SYSTEM_PARAMETERS, and the Subledger Accounting global temporary tables XLA_ACCT_PROG_DOCS_GT, XLA_ACCT_PROG_EVENTS_GT, XLA_AE_HEADERS_GT, XLA_AE_LINES_GT, XLA_BAL_AC_CTRBS_GT, XLA_BAL_ANACRI_CTRBS_GT, and XLA_BAL_ANACRI_LINES_GT. The XLA tables are the targets of the cleanup routine FV_CLEANUP_XLA_GT, which removes residual rows left by interrupted accounting program runs.

Usage Notes

FV_UTILITY is not an end-user interface; it is invoked programmatically. Typical callers are FV concurrent programs, Forms-based screens, and other PL/SQL packages that need consistent message logging, ledger and period lookups, or account string construction. The cleanup routines are commonly scheduled or triggered around Subledger Accounting program execution to prevent stale global temporary table data from affecting subsequent runs. Because it is a body-only utility with extensive inbound dependencies, modifications can affect many downstream consumers; custom code should reference the documented packaged procedures rather than duplicating their logic, and any changes should be regression-tested against the 85 dependent objects.