Search Results validate_rank_meaning




Overview
Explore in AI Chat

Overview

APPS.AS_SALES_LEAD_RANKS_PVT is a private PL/SQL package within the Oracle E-Business Suite Sales Foundation (AS) module. It implements the internal business logic that supports the public sales lead rank application programming interface exposed by AS_SALES_LEAD_RANKS_PUB. The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privilege set of the invoking user, and it operates against the rank definition tables AS_SALES_LEAD_RANKS_B, AS_SALES_LEAD_RANKS_TL, and AS_SALES_LEAD_RANKS_S.

Sales lead ranks classify sales leads into scoring bands so that sales organizations can prioritize follow-up activity. Each rank record carries a minimum score, a maximum score, an enabled flag, a rank code, and a translatable meaning and description. AS_SALES_LEAD_RANKS_PVT encapsulates the validation and maintenance of these band definitions, including the maintenance of lead scores that are recalculated when rank boundaries change. Its header history dates the package to the year 2000, and it remains part of the standard 12.1.1 and 12.2.2 installation.

Key Procedures and Functions

  • VALIDATE_SCORE_RANGE — Verifies that the minimum and maximum score values supplied on a rank record form a coherent range and do not conflict with existing rank definitions. It accepts a validation mode and a flag indicating whether the older ranking engine is in use.
  • VALIDATE_RANK_MEANING — Validates the meaning and description attributes of a rank record, ensuring that the user-entered text satisfies the business rules for a rank definition.
  • CREATE_RANK — Inserts a new sales lead rank into the base and translation tables and returns the generated rank identifier to the caller. It follows the standard EBS API conventions for API version, message list initialization, commit control, and validation level.
  • UPDATE_RANK — Modifies an existing rank definition, reapplying the same range and meaning validations before the update is persisted.
  • DELETE_RANK — Removes a rank definition from the rank tables when it is no longer required, subject to the same validation framework.
  • UPDATE_LEAD_RANK_SCORE — The procedure most often sought by developers and administrators. It reassigns or recalculates the rank score associated with sales lead records, ensuring that leads are mapped to the correct scoring band after rank definitions are created, changed, or deleted. It is the mechanism by which lead data in AS_SALES_LEADS is kept consistent with the rank configuration.
  • WRITE_LOG — An internal diagnostic routine used to record processing or error information during rank maintenance operations.

Tables Accessed

  • AS_SALES_LEAD_RANKS_B — The base table holding rank definitions, including score boundaries, enabled flag, and rank code.
  • AS_SALES_LEAD_RANKS_TL — The translation table storing language-specific meaning and description text for each rank.
  • AS_SALES_LEAD_RANKS_S — The sequence table used to generate unique rank identifiers during creation.
  • AS_SALES_LEADS — The sales lead table whose rank score values are updated by UPDATE_LEAD_RANK_SCORE.
  • DUAL — Used for single-row queries and validation lookups within the package logic.

Usage Notes

Because AS_SALES_LEAD_RANKS_PVT is classified as a private package, it is not intended to be called directly from custom code. The supported entry point is the public package AS_SALES_LEAD_RANKS_PUB, which in turn invokes the private procedures described above. The "Sales Lead Ranks" setup window in Oracle Sales or Oracle TeleSales calls the public API to create, update, and delete rank definitions, and those calls delegate validation and persistence to this package.

The UPDATE_LEAD_RANK_SCORE procedure is typically invoked as part of rank maintenance processing rather than by end users directly. When rank score ranges change, existing leads must be re-evaluated so that their assigned rank reflects the new configuration; this procedure performs that reassignment. The package is referenced by one other package in the ETRM inventory, confirming its role as a supporting component rather than a top-level API. Customizations that need to maintain rank consistency should invoke AS_SALES_LEAD_RANKS_PUB, or where no public equivalent exists, be prepared to handle the standard EBS API parameters for message list handling and commit control, and should verify compatibility against the specific 12.1.1 or 12.2.2 patch level in use.