Search Results amv_chn




Overview
Explore in AI Chat

Overview

APPS.WF_AMV_CHN_ROLES is a reporting and integration view in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is part of the Workflow / Alert Management infrastructure and is exposed through the AMV (Alerts Management Views) layer, which supplies the Oracle Alert Manager and related workflow components with a uniform, flat interface over the various Alert source objects. The view presents Alert Manager channel definitions in a normalized form, converting each channel record into a single row conforming to the standard AMV column contract used by the Alert Manager lookup and selection engines.

Its documented role is to enumerate the active Alert channels — the delivery mechanisms (such as e-mail, fax, printer, or other dispatchers) through which an alert response can be routed — so that the Alert Manager can offer them as selectable values. Because the view is defined in the APPS schema and referenced through public synonyms, it is available to any concurrent program, form, or custom report operating in the EBS environment without additional grants.

Underlying Base Objects

The view is defined over three documented base objects, each accessed through its APPS synonym:

The join is performed on CHANNEL_ID between the _B and _TL tables, and on LANGUAGE_CODE = FNDL.LANGUAGE_CODE, with the additional filter FNDL.LANGUAGE_CODE = USERENV('LANG'). This guarantees that only the row corresponding to the user's current language is returned, avoiding duplicate rows from multi-language installations.

Key Columns

The view exposes a fixed sixteen-column projection, aliased to align with the Alert Manager's expected interface. The principal columns are:

  • Column 1 — a synthetic key formed as 'AMV_CHN'||':'||CHB.CHANNEL_ID, uniquely identifying the channel within the Alert Manager namespace.
  • Column 2 and 3 — CHT.CHANNEL_NAME, the translated channel name, repeated to satisfy the display and description positions of the interface.
  • Column 4 — the literal 'QUERY', indicating the access type used to populate the value list.
  • Columns 5 and 6 — NLS_LANGUAGE and NLS_TERRITORY from FND_LANGUAGES, giving the language context of the returned row.
  • Columns 7 and 8 — NULL placeholders.
  • Column 9 — the literal 'AMV_CHN', the source-object tag.
  • Column 10 — CHB.CHANNEL_ID, the numeric channel identifier used in foreign-key relationships.
  • Column 12 — CHB.STATUS, the enabled/disabled flag of the channel definition.
  • Column 15 — the literal 'N', a standard flag position.
  • Column 16 — the constant 6, a type/sequence discriminator.
  • Remaining positions — TO_DATE(NULL) containers for effective date range filtering, unused by this view.

Common Use Cases and Queries

This view is most often used when customizing or troubleshooting Alert Manager channel selection, and when building integration extracts that need the set of delivery channels valid for the current user's language. Because the language predicate is embedded, the view always returns exactly one language version.

  • List all channels available to the current session: SELECT * FROM APPS.WF_AMV_CHN_ROLES ORDER BY 10;
  • Retrieve only enabled channels: SELECT channel_id, channel_name FROM APPS.WF_AMV_CHN_ROLES WHERE status = 'A';
  • Join to alert definitions to confirm routable channels: use the numeric CHANNEL_ID (column 10) as the join key to the alert channel mappings.
  • Diagnostics: a missing channel in an Alert Manager list of values usually indicates a STATUS other than active in AMV_C_CHANNELS_B, or a missing translation row in AMV_C_CHANNELS_TL for the user's language.

Because the view is a simple, non-aggregated projection with an implicit language filter, it is inexpensive to query and safe to use in both online LOVs and batch extracts.