Requested start time during job scheduling population in local time.

Hello Experts,
Could you please help on the issue.
Requested start time during job scheduling populated with local time even though we have assigned the GMT time zone.
Could you please help , how to change the settings of request start time calender icon to populate the GMT time.
thanks,
Suresh.

Hello Gerben,
Thanks for the reply, even though the default time zone set as GMT in user settings, the requested start time calender pop up the local time instead of GMT time.
Previously requested start time poped up  the GMT time, we have observed this change once we have ran the redwood script for time window elements change and imported some of the job definitions, applications & time windows from other system.
Below is the script we have ran thought shell script
Script Fuctionality
1. Take the mentioned time window
2. iteratate thought the time window elements and add 1 hour to the "time to day from" & "time to day to" parameters.
3. set the changed parametes to time window and persist the changes.
// Variable Declarations
String timewindow = null;
String query = null;
TimeWindow tw = null;
TimeWindowElement twe = null;
long otdvalue = 3600000;
long l1 = 0;
long l2 = 0;
long threshold = 0 ;
long expvalue = 82800000;
long expvalue1 = 85500000;
long indto1 = 0;
long indfrom1 = 300999;
long indto2 = 2700000;
long indfrom2 =  3000999;
Job job = null;
//Declare all the time windows in array
String[] timewindows = {"XX_TIMEWINDOW_01_GMT"};
          for( int i = 0 ; i < timewindows.length; i++)
          timewindow =  timewindows<i>;
          jcsOut.println("TimeWindow"i":"+timewindows<i>);
          tw = jcsSession.getTimeWindowByName(timewindow);
          for (Iterator it1 = tw.getTimeWindowElements(); it1.hasNext();)
               twe = (TimeWindowElement) it1.next();
               Long otd = new Long(otdvalue);
               jcsOut.println("************************");
               jcsOut.println(twe.getTimeOfDayFrom());
               jcsOut.println(twe.getTimeOfDayTo());
               jcsOut.println("************************");
               Long todf = (Long) twe.getTimeOfDayFrom();
               Long todt = (Long) twe.getTimeOfDayTo();
                                  threshold = todf.longValue();
                        // if timeday from equal to 23 GMT assign the 0 GMT
                                  if(threshold == expvalue )
                jcsOut.println("timewindow with 23 GMT");
               l1 = indto1;
               l2 = indfrom1;
                        //if timedayfrom equal to 23:45 GMT assign 0:45 GMT
               else if(threshold == expvalue1)
               jcsOut.println("timewindow with 23:45 GMT");
               l1 = indto2;
               l2 = indfrom2;
                        // Add 1 hour for current time of day from 
               else
               l1 = todf.longValue() + otdvalue;
               l2 = todt.longValue() +  otdvalue;
               Long ll1 = new Long(l1);
               Long ll2 = new Long(l2);
               twe.setTimeOfDayFrom(ll1);
               twe.setTimeOfDayTo(ll2);
               jcsOut.println("After Change:"+ twe.getTimeOfDayFrom());
               jcsSession.persist();
Once after the script competetion the time window time zone remains in GMT.
Could you please check script once and  help us  the time zone change caused  the by script or not?
Thanks,
Suresh

Similar Messages

  • Job Scheduling-restriction based on time

    Hi Everybody,
    I want to schedule a job so that it should not run between 5pm to 6pm everyday and rest of time it should run.
    I am not getting any restriction option to satisfy this condition.
    Anybody having any idea ??
    Regards.

    Hi again,
    In that case, we can create a Wrapper Program.
    ie.
    1. Create a Z program. (It will be a very small program)
    2. Inside this Z Program, call/submit the standard program
    3. Before submitting, write the logic of 5-6.
    Now for background scheduling , use the Z program instead of the std. one.
    Hope this helps.
    regards,
    amit m.
    Edited by: Amit Mittal on Jan 7, 2010 6:44 PM

  • Job Scheduling --- Both Event and Time driven

    Hi,
    We have a Job X scheduled to run on 23:30 hrs everyday. The run of the Job varies from 15 min to 45 min. Now as per Business need we are to schedule a Job Y that runs immediately after finish of Job X. We have another criteria, which is the Job Y should run the following day and not the present day.
    So, if Job X finishes on current day then Job Y too runs on the same date.
    Is there a way in which, we could combine both the Time driven and Even Driven option together and schedule the Job Y.
    Job Y checks that Job X got finished and if date is current date it waits and runs the following day at 00:00 hrs.
    Job Y checks that Job X got finished and if date is following day it runs immediately.
    Please suggest.
    Regards,
    Subhram

    [How to run chained jobs|http://wiki.sdn.sap.com/wiki/display/Basis/Howtorunconsequentorchainedbackground+jobs]
    Hope it helps
    Regards,
    Nick Loy

  • Object locked by another user-during job scheduling

    Hi experts,
    We are facing a issue where in which we are scheduling a program in one system and inside which  RFC is calling some other system and inside the RFC we are calling a BDC to update one field (this is only becoz we are in a situation to track change history ) else we might have used update table using enqueue  and dequeue concepts.
    Now say for example we are using change vendor (XK02) in BDC. now while some user is opening XK02 and editing the vendor , scheduling the program cause the  job to be abbended , this is the issue we are facing currently.
    so please provide some jist on this or suggest some best practice for this.
    Thanks in advance
    S.Janagar

    Hi Janagar,
    According to my opinion, following would be a good approach and will take into account the following problems;
    a) No need to directly update standard table - it is not recommended
    b) Even if other user is using that t-code for that vendor, we can still update it later
    To use this, we can use the RFC function module in BACKGROUND TASK. (please see F1 help on this).
    By calling the same RFC with the suffix in BACKGROUND TASK (and also using DESTINATION ofcourse),
    the system will ensure that
    a) at the time of calling the rfc in background, the other system's vendor code is locked/enqued,
       then the system will automatically, AFTER SOME TIME, try again and run the RFC. So probably after some time, the vendor should get un-locked and the RFC bdc will do the update. The system will keep on trying in frequent intervals for a prefixed number of times. (please see F1 help on BACKGROUND TASK)
    hope this helps.
    regards,
    amit m.

  • Spool request starts later than job

    Hello ,
    a job started at 21:00. The first statement of the ABAP was a write-Statement (Write sy-uzeit)
    The corresponding spool was generated at 23:00. The job stopped at 2:00
    Can someone explain this? I have no idea
    Thanks and best regards
    Simone

    Have you set the job class to "A" ? i.e. high priority?
    Regards,
    Sumit

  • Time Management - Work Schedule /Absence Quota / Part-time quota generation

    Hi Experts,
    Need your help!
    We have a requirement where we need to create distinct work schedules for each irregular / part-time work pattern and the number of work patterns we have identified is more than 1000.  We are using report RPTQTA00 to generate quota. We have used work contract, employee sub-group & employee payscale group in the QUOMO feature to get the base entitlement picked up. We have defined base entitlement for the full time workschedules with 37.0 / 38.5 hours and there is a reduction rule which reduce the absence entitlement for part time employees as per the employement percentage in IT0007. Now we have a scenario where we have created a work schedule with different no of hours for each day of week (M-4, T-6, W-4, TH-6, F-4, S-OFF, SU - OFF); this work schedule is treated as full time work pattern by the system and quota is generated as full time work schedule refering to the QUOMO settings, but as per my client employees with this work schedule have reduced hours of working hours (24 hours, not 37.0 or 38.5 hours)and hence it should be treated as part-time employees, and the quota generated should be proportionately reduced. I have very limited scope to create any ESG or PSG as we do not have any distinct emplyee sub-groups maintained for full-time and part-time employees and the project has already gone-live with payroll/time. It is worth mentioning over here that we are recording absence through ESS and it takes into account the daily planned working time maintained in IT0007, so we are very particular to keep it as accurate as possible.
    I would really appreciate if somebody can please suggest any possible solution for the above issue, or guide me on what would be the best way to tackle it. I can give more details in case anybody need to have a better understanding of the issue to suggest a solution.
    Thanks in advance
    Sujit

    Hi Kathy,
    Yes, i have found the solution to it. I do not know whether it will fit into your situation or not, but i got two solutions for my issue mentioned above, please check it may help:
    1) To use capacity utilization field in IT0008 to get the FTE hours and defining the reduction rule of absence quota based on the capacity utilazation percentage.
    2) There are three user exits available in the standard report RPTQTA00, i have used one of them to write my own rules for the calculations (deduction rule)
    Do let me know if i can help you in any respect. Thanks.
    Regards,
    Sujit

  • Unloading time during scheduling-GATP

    Hi Expert,
    I am facing an issue during GATP. During scheduling the "UNLD" ie Unloading time is not considering. When I checked with the SAP IMG help. It is maintained as "not support ".So how can I include the unloading time during the scheduling ?
    Also is it possible to do any customization for the same ?
    Regards,
    Reji

    Thanks DB49,
    Got the point but allow me to crib a bit.
    If I have a warehouse in middle of Montana and the nearest sea port where I "deliver" the goods (from another country) is Philadelphia then obviously the duration between Philadelphia and Montana is un-ignorable and unpardonable for service level measurements. Somewhere I need to account for this time. Sometimes my obligations end on delivery at port and sometimes I am obliged to deliver at customer door step and it could be the same customer at differnet times in a year. No I am not complicating for the sake of it. This is how the business is.
    So any "requested delivery date" on door delivery terms - delivered duty paid at warehouse door- must consider this part of transit + port clearance  + other waiting times. I thought UNLD was the best condition type for the same. Additing this portion also to TRAN now means I need to build additional access in TRAN and complicate my data maintenance.
    Why according to you SAP provided UNLD as a condition type. I would have appreciated if this was clearly separate duration to represent something unque. On the same reasoning other durations are negligible as compared to TRAN and UNLD or rather TRAN+UNLD and no one cares if pick date and load date are a day or 2 apart.
    Guru.

  • How to lock targetserver execution in job scheduling

    Hi,
    I've a SAP System with a central instance and two application servers.
    I would set authorizations so that users when they schedule their jobs (example in SM37), the field target server is locked and set to a particular application server.
    Any idea ?
    Thanks
      Maurizio Manera

    Hi,
    Giving an overview of the tables involved in batch processing. The jobs details are stored in the system on the following tables.
    TBTCO      - the overall state and information of a background job
    TBTCS      - the view of the jobs that the time based job scheduler has
    TBTCP      - the steps a background job consists of.
    BTCEVTJOB  - the view of the jobs that the event based scheduler has
    BTCCTL     - Controls what BTC schedules runs in system
    Fields include:
    ===============
    JOBNAME, JOBCOUNT: unique identifiers(i.e. key fields)
    SDLDATE, SDLTIME: scheduled date & time of when job is created
    SDLSTRTDT, SDLSTRTIM: scheduled start date & time
    These are the two fields EXECSERVER & REAXSERVER you should be concerned
    EXECSERVER: executing server; filled if you specify a target server
    REAXSERVER: filled at run-time; gets same server as EXECSERVER if target.
    Regards,
    Snow

  • Help need reg requested start

    Hi all,
    i have a scenario like when a event raised then based on date entered by user  after  that date only i need to start processing that task  and it can be  1 month ,so requested start can be set like 1 month etc,.
    my doubt is can i go for workflow using  requested start  or it will be performance issue for time gap in months?
    Please suggest,
    Regards,
    Rajkumar

    Yes, you can use the date entered by the user as the requested start date. As far as performance goes, it will not really effect performance since no task or background job is being executed until after the deadline is reached. However, I would suggest having a maximum number of days the user can enter. You don't want a WF sitting in a waiting status for too long. My personal rule of thumb is that a WF should be started and completed within 30 days. Any (single) business process that takes longer than that to complete perhaps need to be redesigned.
    Derrick
    Banks & Company, LLC

  • Conversion between local time and UTC: Anomaly at Daylight saving time edge

    Hi all,
    I want to convert back and forth between local time including all peculiarities like DST etc. This is the core of my code:
        Date d=new Date(toEpoch());
        Calendar cal=Calendar.getInstance(tz);
        cal.setTime(d);
        int offs=(cal.get( Calendar.ZONE_OFFSET )+cal.get( Calendar.DST_OFFSET ));
        System.out.println("zone_offset: "+cal.get( Calendar.ZONE_OFFSET )+", dst_offset: "+cal.get( Calendar.DST_OFFSET )+", offset: "+offs);
        Calendar cal2=Calendar.getInstance(TimeZone.getTimeZone("Etc/UTC"));
        System.out.println(cal2.getTimeZone().getID());
        cal2.setTime(d);
        cal2.add(Calendar.MILLISECOND,-offs);
        d=cal2.getTime();Looks (and, actually, is) rather complicated. I take two different calendar objects to be absolutely sure that no accidental DST conversion hits me on the UTC side.
    The general case works as expected:
    Date (fourteen digits, 'x'=Exit): 20050909190000
    Entered date: Fr, 9.9.2005, 19:00
    zone_offset: 3600000, dst_offset: 3600000, offset: 7200000
    Etc/UTC
    Date in UTC:  Fr, 9.9.2005, 17:00I live in timezone Europe/Berlin, so during DST we have GMT+2. Let's see what's happening on christmas (non-DST):
    Date (fourteen digits, 'x'=Exit): 20051224180000
    Entered date: Sa, 24.12.2005, 18:00
    zone_offset: 3600000, dst_offset: 0, offset: 3600000
    Etc/UTC
    Date in UTC:  Sa, 24.12.2005, 17:00As expected!
    Now, we enter the dark zone of DST: Each year DST is turned on and off and it seems as if this leads to problems in both cases. Let's start with the next event of this case: At Oct., 30th, 2005, DST is turned off between 2:00 and 3:00 at night. So, we have once 2:30 with DST and (one hour later) 2:30 again without DST. Java, however, garbles things completely (I'm leaving the unneeded lines of my debug output out now):
    Entered date: So, 30.10.2005, 01:59
    zone_offset: 3600000, dst_offset: 3600000, offset: 7200000
    Date in UTC:  Sa, 29.10.2005, 23:59
    Entered date: So, 30.10.2005, 02:00
    zone_offset: 3600000, dst_offset: 0, offset: 3600000
    Date in UTC:  So, 30.10.2005, 02:00
    Entered date: So, 30.10.2005, 02:30
    zone_offset: 3600000, dst_offset: 0, offset: 3600000
    Date in UTC:  So, 30.10.2005, 02:30
    Entered date: So, 30.10.2005, 02:59
    zone_offset: 3600000, dst_offset: 0, offset: 3600000
    Date in UTC:  So, 30.10.2005, 02:59
    Entered date: So, 30.10.2005, 03:00
    zone_offset: 3600000, dst_offset: 0, offset: 3600000
    Date in UTC:  So, 30.10.2005, 02:00So, directly before the DST change, offset is computed correctly. From 3:00 onward, also. But in between, Calendar does neither take an offset of two hours (what would be somehow correct) nor one hour (also somehow correct). Even though it predicts to take the one-hour zone offset into consideration, "GMT" time is actually the same as local time.
    Things become even wireder at the other edge of the DST time range: This year, DST began on March, 27th, 2005: Let's see what is happening:
    Entered date: So, 27.3.2005, 01:59
    zone_offset: 3600000, dst_offset: 0, offset: 3600000
    Date in UTC:  So, 27.3.2005, 00:59
    Entered date: So, 27.3.2005, 02:00
    zone_offset: 3600000, dst_offset: 3600000, offset: 7200000
    Date in UTC:  So, 27.3.2005, 00:00
    Entered date: So, 27.3.2005, 02:30
    zone_offset: 3600000, dst_offset: 3600000, offset: 7200000
    Date in UTC:  So, 27.3.2005, 00:30
    Entered date: So, 27.3.2005, 02:59
    zone_offset: 3600000, dst_offset: 3600000, offset: 7200000
    Date in UTC:  So, 27.3.2005, 00:59
    Entered date: So, 27.3.2005, 03:00
    zone_offset: 3600000, dst_offset: 3600000, offset: 7200000
    Date in UTC:  So, 27.3.2005, 00:00
    Entered date: So, 27.3.2005, 04:59
    zone_offset: 3600000, dst_offset: 3600000, offset: 7200000
    Date in UTC:  So, 27.3.2005, 01:59
    Entered date: So, 27.3.2005, 05:00
    zone_offset: 3600000, dst_offset: 3600000, offset: 7200000
    Date in UTC:  So, 27.3.2005, 03:00While at 1:59, everything is ok, 2:00 is handled as within DST. That's ok, as the hour between 2:00 and 3:00 did not exist in that night in our local time zone, but at 3:00 the system totally screws up things as it suddenly subtracts three hours (while pretending to use two hours). This goes on until 5:00 in the morning when time is shown correctly again.
    Can anyone help me? What am I doing wrong? How do I actually convert correctly between a DST-aware local time zone and GMT/UTC?
    Best regards,
    Dirk

    Well, I would not say I did "just about everything" wrong. Actually, Calendar is not GMT-only as it has time zone information and converts its internal time according to that information if I use the getTime() function (what I do).
    In my applications, I handle dates in my own data structures. My EDate object (which is part of the QJCC library hosted on SourceForge) stores years, months, days, minutes, hours, and seconds seperately. Using this class, I managed to get an actually working time zone conversion this way:
      public void toUTC(TimeZone tz) {
        Calendar cal=Calendar.getInstance(tz);
        cal.clear();
        cal.set(year,month-1,day,hour,minute,second);
        int offs=(cal.get( Calendar.ZONE_OFFSET )+cal.get( Calendar.DST_OFFSET ));
        //System.out.println("zone offset: "+cal.get( Calendar.ZONE_OFFSET )+", DST offset: "+cal.get( Calendar.DST_OFFSET ));
        second-=(offs/1000);
        normalize();
    normalize() does something similar to the lenient stuff in Calendar.
    I will now write the method for the other direction. The most interesting item will be the answer to the question:
    "Tell me the correct DST_OFFSET in TimeZone X when I have the actual point of time given in UTC."
    Perhaps someone can give me a hint?!?

  • Enabling the Local time stamp on Sales Order, Delivery, invoice & PO

    Hi SAP experts,
    I need the valuable inputs for the following requirement- the user ( India based)want to see the local time stamp on transactions VA01(Sales Order), VL01N(Delivery) and VF01(Sales Invoice), ME21N(PO). The system is currently fetching the Malaysian time on these.(invoice and delivery).
    A small info about the issue: As India is 2.5 hrs behind Malaysian time so at 9:30 pm India time system date changes to the next day for us and any invoice done after 9:30 pm is showing next day's date. Also the time reflected on the Invoice is Malysian time which should be actually the local time. As per user, it is a non compliance on regulatory front.
    To simulate the issue we have created an invoice on 3rd Jan at 4:01PM Indian Std time but the time reflected on the invoice is 18:31 which is MY time.
    Also provide help in where to see the time settings for these sales documents?
    I am new to the SAP, All the valuable suggestions are highly appreciated.

    Dear All,
    With the help of security team, we tried to change the Personal time Zone ( of the user) maintained in SU01-Defaults tab to INDIA , but did not get the expected results. THE SYSTEM TIME ZONE JUST MAINTAINED BELOW PERSONAL FIELD IS SHOWING UTC+8.
    After the change , the invoice created at India time is reflecting +2.5 hrs ahead time.
    Pls Suggest , how to acheive this. Any example ecenario can help a lot.
    Thanks a lot in advance for the support.

  • Local Time Feature

    Before this week's update, the local time for my contact would show up next to their name when chatting with them. It was really nice to know whether to say "Good morning" or "Good afternoon".
    But now it's gone. Can this be re-enabled?
    Solved!
    Go to Solution.

    Just been forced to upgrade from version 6.2, which I was very happy with, and this is another annoying issue with the latest software.
    If you are talking to multiple people in different time zones at the same time, it is essential that their local time is shown at the top of the chat screen.
    I understand some users choose to hide that info, which is fine, but for users that don't hide it, please display it all the time (like you used to do in 6.2).

  • Problem in Workflow during activity step with "Requested start" time.

    Hi,
    I am working on SAP workflow.
    In my workflow there is a activity step (wait step) where the workflow should wait before going to step after that wait step. To achieve this, I have used requested start as +10 min with WIS workitem creation. After 10 min, the workflow should proceed to further step but my workflow does not go further.
    It was working good I tested couple of days back but now it doesn't. Can someone please help ?
    Thanks.
    Regards,
    Rajesh.

    Please check the settings in SWU3. Most probably  the settings is not correct. You will get a lot of discussion from this forum if you search with SWU3.
    Thanks
    Arghadip

  • Difference between dispatch time in po and scheduled time in job

    Hi all ,
    can any one please explain me
    what is the exact difference between dispatch time maintained in po and time/date set for job schedule
    here my question is ,i maintained dispatch time as send job with periodically in PO and i had maintained date/time in job process steps with some period.
    when po message is triggered ,which time will be consider system.time specified in job schedule or dispatch time in Po.
    which one consider first?
    Thanks
    konidala

    Dispatch time that is set up as part of the message output condition records, drives at which event does the output be transmitted. Conversely, the date/time during the batch job set up is the time when the batch job must execute the program.
    For example, if you had selected the dispatch time for output NEU in the PO to be '1' and you had set up ME9F program as a background job running daily once at 1PM, when the PO is created and saved at 10AM, the output type NEU will be triggered and will be held in queue. At 1PM when ME9F program is run as part of the background job, it'll pick up this output type for execution and transmission.

  • DI Job Schedules not starting (running) scheduled using DI Web Admin

    I have DI Jobs that have job schedules that I created through DI Web Admin and have active schedules. I have some jobs that start to run at their schedule time while others have active schedules but do not start at their schedule time.
    Edited by: Juan Jacome on Oct 26, 2010 8:56 PM

    Im not sure but a lot of times corruption happens and hence its better you redo your scheduling.
    Regards,
    Den

Maybe you are looking for