Regarding Background Jobs

Hi Basis Gurus,
  I have a small doubt regarding Background jobs.
   Can we       edit    a job which is in the        Scheduled     status. .
If that can be done , i am unable to edit a job . When i am trying to edit the job
the  message i am getting is --- 
" Definition of job Z_MM_MMPV is incomplete. Operation is not
    possible "
Please  guide me how i can resolve this issue,
Thanks in Advance,
Vikram krishna.

Hi Vikram,
Yes, this is possible.
Goto SM37 and display the Job, then select the job and from the menu: Job->Change, and click on Steps. Again select the Job and click on the change button to change whatever you want.
Hope this helps.
Thanks,
Srinivasa

Similar Messages

  • Regarding Background Job scheduling for file to file scenario

    Hi Guru's
    Good morining all of u
    I have one doubt on ...
    can we do background job scheduling for file to file scenario?
    Please give me response as early as possible.
    thanks and regards
    sai

    background jobscheduling for file adapter...
    you can schedule the file adapter according to your requirement as follows:
    In the  Communication Channel Monitoring Locate the link Availability Time Planning,  In Availability Time Planning, choose the Availability time as daily and say create, give the time details, select the communication channel in your case file adapter , goto the Communication Channels tab and filter and add the respective channel, save it
    /people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-

  • Regarding background job.

    Hi All,
    I have to debug background job which is currently running.
    I know how to get the job in debug mode, that is through SM51 transaction...But once i m done with seeing some values in debug mode. I need to put this job back again in the background. Becasue since this is long running job i can not run it in forground.
    Plase guide me in this regards.
    -Sanjay

    Hi,
    You can debug batch jobs by going to 'SM37', type in 'JDBG' in the
    command line ( no '/' ), put the cursor on the job and press enter - will
    take you to the job in debug mode.
    You can do this only after the job has finished execution. This will simulate the exact background scenario with the same selection screen values as used in the job also sy-batch will set to 'X'.
    So type in the transaction code 'JDBG' and place your cursor on the job after It has finished. It will take you to a SAP program in debug mode. Step through this program which is about 10 lines, after this your program will be executed in the debug mode.
    Steps
    1. Create variant called BACKGROUND for program to be debugged.
    2. Execute ZDEBUGBG (pgm code below) in background for immediate processing.
    3. Execute transaction SM50.
    4. Select process that runs ZDEBUGBG.
    5. Goto 'Program/Session' 'Program' 'Debugging'.
    A se80 debug session will open.
    6. Change variable W_EXIT to 'E'.
    7. Step thru (F6) until ZWBTEST comes up.
    1. Go to Transaction SM66 and find your work porocess.
    Select the line work process is on and click on the Debugging button.
    If this is a custom program, you can put a wait statement in the code to buy yourself sometime.
    2. Go to Transaction SM50. From the tool bar "Program/session"->Program->Debugging.
    goto SM37 and from Program menu(not sure.. try other menu's)
    -->Catchjob . it will goto the active job in debugging mode.
    Regards,
    Raj.

  • Doubt regarding background job?

    Hi,
         I am working on IW32 transaction.
    iam going store Sys stataus SETC orders in one internal table then i need to schedule back ground job for orders complete by below procedure i.e <b>Go to Orders-Functions-complete----complete bussiness.</b>.
    Is there any automate procedure to do the same? or we can switch to recording for the that?
    URGENT...
    Regards
    Message was edited by:
            shiva kumar

    Hi shiva,
    I'm afraid I haven't worked at all with this transaction. But maybe I can give you some hints.
    My question is: when you access this menu "Goto > Orders > Functions > complete > complete business", is this creating a background job? If so, you have won the first prize? Because you can go to transaction SM37, display the jobs you have created, and then keep track of the report and the variant that SAP used to schedule this job. Finally, you may enter transaction SM36 to create a new repeating job using <b>exactly</b> the same report name and variant.
    I hope this helps. Best regards,
    Alvaro

  • Query regarding Background Jobs

    I have 3 Application servers + Central instance.
    After a background job has been completed/cancelled, how do I determine on which App Server it was executed?
    Also, Waht does the big Button 'Application Server' display. I am guessing list of all available servers, right?
    Thanks in advance.

    Hello Gautam,
    You can  follow the approach suggested by Santosh. However this approach can be used for only one job at a time. If you want to do it simultanoeusly for several jobs then you can follow the below process:
    1. In SM37 give the selection criterion for the desired  job output and execute.
    2. Now you will have a complete list of the desired jobs.
    3. In the application menu bar you will fiind an icon for Define output fields(normally this icon is reserved for variants). Click on the icon. If you are  not able to find the icon you can also use CTEL+F7.You will get a popup.
    4. In this pop up there will be 2 columns. On the left hand side will be the fields which are already being shown in SM37. On right side you will find the hidden fields like: Progress, Executing server etc.
    5. Select executing server and click the single arrow icon (in the middle) pointing towards left side. Press COPY button and now see the result.
    Regards.
    Ruchit.

  • Regarding Background Job Abort using

    Hi ,
    I am using FM BP_JOB_ABORT to abort background jobs through program,but it taking longtime to cancel background jobs in SM37 after exectuing FM BP_JOB_ABORT in program..
    will i have to write  any statement in program after this  FM BP_JOB_ABORT to cancel the background job immediately through program..
    Awaiting for valuable suggestion..
    Regards
    Anil

    Hi,
    I looking for FM to cancel background jobs quikly through program..
    Regards
    Anil

  • Regarding Background job vs Performance.

    Hi all,
      I ran 2 similar programs in background through SE30 for comparing the performance.In SM37 the Duration(sec.) for the 2nd program is 3 times less than the first program after execution.But runtime analysis shows the performance of the first program is better than the second program by 1.5 times. Why is this difference!
      My question here is, can we consider the time duration shown in SM37 for performance comparison? Why do we get different results in SM37 and SE30?
    What factors affect the background process?
    Please clarrify.
    Regards,
    Venkatesh Kumar S.

    Hi Venkatesh!
    You have overflows. The total in SE30 is just 0.3 sec and 0.4 sec - but in SM37 3086 and 1112 seconds. After a conversion into microseconds, you would have 3 086 000 000 - which is obviously to much.
    For such long times, you can only look on the SM37 times - if you like to get more details, make info messages - they will be in the job log with a time stamp and you can inform about 'data read', 'data converted', 'data output' or something like this.
    Regards,
    Christian

  • Regarding Background job scheduling

    Hi,
    Please guide me how to background schedule job.There are two consecutive screens to be executed one after another-Output of  first screen being input to next  screen.
    Transaction code is BD87.First screen has date bfield.After executing selection screen list of idocs displayed.Particular idoc to be selected and executed again in bachground itself.
    Thank you.

    Hi!
    You can't scedule BD87 directly.
    You have to schedule the following programs using SM36 transaction:
    RBDAPP01 - Processing unprocessed IDocs
    RBDMANI2 - Processing again faulty IDocs
    Create variants for both of the programs, and you have to schedule them for periodical IDoc processing.
    Regards
    Tamá

  • Background job - programs all running at the same time...

    Hi experts,
    i have an issue regarding background job.i have to run multple programs in background one after another in one program.so i am using function modules job_open,submit and job_close.
    my problem all the jobs are statrting at same time .but i want to run after completion of first job second job should start.
    please guide me
    Thanks
    sai
    Edited by: Julius Bussche on Feb 19, 2009 9:36 AM
    Please use meaningfull subject titles

    Try something like
    LOOP AT it_filenames INTO ts_filenames.
      CALL FUNCTION 'JOB_OPEN'
           EXPORTING
                jobname  = jobname
           IMPORTING
                jobcount = jobcount.
      SUBMIT program
        WITH p_file1 = ts_filenames-zzfname
        VIA JOB jobname NUMBER jobcount
        AND RETURN.
      IF sy-tabix EQ 1.
        CLEAR: pred_jobcount,
               pred_jobname.
        GET TIME.
        IF sy-uzeit LT '235950'.
          sdlsstrttm = sy-uzeit + 10.
          sdlstrtdt = sy-datum.
        ELSE.
          sdlsstrttm = '000010'.
          sdlstrtdt = sy-datum + 1.
        ENDIF.
      ELSE.
        sdlsstrttm = '      '. " no_time from LBTCHTOP
        sdlstrtdt = '        '. " no_date from LBTCHTOP
      ENDIF.
      CALL FUNCTION 'JOB_CLOSE'
           EXPORTING
                jobcount             = jobcount
                jobname              = jobname
                predjob_checkstat    = ' '
                pred_jobcount        = pred_jobcount
                pred_jobname         = pred_jobname
                sdlstrtdt            = sdlstrtdt
                sdlstrttm            = sdlstrttm
           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.
      pred_jobcount = jobcount.
      pred_jobname = jobname.
    ENDLOOP.
    I removed the checkstat, cause if you want to check the status you only have to submit one job with multiple steps. (Put JOB_OPEN and JOB_CLOSE out of the loop)
    CALL FUNCTION 'JOB_OPEN'
         EXPORTING
              jobname  = jobname
         IMPORTING
              jobcount = jobcount.
    LOOP AT it_filenames INTO ts_filenames.
      SUBMIT program
        WITH p_file1 = ts_filenames-zzfname
        VIA JOB jobname NUMBER jobcount
        AND RETURN.
    ENDLOOP.
    CALL FUNCTION 'JOB_CLOSE'
         EXPORTING
              jobcount  = jobcount
              jobname   = jobname
              strtimmed = 'X'.
    Regards

  • 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

  • Regarding capturing VF01 ERROR logs in a background job

    Hi ,
    We are running a background job that calls transaction VF01 via BDC .
    CALL TRANSACTION 'VF01' USING   bdcdata
                              MODE    S
                              UPDATE  N
                              MESSAGES INTO gt_messtab.
    In some cases billing documents will not be generated. In such cases systems will throw message "Check the log "
    After which we can check the error messages via Menu Edit>logs.
    This error messages (stored in XVBFS internal table) need to captured in the job log  i.e custom programme.
    Unfortunately i could not found any user exits/BADIs that can help me in capturing message.
    Can you please help me how can i solve this issue?
    Thanks in advance
    Manoj
    Edited by: Manoj J on Nov 16, 2011 9:42 AM
    Moderator message : Duplicate post locked, continue with original thread [How to capture error logs of VF01 in a background job log   |Re: How to capture error logs of VF01 in a background job log].
    Edited by: Vinod Kumar on Nov 16, 2011 3:34 PM

    Hi Manoj,
    I had a similar problem.
    I solved it selecting from VBSK the last record of the user regarding elaboration of invoices, and then calling f.m. 'VBSK_ALV_DISPLAY'.
    Otherwise you could call directly transaction "V.21"
    Hope this could help you
    Andrea

  • Regarding the output of background job in spool

    Hi Friends:
         I have a report.When I run it in foreground, it displays an alv output.
    I want to see the output when I run it in background. When I select the job & press on spool, it shows a message that no list available. Please help with the settings to see the output in spool.
    Suitable points will be rewarded.
    Regards:
    Gaurav

    Hi,
    have a look at this thread:
    Re: OO ALV in background job
    Best regards.

  • Regarding email attachement while running a background job

    Dear Experts,
    When i am running a background job for any ALV report (standard or custom report) <b>automatically</b> the output is going to an e-mail address as a HTML file attachment. I want to change it to EXCEL file attachment.
    Please help me on this issue..
    Kind Regards,
    Tom

    Hi Prasanna,
    Thank you for your reply.  I am not using any code for sending the mail to the recipient E-mail address, system is taking care automatically.
    Few settings were done in SCOT transaction from basis, but no where they mentioned file type is .HTM.
    From my end i have done the following steps.
    1. go to SM36, give a job name.
    2. press on step push button , give the ABAP program name ( any ALV program, i mean standard report or Z report), give the variant and save.
    3. Come back . press on Spool list recipient push button give the e-mail address, press copy button on the  pop up window.
    4. press on start condition button , press on Immediate option and save.
    5. again press on Save button in the screen.
    now here job will be scheduled immediately, go to SM37 check your job status, if it is completed, automatically system is sending an e-mail with the ".HTM" attachment file output to the recipient e-mail address.
    i am not doing any coding part here.
    my concern is system should send the e-mail with ".XLS" file output attachment.
    please advise on this.
    Regards,
    Tom.

  • Regarding Variants for Background jobs

    Hi Folks
    Can you please let me know the procedure how we can create the variants for Background jobs.
    Points are assured for correct answers.
    Regards,
    kumar

    Hi Sree Ram,
    Check this info.
    If you have any selection screen parameters for your program you need to enter the values for those fields in runtime. So, if you schedule your program in background to execute then there is no one to do this job. Here comes the concept of Variant.
    With variant you define what are the selection field values in the runtime. During runtime the program picks this values and runs the program.
    When you execute your program which has selection fields, you enter the values and then you click on 'GO TO ' tab and 'SAVE AS VARIANT'.
    When you schedule your program in background, give this variant also. Then it will run automatically.
    Hope this resolves your query.
    Reward all the helpful answers.
    Regards

  • Regarding Dead line monitoring & Background Job

    Hi Dear PMs,
    plz let me know regarding Deadline Monitoring (IP30) for Maint plan. Why it is requires? only for scheduling multiple plans at a time or is their any other reason?
    What is the meaning of,
      1. Interval for Call Objects
      2. Rescheduling included
      3. Immediate start for all in IP30 screen.
    Why we need to run Back ground job? - only for scheduling open & save daily in background....or for any other reason?
    requested you to giv in detail...
    Thanks in Advance...
    Amol.

    In short, as the name suggest deadline monitoring is used to monitor deadlines so that any due activity could be done well in time. Deadline monitoring helps you to automatically schedule entries that are due within this period.  With the help of Deadline Monitoring, you could schedule multiple Maintenance Plans at the same time from the same transaction with respect to Plant maintenance. For different modules it could used for different purposes. In MM/WM, it could be used for mass changing the batch status. It is also used in Workflows. W.r.t PM, Using IP10, you are able to schedule maintenance plans individually, so to reduce time delays and increase efficiency, Deadline Monitoring is used. 
    Using F1 help on each of these fields should be helpful.
    Interval of Call Objects specify the duration for which you want to execute monitoring of due entries. For example, mentioning 1 mon here would show me all the maintenance plan due for the complete month.
    Immediate start for all: You can use this indicator to show whether the maintenance plans that correspond with the selection criteria are to be scheduled immediately, or whether a list of the selected maintenance plans is to be displayed.
    Rescheduling Inc: You can use the automatic deadline monitoring to schedule a maintenance plan again or for the first time. If you need to reschedule any maintenance plan after having scheduled it, this indicator must be checked:
    The following link might help you understand:
    http://help.sap.com/saphelp_erp60_sp/helpdata/EN/3c/abb350413911d1893d0000e8323c4f/frameset.htm
    Executing in Background helps as it does not bother you to open up the ip30 screen and then print the document. The Document is printed automatically without you having to bother about it within the period u specify behind your background job settings. It could be monthly, daily, weekly, yearly etc. etc.
    Edited by: Usman Kahoot on Apr 5, 2010 10:34 AM

Maybe you are looking for