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

Similar Messages

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

Background job ABORTED in ECC

Hi,
I am working for an upgrade project. We have a program in 4.7 which start background job using the FM: JOB_OPEN and submit7 standard programs with variant using FM: JOB_SUBMIT. Please find the program details below.
1. RMCP6FLS
2. RMCP6RES
3. RMCA9026
4. RMCP6BIN
5. RMCP6RES
6. RMCA9026
7. RMCP6BIN
After this close the job using FM: JOB_CLOSE and find the job status using the FM SHOW_JOBSTATE.
For the same variant it is working fine in 4.7 but in ECC FM SHOW_JOBSTATE aborted = 'X'.
Thanks and Regards
Joby Jacob

Please investigate yourself first, if you are still stuck, open another thread describing what you have analysed so far, providing all necessary details right away.
Thread locked.
Thomas

Trigger mail for cancelled background jobs scheduled using SM37

Dear Experts,
My requirement is to trigger email whenever a job gets cancelled in background.
For this I have already tried creating a workflow using BO BPJOB for event ABORTED.
But for some reason the event is never getting triggered.
I tested executing the workflow from tcode SWDD, it was running successfully, which means that there is no issue with my workflow.
Now I want to resolve the above issue OR
I want to raise the event manually from the program through some BADI or Exit.
But I didn't find any BADI or Exit for tcode SM37. Can anybody let me know if any.

Hi,
Please refer the below links.
Workflow- Background job fail
Re: Send mail when job fails
Regards
GK.
Moderator message: please do not post just links without any further explanations.
Edited by: Thomas Zloch on Sep 20, 2010 11:53 AM

Email multiple spools from background job - SM36 using Spool List recipient

I create a background job using Spool List Recipient to email me the reports. The program that I scheduled to run creates 2 spools. When the spools are sent via email, only the last spool is sent.
Please advise on how I can get the 2 spools sent via email.

i would not use the Spool List recipient from Job and use the function RSPO_SPOOLJOB_TO_OFFICE in your Program instead.
tell me if it helps.
Regards,
Laurent

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.

Trigger Workflow for Background Job Abort

Hi,
I want to start a workflow when a Background Job fails.
I could find the BOs BPJOB & BPJOB_SMAN and the event BPJobSchedMan.Aborted, but it is not getting triggered when a background job cancelled.
Let me know if any specific settings need to be made.
Appreciate your help. Thanks in advance.
Rgds,
Kumar

Hi,
Did you manage to get this working? i am also using BPJOB abort even but its not getting triggered.
Thanks.
Rgds,
Pankaj

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-

Create spool for background jobs which uses submit statement

Hi Gurus,
             I have a quick question regarding the backgroud jobs. When we run a program in the background , it should create a spool for us, but, the problem comes when I am running a program in the background, its not creating the spool. This program uses SUBMIT statement. This program collects the data and it will submit to the other program and then retuen. In this case, its not creating a spool. Its very important for us to look at the spool for this program. Does anybody cam across this kind of problem? I need ur inputs.
Thanks in advance, <REMOVED BY MODERATOR>
Regards,
Srinivas.
Edited by: Alvaro Tejada Galindo on Mar 18, 2008 4:31 PM

hi check this link ...
Scheduling a submitable program as a background task with the number number in a background request name. After scheduling, the background task is completed by function module JOB_CLOSE and released immediately.
DATA: number TYPE tbtcjob-jobcount,
      name TYPE tbtcjob-jobname VALUE 'JOB_TEST',
      print_parameters TYPE pri_params.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
    jobname          = name
IMPORTING
    jobcount         = number
EXCEPTIONS
    cant_create_job = 1
    invalid_job_data = 2
    jobname_missing = 3
    OTHERS           = 4.
IF sy-subrc = 0.
SUBMIT submitable TO SAP-SPOOL
                    SPOOL PARAMETERS print_parameters
                    WITHOUT SPOOL DYNPRO
                    VIA JOB name NUMBER number
                    AND RETURN.
IF sy-subrc = 0.
    CALL FUNCTION 'JOB_CLOSE'
      EXPORTING
        jobcount             = number
        jobname              = name
        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.
    ENDIF.
ENDIF.
ENDIF.
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=backgroundsubmit&adv=false&sortby=cm_rnd_rankvalue
sy-subrc Meaning
0            Background task scheduled successfully.
4            Scheduling cancelled by user on the selection screen.
8            Error during scheduling, i.e. when accessing JOB_SUBMIT internally.
12          Error in internal number assignment.
regards,
venkat.
Edited by: venkat appikonda on Mar 18, 2008 6:32 PM

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á

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

Help Required Regarding - SAP Job names using R3 data flows

We are calling a set of SAP Jobs using R3 data flows in data services. When ever a job fails we first kill the active SAP jobs by logging into SAP and then restarting the Jobs.
There are about 100 odd SAP jobs that we call using these Data services Jobs so we wanted to kill the jobs using a reusable code on the SAP side by passing the Job name just before every R3 flows just incase its still in active status.
So wanted to know if there are any short cuts to retrive the set of associated SAP job names because it will be a tedious process to hardcode the SAP job names and pass them as parameters for all the 100 + SAP job names in the custom defined resuable code.
Any help or advice on this please !!

The program is not meeting the expectations
and the problem is due to reflection.Do we know this for certain?
... my application gets the class name, field name
etc. from an XML file so i don't know their method names
beforehand .
Now since every class instance corresponds to a row
in the database and i have to call get and set
methods of each class instance so the performance
keeps on degrading as the number of columns and rows increase .
Can somebody suggest some improvement regarding this
and regarding creating multiple instances of the same object Class.forName() will be using a hash already, so there is probably not much room for improvement.
Class.newInstance() probably does not take significantly more processing than a simple "new Fubar();".
Umpteen reflective method invokations (one per column) for each row/instance - Are you saying these are the problem?
You can test this easy enough.
If you comment out the reflective method invocations and leave the rest of your code untouched,
does your application processing speed up significantly?

How to delete Background job

hi all,
i am working on ECC6.0.
i am not able to find the path to delete background job completly.
can any body give me the navigation for the same in ECC6.0
Thanks in advance

hi
hopen ths wll help
To delete a background job explicitly, use:
BP_JOB_SELECT to obtain the jobname and job number of the job that you wish to delete.
You can select jobs according to all of the criteria available in the interactive background processing management system:
Jobname: Using a well-planned naming convention for your jobs will help you to select them precisely.
Job number
Name of the user who scheduled a job
Specifications for the start-time window/no start time scheduled
Start dependent upon predecessor jobs
Start dependent upon an event and event argument
Job status (preliminary, scheduled, ready, running, finished, aborted).
BP_JOB_DELETE to delete the job. The job log is deleted as well, if the job has already been run.
A job cannot delete itself. Also, a job that is currently running cannot be deleted. However, you can have it deleted automatically if it is completed successfully. See the DELANFREP parameter of JOB_OPEN.
Sample Program: Deleting a Background Job
Data declarations: BP_JOB_SELECT
DATA JSELECT LIKE BTCSELECT.
DATA SEL_JOBLIST LIKE TBTCJOB OCCURS 100 WITH HEADER LINE.
Sample selection criteria
JSELECT-JOBNAME = 'Name of job'.
JSELECT-USERNAME = SY-UNAME.
CALL FUNCTION 'BP_JOB_SELECT'
EXPORTING
JOBSELECT_DIALOG = BTC_NO
JOBSEL_PARAM_IN = JSELECT
IMPORTING
JOBSEL_PARAM_OUT = JSELECT
TABLES
JOBSELECT_JOBLIST = SEL_JOBLIST
EXCEPTIONS NO_JOBS_FOUND = 1
SELECTION_CANCELED = 2
OTHERS = 99.
In this example, the program loops over the internal table
SEL_JOBLIST and deletes each of the jobs that was selected.
Alternative: Have the user select the job to be deleted
with BP_JOBLIST_PROCESSOR. For an example, please see
Sample Program: Wait for Predecessor Job with JOB_CLOSE.
LOOP AT SEL_JOBLIST.
CALL FUNCTION 'BP_JOB_DELETE'
EXPORTING
FORCEDMODE = 'X'
JOBNAME = SEL_JOBLIST-JOBNAME
JOBCOUNT = SEL_JOBLIST-JOBCOUNT
EXCEPTIONS
OTHERS = 99.
ENDLOOP. *
FORCEDMODE deletes the job header even if other portions of the
job cannot be deleted from the TemSe facility, where they are
held.
FORCEDMODE can be used without fear of causing problems in the
System. Any TemSe problem that affects background jobs can be
resolved directly in the TemSe system and does not require the
job header.
regards
navjot
reward if helpfull

Regarding Background Job Abort using

Similar Messages

Maybe you are looking for