Results for “ahl_mc_rule_statements_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The table AHL.AHL_MC_RULE_STATEMENTS is a core data object within the Oracle E-Business Suite (EBS) Oracle Complex Maintenance, Repair and Overhaul (CMRO) / Enterprise Asset Management family of modules — specifically the Asset Lifecycle (AHL) schema, which underpins Maintenance Management rule processing. The object stores Maintenance Condition (MC) rule statements, meaning the individual logical building blocks that together compose a complete maintenance rule. Each row represents one statement — a subject, an operator, and an object — that a rules engine evaluates to determine whether a maintenance rule evaluates to true or false.

The object is documented as VALID in both EBS 12.1.1 and 12.2.2, resides in the APPS_TS_SEED tablespace, and carries the FND Design Data reference AHL.AHL_MC_RULE_STATEMENTS. Based on the foreign-key topology — where the table references itself through SUBJECT_ID and OBJECT_ID and is referenced back by those same columns — the heuristic Data Vault classification for this object is satellite-leaning. In Data Vault modelling terms, this suggests the table behaves primarily as a descriptive satellite attached to a parent rule hub (RULE_ID), with self-referencing links used to build recursive statement hierarchies.

Key Information Stored

The table contains 37 documented columns in 12.2.2. The most functionally significant are summarized below.

• RULE_STATEMENT_ID — NUMBER, the surrogate primary key (AHL_MC_RULE_STATEMENTS_PK) and unique identifier of each rule statement. It is also the single column of the unique index AHL_MC_RULE_STATEMENTS_U1, which stands as the business-key candidate for this object.
• RULE_ID — NUMBER, foreign key back to the MC Rules parent. Also indexed non-uniquely by AHL_MC_RULE_STATEMENTS_N1, which supports fast retrieval of all statements belonging to a rule.
• TOP_RULE_STMT_FLAG — VARCHAR2 marker identifying the top-level (root) statement of a rule hierarchy.
• NEGATION_FLAG — VARCHAR2 indicator that the statement's logical result should be negated.
• SUBJECT_ID and SUBJECT_TYPE — the left-hand operand of the statement. Subject type distinguishes a POSITION from a nested RSTMT (rule statement), enabling recursive statement trees.
• OPERATOR — VARCHAR2(30) the rule operator applied between subject and object (for example, equality, greater-than, containment).
• OBJECT_ID and OBJECT_TYPE — the right-hand operand, again permitting either a concrete object reference or a nested rule statement.
• OBJECT_ATTRIBUTE1 through OBJECT_ATTRIBUTE5 — VARCHAR2(30) free attributes qualifying the object side of the expression.
• OBJECT_VERSION_NUMBER — NUMBER used for optimistic locking during concurrent updates.
• SECURITY_GROUP_ID — NUMBER used in application hosting and referenced by FND_SECURITY_GROUPS.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Who columns for audit tracking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1..ATTRIBUTE15 — descriptive flexfield (DFF) structure-defining and segment columns for client-specific extensions.

Common Use Cases and Queries

Typical reporting and diagnostics against this table include retrieving all statements for a given rule, reconstructing a rule's full logical expression tree, and identifying rules that reference other rule statements recursively.

• Rule composition report — join to the parent rule and list every statement, using N1 for performance:
  SELECT rule_statement_id, subject_id, operator, object_id FROM ahl_mc_rule_statements WHERE rule_id = :p_rule_id;
• Root-statement identification — isolate the entry point of a rule hierarchy:
  SELECT * FROM ahl_mc_rule_statements WHERE rule_id = :p_rule_id AND top_rule_stmt_flag = 'Y';
• Recursive nesting traversal — because SUBJECT_ID and OBJECT_ID can point back into this same table (as RSTMT subjects/objects), a hierarchical (CONNECT BY) query can walk a nested statement tree to validate rule logic or detect circular references.
• DFF-based operational reporting — query ATTRIBUTE1..ATTRIBUTE15 keyed by ATTRIBUTE_CATEGORY to surface site-specific statement attributes in BI Publisher or Discoverer reports.
• Security-scoped extraction — filter by SECURITY_GROUP_ID in multi-org / hosting environments to ensure users only see statements in their authorized security group.

Related Objects

• AHL.AHL_MC_RULE_STATEMENTS (self-referencing) — joins on SUBJECT_ID = RULE_STATEMENT_ID and OBJECT_ID = RULE_STATEMENT_ID, enabling nested rule statement hierarchies.
• AHL_MC_RULES — parent rule definition; join via AHL_MC_RULE_STATEMENTS.RULE_ID = AHL_MC_RULES.RULE_ID.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for application hosting security scoping.
• AHL_MC_RULE_HEADERS / related MC rule tables — upstream rule configuration objects holding the rule metadata that these statements elaborate.
• AHL rule engine APIs and concurrent programs — the MC rule evaluation processes consume statement rows at runtime to evaluate maintenance conditions across asset positions.
• AHL_POSITIONS — referenced indirectly as the POSITION subject/object type, joining through SUBJECT_ID / OBJECT_ID when SUBJECT_TYPE or OBJECT_TYPE equals POSITION.

Because the table is designated FND Design Data and resides in the seed tablespace, it should be treated as a standard seeded object; extensions are expected to be implemented through the descriptive flexfield columns rather than direct DDL modification.