Life To Date is Corrupted after Zero Meter Reading for Update Type Meter (Doc ID 1344898.1)

Last updated on OCTOBER 25, 2016

Applies to:

Oracle Installed Base - Version 12.1.2 and later
Information in this document applies to any platform.

Symptoms

Below we listed two symptoms where this issue can happen.  In either case same solution can be applied.

First Symptom:

Actual Behavior
After applying <Patch 12536426>, if a Work Order (WO) is completed with a zero meter reading, the Life to Date reading is recalculated incorrectly. This occurs when the WO reading date/time is less than the last reading.

Expected Behavor
Expect that the Life to Date reading would not be corrupted by a zero reading.

Steps to Reproduce
The issue can be reproduced at will with the following steps:

Responsibility: Maintenance Superuser > search for a work order WO assigned to meter rule based PM scheduling.
Meter is Change Type - Ascending

1. Meter readings are imported by Meter reading import in on-line mode from manufacturing lines. New meter readings are entered before the technician completes the existing preventive maintenance WO.
2. Complete work order and enter a zero meter reading. The reading date is less than last existing meter reading (from import).
3. Life to Date value is incorrectly recalculated for all meter readings after this zero value. Life to Date value is constant from date with zero meter reading
4. The same behavior occurs, regardless of how the zero meter reading was added - as WO completion data or directly from Asset tab - meter reading
5. Due to this issue, the Life to Date reading is corrupted, and Preventive Maintenance (PM) Work Orders are incorrectly generated.

Second Symptom:

ACTUAL BEHAVIOR
---------------
Net and Life to Date calculations are going wrong when the time stamp of the current reading is prior to the existing reading time stamp.EXPECTED BEHAVIOR

Expected behavior
-----------------------
Net and Life to Date calculations should be correct even though the time stamp of the current reading is prior to the existing reading time stamp.STEPS

Steps to reproduce
-----------------------
The issue can be reproduced at will with the following steps:

1. Navigation: Oracle install base agent user-->item instance

2.Go to counters tab and search for the counter

3.enter the reading with the time stamp prior to the reading in the history, the net and life to date will not be sum up to previous reading.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms