Search Results get_currentuser

Overview

AS_SALES_MEMBER_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its header declares AUTHID CURRENT_USER, meaning that when the package executes it resolves unqualified object references using the privileges and schema of the invoking user rather than the definer. This is a notable characteristic for a package catalogued in the APPS tier and has direct consequences for how it can be called and what it can see at runtime.

The package header comments state that its purpose is to serve as a private API for generic commodity APIs used across OSM — Oracle Sales and Marketing, the historical CRM component of the E-Business Suite. The package is classified as PVT (private), which in Oracle Applications naming convention signals that it is an internal implementation vehicle rather than a supported public interface for customer extensions. The header originates from asxvsmbs.pls (version 115.4, dated 2002/11/06), indicating that the source has been stable since the 11i era and has been carried forward unchanged into the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The package header documents a single procedure: Get_CurrentUser. No parameter list is published in the available metadata, and no signature details are recorded. Its purpose, consistent with the naming and with the OSM context, is to retrieve information about the currently logged-in application user and expose it to the surrounding private API layer. In the OSM schema, session identity is frequently required to determine sales-member ownership, territory assignment, and access filtering, so a lightweight private helper that resolves the current user avoids repeated FND_GLOBAL lookups scattered across the commodity APIs.

Because the procedure is declared in the package specification, it is callable from other PL/SQL units; because the package is private, Oracle does not document it as an extension point. The header revision history records only the initial creation by ALHUNG on 6/19/98.

Tables Accessed

The documented metadata records no table references via APPS synonyms for this package. That is consistent with the typical implementation of a current-user helper: such a routine normally relies on session context — for example values maintained by FND_GLOBAL (USER_ID, RESP_ID, RESP_APPL_ID) or the underlying FND_SESSION / session-management data — rather than on application business tables. Where the package touches dictionary objects, the AUTHID CURRENT_USER directive means resolution occurs under the caller's schema. No insert, update, or delete activity is documented.

Usage Notes

Given its private classification and its role as a commodity API within OSM, AS_SALES_MEMBER_PVT is expected to be invoked from other PL/SQL packages in the AS/OSM product family, and indirectly from Oracle Forms, concurrent programs, or OAF pages that call those packages. It is not intended to be called directly from custom code, and Oracle support does not guarantee the Get_CurrentUser signature or behaviour across releases. Customers requiring the current user in custom extensions should use the supported FND_GLOBAL.USER_ID / FND_GLOBAL.USER_NAME APIs instead.

The search term "get_currentuser" aligns with the single documented procedure in this package. Because the package is private and its specification exposes only that one routine, any investigation of the search term in an EBS 12.1.1 or 12.2.2 environment should treat this object as an internal OSM helper rather than a general-purpose identity API.