Search Results delete_rank

Overview

AS_SALES_LEAD_RANKS_PUB is a public PL/SQL API in the Oracle E-Business Suite APPS schema that manages sales lead rank definitions used by Oracle Sales and Oracle TeleSales (Sales Foundation). Sales lead ranks provide a scoring band structure that classifies incoming sales leads by their computed score. Each rank carries a minimum score, a maximum score, an enabled flag, and descriptive text, allowing an organization to segment leads into categories such as Hot, Warm, or Cold, and to drive assignment, prioritization, and follow-up rules.

The package is declared AUTHID CURRENT_USER and serves as the sole supported interface for creating, maintaining, and removing rank rows in the underlying base table. It was originally authored in July 2000 and follows the standard Oracle Application Object Library (AOL) API programming model, with the current header indicating maintenance through release 11.5.x schema versions. The package is classified as a PUBLIC (PUB) API, meaning it is intended for use by other Oracle applications and by customer extensions rather than being restricted to internal package-private calls.

Key Procedures and Functions

The ETRM metadata documents three procedures. The package additionally declares a record type, sales_lead_rank_rec_type, which carries the rank identifier, audit columns, score boundaries, enabled flag, meaning, and description; this record is the primary payload for the create and update operations.

• CREATE_RANK — Inserts a new sales lead rank definition using the supplied rank record. It returns the generated rank identifier to the caller so that subsequent operations can reference the newly created row.
• UPDATE_RANK — Modifies an existing rank definition, including its score range, enabled status, and descriptive attributes, based on the rank record passed in by the caller.
• DELETE_RANK — Removes a sales lead rank identified by its rank identifier. This is the procedure most directly associated with the search term "delete_rank" and is the supported mechanism for retiring a rank definition.

All three procedures conform to the AOL API signature convention, accepting an API version, an initialization flag, a commit flag, and a validation level as inputs, and returning the standard x_return_status, x_msg_count, and x_msg_data error-handling outputs. Callers must inspect x_return_status and retrieve messages through the standard FND_MSG_PUB mechanism before assuming success. No parameter lists are reproduced here beyond what the documented metadata exposes.

Tables Accessed

The documented table reference is AS_SALES_LEAD_RANKS_B, accessed through an APPS synonym. This is the base (non-translated) table that stores rank definitions, and it is the target of the insert, update, and delete operations performed by the corresponding procedures. The package header comment states its purpose as adding ranks into both the base table and the _TL translation table, so the create and update paths also maintain the multilingual rank descriptions (MEANING and DESCRIPTION) held in the associated translation table.

Usage Notes

AS_SALES_LEAD_RANKS_PUB is referenced by two other packages within the APPS schema, indicating that it is called programmatically rather than only from the user interface. Typical invocation paths include the Sales Foundation setup forms where administrators define lead scoring bands, concurrent programs that seed or migrate rank data, and custom integration code that provisions rank definitions during implementation or data load.

When calling DELETE_RANK, the commit flag should be set to FND_API.G_FALSE when the call is part of a larger transaction, allowing the caller to control commit boundaries and rollback on error. Validation level should ordinarily remain at G_VALID_LEVEL_FULL so that score-range and referential checks are enforced before the delete proceeds. Because only the base table is documented in the metadata, implementers should verify translation-table dependencies and any existing lead-to-rank associations before deleting a rank, as removal may affect historical scoring references. As with all PUB APIs, direct DML against AS_SALES_LEAD_RANKS_B should be avoided in favor of these documented entry points.