Background jobs are scheduled in future date

Hi
A system which is used by a customer test system was installed and scheduled the jobs in 2010( in future date).
Now we have changed the date to current date. But still all the background jobs are in future date.
There are around 500 jobs are scheduled. And it not possible to reschedule one by one.
Is there any way workaround to change it back to current date format.
Best Regards,
Jai

Dear Jai,
The jobs scheduler should have this dates changed to current.  If its a third party system which are running these batches, then be careful to convey the same message to the 3rd party.
If its in SAP, then the schedule change date should execute your jobs. At the same time, ensure that the transports between the test systems match to the destination.
Do let me know for any clarification.
Thanks
Madhu

Similar Messages

  • GN_GENERATE_CHECK and SM_SERVICE_CONTENT_UPDATE background jobs are failing

    We recently upgraded our Solution Manager to 7 ehp1.  A couple of the background jobs are not able to complete.
    Both jobs have the following entry in the job logs
    Step 001 started (program RAGS_DSWP_SERV_CONTENT_UPDATE, variant , user ID SOLMAN_ADMIN
    No authorization
    I'm not sure where to look for the authorization issue.  Any advice would be appreciated.
    Thanks
    Laurie McGinley

    we are on SM 7.01 (EHP1)  - and we have the same problem:
    Jobs GN_GENERATE_CHECK and GN_WORKLIST_GENERATE
    both jobs end abnormal with joblog:
    Object requested is currently locked by user SOLMAN_BTC
    Job cancelled after system exception ERROR_MESSAGE
    but the job-start is not corresponding to the entries in table SMCONFIGJOBS
    both jobs are startet at 00:01:44 (both !!!) 
    in table SMCONFIGJOBS the entry are
    REPORTNAME         GN_GENERATE_CHECK
    REPVARIANT
    JOBNAME            GN_GENERATE_CHECK
    PRIORITY           50
    PERIOD TYPE        DAY
    PERIOD INTERVAL    1
    START TIME         00:15:00
    ISIMMEDIATE
    INACTIVE
    WORKLOAD           M
    COMM2SAP
    REPORTNAME         GN_WORKLIST_GENERATE
    REPVARIANT
    JOBNAME            GN_WORKLIST_GENERATE
    PRIORITY           50
    PERIOD TYPE        DAY
    PERIOD INTERVAL    1
    START TIME         00:01:00
    ISIMMEDIATE
    INACTIVE
    WORKLOAD           L
    COMM2SAP
    any suggestions why the jobstart is not corresponding to the starttime in table SMCONFIGJOBS
    what job is scheduling these 2 Jobs GN_GENERATE_CHECK and GN_WORKLIST_GENERATE
    which other job maybe responsible for the object lock???

  • Overview, which Jobs are scheduled and which haven't finished successfully

    We are using GridControl jobs to administrate several databases (e.g. execute exports, analyze schemas, etc.). All of these jobs are scheduled...
    The "Home" tab of the GridControl GUI has the information "All target jobs" with "Problem executions" and "Suspended executions" - but what we would
    like to have is a view, which contains the job-names and their status.
    I've looked through the data-dictionary of the GridControl repository and found several tables and views which contain all kind of informations about the
    jobs.
    Does anybody already know, how to setup a view with the needed informations?
    We can't use the tab "Job activity" since the result of the view should be mailed to the developers...
    Any help will be appreciated...
    Rgds
    JH

    we are rather new to GridControl and not very experienced with the reports. I thought that just the already defined report-categories could be used.
    I went through the reports but couldn't find any report which is related to jobs.
    But thansks for your suggestion - we will try to create a report...

  • SAP GRC AC 5.3 RAR Background jobs are cancelled

    Hi Experts,
    we have newly implemented theS AP GRC AC 5.3 RAR  Help me in troubleshooting the Background jobs cancellation in SAP GRC AC5.3 RAR.. we have reported this issue to customersupport they asked us to upgrade the front end  patch level to Sp15, even we upgraded still i have the same problem.. later we upgraded the backend patch  according to the SAP Note. still the problem is not resolved.
    Latest recommendation they are asking us to uninstall the SMD agent.. and also my java control.exe is showing yellow color
    help me how to resolve the issue.??
    Edited by: n.s.k mohan on May 10, 2011 6:21 AM

    Hi,
    Could you please first change RAR log settings to Java logger then take a restart of the system. After that log for your background will start coming in RAR. Then schedule the job if it fails then paste background job log here.
    Also, in future, please raise GRC related issue in GRC forum so that you can get more replies.
    Thanks
    Sunny

  • All Background Jobs Are cancelled

    Hi all,
    I make a new server by restoreing backup of our production server and SAP is running well.But when I schedule any back ground jobs all jobs are cancelled.Due to this I am not able to run SGEN.Even when I manually schedule any back ground jobs it also cancelled and I am not getting any job log in SM37.I am not able to understand why this happens as I am not found any cancelled job log.Please suggest what shall I do to overcome this problem.
    Advance Thanks
    Nirmal

    Hi,
    check the file system /SAPMNT/<SID> space in your System.I think ur memory is fully utilized sapmnt folder.
    if u not need old logs  delete the log file in the following location.
    sapmnt/D01/global//<Clientno>JBLOG.
    Regards
    Senthil Kumar.S

  • Background Jobs are failing

    Hi Gurus,
    Below are the jobs which are being failed in our solution manager system since two weeks with error " Logon of user 'DDAWES' in cleint 100 failed.  Found that user got locked due to some auditing reasons and i had changed the background jobs  to run with another user however jobs are failing with same errror.
    Jobs List:
    SM:ACCELERATE DOC USAGE
    SM:CSA SESSION REFRESH
    SM:DYNAMIC TABU UPDATE
    SM:EXEC SERVICES
    SM:REFRESH ENTRYSCREEN
    SM:RNOTIFUPDATE01
    SM:SESSIONS RESET
    Unsure about this case why the jobs were failing though we have changed the user.
    Any sugegssions would be much appriciable
    Thanks & Regards,
    Vinod

    Both users are having same authorizations and both are dailog users only. It looks weird when i changed the user in job step for released jobs, it got changed and updated the job step with new use at that moment. However the jobs are faling and when i go through the job logs there I could see that OLd user name in job step.
    Changed the released  jobs many times to run with another user, however the jobs are failing with error " Logon of user DDAWES in client 100 failed when starting a step".
    Please note the jobs were running fine before the user locked out due to auditing. Also please let me know how do i check the E2E changes ? in SDM ? is ther any transaction code that i can check?
    Please suggest...
    Thanks & Regards,
    Vinod
    Edited by: vinod kumar on Jul 6, 2009 5:34 PM

  • Background Jobs are failing in DEV server after SP upgrade

    Hi Everyone,
    Below jobs are being failed in dev server after SP upgrade with error variant does not exist.
    SWWERRE, SWWDHEX, SWWCOND,  SWWCLEAR,SWFSLSDLEX, NON SAP USER UPLOAD
    System Details:
    SAP Version: ECC 6.0
    Database: SQL 2005
    OS: Windows 2003, SR2, 64 - bit.
    Kernel Patch: 221
    SAP_BASIS:19
    SAP_ABA :19
    SAP_APPL : 16
    SAP_AP :17
    SAP_HR : 51
    SAP_BW : 21
    PI_BASIS 2006_1_700 : patch 009
    ST_PI: ST_PI 2005_1_700 : 006
    FINBASIS : 16
    LOSFE: 16
    Can any one have idea on above mentioned jobs.
    Thanks & Regards,
    Vinod

    > Below jobs are being failed in dev server after SP upgrade with error variant does not exist.
    > SWWERRE, SWWDHEX, SWWCOND,  SWWCLEAR,SWFSLSDLEX,
    Those are workflow related jobs.
    > NON SAP USER UPLOAD
    This is a job name and not the program name.
    Markus

  • Does BPC requires a dialog type user because the jobs are scheduled from the BPC interface?

    Hi Gurus,
    I am a security person and we have a requirement from BPC functional team that they need a dialog user to schedule jobs. Below is the reply from functional team  
    "BPC supports only a regular user (dialog) for scheduling jobs and this user-id
    requires all the data access inside BPC to run the jobs. So long as the user is
    of type dialog and has all the access inside BPC, we should be fine."
    My question is Why we need a dialog for something in background. BPC does have a automatically created user BPC_SERVICE which is a System user, can't we use this user instead of a dialog user ? Please advise..
    Regards,
    Salman

    Let me put like this.. Requirement is: For Legal Consolidation run, the authorization required is all data access profiles/task profiles must be assigned to a dialog user else it is failing. Functional is stating that without this access assigned to their regular(dialog) user id the legal consolidation is failing and they also mentions that they can't use system user like BPC_SERVICE to complete this task.
    My question: Is BPC is designed like this where we need to give full access to a dialog user to complete a task which runs in background ?

  • Charms :  Background job not scheduled (normal correction) ?

    Hi,
    I am trying to run a dry cycle for normal correction but when i go to task plan in any ticket to release a request. When i schedule this job " release a request" , i dont see any job running in background in SM37. I think job is not gettin sceduled properly.
    Please help me out

    Hi,
    All right. We need to dig this one
    I guess you schedule the import by going the the tasklist
    and you get a red flag for this activity in the calendar ? do you have any error message ?
    If the messagein the task-list is not self-explanatory you can check the SLG1 log in SOLMAN. Which error message do you get there. (select the correct time frame, the log could be big)
    My guess is that some S_RFC authorisation is still missing there
    This authorisation is outside SAP_ALL and is often the cause of this kind of issue
    Tell me the error message and we will hopefully  fix this (I had the same kind of issue when I started last year)
    best regards Xavier

  • Reg:Background jobs are failing with out logs

    Hi Team,
    When i ran sm65 transaction in production i got the output.
      Test: Database table consistency test
         ==>  Inconsistent step no. for following job(s):
             ACS_SAP_HR                      14525701
             ACS_SAP_HR                      14525702
             ACS_SAP_HR                      14525801
             AUTO_SESSION_MANAGER            22091204
             AUTO_SESSION_MANAGER            22091301
             AUTO_SESSION_MANAGER            22132501
             EU_PUT                          19060603
             EU_REORG                        18180604
             OPEN_ENROLLMENT_SEND_EMAIL      15145305
             OPEN_ENROLLMENT_SEND_EMAIL      18301801
             RPTIME00                        22000822
             RSUVM008                        14330102
             SEND_INET_EMAIL                 08082001
    Can you please let me know how to proceed further.
    Thanks & Regards,
    Deve

    check this might help you
    http://mailman.mit.edu/pipermail/sap-wug/2005-July/018391.html
    Note 581692 - Apparently inconsistent job data - incorrect stepcount
    Note 1272015 - Jobs with empty job names or job count
    Note 37104 - Error analysis: Background processing system
    Edited by: Bhudev on May 22, 2009 6:22 AM

  • Background job "EU_REORG" scheduled to run daily is taking lot of time.....

    1) My BTC work processes always in run state.due to this my server is very slow.can i stop these processes?is there any harm in stopping these processes?
    due to this my server is very slow... how to speed up this job execution?
    i'm searching some threads.i have got SM50 . in that i got some info about background program which is long running and slowing down
    This is part of EU_REORG job that is scheduled to run daily.
    Report / Spool action : SAPLSEU_COMPONENT
    Main Program : RS_APPL_REFRESH
    Action                        Table
    Sequential Read        TADIR
    Database Number Time (usec) Recs.
    Direct Read 0 0 0
    Sequential Read 0 0,000000000000000E+ 0
    Insert 0 0 0
    Update 0 0 0
    Delete 0 0 0
    Sources 3.229.092 (Bytes)
    RSQL 367870216 (Bytes)
    Commit 4.349.042
    DB Procedure Calls 0 0
    Roles / Memory Number Time (usec)
    Roll In 3 1.583
    Roll Out 4 34.970
    Roll 286.720 (Bytes)
    Page 24.576 (Bytes)
    Memory (Total) 144.252.304 (Bytes)
    Memory(Total Private) 0 (Bytes)
    Memory (used) 137.970.624 (Bytes)
    Memory (Max. Transaction) 144.242.016 (Bytes)
    Memory (Max. Dialog Step) 144.242.016 (Bytes)
    this is what i got.  Please resolve....
    2) how to speed up the start of my sap instance ? it is taking nearly 20 mins to get all the work processes in wait mode..except this back ground job which is not coming into wait mode....
    Thanks & regards
    Will

    Hi,
    EU_REORG is scheduled to run every night (quiet time etc.) so as to refresh the 'where-used' index for the Development Workbench tools. Note 18023 will give you more information about the job.
    Check Note 1353707 if it applies to your case.

  • Background job finished but Error sending data

    Dear all,
    report is running in my prod server . once this report completed sapuser get mail . when i check the job status it shows
    Job started
    Step 001 started (program GP4CF9U420G825I4P7DU8XY49WH, variant CUSTOMEROUTSTD, user ID S2K_BASIS)
    Spool request (number 0000012259) created without immediate output
    Error sending data (4)
    Job finished
    one more clarity i required
    this report should goes to 4 SAP users . how can i configure this report to 4 sapusers
    kindly suggest me

    > Step 001 started (program GP4CF9U420G825I4P7DU8XY49WH, variant CUSTOMEROUTSTD, user ID S2K_BASIS)
    > Spool request (number 0000012259) created without immediate output
    > Error sending data (4)
    I'd check SCOT/SOST for any errors. Also check the syslog (SM21).
    > this report should goes to 4 SAP users . how can i configure this report to 4 sapusers
    Create a distribution list (SAPoffice-Inbox - environment - distribution list) and enter that as addresse for the output.
    Markus

  • How to schedule the background job daily twice?

    Hi,
    How to schedule the background job daily twice? any conditions?
    Regards,
    Srihitha

    see the step by step procedure.
    Scheduling Background Jobs:
    1. Background jobs are scheduled by Basis administrators using transaction SM36.
    2. To run a report in a background, a job needs to be created with a step using the report name
    and a variant for selection parameters. It is recommended to create a separate variant for each
    scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g.
    company codes).
    3. While defining the step, the spool parameters needs to be specified
    (Step-> Print Specifications->Properties) to secure the output of the report and help authorized users
    to find the spool request. The following parameters needs to be maintained:
    a. Time of printing: set to “Send to SAP spooler Only for now”
    b. Name – abbreviated name to identify the job output
    c. Title – free form description for the report output
    d. Authorization – a value defined by Security in user profiles to allow those users to access
    this spool request (authorization object S_SPO_ACT, value SPOAUTH). Only users with matching
    authorization value in their profiles will be able to see the output.
    e. Department – set to appropriate department/functional area name. This field can be used in
    a search later.
    f. Retention period – set to “Do not delete” if the report output needs to be retained for more
    than 8 days. Once the archiving/document repository solution is in place the spool requests could
    be automatically moved to the archive/repository. Storage Mode parameter on the same screen
    could be used to immediately send the output to archive instead of creating a spool request.
    Configuring user access:
    1. To access a report output created by a background job, a user must have at
    least access to SP01 (Spool requests) transaction without restriction on the user
    name (however by itself it will not let the user to see all spool requests). To have
    that access the user must have S_ADMI_FCD authorization object in the profile with
    SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).
    2. To access a particular job’s output in the spool, the user must have
    S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used
    in the Print Specifications of the job (see p. 3.d above).
    3. Levels of access to the spool (display, print once, reprint, download, etc) are
    controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least
    BASE access (display).
    On-line reports:
    1. Exactly the same configuration can be maintained for any output produced
    from R/3. If a user clicks “Parameters” button on a SAP Printer selection dialog, it
    allows to specify all the parameters as described in p. 3 of
    “Scheduling background jobs” section. Thus any output created by an online report
    can be saved and accessed by any user authorized to access that spool request
    (access restriction provided by the Authorization field of the spool request
    attributes, see p. 3.d of “Scheduling background jobs” section).
    Access to report’s output:
    1. A user that had proper access (see Configuring user access above) can
    retrieve a job/report output through transaction SP01.
    2. The selection screen can be configured by clicking “Further selection
    criteria…” button (e.g. to bring “Spool request name (suffix 2)” field or hide other
    fields).
    3. The following fields can be used to search for a specific output (Note that
    Created By must be blank when searching for scheduled job’s outputs)
    a. Spool request name (suffix 2) – corresponds to a spool name in p. 3.b in
    “Scheduling background jobs” section above).
    b. Date created – to find an output of a job that ran within a certain date range.
    c. Title – corresponds to spool Title in p. 3.c in “Scheduling background jobs”
    section above).
    d. Department - corresponds to spool Department in p. 3.e in “Scheduling
    background jobs” section above).
    4. Upon entering selection criteria, the user clicks the Execute button to
    retrieve the list of matching spool requests.
    5. From the spool list the user can use several function such as view the
    content of a spool request, print the spool request, view attributed of the spool
    request, etc. (some functions may need special authorization, see p.3 in
    Configuring user access)
    a. Click the Print button to print the spool request with the default attributes
    (usually defined with the job definition). It will print it on a printer that was
    specified when a job was created.
    b. Click the “Print with changed attributed” button to print the spool request
    with the different attributes (e.g. changing the printer name).
    c. Click the “Display contents” button to preview the spool request contents. A
    Print and Download functions are available from the preview mode.

  • What is the spool, what is its role in background job scheduling

    Hi,
    I want to know what is meant by Spool request and spool number generated.
    Tell about transaction SP01.
    How it is linked to Background job scheduling.
    thanks.
    sam.

    Hi,
    Refer this link.
    https://www.sdn.sap.com/irj/sdn/inf?rid=/library/uuid/7a5f4061-0a01-0010-c9bc-a4e4cb100438
    About SP01.
    Printing does not work in SAP. There is a printer definition for your local printer, but it does not work. Presuming that you use the program SAPLPD on your computer.
    Boot your computer and start only the SAPLogon and the SAPLpd program.
    Delete all of your old print jobs in the SAP system (Transaction SP01).Generate only one new print job.
    Check that there is enough resource in your computer. Check the free memory (Win 3.1x) and the free disk space (The lists are temporarily saved on your disk).
    Open the SAPLPD and read the print log in the window. The printer definition must correspond with the parameters shown here.
    Check that the standard printer is on the same lpt (Win 3.1: Control panel, Printer) as defined for the printer (usually lpt1).
    In Transaction SP01 read the protocol of your print job. Do not generate new print jobs! Wait till the SAP system changes the status of the print job.
    If you can not find the print job in SP01 anymore, then the print job was successfully printed out. If it didn't come out on your printer and the SAPLpd didn't indicate an incoming print job, then the connection was realised with another PC. Then SAP printer definition you used, does not correspond with your computer.
    Scheduling Background Jobs:
    1.        Background jobs are scheduled by Basis administrators using transaction SM36.
    2.        To run a report in a background, a job needs to be created with a step using the report name
    and a variant for selection parameters. It is recommended to create a separate variant for each
    scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g.
    company codes).
    3.        While defining the step, the spool parameters needs to be specified
    (Step-> Print Specifications->Properties) to secure the output of the report and help authorized users
    to find the spool request. The following parameters needs to be maintained:
    a.        Time of printing: set to u201CSend to SAP spooler Only for nowu201D
    b.        Name u2013 abbreviated name to identify the job output
    c.        Title u2013 free form description for the report output
    d.        Authorization u2013 a value defined by Security in user profiles to allow those users to access
    this spool request (authorization object  S_SPO_ACT, value SPOAUTH).  Only users with matching
    authorization value in their profiles will be able to see the output.
    e.        Department u2013 set to appropriate department/functional area name. This field can be used in
    a search later.
    f.        Retention period u2013 set to u201CDo not deleteu201D if the report output needs to be retained for more
    than 8 days. Once the archiving/document repository solution is in place the spool requests could
    be automatically moved to the archive/repository. Storage Mode parameter on the same screen
    could be used to immediately send the output to archive instead of creating a spool request.
    Configuring user access:
    1.        To access a report output created by a background job, a user must have at
    least access to SP01 (Spool requests) transaction without restriction on the user
    name (however by itself it will not let the user to see all spool requests). To have
    that access the user must have S_ADMI_FCD authorization object in the profile with
    SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).
    2.        To access a particular jobu2019s output in the spool, the user must have
    S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used
    in the Print Specifications of the job (see p. 3.d above).
    3.        Levels of access to the spool (display, print once, reprint, download, etc) are
    controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least
    BASE access (display).
    On-line reports:
    1.        Exactly the same configuration can be maintained for any output produced
    from R/3. If a user clicks u201CParametersu201D button on a SAP Printer selection dialog, it
    allows to specify all the parameters as described in p. 3 of
    u201CScheduling background jobsu201D section. Thus any output created by an online report
    can be saved and accessed by any user authorized to access that spool request
    (access restriction provided by the Authorization field of the spool request
    attributes, see p. 3.d of u201CScheduling background jobsu201D section).
    Access to reportu2019s output:
    1.        A user that had proper access (see Configuring user access above) can
    retrieve a job/report output through transaction SP01.
    2.        The selection screen can be configured by clicking u201CFurther selection
    criteriau2026u201D button (e.g. to bring u201CSpool request name (suffix 2)u201D field or hide other
    fields).
    3.        The following fields can be used to search for a specific output (Note that
    Created By must be blank when searching for scheduled jobu2019s outputs)
    a.        Spool request name (suffix 2) u2013 corresponds to a spool name in p. 3.b in
    u201CScheduling background jobsu201D section above).
    b.        Date created u2013 to find an output of a job that ran within a certain date range.
    c.        Title u2013 corresponds to spool Title in p. 3.c in u201CScheduling background jobsu201D
    section above).
    d.        Department - corresponds to spool Department in p. 3.e in u201CScheduling
    background jobsu201D section above).
    4.        Upon entering selection criteria, the user clicks the Execute button   to
    retrieve the list of matching spool requests.
    5.        From the spool list the user can use several function such as view the
    content of a spool request, print the spool request, view attributed of the spool
    request, etc. (some functions may need special authorization, see p.3 in
    Configuring user access)
    a.        Click the Print button   to print the spool request with the default attributes
    (usually defined with the job definition). It will print it on a printer that was
    specified when a job was created.
    b.        Click the u201CPrint with changed attributedu201D button   to print the spool request
    with the different attributes (e.g. changing the printer name).
    c.        Click the u201CDisplay contentsu201D button   to preview the spool request contents. A
    Print    and Download   functions are available from the preview mode.
    Exporting the Contents of a Spool Request
    Use
    You want to export the contents of a spool request as a text file to the SAP GUI working directory or to a directory of your choice. The content of the spool request is downloaded as plain text without, for example, graphics, images, or specific fonts.
    The following procedures are irrelevant for the PDF-based form printing integrated as of SAP Web Application Server 6.40, since the print data can be opened and stored as a PDF. See also Displaying and Printing PDF-Based Forms.
    Procedure
    Exporting to the SAP GUI Working Directory:
    Choose Spool Request ® Forward® Export as Text.
    The entire text is stored in your SAP GUI working directory in ASCII format.
    A file of this type is named using the following pattern:
    .txt
    Example: ABC0000004327.txt
    You require appropriate authorization for this function.
    Exporting to a Directory of Your Choice:
    With this method of exporting a spool request, the content of the spool request is first displayed and you then download the screen list as a text file to the directory of your choice.
           1.      Select the spool request to be exported and choose  Display Contents.
           2.      In the case of SAPScript/Smart Forms documents, activate list display by choosing Goto.
           3.      Choose System ® List ® Save ® Local File.
           4.      Choose one of the available formats and confirm your choice.
           5.      Choose a directory and save the spool request.
    By default, only the first 10 pages of a spool request are saved in a file. You can increase the number of pages to be saved by choosing Goto ® Display Requests ® Settings and making the desired entries in the Display Area group box.

  • Variants for background jobs

    You need to schedule and automate batch jobs in an organisation. There will be multiple variants and multiple steps within same batch jobs. The variants are date dependent and needs to change every day. You need to automatically change the variants every day and schedule the jobs. Also check for the failures in the jobs. Apart from that Once the jobs in one server example : R/3 server ends the jobs in BW servers should be triggered automatically. Explain all steps with proper T codes and also provide a dry run example. Also provide all the table used for the variants purpose.
    Please help on this,thanks
    Narendra

    Hi Narendra,
    The background jobs are scheduled depending on the requirement with specific variants which are both date specific and even specific sometimes. These variants are created for the programs or reports which are run in the background job ,These variants are stored in VARID table for client specific variants and
    VARID_CI for client independent. For most of the times all these jobs are maintained in some job scheduling tools so that they automatically inform about job failures and processes can be automated.In our organisation we use UC4 for background job schedulign and it controls the process as you are looking for.
    Please award points accordingly
    With Regards,
    Junaid
    Message was edited by:
            muhammed junaid

Maybe you are looking for