Tolerance Upper & Lower limit in MIRO

Dear All,
my scenario is when i am doing MIRO that Vendor bill amount is 1000/- & SAP Amount 990 so i want set tolerance for upper limit 10/- rupees & lower limit for 100/- rupees.
is it possible & please suggest me what can i do.?
Thanks
Sachin Deshmukh

Hi,
As per your suggestion i hvae set Activate item Amount check tick For Company Code. After that i set tol key PP for upper 10val & lower 100Val.
after i create new MIRO & check my scenario but it is not working. its working only lower limit & it shows Warning message.
its my company csenario.
please help me.
Thanks

Similar Messages

Safety Upper/Lower limit in delta extraction

hi all
since i am new,just i want to know
what is the diff between safety lower limit and upper limit
and how these are used in delta.
thankq in advance

I do see that you are new - but the topic of safety limits has been discussed many a time on the forums - please search the forums before you post...

Upper/Lower limit for delta extractor

Hi Experts,
Where can I see the configuration of the upper/lower safety limit for a delta extractor (tcode)? I would like to determine the configuration of one of our FI extractors.
Regards
Mark

Hi Chandra,
When checking the source system the extractor is extracted using FM RKE_BIW_GET_DATA_API. When we display the datasource and click on generic delta, we are getting an error "Specified table does not exist."
Forgot to mention this is a SAP delivered extractor for CO-PA.
Regards
Mark

Purchase net price condition - Upper, lower limit!

Hi SAPients,
Please help me on this one.
While creating a PO, I want the system to throw an error when the net price entered in the PO is 10% more or 20% less than the price I have maintained in the Purchasing info record. Is there a way of configuring this somehow? Any other work around or suggestions also welcome. Thank you!
Thanks and regards,
Arun

Hi Arun,
I think you might have a couple of options here:
1,Check out T-code OLME   > condition   >define price
determination   > define limits
However here you are required to give a unit of measure, if in a info
record which has a different unit of measure than here, then the price
variance check will not performed,
Perhaps, you may insert several entries for PB00 but with different unit
of measures
once the price in info record (me12)exceed the variance limit, error
message VK 038 will appear .
2.IMG   >MM-Purchasing >PO >Set Tolerance Limits for Price Variance.
Here you can maintain the varaince limit then in me21n the effective
price will be checked against the valuation price in mm03, if it exceed
the tolerence, Effective price higher than material price will be issued,
However,this check will not perform directly in the me12
it will be checked in me21n later.
Hope this helps.
Best regards,
Adam.

Define upper/lower limits for shipment cost condition

Hi people, help please!
How can I define upper/lower limit for shipment cost conditions?.
The transaction TK11 has the functionality for upper/lower limits, but I can't find how to define it in customizing.
I follow the path Logistic Execution>Transportation>Pricing>Pricing Control>Define Condition Types, but is not like the transaction for pricing elements in condition types for sales.
How can I do it?
Regards.

The problem is on the class condition import limits.
I cant customize upper and lower prices for the shipment cost class condition and i cant find how define it or what else can I do.
The customizing transaction for shipment cost lass condition is not like sales price class condition, please look this:
For the shipment cost class condition follow the path SPRO>Logistic Execution>Transportation>Shipment Cost>Pricing>Pricing Control>Define Condition Types.
For the sales price class condition follow the path SPRO>Sales and Distribution>Basic Function>Pricing>Pricing Control>Define Condition Types, and take a look in Define upper/lower limits for conditions.
So then, when I go to functional transaction VK11 for the sales price condition y cant assign an import out of the limits defined. I need the same for shipment cost condition, transaction TK11, but I cant find where define the limits, as result, user can load any import without limits.
I hope the explanation is useful.

Amending the mic upper lower limits at the time of RR

Hi, Please advise how to change the upper lower limit of the mic during resultts recording? Also advise how to cancel the recorded values of the results recording so that the lot status becomes REL? Can we change REL to CRTD status. Thank you every one supporting the beginners.

please advise how to change the upper lower limit of the mic during resultts recording?
Its really not possible
Also advise how to cancel the recorded values of the results recording so that the lot status becomes REL?
You can not cancel but change the values .This is possible if you declare all char as "Long term " char in control indicator.
This will give status LTIN to char which allows you to change the RR values at any times
Can we change REL to CRTD status.
In QA02-->click on "Reset"-->save -->this will change status from REL to CRTD.
but this is only possible when UD is not taken

Invoice Tolerance variance PP not working for lower limit

I am working in ECC 6.0 environment. I had configured tolerance variance PP to check MIRO value with GR Value. I had maintained upper and lower tolerance limits equal to 1000/- and had set messages M8082 and M8084 to error to stop invoice activity if invoice value is not within interval specified by tolerance variance.
I had posted a GRN with value 5000/-. Now, at time of MIRO ---
1) If i change MIRO value more than 6000/-, error message M8082 is there, which is correct.
2) But, if i decrease MIRO value by 500/- (which is within lower limit of variance), error message M8084 is there which should not be there until MIRO value will be reduced by more than 1000/-.
Kindly resolve this issue asap.

Hi !
Please note the following:
The system will check the lower tolerance limit but an invoice will
never be blocked if the LOWER limit is exceeded. The system will only
display a warning message. In the standard system invoices will only be
blocked if the UPPER limit is exceeded because normally one wants to
prevent to pay more than expected.
In SAP Library: MM-Invoice with Variances-Tolerances you will also
find the following explanation:
Variances are allowed within predefined tolerance limits. If a varianc
exceeds a tolerance limit, however, the system issues a message
informing the user. If an upper limit (except with BD and VP) is
exceeded, the invoice is blocked for payment when you post it. You mus
then release the invoice in a separate step. If the tolerance limit fo
BD is exceeded, the system cannot post the invoice."
The system will check the lower limit but an invoice will never
be blocked if the lower limit is exceeded. The system will only
display a warning message. In the standard system invoices will only b
blocked if the upper limit is exceeded because normally one
wants to prevent to pay more than expected.
Best regards
Erika

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.

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

Tolerance limit for MIRO document

Hi Gurus,
We have 3 below scenarios on Tolerance limit in MIRO document and need a guidance to setup in SAP.
1. If the amt is less than Tolerance limit -- The user should select a seperate GL account manually instead of system adjusting the variance amt automatically to PPV account.
2. If the amt is greater than Tolerance limit --- We should be able to add a line item in PO and enter a GL account manual or add an item in IR.
3. If there is a high difference then it should return to the Vendor.
The quick guidance will be appreciated.
Thanks,
SP

hi,
u go to IMGpath - MM - inventory management and physical inventory - Goods receipts - Set Tolerance Limits, specify u copy to ur company code 0001 -B1, 0001 - B2, 0001 - VP,
IMGpath - MM - logistices invoice verfication - incoming invoice -Configure vendor specific tolerance enter new entries,
IMGpath - MM - logistices invoice verfication -invoice block - Set Tolerance Limits
copy u specific c.code 0001 - BD, 0001 - VP enter and save
after will go to check steps , get it output
regards
janu

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

Lower limit relative and upper limit dropdown in timesheet

Iu2019ve a question about the time sheet.
In the back end side we set the configuration to scroll down or up the time sheet. Setting Lower limit relative and upper limit relative with Value "2" .Now users can scroll down/up two weeks the timesheet from the key date
Iu2019ve checked In CAT2 tcode and it works fine. If you go back for more than 2 weeks the system returns an error.
But when i go to portal timehseet ,this error is not happening ,not retricting the user.
Allowing the user to move backwards.
How this can be restricted in portal time sheet in ess.
Thanks,
Nachy

It should be noted that this exit only prevents changes not display
There was moves to release functionality to limit scrolling on Webdynpro - however you would need to open a development request as per www.service.sap.com/rollin to find out what progress has been made
I also saw one customer who inserted a line of custom code to restrict scrolling access -4 weeks
and +6 weeks via sy-datum + 42 and sy-datum - 28 - however a complete solution would require an HR/CATS ABAP'er
Cheers
Stuart

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

Tolerance Upper & Lower limit in MIRO

Similar Messages

Maybe you are looking for