Customer Exit IMRC0001 for condition based preventive maintenance

Question

Dear Experts,
I am using customer Exit IMRC0001 for creating maintenance order if my measuring point reading exeeds the thresold value or it is  out of the upper and lower limit range , which i have set for that particular Measuring point.
This scenario is working fine if i am creating measuring point with unit *C (Degree centigrade-Temp).
But it is not working fine for measuring point having unit other then *C
Like : Kg/Cmsq, Bar, Run Hr, Vaccum, voltage, current, consumption etc
The Reason for this i have found out.The logic return in the program only considers the *C unit
Say if i set 50c as my target value in Measuring point*
In Table IMPTT the value is getting stored as 50 + 273.15 = 323.15
But if i enter 5 Ohm as my target value in Measring point
In Table IMPTT the value is getting stored as 5 only.
Target Value field name is DESIR
So i want to know why for some units the same value is getting stored and why for some units value with some formula getting stored.
Regards,
Amar Jadhav

Answer 1

does your characteristic allow decimals??
also why not use deg K instead of deg C
ignore above
see note 525948
Symptom
When you change the target value of a measuring point, it seems as if the system updates incorrect values for the 'Target value' field in the change documents.
Other terms
IK02, IK03, IMPT
Solution
The internal display of field 'Measuring Point Target Value' has the SI unit belonging to the unit of measurement.
Example:
For temperatures, the target value can be displayed in the user interface (RIMR0-DESIC) in the units of measurement Celsius, Fahrenheit or Kelvin. However, the database display in field IMPTT-DESIR always refers to the respective SI unit Kelvin.
As the change documents always refer to the database display, they also refer to the SI unit.
Edited by: Virendra Pal on Oct 1, 2008 2:34 PM