Search Results ams_fund_utilized_all_pkg




Overview
Explore in AI Chat

Overview

The package body APPS.AMS_FUND_UTILIZED_ALL_PKG is a member of the Oracle E-Business Suite (EBS) Trade Management (formerly Advanced Marketing) schema, residing in the APPS schema. It provides the underlying implementation for maintaining the "Funds Utilized" entity, which records how marketing funds, accruals, and budgets are consumed against customer or promotional activities. In Oracle EBS 12.1.1 and 12.2.2, this package functions as the supporting body behind the Funds Utilized maintenance API, exposing the DML logic that forms, concurrent programs, and the multi-language translation framework use to create, modify, and delete funds utilized records. Its status is documented as VALID, indicating a healthy compiled body in the reference environment.

The package is classified as a generic (OTHER) API rather than a form-driven or concurrent-manager-driven interface. This classification implies that the procedures are intended to be called programmatically, typically by forms infrastructure, translation utilities, or upgrade and loading routines rather than by end users directly.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions within the package body:

  • INSERT_ROW — Creates a new Funds Utilized row in the base table, populating the mandatory columns and any application-defined attributes supplied by the caller.
  • LOCK_ROW — Acquires a row-level lock on an existing Funds Utilized record to support concurrent update protection and optimistic locking semantics used by the enclosing form.
  • UPDATE_ROW — Applies changes to an existing Funds Utilized record, updating the base row to reflect revised utilized amounts or descriptive attributes.
  • DELETE_ROW — Removes an existing Funds Utilized record, along with any dependent translation rows, from the underlying entity.
  • ADD_LANGUAGE — Inserts a new translation row into the _TL table for a specified language, supporting the Oracle multi-language (MLS) framework.
  • TRANSLATE_ROW — Updates translated descriptive columns (for example, the name or description) for a specific language in the translation table.
  • LOAD_ROW — Loads a Funds Utilized row together with its translation data, commonly used during data migration, seeding, or upgrade scripts.

The package also depends on the APP_EXCEPTION package for error raising and on FND_MESSAGE for message retrieval, enabling consistent, localizable error handling.

Tables Accessed

The package body directly references the following objects (through APPS synonyms):

  • OZF_FUNDS_UTILIZED_ALL_B — The base table storing Funds Utilized records, including identifiers and numeric utilization columns. This is the primary target of INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOAD_ROW.
  • OZF_FUNDS_UTILIZED_ALL_TL — The translation table holding language-specific descriptive text. It is maintained through ADD_LANGUAGE and TRANSLATE_ROW and read during LOAD_ROW to persist translated attributes.
  • OZF_FUNDS_UTILIZED_S — The sequence used to generate primary key values for the base table, referenced in the user's search as ozf_funds_utilized_s. The package body draws next values from this sequence during INSERT_ROW and LOAD_ROW.
  • FND_LANGUAGES — The Oracle Applications language repository, consulted to validate the language code passed to ADD_LANGUAGE and TRANSLATE_ROW.
  • DUAL — Used for single-row expressions, such as retrieving a sequence value or a SYSDATE default.

The dependency list confirms that no external application package other than APP_EXCEPTION, FND_MESSAGE, and Oracle's STANDARD is required, keeping the package's coupling to the EBS codebase minimal.

Usage Notes

AMS_FUND_UTILIZED_ALL_PKG is not referenced by any other database object, confirming it is a leaf-level API rather than a shared utility. It is most likely invoked by the Funds Utilized maintenance form or window, the multi-language translation loader, and by upgrade or data-migration scripts that seed Funds Utilized data. Because the procedures follow the standard Oracle EBS multi-language pattern (base table plus _TL table with ADD_LANGUAGE, TRANSLATE_ROW, and LOAD_ROW), custom code should mirror that pattern when creating or translating records, rather than performing direct DML against the underlying tables. The package's sole public dependencies are DUAL, FND_LANGUAGES, and the sequence OZF_FUNDS_UTILIZED_S, so it serves as the canonical entry point for any programming interface to the Funds Utilized entity in Oracle EBS 12.1.1 and 12.2.2.