Results for “ams_query_cond_disp_struct_vl”

28 results




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

Overview

AMS_QUERY_COND_DISP_STRUCT_VL is a read-only, language-aware (VL = "view with translation") database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the AMS (Marketing) product family and is a component of the Audience Workbench query-definition infrastructure. The view exposes the non-variant portion of a query condition — that is, the structural "body" of a condition whose elements remain constant regardless of whether the condition is rendered or evaluated in the context of an Administrative user or an End User. As documented in ETRM, the object "stores the body of the condition or in other words, has the non-variant information (condition parts that don't change between Admin and End User) in a query condition in Audience Workbench."

The distinguishing feature of this view for the "display_text" search is that it joins the translation table to surface the DISPLAY_TEXT column, the human-readable, language-specific label associated with a query condition display structure. This makes the view the preferred reporting and integration entry point when a user needs to present condition structure metadata in the session language rather than the raw base-table identifiers.

Underlying Base Objects

The view is defined over two APPS synonyms, which resolve to the corresponding AMS base tables:

  • AMS_QUERY_COND_DISP_STRUCT_ALL — the transactional/base table holding all non-translated structural attributes of query condition display structures. It supplies the column set prefixed with B in the view text (all columns except DISPLAY_TEXT).
  • AMS_QUERY_COND_DISP_STRUCT_TL — the translation table supplying language-specific content, aliased T in the view text, and contributing DISPLAY_TEXT.

The join predicate is B.QUERY_COND_DISP_STRUCT_ID = T.QUERY_COND_DISP_STRUCT_ID AND T.LANGUAGE = USERENV('LANG'). The USERENV('LANG') predicate restricts the result to the language of the current session, giving a single-row-per-structure result for the active locale. The view also synthesizes a ROW_ID from B.ROWID, exposing the physical row identifier of the base (ALL) record.

Key Columns

Common Use Cases and Queries

The view is typically used in Marketing reporting and integrations to enumerate the display labels and structural layout of Audience Workbench conditions without repeatedly coding the join to the translation table. A representative query retrieving display text for a given template is:

  • SELECT QUERY_COND_DISP_STRUCT_ID, QUERY_TEMPLATE_ID, TOKEN_SEQUENCE, TOKEN_TYPE, DISPLAY_TEXT, NON_VARIANT_VALUE FROM AMS_QUERY_COND_DISP_STRUCT_VL WHERE QUERY_TEMPLATE_ID = :p_template_id ORDER BY EXP_DISPLAY_SEQ, TOKEN_SEQUENCE;
  • Joining to the parent template to produce a full rendered condition listing for a locale:

SELECT s.QUERY_CONDITION_ID, s.TOKEN_SEQUENCE, s.DISPLAY_TEXT FROM AMS_QUERY_COND_DISP_STRUCT_VL s WHERE s.LANGUAGE = USERENV('LANG') AND s.SECURITY_GROUP_ID = -1 ORDER BY s.QUERY_CONDITION_ID, s.EXP_LOGIC_SEQ;

Because the view is filtered by USERENV('LANG'), results automatically reflect the session language; applications that must show all installed translations should query AMS_QUERY_COND_DISP_STRUCT_TL directly instead. For DBA verification, all four objects are documented as VALID in both EBS 12.1.1 and 12.2.2.