Results for “ams_list_rules_all”

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

Overview

AMS_LIST_RULES_ALL is a Marketing (AMS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores user-defined rules used to identify duplicate accounts or contacts within a generated or imported list. In EBS list management and deduplication workflows, these rules determine how incoming list members are matched against existing records, and the weightage and field-level criteria defined by each rule drive the scoring logic that flags potential duplicates. The table is owned by the AMS schema and holds 19 documented columns.

From a Data Vault modeling perspective, the heuristic classification for this table is hub-leaning. This suggests modeling LIST_RULE_ID as a hub key representing the durable business concept of a deduplication rule, with descriptive and temporal attributes (such as weightage, validity dates, and flags) carried in an associated satellite. The two dependent child tables then behave as link or satellite structures referencing the hub.

Key Information Stored

• LIST_RULE_ID — surrogate primary key (constraint AMS_LIST_RULES_ALL_PK), uniquely identifying each rule.
• LIST_RULE_NAME — the business-key candidate; it participates in the unique index AMS_LIST_RULES_ALL_UK1 and is the column most commonly referenced by users searching for a specific rule.
• LIST_RULE_TYPE and LIST_SOURCE_TYPE — classify the rule by purpose and by source (generated versus imported list).
• WEIGHTAGE_FOR_DEDUPE — controls the relative weighting applied during duplicate scoring.
• ACTIVE_FROM_DATE / ACTIVE_TO_DATE — define the effective window during which the rule applies.
• ENABLED_FLAG and SEEDED_FLAG — indicate whether the rule is currently active and whether it is Oracle-seeded versus user-defined.
• ORG_ID — multi-org operating unit context; SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS controlling access.
• DESCRIPTION — free-text explanation of the rule.
• Standard Who/audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.
• ZD_EDITION_NAME — appears with LIST_RULE_ID in the unique index AMS_LIST_RULES_ALL_U1, supporting editioning.

Common Use Cases and Queries

Typical usage includes locating a rule by its business name, reviewing active rules for a given operating unit, and auditing which rules drive duplicate detection. A common lookup pattern is:

• SELECT LIST_RULE_ID, LIST_RULE_NAME, LIST_RULE_TYPE, ENABLED_FLAG FROM AMS_LIST_RULES_ALL WHERE LIST_RULE_NAME = :list_rule_name;
• SELECT * FROM AMS_LIST_RULES_ALL WHERE ENABLED_FLAG = 'Y' AND SYSDATE BETWEEN ACTIVE_FROM_DATE AND ACTIVE_TO_DATE ORDER BY LIST_RULE_NAME;
• Joining to AMS_LIST_RULE_FIELDS to retrieve the individual field criteria configured for a rule, and to AMS_LIST_RULE_USAGES to see where each rule has been applied.

These queries support configuration review, migration validation between 12.1.1 and 12.2.2, and reconciliation of rule definitions across environments.

Related Objects

• AMS_LIST_RULE_FIELDS — child table; joins on LIST_RULE_ID to define the fields evaluated by each rule.
• AMS_LIST_RULE_USAGES — child table; joins on LIST_RULE_ID to record where the rule is used.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID, providing security group assignment.
• Marketing list and deduplication processes consume these rules to score generated or imported list members.