Search Results get_parent_src

Overview

OZF_FUND_ADJUSTMENT_PVT is an Oracle E-Business Suite PL/SQL package owned by the APPS schema within the Oracle Trade Management (OZF) product family. It operates as a private (PVT) API layer dedicated to the management of trade promotion funds, accruals, and budgets — specifically the creation, adjustment, posting, and currency conversion of fund utilization and budget amounts. The package supplies the transactional backbone that allows Trade Management to track how much of a lump-sum, accrual-based, or budget-based fund has been consumed, adjusted, or reconciled against actual activity. It is not intended as a public interface; instead, it is consumed by other OZF packages that expose the higher-level business surface to forms, concurrent programs, and the Trade Management user interface.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions. Representative examples include:

• CREATE_FUND_UTILIZATION — establishes a new utilization record against a fund, recording consumption of the fund's available balance.
• CREATE_BUDGET_AMT_UTILIZED — generates the budget amount utilized entry that tracks drawn-down budget value.
• CONVERT_CURRENCY and GET_EXCHANGE_RATE — pair together to translate fund and budget amounts between currencies using Oracle's standard conversion mechanism, ensuring multi-currency fund tracking is consistent.
• PROCESS_ACT_BUDGETS — processes activity budgets, likely consolidating or recalculating budget positions tied to campaign or offer activity.
• POST_UTILIZED_BUDGET and ADJUST_UTILIZED_BUDGET — handle the posting of utilized budget amounts and subsequent adjustments, forming the core of the fund adjustment workflow.
• UPDATE_BUDGET_SOURCE — maintains the source attribution for a budget record.
• POST_SF_LUMPSUM_AMOUNT — posts single-fund lump-sum amounts, supporting lump-sum fund types.
• GET_PARENT_SRC — resolves a parent source reference, supporting hierarchical fund-source relationships.

The remaining documented procedures follow the same CRUD-and-post pattern, collectively maintaining the integrity of the fund utilization lifecycle.

Tables Accessed

The package reads and writes the following documented tables (via APPS synonyms):

• OZF_FUNDS_ALL_B and OZF_FUNDS_UTILIZED_ALL_B — the primary fund and fund-utilization base tables holding balances and consumption records.
• OZF_ACT_BUDGETS and OZF_ACT_OFFERS — activity budget and offer linkage, used when processing activity-driven budgets.
• OZF_OFFERS, OZF_OBJECT_FUND_SUMMARY, and OZF_REQUEST_HEADERS_ALL_B — offer definitions, fund summaries, and request headers tying adjustments to the originating business request.
• AMS_ACT_PRODUCTS, AMS_CAMPAIGN_SCHEDULES_B, AMS_CUSTOM_SETUP_ATTR, and AMS_EVENT_OFFERS_ALL_B — Oracle Marketing (AMS) entities establishing the campaign, event, and product context for fund activity.
• HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL — customer and site context for fund ownership and utilization.
• OE_PRICE_ADJUSTMENTS — Order Management price adjustments that may drive or reflect fund consumption.

Usage Notes

OZF_FUND_ADJUSTMENT_PVT is invoked indirectly rather than directly from end-user forms. Its direct callers include AMS_ACTMETRIC_PVT, OZF_ACTBUDGETS_PVT, OZF_ADJUSTMENT_EXT_PVT, OZF_CLAIM_ACCRUAL_PVT, OZF_FUND_RECONCILE_PVT, OZF_FUND_UTILIZED_PUB, OZF_FUND_UTILIZED_PVT, OZF_NET_ACCRUAL_ENGINE_PVT, OZF_OFFER_PVT, and OZF_RESALE_COMMON_PVT. It also underlies the OZF_FUND_CHECKBOOK_V view. Consequently, it executes during fund accumulation, checkbook display, accrual posting, reconciliation, and offer fund utilization flows. Because it relies on FND_API, JTF_PLSQL_API, STANDARD, and OZF_UTILITY_PVT, it expects a standard EBS runtime environment and supports API-level error handling and rollback semantics. Customizations should never call the PVT layer directly; integrations should use the corresponding _PUB package or the documented concurrent programs, as the private package signature is not guaranteed to remain stable across patches or upgrades in 12.1.1 and 12.2.2.