Search Results aso_apr_rules_u1

Overview

ASO.ASO_APR_RULES is a transactional table in the Oracle E-Business Suite Order Management and Oracle Approvals Management (OAM) integration layer. It records the specific approval rules that were evaluated and applied against a given approval instance. Specifically, the table persists the OAM rule identifier and the corresponding OAM action identifier for each rule that participated in an approval decision, providing an auditable trail of why a particular order, quote, or sales document received the approval outcome it did. Within EBS 12.1.1 and 12.2.2, the object resides in the ASO schema, is deployed to the APPS_TS_TX_DATA tablespace with PCT Free of 10, and is registered in FND Design Data as ASO.ASO_APR_RULES.

From a Data Vault modeling perspective, the heuristic classification for this table is standalone. This suggests the object is best modeled as an independent entity rather than as a strict hub, link, or satellite, because its foreign key footprint in the documented metadata is limited to a single reference toward FND_SECURITY_GROUPS via SECURITY_GROUP_ID. The rule and action identifiers that point to the OAM rule engine are documented as logical foreign keys to AME_RULES rather than as enforced database constraints.

Key Information Stored

The table comprises 32 documented columns. The most operationally significant are:

• RULE_ID — Numeric primary key of the row, and the sole column of the unique index ASO_APR_RULES_U1. This is the surrogate identifier for an applied rule record.
• OAM_RULE_ID — The OAM rule identifier, described as a foreign key to the OAM rule. This ties the applied rule back to its definition in AME_RULES.
• RULE_ACTION_ID — The OAM rule action identifier, capturing which action the rule produced for the approval instance.
• OBJECT_APPROVAL_ID — The parent approval instance identifier. This is the driving column of the non-unique index ASO_APR_RULES_N1 (OBJECT_APPROVAL_ID).
• SECURITY_GROUP_ID — The only documented enforced foreign key, referencing FND_SECURITY_GROUPS, used for multi-tenant data isolation.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/BC4J layer to detect concurrent updates.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns, with CREATED_BY and LAST_UPDATED_BY referencing FND_USER.USER_ID.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE20 — Descriptive flexfield segments, each VARCHAR2(240), available for customer-specific extension.

Business-key candidacy is effectively limited to RULE_ID, since ASO_APR_RULES_U1 is the only unique index documented. Row volume is expected to be high, as one approval instance may evaluate many rules before a decision is reached.

Common Use Cases and Queries

Typical usage centers on approval auditing and troubleshooting stuck or unexpectedly routed approvals. A frequent pattern retrieves all rules applied to a specific approval instance:

• SELECT rule_id, oam_rule_id, rule_action_id FROM aso.aso_apr_rules WHERE object_approval_id = :p_approval_id; — supports the N1 index path.
• Joining to AME_RULES on oam_rule_id reconstructs the human-readable rule name and action description applied to each approval.
• Point lookups by primary key use WHERE rule_id = :p_rule_id to resolve the unique index ASO_APR_RULES_U1.
• Reporting on rule frequency, e.g. counting occurrences per OAM_RULE_ID over a date range using CREATION_DATE, identifies the most frequently triggering approval rules.
• Multi-tenant extraction filters on SECURITY_GROUP_ID to restrict results to the appropriate operating unit or security context.

Because OAM_RULE_ID and RULE_ACTION_ID are not enforced by database constraints, validation queries should account for orphaned references where AME_RULES definitions have since changed or been removed.

Related Objects

• AME_RULES — Holds the OAM rule definitions referenced by OAM_RULE_ID and RULE_ACTION_ID. The principal join target for reconstructing rule semantics.
• FND_SECURITY_GROUPS — Referenced through the enforced foreign key SECURITY_GROUP_ID.
• FND_USER — Referenced by CREATED_BY and LAST_UPDATED_BY for audit attribution.
• FND_LOGINS — Referenced by LAST_UPDATE_LOGIN for the operating system login identifier.
• The parent approval instance object identified by OBJECT_APPROVAL_ID, which anchors each rule record to its approval context.
• The ASO approval engine packages and APIs that populate this table during runtime rule evaluation.