Search Results ozf_utility_pvt




Overview

OZF_UTILITY_PVT is a private PL/SQL utility package in the APPS schema that underpins the Oracle E-Business Suite Trade Management (formerly Oracle Trade Management, OZF) and Marketing (AMS) application family. It consolidates a wide range of low-level helper routines — currency conversion, timezone handling, lookup validation, foreign-key verification, uniqueness checking, and standardized message/logging utilities — into a single repository consumed across the OZF and AMS modules. Although the package is classified as PVT (private), meaning it is not intended as a public integration API, it is referenced by 159 other database objects, making it one of the most pervasive internal dependencies in the Trade Management schema. It provides a consistent framework for defensive data validation and error handling that the calling packages rely on for data integrity and user-facing diagnostics.

Key Procedures and Functions

The package exposes 65 documented procedures and functions. They can be grouped as follows:

Tables Accessed

Through APPS synonyms the package reads and writes a range of foundation and Trade Management tables. AMS_ACT_LOGS, AMS_ACT_LOGS_S, and AMS_ACT_LOGS_TRANSACTION_ID_S support activity logging; AMS_CAMPAIGN_SCHEDULES, AMS_SOURCE_CODES, AMS_STATUS_ORDER_RULES, AMS_USER_STATUSES_TL, AMS_MEDIA_TL, and AMS_CUSTOM_SETUP_ATTR provide campaign and media metadata. FND_LOOKUP_VALUES supplies lookup validation, while HR_ALL_ORGANIZATION_UNITS_TL, JTF_RS_ROLE_RELATIONS, HZ_CUST_ACCOUNTS, HZ_PARTIES, and MTL_SYSTEM_ITEMS_KFV support organizational, customer, and product validations. Additional references include OZF_ACT_BUDGETS, OZF_FUNDS_ALL_B/VL, OZF_OBJECT_FUND_SUMMARY, OZF_OFFERS, OZF_SYS_PARAMETERS_ALL, and OZF_LOOKUPS for core Trade Management data, plus FND_CURRENCIES_VL, GL_CURRENCY_API, GL_MC_CURRENCY_PKG, and GL_SETS_OF_BOOKS for currency and ledger processing.

Usage Notes

OZF_UTILITY_PVT is invoked primarily by other PL/SQL packages within Trade Management and Marketing rather than directly by end users. It is called during form saves, concurrent program executions, workflow business events, and custom code extensions that require standardized validation, currency conversion, or logging. Because it depends on FND_API, FND_MSG_PUB, FND_GLOBAL, and FND_PROFILE, correct initialization of the FND session context is required before invocation. Developers extending OZF or AMS functionality should treat the package as read-only infrastructure and avoid modifying it, since its behavior cascades to 159 dependent objects. Custom code that calls these utilities must observe the same error-handling conventions (message stack population and exceptions via FND_API) expected by the surrounding application code.