Results for “token_sequence”

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

Overview

The AMS.AMS_QUERY_COND_DISP_STRUCT_ALL table is a Marketing (AMS) module data object within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the structural definition of query conditions used by Audience Workbench, holding the "body" of each condition — specifically the non-variant portions that remain constant between the Admin-facing setup and the End User view. In effect, it captures the reusable, shared definition of a condition so that audience-building logic does not have to be duplicated across user contexts.

Multi-lingual/multi-tenant style naming (_ALL) and the presence of ZD_EDITION_NAME indicate the table participates in Oracle's editioning and MLS-style data model, storing edition-aware rows rather than a single logical record.

Under the heuristic Data Vault classification supplied in the metadata, this table is modeled as standalone. In Data Vault terms this suggests treating it as a satellite or standalone reference rather than a pure hub or link — it carries descriptive, non-key attributes anchored by a surrogate identity, with limited outbound relationships.

Key Information Stored

The table contains 24 columns. The most significant are:

• QUERY_COND_DISP_STRUCT_ID — The surrogate primary key identifying each condition display structure row.
• ZD_EDITION_NAME — Edition discriminator; combined with the PK it forms the unique index AMS_QUERY_COND_DISP_U1, making (QUERY_COND_DISP_STRUCT_ID, ZD_EDITION_NAME) the business-key candidate.
• QUERY_TEMPLATE_ID — Reference to the parent query template the condition belongs to.
• QUERY_CONDITION_ID — Identifies the specific condition this structure describes.
• TOKEN_TYPE and TOKEN_SEQUENCE — Define the type and ordering of tokens (building blocks) in the condition expression.
• AVAILABLE_LOV_ID — The list-of-values source associated with the condition, used for value selection.
• VALUE_TYPE and DATA_TYPE — Describe the semantic and technical type of the condition value.
• NON_VARIANT_VALUE — The core payload: the portion of the condition that does not change between Admin and End User contexts.
• QUERY_ALIAS_ID — Foreign key to AMS_QUERY_ALIAS, tying the condition to a query alias.
• EXP_LOGIC_SEQ and EXP_DISPLAY_SEQ — Control expression logic ordering and display ordering respectively.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, enforcing data security partitioning.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, and concurrent program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

This table is primarily a configuration backbone for Audience Workbench. Typical scenarios include diagnosing why an audience condition renders or evaluates incorrectly, tracing token composition, and reporting on condition structures for a template.

Retrieve all condition structures for a template:

• SELECT query_cond_disp_struct_id, query_condition_id, token_type, token_sequence, non_variant_value FROM ams_query_cond_disp_struct_all WHERE query_template_id = :p_template_id ORDER BY token_sequence;

Join to the alias for readability:

• SELECT s.query_condition_id, a.alias_name, s.non_variant_value FROM ams_query_cond_disp_struct_all s, ams_query_alias a WHERE s.query_alias_id = a.query_alias_id;

Reporting use cases include auditing non-variant payloads across templates, verifying edition-specific definitions via ZD_EDITION_NAME, and validating security group coverage.

Related Objects

• AMS_QUERY_ALIAS — joined via QUERY_ALIAS_ID → AMS_QUERY_ALIAS.QUERY_ALIAS_ID.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID.
• Query Template objects referenced by QUERY_TEMPLATE_ID (Audience Workbench template definitions).
• Query Condition objects referenced by QUERY_CONDITION_ID — the variant counterpart to this non-variant structure.
• FND_LOVS / LOV definitions referenced by AVAILABLE_LOV_ID.
• FND_CONCURRENT_REQUESTS — indirectly via REQUEST_ID for concurrent program traceability.
• Audience Workbench collection/segment objects that consume condition structures at runtime.