Background job finished but Error sending data

Dear all,
report is running in my prod server . once this report completed sapuser get mail . when i check the job status it shows
Job started
Step 001 started (program GP4CF9U420G825I4P7DU8XY49WH, variant CUSTOMEROUTSTD, user ID S2K_BASIS)
Spool request (number 0000012259) created without immediate output
Error sending data (4)
Job finished
one more clarity i required
this report should goes to 4 SAP users . how can i configure this report to 4 sapusers
kindly suggest me

> Step 001 started (program GP4CF9U420G825I4P7DU8XY49WH, variant CUSTOMEROUTSTD, user ID S2K_BASIS)
> Spool request (number 0000012259) created without immediate output
> Error sending data (4)
I'd check SCOT/SOST for any errors. Also check the syslog (SM21).
> this report should goes to 4 SAP users . how can i configure this report to 4 sapusers
Create a distribution list (SAPoffice-Inbox - environment - distribution list) and enter that as addresse for the output.
Markus

Similar Messages

Background job finishes but error Error While Updating Material into Standard SAP5678

Dear
we run background job which finishes successfully but when we sqw logs it shows
Error While Updating Material into Standard SAP5678
Kindly share the reasons
Regards

This is an ERP Upgrade space and you should consider raising threads in the right space for prompt replies. Next time consider using SAP NetWeaver Administrator space for issues like these. Also you should consider closing your previous thread with the correct answer for future reference.
What I see is a custom job. You should check what the job does and also the trace file of the work process and the consult with the application team or the developer for more information. Unfortunately with that screenshot there is nothing much we can advice you.
Regards
RB

Background job finished but flat file not created in the Background

Dear all,
ZHR_CSD program is scheduled to run daily at 00:01:00. This program is generating the flat file in the folder CSD/HR.
when i schedule this program to run immediately it is generating the flat file.
But when i schedule this program in Background it is not generating flat file .
Regards

Hi,
As suggested by Eric, your Z Program is probably using GUI_DOWNLOAD Function Module.
GUI_DOWNLOAD or any other GUI function modules (FM) will only run in foreground, not in Background.
Ask your developer to code that Z Program with OPEN DATASET logic, if its possible.
The Reverse situation is well described in [this thread|Background Job assigment with variant in SM37 , for Textfile uploading], please refer it to get some relative information for the same.
Regards,
Bhavik G. Shroff

Afer background job finished, spool was not generated

hi all
Afer background job finished, spool was not generated but all background jobs is not
soem background jobs was created spool.
even if same user and same backgorund job, sometime generated spool or not.
how can I solve??
thanks

Hi,
Spool will be generated only spool specification wil be defined for that job.
Select the job go to steps spool specification you can see the device assigned to it.
Regards
Ashok

Sending of email triggered in a background job ends with error.

Hello all,
I have created a API which triggers mail to a distribution list using class CL_BCS. When i execute this API in foreground it works fine and the mails are triggered.
However i am calling this API in a report which will scheduled as a background job in my application and this job executes for some 5 to 6 hours and after that i trigger the mail. However at this point the job gets cancelled due to an abort message raised in
one of the CL_BCS methods.
The method is cl_cam_address_bcs=>create_internet_address which is called in my API and internally this calls many other methods. The abort meessage is thrown from the method instantiate_imp_class of class CL_EXIT_MASTER.
The ST22 log reads like this:
Runtime Errors: LOAD_SWITCHSTATES_MISMATCH
Short text: Current switch statuses are incompatible with program switch statuses.
What happened?
    The current switch statuses that are read for the execution of the
    program "CL_IM_CVI_ADDRESS_UPD_IMPL====CP" are incompatible with the switch
     statuses with which the
    program "CL_IM_CVI_ADDRESS_UPD_IMPL====CP" was generated at the time
     20090902114544.
Any advice would be greatly helpful.
Warm Regards,
Naveen M

Hi!
How you determine sender (method set_sender) ? if you use current user, when it runs on background use a backgorund user and it maybe can not determine an email.
Try force a sender (harcode your user for test when sy-batch eq 'X')
If it works, you need to determine the user to be used on jobs to solve this problem.
I hope it helps
Regards!!!!

Background Job cancelling with error Data does not match the job definition

Dear Team,
Background Job is getting cancelled when I run a Job on periodically but the same Job is executing perfectly when I run it manually(repeat scheduling) .
Let me describe the problem clearly.
We have a program which picks up files from an FTP server and posts the documents into SAP. We are scheduling this program as a background Job daily. This Job is running perfectly if the files contain no data. But if the file contains data the JOb is getting cancelled with the following messages.
And also the same Job is getting executed perfectly when repeat scheduling is done ( even for files with data).
Time     Message text                                                                       Message class Message no. Message type
03:46:08 Job PREPAID_OCT_APPS2_11: Data does not match the job definition; job terminated        BD           078          E
03:46:08 Job cancelled after system exception ERROR_MESSAGE                                      00           564          A
Please help me in resolving this issue.
Thanks in advance,
Sai.

hi,
If you have any GUI function modules used in the program of job
you cannot run it in background mode.

Background jobs are scheduled in future date

Hi
A system which is used by a customer test system was installed and scheduled the jobs in 2010( in future date).
Now we have changed the date to current date. But still all the background jobs are in future date.
There are around 500 jobs are scheduled. And it not possible to reschedule one by one.
Is there any way workaround to change it back to current date format.
Best Regards,
Jai

Dear Jai,
The jobs scheduler should have this dates changed to current. If its a third party system which are running these batches, then be careful to convey the same message to the 3rd party.
If its in SAP, then the schedule change date should execute your jobs. At the same time, ensure that the transports between the test systems match to the destination.
Do let me know for any clarification.
Thanks
Madhu

Error sending data to an SCMTM system from an R3 system

Dear Friends
I am trying to send an Idoc from R3 system to an SCMTM system.
I have imported the idoc, message mapping is preconfigured from SAP and requisite configurations in ID have been completed.
I am getting this error in sxmb_moni when I use FTP adapter to post the data to SCMTM system:(it is showing as processed successfully)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_NOT_FOUND</SAP:Code>
<SAP:P1>,BS_TM7_100</SAP:P1>
<SAP:P2>,BS_ECV_350,,</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver agreement found for sender ,BS_TM7_100 to receiver ,BS_ECV_350,,</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
When I tried to do this with Idoc receiver adapter but it was giving this following error in Call adapter:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>ShipmentRequestRequest_In</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Unable to interpret IDoc interface ShipmentRequestRequest_In</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Do we have to use some other way of sending data to SCMTM system?or what should we use?
Do we have to suppress any acknowledgements in IDXNOALE,then please give me the steps for it
Please help.
Thank You
Warm Regards
Arjun Ghose
Edited by: Arjun Ghose on Apr 7, 2009 10:48 AM

Hi Rajesh
Found the problem in Receiver agreement/Operation Mapping /Message Mapping after running the test:
Operation Mapping
DESADVDELVRY03_2_ShipmentRequestRequest
Runtime error
Runtime exception occurred during application mapping com/sap/xi/tf/_DESADVDELVRY03_to_ShipmentRequestR~; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Parsing an empty source. Root element expected!
... (136 lines)
In message mapping I tested, but it gave no error.In Operation Mapping there was error:
18:19:04 Start of test
RuntimeException during appliction Java mapping com/sap/xi/tf/_DESADVDELVRY03_to_ShipmentRequestRequest_
com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:ShipmentRequestRequest. Values missing in queue context. Target XSD requires a value for this element, but the target-field mapping does not create one. Check whether the XML instance is valid for the source XSD, and whether the target-field mapping fulfils the requirement of the target XSD at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:366) at com.sap.aii.mappingtool.tf7.AMappingProgram.start(AMappingProgram.java:496) at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:133) at com.sap.aii.mappingtool.tf7.AMappingProgram.transform(AMappingProgram.java:626) at com.sap.aii.ib.server.mapping.execution.JavaMapping.executeStep(JavaMapping.java:92) at com.sap.aii.ib.server.mapping.execution.Mapping.execute(Mapping.java:60) at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:87) at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:54) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:139) at com.sap.aii.ibrep.server.mapping.exec.ExecuteIfMapCommand.execute(ExecuteIfMapCommand.java:33) at com.sap.aii.ib.server.mapping.exec.CommandManager.execute(CommandManager.java:43) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:40) at com.sap.aii.ibrep.server.mapping.MapServiceBean.execute(MapServiceBean.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1579_10000.execute(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
18:19:05 End of test
I could not make out where is the problem .Please help.

Scheduled TMS_ # TMS_TP_IMPORT background jobs fail with error code 0232

Is anyone else having the problem we've just encountered since upgrading to ECC 6.0 and CRM 2007, where once setting up the automatic import ALL background jobs, to have all of the Transport Change Requests imported into the Q-Prod testing systems automatically, fail after several successful runs?
After setting up the automatic import background job to run every 15 minutes, the first few run successfully (importing any transports as it should), then the transports stop being imported.
The background jobs continue to run, but have the following in the job log overviews CRM 2007 - "Could not start transport control program tp". R\3 ECC 6.0 - "Transport control program tp ended with error code 0232".
Only by deleting the background job and recreating it (or manually importing) from STMS, can the transports continue to be imported. Although I have noticed that there are multiple tp.exe processes started, which need to be deleted before the STMS and TMS Background jobs work again.
The:
   DB is SQL Server 2005
   disp+work is at version 7000.150.14.48855
   R3Trans is at version 7000.149.14.47907
   tp is at version 7000.144.14.39594
Any suggestions on how to cure this for good?

Thanks All
FYI
SAP first suggested the following notes: 19466, 1150361, and to add a Startup profile parameter rfc/use_gwstart = 1. Which was only partially successful.
I guess it had more to do with RFC processes hanging than it did with the tp, which was fixed in a later kernel patch level.
I've upgraded the kernel to the latest (70000.181.0.0) and my problem was fixed.
Ken

Background Job Hanged but no work process assigned

Hi,
Background job has hanged When i see in SM37. But no work process assigned to this job. All work process are waiting status.
What could be the reason. What is the resolution process.
Thanks,
Dayakar

How did you come to a conclusion that the bg job is hangend.
What is the status of the job. ? I guess Job defined, but not yet eligible to run even if the start condition has been fulfilled so it should be in Scheduled status.

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,

Output after the background job finished successfully

Hi All,
We executed a Dunning job in the background (sm37) and the job finished succesfully. How to check whether the job has created an output ? Where to look for the output ?
Regards
Shiva

You can check the spool request of your job via SM37 or SMX. Go to SM37 select your job and check the spool request.
Regards
Subhash

Background Job Finishing with Database system not supporting

Hi All,
When i am running the RSCOLL00 program its executes all the programs and finally it says DataBase system not supporting.
And i am not getting any dumps.
Due to this in ST03N i could nt able to find the data for the present day and also last minutes load.
Please guide me.
Thanks,
Mahesh

Hi Kaushik,
here is the log
Job started
Step 001 started (program RSCOLL00, variant , user ID HOUSEKEEPING)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV on server tcs050983
Clean_Plan:Cleaning up jobs of system PI7
Clean_Plan:finished
Database system not supported
Job finished
Thanks,
Mahesh

Background Job Log - Interface error

Hi,
I am using a program in back ground which will transfer the data from one FTP server to another FTP server, the program is scheduled in back ground, the Job appears in green means sucessful but
in Job log I get the following log, (an if there are 10 file to be sent, 8 files moves but 2 files fails).
ftp> Interactive mode Off .#
ftp> prompt
ftp> open primary-proxy
Invalid command.#
Invalid command.#
ftp> sk74n2w9
Not connected.#
ftp> ascii
Not connected.#
Not connected.#
ftp> close
quit Transfer Complete
> ftp: connect :Connection refused
D:\usr\sap\PRD\D00\work>endlocal
Please give your valuable imputs.
Regards,
Prabhu

Hi all,
Please give some inputs on the above question. and any clarifications pls let me know.
Regards,
Prabhu
Edited by: prabhu jayaraman on Dec 9, 2008 7:06 AM

Error in active background jobs

Hi All,
i facing problem while cosing the job
i have written the code
      IF NOT p_imm IS INITIAL.
        CALL FUNCTION 'JOB_CLOSE'
          EXPORTING
            jobcount             = l_f_jobcount
            jobname              = l_f_jobname
            strtimmed            = l_flg_start_sofort
          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.
COMMIT WORK .
and it is not showing any error and it should finished the job in sm37 but i am always getting the ststus active rather than finished.
please suggest what could be the reason
Thanks,
Madhu

hi all,
please help me on this..
when there is no data then background job finish the job and in the job log it shows thst no valid data for selection. but if there si any data ... the job status stil active and it never get finished.... and finaly it get cancelled.
even while dubugging it never shows sy-subrc value other than 0. even when i run the background job manually for the submit sdt program it finish the job. I don't understand the reason why it is in active stage while executing id dialog.
Please mention if there is any parameter value missing ..
my code as follows..
do n times. "n muber of jobs
Start Immediately
      IF NOT p_imm IS INITIAL.
l_flg_start_sofort = 'X'.
(1)Open the job
      CALL FUNCTION 'JOB_OPEN'
        EXPORTING
          jobname          = l_f_jobname
        IMPORTING
          jobcount         = l_f_jobcount
        EXCEPTIONS
          cant_create_job = 1
          invalid_job_data = 2
          jobname_missing = 3
          OTHERS           = 4.
      IF sy-subrc <> 0.
        MESSAGE e032(sxmsf) WITH l_f_jobname.
      ENDIF.
(2)Report start under job name
      SUBMIT (g_c_prog_c1_lo)
             WITH s_partn IN r_partn
             WITH s_parro IN s_parro
             WITH s_grvsy IN s_grvsy
             WITH s_lgreg IN s_lgreg
             WITH p_updab = p_updab
             WITH p_updbi = p_updbi
             WITH p_enqal = p_enqal
             TO SAP-SPOOL WITHOUT SPOOL DYNPRO
             VIA JOB l_f_jobname NUMBER l_f_jobcount AND RETURN.
*(3)Job closed when starts Immediately
      IF NOT p_imm IS INITIAL.
        CALL FUNCTION 'JOB_CLOSE'
          EXPORTING
            jobcount             = l_f_jobcount
            jobname              = l_f_jobname
            strtimmed            = l_flg_start_sofort
          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.
      COMMIT WORK .
      ADD 1 TO g_cnt_job.
      l_r_tbtcjob-jobcount = l_f_jobcount.
      l_r_tbtcjob-jobname = l_f_jobname.
      l_r_tbtcjob_previous = l_r_tbtcjob.
      IF NOT l_flg_first_job IS INITIAL.
        g_v_tbtcjob_first = l_r_tbtcjob.
      ENDIF.
      CLEAR: l_flg_first_job.
    ENDDO.
thanks

Background job finished but Error sending data

Similar Messages

Maybe you are looking for