Search Results ahl_mc_rule_statements




Overview
Explore in AI Chat

Overview

AHL_MC_RULE_STATEMENTS is a table in the AHL schema (Complex Maintenance Repair and Overhaul) within Oracle E-Business Suite. It stores the individual rule statements that make up maintenance rules defined in the AHL module. Each row represents a discrete statement composed of a subject, an operator, and an object, forming the logical building blocks from which complete maintenance and repair rules are assembled. The table is central to the rule engine that governs how the AHL product evaluates conditions during complex maintenance, repair, and overhaul activities.

From a Data Vault modeling perspective, the metadata's heuristic classification indicates this object is satellite-leaning. This suggests it behaves primarily as a descriptive, attribute-bearing entity that records changing details around a parent business key, rather than acting as a standalone hub or a pure association link. The heavy presence of auditable and descriptive columns, together with self-referencing foreign keys on SUBJECT_ID and OBJECT_ID, supports this interpretation. The self-referencing relationships further suggest hierarchical or nested rule construction, where statements can reference one another.

Key Information Stored

The table contains 37 documented columns. The surrogate primary key is RULE_STATEMENT_ID, enforced by the primary key constraint AHL_MC_RULE_STATEMENTS_PK and also backed by the unique index AHL_MC_RULE_STATEMENTS_U1. RULE_STATEMENT_ID is the single documented business-key candidate.

The most important stored information includes the following:

Common Use Cases and Queries

Typical usage centers on retrieving and validating the composition of maintenance rules. A common query joins statements back to their rule and resolves security group access:

  • Retrieve all statements for a given rule: SELECT RULE_STATEMENT_ID, SUBJECT_ID, OPERATOR, OBJECT_ID FROM AHL_MC_RULE_STATEMENTS WHERE RULE_ID = :p_rule_id;
  • Identify top-level statements: ... WHERE TOP_RULE_STMT_FLAG = 'Y';
  • Find negated clauses: ... WHERE NEGATION_FLAG = 'Y';
  • Join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to restrict results to authorized security groups.
  • Self-joins on SUBJECT_ID and OBJECT_ID to traverse nested statement hierarchies.

Reporting use cases include auditing rule definitions, tracing which statements reference which subjects and objects, and validating rule completeness before deployment. Because the table carries OBJECT_VERSION_NUMBER, integration or data-load routines should honor optimistic locking semantics.

Related Objects

The most significant related objects are identified through the documented foreign key relationships:

  • AHL_MC_RULE_STATEMENTS (self-referencing) — via SUBJECT_ID and OBJECT_ID; these self-joins model nested or dependent statements.
  • AHL_MC_RULE_STATEMENTS.RULE_ID — references the parent rule, linking statements to their enclosing rule definition.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, enforcing multi-organization security access.
  • The RULE_ID, SUBJECT_ID, and OBJECT_ID relationships collectively anchor this satellite table to the broader AHL rule configuration model.

Because the metadata lists several unresolved foreign key targets (marked as unknown tables), administrators should confirm the exact parent objects via AHL's rule configuration and dictionary views when building joins. In practice, this table is queried alongside the AHL rule and rule-statement view layer to reconstruct complete, human-readable rule definitions for maintenance planning and execution.