Results for “delete_fund”

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

Overview

OZF_FUND_EXTENSION_PVT is a private (PVT) PL/SQL package in the Oracle EBS Trade Management (formerly Oracle Marketing) module, owned by the APPS schema and declared with AUTHID CURRENT_USER. It provides the extension API layer through which the EBS "Delete Objects" framework validates and physically removes trade promotion fund records. The package works in tandem with the standard OZF Funds entity, which stores promotional fund headers and their translated attributes, and it encapsulates the referential-integrity logic that determines whether a fund may be deleted. Because it is classified as a private API, it is not intended for direct invocation by external integrations; instead it is called from within the application's own deletion processing. The header comment tag identifies the source as ozfvfexs.pls, version 115.1, with an original creation date of 2004, indicating the package has been stable across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

• validate_delete_fund — Called by the Delete Objects framework prior to any destructive action. Its purpose is twofold: first, to identify and return details of dependent objects that prevent the fund from being deleted; second, when no such blocking dependencies exist, to identify dependent objects that may be deleted and the relationships that can be safely disassociated. The procedure returns a dependent-objects table using the AMS_UTILITY_PVT.DEPENDENT_OBJECTS_TBL_TYPE structure, populated through the x_dependent_object_tbl output parameter, along with the standard API return status, message count, and message data outputs.
• delete_fund — Invoked by the Delete Objects framework to perform the hard table delete of the fund once validation has succeeded. It follows the standard EBS API parameter convention, accepting an API version number, initialization message list flag, commit flag, the target object identifier and object version number, and returning the standard status and message outputs. No dependent-objects table is returned by this procedure.

Tables Accessed

The package reads and writes across the fund, offer, activity, and pricing structures. Fund header and translation data reside in OZF_FUNDS_ALL_B and OZF_FUNDS_ALL_TL, with utilization tracked in OZF_FUNDS_UTILIZED_ALL_B. Offer associations are handled through OZF_OFFERS and pricing list structures through QP_LIST_HEADERS. Activity-level dependencies are evaluated against AMS_ACT_ACCESS, AMS_ACT_MARKET_SEGMENTS, AMS_ACT_PRODUCTS, and the OZF activity budget and metric tables OZF_ACT_BUDGETS, OZF_ACT_METRICS_ALL, OZF_ACT_METRIC_FACTS_ALL, OZF_ACT_METRIC_FORMULAS, and OZF_ACT_METRIC_FORM_ENT. The PLITBLM table is referenced for pricing list line data. These accesses support both the dependency inspection performed by validate_delete_fund and the cascading removal performed by delete_fund.

Usage Notes

OZF_FUND_EXTENSION_PVT is not exposed to end users directly. It is invoked by the Delete Objects framework when a user attempts to delete a fund from the Trade Management fund maintenance user interface, and it is referenced by two other packages within the application code base. Because the procedures default the initialization and commit flags to FND_API.G_FALSE, callers retain control over transaction boundaries and must issue their own commit. Customizations that require programmatic deletion of funds should call the validated public API surface rather than this private package, and any direct use should replicate the validate-then-delete sequence to preserve transactional integrity. The dependent-objects table returned by validation allows the framework to present blocking and deletable dependency details to the user before the hard delete proceeds.