Search Results as_interest_types_v




Overview
Explore in AI Chat

Overview

AS_INTEREST_TYPES_V is a read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the AS - Sales Foundation product family, which supplies the reference data used by Oracle Sales, TeleSales, and related CRM modules. The view presents interest type definitions in a single language, without any organization-specific (multi-org / operating unit) information. Its purpose is to expose the interest type reference list — the categories used to classify contacts, leads, and companies by their areas of interest — together with the flags that control how each interest type may be used in the application.

The view is a classic language-joined lookup view. It combines the base table that stores the language-independent columns with the translation table that stores the language-dependent text. Because the join is constrained to the session language, the view always returns description text in the language of the current user environment, making it suitable for forms, reports, and integration extracts that require display-ready values rather than raw IDs.

Underlying Base Objects

AS_INTEREST_TYPES_V is defined over two documented base objects, both referenced through APPS synonyms:

  • AS_INTEREST_TYPES_B — the base table holding the language-independent attributes of each interest type, including the primary key and the functional flags. It is aliased as B in the view text.
  • AS_INTEREST_TYPES_TL — the translation table holding the interest type name and description for each installed language. It is aliased as T in the view text.

The two tables are joined on INTEREST_TYPE_ID, with an additional predicate restricting rows to the current session language via USERENV('LANG'). Only interest types that have a translation row in the active language are therefore returned. The join is not organization-filtered, which is consistent with the view's stated design as non-org-specific reference data.

Key Columns

Common Use Cases and Queries

Typical uses include populating interest type list-of-values in custom forms and OAF pages, feeding CRM reports and extracts, and validating interest type identifiers during data conversion. A straightforward enabled-only query is:

SELECT interest_type_id, interest_type, description FROM apps.as_interest_types_v WHERE master_enabled_flag = 'Y' ORDER BY interest_type;

To retrieve only the types usable for lead classification:

SELECT interest_type_id, interest_type FROM apps.as_interest_types_v WHERE lead_classification_flag = 'Y' AND master_enabled_flag = 'Y';

For integration extracts, join to the base table when organization-specific or untranslated data is required, and reserve this view for language-sensitive, enabled-status filtering. Because the view is non-org-specific and language-scoped, it should not be used to determine operating-unit-level setup; that information is held elsewhere in the Sales Foundation data model.