Search Results param_value_2

Overview

The AMS_LIST_QUERIES_PARAM_VL view is a seeded, VALID database object owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the AMS (Marketing) product family and functions as a "validation" (VL) view — a localized presentation layer that joins a transactional base table to its translation table so that parameter definitions are surfaced alongside their language-specific display names.

In the AMS data model, a "list query" is a stored, reusable query object used by marketing and campaign functionality to retrieve lists of customers, contacts, or other entities. Each list query can be parameterized, and those parameters — including the values and conditions that drive the query — are persisted in the underlying parameter tables. The VL view exposes those parameters in the session's active language, making it suitable for both reporting and integration. For the user searching on condition_value, this view is the object where that column is exposed for query and reporting purposes.

Because it is a view rather than a table, no data is stored in AMS_LIST_QUERIES_PARAM_VL; it is a read-only projection intended for querying, forms, and concurrent/BI reporting.

Underlying Base Objects

Per the ETRM metadata, the view is defined over two objects, both referenced through synonyms in the APPS schema:

• AMS_LIST_QUERIES_PARAM — the base table holding the actual parameter records, keyed by LIST_QUERY_PARAM_ID and linked to a parent list query via LIST_QUERY_ID.
• AMS_LIST_QUERIES_PARAM_TL — the translation (TL) table holding the language-specific DISPLAY_NAME for each parameter.

The view is constructed with an inline SELECT that joins the two tables on LIST_QUERY_PARAM_ID and filters the translation table with T.LANGUAGE = USERENV('LANG'). This ensures only the display name matching the running session's language is returned. The view also derives a ROW_ID from the base table's ROWID to support forms-based row identification.

Key Columns

• LIST_QUERY_PARAM_ID — primary key of the parameter record; the join key between the base and translation tables.
• LIST_QUERY_ID — foreign key to the parent list query to which the parameter belongs.
• PARAMETER_NAME — the technical name of the parameter.
• PARAMETER_VALUE / PARAM_VALUE_2 — stored value(s) supplied for the parameter.
• CONDITION_VALUE — the condition associated with the parameter, used to qualify how the value is applied or evaluated.
• ATTB_LOV_ID — reference to a value-set/LOV definition used to constrain parameter entry.
• PARAMETER_ORDER — sequencing used to display or process parameters.
• DISPLAY_NAME — the translated label sourced from the TL table.
• OBJECT_VERSION_NUMBER — optimistic locking column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit (WHO) columns.

Common Use Cases and Queries

Typical uses include reporting on how list queries are parameterized, diagnosing why a marketing list query returns unexpected results, and integrating list-query definitions into external systems. Because the view is language-aware, it is preferred over querying the base table directly when display names are required.

Retrieve all parameters for a given list query:

• SELECT parameter_name, display_name, condition_value, parameter_value FROM ams_list_queries_param_vl WHERE list_query_id = :p_list_query_id ORDER BY parameter_order;

Locate parameters filtered by a specific condition value:

• SELECT list_query_id, parameter_name, condition_value FROM ams_list_queries_param_vl WHERE condition_value = :p_condition;

List parameters with their LOV binding and ordering:

• SELECT list_query_param_id, parameter_name, attb_lov_id, parameter_order FROM ams_list_queries_param_vl WHERE list_query_id = :p_list_query_id;

For bulk extraction, join the view to AMS_LIST_QUERIES_ALL_B (or its VL variant) on LIST_QUERY_ID to surface the parent query name alongside each parameter.