Results for “ahl_mc_rules_b”

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

Overview

AHL_MC_RULES_B is the base table that stores Maintenance Constraint (MC) rules within the Oracle E-Business Suite product AHL — Complex Maintenance Repair and Overhaul. It resides in the AHL schema and is classified as VALID in the ETRM metadata for release 12.1.1 and 12.2.2. The table persists the rule definitions that drive constraint checking and rule evaluation logic for a Maintenance Constraint header, forming the operational rule layer that sits beneath the MC header record.

Each row in AHL_MC_RULES_B represents a single named rule attached to a Maintenance Constraint header. The rule is the child entity in the header-to-rule relationship: an MC header may own multiple rules, and each rule belongs to exactly one header. This parent-child dependency is confirmed by the foreign key path AHL_MC_RULES_B.MC_HEADER_ID referencing the MC header definition, and by the composite unique index AHL_MC_RULES_B_U2 on (MC_HEADER_ID, RULE_NAME), which enforces that a rule name is unique only within its parent header.

From a data-modeling perspective, the ETRM heuristic classifies this object as satellite-leaning, meaning it is best treated as an attribute-bearing child that extends its parent rather than as a hub or a junction. The classification is a modeling suggestion inferred from the foreign-key structure, not a normative declaration, but it correctly reflects the one-to-many header-to-rule dependency.

Key Information Stored

The table contains 29 documented columns. The most significant are:

• RULE_ID — the surrogate primary key, enforced by AHL_MC_RULES_B_PK and also asserted by the unique index AHL_MC_RULES_B_U1. This is the single-row identifier used by all downstream references.
• MC_HEADER_ID — the foreign key to the Maintenance Constraint header. Together with RULE_NAME it forms the business-key candidate AHL_MC_RULES_B_U2.
• RULE_NAME — the user-facing name of the rule, unique within its parent header. This is a business-key candidate, not the surrogate.
• RULE_TYPE_CODE — the coded classifier determining which rule-evaluation logic applies to the row.
• ACTIVE_START_DATE and ACTIVE_END_DATE — the effective-dating window that governs when the rule is in force.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, controlling which security grouping may access the row in a multi-organization or filtered context.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the EBS framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS who-columns providing audit lineage for every insert and update.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive-flexfield columns, enabling without-customization extension of rule metadata.

The surrogate key RULE_ID should be used for all physical joins; RULE_NAME and MC_HEADER_ID should not be relied upon as globally unique identifiers.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios retrieve all rules for a given constraint header, filter rules by active date range, or list rules by type. A representative query joining the table to its header is:

• SELECT r.rule_id, r.rule_name, r.rule_type_code, r.active_start_date, r.active_end_date FROM ahl.ahl_mc_rules_b r WHERE r.mc_header_id = :header_id ORDER BY r.rule_name;
• Active-rule filtering applies SYSDATE BETWEEN NVL(active_start_date, SYSDATE) AND NVL(active_end_date, SYSDATE) to isolate rules in force.
• Rule-type summarization groups by RULE_TYPE_CODE to count rule coverage across headers.
• Concurrency troubleshooting selects RULE_ID, OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY to trace who last modified a rule.

Because the table exposes flexfield attributes, reporting against ATTRIBUTE1 through ATTRIBUTE15 supports site-specific enrichments without schema changes.

Related Objects

• AHL_MC_RULES_TL — the translation table for rule names and descriptions, joined on RULE_ID.
• AHL_MC_HEADERS_B — the parent Maintenance Constraint header referenced by MC_HEADER_ID.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID to enforce row-level access filtering.
• AHL_MC_RULE_DETAILS — the child detail records that further decompose a rule, joined on RULE_ID.
• AHL_MC_RULES_B_PK / _U1 / _U2 indexes — the primary, unique, and business-key indexes that enforce integrity and drive lookup performance.