Search Results fun_net_util




Overview
Explore in AI Chat

Overview

FUN_NET_UTIL is a utility package owned by the APPS schema in Oracle E-Business Suite. It forms part of the Oracle Financials Netting module, which supports intercompany and intercompany-style netting of payables and receivables obligations across trading partners and operating units. The package is classified as a UTIL (utility) API, indicating that it does not expose business transaction entry points directly to end users; instead, it provides reusable infrastructure services consumed by other packages in the netting subsystem. In EBS 12.1.1 and 12.2.2, the object carries a VALID status, confirming it compiles cleanly and is actively maintained by Oracle.

The package's principal responsibilities relate to diagnostic message logging and currency rounding. These are cross-cutting concerns required by every netting process, including netting batch creation, approval workflow integration, cancellation, and merger of supplier or customer records. By centralizing these services in a single utility package, Oracle keeps the functional packages free of duplicated error-handling and rounding logic.

Key Procedures and Functions

The ETRM metadata documents four entry points within APPS.FUN_NET_UTIL:

  • LOG_MSG — Records an informational or diagnostic message produced during netting processing. It is the general-purpose logging interface used by the calling packages.
  • LOG_UNEXPECTED_MSG — Specifically logs unanticipated or unexpected conditions, allowing developers and support staff to distinguish abnormal processing outcomes from routine diagnostics.
  • LOG_STRING — Persists a caller-supplied string, typically used when the message payload is already formatted or when raw text must be captured without additional message-framework processing.
  • ROUND_CURRENCY — Returns a currency amount rounded in accordance with the precision rules defined for the relevant currency, ensuring that netting amounts conform to the minimum and maximum account unit rules of the ledger currency.

Parameter lists are not exposed in the documented metadata and are therefore not reproduced here. The naming convention and the dependency graph indicate that these routines are invoked internally by the netting packages rather than by external customers directly.

Tables Accessed

The only documented table reference is FND_CURRENCIES, accessed through an APPS synonym. FND_CURRENCIES is the Oracle Application Object Library table that stores currency definitions, including ISO codes, precision attributes, and rounding factors. FUN_NET_UTIL consults this table to supply the ROUND_CURRENCY routine with the correct precision and rounding behavior for the currency in which a netting transaction is denominated. No other base tables are listed in the ETRM excerpt, which is consistent with a utility package whose logging routines write to the standard concurrent-manager log and output mechanisms rather than to dedicated application tables.

Usage Notes

FUN_NET_UTIL sits low in the netting call stack. The documented reverse-dependency list shows that it is referenced by six packages: FUN_NET_APPROVAL_WF, FUN_NET_ARAP_PKG, FUN_NET_BATCHES_PKG, FUN_NET_CANCEL_PKG, FUN_NET_CONC_PROG_PKG, and FUN_VENDORMERGE_GRP, and also by itself. This dependency footprint confirms that it is invoked implicitly whenever a user runs a netting concurrent program, submits a netting batch, initiates the approval workflow, cancels a netting transaction, or executes a supplier merge involving netting data. Because the package is not itself exposed to a form or a concurrent program, it is rarely called from custom code; Oracle's own packages are its principal consumers.

Administrators and technical consultants generally encounter FUN_NET_UTIL only when diagnosing netting errors or when validating the compiled state of the APPS schema after an upgrade to 12.1.1 or 12.2.2. In release 12.2.x it remains a database-resident package unaffected by the online patching editioning model applied to certain other objects. Any recompilation or invalidation of this package should be treated as significant, since its dependents will be invalidated in turn until recompilation completes.