Search Results jl_zz_fa_utilities_pkg




Overview
Explore in AI Chat

Overview

JL_ZZ_FA_UTILITIES_PKG is a custom utility package deployed in the APPS schema within Oracle EBS 12.1.1 and 12.2.2. Its name follows the conventions of Oracle's Japanese localization (JL) module layered over Fixed Assets (FA), with the "ZZ" segment denoting a customer-specific or regional extension rather than a standard Oracle-delivered object. The package body provides a consolidated set of low-level helper routines that other custom programs in the same family call for error handling, message resolution, and transaction control.

The package is best understood as infrastructure rather than business logic. It does not model assets, books, or depreciation; instead it standardizes the way surrounding programs raise and report failures. By centralizing error retrieval and exception raising, it ensures message text and error numbers are resolved consistently through the Oracle Application Object Library message dictionary.

Key Procedures and Functions

  • RAISE_ERROR — Retrieves an application message via FND_MESSAGE, captures the resolved text, and terminates execution by raising an application exception carrying the message text, message type, and numeric error code. The error number is obtained through GET_APP_ERRNUM, so the raised exception is traceable to a seeded message.
  • RAISE_ORA_ERROR — Captures SQLERRM and passes the resulting text to APP_EXCEPTION.RAISE_EXCEPTION, providing a uniform path for surfacing native Oracle errors from custom code.
  • GET_APP_ERRNUM — Accepts an application short name and message name and returns the corresponding MESSAGE_NUMBER from FND_NEW_MESSAGES. The lookup is language-aware, comparing LANG against the user's session language, and joins FND_NEW_MESSAGES to FND_APPLICATION on APPLICATION_ID to scope the message to its owning application.
  • DO_COMMIT — Performs the commit operation for the calling program. It is the package's transaction-control entry point, allowing callers to persist work through a single, auditable commit call rather than embedding COMMIT statements throughout their own code. As the name indicates, it is invoked at deliberate points rather than after every DML statement.

Tables Accessed

The documented data access is limited to two AOL reference tables, both read through APPS synonyms. FND_NEW_MESSAGES supplies the message number, message name, and language code used by GET_APP_ERRNUM; it is the runtime repository of seeded application messages. FND_APPLICATION supplies the application short name and the APPLICATION_ID join key, binding each message to the correct product. Both tables are read-only from this package's perspective. No Fixed Assets transaction tables are queried, reflecting the package's role as shared utility code. The remaining routines, RAISE_ERROR, RAISE_ORA_ERROR, and DO_COMMIT, perform no table access of their own.

Usage Notes

The package is referenced by four other packages, which indicates reuse across a small family of related custom programs. Typical invocations are from custom PL/SQL concurrent programs, database packages, or client-side blocks that require a uniform failure and commit strategy. A caller generally wraps its logic in a block, calls DO_COMMIT when a logical unit of work completes, and calls RAISE_ERROR or RAISE_ORA_ERROR in the exception handler to stop processing with a meaningful message. Because RAISE_ERROR resolves messages dynamically by language, output respects the session language. The package carries the header revision 115.1 dated 1999, so it is legacy code; implementers should treat it as stable but review language and message seeding when extending it. When debugging failures, note that the exception text originates from the message dictionary, so a missing or untranslated message will produce an incomplete error description. Because DO_COMMIT commits all pending work in the session, callers should invoke it only when no other uncommitted changes need to be preserved or rolled back.