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.

Similar Messages

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

What to add to an program code in order to trigger an background job

Hi there
I wander what to add to an program code in order to trigger an event which consequently can trigger an background job
thx in advance

Check this code:
DATA : v_jobhead LIKE tbtcjob.
DATA : v_jobcount LIKE tbtcjob-jobcount.
DATA : v_eventparm LIKE tbtcjob-eventparm.
DATA : v_flg_released TYPE c.
DATA: e_error.
DATA: running LIKE tbtcv-run.
TYPES: esp1_boolean LIKE boole-boole.
CONSTANTS: esp1_false TYPE esp1_boolean VALUE ' ',
 esp1_true TYPE esp1_boolean VALUE 'X'.
CONSTANTS: true TYPE boolean VALUE esp1_true,
 false TYPE boolean VALUE esp1_false.
PARAMETERS: v_jobnam LIKE tbtcjob-jobname,
 v_report LIKE sy-repid,
 v_varian LIKE raldb-variant,
 v_uname LIKE sy-uname.
START-OF-SELECTION.
* add the new job
CALL FUNCTION 'JOB_OPEN'
 EXPORTING
* delanfrep = 'X'
 jobname = v_jobnam
 IMPORTING
 jobcount = v_jobcount
 EXCEPTIONS
 cant_create_job = 1
 invalid_job_data = 2
 jobname_missing = 3
 OTHERS = 4.
IF sy-subrc <> 0.
 e_error = true.
ELSE.
 CALL FUNCTION 'JOB_SUBMIT' " or you can use SUBMIT statement as well.
 EXPORTING
 authcknam = v_uname
 jobcount = v_jobcount
 jobname = v_jobnam
 report = v_report
 variant = v_varian
 EXCEPTIONS
 bad_priparams = 1
 bad_xpgflags = 2
 invalid_jobdata = 3
 jobname_missing = 4
 job_notex = 5
 job_submit_failed = 6
 lock_failed = 7
 program_missing = 8
 prog_abap_and_extpg_set = 9
 OTHERS = 10.
 IF sy-subrc <> 0.
 e_error = true.
 ELSE.
 CALL FUNCTION 'JOB_CLOSE'
 EXPORTING
* EVENT_ID = IC_WWI_WORKPROCESS_EVENT
* EVENT_PARAM = V_EVENTPARM
* EVENT_PERIODIC = 'X'
 jobcount = v_jobcount
 jobname = v_jobnam
 strtimmed = 'X'
 IMPORTING
 job_was_released = v_flg_released
 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.
 e_error = true.
 ELSE.
 DO.
 CALL FUNCTION 'SHOW_JOBSTATE'
 EXPORTING
 jobcount = v_jobcount
 jobname = v_jobnam
* IMPORTING
* ABORTED =
* FINISHED =
* PRELIMINARY =
* READY =
* running =
* SCHEDULED =
 EXCEPTIONS
 jobcount_missing = 1
 jobname_missing = 2
 job_notex = 3
 OTHERS = 4.
 IF sy-subrc <> 0.
 e_error = true.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 ENDIF.
 IF running = space.
 EXIT.
 ENDIF.
 ENDDO.
 ENDIF.
 ENDIF.
ENDIF.

How to trigger a background job from BADI method.

hi friends,
i need to trigger a background job from the badi method CHANGE_AT_SAVE for the BADI BOM_UPDATE.
for this i think i need to create an event which i should give with parameters during job creation.
can you pls help me solve this issue.
thank u all.

Hi Saravanan,
Here is an example of what you have to do.
Regards,
Eric
Reward any helpful sugestion.
*&      Form generar_job
FORM generar_job .
Generar Variante
PERFORM generar_variante.
w_fecha = sy-datum + 3.
CALL FUNCTION 'DATE_COMPUTE_DAY'
    EXPORTING
      date = w_fecha
    IMPORTING
      day = w_weekday.
Si la fecha cae en sabado o domingo se debe continuar el lunes.
CASE w_weekday.
    when '1'.
      ADD 2 TO w_fecha.
    WHEN '6'.
      ADD 2 TO w_fecha.
    WHEN '7'.
      ADD 1 TO w_fecha.
ENDCASE.
w_jobname = 'ZQM_CIERRE_LOTE_INSPECCION'.
CALL FUNCTION 'JOB_OPEN'
    EXPORTING
      jobgroup         = 'QUEUE'
      jobname          = w_jobname
    IMPORTING
      jobcount         = w_jobcount
    EXCEPTIONS
      cant_create_job = 1
      invalid_job_data = 2
      jobname_missing = 3
      OTHERS           = 4.
IF sy-subrc EQ 0.
    CALL FUNCTION 'JOB_SUBMIT'
      EXPORTING
        authcknam               = sy-uname
        jobcount                = w_jobcount
        jobname                 = w_jobname
        report                  = 'ZQM_CIERRE_LOTE_INSPECCION'
        variant                 = w_var
      IMPORTING
        step_number             = w_stepnum
      EXCEPTIONS
        bad_priparams           = 1
        bad_xpgflags            = 2
        invalid_jobdata         = 3
        jobname_missing         = 4
        job_notex               = 5
        job_submit_failed       = 6
        lock_failed             = 7
        program_missing         = 8
        prog_abap_and_extpg_set = 9
        OTHERS                  = 10.
    IF sy-subrc EQ 0.
      CALL FUNCTION 'JOB_CLOSE'
        EXPORTING
          jobcount             = w_jobcount
          jobname              = w_jobname
          sdlstrtdt            = w_fecha
          sdlstrttm            = w_hora
        IMPORTING
          job_was_released     = w_rel
        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 EQ 0.
        IF w_rel EQ 'X'.
          WRITE:/ w_jobname, 'FUE LIBERADO. VER SM37.'.
        Guardamos los destinatarios
          PERFORM destinatarios_job.
        Guardamos la información a utilizar al ejecutar el job
          PERFORM guardar_datos_job.
        ELSE.
          WRITE:/ w_jobname, 'NO FUE LIBERADO'.
        ENDIF.
      ELSE.
        WRITE:/ w_jobname, 'NO FUE CERRADO'.
      ENDIF.
    ELSE.
      WRITE:/ w_jobname, 'NO FUE ENVIADO'.
    ENDIF.
ELSE.
    WRITE:/ w_jobname, 'NO FUE CREADO'.
ENDIF.
ENDFORM.                    " generar_job

Trigger a background job immediately after a file is placed in App Server

Hi all,
I have a program ZPGM1 that needs to be executed in background when a file is placed in an application server.
I know i can schedule ZPGM1 to trigger in background after an event say ZEVENT1.
Also i know i raise the event ZEVENT1 using FM BP_EVENT_RAISE but my problem is who would raise the event.
The file is being dropped in application server at random time by 3 party vendor. I need to execute my ZPGM1 immediately after the file is placed in Application Server.
Is ther a way that this can be achieved. Let me know
Thanks
Kajol

You will need to develop a custom, non-SAP "listener" program or a script. This program/script will need to check if the file is present (e.g. by using an OS-level event) and, if so, start SAPEVT.EXE program with corresponding parameters.
SAP Help on raising events externally:
http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e6b543b11d1898e0000e8322d00/frameset.htm
There is also third-party software available, but it is very expensive:
http://www.redwood.com/

Tcode to trigger a background job

Hi,
Can we create a tcode which triggers a background job?
Ezhil.

My User asked for a custom tcode for VF01 which use the copy control from the order and delivery and not allow any manual changes as it is done when the invoice is created in the background.
So he wants a t code trigger the creation of billing in the background.
The most critical requirement is to prevent the user from overriding or changing pricing conditions.
My question is
Is it possible to create a tcode which trigger the background creation?
What shall i tell user?
Ezhil

Thru MEB4 the Tax amount and Tax percenatage not trigger in Background Job

Hi,
          When I am executing the T.Code- MEB4 (Rebate Settlement) thru Foreground the Vendor Rebate Amount and Tax are showing.
                                  When I am executing in Background job the Tax amount and Tax Percentage are not triggering (Only the Rebate amount only showing) after execution of Background job in when viewing the job display.
                   Background Job Name: RWMBON01.
   Please suggest.

Shankar,
Thanks for reply.
If I don't put amount in the basic data tab( MIRO) then it does not allow to "simulate" or "Post". But here I can simulate and Post
I check every thing in WHT Config but I could't found the solution.
I want to tell another thing, we recently went to patch upgrade from Version 4.7 E SP 22   to 4.7 E SP30.
My question, Is the pacth upgrade affects in anyway???
If any suitable answer appreciatable.
Thanks once again for your reply.

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

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

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 SM36 and create a Background job, then create another job then press Start condition, 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 TAB called STEP, 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

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

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.

Background job not executing... pls help

I want to schedule and execute a batch job with the start date and time with another program.
In program1 im doing the below.
job_open
 getting job_count
CALL FUNCTION 'GET_PRINT_PARAMETERS'
 EXPORTING
 no_dialog = abap_true
 IMPORTING
 out_parameters = ls_params
 valid = lv_valid
 EXCEPTIONS
 archive_info_not_found = 1
 invalid_print_params = 2
 invalid_archive_params = 3
 OTHERS = 4.
SUBMIT (c_test) VIA JOB lv_jobname
 NUMBER lv_jobcount
 TO SAP-SPOOL WITHOUT SPOOL DYNPRO
 SPOOL PARAMETERS ls_params
 AND RETURN.
CALL FUNCTION 'JOB_CLOSE'
 EXPORTING
 JOBCOUNT = lv_jobcount
 JOBNAME = lv_jobname
 LASTSTRTDT = p_sdate
 LASTSTRTTM = p_stime
 targetserver = lv_targetserver
 EXCEPTIONS
 CANT_START_IMMEDIATE = 1
 INVALID_STARTDATE = 2
 JOBNAME_MISSING = 3
 JOB_CLOSE_FAILED = 4
 JOB_NOSTEPS = 5
 JOB_NOTEX = 6
 LOCK_FAILED = 7
 INVALID_TARGET = 8
 OTHERS = 9.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
in the job_closei gave start date and time, but the job is getting scheduled but not to released/cancelled status.
I want the job to happen at that given time and date,
is there anything im missing,
pls help

Rajan,
In the same documentation it says : Note: if a user does not have the authorization to release a job, then the job is scheduled with the status planned.
Now after i run this program , and check SM37, the status is scheduled. so this tells not an authorization issue.
Also i can go and schedule on a given time from SM36.
Now after reading that i also passed the parameter JOB_WAS_RELEASED importing it is geting blank value.
but documentation says, it shud be X if Job is released.
any idea pls....
Niraja

Error in Background Jobs After Client Copy

Hi,
We had performed a system refresh from a production client(with client no 300) to a quality server (client no: 200). The post processing steps were performed ok. Later the client 300 on the quality server was dropped. However, the scheduled user jobs in the background on client 200 still refer to the original client 300 and abort.
Is there any way of modifying there jobs(there are lots of them) so that the client(300 in this case) reference is modified to the existing client 200.
Points will be rewarded for good answer.
Thanks and Regards,
Subodh

Hi
The reason for the jobs getting cancelled could be that they are
client dependent jobs and inoder to resolve the issue, please
reschedule the jobs in client 200 and check whether the job fails.
Please let me know if all the jobs are failing or the issue is only
with the client dependent jobs.
Hope this information helps. Please get back to me if further
assistance is required. I would be glad to assist you.
venkat

How to submit a program after completion of a background job

Hi Experts,
I have a small issue. In my report program i am calling one transaction using call transaction it will trigger a background job. After completion of this background job i need to submit another program, Because the background job updating few values, using this value only the second program functionality will works.
Currently when i execute my report its calling 1st program and triggering the background job. Once the job started again the program triggering the next program. Here after competion of the background job only this program should submit next program. Anyone kindly suggest some clue.
    CALL TRANSACTION 'ZSAPRCK60' USING    zbdcdata
                            OPTIONS FROM g_s_options
                            MESSAGES INTO msg_tab.
SUBMIT SAPRCK10    VIA SELECTION-SCREEN
                    WITH kalaid = p-kalaid
                    WITH kaladat = sy-datum
                    WITH PARALLEL = 'X'
                    WITH SERVNUM = '10'
                    WITH backgr = 'X'
                    AND RETURN.
Mohana

Hi,
There is one function module there which gives you the job status .. if the job is finished then the value will be 'F'.I don't exactly remember the FM but then you can search with BDLSTATUS or BDSTATUS in SE37..
do.
call fm BD****STATUS
IF STATUS (IMPORT PARAMTER) eq 'F'.
exit.
endif.
enddo.
Regards,
Nagaraj

Trigger a background job after executing tcode MMPV

Similar Messages

Maybe you are looking for