Search Results amw_object_rules_u1

Overview

AMW.AMW_OBJECT_RULES is a setup table within the Oracle E-Business Suite Application Management Workbench (AMW) schema. Its documented purpose is to store configuration data that governs the approval of objects through Oracle Workflow. In practice, the table acts as a rules registry: each row associates a given object type with the approval mechanism, workflow-enabled API package, and procedure that should be invoked when that object requires approval. Because it resides in the APPS_TS_SEED tablespace and carries a SEEDED_FLAG column, the table is clearly intended to hold Oracle-seeded metadata as well as customer-defined extensions.

The table is physically owned by the AMW schema and exposed to the E-Business Suite runtime through the APPS synonym AMW_OBJECT_RULES. From a dimensional modeling perspective, the heuristic Data Vault classification for this object is standalone, with no Parent-Child foreign key relationships to other AMW tables. The only documented foreign key is a reference from SECURITY_GROUP_ID to FND_SECURITY_GROUPS, which supports Multi-Org and hosted-environment security partitioning rather than a business relationship.

Key Information Stored

The table contains seventeen documented columns. The most operationally significant are:

• OBJECT_RULE_ID — The system-generated unique identifier. This is the surrogate primary key, backed by primary key constraint AMW_OBJECT_RULES_PK. It is also the column covered by the unique index AMW_OBJECT_RULES_U1, making it the primary business-key candidate for external references.
• OBJECT_TYPE — Identifies the class of object (for example a document, change order, or other workflow-enabled entity) to which the rule applies.
• APPROVAL_TYPE — Specifies the approval strategy associated with the object type, driving which workflow approval path is activated.
• RULE_USED_BY — Records which component or consumer relies on this rule.
• RULE_TYPE — Classifies the rule itself, allowing multiple rule variants to coexist for the same object type.
• API_TYPE — Indicates the category of the approval API invoked when the rule fires.
• PACKAGE_NAME and PROCEDURE_NAME — Name the PL/SQL package and procedure that Oracle Workflow calls to evaluate or execute the rule.
• SEEDED_FLAG — Distinguishes Oracle-delivered seed rows from customer-created rows, which is essential when assessing upgrade impact.
• APPLICATION_ID — Ties the rule to the owning application registered in FND_APPLICATION.
• SECURITY_GROUP_ID — The foreign key to FND_SECURITY_GROUPS, used primarily in hosted and Multi-Org deployments.
• OBJECT_VERSION_NUMBER — Supports optimistic locking for concurrent updates.

The remaining columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN) constitute the standard WHO audit trail maintained by Applications Forms and concurrent programs.

Common Use Cases and Queries

The most frequent operational need is to inventory which objects are configured for workflow-driven approval and which PL/SQL code they invoke. A useful query joins the rule metadata with the seeding indicator:

SELECT object_rule_id, object_type, approval_type, rule_type,
       package_name, procedure_name, seeded_flag
  FROM amw.amw_object_rules
 WHERE seeded_flag = 'N'
 ORDER BY object_type;

During upgrades, a filter on SEEDED_FLAG = 'Y' isolates Oracle-supplied rows that may be overwritten, while customer extensions can be re-verified. Support teams investigating a missing approval step typically query the table for a specific OBJECT_TYPE and confirm that PACKAGE_NAME and PROCEDURE_NAME resolve to a valid compiled object in the database. Security administrators working in a shared-services or hosted environment join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to validate that rules are visible only to the intended operating unit or security group. Finally, a transaction-level audit query orders rows by LAST_UPDATE_DATE to identify recently modified rules and trace them back to LAST_UPDATED_BY.

Related Objects

Because the table is classification-standalone, the dependency footprint is narrow. The most relevant related objects are:

• FND_SECURITY_GROUPS — Joined on SECURITY_GROUP_ID; the only documented foreign key relationship.
• FND_APPLICATION — Joined on APPLICATION_ID to resolve the application short name and description.
• FND_OBJECTS / FND_OBJECT_INSTANCES — Workflow object registrations that typically mirror the OBJECT_TYPE values held here.
• WF_ITEM_TYPES / WF_PROCESS_ACTIVITIES — The workflow definition tables that consume the package and procedure names supplied by AMW_OBJECT_RULES.
• AMW_OBJECT_RULES_U1 — The unique index on OBJECT_RULE_ID, providing fast single-row lookup.

Despite its small footprint, AMW_OBJECT_RULES is central to ensuring that object approvals are routed to the correct workflow-enabled API at runtime.