Results for “min_score”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AS_SALES_LEAD_RANKS_B table is a Sales Foundation (product family AS) base table that defines the various ranks a sales lead can hold within Oracle E-Business Suite. It resides in the OSM schema and stores the rank definitions that govern how leads are qualified and prioritized. It serves as the master reference for lead ranking criteria, exposing score boundaries (minimum and maximum) that map a lead's computed score to a discrete rank value.

Under the heuristic Data Vault classification mined from its foreign-key structure, this object is characterized as hub-leaning. This is a modeling suggestion rather than a deployment fact: the table carries a single-column surrogate primary key (RANK_ID) and serves as the unique parent of several dependent tables, which is consistent with hub-style reference data. Because EBS does not natively implement Data Vault, this classification should be treated only as an analytical lens for interpreting the table's role.

Key Information Stored

The table is defined with eleven documented columns in the ETRM 12.2.2 physical schema. The most significant are:

• RANK_ID — the surrogate primary key, enforced by the AS_SALES_LEAD_RANKS_B_PK constraint. This is the value propagated into all dependent tables.
• MIN_SCORE and MAX_SCORE — the lower and upper numeric boundaries of the score range that qualifies a lead for this rank.
• ENABLED_FLAG — controls whether the rank definition is active and selectable during lead qualification.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS that scopes the rank record for multi-organization or multi-business-group security.
• ZD_EDITION_NAME — the editioning column supporting online patching in EBS 12.2.x; it participates in the unique index AS_SALES_LEAD_RANKS_B_U1.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard WHO columns present on virtually every EBS transactional table.

The unique index AS_SALES_LEAD_RANKS_B_U1 is defined on (RANK_ID, ZD_EDITION_NAME). While RANK_ID is the surrogate key, the composite with the edition name is the documented business-key candidate that guarantees uniqueness across patch editions. Note that the translated, user-facing name and description of each rank are not stored in this base table; they reside in the companion table AS_SALES_LEAD_RANKS_TL.

Common Use Cases and Queries

Typical usage centers on lead qualification reporting and validation of rank definitions. The table is read whenever a lead's score must be resolved to a rank label. Because descriptive text lives in the _TL table, queries generally join the two.

• Resolving a lead to its rank: join leads to ranks on the LEAD_RANK_ID = RANK_ID relationship and then to the translation table for the display name.
• Validation of score bands: query MIN_SCORE and MAX_SCORE to detect overlapping or gapped ranges.
• Extract of active ranks: filter ENABLED_FLAG = 'Y' for lookup and reporting use.
• Security-scoped listings: join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to respect operating unit restrictions.

A representative pattern combines the base and translation tables, restricted to active ranks and constrained by SECURITY_GROUP_ID, with translation rows selected for the appropriate LANGUAGE.

Related Objects

• AS_SALES_LEAD_RANKS_TL — the translation table referencing RANK_ID; holds language-specific rank names and descriptions.
• AS_SALES_LEADS — the primary consumer, referencing ranks via LEAD_RANK_ID. This is the most common join path.
• FND_SECURITY_GROUPS — referenced by this table through SECURITY_GROUP_ID for data security scoping.
• WSH_TRIPS — references RANK_ID, indicating ranks are reused to sequence or order trips in shipping.
• WSH_TRIPS_INTERFACE — the open-interface staging counterpart, also referencing RANK_ID.
• WSH_DELIVERY_LEG_ACTIVITIES — references RANK_ID, applying the same ranking concept to delivery-leg activities.

These relationships show that, although the table originates in Sales Foundation, its rank identifiers are shared by outbound logistics objects, so changes to rank definitions can affect both lead management and shipping trip ordering.