Background job Problem

Hi,
I scheduled a Program for background job running for every 10 minutes.
When i go to SM37 I am seeing all the background jobs, it is creating a newline for every 10 min in the list.
my problem is , Is there any settings to change for showing only one job that means over writing the old job and show the latest job.
Thanks in advance,
fractal

Assuming that intention is to monitor jobs that are either failed or active, you can deselect rest of the radio buttons at the selection screen so as to see failed / active jobs.
Other than this, I dont think there is any solution / way to do this.

Similar Messages

CUP: Email Reminder background job problem

Hi All,
I have been experiencing a problem in CUP for Email Reminder background job. The job is always in "BUSY" status. It is not in "Available" status as others! Can somebody help me on this?
Regards,
Faisal

Hi!
Don't worry Faisal,
We have the same problem, but with escalation job. The message was opened in the 19th of May this year, but it's still in process. At the begining consultants suggested us to upgrade our system with the latest SP, but it doesn't work. We are on the latest SP with all patches but the problem persists. Of cource, we met all requirements for job planning, and performance suggested by different SAP specialist - nothing is changed.
I think it would be better if you write the message directly to SAP hotline. You are not alone
Regards,
Artem

ALV background job problem

Hello gurus,
Kindly help me in resolving this back ground job problem.
We have a program which gives a tabstrip alv output. they are calling subscreens for this and using containers for alv.
its running good in foreground but going dump in back ground execution.
i have used the code written in forums,
data: or_doc type ref to cl_gui_docking_container .
if cl_gui_alv_grid=>offline( ) is initial.
    create object or_custom_container
           exporting container_name = c_container.
create object or_grid
         exporting i_parent = or_custom_container.
else .
create object or_grid
         exporting i_parent = or_doc .
endif .
now the error is ''set screen not allowed in subscreens.''
Could you tell me wats the problem
regards
rajesh

Hi Sandeep,
Change the 1st statement of your program
REPORT ZALV LINE-SIZE 300.
Specify output device as LOCL or LP01 with format as X_65_255 for 255 character width of output.
If width of ALV output is more than 255 say 325, then create a format in SPAD as X_65_325 & assign the same to ALV.
Best regards,
Prashant

Error in Mass process chain DP background job for Deinitialize version

Hi,
When I execute the process chain for DP background job to delete the planning area version, it gives error message
"Process DP Background Processing, variant DELETE XXXXXXX has status Ended with errors (instance D973YTQRSF0FRPV5TCR28L"
It is working well, when I tried the same manually with the same input parameters used in background job variant.
What could be the cause for the background job problem.
Thanks and regards
Murugesan

Hi Datta,
I am not deleting the planning version, I am using Macro in the DP background job to delete or make the key figure values to 0.
Thanks and regards
Murugesan

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.

Problems with background job

Hi,
I have problems when creating a job that is supposed to be run once in background. I use the common steps as described below. My problem is that the report is executed twice.
- First it is executed synchronously when the job is created
- Then it is executed in the normal job step as I want it to do
I don't want it to be executed the first time because it creates data!!!
Code:
CALL FUNCTION 'JOB_OPEN'
     EXPORTING
          jobname = w_jobid
     IMPORTING
          jobcount = w_jobnr
          sdlstrtdt = sy-datum
          sdlstrttm = sy-uzeit.
SUBMIT (p_prog)
WITH p_idocnr = p_idocno
           USER            p_user
           VIA   JOB       w_jobid
                 NUMBER w_jobnr
                 AND       RETURN.
CALL FUNCTION 'JOB_CLOSE'
     EXPORTING
          jobcount         = w_jobnr
          jobname          = w_jobid
          strtimmed        = 'X'
     IMPORTING
          job_was_released = w_jobrel.
Does anyone have a clue of what I should do to prevent this?
// Regards Hans

Hi again,
1. U are right.
2. It will happen if we use SUBMIT.
3. As per the help documentation,
    it will run the program in separate session,
   ( as soon as submit statement comes)
4. and run the INITIALIZATION event.
The VIA JOB addition also loads the program accessed in a separate internal mode when the SUBMIT statement is executed and the system performs all the steps specified before START-OF-SELECTION. This means the events LOAD-OF-PROGRAM and INITIALIZATION are triggered and selection screen processing is performed. If the selection screen is not processed in the background when VIA SELECTION-SCREEN is specified, the user of the calling program can eidit it and schedule the program accessed in the background request using the function Place in Job. If the user cancels selection screen processing, the program is not scheduled in the background job. In both cases, execution of the program executed is completed after selection screen processing and the system returns to the calling program due to the AND RETURN statement.
regards,
amit m.

Problem with background job using SUBMIT under different user

Hi All,
I am submitting a background job under different user name. I am submitting this job by using JOB_OPEN , SUBMIT report and JOB_CLOSE. But submit statement is returning sy-subrc 8, becuase of this the job_close is failed. Can you please help me to solve this problem.
Thanks in advance.
Tjgupta

Hi,
The user is having all authorizations. is there any difference with user types?
This user is having user type " as communication data".
Thanks,
Tjgupta

Problem related to Outbound Delivery creation via Background Job

Hi ,
We are using the program RVV50R10C for creating OBD incase of STO .
Z variant is created to take care of selection parameters which inlcudes Shipping Point , Delivery creation date , Calc Rule, Delivery priority and shipping conditions.
The job is scheduled to run for every 10 minutes .
As planned the job is running for every 10 minutes but the OBD are created after 1 hour .
What are possible causes of this error.?
Please note that there exists enough stock.
Regards
Ramesh Ch

I think you will have the same problem when doing it manually with VL10B.
The creation is based on entries in an index. there is a userexit where you can influence how and when an entry goes into the index. E.g. you can speed up the overall performance if you do not update the index all the time, instead you are doing this with a background job from time to time.
Check if this is the case in your system.
this note may give you some hints:
Note 356061 - Incorrect index compilation caused by own checks

Background job scheduling problem in APO

Hi fellow SDNers,
i am going through this peculiar problem of background job scheduling:
scenario is like , i have an CSV (excel file) in aplication server which would load data into the infosource, which i have scheduled to run in backhround (in infopackage) ,after event is triggered (option in scheduling tab of infopackage...THE SCHEDULING OPTIONS)
now everything seems to be fine.. but the data is not getting loaded...?? could u lease help me out..how to load data from excel file (in background), after an event gets triggered.
thanks in advance,
Rohan

hi Alexander,
i am triggering the event from BP_EVENT_RAISE FM in APO by passing the event id... this would automaitically raise the event...just like sm64
Thanks
Rohan

Problem in Background Job. Job Completed Successfully but data not Posted

Hi All,
There is a problem in Background Job in Production server (600).
The job completed successfully but data not posted.
The same Job was working perfectly till the starting of the May month.
but now it is not working and rebate has not been posted.
Where to check and what to check
Pls suggest.
Regards,
P Kamal

Hi ,
Please first check the status of the Job , ifs successfully completed then debug it (tcode JDBG) and
check out, whether the values passed (might be using Import-export ,set-get parameter Ids) to the Job are getting passed properly or not. These values might not be getting passed properly.
If it has some error in Job Log then let me know the error.
Regards,
Uma

Background job in Released status and does not run. What is the problem?

Hi Experts,
I ran a ABAP report as a background job. But when I see the job status in SM37 I found that it is "Released" but the job does not run further, It remains in "Released" state. I have given the correct variant and start condition "immediate" . Moreover there is no spool and log as well.
The ABAP report runs fine in forground. It used to run in background few days back.
What could be the problem? Kindly help!
Thanks
Gopal

Hi Bob,
But I checked after 2 days still the job status is in Released state. There were some other jobs that ran successfully. So atleast after two days I hope the job should have run. I can't even delete it. What shall I do?
Thanks
Gopal

Problem in Background Job Scheduling in GRC 5.3

Dear All,
I am configuring GRC RAR 5.3 SP11. While scheduling background jobs, only one job is running at a time. If I am scheduling Management report for one client of system (XYZCLNT300) and another job for User, Role and Profile synchronization- Full Sync for other client of the same system (XYZCLNT400).
So, only one job is running at one time and other job remains in Ready state. I have done following Config in GRC System:
1) GRC system has 2 server nodes.
2) Each Server node has 3 background job workers and 5 web service workers.
While Running 2 job at sametime, one is in Running status and other is in Ready Status. But that time only 2 background job workers are occupied one from each node while others are in IDLE state.
I am wondering if I have free background job workers then why other job is in Ready Status. Is there nay parameter that needs to be changed to run multiple background jobs in parallel ?
Please suggest.
Thanks
Sunny

Hi,
As per SAP Note 1371501 - Multiple Batch Risk Analysis at a time, we cannot run multiple batch risk analysis at a time.
Batch Risk analysis will run only on server0 node.
Thanks
Sunny

File path problem in background job spool

Hello ,
i have probelm in file path of the background job in spool.
i have selection screen
Radiobutton : p_local
parameter: path1.
Radibutton: p_applicatioserver
parameter: path2.
if i keep program in background job, it will alwas take second option.
Now user selected first option and executed job in abckground. File stored in the spplication server with corect file path name. (path2)
But when i go to sm37 entered job name and checked the spool, it gives me the file path name path1. but i need the file path1 in the background spool. my question whether i need to change the file path name in program or whether i have to change the setting
Regards,
zub

First of all, local is not an option in background job; you can only save to the apps server, and your program should take that into consideration by checking for sy-batch = 'X', for example. You should be checking in your at selection-screen to be sure the user has not chosen local path and file and background job.

Problem in getting spool number of a background job.

Hi all,
In a Z program I am calling a standard program to run as background job. I need to get the report o/p of the standard program. For this I need the spool no of the background job. Now I am querying on table tbtcp by giving jobname. Program name and run date and getting the spool no. but the cache is that the table is not getting updated with the spool no as soon as the job finishes. It is taking some time to update the table ( The time depends on the no of background jobs scheduled. ). So of we query on the table immediately after the background job finishes we are getting spool no as 0. so I am unable to read the spool into Internal tables. Even the table tsp01 is also behaving in the same way. ( it is taking time to update ) .
Any pointers to this will be appreciated .
Regards,
Shiva....

This is some prototype that I put together from separate pieces, so it looks funky, but might be helpful. The first step is to SUBMIT the program with EXPORTING LIST TO MEMORY. The next FM reads the list from memory and the next one (optional) converts it to a text format. You might want to search for other FMs in SE37 by 'LIST*'.
DATA list_tab TYPE TABLE OF abaplist.
SUBMIT RPR_TRIP_HEADER_DATA
USING SELECTION-SET 'OLD_LIST'
EXPORTING LIST TO MEMORY
              AND RETURN.
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
    listobject = list_tab
EXCEPTIONS
    not_found = 1
    OTHERS     = 2.
types : t_txt(1000) type c.
DATA: i_txt2 type table of t_txt,
i_txt type list_string_table.
call function 'LIST_TO_ASCI'
EXPORTING
*   LIST_INDEX               = -1
   WITH_LINE_BREAK          = 'X'
IMPORTING
   LIST_STRING_ASCII        = i_txt
*   LIST_DYN_ASCII           =
TABLES
   LISTASCI                 = i_txt2
   LISTOBJECT               = list_tab
EXCEPTIONS
   EMPTY_LIST               = 1
   LIST_INDEX_INVALID       = 2
   OTHERS                   = 3
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
Also check this links:
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/spool-number-of-previously-printed-abap-list-635173#

Background job- getting printed automatically

In my BDC Program i have submitted Session for Background Processing using
Submit RSBDCSUB..........
my code is also given below..The problem is after the user executes the program, background job is automatically going to his Local printer and getting printed. HOw to avoid this?
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
            jobname          = gf_jobname
       IMPORTING
            jobcount         = gf_jobcount
       EXCEPTIONS
            cant_create_job = 1
            invalid_job_data = 2
            jobname_missing = 3
            OTHERS           = 4.
*-Submit the selected sales orders for changes.
SUBMIT rsbdcsub AND RETURN
         WITH mappe = v_sess
         WITH von = sy-datum
         WITH bis = sy-datum
         WITH z_verarb = 'X'
         WITH fehler = space
         WITH batchsys = space
         WITH logall = space
         USER sy-uname VIA JOB gf_jobname NUMBER gf_jobcount.
IF sy-subrc NE 0.
    MESSAGE i999 WITH text-013.
    EXIT.
ENDIF.
*-Close job and start immediately.
CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
            jobcount             = gf_jobcount
            jobname              = gf_jobname
            strtimmed            = 'X'
       IMPORTING
            job_was_released     = gf_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.

On SUBMIT use
SUBMIT zxxxxxx TO SAP-SPOOL
                    WITHOUT SPOOL DYNPRO
                    IMMEDIATELY ' '
                    KEEP IN SPOOL 'X'
                    DESTINATION printer
                     NUMBER number
                    AND RETURN

Background job Problem

Similar Messages

Maybe you are looking for