No, it is the same thing. The one runs the ABAP, the other does a submit of the ABAP. It is the same ABAP, with the submit the basis team has tighter control of where it gets executed and how many reports can run in parallel at any time. Ask your SAP Basis team about “SAP Spool Jobs”…
I am also facing the same issue when i tried to intall “Plant Maintenance” Rapid Mart. I changed the execute in background option to ‘Yes’. But that is also not helping me…
CA Rapid Mart running fine for more than six months and this is the first time error occured after the R3 sits about 18 minutes. SAP R3 data store is set to “Generate and Execute” in backgroup:
I have had out sap people watch the job and they can see the dialog sessions on their side. I have had this open with support, but they haven’t been able to help as of yet.
There must be something on the SAP side that is causing this I assume.
NB: We have also tried changing to ‘execute preloaded’ but that didn’t help either.
Major difference. Normal abap flows do a select on data via a job in sap, should be done as a background job. then via a share or FTP a flat file is send back to the BODS server.
Extractors are using extractors and stream the data to the BODS server.
For extractors timing out there is yet another SAP Note. My task with the priority 2 for next week is to make finding all ODP/Extractor related notes simpler.