Results for “dialog_type”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AMS_DIALOGS_ALL_B is the base (language-independent) table for the Dialog object in the Oracle Marketing (AMS) module, with the owner schema documented as AMS. It stores the master definition of every marketing dialog — the interactive, guided conversation flow presented to a customer or resource as part of a campaign, telemarketing script, or one-to-one marketing program. The table is registered as VALID against Oracle EBS 12.1.1 and 12.2.2 and carries 52 documented columns. It sits at the center of the dialog subsystem: the translated description text, the component composition of a flow, the URL parameter associations, and the response records all resolve back to a dialog row through DIALOG_ID.
From a Data Vault modeling perspective, the FK topology classifies this table as satellite-leaning. It holds descriptive attributes and status characteristics attached to a dialog entity, and it carries a set of foreign keys that reference independent entities (campaign, resource, application, currency, language, custom setup, user status, security group) rather than acting as a pure junction between them. The primary key AMS_DIALOGS_ALL_B_PK on DIALOG_ID is confirmed by a unique index AMS_DIALOGS_ALL_B_U1 on the same column, so the two coincide.
Key Information Stored
The surrogate primary key is DIALOG_ID, which also serves as the single documented business-key candidate via unique index AMS_DIALOGS_ALL_B_U1. All dependent child tables join on this column.
- DIALOG_ID — surrogate primary key and the join column for every child table.
- DIALOG_TYPE and PURPOSE — categorise and describe the nature of the dialog.
- PROGRAM_ID — FK to AMS_CAMPAIGNS_ALL_B; identifies the campaign or program the dialog belongs to.
- OWNER_ID — FK to JTF_RS_RESOURCE_EXTNS; the resource responsible for the dialog.
- APPLICATION_ID — FK to FND_APPLICATION, tying the dialog to a registered Oracle application.
- ORG_ID, SECURITY_GROUP_ID, and BUSINESS_UNIT_ID — multi-org and security-group context; SECURITY_GROUP_ID references FND_SECURITY_GROUPS.
- CUSTOM_SETUP_ID — FK to AMS_CUSTOM_SETUPS_B.
- USER_STATUS_ID — FK to AMS_USER_STATUSES_B, with SYSTEM_STATUS_CODE and STATUS_UPDATE_DATE recording status history.
- ACTIVE_FLAG, GLOBAL_FLAG, CONFIDENTIAL_FLAG, TEMPLATE_FLAG — control flags governing visibility, reuse, and confidentiality.
- START_DATE / END_DATE and START_PERIOD_NAME / END_PERIOD_NAME — validity window of the dialog.
- LANGUAGE_CODE, TRANSACTION_CURRENCY_CODE, FUNCTIONAL_CURRENCY_CODE — language and currency context, referencing FND_LANGUAGES and FND_CURRENCIES.
- BUDGET_AMOUNT_TC / BUDGET_AMOUNT_FC — budgeted amounts in transaction and functional currency.
- ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns for customer-defined extensions.
Common Use Cases and Queries
The most frequent access pattern is retrieving active dialogs for a given campaign, filtered by status and date window. A representative query joins the base table to its translation table:
- Locating dialogs by owner or resource: select DIALOG_ID, DIALOG_TYPE, PURPOSE from AMS_DIALOGS_ALL_B where OWNER_ID = :resource_id and ACTIVE_FLAG = 'Y'.
- Campaign dialog inventory: join PROGRAM_ID to AMS_CAMPAIGNS_ALL_B to report all dialogs attached to a campaign.
- Multilingual reporting: join AMS_DIALOGS_ALL_TL on DIALOG_ID to obtain translated names and descriptions.
- Status reporting: join USER_STATUS_ID to AMS_USER_STATUSES_B and filter by SYSTEM_STATUS_CODE to identify stale dialogs.
- Flow validation: left-join AMS_DLG_FLOW_COMPS_B to confirm that every active dialog has at least one component.
- Budget extracts: aggregate BUDGET_AMOUNT_TC by ORGANIZATION or by TRANSACTION_CURRENCY_CODE for marketing spend analysis.
- Security-scoped lists: constrain results by ORG_ID and SECURITY_GROUP_ID when operating in a multi-org environment.
Related Objects
The child tables that reference this object via DIALOG_ID are the most significant dependents:
- AMS_DIALOGS_ALL_TL — translation table holding language-specific text; join on DIALOG_ID.
- AMS_DLG_FLOW_COMPS_B — defines the components (questions, prompts, branches) that make up a dialog flow.
- AMS_DLG_FLOW_COMP_REL — relationships and sequencing between those flow components.
- AMS_DLG_URL_PARAM_ASSOCIATIONS — parameter mappings used when a dialog drives a web or landing-page URL.
- AMS_CPAG_DLG_RESPONS_B — captured responses linked to dialogs.
Parent (referenced) objects include AMS_CAMPAIGNS_ALL_B, JTF_RS_RESOURCE_EXTNS, FND_APPLICATION, FND_LANGUAGES, FND_CURRENCIES, AMS_CUSTOM_SETUPS_B, AMS_USER_STATUSES_B, and FND_SECURITY_GROUPS.
-
This stores the dialog object
-
This stores the dialog object
-
VIEW: AMS.AMS_DIALOGS_ALL_B# 12.2.2
-
VIEW: AMS.AMS_DIALOGS_ALL_B# 12.2.2
-
View: AMS_DIALOGS_VL 12.1.1
This is the view for dialog and it's also striped by language.
Not implemented in this database·Explore AMS module →
-
View: AMS_DIALOGS_VL 12.2.2
This is the view for dialog and it's also striped by language.
Not implemented in this database·Explore AMS module →
-
TABLE: AMS.AMS_DIALOGS_ALL_B 12.1.1
-
TABLE: AMS.AMS_DIALOGS_ALL_B 12.2.2
-
eTRM - AMS Tables and Views 12.2.2
This table is used to store tracking data for web advertisement and offer type schedules
-
eTRM - AMS Tables and Views 12.1.1
This table is used to store tracking data for web advertisement and offer type schedules