Results for “sales_lead”

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

Overview

APPS.AST_ENTY_ATTR_VALUES_SL_V is a reporting view in the Oracle E-Business Suite (EBS) ETRM (Enterprise Territory and Resource Management, historically marketed as Oracle Sales and Marketing / Oracle TeleSales) schema. It exposes a filtered, user-language-resolved slice of the attribute-value data used to score and qualify sales leads. Specifically, the view restricts the underlying attribute-value records to those belonging to the entity SALES_LEAD and that are currently enabled (ENABLED_FLAG = 'Y'), and it joins in the translatable attribute definitions for the session's language.

The view does not model a business transaction of its own; rather it is a denormalized convenience layer over ETRM's generic attribute framework. ETRM stores lead-scoring and qualification attributes in a flexible name/value model so that administrators can define custom scoring criteria without schema changes. This view flattens that model into readable rows (attribute value plus its name, short name, and description) for a single entity type. It is the "SL" (sales lead) counterpart to other entity-specific views in the same family.

Underlying Base Objects

The view is defined over two documented base objects, both consumed in APPS through synonyms:

• PV_ENTY_ATTR_VALUES (alias a) — the core entity/attribute value table holding one row per (entity, attribute, party) attribute instance, together with its value, score, and enabled flag.
• PV_ATTRIBUTES_TL (alias b) — the translated attribute definitions table, joined on ATTRIBUTE_ID, supplying the language-specific NAME, SHORT_NAME, and DESCRIPTION.

Joins and filters applied by the view definition:

• a.attribute_id = b.attribute_id — pairs each value with its definition.
• a.entity = 'SALES_LEAD' — constrains to the sales-lead entity only.
• a.enabled_flag = 'Y' — excludes disabled/inactive attribute values.
• b.language = userenv('LANG') — returns attribute text in the current session language.

The view also exposes a.rowid as ROW_ID, which is useful for joined-update and DML-through-view scenarios.

Key Columns

• ENTY_ATTR_VAL_ID — primary identifier of the attribute-value record.
• ENTITY — entity discriminator; always 'SALES_LEAD' in this view.
• ENTITY_ID — identifier of the owning entity instance (e.g., the lead).
• ATTRIBUTE_ID — foreign key to the attribute definition.
• PARTY_ID — party associated with the attribute value, when applicable.
• ATTR_VALUE — the stored attribute value used in lead scoring/qualification.
• SCORE — numeric score contributed by the attribute.
• ENABLED_FLAG — always 'Y' as filtered.
• NAME / SHORT_NAME / DESCRIPTION — language-resolved attribute labels from PV_ATTRIBUTES_TL.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical uses include lead-scoring reports, qualification dashboards, and integration extracts from ETRM to downstream analytics. Attribute and score values are consumed read-only.

Listing all enabled sales-lead attributes and values:

SELECT enty_attr_val_id, entity_id, name, attr_value, score FROM apps.ast_enty_attr_values_sl_v;

Reviewing score contribution per attribute name:

SELECT name, COUNT(*) instances, SUM(score) total_score FROM apps.ast_enty_attr_values_sl_v GROUP BY name ORDER BY total_score DESC;

Enriching a specific lead by its entity identifier:

SELECT entity_id, name, attr_value, score FROM apps.ast_enty_attr_values_sl_v WHERE entity_id = :lead_id;

Because the view applies its own language and entity filters, applications should not re-apply those predicates; custom consumers should never write back through this view unless performed via the documented base objects.