Background job is in on hold

Dear sir,
i am facing problem in background job.
we have scheduled MRP run in background.
Background job is in "on Hold " and status "ARFC". The job is running in "Active" mode for 11 hours.
please give me the suggestions with your experience
regards
Ramesh

Hi,
Refer this
Background work process On-hold
Regards,
Ravi

Similar Messages

MRP background job - on hold - ARFC

hi
Off late, the MRP background job scheduled weekly is taking a very long time. more than 4 hours and when i check the status in SM50, it shows the job shows status ON HOLD and reason as ARFC.
In SM66 , i can see the job is STOPPED.
But after a long interval it gets running and the job gets completed after several hours.
Can anyone please help me on this.
Thanks and Regards
Joe

Hi Joe,
Since this job is a weekly job. It's might be the case that the job is processing lot of data. Can you check the job logs in the SM37, exactly what is the error message you are getting.
The probable solution can be restricting the selection to finish the job in very less time.
Rgds,
Ashish

Background job - on hold

Hi
Can I put a background job 'on hold' ? how ? A particular job is utilizing more work processes.
Thanks
Rajesh.

Hi,
If the job is running, you can not really "pauze" it...if you have access you could "debug" its like pushing the pauze...
A job normally only takes 1 process, but it could be using dialogs also ... So i really need to know a bit more about the problem before I can give more advice.;
Rgds
Nico

Background Job Processing Spool Retention period

Hi ,
In my program i am calling another ABAP program and sumitting the same as a background job(using Job_Submit,Close etc.)
In this case i can view the Spool generated by the called program(using sm37).
But this spool exists for a very less period in the system.Is it possible to specify a retention period,as 90 days in my case.?
Pls Help !!!
Answers will be rewarded.
Regards,
Rohan

hi Roahn,
You must set print parameters before the printing process starts.
When printing lists after creating them, the system uses the print format specified in the print parameters to split the completed list and fit it onto the print pages, truncating it if necessary.
When printing lists while creating them, the system uses the print format to actually format the list in the program.
Print parameters are set either interactively by the user or from within the program.
For each print process, the spool system needs a complete and consistent set of print parameters. In ABAP, the structure PRI_PARAMS (ABAP Dictionary) represent a set of print parameters.
When passing the print parameters interactively, the system displays a dialog box after starting the report, on which the user has to enter the most important print parameters.
It's shown below which input field of the Print List Output dialog window conform to which PRI_PARAMS component.
Input field----
Retention period
Component-------PEXPI
Meaning----
Number of days for which the system holds the spool request before deleting it. (Default value: 8).

Background job executed as SAP*, need advice to change owner.

Hi all,
I'm facing an issue where my SAP background job currently has 2 job "SAP_CCMS_CPH_REORG" and "SAP_CCMS_CPH_HRCOLL" under the ownership of sap. I would like to move them away from SAP ID.
I have tried to recreate the job using sm36 (and using my ID with sap_all profile) in testing environment, but it not seem to work.
Highly appreciates any advices and/or pointers with regards to the above mention question.
Thank you.

Hi all,
Thank you for the reply but I have forgotten to add a few updates.
The issue is that I can change owner from SAP* to my ID with sap_all profile.
But, after execution,
Job with sap* owner ended successfully, with spool status marked as completed.
whereas
Job with my ID as owner ended successfully, but spool status marked as "waiting"
error mesage:
Description          Value
Status:              Frontend unavailable
Last event:
Message:             Request on hold
Date:                19.02.2009
Time:                11:57:28
Job status:          On hold
Error class:         Delayed
Area:                Data transfer
Printout:            Not printed
Apologies for the inconveniences caused.

Background job issue

The background job - SAP_COLLECTOR_FOR_NONE_R3_STAT is taking too long to complete.
It is stuck with -
Reason - RFC
Status - On-hold
Double clicking on the work process I see this -
Waiting f.
Gateway A92SV093XI034
Report / Spool action
CL_SLD_ACCESSOR===============CP
On the SAP system of server A92SV093XI034, rdisp/max_gateways = 500 and the SLD is running fine.
So, could you please tell me the cause of the work process being stuck?

Jobs been running for last 2 days, so no errors.
I cancelled the jobs now.
Also, I checked the SAPSLDAPI RFC and it is not connecting to the SLD.
So, mostly a problem with SLD connection.
I checked everything as per the Link -
http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm
Just can't figure out what's wrong

Why is the job putting itself on hold?

Hi All
I have a program connecting to and reading from a remote ftp server. If I run the program manually in forground or background everything is fine and completes within seconds. If I set up a job in SM36 the job put itself on hold with RFC as reason and runs for hours without doing much. Any ideas how to solve this??
Regards
Marius

Hi Marius,
As usual I suspect you might get better answers if you describe in more detail what you're actually doing. I haven't encountered the problem you're describing yet, so I can only give some very generic (probably useless) comments.
I'm assuming that you're using standard SAP functionality for the ftp with RFC destination SAPFTPA; should you be using RFC destination SAPFTP (which I'd assume should fail in background and not hang) switch to SAPFTP. When using SAPFTPA you can try enabling the RFC trace in the destination and check if that gives any insights. Furthermore it might be helpful to read through [OSS note 93042 - Problems with SAPFTP|https://service.sap.com/sap/support/notes/93042].
Also, not sure if still applicable, but [OSS note 354464 - Problems with saphttp and sapftp on the frontend|https://service.sap.com/sap/support/notes/354464] is an interesting read as it explains how sapftp works when using the frontend (so probably not helping with your problem, but might give you some additional insight).
Cheers, harald

BackGround Job's Spool Request is having "Waiting" "Frontend unavailable"

Hello Friends,
I am facing one problem related to Spool Request, which is generated through Scheduled Background Jobs (scheduled by funcional people).
The Background Job is having status "completed" when analyzing it. But, its associated Spool Request is showing "waiting" Status, with "Frontend unavailable" as Status Text.
Here is the brief status of that Spool Request.
28448     1      300 USER1 00:00 LP01 X_65_80      Frontend unavailable
in Detail:
Description          Value
Status:              Frontend unavailable
Last event:
Message:             Request on hold
Date:                01.07.2009
Time:                00:00:27
Job status:          On hold
Error class:         Delayed
Area:                Data transfer
Printout:            Not printed
The Setting of LP01 O/Device is as followed:
Output Device        LP01
Device Type        SWIN SWIN : Windows printing via SAPlpd
Device Class      Standard Printer
Host Spool Access Method       F F: Printing on Front End Computer
Host printer                     __DEFAULT
Moreover, the SAP User USER1 is allocated LP01 as Output Device with "Output Immediately" & "Delete After Output" checked status.
Some Background Jobs are showing the same status for this LP01.
I have a doubt on allocated O/P Device LP01.
Any Clue for this issue ?
Regards,
Bhavik G. Shroff

Hello Markus,
Here , in our Landscape , there is not Print Server. All are taking prints through, Networked Printer and their local connected Printers.
Can i configure "send to SAP Spooler for now" instead of "Print Immediately "in the Print Specification of those Background Jobs ?
Moreover, Some Background jobs are sending E-Mails with the processed Reports as an Attachments. They are showing sometime unexpected behavior, in sending emails, although there is no relation is with this Printing related issue.
When i am looking into "Overview of Send Orders" of SCOT, some Background Jobs are showing success for sending emails, and some are not showing success, even though All the recipients are same for the scheduled Background Jobs which are running on same time.
Regards,
Bhavik G. Shroff

Urgent : Want to know table stores spools created by a background job

Actually background job executed by me creates 2 spool requests
table - tbtcpv holds only the 1 spool
Can any one tell me the table which stores all the spool created by the background job ?
Need urgent help.....

Guru,
Try with below tables
TBTCO
TBTCO
TBTCP
TBTCR
TBTCS
TBTCJSTEP
TBTCO
TBTCP
Pls. reward if useful..

Mass Delete Background Jobs in RAR

We frequently run out of file space on our Dev box of RAR. The reason being that we have close to 1500 background jobs out there created/ran by multiple users. I know that we can select each and every row and with the Ctrl+ key.. delete them simultaneously. Is there a better way to delete the jobs from within RAR ?

Hi,
To delete multiple jobs in RAR, Search the jobs based on last run date and from the list of the jobs, press the Ctrl key + select the row. By holding the ctrl key pressed you can select multiple row of entries (jobs scheduled) and then can click on the delete button to delete them simultaneously.
Hope this helps!!
Regards,
Raghu

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

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

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

Scheduling one background job inside another

Hi All,
Is it possible to Scheduling one background job inside another.? i.e In my Z program I am calling job_open, job_submit, job_close and to execute one standard report in background. And after that I am executing my Z program itself from SE38 as Program->Execute->Background->Execute Immediately. Is this logically correct? I am asking this because I am not getting the desired result
Thanks & Regards,
Neethu.

HI,
Check the job steps in SM36.
First schedule the Standard job and in the job steps schedule the z report.
Schedule job in chain

Background Job pass value

Hi, I am calling a Background job in my program. I am using JOB_OPEN, JOB_SUBMIT and JOB_CLOSE FM to start a job. My need is to pass a value to the job program(job program doesnt have any selection screen values). Is their any way without creating variants each time to pass value to it.
Please advice.....

Hello,
You can first use JOB_OPEN which returns job number. Then build ranges or parameters to use SUBMIT to call the program.
Eg: SUBMIT RM06BB20 AND RETURN
      WITH S_EKGRP IN R_EKGRP
      WITH S_EKORG IN R_EKORG
      WITH S_FLIEF IN R_FLIEF
      WITH S_KONNR IN R_KONNR
      USER sy-uname VIA JOB w_jobname
      NUMBER w_job_number.
Now use JOB_CLOSE.
Thanks,
Venu

How can i get Background Jobs list which is made me?

I created background job using JOB_OPEN and SUBMIT and JOB_CLOSE.
I need to Background Job list which is made me..
Do u know any function or logic?
plz~

[BP_JOBVARIANT_OVERVIEW|http://help.sap.com/saphelp_45b/helpdata/en/fa/096ccb543b11d1898e0000e8322d00/frameset.htm]
BP_JOBLOG_READ

Submit RSEOUT00 as background job

Hi all,
Here is my requirement.There is a Z program from which RSEOUT00 program has to be called , so that it will change the Idoc status to '03'. I tried using Submit RSEOUT00..and return and also tried JOB_open and then SUBMIT rseout00 WITH docnum EQ p_idocno user sy-uname via job jobname number jobcount and return and then JOB_CLOSE .I checked SM37 also where i can see this job as finished..
I tried COMMIT WORK statement and also WAIT statement .
But still the idoc status wont change to '03' .
Can anyone plase advise on how to correct this .
Regards,
Sudheer

Hi,
I have created background job for RSEOUT00 and written the below code. It worked.
DATA: w_number           TYPE tbtcjob-jobcount,
           w_name              TYPE tbtcjob-jobname VALUE 'ZTEST_JOB'.
   CALL FUNCTION 'JOB_OPEN'
     EXPORTING
       jobname          = w_name
     IMPORTING
       jobcount         = w_number
     EXCEPTIONS
       cant_create_job = 1
       invalid_job_data = 2
       jobname_missing = 3
       OTHERS           = 4.
   IF sy-subrc = 0.
     SUBMIT rseout00 VIA JOB w_name NUMBER w_number AND RETURN.
     IF sy-subrc = 0.
       CALL FUNCTION 'JOB_CLOSE'
         EXPORTING
           jobcount             = w_number
           jobname              = w_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.
Thanks,
Appanaboina

Background job is in on hold

Similar Messages

Maybe you are looking for