Results for “aml_rule_applied_attrs”

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

Overview

AML_RULE_APPLIED_ATTRS is an Oracle Marketing (AMS) transactional table that records the winning rule log produced during lead evaluation. When the Marketing rule engine scores and qualifies leads, it evaluates one or more candidate rules and selects a winner; the winning rule's individual attribute-level conditions are then persisted in this table. Each row represents a single attribute comparison (an attribute, an operator, and the values compared) that contributed to the winning rule decision for a given lead evaluation instance.

The object resides in the AMS schema and is classified as VALID in the documented EBS 12.1.1 / 12.2.2 ETRM metadata. Its heuristic Data Vault classification is standalone, mined from the foreign-key structure. In Data Vault modeling terms, this suggests the table behaves as an appended, immutable-style record rather than a true hub or link: it carries detail attributes tied to a parent event but does not itself act as a shared business key subject area. A satellite-style treatment around the parent "rule applied" event is therefore the most natural modeling suggestion.

Key Information Stored

The table is documented with 18 columns on the 12.2.2 physical schema. The most important of these are:

• RULE_APPLIED_ATTR_ID — surrogate primary key for the attribute-level record.
• ENTITY_RULE_APPLIED_ID — foreign key to PV_ENTITY_RULES_APPLIED, tying the attribute row to the parent winning-rule application event. This is the principal business join key.
• ATTRIBUTE_ID — identifies the lead attribute that was evaluated.
• OPERATOR — the comparison operator applied during evaluation (for example equals, greater than, between).
• ATTRIBUTE_VALUE and ATTRIBUTE_TO_VALUE — the rule's configured value(s); the "to" variant supports range operators.
• LEAD_VALUE — the actual lead attribute value captured at evaluation time.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group access control.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the AMS framework.

Standard EBS audit columns are also present: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. Concurrent-program lineage is captured via REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, which is significant because lead evaluation is typically executed from a batch/conc program.

Common Use Cases and Queries

Typical scenarios include auditing why a lead qualified, reproducing a historical rule decision, and reporting on the distribution of rule outcomes across campaigns. A representative join to the parent table follows:

• SELECT a.ENTITY_RULE_APPLIED_ID, a.ATTRIBUTE_ID, a.OPERATOR, a.ATTRIBUTE_VALUE, a.ATTRIBUTE_TO_VALUE, a.LEAD_VALUE FROM AMS.AML_RULE_APPLIED_ATTRS a WHERE a.ENTITY_RULE_APPLIED_ID = :p_id;
• Security-filtered reporting: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict rows to the appropriate operating unit or security group.
• Batch troubleshooting: filter on REQUEST_ID and PROGRAM_APPLICATION_ID to inspect the attribute-level output of a specific lead-evaluation concurrent request.
• Rule-effectiveness analysis: group by ATTRIBUTE_ID and OPERATOR to determine which rule conditions most frequently drive winning outcomes.

Related Objects

The most significant related objects are:

• PV_ENTITY_RULES_APPLIED — parent of the winning-rule application; joined on ENTITY_RULE_APPLIED_ID = PV_ENTITY_RULES_APPLIED.ENTITY_RULE_APPLIED_ID.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for access control.
• Additional AMS rule and lead tables (AML_* / PV_*) supply rule definitions and lead records referenced by ATTRIBUTE_ID and the parent application event.
• Standard EBS concurrent-program and audit tables are referenced indirectly through REQUEST_ID and the WHO columns.