Search Results ame_action_types




Overview

AME_ACTION_TYPES is a configuration table owned by the HR schema within the Oracle E-Business Suite, and it belongs to the PER (Human Resources) product family. It forms part of the Oracle Approvals Management Engine (AME), the rules-based framework that determines approval routing for transactions such as requisitions, purchase orders, expense reports, and human-resources actions. Each row in this table defines a discrete action type — a named, executable behavior that AME can invoke when an approval rule fires or when the engine moves a transaction through its approval lifecycle.

Under the heuristic Data Vault classification mined from its foreign-key structure, this object is assessed as a standalone entity. In Data Vault modeling terms, this suggests the table behaves as an independent reference or configuration set rather than participating in a hub/link/satellite hierarchy. The only documented outbound foreign key references FND_SECURITY_GROUPS, indicating that action types can be scoped or secured by a security group rather than tied to a transactional parent.

Key Information Stored

The table is documented with 16 columns in the ETRM 12.2.2 physical schema. The most significant are:

Common Use Cases and Queries

Administrators and technical consultants query this table to audit which approval actions are enabled, to trace the procedure invoked for a given action, and to verify effective dates when troubleshooting approval behavior. A typical lookup joins the security group to resolve the owning group name:

  • List active action types: SELECT action_type_id, name, procedure_name FROM hr.ame_action_types WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE);
  • Resolve the security group: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to display the group name alongside each action type.
  • Detect dynamic descriptions: filter where DYNAMIC_DESCRIPTION is set and DESCRIPTION_QUERY is populated, useful when reviewing runtime-generated approval messaging.

Reporting use cases include approval-configuration audits, impact analysis before patching AME rules, and documentation of the action catalog for compliance reviews.

Related Objects

The most significant dependent and referenced objects are:

  • FND_SECURITY_GROUPS — referenced via AME_ACTION_TYPES.SECURITY_GROUP_ID; the sole documented foreign key.
  • AME_RULES / AME_RULE_ACTIONS — rules that bind action types to approval conditions.
  • AME_APPROVAL_GROUPS and AME_ATTRIBUTES — the wider AME configuration model.
  • AME_API — the public API that consumes action types during approval processing.
  • AME_ACTION_TYPES_PK — the unique index enforcing the business-key candidate.