Search Results object_rule_id

Overview

AMW_OBJECT_RULES is a configuration table in the AMW (Internal Controls Manager) product of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. Its stated purpose is set up: it defines the rule metadata that governs how objects are routed for approval through Oracle Workflow. Each row describes a rule applied to a given object type, together with the approval mechanism, the stored package and procedure calls that implement the rule, and the security group within which the rule is visible. Because the table is used only for administration rather than transactional processing, its volume is typically low and changes are infrequent and deliberate.

From a dimensional modeling perspective, the mined Data Vault classification for AMW_OBJECT_RULES is standalone. This is a heuristic suggestion rather than a schema requirement: the table does not sit at the center of a documented hub-and-link network and holds no dependent child relationships. It therefore behaves closest to a reference or configuration entity, and would be modeled in a Data Vault design as a small hub or reference table rather than as a satellite of a larger business key.

Key Information Stored

The physical schema documented for 12.1.1 contains 17 columns. The most significant of these are:

• OBJECT_RULE_ID — the surrogate primary key, enforced by AMW_OBJECT_RULES_PK and backed by the unique index AMW_OBJECT_RULES_U1. This is the only documented business-key candidate; there is no natural composite key recorded.
• OBJECT_TYPE — the class of object to which the rule applies, such as the internal control, process, or risk entities managed within Internal Controls Manager.
• APPROVAL_TYPE — identifies the approval mode applied to the object, determining whether approval is required and how it is initiated.
• RULE_TYPE and RULE_USED_BY — categorize the rule and indicate the context in which it is consumed.
• API_TYPE, PACKAGE_NAME, and PROCEDURE_NAME — together these bind the rule to the PL/SQL entry point invoked when the workflow processes the object, allowing the approval logic to be extended without changing workflow definitions.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, which scopes the rule to a security group and therefore to the operating unit or organization context of the implementing party.
• SEEDED_FLAG — distinguishes Oracle-delivered seed data from customer-defined rules, which is essential when planning upgrades and patches.
• APPLICATION_ID — the owning application, supporting multi-application filtering.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard WHO audit columns maintained by the EBS audit framework.

Common Use Cases and Queries

Administrators query this table to verify which rules exist before troubleshooting a stalled approval, and developers query it to confirm the package and procedure that a given object type will invoke. A typical diagnostic joins the rule to its security group:

• SELECT OBJECT_RULE_ID, OBJECT_TYPE, APPROVAL_TYPE, RULE_TYPE, PACKAGE_NAME, PROCEDURE_NAME, SEEDED_FLAG FROM AMW.AMW_OBJECT_RULES WHERE OBJECT_TYPE = :p_object_type;
• SELECT r.OBJECT_RULE_ID, r.RULE_USED_BY, r.API_TYPE, g.SECURITY_GROUP_NAME FROM AMW.AMW_OBJECT_RULES r, FND_SECURITY_GROUPS g WHERE r.SECURITY_GROUP_ID = g.SECURITY_GROUP_ID ORDER BY r.OBJECT_TYPE;
• SELECT SEEDED_FLAG, COUNT(*) FROM AMW.AMW_OBJECT_RULES GROUP BY SEEDED_FLAG; — useful before an upgrade to identify customer-modified versus seeded rules.

Reporting is largely administrative rather than analytical: rule inventories, seeded-versus-custom analyses, and verification that every object type requiring approval has at least one active rule mapped to a valid package and procedure.

Related Objects

The documented foreign key defines the principal relationship to FND_SECURITY_GROUPS via SECURITY_GROUP_ID. Beyond that, the significant dependent objects are the AMW entity tables for controls, processes, and risks whose OBJECT_TYPE values are configured here, the Oracle Workflow tables and APIs (WF_ITEM_TYPES, WF_PROCESSES) that consume the rule during routing, and the PL/SQL packages named in PACKAGE_NAME and PROCEDURE_NAME that implement the approval logic. The standard EBS WHO columns align the table with FND_USER and FND_LOGINS, and the unique index AMW_OBJECT_RULES_U1 underpins any programmatic lookup by OBJECT_RULE_ID.