Search Results ame_action_types_pk

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

Overview

HR.AME_ACTION_TYPES is a reference and configuration table within the Oracle E-Business Suite Approval Management Engine (AME). It stores the master list of action types that AME can execute against a transaction or approval rule. Each row defines an action type by name, an associated PL/SQL package (PROCEDURE_NAME) that implements the action type handler, and descriptive attributes. AME uses this metadata when evaluating approval rules to determine which programmatic actions are available and how they should be invoked.

The table resides in the HR schema and is registered in FND Design Data as PER.AME_ACTION_TYPES, with storage in the APPS_TS_TX_DATA tablespace. Its indexes live in APPS_TS_TX_IDX. The object is documented as VALID in both 12.1.1 and 12.2.2. Heuristic Data Vault classification suggests this table behaves as a standalone reference hub for action types, since it does not reference other AME tables and no child tables are documented that would justify a link structure. The presence of a SECURITY_GROUP_ID foreign key to FND_SECURITY_GROUPS is the sole documented outbound relationship, but the column is marked "Not used" in the metadata.

Key Information Stored

The primary identifier is ACTION_TYPE_ID, a NUMBER surrogate key. The documented unique index, AME_ACTION_TYPES_PK, is composed of ACTION_TYPE_ID, START_DATE, END_DATE, and ZD_EDITION_NAME. This composite structure makes the index a date-effective business-key candidate rather than a single-column key: the same ACTION_TYPE_ID can appear across multiple activation windows managed by START_DATE and END_DATE.

• ACTION_TYPE_ID – Surrogate identifier for the action type.
• NAME – Human-readable action type name (VARCHAR2, 50), used in AME rule configuration and lookups.
• PROCEDURE_NAME – The PL/SQL package implementing the action type handler (VARCHAR2, 50); the critical operational link between configuration and executable code.
• DESCRIPTION – Static description of the action type (VARCHAR2, 100).
• START_DATE / END_DATE – Activation and inactivation dates controlling the date-effective window for each row and participating in the primary key index.
• DYNAMIC_DESCRIPTION – Flag indicating whether the action type generates a description at runtime.
• DESCRIPTION_QUERY – SQL statement (VARCHAR2, 4000) used to fetch a dynamic description when enabled.
• OBJECT_VERSION_NUMBER – System-generated version counter incremented on each update, used for optimistic locking.
• ZD_EDITION_NAME – Editioning column (VARCHAR2, 30) supporting Online Patching in 12.2.2; part of the primary key index.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard Who columns for audit lineage.
• SECURITY_GROUP_ID – Declared as NUMBER(15) but documented as not used; retains a foreign key to FND_SECURITY_GROUPS for legacy compatibility.

Common Use Cases and Queries

Typical scenarios include reporting the catalog of available AME action types, verifying which PL/SQL package handles a given action, and auditing date-effective changes to action type definitions. Because the primary key is composite, point lookups by ACTION_TYPE_ID may return multiple rows across editions or activation windows; queries should filter on the edition and date range appropriate to the environment.

• List all currently 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, TRUNC(SYSDATE)) AND ZD_EDITION_NAME = 'CURRENT_EDITION';
• Resolve the handler package for a named action: SELECT PROCEDURE_NAME FROM HR.AME_ACTION_TYPES WHERE NAME = :name;
• Identify action types with dynamic descriptions: SELECT NAME, DESCRIPTION_QUERY FROM HR.AME_ACTION_TYPES WHERE DYNAMIC_DESCRIPTION = 'Y';
• Audit recent definition changes via LAST_UPDATE_DATE and LAST_UPDATED_BY.

These queries support AME rule troubleshooting, upgrade validation, and security review of custom action type handlers.

Related Objects

Documented dependencies for this table are sparse; the FK to FND_SECURITY_GROUPS is the only explicit relationship provided, and no child tables are listed. The following objects are significant in practice:

• FND_SECURITY_GROUPS – Referenced via SECURITY_GROUP_ID; legacy grouping attribute.
• APPS.AME_ACTION_TYPE_UTIL – PL/SQL utility API that reads AME_ACTION_TYPES to resolve handler procedures.
• HR.AME_ACTIONS – Stores action instances whose ACTION_TYPE_ID identifies the definition row in this table.
• HR.AME_RULES / HR.AME_RULE_ACTIONS – Associate rules with the actions and action types defined here.
• HR.AME_ATTRIBUTES / HR.AME_CONDITIONS – Companion AME configuration tables used alongside action types during rule evaluation.
• PER.AME_ACTION_TYPES design data – FND Design Data registration controlling deployment of this table across editions.