Search Results get_system_timezone

Overview

APPS.PVX_UTILITY_PVT is a private (PVT) PL/SQL utility package belonging to the Oracle Procurement and Supplier Portal product family within Oracle E-Business Suite. Its header indicates it was last shipped at version 120.4 and is a foundational "private" API intended for internal consumption by other packages rather than direct calls from end-user code. The package provides a reusable library of validation, lookup, time-zone, and history-logging helper routines that are shared across procurement and supplier-facing modules. Because it is classified as a PVT API, its procedures and functions are not guaranteed to be stable across patches and should be treated as internal implementation detail. The package is referenced by 71 other packages, confirming its role as a widely reused utility layer. It exposes 18 documented procedures and functions and operates against both FND and HZ/PER schemas via APPS synonyms.

Key Procedures and Functions

• CHECK_FK_EXISTS — verifies that a foreign-key value is valid against a nominated table and primary key, returning the standard FND_API true/false flag. An optional additional WHERE clause may be appended.
• IS_VENDOR_ADMIN_USER — determines whether the current user holds the vendor administrator role, returning FND_API true/false with no internal exception handling.
• CHECK_LOOKUP_EXISTS — confirms that a lookup code exists in a given lookup type.
• CHECK_UNIQUENESS — checks that a candidate value is unique within a target column or table.
• IS_Y_OR_N — validates that a value is a recognised Yes/No flag.
• DEBUG_MESSAGE, ERROR_MESSAGE, DISPLAY_MESSAGES — shared diagnostic and message-stack helpers used to write debug output, register errors, and surface accumulated messages to the caller.
• GET_LOOKUP_MEANING — retrieves the descriptive meaning for a lookup code.
• GET_SYSTEM_TIMEZONE and GET_USER_TIMEZONE — return the system-level and user-profile-level time zones respectively; these are the routines most commonly cited when resolving time-zone context.
• CONVERT_TIMEZONE — converts a supplied date/time between time zones.
• GET_RESOURCE_NAME — returns a resource (person) display name.
• GET_CONTACT_ACCOUNT_ID — resolves a contact to its associated customer account identifier.
• CREATE_HISTORY_LOG — writes an audit/history record, using the log parameter record and table types defined in the package specification.
• GET_BUSINESS_DAYS and ADD_BUSINESS_DAYS — calculate elapsed business days and derive a future date by adding business days.

Tables Accessed

The package reads and writes through APPS synonyms. FND_NEW_MESSAGES supports the message/debug routines. HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, and HZ_PARTY_PREFERENCES back the customer, contact, and preference lookups (GET_CONTACT_ACCOUNT_ID, IS_VENDOR_ADMIN_USER). JTF_RS_RESOURCE_EXTNS and JTF_RS_ROLE_RELATIONS support resource name and role resolution. PER_ALL_PEOPLE_F provides person data for resource lookups. PV_GE_HISTORY_LOG_B_S and PV_GE_HISTORY_LOG_PARAMS_S are the base and parameter history tables written by CREATE_HISTORY_LOG, while PLITBLM is an Oracle internal message table often joined for message retrieval. DUAL is used for singleton value expressions.

Usage Notes

PVX_UTILITY_PVT is a supply-only utility layer: it is intended to be called from other PL/SQL packages, Oracle Forms, OAF pages, and concurrent programs rather than invoked directly by end users. When a developer searches for get_system_timezone, the relevant entry point is GET_SYSTEM_TIMEZONE, typically paired with GET_USER_TIMEZONE and CONVERT_TIMEZONE to normalise timestamps across the application. Because the package is classified PVT and carries the deprecated "$Header ... ship" marker, customisations should avoid depending on its signatures; callers should instead use the public API that wraps these routines. Its 71 dependent packages confirm that most procurement and supplier-portal flows transitively rely on it, so any change to its behaviour can have wide-reaching effects across the 12.1.1 and 12.2.2 codebaselines.