Search Results get_sales_groups




Overview
Explore in AI Chat

Overview

AS_SALES_GROUP_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Per its documented header comment, its stated purpose is to serve as a private API for generic commodity APIs used across OSM (Oracle Sales and Marketing / Order Settlement Management family of modules). The package is declared with AUTHID CURRENT_USER, meaning that at runtime its unqualified object references and privilege checks resolve under the invoking schema rather than under APPS. The header identifies it as a "PVT" classified package, an Oracle designation indicating that it is an internal, private API intended for use by other application code within the same product family rather than as a published interface for customer extensions.

The package name and its single documented procedure, Get_Sales_groups, indicate that its business function is to resolve and return sales group definitions used by generic commodity processing logic. Sales groups in this context represent organizational groupings of sales representatives or sales channels against which commodity or order-related transactions are associated. The source header carries a revision marker ($Header: asxvsgrs.pls 115.4 2002/11/06 ...), confirming that the object has been stable since the 11.5.x code line and is carried forward essentially unchanged into EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented package body exposes a single procedure relevant to the "get_sales_groups" search term:

  • Get_Sales_groups — The only procedure named in the package header comments. Its documented purpose, as reflected in the header block, is to support the generic commodity APIs by returning sales group information to calling code. The header does not publish a parameter list, so no signature should be assumed; consumers must inspect the actual package specification in the target instance to determine the exact argument order and types. The procedure operates in the context of the calling user due to the AUTHID CURRENT_USER clause, so effective privileges on any referenced tables derive from the invoking session.

ETRM metadata records zero separately documented procedures or functions within the package body, which is consistent with a very small, single-purpose private utility. No overloads, functions, or public constants are documented.

Tables Accessed

The ETRM metadata does not enumerate any tables referenced via APPS synonyms for this package. The source header likewise contains no embedded SQL or table references within the documented excerpt. Given the naming convention (AS_ prefix for the Oracle Sales and Marketing product family) and the procedure name, the package is presumed to read from sales group definition tables within the AS schema, such as the sales group header and line tables, in order to return the requested group records. However, because neither the ETRM record nor the published excerpt identifies specific tables, no table should be asserted as fact. Any implementation or debugging effort should verify actual table access by querying ALL_DEPENDENCIES or reviewing the full package body in the deployment instance.

Usage Notes

AS_SALES_GROUP_PVT is a private API. It is not intended for direct invocation from customer forms, concurrent programs, or custom extensions; the "PVT" classification signals that Oracle reserves the right to change its interface without notice. It is referenced by zero other packages according to the ETRM metadata, indicating either that its callers are not themselves APPS-owned packages captured in that dependency map, or that the procedure is invoked only from a small number of internal call sites. In practice, such commodity APIs are called during order or settlement processing flows where sales group attribution is required. Developers investigating the "get_sales_groups" behavior are advised to trace callers through dependency views and to treat the procedure as an internal helper whose contract may be altered across patches. When the full specification is available, that source should be treated as authoritative over any inferred signature.