Search Results ams_event_headers_b




Overview
Explore in AI Chat

Overview

The APPS.OZF_OBJFUNDSUM_PVT package body is a private (PVT-classified) PL/SQL API within the Oracle E-Business Suite Trade Management (formerly Oracle Marketing / Oracle Funds) module. Its purpose is to maintain the object-level fund summary records stored in the OZF_OBJECT_FUND_SUMMARY table and its intersection table OZF_OBJECT_FUND_SUMMARY_S. These summary records aggregate budget, accrued, and consumed fund amounts that have been associated with a specific promotional or marketing object, such as an offer, a budget, or an activity. In ETRM releases 12.1.1 and 12.2.2, this package is part of the internal funding engine that keeps object fund balances synchronized with transactional activity generated by offers, budgets, and accruals.

The package is classified as PVT, meaning it is not intended as a public integration API. Instead, it is invoked from within the OZF funding stack — particularly by OZF_ACTBUDGETS_PVT and related internal packages — to create, validate, process, and complete object fund summary records as part of a controlled workflow.

Key Procedures and Functions

The documented package exposes five procedures/functions that together implement the lifecycle of an object fund summary record:

  • CREATE_OBJFUNDSUM — Inserts a new object fund summary record for a given object, initializing the summary structure used to track funding amounts against that object.
  • UPDATE_OBJFUNDSUM — Modifies an existing object fund summary record, typically to reflect changed or recalculated fund amounts.
  • PROCESS_OBJFUNDSUM — Executes the core business logic that aggregates and applies fund movements to the object fund summary.
  • VALIDATE_OBJFUNDSUM — Performs validation checks against the summary data prior to persistence, using the standard ETRM validation conventions.
  • COMPLETE_OBJFUNDSUM_REC — Finalizes an object fund summary record, marking the workflow as complete and releasing associated processing state.

The naming pattern (CREATE, UPDATE, VALIDATE, PROCESS, COMPLETE) reflects the standard Oracle Application Framework private-API convention used throughout ETRM, where each procedure represents a discrete step in an internal record-handling flow.

Tables Accessed

The package operates against the following documented tables, all accessed through APPS synonyms:

  • OZF_OBJECT_FUND_SUMMARY — The primary summary table, holding aggregated fund amounts per object. This is the main read/write target of the package.
  • OZF_OBJECT_FUND_SUMMARY_S — The intersection/association table linking fund summary records to their source objects. The _S suffix indicates a relationship table used to resolve object-to-summary associations.
  • OZF_FUNDS_ALL_B — The base funds table, providing fund definitions and amounts referenced when building the summary.
  • OZF_ACT_OFFERS — The activity-to-offer association table, used to determine which offers contribute to the object fund summary.
  • DUAL — Used for single-row PL/SQL evaluations, consistent with standard Oracle development practice.

In addition, the package depends on several shared infrastructure packages, including FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, JTF_PLSQL_API, OZF_ACTBUDGETS_PVT, and OZF_UTILITY_PVT. These provide error handling, message resolution, profile lookups, and shared OZF utility logic.

Usage Notes

Because OZF_OBJFUNDSUM_PVT is a private package, it is not designed for direct invocation by external integrations. It is typically called from:

  • Other OZF internal packages, notably OZF_ACTBUDGETS_PVT, which orchestrates budget and activity processing;
  • Concurrent programs within the Trade Management funding suite that rebuild or reconcile object fund summaries;
  • PL/SQL triggers or workflow activities internal to the OZF funding schema.

The ETRM metadata confirms that the package is referenced by five other database objects, but that it does not itself reference any objects outside the APPS and SYS/STANDARD schemas. Developers maintaining custom extensions in this area should invoke the public funding APIs rather than this private package, since its signature and behavior are not part of the supported integration surface and may change between patch levels of 12.1.1 and 12.2.2.