Many customers are asking how to delete old bdocs or why the entries in table SMW3_BDOC* are becoming more and more.
The report SMO6_REORG2 can be used to delete the obsolete bdocs. And it is recommended to be run in the production system periodically. So the entries in table SMW3_BDOC* would not be increasing so fast.
The report SMO6_REORG2 calls many different reports and you can see the options for reorg different objects. You can find more details in note 206439.
Before running the SMO6_REORG2 report, you might consider running basis report RSRLDREL2 for relation table SMW0REL to delete the object links for BDoc’s. Please see KBA 1922644 for details.
In the program SMO6_REORG2, you can define variants to separate the options in different jobs. As mentioned in note 493156, the parameter “Days to hold” means the days to hold the bdocs from now and it should be a low whole number. The default and recommended value is 7.
Additionally, this report SMO6_REORG2 only deletes successfully processed Bdocs. The Bdocs with errors cannot be deleted because that will cause data inconsistency. If you want to delete previous unsuccessful Bdocs, you can manually set the Bdoc status to “set to processed” in SMW01 by menu “Bdoc Message-> Process-> Delete”. After that, run the report SMO6_REORG2 again, the bdocs can be deleted.
Here is also a note 1138051 which contains the parameter to prevent creating object links between bdoc. But this is not very recommended.