Create Background Job after data saved in module

Hello,
I have a program that has a start selection screen with material group, you enter your data, execute.  When it has finished you get a ALV of sales order with items where you can make changes to dates and other details and save.  I would like to add a save in background option.  Is this possible? I assume it would be difficult because of the container.. it uses a bapi to save sale orders...
The employees run this job which takes a little while.. at the end of the day.. they go home and of course SAP has timed out.  If they can run it in the background then no problem....
Thanks,
AJ

well, you can pass the data from the same to an other program and submit it in background.
Just create a job.
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
            jobname          = gv_jobname
       IMPORTING
            jobcount         = gv_jobcount
       EXCEPTIONS
            cant_create_job  = 1
            invalid_job_data = 2
            jobname_missing  = 3
            OTHERS           = 4.
  IF sy-subrc <> 0.
*   no error required
  ENDIF.
submit your program with job name and job count.
CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
            jobcount             = gv_jobcount
            jobname              = gv_jobname
            strtimmed            = 'X'
       EXCEPTIONS
            cant_start_immediate = 1
            invalid_startdate    = 2
            jobname_missing      = 3
            job_close_failed     = 4
            job_nosteps          = 5
            job_notex            = 6
            lock_failed          = 7
            OTHERS               = 8.
  IF sy-subrc <> 0.

Similar Messages

  • Trigger a background job after executing tcode MMPV

    Hi All,
    I would like to trigger a background job after executing tcode MMPV. In MMPV, after closing a particular period and entering
    new period, the transaction will be saved. After saving, the background job should be triggered. How to do it?
    Regards,
    Vinod

    Depending what system you are on your best bet would be to create an enhancement point inside a form, that is called after the save has been performed, and raise an event within that form.
    Events can be used to trigger background jobs are maintained in transaction SM62.
    Cheers.

  • Create Background jobs

    How can i create background jobs and link them to the Event so that they will be triggered? I have no clue on this, can anyone explain in a detailed manner with the Transaction codes for each.
    Thanks in advance.

    Hi laitha,
    JOB is a program which starts to a determined point of time and executes some standard programs in the system. JOBs can be planed to a determined point of time on the regular basis (every night, for example) or to some discret time moments. So, the JOB can be planed and then will be started automatically without the manual start.
    Realtime programs are understood in the most cases as actual program execution which is started by somebody to the actual moment of time.
    Typically per JOBs some special processes will be started that should be executed automatically and regularly: for example, IDOC application, some correction reports, statistic updates etc.
    Standard jobs are those background jobs that should be run regularly in a production SAP System These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
    Use
    As of Release 4.6C, the Job Definition transaction ( sm36 ) provides a list of important standard jobs, which you can schedule, monitor, and edit.
    Standard jobs are those background jobs that should be run regularly in a production SAP System. These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
    for more information you can go thru the following thread:
    http://help.sap.com/saphelp_nw70/helpdata/en/24/b884388b81ea55e10000009b38f842/frameset.htm
    About Events:
    Events have meaning only in the background processing system. You can use events only to start background jobs.
    Triggering an event notifies the background processing system that a named condition has been reached. The background processing system reacts by starting any jobs that were waiting for the event.
    Types of Events:
    There are two types of events:
    1.)System events are defined by SAP. These events are triggered automatically when such system changes as the activation of a new operation mode take place.
    2.)User events are events that you define yourself. You must trigger these events yourself from ABAP or from external programs. You could, for example, signal the arrival of external data to be read into the SAP system by using an external program to trigger a background processing event.The event scheduler processes an event if the event is defined in the system.
    For example, if a system (System 1) receives an event from another system (System 2), the event scheduler of System 1 processes the event only if it is defined in System 1. That event does not need to be defined in System 2 (the sending system).
    You define an event by assigning a name (EVENTID) to it. When defining an event, you do not define the event arguments.
    for more information you can go thru the following thread:
    http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e2a543b11d1898e0000e8322d00/frameset.htm
    When you schedule the process chain or infopackages the jobs associated with it run in the background mode. In case you want to create a job for a specific activity you can do so in SM36. You would be creating jobs that would get executed in any one of the options:
    1. Immediate
    2. Date & Time
    3. After event.
    4. After job.
    5. At Operation mode.
    In case you want to view the job logs go to sm37.
    _List of Background Jobs_
    BIREQU - Load of a Request/Reconstruction of a request
    BI_AGGR4 - Aggregates activation
    BI_BTCH - Any batch job like ABAP program run in background
    BI_DELR - Deletion of request
    BI_HIER - Hierarchy loading/activation
    BI_ODSA - ODS activation
    BI_PROCESS_ABAP - ABAP program in process chain
    BI_PROCESS_LOADING - Data Loading in process chain using nfopackage
    BI_PROCESS_ODSACTIVAT - ODS actiavation in Process chain
    BI_PROCESS_TRIGGER - Trigger job for process chain
    BI_PSAD - probably PSA deletion
    BI_STAT - Building statistics
    BI_STRU - Change run job
    BI_WRITE_PROT_TO_APPLLOG - Application log job
    RANATL_ACCT_CACHE_WARMUP
    Use tcode SM62 to create User events.
    Use tcode SM64 to trigger the event.
    Wizards for Event Creation :pls chk this link
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/f7/d1c20a02d511d3a6550060087a79ea/frameset.htm
    *pls assign points,if info is useful**
    Regards
    CSM reddy

  • Scheduled Background jobs after Client Copy

    Hello,
    I've been doing some searching online and I don't seem to be able to find a definitive answer to this question:
    Are background jobs client specific?
    I've seen some discussions on here say some are and some are not.  I've also seen a discussion that says ALL background jobs are client specific.
    It's really related to non-SAP background jobs after a client copy.
    If I have a client 100 in QA with half a dozen non-SAP standard jobs configured, and I create client 110 in QA and perform a remote client copy from PROD into client 110 on QA, will my non-SAP standard backgrounds run in Client 110, or do I need to set them all up again?
    Thanks

    Hello All
    If I have a client 100 in QA with half a dozen non-SAP standard jobs configured, and I create client 110 in QA and perform a remote client copy from PROD into client 110 on QA, will my non-SAP standard backgrounds run in Client 110, or do I need to set them all up again?
    Yes. You will need to set those non standard jobs in the new client. When you schedule a job there will be a reference to the client where the job will be executed is stored under AUTHCKMAN in the table TBTCO. If the job is scheduled periodically then the job is executed only on the client where it is scheduled.
    I used SAP_ALL profile when performing the client copy.  So my scheduled jobs WILL have been copied along with everything else? Is that correct?
    In SAP_ALL profile the background jobs will be coming from source client not from QA client 100.
    No. Background jobs are not transportable and will not be copied during a client copy. Job definitions are client independent.
    Read these SAP notes.
    31503 - FAQ: Background jobs
    51135 - Why are bkgd processing jobs not generally transportable?
    If you want to schedule those jobs in the new client the follow the suggestion in the SAP note 3150 point 6.
    Regards
    RB

  • How define background job, after a job,  daily

    Hi Gurus!
    i need to create several Jobs, one after another. i'm working with R/3 enterprise.
    I can create a Job after another, but I can't put it daily.
    anyone knows how I can define job, after a specific job, daily???
    THANKS!!!!

    Hi Oscar,
    If you want to execute the Background jobs one by one(sequence order),
    Goto <b>SM36</b> and create a Background job, then create another job then press <b>Start condition</b>, in this one there is  a tab after JOB, here give the job name, os the will be run after this job complets
    another way is there, if you want to run the jobs in a sequence, there is a <b>TAB called STEP</b>, create a Job name then press the tab STEP, here give the first job name then press the create button then create the second job name.. like this you can give N number of background Programs one by one
    hope you got the answer
    Thanks
    Sudheer

  • How to create Background job for Dialog program

    Hi Experts,
    I have copied Standard tcode to Z-tcode (CS12 tcode).
    Now my requirement is to create background job for this program (but program is not a 'E' type its 'I').
    How we can schedule Dialog program to Background.
    Pls suggest me.
    Regards
    SK

    Hi do as below :
    Reefer below :
    Bakcground Job Creation
    You will have to submit your report using Submit statement ,
    then inside the submitted report write open_job.
    Regards,
    Uma

  • Create background job

    Hi,
    is it possible to create background job of a program with POO, i had a look on class, i found CL_BP_ABAP_JOB or CL_BP_JOB but i don't use them.
    Otherwise i will use 'JOB_OPEN' but i like POO
    Can you help me ?

    I answer myself...
    The class to use is cl_bp_abap_job.

  • Problems creating background job for program (job open, submit and close)

    Hi gurus,
    im trying to start a background job using the FM BP_START_DATE_EDITOR to show the start date to the job or if it's imediate. this FM it's working fine, after call it im opening a job, submiting it and call the job close FM and the job close FM creates me the job.
    The problem it's when i go to the sm37 to see the job status the job has been canceled, and the job log says that i have to give a start date to the job.
    What i dont understand it's either the job is imediate or i choose a date to start the job always gives me this error...
    Below goes my code,
    any ideas will be rewarded
      CLEAR: stdt_modify_type, stdt_output.
      CALL FUNCTION 'BP_START_DATE_EDITOR'
           EXPORTING
                stdt_dialog                    = 'Y'
                stdt_input                     = stdt_input
                stdt_opcode                    = 14
           IMPORTING
                stdt_modify_type               = stdt_modify_type
                stdt_output                    = stdt_output
           EXCEPTIONS
                fcal_id_not_defined            = 1
                incomplete_last_startdate      = 2
                incomplete_startdate           = 3
                invalid_dialog_type            = 4
                invalid_eventid                = 5
                invalid_opcode                 = 6
                invalid_opmode_name            = 7
                invalid_periodbehaviour        = 8
                invalid_predecessor_jobname    = 9
                last_startdate_in_the_past     = 10
                no_period_data_given           = 11
                no_startdate_given             = 12
                period_and_predjob_no_way      = 13
                period_too_small_for_limit     = 14
                predecessor_jobname_not_unique = 15
                startdate_interval_too_large   = 16
                startdate_in_the_past          = 17
                startdate_is_a_holiday         = 18
                startdate_out_of_fcal_range    = 19
                stdt_before_holiday_in_past    = 20
                unknown_fcal_error_occured     = 21
                no_workday_nr_given            = 22
                invalid_workday_countdir       = 23
                invalid_workday_nr             = 24
                notbefore_stdt_missing         = 25
                workday_starttime_missing      = 26
                no_eventid_given               = 27
                OTHERS                         = 28.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        MOVE 'X' TO gv_flag.
      ENDIF.
      DATA jobname LIKE tbtcjob-jobname.
      DATA jobcount LIKE tbtcjob-jobcount.
      DATA job_release LIKE  btch0000-char1.
      DATA job_imediate TYPE c.
      CLEAR: jobname, jobcount, job_release.
      CONCATENATE 'MAPAEXEC' sy-uname sy-datum
                   INTO jobname SEPARATED BY space.
      CALL FUNCTION 'JOB_OPEN'
           EXPORTING
                jobname          = jobname
           IMPORTING
                jobcount         = jobcount
           EXCEPTIONS
                cant_create_job  = 1
                invalid_job_data = 2
                jobname_missing  = 3
                OTHERS           = 4.
      IF sy-subrc <> 0.
        MESSAGE i003(zmapas).
        EXIT.
      ENDIF.
      SUBMIT z_mapa_execucao_orcamental
             VIA JOB jobname NUMBER jobcount
             WITH ano EQ ano
             WITH so_perio IN so_perio
             WITH so_date IN so_date
             WITH so_org EQ so_org
             WITH so_num IN so_num
             AND RETURN.
      IF stdt_output-startdttyp EQ 'I'.
        CLEAR job_imediate.
        job_imediate = 'X'.
      ENDIF.
      CALL FUNCTION 'JOB_CLOSE'
           EXPORTING
                calendar_id                 = stdt_output-calendarid
                event_id                    = stdt_output-eventid
                event_param                 = stdt_output-eventparm
                event_periodic              = stdt_output-periodic  "?
                jobcount                    = jobcount
                jobname                     = jobname
                laststrtdt                  = stdt_output-laststrtdt
                laststrttm                  = stdt_output-laststrttm
                prddays                     = stdt_output-prddays  "??
                prdhours                    = stdt_output-prdhours  "?
                prdmins                     = stdt_output-prdmins  "??
                prdmonths                   = stdt_output-prdmonths
                prdweeks                    = stdt_output-prdweeks  "?
                predjob_checkstat           = stdt_output-checkstat
                pred_jobcount               = stdt_output-predjobcnt
                pred_jobname                = stdt_output-predjob
                sdlstrtdt                   = stdt_output-sdlstrtdt
                sdlstrttm                   = stdt_output-sdlstrttm
                strtimmed                   = job_imediate
                targetsystem                = stdt_output-instname
                start_on_workday_not_before = stdt_output-notbefore
                start_on_workday_nr         = stdt_output-wdayno
                workday_count_direction     = stdt_output-wdaycdir
           IMPORTING
                job_was_released            = job_release
           EXCEPTIONS
                cant_start_immediate        = 1
                invalid_startdate           = 2
                jobname_missing             = 3
                job_close_failed            = 4
                job_nosteps                 = 5
                job_notex                   = 6
                lock_failed                 = 7
                OTHERS                      = 8.
      IF sy-subrc <> 0.
        MESSAGE i003(zmapas).
        EXIT.
      ELSE.
        MESSAGE i004(zmapas) WITH jobname.
      ENDIF.
    Thanks in advance,
    Best Regards
    João Martins

    Hello João.
    In debug mode, check the value of variables you passed to parameters sdlstrtdt and sdlstrttm.
    As aditional info, I usually achieve your goal without FM BP_START_DATE_EDITOR.
    Check this code:
    CALL FUNCTION 'JOB_OPEN'
          EXPORTING
               jobname          = w_jobname
          IMPORTING
               jobcount         = w_jobcount
          EXCEPTIONS
               cant_create_job  = 1
               invalid_job_data = 2
               jobname_missing  = 3
               OTHERS           = 4.
    CHECK sy-subrc = 0.
    CLEAR seltab_wa.
    MOVE: t_jobs-param TO seltab_wa-selname,
    t_processar-line+34 TO seltab_wa-low.
    APPEND seltab_wa TO seltab.
    seltab_wa-selname = 'P_LOJA'.
    seltab_wa-low = t_processar-ficheiro+7(4).
    APPEND seltab_wa TO seltab.
    *** Submete o programa para o JOB
    SUBMIT (t_jobs-repid)
      WITH  SELECTION-TABLE seltab
      USER sy-uname
       VIA JOB w_jobname NUMBER w_jobcount
       AND RETURN.
    *** Encerra o JOB
      l_hora = sy-uzeit.
      ADD 60 TO l_hora.
    CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
          jobcount           = w_jobcount
          jobname           = w_jobname
          sdlstrtdt            = sy-datum
          sdlstrttm           = l_hora
          targetserver       = w_servidor
       IMPORTING
          job_was_released     = l_liberado
       EXCEPTIONS
          cant_start_immediate = 1
          invalid_startdate    = 2
          jobname_missing      = 3
          job_close_failed     = 4
          job_nosteps          = 5
          job_notex            = 6
          lock_failed          = 7
          OTHERS               = 8.
    Regards.
    Valter Oliveira.

  • Inbound IDoc creating background job even for trigger immediately setup

    All,
    I have a very serious problem in our production system.
    Scenario:
    Vendor is chagend in system A (Outbound) and the same is interfaced to System B (Inbound) and i am using trigger immediately option, but still I am seeing a background job is created for 'RBDAPP01' and creating the spool request. The issue is I am sending 1000 of idocs and the spool number is increasing daily in system B.
    So, can any one explain me why the background job is getting triggered even though I set the partner profile settings as 'Trigger Immediately'.
    The above issue is not happening in our quality system it simply updagtes vendor information in system B with out creating any background job. Please note that the same settings are maintained in both the systems.
    Your immediate inputs are really valuable for me.
    Regards,
    Suman

    This is an performance issue on the receiving system. In case the system does not have enough resources to process the IDoc immediately it will always schedule a background job to ensure the processing of data.
    You need to check whether the system has enough work processes available during the time when 1000 of IDocs are received or send the IDocs in packages with some time in between.
    Regards,
    Kai

  • Create background job triggered by another job

    Hi experts,
    I want to run FCHU in background everytime I finished run F110.
    I'm thinking to use background job creation SM36 - triggered by job. But the problem is, job created from F110 the job name is not fixed.
    Please anyone can give better idea ??
    Thanks,
    Melissa

    Hi melissa,
    The suggestion given by Prem is perfectly Ok.
    I would suggest you to create an event  by sm62 and then create an event triggered  background job which will run the FCHU in Back ground.
    So you need to get an enhancement point in F110 and put the code of triggering the event .
    If there is no enhancement  then you can create a program which will call the Transaction F110 by using CALL TRANSACTION statement and after F110 processing the control will get back to your program and you can write a code for triggering the event by using the FM SWE_EVENT_CREATE.
    I hope this will help you

  • Backup of background jobs after system refresh

    Hi All,
    I want to know that during the system refresh how can we take the backup of the background jobs which are in "Released" state so that we can schedule them the same way after the refresh is done. Presently we are taking the screen shot of "start condition" and "step" of each and every job and then using those screenshots we are scheduling them again after the refresh is completed. It would be really helpful and time saving for us if we come to know the tables where this information is stored and also if there is any other easier way for this.
    Regards,
    Lovneesh

    Hello,
    Check the below thread. It mentions all the tables that contain batch job information.
    https://scn.sap.com/thread/1709175
    " Check below mentioned tables
    BTCCTL,
    BTCDELAY
    BTCEVTJOB
    BTCH1000
    BTCH1010
    TBTCO
    TBTCP
    These have all the information you need regarding background jobs, you may export these tables at the source and import them "
    Check and provide feedback.
    Regards,
    Mudasir

  • Error message while runing the Synch Job in Background job after Patch Upgd

    Friends
    We are 5.3 GRC CC on Windows 2003 and ECC 6.0  BI 7.0
    We just upgraded the patches to 12 for GRC CC and ran the Synch job in background....
    Eveytime we run the Synch job for Usre Roles and profiles or Batch Risk Analysis in Background, job finishes until 99 percent and then gives "Error" Message...
    Heres is the job history..:
    2010-09-26 13:14:25 Started Incremental Batch Risk Analysis 09262010 started :threadid: 0
    2010-09-26 13:18:06 Failed Error while executing the Job for Object(s) :PPORTELLA:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot i... (see log for details)
    2010-09-26 13:18:14 Failed Error while executing the Job for Object(s) :RCHAPMAN:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot in... (see log for details)
    2010-09-26 13:18:02 Failed Error while executing the Job for Object(s) :OJONES:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot inse... (see log for details)
    2010-09-26 13:19:21 Failed Error while executing the Job for Object(s) :YPATEL:[NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_CC_COMPROL__5CE34ED1'. Cannot inse... (see log for details)
    2010-09-26 13:49:42 Failed Error Job not completed
    Did anyone has the same issue after the patch upgrade ?
    Pranav
    The version info for the GRC CC..
    Version: AC-RAR 5.3_12.0
    Build ID: 05140510

    Hi I do get a error while scheduling Background job in RAR 5.3 , Please help me out...........waiting for your reply
    Apr 13, 2012 7:38:59 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:39:00 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:39:01 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:39:02 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:39:03 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:39:04 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:39:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:06 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:39:06 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:07 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:39:07 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:08 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:39:08 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:09 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:39:09 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:10 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:39:10 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:11 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:39:11 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:12 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:39:12 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:13 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:39:13 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:39:14 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:39:15 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:16 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:40:16 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:17 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:40:17 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:18 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:40:18 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:19 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:40:19 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:20 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:40:20 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:21 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:40:21 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:22 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:40:22 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:40:23 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:40:23 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:24 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:41:24 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:25 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:41:25 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:26 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:41:26 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:27 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    Apr 13, 2012 7:41:27 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=3&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:28 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    Apr 13, 2012 7:41:28 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=4&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:29 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    Apr 13, 2012 7:41:29 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=5&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:30 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    Apr 13, 2012 7:41:30 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=6&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:41:31 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    Apr 13, 2012 7:41:31 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=7&daemonType=WS
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:42:32 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    Apr 13, 2012 7:42:32 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=0&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:42:33 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    Apr 13, 2012 7:42:33 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=1&daemonType=BG
                    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:814)
                    at com.virsa.cc.xsys.bg.AnalysisDaemonThread.run(AnalysisDaemonThread.java:67)
                    at java.lang.Thread.run(Thread.java:534)
    Apr 13, 2012 7:42:34 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=G:\usr\sap\VIN\DVEBMGS00\j2ee\cluster\server0\.&threadId=2&daemonType=BG
    Apr 13, 2012 7:42:34 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    WARNING: Server returned HTTP response code: 500 for URL: http://home:50000/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?dae

  • Unable to create Background job

    Hi All,
    I am trying to create a background job for standard program RFBIBL00 from a client QP1-231. But I am not able to do it as I am getting a message that the client differs from the original client qp1-020.
    I AM ABLE TO CREATE THE BACKGROUND JOB FROM QP1-020,but not from QP1-231.
    Please look into the matter and let me know why I am not able to creat the job from QP1-231.
    I promise to reward.

    Hi,
         Please check with your basis team whether you have authorization for the same.
    Raghav

  • Hi friends need some help while creating background job

    I need to run a batch report in background in SM36 when any cancellation of sales order is done in VL09.
    i.e when a cancellation of sales order is done i have to run a batch report which will call an IDOC outbound generation function module that will create the IDOC.....
    Please tell me how to do this.....

    Hi,
    To submit backgroud jobs.
    Call Function 'Job_Open'.
    SUBMIT <report name>
    WITH <input variants>
    USER sy-uname
    VIA JOB <job name>
    AND RETURN.
    If sysubrc eq 0.
    Call Function 'Job_Close'.
    Reward if helpfull.

  • Periodic Background Jobs after another Job finishes

    Hi
    I have to schedule a job 'B' to run after job 'A' finishes.
    When i schedule job 'B' to run after job A , it runs only once , while i need the job B to run periodically after job A finishes.
    1) I cannt make job B as step 2 of job A , because job A is not scheduled by me and i cannt change that.
    Can anyone tell me how to i trigger the job B periodicaly after job A finishes .
    Any solution or hint would be appreciated.
    Looking forward to some helpful replies from the gurus of SAP.
    Regards
    Purva

    Dear Team,
    Job ES_RPTMC_CREATE_CHANGEPOINT_AUTH  ran only once where as SEC:INDX_UPDATE_FOR_STRUCT_AUTHS ran daily.
    CAUSE:
    “The start condition "Start after job" is internally mapped by means of "Start after event SAP_END_OF_JOB with the parameter <Jobname><Jobcount> of the predecessor". The pair <Jobname><Jobcount> is the unique key for a job.
    If a job is executed periodically, the SAP_END_OF_JOB event is always triggered with different parameters.
    The successor in turn waits for SAP_END_OF_JOB with just one particular parameter (this is the parameter with <Jobname><Jobcount> from the first predecessor). When the successor is rescheduled, the key fields from the next predecessor must therefore always be known in advance, something which is not always technically possible.”
    SOLUTION:
    This task can be completed with the new ABAP program Program  BTC_EVENT_RAISE.
    The program is delivered by Support Package for Basis Releases 640 and 700, and is included in the standard system in all subsequent releases.
    The program is used to trigger a batch event. Existing programs do not therefore have to be changed. The BTC_EVENT_RAISE program has several parameters in the selection screen, including the event (and parameters) that is to be triggered.
    PROCESS:
     Go To SM64
     Click on Create
     Create two events.
    Our Case:
    We created Z_ES_CP_AUTH and Z_SEC_AUTHS
     Go to SE38
     Give the event name as BTC_EVENT_RAISE
     Select Variants and click on Display
     Give the variant name as the one you created.
    Our Case:
    Z_ES_CP_AUTH
     Click on Create
     Give in the details for variants
     Click on attributes and give the details for attributes
     Go to the job which needs to be run first
    • Select the job in released status
    • Job->Change
    • Step
    • Add BTC_EVENT_RAISE as the last step of the job with the parameter as the variant created
    Our Case:
    Step: BTC_EVENT_RAISE, Parameter: Z_ES_CP_AUTH
     Go to the job which needs to be run next
    • Select the job in released status
    • Job->Change
    • Start Condition -> After Event.
    • Give the BTC_EVENT_RAISE parameter of the first job as the event of the second job.
    Our Case:
    After Event: Z_ES_CP_AUTH
     Save the changes.
     The jobs will start running one after the other with the given frequency.
    Thanks
    Joginadham U

Maybe you are looking for

  • IDoc Acknowledgment Clarification

    Hi,      I have a doubt in IDoc Acknowledgment Scenario My doubt is: My XI server date is a week prior to the date of R/3 server. Is it possible to get Acknowledgment for IDoc if the date of the R/3 server and XI server doesn't match. Thanks in advan

  • Submit form in a div to a cfdiv

    Hi all, I have a page with a search form at the top, and the search results at the bottom. I would simply like to have the form, which is currently in a div, submit to the search results cfdiv. I know I could put the form and search results together

  • Use folios completely offline

    Hi, I use InDesign CS5.5 for creating folios playable on iPad via the Digital Publishing Suite, it works pretty good and the benefit system for my client is that once the folio loaded on the iPad in Content Viewer it can be viewed offline, no need in

  • Where I need to check to make profile field in ECM compulsory?

    Hi Guys, where I need to check to make change type & profile field in ECM compulsory(in CC01/CC31)? Thanks & Regards JS

  • Access Restriction

    I think Linksys should redesign the Access Restriction in the Router configuration.  I currently have a 3rd party software block some sites at my stepson's computer.  However, I cannot block those website whenever he uses his PSP or his iPod Touch.