Background Job Sheduling

Hi,
How to define a background jobs in Sm37.
Give me the steps.
Rgds,
Shradha

Hi !
Here's how to do it - in this example to create a periodic job... just try it...
First - create a Report-Variant for your print programm using the SE38.
Then...
1.) Call the transaction SM36
Enter a Job Name / You may set a job class other
than 'C' (See online Help on that field).
2.) Push the STEP Button
3.) Push the ABAP Program button
Enter der programm name an the variant name
save that window
4.) Push "BACK"
5.) Push "Start Condition"
6.) Push Date/Time
Enter Date + Time for the first start
Mark "Periodic Job" !!
7.) Push "Period Values"
Set the period you want the job to be started
Save everything
That should work....
read this SAP help for Job Scheduling.
http://help.sap.com/saphelp_nw04/helpdata/en/ef/2c513897110872e10000009b38f889/frameset.htm
Regards

Similar Messages

How to select server in which background job should run

Hi,
I want to run my program as background job. I want the user to select the server, in which background job should be run, in the selection screen of my program. When it is sheduled in background the job should run in the selected server.
How to do this?
Regards,
Sriram

Hi,
please write the code like as below.
DATA : D_GROUP like TBTCJOB-JOBGROUP.
use the function moulde JOB_OPEN.
D_JOBNAME = SY-REPID.
D_GROUP- BTCSYSREAX = " pass the target server name Here
 CALL FUNCTION 'JOB_OPEN'
 EXPORTING
 JOBNAME = D_JOBNAME
 JOBGROUP = D_GROUP
 IMPORTING
 JOBCOUNT = D_JOBNO
 EXCEPTIONS
 CANT_CREATE_JOB = 1
 INVALID_JOB_DATA = 2
 JOBNAME_MISSING = 3
 OTHERS = 4.
submit <Program name>
 USER SY-UNAME VIA JOB D_JOBNAME NUMBER D_JOBNO
 USING SELECTION-SET ' var1 ' " Give varient name
 AND RETURN.
CALL FUNCTION 'JOB_CLOSE'
 EXPORTING
 JOBCOUNT = D_JOBNO
 JOBNAME = D_JOBNAME
 STRTIMMED = 'X'
 IMPORTING
 JOB_WAS_RELEASED = D_REL
 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.
Hope this will helps you
Regards
Kiran

Background Job Terminating with Signal 4 received by operating system

Hi ,
There is a zee ABAP program which is working fine in foreground but the same was not working at BACKGROUND when I shedule the job with the same zee ABAP program. the job is terminating with "Job also cancelled due to process termination. See the system log" But the same was worked previous at background too, there are no changes to the program too.The problem was with only this zee ABAP program for remaining are all working fine.
St22:
An SAP System process was terminated by an operating system signal.
Possible reasons for this are:
1. Internal SAP System error.
2. Process was terminated externally (by the system administrator).
           Last error logged in SAP kernel
Information on where termination occurred
The termination occurred in the ABAP/4 program "ZSDUZ980" in
"ADD_NO_ACTIVITY_RECORDS".
The main program was "ZSDUZ980".
The termination occurred in line 1174
of the source code of program "ZSDUZ980" (when calling the editor 11740).
The program "ZSDUZ980" was started as a background job.
Component............ "Taskhandler"
Place................ "SAP-Server witco-10_NCQ_00 on host witco-10 (wp 1)"
Version.............. 1
Error code........... 11
Error text........... "ThSigHandler: signal"
Description.......... " "
System call.......... " "
Module............... "thxxhead.c"
Line................. 7209
The error reported by the operating system is:
Error number..... " "
Error text....... " "
System Environment
SAP Release.............. "31I"
Operating system......... "AIX"
Database type............ "ORACLE"
SAP kernel............... "31I"
SAP database version..... "31I"
Thanks
Sambi

Hi Mark,
Thanks for the reply,
Below are the memory details in our system, according to the Notes you send to me, They have set it as it is.
abap/heap_area_dia                          188743680
abap/heap_area_nondia                       400556032
abap/heap_area_total                        838860800
abap/heaplimit                              25165824
The same Zprogram was worked before in the BAckground, But from last week it stop working. But there are no chages happen to this zee ABAP program.
Thanks
Sambi

Background job stoppped in client export

Dear all,
I am trying to do client export form one SAP system to other SAP system. I sheduled the client export process in background job,it was running for long time.
Now when i check in sm50 the BGD process is been stopped , but in scc3 it shows its processing.
What is the necessary steps i need to start the job without stopping it.
Kindly Guide me.
Regards,
Rakesh

Hi ,
I resheduled the process, once again i am getting the same error.
My Background job is been stopped after few minutes.
The reason is RFC in background. But i had defined the RFC between the two systems clearly and my customizing and workbench transports is working fine.
Kindly guide me ,
Regards,
Rakesh.

TEXT_CONVERT_XLS_TO_SAP in background job schedule giving error

Hi Experts,
I used TEXT_CONVERT_XLS_TO_SAP to upload excel data. it is working fine in forground.
As large volume of data is there, I sheduled it in back ground using SM 36/ SM37.
data is not getting uploaded. I closed the excel file...still it is not getting uploaded. internal table contains no data.
Can any one help me on this....
Regards,
apuri

Hi kiran,
he function modulw which u r using is GUI function module.
Gui function module will not work in background jobs.
Thanks,

Setting Background job for BDC

Dear Frds,
I created upload program(i.e through call transcation) for Material Master.I sheduled background job through SM36/SM37 .But it is giving error as "code page error"
if any body has idea on this topic.please send me the details.

have you used any GUI_UPLOAD or WS_UPLOAD or UPLOAD function modules ?
I mean how your uploading legacy data to the internal table? if you used uploading from presentation server,then you can NOT use the program to run in background. either you have to place the file on application server or use the program in foreground mode.
Regards
Srikanth

How to get Current Background Job name and Job Count programmically?

Hi all,
I have a requirement wherein I need to get the Current Background Job name and Job Count in the program and store it in a custom table. In other words, whenever I schedule a particular program ( This is a Std program) in background, I need to update this table with the Job Name and Job Count. This will be used by another program later to read the Job Information from table TBTCO. TBTCO has key fields Job Name and Job ID. The sheduled program will be a SAP standard program and I'll be writing the logic to get the info in an Implicit Enhancement Spot.
Is there anyway I can do this? Any FM to get this information?
Thanks,
Mahesh.

Hey Adrian,
Thanks a lot. This is what exactly i was looking for. Appreciate it.
Mahesh.

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

Error while scheduling Background Job for User/Role Full Synchronization

Hi all,
We have installed RAR 5.3 Component and uploaded the authorization data & established the connectors to the backend system.
We have performed all the post installation activities and everything is complete.
When we have scheduled User -Full Synchronization with the Back End system as a part of Post Installation Activity we are receiving the below error message
"Error while executing the Job:Cannot assign an empty string to host variable 2."
Also the VIEW LOG/ Terminate Job buttons are disabled in this screen.
Can somebody please help us in resolving the above issue
Thanks and Best Regards,
Srihari.K

Hi,
We are copy pasting the error log (Part as it is huge) below here. We could able to do Full Synch for Roles and also for Profiles. Only for User Synch we are getting this error and none of the users are sychronized to RAR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: Update user WILSONA of HL2-QAHR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: Update user WINDC of HL2-QAHR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: Update user WLADICHJ of HL2-QAHR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: Update user WUK of HL2-QAHR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: Update user ZENGS of HL2-QAHR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: Update user ZHENGL of HL2-QAHR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: All System Flag:false=====Last Batch Flag:true
Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis loadUserData
INFO: @@@ User sync completed for params true: Syskey List is [HL2-QAHR]
Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob run
WARNING: *** Job Exception: Cannot assign an empty string to host variable 2.
com.sap.sql.log.OpenSQLException: Cannot assign an empty string to host variable 2.
     at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
     at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
     at com.sap.sql.types.VarcharResultColumn.setString(VarcharResultColumn.java:57)
     at com.sap.sql.jdbc.common.CommonPreparedStatement.setString(CommonPreparedStatement.java:511)
     at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setString(PreparedStatementWrapper.java:355)
     at com.virsa.cscext.dao.CSCDAO.updateIgnoredUserData(CSCDAO.java:1388)
     at com.virsa.cscext.dao.CSCDAO.populateGenObjUser(CSCDAO.java:1169)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.populateGenObj(BatchRiskAnalysis.java:868)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.insertBAPIUserData(BatchRiskAnalysis.java:142)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.loadUserData(BatchRiskAnalysis.java:390)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1275)
     at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:402)
     at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:264)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:240)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:80)
     at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:436)
     at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1225)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
     at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 13 Status: Error
Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
2@@Msg is Error while executing the Job:Cannot assign an empty string to host variable 2.
Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO: -
Background Job History: job id=13, status=2, message=Error while executing the Job:Cannot assign an empty string to host variable 2.
Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
INFO: -
Complted Job =>13----
Please let us know how to resolve this error
Thanks and Best Regards,
Srihari.K

Internal error occurs in background job scheduling

Hi Experts,
We are facing an error message "Internal error occurs in background job scheduling" while trying to execute a custom report(Z report) in background in SA38.
Please find the following observation on our side on this message.
1) This message is not coming for only one report not for others.
2) SU53 screen shot shows that SE38 check is failed, but the weird thing is not happening for other report.
3) Persons having SE38 auhtorization are able to run this report.
Please advise.
Thanks in advance,
Viven

What is the message ID and number? Have you tried OSS search and debugging?
What does this program do, in a nutshell?

BWREMOTE background job canceled in sap r/3 system

Hi my friends,
Thanks for your help ahead.
Today I checked the background job in SAP R/3 created by BWREMOTE via SM37. It showed me some jobs had been canceled.
I displayed its log, the detail message is:
==========================================
Step 001 started (program SBIE0001, variant &0000000083494, user name BWREMOTE)
DATASOURCE = ZQM_NOT_SHFGRP
Call up of customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 1,593 records
Result of customer enhancement: 1,593 records
Call up of customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 1,593 records
ABAP/4 processor: SAPSQL_INVALID_FIELDNAME
Job cancelled
==========================================
Then I displayed the "Long Text" of the job log. It is
One of the field names in the SELECT clause was not recognized.
Error analysis
The SELECT clause was specified in an internal table at runtime.
It contains the field name "TPR00", but this does not occur in any of
the database tables listed in the FROM clause.
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPLXRSA " in
"EXIT_SAPLRSAP_001".
The main program was "SBIE0001 ".
Source code extract
008840 concatenate 'TPR'
008850 day_temp+6(2)
008860 ' = '
008870 ' ''' zshift '''' into
008880 cond .
008890 append cond to itab .
008900 select schkz into i_not_shfgrp-zzschkz from t552a
008910 where zeity = '2'
008920 and mofid = 'CN'
008930 and mosid = '28'
008940 and ( schkz = 'SFTA' or
008950 schkz = 'SFTB' or
008960 schkz = 'SFTC' or
008970 schkz = 'SFTD' )
008980 and kjahr = day_temp+0(4)
008990 and monat = day_temp+4(2)
> and (itab) .
009010 endselect.
I guess that there is not a field named TPR00 in table t552a.
Next, I opened the 'project management of sap enhancement' via CMOD, entering the project name and chosing 'Display'.
Then Double click the Components 'EXIT_SAPLRSAP_001', we can see the function module 'EXIT_SAPLRSAP_001'. In the source codes, there is an include program, it is 'INCLUDE ZXRSAU01.'.
Then, I double clicked the Include program and find the position program terminated. The source codes are:
ZQM_NOT_SHFGRP *
when 'ZQM_NOT_SHFGRP'.
loop at c_t_data into i_not_shfgrp .
l_tabix = sy-tabix .
clear :mbatch ,zshift,cond ,zfield, zcharg, day_temp .
refresh itab.
if i_not_shfgrp-ausvn is initial.
else.
aa = '080000'.
bb = '160000'.
cc = '235959'.
day_temp = i_not_shfgrp-ausvn.
if i_not_shfgrp-auztv ge aa and
i_not_shfgrp-auztv lt bb .
zshift = 'MSHF' .
elseif i_not_shfgrp-auztv ge bb and
i_not_shfgrp-auztv le cc .
zshift = 'LSHF'.
else .
zshift = 'NSHF'.
day_temp = i_not_shfgrp-ausvn - 1.
endif.
concatenate 'TPR'
day_temp+6(2)
' = '
' ''' zshift '''' into
cond .
append cond to itab .
select schkz into i_not_shfgrp-zzschkz from t552a
where zeity = '2'
and mofid = 'CN'
and mosid = '28'
and ( schkz = 'SFTA' or
schkz = 'SFTB' or
schkz = 'SFTC' or
schkz = 'SFTD' )
and kjahr = day_temp+0(4)
and monat = day_temp+4(2)
and (itab) .
endselect.
endif.
I found that we got a TPR00 during concatenation. In other words, day_temp+6(2) = 00. But I think it is impossible. I can not explain this.
Any ideas, my friends. Many thanks.

select schkz into i_not_shfgrp-zzschkz from t552a
where zeity = '2'
and mofid = 'CN'
and mosid = '28'
and ( schkz = 'SFTA' or
schkz = 'SFTB' or
schkz = 'SFTC' or
schkz = 'SFTD' )
and kjahr = day_temp+0(4)
and monat = day_temp+4(2)
and (itab) . => doesn't make sense?!
endselect.
endif.
it seems something got deleted between 'and' and '(itab)'... so, you'll have to recheck the requirements for your select to fill the 'and' statement further.
so, it should look like
and monat = day_temp+4(2)
and <some kind of condition that needs to be fulfilled>.
endselect.
<some logic to fill a line in your internal table>.
append cond to itab.
endif.
obviously <some kind of condition that needs to be fulfilled> needs to be replaced by a real condition
and <some logic to fill a line in your internal table> needs to be replaced by some kind of formula
I assume something like (otherwise it would be really weird to select that field):
cond = i_not_shfgrp-zzschkz.
or a formula using the i_not_shfgrp-zzschkz field.
It would also be a lot better to replace your select ... endselect by a select single as you'll be selecting 1 record only anyways.
Message was edited by:
RafB

Background Job Sheduling

Similar Messages

Maybe you are looking for