Results for “aml_monitor_log”

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

Overview

AML_MONITOR_LOG is a transaction history table in the Oracle E-Business Suite Marketing module (AMS). It resides in the AMS schema and carries a VALID status across EBS 12.1.1 and 12.2.2. The table records the historical usage of monitor rules, capturing each instance in which a monitor condition is evaluated against a sales lead. Its primary purpose is to provide an auditable trail of monitor rule execution, enabling administrators and marketing analysts to determine how specific leads interact with a given monitor and how frequently monitor rules fire across the lead base.

Within the broader EBS Marketing architecture, this object sits at the intersection of campaign monitoring logic and lead management. Monitors in AMS are rule-driven constructs that watch lead activity and trigger actions when defined conditions are met. AML_MONITOR_LOG preserves the outcome of each such evaluation, making it a reference source for troubleshooting monitor behavior, validating rule configuration, and performing historical analysis of monitor-driven engagement.

Heuristically mined from its foreign key structure, the object is classified as a standalone data vault entity. It does not participate in a composite hub-and-link pair in the strictest sense; instead it functions as a transactional log anchored by a single surrogate key. Practitioners modeling this table for downstream analytics may treat it as an event-style table whose grain is one row per monitor evaluation per lead.

Key Information Stored

The table contains 33 documented columns. The most operationally significant are outlined below.

• MONITOR_LOG_ID — The surrogate primary key, enforced by AML_MONITOR_LOG_PK and additionally covered by the unique index AML_MONITOR_LOG_U1. It uniquely identifies each monitor log entry.
• MONITOR_CONDITION_ID — Foreign key to AML_MONITOR_CONDITIONS. Identifies the specific monitor condition that was evaluated and logged.
• SALES_LEAD_ID — Foreign key to AS_SALES_LEADS. Identifies the sales lead against which the monitor fired, which is the core linkage enabling "how leads use a monitor" analysis.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS. Restricts row visibility according to the security model in force, which is essential for multi-org and role-based reporting.
• MONITOR_ACTION — Records the action taken or resulting state when the monitor condition was satisfied, providing the outcome dimension of the log.
• RECIPIENT_ROLE and RECIPIENT_RESOURCE_ID — Identify the role and resource that received or was associated with the monitor outcome.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Standard concurrent program context columns, indicating which batch process generated the log entry.
• OBJECT_VERSION_NUMBER — Supports optimistic locking and row version control.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking who created and last modified each record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The descriptive flexfield segment set, available for customer-specific extensions.

MONITOR_LOG_ID is the surrogate primary key. There is no separately documented natural or business-key unique index beyond AML_MONITOR_LOG_U1, which mirrors the primary key column.

Common Use Cases and Queries

Typical usage centers on auditing monitor activity, diagnosing why a lead did or did not trigger an action, and reporting on monitor effectiveness. A frequent pattern joins the log to its parent condition and lead:

SELECT l.MONITOR_LOG_ID, l.MONITOR_CONDITION_ID, l.SALES_LEAD_ID, l.MONITOR_ACTION, l.CREATION_DATE
FROM AMS.AML_MONITOR_LOG l
WHERE l.MONITOR_CONDITION_ID = :condition_id
ORDER BY l.CREATION_DATE DESC;

To measure how leads consume a specific monitor, aggregate by lead and condition. To review activity within a security context, filter on SECURITY_GROUP_ID. Because REQUEST_ID and PROGRAM_ID are available, concurrent program runs can be reconstructed to isolate entries produced by a particular batch. Reporting layers commonly surface frequency of monitor actions, recipient role distribution, and time-series trends of monitor firing, using CREATION_DATE as the temporal axis.

Related Objects

• AML_MONITOR_CONDITIONS — Joined via MONITOR_CONDITION_ID; the defining rule record.
• AS_SALES_LEADS — Joined via SALES_LEAD_ID; the lead subject of each monitor evaluation.
• FND_SECURITY_GROUPS — Joined via SECURITY_GROUP_ID; governs row-level access.
• FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS — Joinable through REQUEST_ID and PROGRAM_ID/PROGRAM_APPLICATION_ID to attribute log rows to batch executions.
• FND_USER — Resolvable through CREATED_BY and LAST_UPDATED_BY for audit attribution.

The AMS Marketing monitor framework consumes this table during rule evaluation; dependent reports and extracts rely on the foreign key relationships above to reconstruct monitor behavior end to end.