Results for “call_action_id”

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

Overview

AR_ACTION_NOTIFICATIONS is a Receivables (AR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the list of employees who must be notified about a particular customer call action. In the Oracle CRM call-handling flow, a "call action" represents a scheduled follow-up step performed against a customer call. AR_ACTION_NOTIFICATIONS records the notification recipients associated with each such action, linking a call action to the system user who should receive notification. The table is owned by the AR schema and is marked VALID in the referenced ETRM documentation.

From a Data Vault modeling perspective, the mined metadata classifies AR_ACTION_NOTIFICATIONS heuristically as a link table. This is consistent with its structure: it does not hold descriptive attributes of a business entity in its own right, but rather resolves the association between a call action (AR_CALL_ACTIONS) and an employee/user (FND_USER). Note that the ETRM heuristic is a modeling suggestion only; a formal Data Vault design should confirm grain and historization based on business requirements.

Key Information Stored

The documented physical schema for 12.2.2 contains eight columns. The most significant are:

• ACTION_NOTIFICATION_ID — the surrogate primary key, enforced by the index AR_ACTION_NOTIFICATIONS_PK and also documented as a unique business-key candidate via AR_ACTION_NOTIFICATIONS_U1. This identifier uniquely distinguishes each notification row.
• CALL_ACTION_ID — foreign key to AR_CALL_ACTIONS, identifying the specific customer call action to which the notification applies. Together with EMPLOYEE_ID, this defines the operational association of the row.
• EMPLOYEE_ID — foreign key to FND_USER, identifying the recipient employee/user who must be notified about the call action.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS "Who" audit columns, populated by the concurrent/runtime framework, that track row insertion and modification.

The table therefore represents the many-to-many notification assignment between call actions and employees. The unique index on ACTION_NOTIFICATION_ID confirms the surrogate key; AR_ACTION_NOTIFICATIONS_U1 is the documented business-key candidate. No additional descriptive or status columns are present in the documented schema.

Common Use Cases and Queries

Typical scenarios include auditing who is notified for a given call action, listing an employee's pending call notifications, and reconciling call-handling configuration before integrations. Because the table is a pure link, queries almost always join to AR_CALL_ACTIONS and FND_USER.

For example, to find all employees notified for a specific call action:

• SELECT n.ACTION_NOTIFICATION_ID, n.EMPLOYEE_ID, u.USER_NAME, n.CALL_ACTION_ID FROM AR.AR_ACTION_NOTIFICATIONS n JOIN FND_USER u ON u.USER_ID = n.EMPLOYEE_ID WHERE n.CALL_ACTION_ID = :call_action_id;

To identify every notification assigned to a given user:

• SELECT n.ACTION_NOTIFICATION_ID, n.CALL_ACTION_ID, n.CREATION_DATE FROM AR.AR_ACTION_NOTIFICATIONS n WHERE n.EMPLOYEE_ID = :user_id ORDER BY n.CREATION_DATE;

Reporting extracts frequently join through AR_CALL_ACTIONS to resolve the parent call and through FND_USER to obtain the recipient's display name for notification routing audits. Given the standard audit columns, temporal queries can filter or trend on CREATION_DATE and LAST_UPDATE_DATE.

Related Objects

The following objects are most closely related, based on the documented FK relationships and EBS module context:

• AR_CALL_ACTIONS — parent of the call action; joined on AR_ACTION_NOTIFICATIONS.CALL_ACTION_ID = AR_CALL_ACTIONS.CALL_ACTION_ID. This is the primary business dependency.
• FND_USER — the application user registry; joined on AR_ACTION_NOTIFICATIONS.EMPLOYEE_ID = FND_USER.USER_ID to resolve the notified employee.
• AR_CALL_ACTIONS-related parent call tables in the Oracle CRM/Telephony call stack, which provide the call header context for each action.
• Oracle Receivables call-handling forms and concurrent programs that insert or maintain notification rows, relying on AR_ACTION_NOTIFICATIONS_PK for row identity.
• The unique index AR_ACTION_NOTIFICATIONS_U1, which enforces uniqueness on the primary key column and governs row identity in the documented schema.

As a link table, AR_ACTION_NOTIFICATIONS has no child tables documented; it exists to resolve the call action-to-employee notification relationship and is referenced through its primary key by any dependent process requiring notification-level identification.