Results for “ozf_fund_reconcile_pvt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.OZF_FUND_RECONCILE_PVT is a private PL/SQL package within the Oracle E-Business Suite Trade Management (formerly Oracle Marketing) module. Its role is to reconcile marketing and trade promotion funds against the budgets and activities that consume them. In the Oracle EBS architecture, packages whose names end in the suffix _PVT are internal, private implementation units that are not intended for direct invocation by external custom code; they are typically called by associated public packages, concurrent programs, or workflow components that share the same functional prefix. This package encapsulates the reconciliation logic used to keep fund balances, utilized amounts, and budget summaries consistent across the OZF (Oracle Trade Management / Funds) and AMS (Marketing) schemas.

The package is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2, and its dependency footprint confirms that it depends on the standard Oracle Application Object Library foundation package FND_API, which provides the common API error-handling and message-context infrastructure used throughout EBS application programming interfaces.

Key Procedures and Functions

The documented package exposes seven procedures and functions, all oriented toward fund reconciliation and budget lifecycle management:

• RELEASE_FUND_CONC — A concurrent-program entry point that releases fund amounts, making committed or reserved funds available for utilization.
• RECONCILE_LINE — Reconciles an individual fund or activity line, aligning recorded utilization with the underlying transactional source.
• RECONCILE_BUDGET_LINE — Performs reconciliation at the budget line level, ensuring budgeted figures agree with the accumulated facts.
• RECONCILE_BUDGET_UTILIZED — Recomputes or verifies the utilized portion of a budget, synchronizing consumed amounts against recorded fund usage.
• POST_UTILIZED_BUDGET_CONC — A concurrent entry point that posts utilized budget amounts, persisting reconciled consumption back to the fund tables.
• RECAL_COMM_FUND_CONC — A concurrent routine that recalculates committed or complementary fund balances.
• OPEN_NEXT_YEARS_BUDGET — Rolls budget structures forward into the next fiscal year, supporting annual fund planning cycles.

Because this is a private package, its documented interface is minimal; parameter signatures are not published, and callers should rely on the corresponding public package rather than invoking these units directly.

Tables Accessed

The package reads and writes a range of OZF and AMS tables through APPS synonyms. Fund master and utilization data are held in OZF_FUNDS_ALL_B and OZF_FUNDS_UTILIZED_ALL_B, while OZF_ACT_BUDGETS, OZF_ACT_FORECASTS_ALL, and OZF_ACT_METRIC_FACTS_ALL store the activity-level budget, forecast, and metric fact records that drive reconciliation. Offer and request data flow through OZF_ACT_OFFERS, OZF_OFFERS, and OZF_REQUEST_HEADERS_ALL_B. Aggregated fund information is maintained in OZF_OBJECT_FUND_SUMMARY. Campaign and event context is drawn from AMS_CAMPAIGNS_ALL_B, AMS_CAMPAIGN_SCHEDULES_B, AMS_EVENT_HEADERS_ALL_B, and AMS_EVENT_OFFERS_ALL_B. Supporting tables include QP_LIMITS (Oracle Advanced Pricing limits) and JTF_PERZ_QUERY_PARAM.

Usage Notes

This package is invoked indirectly. It is referenced by the public AMS_APPROVAL_PVT package, which suggests that fund reconciliation is triggered as part of the approval workflow for marketing activities and offers. The concurrent procedures (RELEASE_FUND_CONC, POST_UTILIZED_BUDGET_CONC, RECAL_COMM_FUND_CONC) are designed to be scheduled from the Oracle Trade Management concurrent program interface. Customizations should never call the _PVT package directly; developers requiring fund reconciliation should instead use the supported public API surface or the standard concurrent programs. Any modification or direct call risks breaking the internal contract on which AMS_APPROVAL_PVT depends.