Results for “ams_dlg_context_fields”

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

Overview

AMS_DLG_CONTEXT_FIELDS is a Marketing module table in the AMS schema that defines the context fields which dialog components must populate in the dialog context during dialog execution. Within Oracle EBS 12.1.1 and 12.2.2, it functions as the configuration backbone for Oracle Marketing and Advanced Outbound dialogs, binding each dialog question or flow component to the parameter names that must be resolved at runtime. The table governs how dialog engine components read and write dynamic values — such as respondent attributes, campaign properties, or session-level data — while a dialog is executing.

From a Data Vault modeling perspective, the heuristic classification for this table is satellite-leaning. It is most naturally modeled as a satellite attached to the dialog flow component hub and the question hub, since it records descriptive attributes (parameter names, data source metadata) about those business keys rather than representing a standalone transaction or association event. This is a modeling suggestion only; the physical EBS implementation is a conventional relational table with a surrogate primary key.

Key Information Stored

The table contains 13 documented columns. The most significant include:

• CONTEXT_FIELD_ID — the surrogate primary key, enforced by index AMS_DLG_CONTEXT_FIELDS_PK1 and also available via unique index AMS_DLG_CONTEXT_FIELDS_U1. This is the single business-key candidate documented for the object.
• FLOW_COMPONENT_ID — identifies the dialog flow component to which the context field belongs; foreign key to AMS_DLG_FLOW_COMPS_B.
• QUESTION_ID — the dialog question supplying or consuming the context value; foreign key to AMS_CPAG_QUESTIONS_B.
• PARAM_NAME — the parameter name under which the component reads or writes the value in the dialog context.
• DATA_SOURCE_TYPE_CODE — classifies the source from which the context value is derived (for example, a column, a literal, or a lookup).
• DATA_SOURCE_COLUMN_NAME — the specific source column referenced when the data source type resolves to a column.
• SECURITY_GROUP_ID — the Multi-Org access control identifier; foreign key to FND_SECURITY_GROUPS.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATED_DATE, LAST_UPDATE_LOGIN — the standard EBS audit who-columns maintained by the framework.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the OAF/BC4J stack.

Common Use Cases and Queries

The primary use case is diagnosing why a dialog fails to resolve a context value or why a component receives an unexpected parameter. A common query lists all context fields belonging to a given flow component:

• SELECT context_field_id, param_name, data_source_type_code, data_source_column_name FROM ams.ams_dlg_context_fields WHERE flow_component_id = :p_component_id;
• Joining to AMS_CPAG_QUESTIONS_B on QUESTION_ID to report the question prompt alongside the parameter name, useful when auditing dialog content.
• Filtering by SECURITY_GROUP_ID to respect Multi-Org visibility in custom reports.
• Checking AMS_DLG_CTX_FIELD_USES rows that reference a given CONTEXT_FIELD_ID to determine where a context field is actually consumed before changing or deleting it.
• Verifying OBJECT_VERSION_NUMBER consistency when investigating concurrent-update or lost-update errors reported by the dialog UI.

Related Objects

The following objects are most significant in relation to this table, based on the documented referential relationships:

• AMS_CPAG_QUESTIONS_B — referenced by AMS_DLG_CONTEXT_FIELDS.QUESTION_ID; supplies the dialog questions that drive context values.
• AMS_DLG_FLOW_COMPS_B — referenced by AMS_DLG_CONTEXT_FIELDS.FLOW_COMPONENT_ID; defines the dialog flow components requiring these context fields.
• FND_SECURITY_GROUPS — referenced by AMS_DLG_CONTEXT_FIELDS.SECURITY_GROUP_ID; enforces Multi-Org security.
• AMS_DLG_CTX_FIELD_USES — the dependent child table; its DCF_CONTEXT_FIELD_ID column references AMS_DLG_CONTEXT_FIELDS, recording where each context field is used within the dialog flow.

Because the table is an internal dialog-engine construct rather than a public API surface, maintenance and extension are typically performed through Oracle Marketing configuration screens rather than direct DML. Any changes should preserve referential integrity with the child AMS_DLG_CTX_FIELD_USES rows.