Search Results g_program_id

Overview

AS_SALES_GROUP_PVT is a private PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It forms part of the foundation layer of Oracle Sales, providing internal helper logic used to resolve and manage sales group definitions. Sales groups are the organizational constructs that associate sales representatives, resources, and territories so that revenue, quotas, and opportunities can be attributed to the correct selling entity. The package is classified as a PVT (private) API, meaning it is not intended for direct invocation by external consumers; it is designed to be called by other packages within the same functional family, such as the public sales group API and related sales foundation modules.

The source header identifies the file as asxvsgrb.pls, with the initial creation dated 6/19/98 and the last documented revision dated 11/06/2002 (version 115.4). The package has remained a stable, low-level utility component through the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The ETRM metadata for version 12.2.2 documents zero public procedures or functions, which is consistent with the package's private classification. All program units declared within the body are, by design, internal to the package and therefore not enumerated in the public API registry. No parameter lists are documented, and none should be assumed from the metadata.

The body opens with the declaration section defining the package constants and global variables listed below. These globals are populated at package initialization and are available to every internal routine for the duration of the session:

• G_PKG_NAME — constant identifying the package as 'AS_SALES_GROUP_PVT', used in error and debug messages.
• G_FILE_NAME — constant holding the source file name 'asxvsgrb.pls'.
• G_APPL_ID — application identifier, initialized from FND_GLOBAL.Prog_Appl_Id.
• G_LOGIN_ID — concurrent login identifier, initialized from FND_GLOBAL.Conc_Login_Id.
• G_PROGRAM_ID — concurrent program identifier, initialized from FND_GLOBAL.Conc_Program_Id.
• G_USER_ID — the current application user identifier, initialized from FND_GLOBAL.User_Id.
• G_REQUEST_ID — the concurrent request identifier, initialized from FND_GLOBAL.Conc_Request_Id.

Tables Accessed

The ETRM metadata records no table references through APPS synonyms for this package. This is expected for a private utility that performs validation, identifier resolution, and group-membership checks against sales group structures. Any underlying DML would be directed at the sales group base tables within the AS schema, accessed through the standard APPS synonym layer at runtime, but the documented metadata does not enumerate them.

Usage Notes

Because AS_SALES_GROUP_PVT is a private API, it should not be called directly from forms, concurrent programs, or customer extensions. It is invoked internally by the public sales group API layer whenever group definitions must be validated or resolved during opportunity, territory, or quota processing.

The most commonly referenced element of this package is the global G_PROGRAM_ID, which captures FND_GLOBAL.Conc_Program_Id at session startup. This value, together with G_REQUEST_ID and G_LOGIN_ID, supports audit and concurrent-processing context. Developers tracing a request identifier, program identifier, or user identifier to its source frequently search for "g_program_id" and arrive at this package, since the initialization block is a representative example of the standard EBS convention for capturing FND_GLOBAL session context. The remaining globals serve the same purpose: they expose the application, login, user, and request identifiers so that any internal routine can stamp audit columns or build diagnostic messages without re-querying FND_GLOBAL.