WWI Generation is creating thousands of records in DRAO

[Former Member]

Hi All,

We are experiencing an opportunity right now where our DRAO table is growing at an alarming rate.  We went live on EHS last October and in the last 8 months our DRAO table has had over 13.5 million records generated.  When I create a single WWI report, there are over 2,000 records being generated in that table.  Has anyone else run into this?  We realize that doc types SBE and SBR are not set to KPRO and we're considering that change, but we're concerned the same problem will occur in the content server.  Any help would be appreciated.

Thanks,
Jason

[Former Member · Accepted solution]

Just as an update to anyone reading this post, the reason for all the records in the DRAO table is that SAP stores SBR records in this table in chunks of 25 KB, therefore a 7 MB report will be around 2,000 - 3,000 records.  If your graphics are large, the records could be large.  We've decided to convert all records in this table to our DMS via DMS_KPRO_COVERT.  We've also changed the configuration in our SBR doc type and EH&S to store the newly created SBR docs using KPRO.  There are several notes that can be found by searching KPRO in the SAP Notes search to get your config correct for using KPRO.

[christoph_bergemann · Accepted solution]

Dear Jason

may be OSS note 413150 may be of interest as well (even if you have solved your issue).

C.B.

[christoph_bergemann]

Dear Jason

can you kindly check "DRAO"? I assume that the problem is related to reports of typE "SBE" and not "SBR". This topic is independent of use or not use of KPRO and similar tools.

I assume topic is related to "SBE" once. Check your customizing set up . There is a customizing paramter which you can use to decided if or if not SBE need to be stored. Normally you do not store SBEs. If you use tools as KPRo etc. then you "move" only the document.

C.B.

PS: check e.g. http://scn.sap.com/message/8090182 or similar threads.

[Former Member]

Hi Christoph,

SBE is an issue in DRAO for us as well; however, SBR is also an issue.  I'm attaching a screen shot of the table where one generated report created 2,236 records in the table.  I just ran this report today and we have SBR set to KPRO.

[christoph_bergemann]

Dear Jason

if you did not "check" the "KPRO" flag during the customizing of the document type it is quite clear why DRAO is increasing. According to docu of SAP: you can not set the flag after you have created at least one document); i have "heard" that there might be some "reports" which can be used later. That means you couild check "KPRO" flag and make a "remappgin" of documents; I have no experience in doing so.

DRAO contains the document data. SBRs are stored here. You can only avoid to store SBEs (by proper set of of them); IBDs etc.

Any line contains a "unique" key. This key is the loink to the content of the "whole" document.

May be an "expert" in using DMS ; KPro and other tools can help you. Waht you can think about is to:

a.) zip the documents

b.) or archive tehm (e.g. the historic one)

PLease check EHS help. I assume then that DRAo will decrease

Hope this helps

C.B.

[Former Member]

Thanks Christoph, this helps explain why the change to KPRO didn't seem to help.  We're going to hire a consultant to help us clean up this mess.

Thanks,
Jason

[christoph_bergemann]

Dear Jason

only as add on: check may be:

http://www.stechno.net/sap-notes.html?view=sapnote&id=1408009

http://fmis.minfin.bg/help/EN/16/ce71403017587ee10000000a155106/frameset.htm

http://de.scribd.com/doc/15557133/Sap-PLM-Ehs-Dms-Config

http://scn.sap.com/thread/1706320

http://benxbrain.com/en/index.do?onInputProcessing(brai_thread)&001_thread_id=1712963%20&001_temp=R3...

http://www.consolut.com/en/s/sap-ides-access/d/s/doc/YY-EHS_SR_60_60

https://scn.sap.com/thread/1714639

Related to DMS topics are not only "DRAO" but other tables as well. If you are interested in that: may be check: http://wiki.sdn.sap.com/wiki/display/PLM/Basics+of+Document+Management

As mentioned:

Document type SBE can be set up in such a way that it stays in system e.g. 10 days and is deleted (as document can be regenerated with CVD1) then automatic; tehrefore there is noe reason why DRAO should increase (some background job should run do delete deleted documents form DMS); the "zipping" and "unzipping" of documents as mentioned might help (please refer to SAP EHS help) but it is "clear" that there could be some performance issue. Personally I have bo experince with this "Zip/unzip" process. The archiving is may be the best option. You could archive any report which is "historic" but you need to understand that some user would like to compare "released" and "historic" document and I am not sure if this works if historic document is archieved. So the archiving depends on demand of company.

Depending on the size of your company (number of real substances) and business and how you have e.g prepared MSDS/SDS topic normally you can have roughly 5 - 10 released reports per REAL_SUB. Any of them is roughly of size 250 kBytes (not zipped); in europe because of REACh the size has been increased. As you will increase this number by setting documents to historic and regenerate new ones it is quite clear that DRAO will increase.

Normally companies do not only generate SDS/MSDS using WWI; they handle e.g. inbound documents (raw MSDS) and generate other documents as well .

C.B.