Counter-Based Warranty Creation from Work Order Item Consumption
Counter limits automatically adjust based on asset's current usage when warranties are created from work order item consumption
Counter Registration Policy validation ensures data quality (Skip, Close with Last, Close with Last on Date, No skip)
Automatic counter reading detection based on policy settings
Counter notification threshold calculated as percentage of adjusted limit
Adjusted limits = template limit + asset's current counter reading
+How It Works+
When consuming items on work orders that trigger warranty creation, the system adjusts counter limits to account for the asset's existing usage. The Counter Registration Policy (configured on Work Order Header) determines validation behavior.
Counter Registration Policies:
Skip Policy:
No counter validation required
Warranties created without counter reading
Close with Last Policy:
System automatically finds most recent counter reading
Requires at least one counter reading exists for asset
No manual counter selection needed
Counter limit adjusts based on asset's most recent counter reading
Close with Last on Date Policy:
System automatically finds counter reading on posting date
Requires counter reading exists on exact posting date
No manual counter selection needed
Counter limit adjusts based on asset's last counter reading on posting date
No Skip Policy:
Requires explicit counter reading selection on work order
Counter reading must be assigned before posting
Provides precise warranty tracking control
Counter limit adjusts based on selected counter reading
Example:
Template: Counter Limit = 1000 hours, Threshold = 90%
Asset current usage: 500 hours
Created warranty: Counter Limit = 1500 hours, Threshold Value = 1350 hours (90% of 1500)
+How It Does NOT Work+Policy Enforcement:
❌ Cannot create counter-based warranties without counter reading when policy = "No skip"
❌ Cannot create warranties if no counter history exists when policy = "Close with Last"
❌ Cannot create warranties if no counter reading on posting date when policy = "Close with Last on Date"
❌ Cannot bypass policy validation - policy is enforced at warranty creation time
Counter Reading Assignment:
❌ "Close with Last" policies do NOT require manual counter selection
❌ "No skip" policy does NOT automatically find counter readings
❌ Counter limits do NOT stay at template values - always adjusted for current usage
❌ Threshold percentages do NOT apply to template limits - calculated from adjusted limits
Scope:
❌ Enhancement does NOT affect manually created warranties
❌ Does NOT recalculate existing warranties
❌ Policy settings do NOT apply across different work orders automatically
+Upgrade Impact+
Only affects newly created warranties from work order item consumption
Existing warranties remain unchanged - no recalculation
No data migration required
Review Counter Registration Policy settings on work order templates
Ensure counter recording processes align with selected policies