Search Results ahl_ctr_update_rules_pk

Overview

AHL_CTR_UPDATE_RULES is a table in the AHL schema belonging to the Complex Maintenance Repair and Overhaul (CMRO) module of Oracle E-Business Suite. It stores the configuration rules that govern how equipment counters are updated for a given position in relation to its parent position within an asset or component hierarchy. In CMRO, positions model the physical or functional slots that components occupy on a maintained asset, and counters track usage measures such as flight hours, cycles, or operating time. This table provides the metadata that determines which counters cascade, multiply, or propagate from a parent position down to a child position and under what unit of measure.

Because the table records how measures move between two related positions, each row effectively describes a relationship-driven event rather than a standalone master entity. From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification: the row is anchored by a relationship identifier to a parent-child association and carries descriptive attributes, including a rule code, unit of measure, and a ratio. This classification is a heuristic modeling suggestion, not a constraint enforced by the application.

Key Information Stored

The table is defined with 28 columns, of which the following are the most significant:

• CTR_UPDATE_RULE_ID — the surrogate primary key, enforced by AHL_CTR_UPDATE_RULES_PK and also supported by unique index AHL_CTR_UPDATE_RULES_U1. It uniquely identifies each rule row.
• RELATIONSHIP_ID — identifies the parent-child relationship between positions to which the rule applies. Together with UOM_CODE and RULE_CODE it forms business key candidate AHL_CTR_UPDATE_RULES_U2.
• UOM_CODE — the unit of measure associated with the counter update, forming part of the unique business key.
• RULE_CODE — the code identifying the behavior of the update rule, also part of the unique business key.
• RATIO — the numeric factor applied when propagating or rolling up a counter value from parent to child position.
• SECURITY_GROUP_ID — the security grouping used to restrict visibility and access, with a foreign key reference to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — supports optimistic locking for concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit columns capturing who created and last modified the row and when.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield (DFF) columns available for customer-specific extensibility.

The documented unique indexes distinguish the surrogate primary key (CTR_UPDATE_RULE_ID) from the composite business-key candidate (RELATIONSHIP_ID, UOM_CODE, RULE_CODE), which together guarantee that only one rule exists per relationship, unit of measure, and rule code.

Common Use Cases and Queries

Typical scenarios involve reviewing which counter update rules apply to a given position relationship, auditing the ratio used for roll-up calculations, and reporting on rules by unit of measure or rule code. A representative query retrieves all rules for a relationship:

SELECT ctr_update_rule_id, relationship_id, uom_code, rule_code, ratio
FROM ahl.ahl_ctr_update_rules
WHERE relationship_id = :relationship_id;

Reporting queries frequently join the table to FND_SECURITY_GROUPS to verify the security context, or filter by UOM_CODE to confirm consistent counter behavior across a hierarchy. Because the business key is composite, developers should query on RELATIONSHIP_ID, UOM_CODE, and RULE_CODE rather than assuming uniqueness on any single column. The DFF attribute columns are commonly used when organizations extend counter rules with site-specific configuration values.

Related Objects

The following objects are most relevant to AHL_CTR_UPDATE_RULES based on the documented relationship data:

• AHL_CTR_UPDATE_RULES (self-referencing RELATIONSHIP_ID) — the relationship column references the position relationship construct, tying each rule to a specific parent-child pairing.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, controlling row-level security for the rule definition.
• AHL_POSITION_RELATIONSHIPS — the logical parent of RELATIONSHIP_ID, defining the structure the rule acts upon.
• AHL_COUNTERS / AHL_COUNTER_VALUES — the counter definitions and stored readings that the rules ultimately update.
• AHL_UNITS_OF_MEASURE — the source of UOM_CODE values used to qualify counter updates.
• AHL_CTR_UPDATE_RULES_PK and AHL_CTR_UPDATE_RULES_U2 — the primary and unique constraints enforcing identity and business-key uniqueness.