Search Results ahl_ctr_update_rules_u1




Overview

The AHL.AHL_CTR_UPDATE_RULES table is a seed data table within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, residing in the AHL (Complex Maintenance, Repair, and Overhaul) schema. It stores the configuration rules that govern how counter readings are updated for a position (an assembly or component) relative to its parent position within the asset hierarchy. In the context of ETRM, counters track usage metrics such as flight hours, cycles, or operating time, which drive maintenance program scheduling and due-date calculation.

From a Data Vault modeling perspective, this table exhibits a satellite-leaning profile. Its relationship to AHL_RELATIONSHIPS is captured via the RELATIONSHIP_ID foreign key, while the SECURITY_GROUP_ID column ties records to FND_SECURITY_GROUPS for multi-tenant or application-hosting isolation. The physical schema holds 28 documented columns with two unique indexes, and it is stored in the APPS_TS_SEED tablespace with a PCT Free of 10. The ETRM status is VALID and FND design data is registered as AHL.AHL_CTR_UPDATE_RULES.

Key Information Stored

The following represent the most operationally significant columns:

  • CTR_UPDATE_RULE_ID — Surrogate primary key (NUMBER) and the anchor of the AHL_CTR_UPDATE_RULES_PK primary key constraint. It is the sole column of the unique index AHL_CTR_UPDATE_RULES_U1, which is the object users identify when searching for "ahl_ctr_update_rules_u1".
  • RELATIONSHIP_ID — Foreign key to AHL_RELATIONSHIPS, identifying the parent-child position pairing to which the rule applies.
  • UOM_CODE — Unit of measure for the counter being updated.
  • RULE_CODE — Varchar2(30) rule identifier. The code 'Standard' is seeded by Oracle; customer-specific codes are seeded by implementers.
  • RATIO — Numeric ratio applied when rolling up counter values from child to parent position.
  • OBJECT_VERSION_NUMBER — Locking sequence number supporting optimistic concurrency in the OAF/BC4J framework.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, used in application hosting deployments.
  • Standard Who columnsLAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.
  • ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield (DFF) structure and segment columns for customer extension.

Business-key candidates are defined by the unique indexes: AHL_CTR_UPDATE_RULES_U1 (CTR_UPDATE_RULE_ID) and AHL_CTR_UPDATE_RULES_U2 (RELATIONSHIP_ID, UOM_CODE, RULE_CODE). The composite U2 constraint prevents duplicate rule definitions for the same relationship/UOM/rule combination.

Common Use Cases and Queries

Typical scenarios include auditing which rules are configured for a given parent-child relationship, verifying ratio settings across multiple counter UOMs, and troubleshooting counter roll-up discrepancies.

Query rules for a specific relationship:

SELECT r.CTR_UPDATE_RULE_ID, r.UOM_CODE, r.RULE_CODE, r.RATIO
FROM   AHL.AHL_CTR_UPDATE_RULES r
WHERE  r.RELATIONSHIP_ID = :p_relationship_id
ORDER  BY r.UOM_CODE, r.RULE_CODE;

Identify customer-defined rules beyond the seeded 'Standard' code:

SELECT RULE_CODE, COUNT(*)
FROM   AHL_CTR_UPDATE_RULES
WHERE  RULE_CODE <> 'Standard'
GROUP  BY RULE_CODE;

Reporting joins to AHL_RELATIONSHIPS enrich the rule set with parent and child item descriptions. DFF attributes can be queried by filtering ATTRIBUTE_CATEGORY to the appropriate structure, a common pattern when customers store program-specific metadata alongside the rule.

Related Objects

  • AHL.AHL_RELATIONSHIPS — joined on AHL_CTR_UPDATE_RULES.RELATIONSHIP_ID = AHL_RELATIONSHIPS.RELATIONSHIP_ID; the parent position hierarchy source.
  • AHL.AHL_CTR_UPDATE_RULES_PK — primary key constraint on CTR_UPDATE_RULE_ID.
  • AHL.AHL_CTR_UPDATE_RULES_U1 — unique index on CTR_UPDATE_RULE_ID.
  • AHL.AHL_CTR_UPDATE_RULES_U2 — composite unique index on RELATIONSHIP_ID, UOM_CODE, RULE_CODE.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for hosting isolation.
  • FND_DESCRIPTIVE_FLEXS — supports the ATTRIBUTE_CATEGORY DFF structure registration.
  • AHL.AHL_COUNTERS / AHL.AHL_COUNTER_READINGS — downstream consumers that apply these rules during counter roll-up.