Search Results init_utilization_rec

Overview

APPS.OZF_FUND_UTILIZED_PVT is a private (PVT) PL/SQL package within the Oracle E-Business Suite Trade Management (formerly Trade Management/Advanced Pricing) module, schema APPS, with a documented status of VALID. It belongs to the Oracle ETRM (Enterprise Trade Management) family of fund management objects and forms part of the internal implementation layer that supports accrual and utilization processing for trade promotions and customer funds. The package encapsulates the core business logic for creating, validating, updating, locking, and deleting records that represent the utilization of funds — that is, the consumption or spending of accrued promotional budgets against accruals, claims, or adjustments.

As a PVT package, it is not intended to be called directly by external interfaces; rather, it exposes implementation procedures consumed by public (PUB) wrappers and other internal engine components such as OZF_ACCRUAL_ENGINE, OZF_CLAIM_ACCRUAL_PVT, and OZF_FUND_ADJUSTMENT_PVT. The package therefore sits at the heart of the fund utilization transaction flow, ensuring that budget balances, accrual records, and utilization amounts remain consistent across the Trade Management data model.

Key Procedures and Functions

The ETRM metadata documents twelve procedures and functions within the package, including:

• CREATE_UTILIZATION — Creates a new fund utilization record, applying validation and deriving the record from an offer, claim type, or accrual source.
• CREATE_ACT_UTILIZATION — Creates a utilization specifically associated with an activity or accrual activity record, linking to budget and activity data.
• UPDATE_UTILIZATION — Modifies an existing utilization record, updating amounts, status, or associated attributes.
• DELETE_UTILIZATION — Removes a utilization record, subject to validation of the current state.
• LOCK_UTILIZATION — Acquires a lock on a utilization record to prevent concurrent modification during a transaction.
• VALIDATE_UTILIZATION — Performs business rule validation (fund availability, dates, associations) prior to commit.
• CHECK_UTILIZATION_ITEMS — Checks the items or line-level details attached to a utilization for correctness and completeness.
• CHECK_UTILIZATION_RECORD — Verifies the existence and consistency of the utilization record itself.
• INIT_UTILIZATION_REC — Initializes the PL/SQL record structure used to populate the utilization table columns.
• COMPLETE_UTILIZATION_REC — Finalizes and completes the record, setting derived or defaulted attributes before insert/update.

Exact parameter lists are not published in the metadata and are therefore omitted.

Tables Accessed

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

• OZF_FUNDS_UTILIZED_ALL_B / _TL / _S — the base, translated, and sequence tables holding fund utilization records; these are the primary write targets.
• OZF_FUNDS_ALL_B — source of fund definitions against which utilization is applied.
• OZF_ACT_BUDGETS, OZF_OBJECT_FUND_SUMMARY — budget and summary balances checked and decremented as funds are consumed.
• OZF_OFFERS, OZF_CLAIM_TYPES_ALL_B, OZF_SD_REQUEST_HEADERS_ALL_B — source documents (offers, claim types, deduction requests) driving the utilization.
• AMS_ACT_PRODUCTS — activity product associations used in activity-based utilization.
• OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL — order context for utilization linked to sales orders.
• HZ_CUST_SITE_USES_ALL — customer site information for bill-to/ship-to resolution.
• GL_PERIOD_STATUSES — period open/closed validation.
• FND_LANGUAGES — language for translated (TL) records.

Usage Notes

OZF_FUND_UTILIZED_PVT is invoked indirectly through its public counterpart OZF_FUND_UTILIZED_PUB and the _W wrapper package. It is called by the accrual engine (OZF_ACCRUAL_ENGINE), claim accrual logic (OZF_CLAIM_ACCRUAL_PVT), and fund adjustment processing (OZF_FUND_ADJUSTMENT_PVT) when accruals, claims, or adjustments generate or modify fund utilization entries. In Oracle EBS 12.1.1 and 12.2.2, Trade Management forms and concurrent programs that process accruals, claims, or promotional fund consumption will ultimately reach this package. Custom code should not call the PVT package directly; integrators should use the PUB API or the documented business flows. Because the package validates against GL period status and fund budgets, utilization processing must occur in an open period with sufficient available funds, and record locking behavior should be respected to avoid concurrent update conflicts.