Search Results get_media_name
Overview
OZF_UTILITY_PVT is a private (PVT) PL/SQL package in the Oracle EBS APPS schema that provides a shared library of low-level utility routines for the Oracle Trade Management (OZF) and Oracle Marketing (AMS) application family. Because it is classified as a private API, it is not intended as a public integration surface; rather, it is an internal helper package consumed by other OZF and AMS packages to centralize common operations such as debug and logging, foreign-key and uniqueness validation, lookup resolution, currency and timezone conversion, and status and resource lookups. The package header carries a source revision of 120.7 dated 23-May-2006, and its change history shows continuous additions between 2000 and 2005, reflecting its role as an evolving foundation utility rather than a business-transaction API. In 12.1.1 and 12.2.2, the package remains shipped and is referenced by 159 other packages, which underscores its foundational position within the OZF/AMS code stack.
Key Procedures and Functions
The documented API surface comprises 65 procedures and functions. The core utility groups are as follows:
- Logging and diagnostics: DEBUG_MESSAGE, LOG_MESSAGE, LOGGING_ENABLED, and CREATE_LOG provide conditional debug output, message logging, and a logging-enabled switch. CREATE_LOG, per the history comments, was progressively extended to accept threshold_id, budget_id, transaction_id, notification creation date, and activity_log_id.
- Validation helpers: CHECK_FK_EXISTS verifies foreign-key existence, CHECK_LOOKUP_EXISTS (overloaded, including a variant querying FND_LOOKUPS) validates lookup codes, and CHECK_UNIQUENESS tests for duplicate values. IS_Y_OR_N evaluates a Y/N flag.
- Metadata and name resolution: GET_QUAL_TABLE_NAME_AND_PK returns a qualification table name and its primary key, GET_OBJECT_NAME resolves an object name, GET_RESOURCE_NAME and GET_RESOURCE_ROLE return resource information, and GET_PARTY_NAME was added to resolve party names.
- Lookup and value retrieval: GET_LOOKUP_MEANING, GET_FND_LOOKUP_MEANING, GET_MEDIA_NAME, and GET_CURRENCY_NAME return descriptive meanings and names.
- Currency and time handling: CONVERT_CURRENCY supports currency rounding and conversion, while GET_SYSTEM_TIMEZONE, GET_USER_TIMEZONE, and CONVERT_TIMEZONE handle timezone normalization.
- Error handling and status: ERROR_MESSAGE and DISPLAY_MESSAGES manage error text and message display; CHECK_STATUS_CHANGE, CHECK_NEW_STATUS_CHANGE, GET_DEFAULT_USER_STATUS, GET_SYSTEM_STATUS_TYPE, and GET_SYSTEM_STATUS_CODE handle AMS status logic.
- Security and messaging: IS_IN_MY_DIVISION and IS_IN_MY_AREA perform organizational access checks; SEND_WF_STANDALONE_MESSAGE sends standalone workflow notifications.
Tables Accessed
The package reads and writes a set of AMS, FND, HR, HZ, JTF, and MTL tables through APPS synonyms. AMS_ACT_LOGS and its _S sequence-backed tables, together with AMS_ACT_LOGS_TRANSACTION_ID_S, support the CREATE_LOG logging routines. AMS_CAMPAIGN_SCHEDULES and AMS_CUSTOM_SETUP_ATTR support campaign scheduling and setup-attribute resolution. AMS_MEDIA_TL supplies media names, AMS_SOURCE_CODES provides source codes, AMS_STATUS_ORDER_RULES and AMS_USER_STATUSES_TL drive status ordering and user-status meanings. FND_LOOKUP_VALUES backs the lookup validation and meaning-retrieval functions. HR_ALL_ORGANIZATION_UNITS_TL is used for organization-unit (operating unit) name resolution, relevant to the user's search term "operating_units_tbl." HZ_CUST_ACCOUNTS and HZ_PARTIES support party and customer name retrieval, JTF_RS_ROLE_RELATIONS supports resource-role lookups, and MTL_SYSTEM_ITEMS_KFV provides item description access.
Usage Notes
OZF_UTILITY_PVT is normally invoked indirectly. OZF and AMS forms, concurrent programs, and other PL/SQL packages call its logging, validation, and conversion routines rather than calling the package directly from user-facing customizations. Because the API is private and its history shows signature changes across releases, custom code should avoid depending on it; instead, customizations should use public OZF/AMS APIs or their own utility logic. Where debug output is required, callers should check LOGGING_ENABLED before invoking DEBUG_MESSAGE or LOG_MESSAGE to avoid unnecessary overhead. The package should be treated as internal plumbing that appears on the call stack of nearly every OZF/AMS transaction, not as a documented integration point.