Search Results update_rank

Overview

The APPS.AS_SALES_LEAD_RANKS_PUB_W package is a public wrapper (denoted by the _PUB_W suffix) within the Oracle EBS Sales Foundation (AS) module. It exposes the business logic used to create and maintain sales lead ranks, which are the configurable ranking definitions applied to sales leads to express priority, score, or relative importance. Sales lead ranks drive downstream lead qualification and assignment behavior, allowing organizations to segment and prioritize leads consistently across the Sales application.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, and it relies on the standard Oracle EBS PL/SQL API conventions (API version, initialization of message list, commit control, validation level, and the standard x_return_status, x_msg_count, and x_msg_data output parameters). The header indicates it was last modified in 2006 (version 120.1) and it resides in the APPS schema.

Key Procedures and Functions

The documented package exposes two public procedures. In Oracle EBS the _PUB_W layer typically delegates to an underlying _PUB package, providing a stable public interface for both internal and external callers.

• CREATE_RANK — Creates a new sales lead rank definition. It accepts the standard EBS API control parameters (API version, message list initialization, commit flag, and validation level), returns the standard status and message outputs, and returns the identifier of the newly created rank through x_sales_lead_rank_id. The remaining positional parameters (referenced generically as p7_a0 through p7_a10) carry the rank attribute values; their default values (0-1962.0724 for numbers, fnd_api.g_miss_date for dates, and fnd_api.g_miss_char for character fields) are the standard EBS sentinel values that indicate "not supplied."
• UPDATE_RANK — Modifies an existing sales lead rank. It uses the same standardized control parameters and output parameters as CREATE_RANK, along with the same generic attribute parameters, whose sentinel defaults allow only the intended columns to be changed while unsupplied attributes remain untouched.

Tables Accessed

The ETRM metadata does not enumerate specific tables referenced through APPS synonyms. By inference from the package name and procedure signatures, the procedures operate against the sales lead ranks base table (the AS_SALES_LEAD_RANKS family of tables) and its associated translations, writing rank attribute values and returning the generated primary key. Standard EBS API infrastructure tables and views (such as those backing FND_API message handling) are also invoked implicitly through the shared API framework. Because the metadata lists no explicitly documented table references, integrators should confirm exact object dependencies against the deployed database.

Usage Notes

This package is typically invoked rather than called directly by end users. Common callers include:

• Oracle EBS forms and UI components in the Sales Foundation module that manage lead rank setup.
• Concurrent programs or batch processes that load or migrate lead rank configuration data.
• Custom PL/SQL integrations that need to programmatically create or update lead ranks as part of a data conversion or interface.

When calling the procedures, standard EBS API practices apply: initialize the message list as required, choose an appropriate validation level, and control transaction scope through the commit parameter. Callers should always inspect x_return_status and, on error, retrieve details through x_msg_count and x_msg_data. Because only CREATE_RANK and UPDATE_RANK are documented (no delete procedure is exposed here), record removal is handled elsewhere in the application.