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).

Similar Messages

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).

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

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

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

Remove upper and lower filters for portable devices?

My flash drive was used to download 2 movies- it is 16 GB- but I can not delete the movies to make room for anything else on the drive it keeps saying "write protected". I did not do this, the movies were downloaded from off the internet, how
can I unprotect this media to delete it?
Tony A. Smith,III.

Try looking for a sliding switch on the flash drive. Some flash drives have this switch to provide write protection for the contents and it can be easy to accidentally enable it.
In the image below you can see a slider on the side of the drive that can move between a lock symbol and an unlocked symbol.
If this does not help try reading
http://www.makeuseof.com/tag/how-to-fix-write-protection-errors-on-a-usb-stick/

5.000,00 exceeds the limit 100,00 for condition type PR00.

Please help me to resolve this problem as I am not able to find where sud I go to delete the upper and lower limit of condition type PR00..Whene I maintain the record for pr00 for different material it create a error with limits.

Hi
What error message you are getting? Can you check if you have maintained anything for PR00 in SD > Basic Functions > Pricing > Define condition types > Maintain upper and lower limits.
Thank$

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.

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.

UPPER and lower case file extensions for Photo Shop Elements using Windows 7

How do I persuade WIndows 7 to show both UPPER and lower case file extensions, which is a very useful facility offered by my ancient, 2002, version of Photoshop Elements? When processing large volumes (100 plus) photos it is very useful to be able to spot those that have been processed among those awaiting my gentle touch. The JPEG file extension produced by my camera is UPPER case so by using "Save as" with lower case the modified photos are immediately spotted. This worked fine on Windows XP and the same programme has loaded and works well on my new laptop which came loaded with Windows 7 EXCEPT that it persists in using UPPER case all the time, irrespective of the preference settings in PSE. HELP!
Camperman1

In PSE there is a facility "File > process multiple files".
Using this facility you can actually process multiple files at one go and you can easily rename images.
Addi

Pricing limits for condition type PR00

Hi,
I have got a scenario at hand, where i have to assign tolarence limits to all the conditions types in the pricing procedure. i have maintained limits in Transaction OVB2 except Base price condition type i.e. PR00. the problem i am facing is, we have got some where around 1,500 material and 3,200 customers and the price variation between the material is large(3000-150000). The main purpose of maintaining limits is to reduce the risk when entered manually. Please do consider the general business implications while replying.
eg: new pricing procedures, condition records for base price etc makes a hafty job, so can you please suggest me any other means to have a tolerence limit to condition type PR00(PR00 is used as base price for all pricing procedures).
Thank you, Have a nice day at work.
with regards
RVS Prasad

Hi venkata siva
As you are having around 1500 materials in your business . That means you need to maintain condition records for all these materials. While maintaining condition records only , in VK11 for PR00 condition type , maintain upper limit and lower limit in additional data . Then there should not be an problem
Another way of maintaining pricing at upper limit and lower limit is in OVB2.
Regards
Srinath

Authorization for condition type

I came across a requirement where the sales executive should enter less than or equal to 5% discount from his user id.only the sales manager can enter the more than 5% discount from his user id. is there any authorisation for entering pricing discount.

hi,
may be maintain two different condtion types ( DIS1 and DIS2 )one for executive and one for manager and fixt the upper and lower limits accordingly so that the executive cannot give more than 5 % disc. As well fix a lower limit for the manager as 5 % and so that he can give only more than that.
Let the executive enter value only for DIS1 and manager for DIS2. Try it.
Thanks
Sadhu Kishore

Generic Data Extraction : Setting of Upper and Lower Limits

Hi all,
I'm doing the delta extraction for this non-standard infocube which stores data about measuring documents. The strategy I used was to first update a ODS with the new/changed measuring documents determined by their last changed date. Then it will update the infocube with the new values. In order to get the delta measuring documents to go into the ODS, I specify a upper limit of 1 and lower limit of 0 in the extractor's generic delta settings to get measuring documents that are created/changed the previous day. But the system will still take in the full set of measuring document.
Is there something that I have missed out?
Thanks

Hi,
I dont see anything wrong with what you have done. That is correct, it is recommended that the upper safety interval should be set to 1.
But according to you, the system still gets the newly changed records as of current day. Have you checked the update mode? It should be DELTA UPDATE. It might be marked as FULL UPDATE.
Have you successfully initialized the DELTA Update?
Are you using an appropriate DELTA field? It should be a Calendar Day.
Hope I did help and if i did, please grant points...
--Jkyle

Currency conversion issue for condition type

Hello,
I am creating two invoice document.
1. Customs Invoice (ZCDS)
2. Inter company invoice.(IVA)
both the invoices should be similar. Same pricing procedure is used to create both the documents but in Customs invoice YUMU condition type is not getting converted whereas in IVA the condition type is getting converted. Can anyone tell me the possible reason for this?
ZCDS
IVA
Regards,
Jagjeet

Hi Jagjeet,
For IVA invoice type -(For condition type- YUMU)
Below highlighted part of code is changing KSTEU from 'E' to 'C' for IVA invoice using std prog RVIVAUFT.
For ZCDS Invoice Type -(For condition type- YUMU)
Program RVIVAUFT is not called since ZCDS is not trigerried using Output type unlike IVA.
Hence KSTEU is not getting updated from 'E' to 'C' in case of ZCDS.
To solve your problem write code in User exit - userexit_pricing_copy to change konv-ksteu to 'C' for YUMU condition type at runtime.This will definately solve your problem.This will ensure you get correct/same condition value for IVA and ZCDS...:)
Regards,
Vikas Mulay.

Define Upper and Lower Limit for condition type

Similar Messages

Maybe you are looking for