Results for “ast_enty_attr_values_sl_v”

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

Overview

AST_ENTY_ATTR_VALUES_SL_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and classified under the AST (TeleSales) product family. In EBS 12.1.1 and 12.2.2, the object is registered in the ETRM repository with a status of VALID, indicating that its compiled definition resolves successfully against the underlying dictionary. The view presents entity attribute values that are specifically scoped to sales leads, exposing a single unified result set of attribute scoring and descriptive metadata.

The view is a sales-lead-specific ("_SL_") projection built over the general-purpose attribute value store. It filters the parent entity attribute values table to records where ENTITY = 'SALES_LEAD' and ENABLED_FLAG = 'Y', and joins translated attribute definitions from PV_ATTRIBUTES_TL. This makes it a convenient reporting and integration surface for lead qualification and scoring data without requiring consumers to re-implement the entity and language filters themselves. It is commonly referenced in TeleSales lead management, attribute-based lead scoring, and outbound integration extracts.

Underlying Base Objects

The documented base objects referenced by the view are two synonyms: PV_ENTY_ATTR_VALUES and PV_ATTRIBUTES_TL. Both are resolved through public or APPS synonyms in a standard EBS installation. PV_ENTY_ATTR_VALUES stores the per-attribute values assigned to an entity instance, including the numeric score and enablement flag. PV_ATTRIBUTES_TL is the translation table for attribute definitions, carrying the language-dependent NAME, SHORT_NAME, and DESCRIPTION columns.

The view text joins the two objects on ATTRIBUTE_ID. Restricting the join to A.ENTITY = 'SALES_LEAD' and A.ENABLED_FLAG = 'Y' limits the result to active sales lead attributes, while B.LANGUAGE = USERENV('LANG') restricts the definition rows to the session language. The resultant view therefore returns exactly one translated definition row per active lead attribute value. The view also exposes A.ROWID as ROW_ID, which is a common technique for providing an updatable-looking identifier to downstream tools.

Key Columns

• ROW_ID — the ROWID of the underlying PV_ENTY_ATTR_VALUES row; frequently used as the primary key by forms and integration frameworks.
• ENTY_ATTR_VAL_ID — the unique identifier of the entity attribute value record. This column corresponds to the search term "enty_attr_val_id" and is the primary identifier used to link to a specific lead attribute value.
• ENTITY — constrained to 'SALES_LEAD' in this view; indicates the entity class the attribute value belongs to.
• ATTRIBUTE_ID — foreign key to the attribute definition; the join column to PV_ATTRIBUTES_TL.
• PARTY_ID — the party identifier associated with the lead attribute value.
• ENTITY_ID — identifier of the specific entity instance (lead) to which the value applies.
• ATTR_VALUE — the captured attribute value, typically as text.
• SCORE — numeric score assigned to the attribute value, used in lead scoring and qualification.
• ENABLED_FLAG — constrained to 'Y' in this view; indicates the attribute value is active.
• NAME, SHORT_NAME, DESCRIPTION — language-specific attribute definition text from PV_ATTRIBUTES_TL.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER support auditing and optimistic locking.

Common Use Cases and Queries

The view is typically used to report lead attribute values with their translated definitions, to extract scoring data for lead prioritization, or to feed external systems. A representative query retrieving all active attribute values for a given lead is:

• SELECT enty_attr_val_id, entity_id, party_id, attribute_id, name, attr_value, score FROM apps.ast_enty_attr_values_sl_v WHERE entity_id = :p_entity_id ORDER BY name;

To aggregate scoring by lead:

• SELECT entity_id, party_id, SUM(score) total_score FROM apps.ast_enty_attr_values_sl_v GROUP BY entity_id, party_id ORDER BY total_score DESC;

To resolve a specific attribute value by its identifier:

• SELECT enty_attr_val_id, name, attr_value, score FROM apps.ast_enty_attr_values_sl_v WHERE enty_attr_val_id = :p_enty_attr_val_id;

Because ENTITY and ENABLED_FLAG are hard-coded filters, callers cannot retrieve disabled or non-sales-lead attributes through this view; they must query PV_ENTY_ATTR_VALUES directly for those cases. Similarly, the language filter means results follow the session language, so multilingual reports should set NLS appropriately before querying.