Search Results qp_modifiers

Overview

OZF_ACTBUDGETRULES_PVT is a private PL/SQL package in the Oracle EBS Trade Management (formerly Oracle Marketing and Offers) product family. It encapsulates the business rules that govern activity budgets associated with campaigns, schedules, and offers. The package validates whether budget records may be created, planned, transferred, or approved, and it enforces the relationships that must exist between a budget and its owning activity, category, product eligibility set, and market eligibility set. Because the package is classified as PVT, it is not a public API; it is designed to be called internally by other Trade Management packages and by the forms and concurrent programs that manage budget planning and fund accrual. The header comment indicates the object was separated out of OZF_ACTBUDGETS_PVT in April 2000 and has been maintained through several EBS release cycles, including fixes carried into Release 12 (Bug 6654242, referencing the R12 12.1 code line).

Key Procedures and Functions

• CHECK_CAT_ACTIVITY_MATCH — Validates that the category assigned to a budget matches the activity of the owning campaign schedule or offer. It resolves the activity identifier from AMS_CAMPAIGN_SCHEDULES_B or OZF_OFFERS depending on the used-by type, then confirms the category/activity combination exists in AMS_CAT_ACTIVITIES. Introduced to enforce the category-to-activity consistency rule.
• CHECK_TRANSFER_AMOUNT_EXISTS — Verifies that a budget transfer amount is present and valid before the transfer is processed.
• CHECK_MARKET_ELIG_MATCH — Confirms that the market eligibility defined for a budget is consistent with the eligibility defined on the parent object.
• CHECK_PROD_ELIG_MATCH — Confirms that the product eligibility defined for a budget is consistent with the eligibility defined on the parent object.
• SOURCE_HAS_ENOUGH_MONEY — Checks whether the source fund or budget from which money is being moved has sufficient available balance to satisfy the requested amount.
• BUDGET_HAS_ENOUGH_MONEY — Checks whether the target budget has sufficient funds remaining for the requested allocation or utilization.
• CHECK_APPROVAL_REQUIRED — Determines whether a budget or budget change requires approval, based on the applicable custom setup attributes.
• CAN_PLAN_MORE_BUDGET — Determines whether additional budget may still be planned against the activity, returning the eligibility of further planning. This function was updated in May 2002 to refine the planning-limit logic.
• CREATE_NOTE — Creates a note in the JTF notes repository, typically used to record budget approval, reconciliation, or transfer activity for audit purposes. Prior SQL repository fixes (Bugs 4415878, 4870218) affected statements within this package.

Tables Accessed

The package reads and writes the following tables through APPS synonyms. AMS_CAMPAIGN_SCHEDULES_B supplies the activity identifier for a campaign schedule. AMS_CAT_ACTIVITIES validates category and activity combinations. AMS_CUSTOM_SETUP_ATTR provides custom setup attribute values used in approval determination. JTF_NOTES_B stores notes created by CREATE_NOTE. OZF_ACT_BUDGETS holds the activity budget records being validated. OZF_FUNDS_ALL_B and OZF_FUNDS_UTILIZED_ALL_B supply fund and utilization balances for the sufficient-money checks. OZF_OBJECT_FUND_SUMMARY provides aggregated fund summaries, and OZF_OFFERS supplies the activity media identifier for offer-based budgets.

Usage Notes

OZF_ACTBUDGETRULES_PVT is invoked primarily from the Trade Management budget planning and accrual reconciliation flows within Oracle Forms and from other PL/SQL packages in the OZF schema. Its validation procedures are typically called immediately before inserting or updating budget and fund utilization records, ensuring that category/activity, eligibility, and funding constraints are satisfied. The package is referenced by at least one other package, and is used during accrual reconciliation processing, as noted in the Bug 6654242 fix for error ORA-01400. Custom code should avoid calling this PVT package directly, since its interface is not guaranteed across releases; the supported entry points are the public Trade Management APIs and the standard Forms. When extending or debugging budget behavior, DBMS_OUTPUT tracing can be enabled through the standard FND debug message level, which the package checks via FND_MSG_PUB at initialization.