Results for “is_vendor_admin_user”

8 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PVX_UTILITY_PVT is a private PL/SQL utility package body in the Oracle E-Business Suite 12.1.1 / 12.2.2 environment. The suffix "PVT" designates it as a private API, indicating that it is intended for internal consumption by other packages rather than direct invocation by customer extensions, though its widespread use across the applications makes it a de facto shared utility. Its primary business function is to centralize common validation, lookup, message-handling, timezone, resource, and history-logging logic used throughout the product modules that depend upon it. By consolidating these cross-cutting routines into a single package, the applications enforce consistent behavior for uniqueness checks, foreign-key validation, lookup resolution, and error messaging across many calling programs.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions that perform distinct utility roles. The validation routines include CHECK_FK_EXISTS, which verifies that a referenced foreign-key value exists; CHECK_LOOKUP_EXISTS, which confirms that a lookup code is defined in the lookup tables; CHECK_UNIQUENESS, which enforces uniqueness constraints prior to insert or update; and IS_Y_OR_N, which evaluates whether a flag holds a Y or N value. User-context functions include IS_VENDOR_ADMIN_USER, which determines whether the current user holds vendor administrator privileges, and GET_RESOURCE_NAME, which resolves a resource name from the resource extensions data. Message-handling routines include DEBUG_MESSAGE, ERROR_MESSAGE, and DISPLAY_MESSAGES, all of which integrate with the FND message stack through FND_MSG_PUB and FND_MESSAGE.

Timezone support is handled by GET_SYSTEM_TIMEZONE, GET_USER_TIMEZONE, and CONVERT_TIMEZONE, which together resolve and convert between system and user timezones. Lookup utilities include GET_LOOKUP_MEANING, which retrieves the meaning description for a lookup code. Contact and account resolution is served by GET_CONTACT_ACCOUNT_ID, which returns the account identifier associated with a contact role. History-tracking functions include CREATE_HISTORY_LOG, which writes to the history log base and parameter tables. Finally, GET_BUSINESS_DAYS and ADD_BUSINESS_DAYS provide calendar-aware calculations for business-day arithmetic.

Tables Accessed

The package references a number of application tables, largely through APPS synonyms. FND_NEW_MESSAGES is accessed as part of the message retrieval and display flow. HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, and HZ_PARTY_PREFERENCES support customer account, contact role, and party preference resolution, especially for the GET_CONTACT_ACCOUNT_ID routine. JTF_RS_RESOURCE_EXTNS, JTF_RS_ROLES_VL, and JTF_RS_ROLE_RELATIONS support resource and role resolution for GET_RESOURCE_NAME and user-privilege checks. PER_ALL_PEOPLE_F provides the person record used when resolving user context. PV_GE_HISTORY_LOG_B_S and PV_GE_HISTORY_LOG_PARAMS_S, together with PV_LOOKUPS, back the history logging and lookup routines. DUAL and PLITBLM are used for miscellaneous SQL and index-by table operations.

Usage Notes

Because PVX_UTILITY_PVT is not referenced by any database object but is referenced by seventy-one other packages, it is invoked indirectly through the application modules that depend upon it rather than through direct calls from forms or concurrent programs. This pattern indicates that it is a foundational utility layer, typically entered from higher-level public APIs and business logic routines. Custom code should generally avoid direct invocation and instead rely on the public APIs that call it, reserving direct use only where no alternative utility exists. Given its dependency on FND_API, FND_GLOBAL, and the HZ and JTF schemas, the package operates fully within the standard EBS security and message architecture.