Solution : https://service.sap.com/sap/support/notes/11733 (SAP Service marketplace login required)
Summary :
In all R/3 releases, using ROLLBACK WORK and WRITE together is problematic. The WRITE command impacts the spooler, which writes data to the database. A ROLLBACK WORK command deletes all database changes since the last COMMIT, leading to inconsistencies and potential errors. Specifically, subsequent WRITEs may overwrite previous ones, forcing temporary storage within the ABAP/4 list processor. Using ROLLBACK WORK can disrupt list processing, leading to data loss or errors in spooling tasks. To avoid these issues, database changes should be committed cautiously, and writing to the database should be delayed until certain.
Key words :
abap/4 commands rollback work, table tst01 key spool, symptom key word, magic==x'4f444f23', terms spool_temse_error reason, negative line counters, system rolls back, cautionyour safest strategy, automatic append mechanism, exporting no_rollback = 'x'
Related Notes :
| 645151 | tbb1: Partial print of log in background |
| 504952 | Composite note regarding spooling and printing |
| 448619 | Termination report RVBARCHD in test mode |
| 438930 | Error SPOOL_TEMSE_ERROR in archiving of routing |
| 409479 | PPBICO40 Spool_Temse_Error in background job |
| 326140 | SPOOL_TEMSE_ERROR during order update |
| 320758 | Termination in RPRTEC00 - SPOOL_TEMSE_ERROR |
| 320120 | Ext.HE sett:SPOOL_TEMSE_ERROR for update in backgnd |
| 302946 | SPOOL_TEMSE_ERROR for RSWWWIDE execution in the background |
| 200047 | SPOOL_TEMSE_ERROR for input tax distr. in backgrnd? |
| 135615 | Program termination when activating MRP profiles |
| 125964 | CORUAFW0: Termination due to ROLLBACK and WRITE |
| 96141 | CATS: ABAP processor: SPOOL_INVALID_JOB |
| 46621 | No handle for open TemSe object |