Results for “ams_dlg_identify_rules_b”

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

Overview

AMS_DLG_IDENTIFY_RULES_B is a table in the AMS (Marketing) schema of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. Its documented purpose is to store the rules used to identify a user within the Oracle Marketing dialogue and campaign execution framework. Identification rules define the criteria by which the marketing engine resolves, matches, or selects an individual from a population during list generation, audience segmentation, or dialogue-based interaction processing. The _B suffix denotes the base table of an entity pair, indicating that a corresponding translation or extension table may exist for multi-language or additional attribute storage.

From a Data Vault modeling perspective, the foreign-key topology suggests a hub-leaning classification. The table carries a single-column surrogate primary key, RULE_ID, which serves as the durable business key anchor, while dependent child tables reference that key. This makes AMS_DLG_IDENTIFY_RULES_B a natural hub candidate, with the referencing tables playing the role of links or satellites in a dimensional or Data Vault reinterpretation. It is important to treat this as a heuristic recommendation rather than a documented Oracle design intent.

Key Information Stored

The table contains ten documented columns. The most significant are:

• RULE_ID — the surrogate primary key and the single business-key candidate, enforced by unique index AMS_DLG_IDENTIFY_RULES_B_U1 and primary key constraint AMS_DLG_IDENTIFY_RULES_B_PK1. Every downstream relationship is anchored to this value.
• RULE_TYPE — classifies the nature of the identification rule, allowing the application to distinguish rule behaviors during evaluation.
• SQL_QUERY — stores the query text or statement fragment that the marketing engine executes to identify the target user. This is the operational payload of the rule.
• SECURITY_GROUP_ID — scopes the rule to a specific security group, supporting multi-organization and data-segregation requirements; it references FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — supports optimistic locking and concurrency control during concurrent updates.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns recording who created and last modified the record and when.

The surrogate key RULE_ID is distinct from any user-facing identifier; there is no documented natural or alternate key beyond RULE_ID itself.

Common Use Cases and Queries

Typical scenarios include auditing the identification rules configured for a marketing program, tracing which rules are attached to a dialogue flow component, and reviewing the SQL logic used to resolve users.

• Listing rules by type: SELECT RULE_ID, RULE_TYPE, SQL_QUERY FROM AMS.AMS_DLG_IDENTIFY_RULES_B WHERE RULE_TYPE = :rule_type;
• Auditing recent changes: SELECT RULE_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM AMS.AMS_DLG_IDENTIFY_RULES_B WHERE LAST_UPDATE_DATE > :since;
• Tracing rules to flow components: SELECT fc.IDENTIFY_RULE_ID, r.RULE_ID FROM AMS_DLG_FLOW_COMPS_B fc JOIN AMS_DLG_IDENTIFY_RULES_B r ON fc.IDENTIFY_RULE_ID = r.RULE_ID;
• Resolving rule items: SELECT i.RULE_ID, i.* FROM AMS_DLG_IDENTIFY_ITEMS i WHERE i.RULE_ID = :rule_id;

Reporting use cases center on rule inventory, security-group scoping, and change-tracking for compliance reviews of campaign identification logic.

Related Objects

• AMS_DLG_FLOW_COMPS_B — references this table through IDENTIFY_RULE_ID, linking identification rules to dialogue flow components.
• AMS_DLG_IDENTIFY_ITEMS — child table referencing RULE_ID, holding the individual items that compose a rule.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, providing the security group context for each rule.
• AMS_DLG_IDENTIFY_RULES_TL — the conventional translation companion to a _B base table, should translations be enabled.
• FND_USER — the ultimate subject of identification, consulted indirectly when rules execute against application users.

These relationships confirm the table's central role as the rule definition anchor within the AMS dialogue identification subsystem.