Results for “ams_act_logs”

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

Overview

AMS_ACT_LOGS is a transactional table in the AMS (Marketing) product schema of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. As its documented description states, it stores the runtime logs generated during transactions. In practice it functions as the diagnostic and audit trail for marketing activity processing — campaign activity execution, list import, and list header workflows — capturing messages emitted while those processes run. Each row represents a single log entry tied to an activity log identifier and, where applicable, to the list or import header that produced the entry.

Under the heuristic Data Vault classification mined from its foreign key structure, AMS_ACT_LOGS is modeled as a link. This reflects the fact that the table primarily records associations between a log event and the parent list or import entity that generated it, rather than serving as a standalone hub of business keys or a pure descriptive satellite. This classification should be treated as a modeling suggestion rather than a normative definition.

Key Information Stored

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

• ACTIVITY_LOG_ID — the surrogate primary key, enforced by AMS_ACT_LOGS_PK and mirrored by the unique index AMS_ACT_LOGS_U1. This is the single unique identifier for a log row.
• ACT_LOG_USED_BY_ID — a foreign key that identifies the list header or import list header that consumed the log. This column carries a dual parent relationship (see Related Objects).
• ARC_ACT_LOG_USED_BY — an archival or attribute qualifier for the "used by" reference.
• LOG_TRANSACTION_ID — links the log entry to the transaction that produced it.
• LOG_MESSAGE_TEXT — the human-readable message body recorded for the event.
• LOG_MESSAGE_LEVEL and LOG_MESSAGE_TYPE — the severity level and category of the message, enabling filtering of informational versus error entries.
• DESCRIPTION — a descriptive text field for the log record.
• SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS, enforcing multi-org or security-group data isolation.
• BUDGET_ID and THRESHOLD_ID — optional references to budget and threshold context associated with the logged activity.
• NOTIFICATION_CREATION_DATE — the timestamp indicating when a related notification was created.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER — provide audit and optimistic-locking support.

The only documented business-key candidate is ACTIVITY_LOG_ID itself, via unique index AMS_ACT_LOGS_U1; no additional composite unique constraint is recorded.

Common Use Cases and Queries

AMS_ACT_LOGS is typically queried for process troubleshooting and audit reporting. Common patterns include retrieving all messages for a given parent list or import, isolating errors for a specific transaction, and producing chronological log history for support analysis.

• Find all log entries for a list header:
  SELECT ACTIVITY_LOG_ID, LOG_MESSAGE_LEVEL, LOG_MESSAGE_TEXT, CREATION_DATE FROM AMS.AMS_ACT_LOGS WHERE ACT_LOG_USED_BY_ID = :list_header_id ORDER BY CREATION_DATE;
• Retrieve entries for a specific transaction or error level:
  SELECT * FROM AMS.AMS_ACT_LOGS WHERE LOG_TRANSACTION_ID = :txn_id AND LOG_MESSAGE_LEVEL = 'ERROR';
• Join to the owning list or import header to enrich reporting with the parent object name.

Because runtime logging grows quickly, queries should be constrained by date range, parent identifier, or message level for performance.

Related Objects

• AMS_LIST_HEADERS_ALL — joined via ACT_LOG_USED_BY_ID to the list header that owns or consumed the log.
• AMS_IMP_LIST_HEADERS_ALL — joined via ACT_LOG_USED_BY_ID for import-based list processing.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID to resolve security-group context.
• AMS_ACT_LOGS_PK / AMS_ACT_LOGS_U1 — primary key constraint and unique index on ACTIVITY_LOG_ID, defining row identity.

Collectively these relationships tie the log table into the marketing list-management and import pipelines, supporting both operational monitoring and downstream audit extraction.