Search Results ame_conditions




Overview
Explore in AI Chat

Overview

AME_CONDITIONS is a table owned by the HR schema within the Oracle E-Business Suite, delivered under the PER (Human Resources) product family. It forms part of the Oracle Approvals Management Engine (AME) data model, the rules framework used to determine approval routing, approver lists, and authorization requirements for transactions raised across EBS modules such as Purchasing, Payables, Order Management, and Human Resources. Each row in AME_CONDITIONS represents a discrete conditional expression that, when evaluated against the attributes of a transaction, determines whether an associated approval rule applies.

The ETRM metadata classifies this object as a standalone table based on a heuristic review of its foreign key structure. In Data Vault modeling terms, this suggests treating AME_CONDITIONS as a hub-like reference entity, keyed by CONDITION_ID, rather than as a dependent satellite. Its only documented outbound foreign key, on SECURITY_GROUP_ID, points to FND_SECURITY_GROUPS, but this is a security scope reference rather than a structural business relationship. Because the table is standalone, it functions primarily as a definition or configuration store for the AME rule engine.

Key Information Stored

The documented physical schema for release 12.2.2 lists 19 columns. The primary surrogate identifier is CONDITION_ID, which is the first element of the unique index AME_CONDITIONS_PK. That index also comprises START_DATE, END_DATE, and ZD_EDITION_NAME, indicating that the table is date-effectivity enabled and supports the ZD (zero-downtime) editioning pattern used in Online Patching environments. Consequently, CONDITION_ID alone does not guarantee uniqueness across editions; the full key combination does.

  • CONDITION_ID — surrogate primary key and the internal identifier referenced by other AME entities.
  • CONDITION_TYPE — the operator or comparison category used to evaluate the condition.
  • ATTRIBUTE_ID — the AME attribute against which the condition is evaluated, typically resolving to a transactional or HR attribute definition.
  • PARAMETER_ONE, PARAMETER_TWO, PARAMETER_THREE — operand values supplied to the condition, such as thresholds, qualifying values, or lookup inputs.
  • INCLUDE_LOWER_LIMIT, INCLUDE_UPPER_LIMIT — boolean flags controlling whether boundary values in a range comparison are treated as inclusive.
  • START_DATE, END_DATE — effectivity window governing when the condition is active.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, scoping the record to a security group.
  • CONDITION_KEY — alternate business identifier used for rule definition and migration.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the AME APIs to detect concurrent updates.
  • ZD_EDITION_NAME — editioning column supporting Online Patching in 12.2.x.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

AME_CONDITIONS is principally queried during troubleshooting and audit of approval routing behavior. A typical diagnostic query joins conditions to attributes to identify which rule logic references a given transaction attribute:

  • Filtering active conditions by effectivity window and security group to reproduce the rule set evaluated on a specific transaction date.
  • Retrieving PARAMETER_ONE through PARAMETER_THREE alongside CONDITION_TYPE to confirm whether a range, equality, or list comparison was configured as intended.
  • Auditing CONDITION_KEY and OBJECT_VERSION_NUMBER values when comparing an AME rule migration between environments.
  • Verifying INCLUDE_LOWER_LIMIT and INCLUDE_UPPER_LIMIT when approval outcomes appear inconsistent at exact boundary values.

Related Objects

  • FND_SECURITY_GROUPS — joined on AME_CONDITIONS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
  • AME_ATTRIBUTES — resolves ATTRIBUTE_ID to the attribute definition evaluated by the condition.
  • AME_CONDITION_GROUPS / AME_RULES — link conditions into rule groupings and approval rule definitions.
  • AME_CONDITIONS_TL — translation table for condition display text where present.
  • AME_API and related PL/SQL packages — the supported programmatic interface through which conditions are created and maintained, rather than direct DML.