Results for “ame_rules”

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

Overview

AME_RULES is a core configuration table in the Oracle E-Business Suite Approval Management Engine (AME), owned by the HR schema and classified under the PER (Human Resources) product family. AME is the rules-based engine that drives approver list generation, routing, and approval hierarchy determination for a wide range of EBS business flows, including Purchasing, Payables, iProcurement, Human Resources, and General Ledger journal approvals. The AME_RULES table stores the actual rule definitions that the AME engine evaluates at runtime to determine which approvers should be attached to a given transaction or document.

From a dimensional and historical-tracking perspective, the table exhibits the characteristics of a standalone entity rather than a strictly dependent satellite. The mined relationship data classifies AME_RULES as standalone within the Data Vault heuristic model, though the presence of effective-dating columns (START_DATE, END_DATE, ZD_EDITION_NAME) and audit columns suggests that in a Data Vault re-modeling exercise it could reasonably be treated as a versioned satellite anchored to a rule hub keyed on RULE_ID. This is a modeling suggestion only; the physical implementation is a conventional EBS transactional table.

Key Information Stored

AME_RULES contains 16 documented columns that together describe rule identity, type, effective dating, and relationships to other AME and FND entities.

• RULE_ID — the surrogate primary key for each rule definition, generated by the AME sequence.
• START_DATE, END_DATE — effective dating range controlling when the rule is active and evaluated by the AME engine.
• ZD_EDITION_NAME — the edition identifier used by EBS online patching (ADOP / editioning views) in 12.2.x; combined with RULE_ID and the date range, it forms the AME_RULES_PK unique index and constitutes the business-key candidate.
• RULE_TYPE — categorizes the rule (for example, approval group rules, routing rules, or transaction-type rules), driving how the AME engine interprets the row.
• ACTION_ID — foreign reference to the AME_ACTIONS definition that the rule invokes when its conditions are satisfied.
• RULE_KEY — a unique textual or numeric key used to reference the rule in AME configuration and by the AME API.
• ITEM_CLASS_ID — identifies the AME item class (transaction type) to which the rule applies, such as a purchasing document or expense report.
• DESCRIPTION — free-text description of the rule's purpose.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, scoping the rule to a security group.
• OBJECT_VERSION_NUMBER — optimistic locking column used by OAF-based AME configuration screens.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO audit columns.

Common Use Cases and Queries

Functional consultants and support analysts query AME_RULES most often when diagnosing why a transaction is not routing to the expected approver. Typical reporting includes listing all active rules for a given item class and date, or correlating rules with the actions they trigger.

SELECT r.rule_id, r.rule_type, r.rule_key, r.description,
       r.start_date, r.end_date, a.action_type
FROM   ame_rules r, ame_actions a
WHERE  r.action_id = a.action_id
AND    r.item_class_id = :item_class_id
AND    TRUNC(SYSDATE) BETWEEN r.start_date AND NVL(r.end_date, SYSDATE);

An audit query can identify rules modified after a given date using LAST_UPDATE_DATE, while a security-scoped listing joins to FND_SECURITY_GROUPS via SECURITY_GROUP_ID. Version validation often uses ZD_EDITION_NAME together with RULE_ID to ensure the correct editioned row is returned under 12.2 online patching. Reporting extracts frequently feed a configuration baseline comparison across environments.

Related Objects

• AME_ACTIONS — joined on ACTION_ID; defines the action each rule executes.
• AME_RULE_INPUTS and AME_RULE_CONDITIONS — child tables that hold the input parameters and boolean conditions attached to a rule.
• AME_ITEM_CLASSES — joined on ITEM_CLASS_ID; defines the transaction class the rule applies to.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; the only documented foreign key target.
• AME_APPROVAL_GROUPS and AME_APPROVER_GROUPS — reference rules during approver list generation.
• AME_API package APIs (e.g., AME_API1, AME_API2) — the programmatic interface used to maintain rule definitions.