Search Results check_approval_required

Overview

OZF_ACTBUDGETRULES_PVT is a private PL/SQL package in the Oracle E-Business Suite Trade Management (formerly Oracle Marketing) application, owned by the APPS schema and classified as a Private API (PVT). Its stated purpose is to manage Activity Budget information on behalf of OZF_ACTBUDGETS_PVT, the public package that exposes budget functionality to the Trade Management product family. Because it is a private package, it is not intended to be called directly by customer extensions; instead it encapsulates the business validation and rule logic used internally when activity budgets are created, transferred, approved, or planned.

The package originated in April 2002, created by the developer "feliu" from procedures separated out of OZF_ACTBUDGETS_PVT, and was subsequently modified for Release 12 (the header cites revision 120.1, dated 05-Aug-2005, and one procedure carries an explicit "modified for R12" history note). In EBS 12.1.1 and 12.2.2 the package remains a PVT-class object under the APPS schema, consistent with the ETRM 12.2.2 metadata, which documents nine procedures and lists one dependent package.

Key Procedures and Functions

• check_cat_activity_match — Validates that the category and activity on a budget record match those of the associated campaign or schedule. The history note (04/10/2001) states the rule explicitly: category and activity should match for the budget and the campaign or schedule. The user search term "check_cat_activity_match" refers directly to this procedure.
• check_transfer_amount_exists — Validates a budget transfer request, confirming that funds can be transferred only from a budget source from which the user actually holds the amount. The history notes record the original rule (04/10/2001) and an R12 modification (08/05/2005).
• check_market_elig_match — Validates that the market eligibility defined on the budget is consistent with the associated campaign, offer, or schedule.
• check_prod_elig_match — Performs the equivalent validation for product eligibility.
• source_has_enough_money — Confirms that the source budget or fund has sufficient available balance to satisfy the requested operation.
• budget_has_enough_money — Confirms that the target budget holds sufficient funds for the requested activity or transfer.
• check_approval_required — Determines whether the budget transaction requires approval before it can proceed (listed twice in the package specification, indicating overloaded variants).
• can_plan_more_budget — Establishes whether additional budget may still be planned against the activity, based on applicable limits or rules.
• create_note — Creates a note record, typically used to log budget activity, approvals, or audit commentary.

Tables Accessed

The package operates against Trade Management and shared Oracle Marketing tables accessed through APPS synonyms. AMS_CAT_ACTIVITIES and AMS_CAMPAIGN_SCHEDULES_B supply category/activity and campaign-schedule data used by the match validations. AMS_CUSTOM_SETUP_ATTR provides setup attribute values that drive rule evaluation. OZF_ACT_BUDGETS is the core activity budget table read and updated during validation. OZF_FUNDS_ALL_B, OZF_FUNDS_UTILIZED_ALL_B, and OZF_OBJECT_FUND_SUMMARY support the fund-balance checks performed by source_has_enough_money and budget_has_enough_money. OZF_OFFERS is referenced for offer-level eligibility and budget context. JTF_NOTES_B holds the note records created by create_note.

Usage Notes

OZF_ACTBUDGETRULES_PVT is invoked indirectly through OZF_ACTBUDGETS_PVT, which is the documented calling interface; the ETRM metadata records exactly one dependent package. Typical invocation paths are the Trade Management activity and budget maintenance forms, budget transfer and approval flows, and any concurrent or custom code that calls the public budget API rather than the private package. Validations return a standard x_return_status value indicating success, expected error, or unexpected error, allowing the calling layer to stop processing and surface the message. Because the package is classified PVT and its specification is not part of the supported public API surface, direct calls from customer code are discouraged; customizations should route through OZF_ACTBUDGETS_PVT so that patch upgrades do not invalidate the dependency.