Search Results ame_actions




Overview
Explore in AI Chat

Overview

AME_ACTIONS is a table owned by the HR schema within the Oracle E-Business Suite, associated with the PER (Human Resources) product family. It is a core component of the Approvals Management Engine (AME), the rules-based framework Oracle EBS uses to evaluate approval routing, generate approvers, and record the actions that AME performs when it processes a business transaction. Within this framework, AME_ACTIONS stores the discrete action definitions — that is, the conditional or unconditional operations AME executes when a transaction's approval rules are satisfied, such as adding an approver, sending a notification, or invoking a function.

The table carries a date-effective design, evidenced by its primary key and edition columns, which allows AME configurations to be versioned over time. The ETRM metadata classifies this object heuristically as standalone under Data Vault modeling conventions, meaning it is best treated as an independent reference table rather than a hub or link, as it does not sit at the center of a heavily mined foreign-key web. Its single documented foreign key ties it to FND_SECURITY_GROUPS, indicating that each action definition can be scoped to a security group.

Key Information Stored

The physical schema documented for ETRM 12.2.2 comprises 15 columns. The most operationally significant are described below.

  • ACTION_ID — the surrogate primary key component identifying each action definition. It forms part of the composite unique index AME_ACTIONS_PK (ACTION_ID, START_DATE, END_DATE, ZD_EDITION_NAME).
  • ACTION_TYPE_ID — references the AME action type, distinguishing the category of operation (for example, adding an approver versus sending a notification) that the action represents.
  • PARAMETER and PARAMETER_TWO — hold the arguments or values required to execute the action, such as the approver source or the notification template.
  • START_DATE and END_DATE — define the effective date range during which the action definition is active; both participate in the primary key, reflecting the date-effective design.
  • SECURITY_GROUP_ID — the sole documented foreign key, referencing FND_SECURITY_GROUPS and scoping the action to a security group.
  • DESCRIPTION — free-text description of the action's purpose.
  • ZD_EDITION_NAME — the edition column supporting Oracle's edition-based redefinition, also part of the unique index.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard "Who" audit columns capturing creation and last-modification metadata for each row.

The business-key candidate is the full composite (ACTION_ID, START_DATE, END_DATE, ZD_EDITION_NAME) enforced by AME_ACTIONS_PK, rather than ACTION_ID alone.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios involving AME_ACTIONS include auditing which action definitions are currently active, tracing an action back to its action type, and verifying parameter values used in approval processing.

To list all currently effective action definitions for a security group:

SELECT action_id, action_type_id, description, parameter, parameter_two
FROM   hr.ame_actions
WHERE  security_group_id = :p_security_group
AND    TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));

To inspect the date-effective history of a single action, query by ACTION_ID ordered by START_DATE, which reveals successive configurations across editions. Because the table is short relative to transaction tables, it is frequently joined to action-type reference tables to produce configuration reports. Analysts also use it during upgrades to confirm that no active definitions conflict with modified approval rules.

Related Objects

The following objects are most significant in relation to AME_ACTIONS, based on documented relationships and AME functional dependencies:

  • FND_SECURITY_GROUPS — joined via AME_ACTIONS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID, the only documented foreign key.
  • AME_ACTION_TYPES — referenced through ACTION_TYPE_ID, defining the category and behavior of each action.
  • AME_RULES and AME_CONDITIONS — the rule and condition definitions whose evaluation triggers the actions stored here.
  • AME_APPROVER_GROUPS and AME_APPLICATION_ATTRIBUTES — companion AME configuration tables related through the action-processing flow.
  • AME_ATTRIBUTE_ACTIONS — the association table linking actions to application attributes.

Together these objects form the AME configuration matrix that governs approval routing across EBS transactions.