Skip to Content

WWI Reports create large number of entries in DB tables

Sometimes the amount of data entries created by EHS WWI reports increase in a incomprehensive way, generating huge tables and slowing down the system performance.

The reason for the big number of entries is the way documents are stored. DRAO and DRAW are tables of the Document Management System (DMS).

The data in table 'DRAO' is split into chunks of 2550 bytes. One entry in table 'DRAO' consumes 2550 bytes. So if you upload a file which has 2,550 KB or less, one entry is created. If you upload a file that has more than 2,550 KB, let's say 2,8 KB, then a second entry needs to be created. This second entry allocates again 2,550 KB in total. So, there could be several (up to 9999) entries for each report.

EH&S just uses the DMS functions. So I suggest to delete the obsolete documents, e.g. in transaction CV02N. Then the documents are marked

with a deletion flag. To delete the documents physically from the database, you have to run report MCDOKDEL.

One of the common reasons for it, is that the final reports are stored by the system.

Whether the final reports need to be stored or not is a decision to be made and set under SPRO:

Environment, Health & Safety

  -> Product Safety

     -> Report Shipping

        -> Basic Settings

           -> Specify Shipping Reasons

Call the details screen for every combination of Reason, Reason type and Business Process especially for SD_CALLs, and check whether the flag 'Final report' is set. Of course it is not wrong to set this flag, but this would explain why there are so many end reports. Maybe someone decided to keep end reports in the system or the flag was set inadvertently. If you remove the "final report" indicator flag, the final reports of EH&S report shipping will not be kept in the system, thus reducing the amount of table space needed in tables DRAW and DRAO

Another possibility to reduce the number of stored documents, is execute report RCVDRFSH. For further information see note 940936.

For further description and possibilities, please check SAP note 586293.

Tags: