Search Results ame_approval_group_items_pk

Overview

HR.AME_APPROVAL_GROUP_ITEMS is a transactional table in the Oracle E-Business Suite Approvals Management Engine (AME) schema. It stores the individual member records that constitute an approver group, with each row representing one component of a group definition. Approver groups are the reusable building blocks used by AME to assemble approval routing — a group may contain static approvers resolved through workflow directory services, or nested groups referenced by identifier. The table's FND Design Data identifier is PER.AME_APPROVAL_GROUP_ITEMS, confirming its ownership under the HR/PER product family.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. From a Data Vault modeling perspective, the metadata's heuristic classification is standalone, meaning the object is not formally modeled as a hub, link, or satellite within the documented foreign-key structure. The only declared foreign key is a reference from SECURITY_GROUP_ID to FND_SECURITY_GROUPS, and the SECURITY_GROUP_ID column is documented as not used, so the practical classification is that of an independent detail table anchored by its own surrogate key.

Key Information Stored

The table contains 14 documented columns. The most operationally significant are:

• APPROVAL_GROUP_ITEM_ID — the surrogate primary key and approver group component identifier. It is the first column of the AME_APPROVAL_GROUP_ITEMS_PK unique index.
• APPROVAL_GROUP_ID — the approver group identifier that ties the row to its parent group.
• PARAMETER_NAME — VARCHAR2(20); identifies the type of approver group component.
• PARAMETER — VARCHAR2(320); holds the name of the approver in workflow directory services for a static group, or the approver group identifier for a nested group.
• ORDER_NUMBER — the sequence position of the component within the group.
• START_DATE and END_DATE — the activation and inactivation dates governing row validity.
• OBJECT_VERSION_NUMBER — the system-generated version counter that increments by one on each update, supporting optimistic locking.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who audit columns.
• SECURITY_GROUP_ID — NUMBER(15); documented as not used.

The AME_APPROVAL_GROUP_ITEMS_PK unique index is defined on APPROVAL_GROUP_ITEM_ID, START_DATE, and END_DATE. This composite structure — combining the surrogate identifier with the effective-dating pair — is the business-key candidate and indicates that the table is date-tracked rather than a simple flat key-per-row store. The non-unique index AME_APPROVAL_GROUP_ITEMS_FK1 mirrors the same effective-dating pattern over APPROVAL_GROUP_ID, supporting efficient retrieval of all members of a group for a given date range.

Common Use Cases and Queries

The table is queried primarily during AME rule evaluation and when reporting on approval configuration. A typical pattern retrieves the ordered members of a group that are active on a specific date:

• Resolve the members of a group: SELECT APPROVAL_GROUP_ITEM_ID, PARAMETER_NAME, PARAMETER, ORDER_NUMBER FROM HR.AME_APPROVAL_GROUP_ITEMS WHERE APPROVAL_GROUP_ID = :group_id AND SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE) ORDER BY ORDER_NUMBER;
• Distinguish static from nested members by inspecting PARAMETER_NAME and interpreting PARAMETER accordingly.
• Audit configuration changes using LAST_UPDATED_BY, LAST_UPDATE_DATE, and OBJECT_VERSION_NUMBER.
• Reconstruct historical group membership as of a past date by constraining START_DATE and END_DATE.

Because the primary key includes the effective-dating columns, queries should always bound the date range to avoid returning multiple versions of the same component.

Related Objects

The documented dependency data for this object is deliberately narrow:

• HR.AME_APPROVAL_GROUPS — the parent group definition; join on APPROVAL_GROUP_ID. This is the most significant relationship, since every item row belongs to exactly one group.
• FND_SECURITY_GROUPS — the sole documented foreign-key target, referenced through SECURITY_GROUP_ID, although that column is noted as not used.
• AME_APPROVAL_GROUP_ITEMS_PK — the unique index on APPROVAL_GROUP_ITEM_ID, START_DATE, and END_DATE.
• AME_APPROVAL_GROUP_ITEMS_FK1 — the non-unique index on APPROVAL_GROUP_ID, START_DATE, and END_DATE.

Beyond these documented relationships, the AME rule evaluation layer consumes group membership through the approval group definitions, and the underlying approver identities named in PARAMETER are resolved against workflow directory services at runtime rather than through a declared database constraint.