Results for “ams_dlg_ctx_field_uses”

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

Overview

AMS_DLG_CTX_FIELD_USES is a Marketing (AMS) module table in the Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. According to the ETRM metadata, its purpose is to capture the context fields used by different components. In practical terms, it acts as a cross-reference or association table that records which context fields — defined elsewhere — are consumed by which dialog or flow components. Instead of duplicating field definitions, it maps them, allowing a single context field to be reused across multiple components without redundancy.

The table is owned by the AMS schema and is documented as VALID. It carries nine columns and is governed by the primary key constraint AMS_DLG_FIELD_USES_PK1, defined over (CONTEXT_FIELD_ID, USED_BY_FLOW_COMP_ID). Based on the foreign-key structure mined from the metadata, this object is heuristic Data Vault classified as satellite-leaning: it holds descriptive association attributes and audit columns attached to the key combinations rather than serving purely as a hub or link. This classification is offered as a modeling suggestion, not a physical design mandate.

Key Information Stored

The most significant columns in AMS_DLG_CTX_FIELD_USES are:

• CONTEXT_FIELD_ID — part of the composite primary key; identifies the context field being referenced. It participates in the foreign key to AMS_DLG_CONTEXT_FIELDS via the column DCF_CONTEXT_FIELD_ID.
• USED_BY_FLOW_COMP_ID — the second part of the composite primary key; identifies the flow component that consumes the context field.
• SECURITY_GROUP_ID — supports multi-org/security-group filtering; it carries a foreign key to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications Framework (OAF) to detect concurrent updates.
• CREATED_BY, CREATION_DATE — standard audit columns recording who created the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns recording the most recent modification and its author.
• LAST_UPDATE_LOGIN — audit column capturing the login associated with the last update.

The composite primary key (CONTEXT_FIELD_ID, USED_BY_FLOW_COMP_ID) is the surrogate/associative identifier, while no separate business-key unique index is documented beyond this PK. The foreign-key columns to AMS_DLG_CONTEXT_FIELDS and FND_SECURITY_GROUPS serve as the business-key candidates that tie records to their defining parents.

Common Use Cases and Queries

This table is primarily queried for configuration analysis and dependency reporting. A typical scenario is determining which components use a given context field, or which context fields a given flow component depends on. Sample SQL patterns include:

• Join to the parent field definition to resolve field names: SELECT u.CONTEXT_FIELD_ID, c.FIELD_NAME, u.USED_BY_FLOW_COMP_ID FROM AMS.AMS_DLG_CTX_FIELD_USES u, AMS.AMS_DLG_CONTEXT_FIELDS c WHERE u.DCF_CONTEXT_FIELD_ID = c.CONTEXT_FIELD_ID;
• Filter by security group for multi-org reporting: WHERE u.SECURITY_GROUP_ID = :p_security_group_id.
• Detect unused context fields by anti-joining AMS_DLG_CONTEXT_FIELDS against this table to find definitions with no consuming components.
• Audit analysis using LAST_UPDATED_BY and LAST_UPDATE_DATE to track configuration drift.

Reporting use cases center on impact analysis — before changing a context field's definition, identifying all consuming flow components through this mapping prevents unintended breakage.

Related Objects

The most significant related objects, grounded in the documented foreign keys and primary key structure, are:

• AMS_DLG_CONTEXT_FIELDS — referenced via DCF_CONTEXT_FIELD_ID (foreign key). This is the parent definition table supplying the field master data.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID (foreign key). Provides security-group context for row visibility.
• Related AMS_DLG flow-component tables that define the USED_BY_FLOW_COMP_ID values, establishing which components consume fields.
• Associated AMS dialog/flow metadata views and OAF-based configuration pages that read this mapping for the Marketing application UI.

Because the metadata documents only two explicit foreign keys, additional dependencies should be verified against the live 12.1.1/12.2.2 data dictionary. The core relationship chain remains AMS_DLG_CONTEXT_FIELDS → AMS_DLG_CTX_FIELD_USES → flow components, with FND_SECURITY_GROUPS governing access context.