Search Results fnd_insert

Overview

APPS.HR_UTILITY is a foundational shared PL/SQL utility package inside the Oracle E-Business Suite Human Resources (HRMS) product family. Its header, sourced from pyutilty.pkh, describes it as a collection of "cover routines for FND_MESSAGE," HR trace routines, and miscellaneous helper functionality also referenced through HR_GENERAL. In practical terms, the package centralizes low-level services that other HR modules — and a very large number of dependent objects — rely on: standardized message handling, error raising, runtime tracing and logging, session and location resolution, and product-installation checks.

Because HR_UTILITY is classified in the ETRM as an API of type OTHER, and because the metadata records it as referenced by 15,228 other packages, it functions less as a business-facing API and more as an internal infrastructure layer. It abstracts Oracle Forms/AOL error conventions (FND_MESSAGE, FND_SIGNON-style session data) and diagnostic facilities (DBMS_PIPE, DBMS_OUTPUT, DBMS_UTILITY) behind stable procedure names so that individual HR programs do not each re-implement them. Note the historical purity assertions: the change list indicates that PRAGMA WNDS was applied to all procedures and functions except trace_on and fnd_insert, which is consistent with those two routines performing writes or non-read-only work.

Key Procedures and Functions

The documented interface exposes 39 procedures and functions. They group into several thematic clusters:

• Message handling: SET_MESSAGE, SET_MESSAGE_TOKEN, GET_MESSAGE, GET_MESSAGE_DETAILS, CLEAR_MESSAGE — cover routines that populate, token-substitute, retrieve, and clear the AOL message stack.
• Warnings: SET_WARNING, CHECK_WARNING, CLEAR_WARNING — a parallel mechanism for non-fatal user notifications.
• Errors: HR_ERROR, ORACLE_ERROR, RAISE_ERROR — raise HR-specific, Oracle-server, or generic application errors, typically culminating in FND_MESSAGE.RAISE_ERROR.
• Tracing and logging: TRACE, TRACE_ON, TRACE_OFF, TRACE_UDF (added to allow FastFormula tracing), READ_TRACE_PIPE, READ_TRACE_TABLE. The change list also documents logging-level routines such as log_at_statement_level, log_at_procedure_level, log_at_event_level, log_at_exception_level, log_at_error_level, log_at_unexpected_level, switch_logging_on, and switch_logging_off, plus set_trace_options.
• Session/location and miscellaneous: SET_LOCATION (pragma restriction removed to enable AOL Process Logging), TO, and FND_INSERT.
• Product installation: chk_product_install (with a language parameter and an overloaded variant) verifies whether a given product is installed/legislated.

The user's search term, fnd_insert, corresponds to the documented FND_INSERT routine — notably the one procedure (along with trace_on) excluded from the WNDS purity pragma, indicating it performs data modification rather than pure reads.

Tables Accessed

HR_UTILITY reads a defined set of APPS synonyms reflecting its session, message, and trace responsibilities:

• Session and identity: FND_SESSIONS, FND_USER, FND_RESPONSIBILITY, and ICX_SESSION_ATTRIBUTES supply sign-on context (user, responsibility, session attributes) used for location resolution, tracing, and message context.
• HR configuration: HR_LEGISLATION_INSTALLATIONS supports product/legislation installation checks such as chk_product_install.
• Utilities and diagnostics: DUAL, DBMS_OUTPUT, DBMS_PIPE, DBMS_SQL, DBMS_UTILITY, V$PROCESS, V$SESSION, and PLITBLM back the tracing pipe/table reads and environment lookups.

Usage Notes

HR_UTILITY is invoked pervasively rather than directly by end users. Oracle Forms in HRMS call its message and error routines to present consistent AOL messages; concurrent programs and PL/SQL batch jobs use its logging and trace routines to write diagnostics readable via READ_TRACE_PIPE or READ_TRACE_TABLE. FastFormula developers reach it through TRACE_UDF. Given that custom code, forms, and 15,000-plus dependent packages reference it, callers should treat it as a stable internal API: invoke its documented procedures for messaging, tracing, and installation checks, avoid relying on undocumented behavior, and remember that FND_INSERT and trace_on perform write-class operations and therefore carry different purity and side-effect implications than the read-only cover routines.