Search Results ame_mandatory_attributes_uk1

Overview

HR.AME_MANDATORY_ATTRIBUTES is a reference and configuration table within the Oracle E-Business Suite Approvals Management Engine (AME). It defines which approval attributes are mandatory or required for a given action type, and records the action types that consume a required attribute. In practical terms, the table governs the attribute-to-action-type relationships that AME evaluates when constructing approval routing rules, ensuring that required attributes are supplied before a transaction can be approved.

The object resides in the HR schema with FND design data registered under the PER product family, and it is stored in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. All three documented indexes — AME_MANDATORY_ATTRIBUTES_FK1, FK2, and UK1 — reside in the APPS_TS_TX_IDX tablespace with a date-effective structure keyed on START_DATE and END_DATE.

From a dimensional modeling perspective, the documented schema exhibits a standalone classification, as the table does not reference other database objects. This suggests modeling it as a standalone or link-style component between the AME attribute and action-type domains. The single documented foreign key relationship to FND_SECURITY_GROUPS is associated with the SECURITY_GROUP_ID column, which the metadata explicitly marks as not used.

Key Information Stored

The table is date-effective. Every business relationship is qualified by an activation window, which allows AME to preserve historical configurations while applying only currently valid rows during runtime processing.

• ATTRIBUTE_ID — Identifier of the AME approval attribute participating in the mandatory or required relationship.
• ACTION_TYPE_ID — Identifier of the AME action type that uses or requires the attribute.
• START_DATE — Date on which the row is activated.
• END_DATE — Date on which the row is inactivated.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns providing audit trail and row-level change tracking.
• OBJECT_VERSION_NUMBER — System-generated version of the row that increments by one with each update, supporting optimistic locking in the OAF framework.
• SECURITY_GROUP_ID — Documented as not used; retained for compatibility with the historical multi-org security model. It maps to FND_SECURITY_GROUPS.

The documented unique index AME_MANDATORY_ATTRIBUTES_UK1 covers the combined key ATTRIBUTE_ID, ACTION_TYPE_ID, START_DATE, END_DATE, and ZD_EDITION_NAME. This identifies the business-key candidate: the attribute and action type pairing is unique within an effective date range and edition. The underlying FK1 index on ATTRIBUTE_ID plus the date columns and FK2 on ACTION_TYPE_ID plus the date columns support efficient lookup by either parent identifier. The surrogate primary key is not exposed as a separate sequence column beyond the composite business key; in ETRM 12.2.2 the ZD_EDITION_NAME column supports edition-based redefinition during online patching.

Common Use Cases and Queries

The primary operational use case is resolving which attributes are required for a given action type during approval plan generation. A typical query returns currently active relationships by comparing SYSDATE against the effective date window:

SELECT ATTRIBUTE_ID, ACTION_TYPE_ID, START_DATE, END_DATE FROM HR.AME_MANDATORY_ATTRIBUTES WHERE TRUNC(SYSDATE) BETWEEN START_DATE AND NVL(END_DATE, TRUNC(SYSDATE));

Reporting scenarios include auditing mandatory attribute configuration changes over time, validating that every required attribute has a covering action type, and producing date-effective lineage for compliance reviews. Analysts commonly join ATTRIBUTE_ID to HR.AME_ATTRIBUTES and ACTION_TYPE_ID to HR.AME_ACTION_TYPES to resolve descriptive names. Because the table is date-effective, point-in-time reporting should qualify rows using the START_DATE and END_DATE columns rather than relying on the current system date.

Related Objects

• HR.AME_ATTRIBUTES — Parent definition of each approval attribute referenced by ATTRIBUTE_ID.
• HR.AME_ACTION_TYPES — Parent definition of each action type referenced by ACTION_TYPE_ID.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID; retained for legacy security group scoping even though the column is documented as not used.
• HR.AME_ACTION_USAGES — Defines how action types are consumed and is frequently queried alongside this table for configuration validation.
• HR.AME_RULES and related rule tables

These relationships confirm that HR.AME_MANDATORY_ATTRIBUTES functions as the binding link between the AME attribute domain and the AME action-type domain, and that any configuration change to this table propagates directly into approval routing behavior across AME-enabled transactions.