Search Results ams_dm_models_vl




Overview
Explore in AI Chat

Overview

AMS_DM_MODELS_VL is a multi-lingual (MLS) view owned by the APPS schema in Oracle E-Business Suite. It resides in the AMS (Marketing) product family and exposes data mining model definitions in a language-aware form suitable for reporting, integration, and concurrent processing. The "_VL" suffix follows the standard Oracle EBS naming convention for views that join a transactional base table (the "_B" or "_ALL_B" table) to its translation table (the "_TL" table), returning a single denormalized row per entity using the session language.

In ETRM 12.2.2 the view is documented as VALID. Its role is to present the descriptive, translatable attributes of a data mining model — namely MODEL_NAME and DESCRIPTION — alongside the operational and technical attributes stored on the base table. Because Oracle Marketing uses data mining models to drive predictive scoring, target group selection, and list generation, this view serves as the principal read interface for model metadata in custom reports and interfaces.

Underlying Base Objects

The view is defined over two synonyms resolving to the underlying AMS tables:

  • AMS_DM_MODELS_ALL_B — the base (business) table holding non-translatable model attributes and the model identifier.
  • AMS_DM_MODELS_ALL_TL — the translation table holding MODEL_NAME and DESCRIPTION per installed language.

The join is performed as:

SELECT B.ROWID ROW_ID, B.MODEL_ID, ... B.ATTRIBUTE15, T.MODEL_NAME, T.DESCRIPTION FROM AMS_DM_MODELS_ALL_B B, AMS_DM_MODELS_ALL_TL T WHERE B.MODEL_ID = T.MODEL_ID AND T.LANGUAGE = USERENV('LANG')

The view text therefore imposes two conditions that callers must respect: every base row is matched to exactly one translation row, and the translation row returned corresponds to the language of the current session as returned by USERENV('LANG'). The ALL prefix indicates the base table is not itself partitioned by operating unit at the table level; the ORG_ID column on the view carries the multi-org context.

Key Columns

Common Use Cases and Queries

The view is typically queried through the Apps database user or APPS read-only responsibilities. A basic listing of active models in the session language is:

SELECT model_id, model_name, model_type, status_code, last_build_date FROM apps.ams_dm_models_vl WHERE status_code = 'ACTIVE' ORDER BY model_name;

Restricting to a specific operating unit and joining to the target definition:

SELECT v.model_name, v.target_field, v.target_type, v.total_records FROM apps.ams_dm_models_vl v WHERE v.org_id = :org_id AND v.results_flag = 'Y';

Because MODEL_NAME and DESCRIPTION are language-specific, applications running under a non-English session automatically receive the translated values, provided the corresponding _TL rows exist. Integrations that must retrieve all languages should query AMS_DM_MODELS_ALL_TL directly rather than this view. Reports requiring only technical attributes may read AMS_DM_MODELS_ALL_B to avoid the translation join; the _VL view is preferred whenever user-facing names or descriptions are required.