Solution : https://service.sap.com/sap/support/notes/36781 (SAP Service marketplace login required)
Summary :
SAP Note describes the issue of excessive size in table APQD, which stores batch input sessions. These sessions accumulate due to non-processing, errors, or intentional saving with the KEEP flag. Preventative measures include avoiding needless KEEP flag usage and removing erroneous sessions with transactions SM35 and RSBDCREo. Regular cleanup strategies like running RSBDCREO in all clients are advised. For overgrown tables, initial cleanup is recommended using SM35 or RSBCDREO, followed by database reorganization if necessary due to residual space occupation on some databases. Physical deletion of APQD is a last resort and risky maneuver.
Key words :
truncate table apqd drop storage, symptom table apqd, additional key words, batch input sessions, generate sessions unnecessarily, remove incorrect sessions, database systems apqd, table apqd, table physically, sessions remain
Related Notes :
| 706478 | Preventing Basis tables from increasing considerably |
| 396421 | Batch input folder: runtime errors/Performance problems |
| 35952 | Client deleted, space still filled in database |
| 24438 | Are processed sessions physically traceable? |
| 18307 | Batch input logs and reorganization |