Search Results master_enabled_flag




Overview
Explore in AI Chat

Overview

The view APPS.AS_INTEREST_TYPES_VL is a translated (TL) validation view in Oracle E-Business Suite, belonging to the Oracle Trade Management / Sales Foundation schema (the AS prefix denotes the Sales/Interest Foundation application). Its primary role is to expose interest type definitions — the reference data that classifies contacts, leads, and other entities by their area of interest — in the language of the current session. The view conforms to the standard Oracle EBS "_VL" (view, translated) pattern: it joins a base table with its translation table and filters the translation by the language of the logged-in user.

For reporting and integration purposes, the view presents a denormalized, language-aware record of each interest type, including its identifier, descriptive name, description, and the flag columns that determine whether the interest type applies to company classifications, contacts, lead classifications, expected purchases, or current environments. The view also exposes the MASTER_ENABLED_FLAG column — the column referenced in the user's search — which is a renamed alias of the underlying ENABLED_FLAG. This makes the view the natural join target for any DBI or custom report that needs interest type descriptions alongside their enabled/disabled state.

Underlying Base Objects

According to the documented view text, AS_INTEREST_TYPES_VL is defined over two base objects:

  • AS_INTEREST_TYPES_B — the base table, aliased as B, holding non-translatable attributes (IDs, flags, audit columns, and product category references).
  • AS_INTEREST_TYPES_TL — the translation table, aliased as T, holding the language-specific INTEREST_TYPE name and DESCRIPTION.

Both are referenced through APPS synonyms. The join condition is B.INTEREST_TYPE_ID = T.INTEREST_TYPE_ID AND T.LANGUAGE = USERENV('LANG'), meaning only the translation row matching the current session language is returned. If no translation exists for the session language, the interest type will not appear in the result set — an important consideration for reports that run under a non-standard language or in environments where a translation row for that language is missing.

Key Columns

  • INTEREST_TYPE_ID — Primary key of the interest type; the foreign key referenced by many downstream association tables.
  • INTEREST_TYPE — The display name of the interest type, sourced from the translation table.
  • DESCRIPTION — The translated long description.
  • MASTER_ENABLED_FLAG — Alias of B.ENABLED_FLAG; indicates whether the interest type is active (Y) or inactive (N) at the master data level. This is the column the user searched for and is the canonical way to filter out disabled interest types in a query against the view.
  • COMPANY_CLASSIFICATION_FLAG, CONTACT_INTEREST_FLAG, LEAD_CLASSIFICATION_FLAG — Flags indicating the business contexts in which the interest type may be used (company classification, contact interest, or lead classification respectively).
  • EXPECTED_PURCHASE_FLAG, CURRENT_ENVIRONMENT_FLAG — Additional applicability flags used by demand/sales qualification features.
  • PRODUCT_CATEGORY_ID and PRODUCT_CAT_SET_ID — Optional references to a product category (and its category set) associated with the interest type.
  • Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically used in reporting and integration to resolve interest type names for entity associations (contacts, leads, companies) and to drive LOVs or validation in custom forms. The most frequent query filters on the master enabled flag, since consumers usually want only active interest types.

  • Retrieve all enabled interest types: SELECT interest_type_id, interest_type FROM apps.as_interest_types_vl WHERE master_enabled_flag = 'Y';
  • Join to associations to label records: SELECT a.contact_id, v.interest_type FROM as_contact_interests a, apps.as_interest_types_vl v WHERE a.interest_type_id = v.interest_type_id AND v.master_enabled_flag = 'Y';
  • Report by applicability: filter on contact_interest_flag, lead_classification_flag, or company_classification_flag to build context-specific pickers.
  • Integration/extract: pull all definitions with audit columns for a downstream system, or resolve interest_type_id values to display names during data migration.

Because the view is a translated view, joins should always be performed using INTEREST_TYPE_ID rather than the descriptive name, to avoid language- and duplicate-name-dependent errors.