I have a problem where IDOC's with status 64 are not getting processed via background job. the IDOCs weere getting processed with the background job till today evening, but suddenly no changes were made and the processing of IDOC's with status 64 has stopped and they keep filling up, when i checked the log of the Background job it says finished, and the log has the following information,
17.09.2009 19:05:23 Job started 00 516 S
17.09.2009 19:05:23 Step 001 started (program RBDAPP01, variant POS_IDOCS, user ID SAPAUDIT) 00 550 S
17.09.2009 19:05:25 No data could be selected. B1 083 I
17.09.2009 19:05:25 Job finished 00 517 S
Kindly advise on this.
try to go to BD87 and enter one of the IDOC number that is in 64 status and execute, in the next screen select the correct node and process the IDOC, after processing check the status of this IDOC in WE02, if the status is 53 then it is successfully processed. If this gets processed successfully try the same with rest of the IDOCs that are in 4 status.
OK here is the detailed information of the Issue,
I am getting IDOCs at realtime from via FTP to sap app server location and as soon as idoc is saved it triggers the shell program to run startrfc to put that IDOC into SAP now at this stage we have IDOC's with status 64. we have scheduled teh Background job with SM36 using the ABAP Program RBDAPP01 with varient as current date so nomatter what if i select the vaient it will give me current date which is good for the IDOC to process. the time interval for running the background job has been put to 5 minutes and all the idocs will be processed within that time.
things were going good suddenly the processing of IDOCs stopped, but the background job runs but it wont pickup the IDOC to process, which means that istill have IDOCs with status 64 filling up there is no problem with the IDOCs as if i process them manually it gets processed.
I have tried deleteing the job and putting it aagain but still the same.
Enter below Details as varaint the schedule the job for every 5 time... and check the result...
Created on <blank> to <12/31/9999>
Created at <00:00:00> to <23:59:59>
IDoc Status <64>
Message type <Optional> (If you want only selected Message type to process enter here)
this will solve your issue
The idocs might stay in 64 when there is a short dump when processing them.
That's why I would also suggest to process them via BD87 to check if the idocs (and transactional documents) are succesfully processed. I expect that you might get a dump that you need to analyze.
When i process the IDOC's using BD87, they gets processed wiwth out aany issues no dump is displayed, idoc gets a status 53 after processing via BD87.
There is another problem how ever there are other jobs scheduled to run in the background other than this background job which are getting cancelled and have two different error logs for different jobs they are as follows.
1) 18.09.2009 02:00:06 Job started 00 516 S
18.09.2009 02:00:06 Logon not possible (error in license check) 00 179 E
18.09.2009 02:00:06 Job cancelled after system exception ERROR_MESSAGE 00 564 A
2) 18.09.2009 00:55:27 Job started 00 516 S
18.09.2009 00:55:27 Step 001 started (program RSCOLL00, variant , user ID JGERARDO) 00 550 S
18.09.2009 00:55:29 Clean_Plan:Gestartet von RSDBPREV DB6PM 000 S
18.09.2009 00:55:29 Clean_Plan:beendet DB6PM 000 S
18.09.2009 01:00:52 ABAP/4 processor: DBIF_RSQL_SQL_ERROR 00 671 A
18.09.2009 01:00:52 Job cancelled 00 518 A
This is a production server and the Licence is valid till 31.12.9999, and has no issues with the license.