Results for “ams_dlg_comp_type_outcome_vl”

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

Overview

The AMS_DLG_COMP_TYPE_OUTCOME_VL view is a marketing dictionary (AMS) object within Oracle E-Business Suite, exposed as a multilingual ("_VL") view over the outcome definitions used by dialog component types in Oracle Marketing. It presents translatable outcome metadata—such as outcome names and descriptions—joined with the non-translatable operational attributes held in the base table. The suffix "VL" indicates the view returns rows in the session's current language rather than in every installed language, which is standard behavior for Oracle's translated views.

Functionally, the view exposes the set of possible outcomes associated with each marketing dialog component type. Outcomes represent the discrete results that can be recorded when a customer interacts with a dialog component, forming part of the marketing execution and campaign response model in AMS. The view is primarily used by the marketing application's runtime and by reporting queries that need language-appropriate outcome labels for display or analysis.

Underlying Base Objects

According to the documented view text, AMS_DLG_COMP_TYPE_OUTCOME_VL is defined over two base objects: the non-translatable table AMS_DLG_COMP_TYPE_OUTCOME_B and the translation table AMS_DLG_COMP_TYPE_OUTCOME_TL. The two are joined on OUTCOME_ID, and the translation side is filtered by the language predicate T.LANGUAGE = USERENV('LANG'), which resolves the current session language. This is the canonical Oracle translated-view pattern: the "_B" table stores language-independent data, the "_TL" table stores language-dependent columns keyed by LANGUAGE, and the "_VL" view merges them for the session locale.

The metadata notes that the object is "not implemented in this database" and that no base objects were separately documented, so in a given environment the view and its base tables may not be physically present unless Oracle Marketing is licensed and installed with the relevant component types configured. Where implemented, referential integrity is maintained through OUTCOME_ID, which is the primary key shared between the two base tables.

Key Columns

• OUTCOME_ID — Primary key and join column between the base and translation tables; identifies a single outcome definition.
• OUTCOME_CODE — The internal, language-independent code for the outcome, used by application logic and integrations.
• COMPONENT_TYPE_ID — Foreign key to the dialog component type with which the outcome is associated; establishes the outcome-to-component-type relationship.
• OUTCOME_NAME — The translated, user-facing display name of the outcome, sourced from the translation table.
• DESCRIPTION — The translated descriptive text explaining the outcome's purpose, also sourced from the translation table.
• OBJECT_VERSION_NUMBER — Optimistic-locking version used by the Oracle framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard "WHO" audit columns recording creation and last-update metadata.

Common Use Cases and Queries

The view is most useful when a report or integration needs outcome definitions with localized labels. A typical query joins the view to the component type for display, or filters by OUTCOME_CODE for programmatic lookups. Because translation is resolved automatically, the same SQL returns language-appropriate results in each session.

• Listing all outcomes for a given component type:
  SELECT outcome_id, outcome_code, outcome_name, description FROM ams_dlg_comp_type_outcome_vl WHERE component_type_id = :p_component_type_id ORDER BY outcome_name;
• Resolving an outcome code to its display name:
  SELECT outcome_name FROM ams_dlg_comp_type_outcome_vl WHERE outcome_code = :p_outcome_code;
• Auditing recently changed outcome definitions:
  SELECT outcome_id, outcome_code, last_updated_by, last_update_date FROM ams_dlg_comp_type_outcome_vl WHERE last_update_date > SYSDATE - 30;

Because the view is confined to Oracle Marketing and may not be implemented in every instance, availability should be confirmed before building dependent reports or interfaces.