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

Similar Messages

  • Lower specific limit and upper limit

    Hi, we are entering the lower specific limit and upper limit as 100 and 200 in qp02 screen for certain MIC. The table name mentioned as QFLTP, which is a structure. I want to know in which table this values were saved?

    Dear Yadav
    Use PLMK or QAMV if you want to get the specification from the lot. In this the values will be E which can be interpreted
    for eg 5,5000000000000000E+01  means 55
    9,0000000000000002E-01 = .9
    Regards
    Gajesh

  • User Exit for validating overall limit field and expected limit field-ME2xN

    Dear Gurus,
    Can you please suggest me any user exit or BAdi to validate the overall limit field and expected limit field in transaction ME2xN.
    Or any other way to to achieve this functionality in ME2xN.
    Our Requirement is while raising a service PO in the Limits tab the 'Overall limit' should be same as 'Expected Value', at present the user can enter overall limit greater than 'Expected Value'.
    Regards,
    Priyank Joshi

    this will not work. you cannot add another structure (AUFK) on top of CEBAN. all characteristics have to be of one structure and since you want to release a PR it has to be CEBAN. before attempting to program something around that why do you not go to tx. OLME -> PR -> Release Strategy -> With Classfication -> Release Strategie and run it in a simulation mode. you will then see how it reacts.
    there's a white-paper on service.sap.com explaning in detail release-strategies. it's a good one and a good read too!

  • FO limit item and NB limit item

    Hi Gurus,
    Very vasic question but I am very a newbie in respect to MM.
    What would be the difference in the standard behaviour between a limit item in an NB PO and a limit item in a FO PO?
    I do not think we should create a GR/SES for the NB PO limit item. So what is the purpose of those two PO types?
    Many thanks in advance.

    Hi,
    Blanket Pos have the document type FO. Instead of a specific delivery date, you can specify a validity period for the order.
    Goods receipts or the entry and acceptance of services performed are not necessary in the case of a blanket PO and limit items. The invoices are posted directly with reference to the purchase order, provided that the specified value limit is not exceeded.
    The account assignment need only be specified at the time of invoice entry.
    For detailed information on the subject of value limits, refer to the documentation  MM External Services Management.
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/c3/72ca9255cd11d189660000e8323c4f/frameset.htm
    Regards,
    Edit

  • Ho to convert to lower case values and upper case

    hi
    pls let me know how to convert the varlues to lower case
    and how to conver values to uppoer case
    whichis funtion module to do so?
    regards
    Arora

    Hi,
    <b>TRANSLATE</b>
    Converts characters to strings.
    Syntax
    TRANSLATE <c>  TO UPPER|LOWER CASE
                  |USING <r>.
    The characters of the string <c> are converted into upper- or lowercase, or according to a substitution rule specified in <r>.

  • Upper Limit in % for Tolerance Key AN in OMR6 transaction

    Hi All,
    I have to maintain upper limit in %age terms for Tolerance Key AN (Amount for item without order reference) in OMR6 (Tolerance Group for Invoice Verification) transaction in ECC 6.0 system. But the system is not allowing the same. When I open OMR6, it allows me to put the lower and upper limit in absolute and %age terms. But while saving, it shows only the option of upper limit in absolute terms and not even in %age terms. Request if anybody can help me in telling how to maintain the tolerance key AN for %age terms.
    Anybody's help will be highly appreciated.
    Regards,
    Darshanjeet Singh
    Edited by: Dssachdeva on Dec 24, 2010 4:18 AM
    Request if anybody could help me with this issue.

    Hi Jaydip,
    Thanks for your response.
    I have made the necessary settings earlier also. But when maintaining the changes for %age upper limit, the system doesnot work as required. When I maintain the upper limit in absolute terms, the system works perfectly.
    Request you to please let me know if I can use any user exit to maintain the %age upper limit for tolerance verification.
    Regards,
    Darshanjeet Singh Sachdeva

  • 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 Specification Limit and Upper Specification Limit on Inspection Plan

    Hi Experts:
    I'm trying to input the lower and upper specification limit on inspection plan. I created my inspection characteristic but when I trying to digit the values, the systems erase that and give me the values from the inspection characteristics
    Any idea?

    Hi Deihus,
    1.     While creating MIC you create it with upper, lower and target limits.
    2.     The same MIC when you use in inspection plan, all the control indicators and lower, upper values get copied in to inspection plan from MIC.
    3.     In fact this is the reason you can use this characteristic for several material.
    Kindly excuse me as I could not interpret the term when I trying to digit the values . To digit value means what?
    Whether you want to put different values in inspection plan rather than getting copied from MIC? If yes, you can do so. Just overwrite the values on QP01/QP02 and save.
    Regards,
    Anand
    Edited by: Anand Rao on May 16, 2011 10:50 AM

  • Upper Limit In Range and Coerce

    I found a bug with the In Range and Coerce function, and I tried searching but I didn't see if anyone posted the issue before. Anyways, the Lower Limit is inclusive for the In Range indicator and the Upper Limit is not:
    Using U32, set the Upper limit to 5 and lower limit to 1. When x = 1, In Range is True, and when x = 5 In Range is False.
    Took a little bit of time to figure out why my code wasn't working... but just fyi if no one is aware.

    That's kind of a unique situation... I was thinking more likely to see if an array index is valid. In my mind inclusive is intuitive, but I guess I wouldn't have found out about the setting if it was intuitive.

  • In VB how do I pass my low and high limit results from a TestStand Step into the ResultList and how do I retrieve them from the same?

    I am retrieving high and low limits from step results in VB code that looks something like this:
    ' (This occurs while processing a UIMsg_Trace event)
    Set step = context.Sequence.GetStep(previousStepIndex, context.StepGroup)
    '(etc.)
    ' Get step limits for results
    Set oStepProperty = step.AsPropertyObject
    If oStepProperty.Exists("limits", 0&) Then
    dblLimitHigh = step.limits.high
    dblLimitLow = step.limits.low
    '(etc.)
    So far, so good. I can see these results in
    VB debug mode.
    Immediately after this is where I try to put the limits into the results list:
    'Add Limits to results
    call mCurrentExecution.AddExtraResult("Step.Limits.High", "UpperLimit")
    call mCurrentExecution.AddExtraResult("Step.Limits.Low", "LowerLimit")
    (No apparent errors here while executing)
    But in another section of code when I try to extract the limits, I get some of the results, but I do not get any limits results.
    That section of code occurs while processing a UIMsg_EndExecution event and looks something like this:
    (misc declarations)
    'Get the size of the ResultList array
    Call oResultList.GetDimensions("", 0, sDummy, sDummy, iElements, eType)
    'Step through the ResultList array
    For iItem = 0 To iElements - 1
    Dim oResult As PropertyObject
    Set oResult = oResultList.GetPropertyObject("[" & CStr(iItem) & "]", 0)
    sMsg = "StepName = " & oResult.GetValString("TS.StepName", 0) & _
    ", Status = " & oResult.GetValString("Status", 0)
    If oResult.Exists("limits", 0&) Then
    Debug.Print "HighLimit: " & CStr(oResult.GetValNumber("Step.Limits.High", 0))
    Debug.Print "LowLimit: " & CStr(oResult.GetValNumber("Step.Limits.Low", 0))
    End If
    '(handle the results)
    Next iItem
    I can get the step name, I can get the status, but I can't get the limits. The "if" statement above which checks for "limits" never becomes true, because, apparently the limit results never made it to the results array.
    So, my question again is how can I pass the low and high limit results to the results list, and how can I retrieve the same from the results list?
    Thanks,
    Griff

    Griff,
    Hmmmm...
    I use this feature all the time and it works for me. The only real
    difference between the code you posted and what I do is that I don't
    retrieve a property object for each TestStand object, instead I pass the
    entire sequence context (of the process model) then retrieve a property
    object for the entire sequence context and use the full TestStand object
    path to reference sub-properties. For example, to access a step's
    ResultList property called "foo" I would use the path:
    "Locals.ResultList[0].TS.SequenceCall.ResultList[].Foo"
    My guess is the problem has something to do with the object from which
    you're retrieving the property object and/or the path used to obtain
    sub-properties from the object. You should be able to break-point in the
    TestStand sequence editor immediately after the test step in question
    executes, then see the extra results in the step's ResultList using the
    context viewer.
    For example, see the attached sequence file. The first step adds the extra
    result "Step.Limits" as "Limits", the second step is a Numeric Limit (which
    will have the step property of "Limits") test and the third step pops up a
    dialog if the Limits property is found in the Numeric Limit test's
    ResultList. In the Sequence Editor, try executing with the first step
    enalbled then again with the first step skipped and breakpoint on the third
    step. Use the context viewer to observe where the Limits property is added.
    That might help you narrow in on how to specify the property path to
    retrieve the value.
    If in your code, you see the extra results in the context viewer, then the
    problem lies in how you're trying to retrieve the property. If the extra
    results aren't there, then something is wrong in how you're specifying them,
    most likely a problem with the AddExtraResult call itself.
    One other thing to check... its hard to tell from the code you posted... but
    make sure you're calling AddExtraResult on the correct execution object and
    that you're calling AddExtraResult ~before~ executing the step you want the
    result to show up for. Another programmer here made the mistake of assuming
    he could call AddExtraResult ~after~ the step executed and TestStand would
    "back fill" previously executed steps. Thats not the case. Also, another
    mistake he made was expecting the extra results to appear for steps that did
    not contain the original step properties. For example, a string comparison
    step doesn't have a "Step.Limits.High" property, so if this property is
    called out explicitly in AddExtraResult, then the extra result won't appear
    in the string comparison's ResultList entry. Thats why you should simply
    specify "Step.Limits" to AddExtraResul so the Limits container (whose
    contents vary depending on the step type) will get copied to the ResultList
    regardless of the step type.
    I call AddExtraResult at the beginning of my process model, not in a UI
    message handler, so there may be some gotcha from calling it that way. If
    all else fails, try adding the AddExtraResult near the beginning of your
    process model and see if the extra results appear in each step's ResultList.
    Good luck,
    Bob Rafuse
    Etec Inc.
    [Attachment DebugExtraResults.seq, see below]
    Attachments:
    DebugExtraResults.seq ‏20 KB

  • Issue with Safety Upper limit for CALDAY Field for Generic Data Source

    Hi,
    I have given Upper limit as 1 for Calday field of one of the Generic Data Sources.
    I have got a doubt here.If today's load got failed and I will rerun the load next day.So Will that new run captures all 2 days records.
    Can any one advise me on this.
    Regards,
    K.Krishna.

    Hi,
    A one-day upper safety interval determines that an extraction run today, only fetches records up to yesterday (if the pointer has the day before yesterday date, the extraction comprises from the day before yesterday to yesterday).  This is meant to avoid missing records that were about to be persisted in the database when the delta extraction is running but whose date was determined in memory before the delta started.
    If pointer has today date value and you want to load data from today and yesterday, you should use a lower safety interval.  Take into account that this could reload data previously extracted.  Therefore, only InfoProviders with overwritting features (DataStores or InfoObject master data) should be used as targets of this extractions.
    You can find further details at:
    http://help.sap.com/saphelp_nw04/helpdata/en/37/4f3ca8b672a34082ab3085d3c22145/content.htm
    I hope this helps you.
    Regards,
    Maximiliano

  • Value param too long. Upper limit is 32000

    Is there a character limit to An html portlet? Say some where around an Upper limit of 32000.

    Taken a sentence from Hans Forbrich :
    "Are you sure this is not related to a specific technology for which a separate forum exists? (Y/N)"
    And :
    Community Feedback and Suggestions
    Use this forum for feedback about OTN programs, Web site content, and systems - product-related questions cannot be answered here.
    Nicolas.

  • Waveform chart X-Axis reverses itself when upper limit is edited in Absolute Time - problem may be linked to Timestamp Control?

    I've seen this problem for some time now, and it still exists in the Silver toolset Waveform Chart in LV 2012.  If the chart is in strip mode, and you edit the upper limit value to a point in the future, the X-Axis will invert (higher values/ later time to the left), to the limit of the Chart History length.  This happens whether the chart is active (logging data on a compiled executable) or even when in design mode, though it's more consistent when there's data in the chart.  It's not history length related as far as I can tell, as I set the length to 7 days of sampling @ 1-second intervals (605K), and it happens when I try to set the end time to an hour in the future with only a few minutes of data collected - suddenly the right Absolute Time becomes the time my last sample point was collected, while the left Absolute Time becomes nearly 7 days in the future (so neither end point is what I was setting it to).
    It's nice that the chart gives the option of editing the limits, but as such, it's important that they work as you would expect them to.
    Also - until this is addressed, is there a way to lock it against editing?  Until a fix is made, my workaround is to put a transparent button over the range start & end points, and a transparent flat rectangle above all other mid-range points, and pop-up a data entry form with a Timestamp control to allow editing.  Unfortunately, this doesn't work as I would expect, as typing "11 AM" in the Timestamp control over a prior value of say "10:05:34.232 AM" ends up becoming "11:05:34.232 AM" instead.  ???  Another error - or is this by design?  If it's by design, is there an option to make it behave as I would prefer (11 AM = 11:00:00.000 AM), as Excel behaves with timestamps?  I can't help but suspect this may be linked to the chart axis issue.
    Also - I just built a simplified chart modeled somewhat on my current project, and could not get this to recur.  BUT... had the strangest thing happen:  My sample data was generated using the Trig functions for Sine and Cosine, and at one point my waveforms distorted on the display, so I'm attaching that here plus the simplified chart project.
    Last - my system is LV 2012 on Win7 Pro-x64.
    Thanks!
    Erik
    Attachments:
    Chart data distorted.png ‏45 KB
    Waveform Chart Flaw.zip ‏17 KB

    I am not so sure that this is a bug, and I have not been able to reproduce this behavior that you are describing. 
    But you can lock it from editing by right-clicking on the graph and go to Properties>>Appearance>>Enabled State --> Disabled
    Also, word of advice for the future: You will get more replies from the community with shorter posts and keeping it to one question per post. Summarize what the issue is, and put the detailed documentation and instructions to reproduce in the actual VI. 
    Huntington W
    National Instruments
    Applications Engineer
    ***Don't forget to give Kudos and Accepted as Solution where it is deserved***

  • Add to only upper limit

    -Hello Everyone
    I'm new with TS, and running TS2.0
    Q1:
    I want a multiple numeric step measurement to only compare to a upper limit value. Can I do it?
    Apparently TS allows me to compare to a low limit, and not necessary have an upper limit.
    However, I can't do the opposite... comparing just the upper limit and not have a low limit.
    I guess an easy solution would just to add inf or -inf.
    Q2:
    1)Some steps I have test with different limits.
    2)Some steps I have test with same limits.
    3)Some steps I have test with different/same limits, but different units.
    for 1) should I use multiple numeric limit test or use a loop & change step limits.
    for 2) use a numeric limit test, or use a loop to do the comparisons.
    for 3) again use solution in 1).
    Just curious, in how the most efficient way would be.
    thanx

    Hi,
    For Q1, yes you can do upper limits (GT) testing, unfortunately TestStand stores the limit value in the lower limit property whether its a lower limit test or an upper limit test. There are tricks you can do, which have been address in this forum and maybe a knowledge base note or example on the NI website, so as to store the upper limit value in the correct place.
    For Q2, there are examples showing how to use different limits based on expression see
    here
    and there is an example in the TestStand examples under limit loader.
    Whether to use Multiple Limits steps or Numeric Limit Test steps really depends on what sort of tests you perform and whether the test returns more than one result. But using MultipleLimitsTest step with the limit file can get a bit confusing to look at.
    Hope this is of help.
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • WARNING:Could not lower the asynch I/O limit to 224 for SQL direct I/O. It is set to -1

    Hi,
    We have recently upgraded single instance database to 10.2.0.5 patch set 4 on windows server 2003 64 bit
    After upgrading we are facing  issue of number of warnings in trace files (bdump)
    WARNING:Could not lower the asynch I/O limit to 224 for SQL direct I/O. It is set to -1
    I know this is bug 9772888 and oracle suggest to upgrade to 11.2.x but we can't upgrade it now on early basis.
    According to oracle it is useless warning and can be ignored but these traces are consuming more than 500MB space per day and we are unable to delete trace files as oracle countinously using those file for writting
    it is production database kindly suggest solution other than upgrade.
    trace files sid_sxxx_XXX.trc
    if we set max_dump_file_size to XXXM or G will it resolve our problem?
    or is there any way to flush warnings to new file and delete old one.
    Please suggest
    Thanks
    shah

    duplicate thread.
    I suggest you don't multipost.
    I also suggest you upgrade from Windows 2003 (10 years old and probably desupported)
    and 10gR2 (desupported for a few years)
    Sybrand Bakker
    Senior Oracle DBA

Maybe you are looking for