Search Results ame_attributes




Overview
Explore in AI Chat

Overview

The AME_ATTRIBUTES table resides in the HR schema and belongs to the PER (Human Resources) product family within Oracle E-Business Suite. It forms part of the Oracle Approvals Management Engine (AME) data model, which governs the configurable approval rules, routing, and authorization logic used throughout EBS transactions. In this capacity, AME_ATTRIBUTES stores the definition of the attributes that AME evaluates when determining whether an approval rule applies to a given business transaction, such as a purchase order, expense report, or HR action.

The ETRM metadata classifies this object heuristically as standalone within the Data Vault model. From a modeling perspective, this suggests AME_ATTRIBUTES behaves as an independent reference or configuration entity with no inbound foreign-key dependencies from other tables, though it does reference FND_SECURITY_GROUPS via SECURITY_GROUP_ID. It is best treated as a reference hub for approval attribute definitions rather than a transactional satellite.

Key Information Stored

The table is keyed by ATTRIBUTE_ID, which acts as the primary surrogate identifier for each attribute definition. The documented unique index AME_ATTRIBUTES_PK combines ATTRIBUTE_ID, START_DATE, END_DATE, and ZD_EDITION_NAME, indicating that attributes are versioned and dated, with effective period tracking and edition support.

  • ATTRIBUTE_ID — the surrogate primary key uniquely identifying each attribute.
  • NAME — the display or internal name of the attribute used in approval rules.
  • ATTRIBUTE_TYPE — the data type of the attribute (for example, number, string, or date), which determines how AME evaluates values.
  • LINE_ITEM — identifies the transaction line item to which the attribute applies.
  • DESCRIPTION — free-text description of the attribute's purpose.
  • SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, scoping the attribute to a security group.
  • APPROVER_TYPE_ID — links the attribute to the approver type used in routing decisions.
  • ITEM_CLASS_ID — associates the attribute with a specific item class.
  • START_DATE / END_DATE — effective dating that governs when the attribute definition is valid.
  • ZD_EDITION_NAME — edition tracking column supporting multiple configuration editions.
  • OBJECT_VERSION_NUMBER — optimistic-locking control for concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing creation and modification metadata.

Common Use Cases and Queries

The primary use case is rule tracing and configuration auditing: identifying which attributes drive approval routing for a given transaction context. A typical query retrieves all active attributes for a security group:

  • SELECT attribute_id, name, attribute_type, line_item FROM ame_attributes WHERE security_group_id = :sg AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)+1);
  • Joining to FND_SECURITY_GROUPS to resolve the security context of each attribute.
  • Filtering by APPROVER_TYPE_ID or ITEM_CLASS_ID to isolate attributes tied to a specific approver type or item classification.
  • Reporting on attributes by NAME to inventory the approval attributes configured in a given environment, useful during implementations and upgrades between 12.1.1 and 12.2.2.

Related Objects

AME_ATTRIBUTES participates in the broader AME and shared configuration schema. The most significant related objects include:

  • FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; the primary documented FK relationship.
  • AME_APPROVER_TYPES / AME_APPROVER_TYPE_ATTRIBUTES — upstream definitions of approver types referenced by APPROVER_TYPE_ID.
  • AME_RULES and AME_CONDITIONS — the rules framework that consumes attribute definitions when evaluating conditions.
  • AME_ITEM_CLASSES and AME_CALLING_APPS — define the item classes and calling application context for attributes.
  • FND_SECURITY_GROUPS and the AME setup public APIs used to create and maintain attribute definitions.

Together these objects provide the configuration backbone that AME relies upon when resolving approval routing across EBS modules.