Upper Limit - Lower Limit in Measuring Points

Dear PM Experts,
In my company we have an Equipment where the temperature of it has to be maintained in a certain range. if the temperature falls out side the range the maintenance team has to attend. In SAP I registered this point as a measuring point. And I'm aware of the fact that we can maintain Upper and Lower Limits of reading for a measuring point in SAP.
But I want SAP to automatically create a PM Notification/Order once the user enters a value out side the above specified range. I know that this is possible with conters when the reading reaches a certain value. But couldn't figure out a method for the latter.
Please provide me a solution.
Rgds
Deepal

Hello Deepal;
You will have to activate exit: IMRC0003.
Then you'll have to create a maintenance plan, maintaining the equipment & the measuring point. Based on the call object: order/ notification- system will automatically trigger the object when the actual reading falls outside the specified range.
Hope this helps.
Regards
Hemant

Similar Messages

Datatable for upper and lower limit maintained in Measuring Point.

Hi,
I am making use of user exit : IMCR0001. User exit generates maintenance order for measuring reading which are beyong the range maintained in measruing point.
I have create measuring point with characteristics as TEMPERATURE. I have maintained upper limit : 1500 C & lower limit : 1200 C.
When I check datatable IMPTT and look for upper and lower limit, it is showing me : Upper range :1.7731500000000001E03 Lower range : 1.4731500000000001E03
Why is that I can not find the actual value as 1500 and 1200 n the datatable?
In which datatable I can find these values?
Kindly help.
Thanks in advance.
Regards,
TOM.

Hi Tom,
These are system Generated Values, but they will be concatenated by a few Zeros, but you can always find the exact value,
I am able to see the Values correctly in my system follower by some 10-12 zero's "E"+ 02 or 03.
but can check the values
can cross check the Characteristics for the same measuring point?
Regards,
Yawar Khan

Read the signal value that pass over the upper and lower limit..

how to create the system which can read the signal value that pass the lower and upper limit? i've try but the system only read the value that in range of upper and lower limit..thanks..

Im not very sure if this system can read the value that pass over the limit..because at the save file data so many value(i will attach that file)..and i dont know how to setting to get the failure values only..
Actually i want to build some system that can read and save value that pass over the limit..i take the signal from simulation sine signal..no hardware required..
im very new with this software and im in learning process..
A very big thanks to all that helping me..
save file data from the system
Channels 8
Samples 1 1 1 1 1 1 1 1
Date 2012/03/05 2012/03/05 2012/03/05 2012/03/05 2012/03/05 2012/03/05 2012/03/05 2012/03/05
Time 12:30:11.099999 12:30:11.216 12:30:11.216 12:30:11.216 12:30:11.099999 12:30:11.216 12:30:11.216 12:30:11.216
X_Dimension Time Time Time Time Time Time Time Time
X0 1.0000000000000001E-1 1.0000000000000001E-1 1.0000000000000001E-1 1.0000000000000001E-1 1.0000000000000001E-1 1.0000000000000001E-1 1.0000000000000001E-1 1.0000000000000001E-1
Delta_X 0.001000 0.001000 0.001000 0.001000 0.001000 0.001000 0.001000 0.001000
***End_of_Header***
X_Value Sine (Negative Peak) Failures (Negative Peak) Upper Limit (Negative Peak) Lower Limit (Negative Peak) Sine (Positive Peak) Failures (Positive Peak) Upper Limit (Positive Peak) Lower Limit (Positive Peak) Comment
0.100000 -6.999066 -6.999066 5.000000 -5.000000 6.999136 6.999136 5.000000 -5.000000
0.200000 -6.998993 -6.998993 5.000000 -5.000000 6.999204 6.999204 5.000000 -5.000000
0.300000 -6.998917 -6.998917 5.000000 -5.000000 6.999269 6.999269 5.000000 -5.000000
0.400000 -6.998838 -6.998838 5.000000 -5.000000 6.999331 6.999331 5.000000 -5.000000
0.500000 -6.998756 -6.998756 5.000000 -5.000000 6.999391 6.999391 5.000000 -5.000000
0.600000 -6.998672 -6.998672 5.000000 -5.000000 6.999447 6.999447 5.000000 -5.000000
0.700000 -6.998585 -6.998585 5.000000 -5.000000 6.999501 6.999501 5.000000 -5.000000
0.800000 -6.998495 -6.998495 5.000000 -5.000000 6.999552 6.999552 5.000000 -5.000000
0.900000 -6.998403 -6.998403 5.000000 -5.000000 6.999601 6.999601 5.000000 -5.000000
1.000000 -6.998307 -6.998307 5.000000 -5.000000 6.999646 6.999646 5.000000 -5.000000
1.100000 -6.998209 -6.998209 5.000000 -5.000000 6.999689 6.999689 5.000000 -5.000000
1.200000 -6.998108 -6.998108 5.000000 -5.000000 6.999729 6.999729 5.000000 -5.000000
1.300000 -6.998005 -6.998005 5.000000 -5.000000 6.999766 6.999766 5.000000 -5.000000
1.400000 -6.997898 -6.997898 5.000000 -5.000000 6.999801 6.999801 5.000000 -5.000000
1.500000 -6.997789 -6.997789 5.000000 -5.000000 6.999833 6.999833 5.000000 -5.000000
1.600000 -6.997677 -6.997677 5.000000 -5.000000 6.999862 6.999862 5.000000 -5.000000
1.700000 -6.997563 -6.997563 5.000000 -5.000000 6.999888 6.999888 5.000000 -5.000000
1.800000 -6.997445 -6.997445 5.000000 -5.000000 6.999912 6.999912 5.000000 -5.000000
1.900000 -6.997325 -6.997325 5.000000 -5.000000 6.999932 6.999932 5.000000 -5.000000
2.000000 -6.997202 -6.997202 5.000000 -5.000000 6.999950 6.999950 5.000000 -5.000000
2.100000 -6.997076 -6.997076 5.000000 -5.000000 6.999965 6.999965 5.000000 -5.000000
2.200000 -6.996948 -6.996948 5.000000 -5.000000 6.999978 6.999978 5.000000 -5.000000
2.300000 -6.996817 -6.996817 5.000000 -5.000000 6.999988 6.999988 5.000000 -5.000000
2.400000 -6.996683 -6.996683 5.000000 -5.000000 6.999994 6.999994 5.000000 -5.000000
2.500000 -6.996546 -6.996546 5.000000 -5.000000 6.999999 6.999999 5.000000 -5.000000
2.600000 -6.996546 -6.996546 5.000000 -5.000000 7.000000 7.000000 5.000000 -5.000000
2.700000 -6.996683 -6.996683 5.000000 -5.000000 6.999994 6.999994 5.000000 -5.000000
2.800000 -6.996817 -6.996817 5.000000 -5.000000 6.999988 6.999988 5.000000 -5.000000
2.900000 -6.996948 -6.996948 5.000000 -5.000000 6.999978 6.999978 5.000000 -5.000000
3.000000 -6.997076 -6.997076 5.000000 -5.000000 6.999965 6.999965 5.000000 -5.000000
3.100000 -6.997202 -6.997202 5.000000 -5.000000 6.999950 6.999950 5.000000 -5.000000
3.200000 -6.997325 -6.997325 5.000000 -5.000000 6.999932 6.999932 5.000000 -5.000000
3.300000 -6.997445 -6.997445 5.000000 -5.000000 6.999912 6.999912 5.000000 -5.000000
3.400000 -6.997563 -6.997563 5.000000 -5.000000 6.999888 6.999888 5.000000 -5.000000
3.500000 -6.997677 -6.997677 5.000000 -5.000000 6.999862 6.999862 5.000000 -5.000000
3.600000 -6.997789 -6.997789 5.000000 -5.000000 6.999833 6.999833 5.000000 -5.000000
3.700000 -6.997898 -6.997898 5.000000 -5.000000 6.999801 6.999801 5.000000 -5.000000
3.800000 -6.998005 -6.998005 5.000000 -5.000000 6.999766 6.999766 5.000000 -5.000000
3.900000 -6.998108 -6.998108 5.000000 -5.000000 6.999729 6.999729 5.000000 -5.000000
4.000000 -6.998209 -6.998209 5.000000 -5.000000 6.999689 6.999689 5.000000 -5.000000
4.100000 -6.998307 -6.998307 5.000000 -5.000000 6.999646 6.999646 5.000000 -5.000000
4.200000 -6.998403 -6.998403 5.000000 -5.000000 6.999601 6.999601 5.000000 -5.000000
4.300000 -6.998495 -6.998495 5.000000 -5.000000 6.999552 6.999552 5.000000 -5.000000
4.400000 -6.998585 -6.998585 5.000000 -5.000000 6.999501 6.999501 5.000000 -5.000000
4.500000 -6.998672 -6.998672 5.000000 -5.000000 6.999447 6.999447 5.000000 -5.000000
4.600000 -6.998756 -6.998756 5.000000 -5.000000 6.999391 6.999391 5.000000 -5.000000
4.700000 -6.998838 -6.998838 5.000000 -5.000000 6.999331 6.999331 5.000000 -5.000000
4.800000 -6.998917 -6.998917 5.000000 -5.000000 6.999269 6.999269 5.000000 -5.000000
4.900000 -6.998993 -6.998993 5.000000 -5.000000 6.999204 6.999204 5.000000 -5.000000
5.000000 -6.999066 -6.999066 5.000000 -5.000000 6.999136 6.999136 5.000000 -5.000000
5.100000 -6.999136 -6.999136 5.000000 -5.000000 6.999066 6.999066 5.000000 -5.000000
5.200000 -6.999204 -6.999204 5.000000 -5.000000 6.998993 6.998993 5.000000 -5.000000
5.300000 -6.999269 -6.999269 5.000000 -5.000000 6.998917 6.998917 5.000000 -5.000000
5.400000 -6.999331 -6.999331 5.000000 -5.000000 6.998838 6.998838 5.000000 -5.000000
5.500000 -6.999391 -6.999391 5.000000 -5.000000 6.998756 6.998756 5.000000 -5.000000
5.600000 -6.999447 -6.999447 5.000000 -5.000000 6.998672 6.998672 5.000000 -5.000000
5.700000 -6.999501 -6.999501 5.000000 -5.000000 6.998585 6.998585 5.000000 -5.000000
5.800000 -6.999552 -6.999552 5.000000 -5.000000 6.998495 6.998495 5.000000 -5.000000
5.900000 -6.999601 -6.999601 5.000000 -5.000000 6.998403 6.998403 5.000000 -5.000000
6.000000 -6.999646 -6.999646 5.000000 -5.000000 6.998307 6.998307 5.000000 -5.000000
6.100000 -6.999689 -6.999689 5.000000 -5.000000 6.998209 6.998209 5.000000 -5.000000
6.200000 -6.999729 -6.999729 5.000000 -5.000000 6.998108 6.998108 5.000000 -5.000000
6.300000 -6.999766 -6.999766 5.000000 -5.000000 6.998005 6.998005 5.000000 -5.000000
6.400000 -6.999801 -6.999801 5.000000 -5.000000 6.997898 6.997898 5.000000 -5.000000
6.500000 -6.999833 -6.999833 5.000000 -5.000000 6.997789 6.997789 5.000000 -5.000000
6.600000 -6.999862 -6.999862 5.000000 -5.000000 6.997677 6.997677 5.000000 -5.000000
6.700000 -6.999888 -6.999888 5.000000 -5.000000 6.997563 6.997563 5.000000 -5.000000
6.800000 -6.999912 -6.999912 5.000000 -5.000000 6.997445 6.997445 5.000000 -5.000000
6.900000 -6.999932 -6.999932 5.000000 -5.000000 6.997325 6.997325 5.000000 -5.000000
7.000000 -6.999950 -6.999950 5.000000 -5.000000 6.997202 6.997202 5.000000 -5.000000
7.100000 -6.999965 -6.999965 5.000000 -5.000000 6.997076 6.997076 5.000000 -5.000000
7.200000 -6.999978 -6.999978 5.000000 -5.000000 6.996948 6.996948 5.000000 -5.000000
7.300000 -6.999988 -6.999988 5.000000 -5.000000 6.996817 6.996817 5.000000 -5.000000
7.400000 -6.999994 -6.999994 5.000000 -5.000000 6.996683 6.996683 5.000000 -5.000000
7.500000 -6.999999 -6.999999 5.000000 -5.000000 6.996546 6.996546 5.000000 -5.000000
7.600000 -7.000000 -7.000000 5.000000 -5.000000 6.996546 6.996546 5.000000 -5.000000
7.700000 -6.999994 -6.999994 5.000000 -5.000000 6.996683 6.996683 5.000000 -5.000000
7.800000 -6.999988 -6.999988 5.000000 -5.000000 6.996817 6.996817 5.000000 -5.000000
7.900000 -6.999978 -6.999978 5.000000 -5.000000 6.996948 6.996948 5.000000 -5.000000
8.000000 -6.999965 -6.999965 5.000000 -5.000000 6.997076 6.997076 5.000000 -5.000000
8.100000 -6.999950 -6.999950 5.000000 -5.000000 6.997202 6.997202 5.000000 -5.000000

How to set upper and lower limit for service notification in SPRO

Hello everyone,
Good morning....!!
I am new to SAP PM and to SCN as well.
I have a question on Service notification user status.
I have notification profile configured in SAP as below:
Status no      Status          Short text              Lower limit          Upper limit
5                  REGD          Registered                1                          70
10                PCKS            Pack sent                  1                          70
20                APRC            Application received 1                        70
etc..
I want the statusesto be set as navigation should only allow to go back one by one...like from APRC -->PCKS not to REGD.From PCKS -->REGD etc..not vice versa.
Can enayone explain me to how to set lower and upper limits for these according ot the above requirement.
for more details please check my attachment.
Thanks in advance..!!
Regards,
Sudha.

Once you change the status to previous status, just save the order. Then again open the order & try to change the user status.
Just I made replica of your profile. I could able to change (even without saving the order).

Increment and decrement to reach upper and lower limit

I have to simulate a central heating system. A heater is turned on, room temp rises to 'upper limit'; heater is turned off when upper limit is reached. When heater is off, temp drops until lower limit is reached then heater is turned on again. I'm scratching my head!! have tried various case structures but cant get it to run continually. Whats the best way to do this? PS, im a noob! :-)

Use a shift register to keep the current heater state (since you only want the state to change when you go outside of the limits). From there, the Select function helps keep things straight.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
Heater control.png ‏12 KB

MIC with different upper and lower limit

Hi experts,
I have a scenario where I have a characteristic to be tested for trace element in a chemical.
But the upper and lower specification of this MIC is different for different chemicals (material numbers) . ie the specification depends on chemical (material) to be inspected.
So I am stuck with a combination a number of MICs with same trace element (say iron) to be tested for a number of chemicals.
How does QM handle this scenario ?
Rgds
JMG

1st - Are you batch managed? if so you can create a batch class and add a general characteristic to it linked to a single MIC. Use this MIC in your inspection plans. Then in the batch class set the specs limits.
You can create a separate batch class for each group of materials. I.e. those with the same specs.
You can also modify the spec value in the classification view for each material that is different then the spec in the class.
You can also create plans which use the same MIC but in the plan you unlock it and set the spec. Then assign all the materials using that spec to the same plan.
This is all very simplied above. But under NO circumstances should it be necessary to create multiple MICS for the same test with all different specs!
Craig

Define Upper and Lower Limit for condition type

Hi dear All,
I´ve defined a new condition type with calculation rule = percentage and when I created the entry in the PER column and UoM column the system does not allow me to put any value.
Does anybody know how to solve this issue?
Thanks a lot,
Petterson

Once you change the status to previous status, just save the order. Then again open the order & try to change the user status.
Just I made replica of your profile. I could able to change (even without saving the order).

Tolerance key PP - Lower limit

We have configured tolerance key PP with lower limit of 0$ for both absolute and percentage. When I try to post the invoice with a lower price, I receive a warning message that the price is too low (which is correct).
The problem is that when I try to post this invoice, it is getting posted without being blocked. Since the lower limit is defined, shouldn't the invoice be blocked when it is below lower limit defined.
Is there any other setting that I need to make to ensure that the invoice is getting blocked when it is posted below the lower limit defined? Please help. Thanks.

Thanks to both of you! Here are the limits that I defined:
Price variance
Absolute lower limit
Check limit X Value 0,00
Absolute upper limit
Check limit X Value 0,00
Percentage lower limit
Check limit X Value 0,00
Percentage upper limit
Check limit X Value 0,00
Based on the limits defined, an invoice should be blocked when it exceeds either upper or lower limit. The upper limit is working fine. However, the lower limit is not causing the invoice to block.
Eg: PO net price is $100. I post an invoice with price $50. This lower price is not causing the invoice to block.

Measuring Point & Counter

Hi PM Gurus,
Can you tell me about the performance based maitenance :
1. Measuring Point (M.P.)
2.Counter
What are the characterstic units come under the Measuring Point.is it right that only we can give upper and lower limit in M.P not in counters.Also User exit is only created for MP not for counter.
What are the basic difference between Measuring Point & Counter.
In both the cases is it necessary to select counter tick mark or only in case of counter ?Is there is any difference while generating the plan
Regards,
RC

Hi Raju,
You can do this through,
IMG - Maintenance Plan,work center, task list & PRTS - Maintenance Plan - Set maintenance plan catagories.
Here in call object column you can define which type of call object you want for your maintenance order based on this you will get the order or notification as a call object.
And rest of the things measuring point & counter that already defined in this thread.
Regards,
Rip

Measuring Point in Maintenance Plan

How can I link a measuring point (not a counter) to the Maintenance Plan?
Currently, I can only link a counter to a Maintenance Plan but not a measuring point.
The reason why I am asking for this is that I would like to trigger automatic creation of a work order whenever a measurement reading for an equipment goes outside the specified upper and lower limit of a measuring point. I would like to define a condition in the maintenance plan for this based on the measuring point say for example temperature.
I believe activating userexit IMRC0001 is just part of the solution. Is there something else that needs to be done?
Thanks.
Giscard

I have already activated userexit.
Is it correct that the userexit is triggered upon saving a measurement reading (tcode IK11)?
Do you have sample code for the userexit so that a Notification or Work Order will automatically be created when the reading entered is outside the upper and lower limit?
But my questions actually is this - Is possible to link a measurement point (not a counter) to a Maintenance Plan?

Measurement range limits in creating measuring point

Hi,
i'm creating a measuring point where i need to enter the measurement range limits i.e upper range limit and lower range limit.
Can anyone let me know where exactly the values are getting stored i.e table
or any function module available to get lower range limit and upper range limit
Pls let me know if anyone has any idea
Thanks

Hi Taran,
Could you please tell me how did you load the Upper and Lower limit range for measuring points...
Thanks,
Geetha

Upper and lower limits on Chart

I am using crystal version 9
On a line graph is there a way to add an upper and lower limit line on the chart
Thanks

Did you remember to turn off autoscaling? If not, it'll scale right back. Otherwise, you should have the correct property node.

OMR6 upper and lower limits

I am developer and this is not my area of expertise, so not sure if wording will be correct. I believe We place payments blocks on invoices based on values set in OMR6. This is where the configuration is done. However I have been told that the system will not do this for lower limits. Can this be done in OMR6 or is there another area we can do this without having to create a user exit? I'm told that upper limits work fine but that the design of the system does not allow this for lower limits. Anyone have any ideas of where configuration can be done for this?

I had someone here walk me through what was in the setup. For the the Tolerance key "PP" for this specific company there is an upper and lower limit entered and the "check limit" is selected for both upper and lower entries. The upper limit check works but the lower limit check does not work. They said, all SAP notes say you have to enable a specific user exit to get the lower limit to work for "PP". This does not sound right but might be true. Is there something special you have to do with the "PP" type to get it to work? I cannot imagine SAP having the lower limit entry there but not using it, but like I said it is possible.

Lower Limit - Upper Limit in Measuring Points

Dear Experts,
Kindly i need to know where i put SAP ABAP code and what is code ?
steps:
1- active business function IMRC0001 from TCODE: SMOD
2- go to Tcode : IK01 to create measurement point .
3- go to Tcode : IK11 to write measurement if not in range it create notification on Tcode : IW28 < this action done when code abap written >
thanks, best regards

Where to write code
1. SMOD
2 Double click on the Exit name
3. Double click on the Include name
4. This is the area you need to put the code.
What code
It will be a lengthy code and different for your application. So your ABAPer will help you write the code here, upon your specification of the requirements.
Best of Luck
KJogeswaraRao

What is the significance of Safety Upper Limit and Lower Limit

Hello Experts,
I was trying to create a generic datasouce in rso2 , while setting the delta specific field I have selected date field and I need to know the significance of other two input fields provided over there:
Safety Interval Upper Limit.
Safety Interval Lower Limit.
and check box Real Time Enable.
Thanks,
Vijay

Hi Vijay
Safety Interval Upper Limit of Delta Selection This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure. The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read. Leaving the value blank increases the risk that the system could not extract records arising during extraction. Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00. A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either. For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number). Safety Interval Lower Limit This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction. For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems. Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable. these are used to determining the delta in a datasource: 1. Time stamp - The field is a DEC15 field which always contains the time stamp of the last change to a record in the local time format. 2. Calendar day - The field is a DATS8 field which always contains the day of the last change. 3. Numerical pointer - The field contains another numerical pointer that appears with each new record .
also dwload this How to Generic Delta doc https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
2.
You can determine the upper limit of the time. To do this, you specify a time period relative to the current date. The time unit for the time period can be specified in days, weeks, months, quarters, years, posting periods, or fiscal years.
The upper limit can also be rounded down to the end of a time period by selecting another, additional time unit, so that, for example, only complete months or years can be archived when a date field is selected as a selection characteristic for the time slice. The time slice defined in this way contains the complete time period before the upper limit calculated.
1. If delta field is Date (Record Create Date or change date), then use Upper Limit of 1 day.
This will load Delta in BW as of yesterday. Leave Lower limit blank.
2. If delta field is Time Stamp, then use Upper Limit of equal to 1800 Seconds (30 minutes).
This will load Delta in BW as of 30 minutes old. Leave Lower limit blank.
3. If delta field is a Numeric Pointer i.e. generated record # like in GLPCA table, then use
Lower Limit. Use count 10-100. Leave upper limit blank. If value 10 is used then last 10
records will be loaded again. If a record is created when load was running, those records
may get lost. To prevent this situation, lower limit can be used to backup the starting
sequence number. This may result in some records being processed more than once;
therefore, be sure this DataSources is only feeding an ODS Object
Hope this will help you
Thanks & Regards
Kiran

Upper Limit - Lower Limit in Measuring Points

Similar Messages

Maybe you are looking for