Search Results ame_rules

Overview

The APPS.ASO_APPROVAL_RULES_ALL_V view is a reporting and integration construct within the Oracle E-Business Suite Order Capture (ASO) module. It presents a resolved, human-readable listing of approval rules that govern quote and order approval processing by joining the ASO rule registration table to the Oracle Approvals Management (AME) engine definitions. In EBS 12.1.1 and 12.2.2, approval routing for Oracle Quoting and Order Management is delegated to AME, which stores the rule logic, while ASO holds the linkage between an object approval context and a specific AME rule. The view exists to collapse that multi-table relationship into a single queryable surface, allowing implementers, support analysts, and reporting tools to identify which AME rules are currently active for an approval object without navigating the raw AME schema. Because the view filters on end dates, it exposes only rules and actions that remain in effect at query time.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is owned by APPS and is defined over the following synonyms: ASO_APR_RULES, AME_RULES, and AME_ACTIONS. The view text joins ASO_APR_RULES (aliased AAR) to AME_RULES (AMR) on OAM_RULE_ID = RULE_ID, and then joins AME_RULES to AME_ACTIONS (AMA) on ACTION_ID. Each join is additionally constrained so that either the END_DATE is null or SYSDATE is less than END_DATE for both the rule and the action. This makes the view an inner-join, current-state projection: rows whose underlying rule or action has expired are excluded. Consequently, the view reflects the present approval configuration rather than historical rule definitions.

Key Columns

• OBJECT_APPROVAL_ID — Identifier linking the rule to the ASO object approval context, tying the AME rule to the specific approval configuration within Order Capture.
• RULE_ID — The AME rule identifier (OAM_RULE_ID), the primary correlation key to the AME engine.
• RULE_DESCRIPTION — The descriptive text of the rule drawn from AME_RULES.DESCRIPTION, providing the readable rule name.
• APPROVAL_LEVEL — The description sourced from AME_ACTIONS.DESCRIPTION, indicating the action or approval level associated with the rule.
• CREATION_DATE, CREATED_BY — Audit columns identifying when and by whom the ASO rule record was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing the most recent modification of the underlying ASO rule row.

Common Use Cases and Queries

A primary use case is auditing which AME rules are currently active for a given approval object, including verification that a rule and its action have not expired. A representative query is:

SELECT object_approval_id, rule_id, rule_description, approval_level FROM apps.aso_approval_rules_all_v WHERE object_approval_id = :p_object_approval_id;

A second scenario supports troubleshooting by listing all active rules with their approval levels:

SELECT rule_id, rule_description, approval_level FROM apps.aso_approval_rules_all_v ORDER BY rule_description;

The view is also useful as a security-checked reporting source, since it resides in APPS and honors row-level security and the APPS schema grants. Because it filters expirations internally, reports built on it automatically reflect only currently effective approval routing.