Fixed value/lower limit ' ' reoccurs

Hi,
I am getting the following error when i am activate my domain.
fixed value/lower limit ' ' reoccurs
How do i proceed?
Regards
Shilpi

Hi Shlipi,
Check your inserted values/range in your domain.
Probably you have some lower value that not valid (or empty)
Good Luck
Eli Steklov
Please Reward Points if it Helped

Similar Messages

The validity interval has the initial value as lower limit

Hi Friends,
When i was executing a query on Multiprovider,
got an error like
"The validity interval has the initial value as lower limit"
Actually The multiprovder has been built on two infocubes 0CFM_C10 & 0CFM_C11, in those 0CFM_C10 contains the non-cumulative values.
Even i've checked the query also in query designere it is saying like the query is correct, in that query we are using Key Date...
please help me onthis, awaiting for your answers
thanks in advance

Hi you can try using inial at the update rules

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

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

Lower limit can only be changed during initial entry, Message no. NR651

Hi Experts,
As per the number ranges limit values defined in the system for the planned orders, there is a need to increase the number ranges.
System is not allowing us to change the limit values of the Planned orders in MD91 and showing the Message no. NR651.
We have also searched for the available threads in SCN and other sites, but didn't find the root cuase link for this error.
System message:
Lower limit can only be changed during initial entry
Message no. NR651
Diagnosis
You have tried to change the lower limit of an interval which has a non-initial number status.
System Response
The change was not executed.
Please guide us how can we increase the number ranges for planned orders.
Thanks in advance.

Hi,
You can create a new number range or change in transaction OMi2 or in MD91.
Assign the 02 by clicking number range in OMi2
or in transaction OPPQ click on number range & select the 02.
Do the changes as described and analyse the results. Ensure that while testing no body is creating the planned orders.
Regards,
Narresh

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.

Need information on Error ORA-30052:invalid lower limit snapshot expression

Hello all,
I have been running some flashback version queries on Oracle DB like:
SELECT versions_xid,VERSIONS_OPERATION, LABEL_NAME FROM <table_name> VERSIONS BETWEEN SCN <scn1> AND <scn2>;
It was working fine, but after some interval, I got the following error on executing the command:
ORA-30052: invalid lower limit snapshot expression
30052. 00000 - "invalid lower limit snapshot expression"
*Cause: The lower limit snapshot expression was below the UNDO_RETENTION
limit.
*Action: Specify a valid lower limit snapshot expression.
On Google, it could find this useful information only http://docs.oracle.com/cd/B28359_01/server.111/b28320/initparams251.htm but this didn't made me understand the problem i have been facing and the cause.
On running the command "show parameter retention", I got the following result:
NAME TYPE VALUE
db_flashback_retention_target integer 1440
undo_retention integer 900
Can anyone please help us out here what could be the issue here and what will be the solution?
Thanks
Ankush Gupta

Hi,
The flashback always works along with Undo segment....
Issue:
By default the undo retention is 900 seconds.One restriction with using specific timestamps or SCNs is that they must be within the boundaries of the undo_retention parameter.
The db_flashback_retention_target integer 1440 min (24 hrs) parameter is for flashback logs and it has nothing to do with table flashback.
The flashback only uses the data in undo and which is in turn handled by undo retention i.e, 900 sec or 15 min.
Solution:
Try increasing the undo retention value and run the same. Hope, it'll run without any error.
thanks,
-Seshi

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

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

Safty lower limit

hi experts
what is safty lower limit and safty upper limit in setting up delta in generic extraction
puli

Hi Sridhar,
This is from 'how to generic delta' doc
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Example for Determining Selection Intervals with a Generic Delta:
1. For every delta extraction, there is a selection criteria generated: ?last extraction status
(RSA7) < x <= Today.
2. Offsets for upper and lower delimiter are subtracted from the respective sides
3. Example 1 shows the normal behavior (both offsets = 0), example 2 shows both safety
intervals (offset for lower delimiter = 2, offset for upper delimiter = 1)
4. Offset for lower delimiter can only be defined for delta method new status for changed
records
Example 1 (both offsets = 0):
Example 2 (offset = 2 resp. offset = 1):
Tips:
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
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.
*pls assign points,if info is useful**
Regards
CSM reddy

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

Find characteristic with fixed value at planning levels

Hi Experts,
I need to know which are the planning levels that contains a characteristics with a specific fixed value (ex: 0UVERSION = 220 )
Does anybody know how can I do it?
Thanks in advance

Hi,
Please create a query (tcode SQVI) on tables UPC_PLEVEL and UPC_OPTIOS. The join will be on field GUID. Select all the fields as available for display and selection. UPC_OPTIOS has the selection values maintained for the level. Please put in
UPC_OPTIOS-FIELDNAME = 0UVERSION
UPC_OPTIOS-SIGN = I
UPC_OPTIOS-LOW = 220
this will give you all the levels that have the said value
hope this was helpful
thanks

The fixed value date is empty and not displayed in the VA05 report

Hi SD Gurus,
With in the Sales Order in the line item level in the billing tab we have the fixed value date (VBKD - VALDT) were entered.
But when we try to execute the report VA05 were the fixed value date column shows empty (i.e without the date it shows the blank). Can you any one help me with regard.
We would like to fix this problem.
Thanks in advance for providing solution to this query.
Thanks and Regards,
SAP-SD group

Hi janarthanam,
Ok.
Goto t-code SQVI,SAP Quickviewer.
Give a name to your query and enter description ,etc.
Next enter the table from which you want to fetch data,ie,VBKD .
Select "Layout mode" for displaying data on the SAP screen or "Basis mode " if you want to extract the data to a word doc,excelsheet or a flat file.
Next you can select the fields you want to display into your report,their position and ascending/descending order,Here make sure u select
the field u need to display ie. the fixed value date ( VALDT) .
also select the fields u wish to have in the selection criteria.
Enter these required information and u would get a report on the SAP screen or in your desired format.
Hope it will suffice you.
For any queries ,your are welcomed.
Thanks,
Umesh.

How to associate a fixed $ value to a date cell?

I'm trying to keep track of payments made, according to date.
I have one column where I enter dates.
Can I associate these date cells to a fixed $ value, so that each time I enter a new date the SUM cell will automatically update?
I hope so...
Thanks!

HI cp,
By "associate these cells to a fixed $ value," I assume you mean that fixed value will be added to the sum as each date in sentered.
Here are two examples, one showing the fixed amount in the adjacent column when the date (or anything) is entered in column A, the other showing only the total.
Both use a second table to hold the fixed value, making it easy to edit, if necessary.
Formulas:
(Method 1)
B2, and filled down to B10: =IF(LEN(A)>0,Fixed value :: A$2,"")
LEN(A) returns the length (in character) of the entry in the cell in this row of column A. If anything is entered, the IF condition is TRUE, and IF returns the value in A2 of the smaller table. If nothing has been entered, the condition is FALSE, and IF returns a null string to the cell.
B11: =SUM(B)
Row 11 is a Footer row, and is not included in the cells to be summed.
(Method 2)
D11: =Fixed value :: A2*COUNTA($A)
COUNTA counts the number of entries in column A of the Main table, then multiplies the fixed value in the small table by the result of the count and returns the result.
This formula may be placed in any cell.
(Both methods)
The cell reference to Fixed Value::A2 (or Fixed Value::A$2) may be replaced with the actual value, and the second table eliminated, if desired.
Regards,
Barry

How can batch field in Purchase Order(PO) be a fixed value????

Hi Experts,
In SAP, when create a purchase order, there is a field "Batch" for every item,
which means "Assigns a material that is manufactured in batches or production lots to a specific
batch ".
For some special reasons, we want for some certain materials,when create purchase orders every
time,the "Batch" field will be a fixed values.
For example,for material "AB1" ,"CD2",when create purchase orders every time,the "Batch" field will
be "2345" automatically,do not need input manually.But for all the other materials, the "Batch" field would be null ,no value.
How can I do this? How can assign fixed batch number values to some certain materials in Purchase
Order?
If there needs some ABAP development,which user exit do I need??
Thanks for any reply!

Hi there,
You may need to establish, whether you wish to use batch managent or split valuation.
Spilt valuation does allow you to default values into purchasing documents via information records, but I guess it depends on what else you want to do with this tracking
Split valuation can be controlled independently at the material and plant level
Regards
Steve

Fixed value/lower limit ' ' reoccurs

Similar Messages

Maybe you are looking for