DP background job version value shows to{q}ZsmfF

Hi,
I am using DP background jobs in Mass processing. The Version field in the mass processing job displays value as "toZsmfF".
I tried to change the version to 700 in transaction SAPAPO/MC8D. But the version field is disabled.
I also tried after removing the DP background job from all the process chains where ever it was used. After that also the version field, planning book,data view are not active to change (greyed -unable to change). How can change the version value in the DP background jobs.
Thanks and regards
Murugesan

This is becasue the DP job executed without initializing the planning area for the version. Created new job with differenet name and assigned with version.

Similar Messages

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

Error in TLB background job"Version does not exist"

Hi Gurus,
We are getting error of "Version does not exist " in TLB background run..The T-lane is between 2 DCs .we have checked everything but unfortunately
we are not able to detect the root cause for the error.
Your help will be appreciated.
Thanks in advance
Suyash

Hi Suyash,
I hope than your planning version is active!
I also suppose than you have maintained mean of transport and products at Tr.Lanes level.
I think that you have some master data inconsistency in the version.
Please run the reports; /SAPAPO/OM17, /SAPAPO/TSCONS, /SAPAPO/TSLCREORGSNP
You can also run Model Consistency check (t.code /SAPAPO/CONSCHK). First you have to define the Model (t.code /SAPAPO/SCC07) and the Profile (t.code /SAPAPO/CONSPRF).
Thanks, Marius

USMM report showing some Background job, which not in SAP

Sir,
I took USMM report from SAP PRD system for audit purpose. Everything is fine , expect some background job. There showing some background job finish on 01.04.2013. But I don't find any background job in SM37 which showing finish in USMM report. Please suggest what to do. Following are the background Job..
0000 Measurement Extensions Finished on 01.04.2013 at 12:55:30
0001 ABAP Workbench Finished on 01.04.2013 at 12:55:44
0002 Mobile Engine Finished on 01.04.2013 at 12:55:24
0009 Activity Checks Finished on 01.04.2013 at 12:56:55
0100 mySAP Human Resources Finished on 01.04.2013 at 12:55:26
0101 SAP HR e-recruitment Finished on 01.04.2013 at 12:55:24
0200 mySAP Banking Finished on 01.04.2013 at 12:55:25
0250 Financial Services Loan Management Finished on 01.04.2013 at 12:55:25
0300 mySAP Healthcare Finished on 01.04.2013 at 12:55:25
0400 mySAP Utilities Finished on 01.04.2013 at 12:55:26
0500 mySAP Telecommunications Finished on 01.04.2013 at 12:55:26
0600 mySAP Insurance Finished on 01.04.2013 at 12:55:26
0700 mySAP Public Sector Finished on 01.04.2013 at 12:55:26
0730 mySAP Public Sector Campus Finished on 01.04.2013 at 12:55:26
0800 mySAP Oil & Gas Finished on 01.04.2013 at 12:55:26
0900 mySAP Engineering & Construction Finished on 01.04.2013 at 12:55:27
1000 mySAP Aerospace & Defense Finished on 01.04.2013 at 12:55:28
1100 mySAP Automotive Finished on 01.04.2013 at 12:55:28
1201 SAP Financial Supply Chain Management Finished on 01.04.2013 at 12:55:26
1215 SAP FSCM Credit Management Finished on 01.04.2013 at 12:55:27
1500 mySAP Retail Finished on 01.04.2013 at 12:55:26
1550 BI Accelerator Finished on 01.04.2013 at 12:55:27
2100 SAP Records Management Finished on 01.04.2013 at 12:55:28
2200 ICM Incentive and Commissions
Management
Finished on 01.04.2013 at 12:55:27
2320 SAP Exchange Infrastructure Finished on 01.04.2013 at 12:55:29
2600 SAP Exchange Infrastructure Adapter Finished on 01.04.2013 at 12:55:29
6000 mySAP Financials Real Estate Finished on 01.04.2013 at 12:55:28
7100 mySAP Financials Corporate Finance
Mgmt
Finished on 01.04.2013 at 12:55:28
7500 Third-Party CAD Integration Finished on 01.04.2013 at 12:55:29
7550 SAP Learning Solution Finished on 01.04.2013 at 12:55:30
8020 Recipe Management Finished on 01.04.2013 at 12:55:29
8030 Catch Weight Management Finished on 01.04.2013 at 12:55:28
8040 RBD Tool Finished on 01.04.2013 at 12:55:29
8050 Bex Broadcaster Finished on 01.04.2013 at 12:55:28
Thanks & Regards,
Nabin Chatterjee

Hi,
You will get the list of background jobs in SM37.
It seems that these jobs are not being scheduled by your user ID.
In username field use * and check on the desired job statuses and use the date from and to on which you want to see the jobs.
Screen shot is also attached for your reference.
Regards,
Siddharth Khandelwal

BACKGROUND JOB WAS NOT SCHEDULED/LOG FILE NOT YET GENERATED

Hello,
To generate the log report, /VIRSA/ZVFATBAK program is scheduled on hourly basis but some time report doesn't get generated and if we see the background job then it shows sucessfully finished.
If we see the maually the log report for FFID then below error message is displayed.
" BACKGROUND JOB WAS NOT SCHEDULED/LOG FILE NOT YET GENERATED"
Can anyone guide me to solve the issue.
Thanks in advance.
Best Regards,
Prashant Dubey

Hi,
once chk the status of the job by selecting that and check job status(cltr+shift_f12)
since it was periodically scheduled job there will be a RELEASED job after every active job..
so try to copy that into another job using copy option and give some new name which u have to remember...
the moment u copy u can find the same copied job in SCHEDULED status...
from here, try to run it again on hourly basis....
After copying the job u can unschedule the old released job to scheduled otherwise 2 will run at a time...
rgds,

Hung background job

User started a background job 1hr before offline backup started. Now background job in SM37 shows status as active BUT when I tried to cancel job, popup message said "Job is not Active - cancellation not possible!". So next, I decided to delete job, message said "job is active. The selected function cannot be performed". In SM50, I cannot find any BGD process being used.
So, user has started new job today and that job is for sure running because it is using process type BGD.
How to I get rid of the 1st job??
Thanks;
Huda

hi,
I think you already cancelled the job in SM37 and tries to cancel it mulitple times thats y it is showing job is not active.
Ok regarding the SM50, if you are not seeing any background job in SM50 that means job got cancelled already don't worry about it. It will not get updated so quickly in SM37 but I am sure that it got cancelled.
go to SM51 and check there also is there any sessions with you user id?

Alv show in report but when see in spool (after run background job) there i

my program have some error when i run result alv show in report but when see in spool (after run background job) there is no data, (other program can see result in spool)
Please help
here is some example of my program
********************************declare internal table*****************************
internal table output for BDC
data : begin of t_output occurs 0,
bukrs type anla-bukrs,
anln1 type anla-anln1,
anln2 type anla-anln2,
zugdt type anla-zugdt,
result(70) type c,
end of t_output.
*****get data from loop********************************
loop at t_anla.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
              INPUT = t_anla-anln1
         IMPORTING
              OUTPUT = t_anla-anln1.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
              INPUT = t_anla-anln2
         IMPORTING
              OUTPUT = t_anla-anln2.
check record is correct or not
    select single bukrs anln1 anln2 zugdt
    into w_output
    from anla
    where bukrs = t_anla-bukrs and
    anln1 = t_anla-anln1 and
    anln2 = t_anla-anln2
   zugdt = '00000000'
if record is correct
    if sy-subrc = 0 and w_output-zugdt = '00000000'.
      w_output-bukrs = t_anla-bukrs.
      w_output-anln1 = t_anla-anln1.
      w_output-anln2 = t_anla-anln2.
      w_output-result = 'Yes : this asset can delete'.
      append w_output to t_output.
if record is not correct
    elseif sy-subrc = 0 and w_output-zugdt <> '00000000'.
there is error record this asset have value already
      v_have_error = 'X'.
      w_output-bukrs = t_anla-bukrs.
      w_output-anln1 = t_anla-anln1.
      w_output-anln2 = t_anla-anln2.
      w_output-result = 'Error : this asset have value already'.
      append w_output to t_output.
    else.
there is error record this asset donot exist in table anla
      v_have_error = 'X'.
      w_output-bukrs = t_anla-bukrs.
      w_output-anln1 = t_anla-anln1.
      w_output-anln2 = t_anla-anln2.
      w_output-result = 'Error : this asset doest not exist'.
      append w_output to t_output.
    endif.
*end of check record is correct or not
    clear w_output.
endloop.
******************************show data in ALV***************************************************
show data from file in ALV
perform display_report_ALV.
*&      Form display_report_ALV
form display_report_ALV.
DATA: LT_FIELD_CAT TYPE SLIS_T_FIELDCAT_ALV,
      LT_EVENTS TYPE SLIS_T_EVENT,
      LV_REPID LIKE SY-REPID.
PERFORM ALV_DEFINE_FIELD_CAT USING LT_FIELD_CAT.
PERFORM ALV_HEADER_BUILD USING T_LIST_TOP_OF_PAGE[].
PERFORM ALV_EVENTTAB_BUILD USING LT_EVENTS[].
LV_REPID = SY-REPID.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            I_CALLBACK_PROGRAM = LV_REPID
            IT_FIELDCAT        = LT_FIELD_CAT
            I_SAVE             = 'A'
            IT_EVENTS          = LT_EVENTS[]
       TABLES
            T_OUTTAB           = t_output
       EXCEPTIONS
            PROGRAM_ERROR      = 1
            OTHERS             = 2.
IF SY-SUBRC NE 0.
    WRITE: / 'Return Code : ', SY-SUBRC,
      'from FUNCTION REUSE_ALV_GRID_DISPLAY'.
ENDIF.
endform.
*&      Form alv_define_field_cat
      text
     -->P_LT_FIELD_CAT text
FORM ALV_DEFINE_FIELD_CAT USING TB_FCAT TYPE SLIS_T_FIELDCAT_ALV.
DATA: WA_FIELDCAT LIKE LINE OF TB_FCAT,
    LV_COL_POS TYPE I.
DEFINE FIELD_CAT.
    CLEAR WA_FIELDCAT.
    ADD 1 TO LV_COL_POS.
    WA_FIELDCAT-FIELDNAME = &1.
    WA_FIELDCAT-REF_TABNAME = &2.
    WA_FIELDCAT-COL_POS = LV_COL_POS.
    WA_FIELDCAT-KEY = &3.
    WA_FIELDCAT-NO_OUT = &4.
    WA_FIELDCAT-REF_FIELDNAME = &5.
    WA_FIELDCAT-DDICTXT = 'M'.
    IF NOT &6 IS INITIAL.
      WA_FIELDCAT-SELTEXT_L = &6.
      WA_FIELDCAT-SELTEXT_M = &6.
      WA_FIELDCAT-SELTEXT_S = &6.
    ENDIF.
    WA_FIELDCAT-DO_SUM = &7.
    WA_FIELDCAT-OUTPUTLEN = &8.
    APPEND WA_FIELDCAT TO TB_FCAT.
END-OF-DEFINITION.
FIELD_CAT 'BUKRS' 'ANLA'     'X' '' 'BUKRS' 'Company Code' '' ''.
FIELD_CAT 'ANLN1' 'ANLA'     'X' '' 'ANLN1' 'Asset Number' '' ''.
FIELD_CAT 'ANLN2' 'ANLA'     'X' '' 'ANLN2' 'Asset Sub Number' '' ''.
FIELD_CAT 'ATEXT'   'T5EAE'     'X' '' 'ATEXT' 'Result' '' ''.
FIELD_CAT 'RESULT' ''     'X' '' 'RESULT' 'RESULT' '' ''.
ENDFORM.                    " alv_define_field_cat

Hi,
Check this code..
FORM display_report_alv.
DATA: lt_field_cat TYPE slis_t_fieldcat_alv,
lt_events TYPE slis_t_event,
lv_repid LIKE sy-repid.
PERFORM alv_define_field_cat USING lt_field_cat.
PERFORM alv_header_build USING t_list_top_of_page[].
PERFORM alv_eventtab_build USING lt_events[].
lv_repid = sy-repid.
IF sy-batch EQ 'X'. ----> " System Field for Backgroud..if Background use list display
    CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
      EXPORTING
        i_callback_program = lv_repid
        it_fieldcat        = lt_field_cat
        i_save             = 'A'
        it_events          = lt_events[]
      TABLES
        t_outtab           = t_output
      EXCEPTIONS
        program_error      = 1
        OTHERS             = 2.
ELSE.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
      EXPORTING
        i_callback_program = lv_repid
        it_fieldcat        = lt_field_cat
        i_save             = 'A'
        it_events          = lt_events[]
      TABLES
        t_outtab           = t_output
      EXCEPTIONS
        program_error      = 1
        OTHERS             = 2.
ENDIF.
IF sy-subrc NE 0.
    WRITE: / 'Return Code : ', sy-subrc,
    'from FUNCTION REUSE_ALV_GRID_DISPLAY'.
ENDIF.
ENDFORM.                    "display_report_ALV

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

Background job not showing full output of Report

Dear Experts
we have created zpgm for stad report and try to take output as mail to particular user for future analysis bcaz stad gives only 2 days report only we need keep report for months together so when we run job in foreground it shows proper output but when same thing when we run from background it shows only some part of report in mail (we are unable to get full output through background job )
we send mail through spool receipts we have created folder and maintain user for getting mails through so15 distribution list
we need some input to come out of this major issue
if there is any other workaround let me know
Regards

Hello,
If a job is defined by transaction SM36, the print format parameters will only be taken into account, if they are saved as user specific print parameters of the batch user. If no user specific print format
is defined, the ALV standard logic will be processed adjusting the print format to the actual line size of the report.
For example, the list line size is about 132 characters, the widest available format of the chosen printer will be selected X_65_132.
The problem would be solved by defining a device type which is no format assigned to print, or by defining user specific print format parameters for the batch user, who creates the jobs in SM36 (see
SAP note 1179399, item 6).
Regards,
David

Background Job Still Running - Data Can Be Displayed Only Msg Populated in Maintain Versions (OKEQ) Screen

Hi,
I try to create 2013 FY in "Setting for Each FY" in OKEQ - Maintain Versions unfortunately I have created Null FY, try to delete Null FY on the time it will ask Job schedule, I have cancelled the job & reopen Maintain Versions (OKEQ) screen on the time system populated the msg "Background Job still running - Data can be displayed only"
In Settings for Each FY screen there is no New Entries button, all FY are blocked status, changes was not allowed.
How can I resolve it.
Waiting for your valuable suggestions.
Regards,
Nageswar.

Dear Rajneesh Saxena
Thanks for your prompt reply.
Yes you are correct, on the time of deletion it will ask Background Job Process, for immediate deletion must & should select "NO".
While "Settings for Each FY" screen populates message "Background Job Still Running - Data Can Be Displayed Only" open screen in display mode enter the command "=KILL" in command bar press enter, then you will allow to changes get New Entries button also.
Problem is solved
Regards,
Nageswar.

Background job status showing cacelled message number 564

Hi Experts,
We have a program wich will collect the purchase requisitions and releasses them.
1) if u manually execute this report it will show the requisitions which have to be released in ALV .then u can select them and release
2) if u run it in background, whenever it got the requisitions job ended with succussfully and finished , but if there are no requisitions our program will give warning message that no requisitions found , but after that job ststus is showing cancelled .
now how to stop this cancelled message from it ?
if do not show the warning message 'norequisitions found' then the job is successfully executed.
plz guide me in this
job log is like below :
                                                                                Date       Time     Message text                                                                              Message class Message no. Message type
29.03.2011 03:18:27 Job started                                                                                00           516          S
29.03.2011 03:18:28 Step 001 started (program ZZ_REQU_DAILY_REPORT, variant &0000000000019, user ID KRISHNAV)      00           550          S
29.03.2011 03:18:35 No Requisitions found for release!!                                                            00           001          E
29.03.2011 03:18:35 Job cancelled after system exception ERROR_MESSAGE                                             00           564          A
Thanks,
Vk

Hello Vk,
This is because 'W' messages behave as 'E' when used in report programs. Check the report DEMO_MESSAGES if you don't beleive me
Anyway back to your question, as i've mentioned you can't use 'W' messages in report. You can:
1. Write a log of your messages using traffic lights to indicate whether error, success or warning.
2. My fav, write an application log & display it to the user.
BR,
Suhas

How to set dynamic value for field Month when running background job ?

Dear guys,
I have a Z* report in our company, in the selection screen there is a period field (Month and Year) and this report running in background job periodically. My Question is how i can set for Month field become dynamic follow month value of date when this report executed ?
Example :
When Z* report running in background on 16.04.2008, Month Value will be 04 and when running on 16.05.2008, Month Value will be 05.
Please advice.
Regards
Gunawan

Dear guys,
I have a Z* report in our company, in the selection screen there is a period field (Month and Year) and this report running in background job periodically. My Question is how i can set for Month field become dynamic follow month value of date when this report executed ?
Example :
When Z* report running in background on 16.04.2008, Month Value will be 04 and when running on 16.05.2008, Month Value will be 05.
Please advice.
Regards
Gunawan

Change internal table values in background job

Hello All,
Currently we have a report which is running in background job.
Because of error in one PO (error in header status), the job is getting cancelled in production.
Is there any way, we can exclude this PO in debugging from the internal table.
The report should run in background, the requirement is exclude the PO from internal table and the background process should run as normal after excluding that PO.
Please advise how to do this.
Thanks,
Priya

Hi All,
Thanks for your replies.
I found the following way to debug the background job helpful. Go to SM37, select the job name and do as shown below. Once you click Capture: Active job, debugger will open and we can analyze from there further.

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.

Background Job Scheduling

Hi,
I am scheduling a report to run in background.
In this report it is creating background jobs automatically for different company codes.
It submits the 1st background job and waits until it finishes.
Then 2nd job starts in background and continues with other jobs.
At end it finishes all the jobs and closes.
Now my problem is.
1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
2.       If possible how can we do that.
What I have written is
loop at companycode.
Create job name.
call fun 'Job_Open'.
submit xxxx user sy-uname via job job_name numer job_count
to sap-spool
spool parameters l_spool_parameter
without spool dynpro
with companycode
with ......
and return.
endloop.
Please help ASAP, urgent.

hi praveen,
Job Scheduling Explained
Definition
Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the jobs definition. There are several ways to schedule jobs:
From Transaction SM36 (Define Background Job)
With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
Through the background processing systems own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
Through an external interface.
Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
       1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
       2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
       3.      Set the jobs priority, or Job Class:
·         High priority:      Class A
·         Medium priority: Class B
·         Low priority: Class C
       4.      In the Target server field, indicate whether to use system load balancing.
·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
·         To use a particular application server to run the job, enter a specific target server.
       5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
       6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
       7.      Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
       8.      Save the fully defined job to submit it to the background processing system.
       9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
Specifying Job Start Conditions
Use
When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
Procedure
Choose the Start condition button at the top of the Define Background Job screen.
Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
Once youve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
Managing Jobs from the Job Overview
Use
The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
Procedures
To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
To copy a single existing job, choose Job ® Copy.
To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
To repeat a single job, choose Job ® Repeat scheduling.
To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
To review information about a job, choose Job ® Job details. Details displayed can include:
current job status
periodicity, or the repetition interval
other jobs linked to the current job, either as previous or subsequent jobs
defined job steps
spool requests generated by the current job
To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
regards
karthik
reward me points if helpfull

DP background job version value shows *to{q}ZsmfF*

Similar Messages

Maybe you are looking for

DP background job version value shows to{q}ZsmfF