Avoid storage of Attachments in SAP Office tables (SOOD, SOFM, SOC3, SOFFCONT1) & Store it on OpenText Archive Server
Many times storing Attachments, notes.etc.etc can consume SAP office database table space which needs to be cleaned up very often.
To avoid storage of GOS menu items store the SAP office tables and store them in OpenText Archive server we can use SGOSATTR table to configure custom class with custom code to store attachment items to OpenText Content Server.
This blog provides the idea how it can be achieved. Currently, it is tried with “Create Attachment” GOS menu item similarly it can be extended to other GOS menu items too.
By default “Create Attachment” GOS menu item uses below highlighted class.
This particular class is copied to Z class to replace the code in the method “EXECUTE”
Custom code is filled to achieve the storage of the attached files into OpenText Content Repository
Archive id generated after running of this code and successful Archiving into OpenText Content Repository can be seen in the below screen shot
Check on the OpenText Server shows the document is stored as I did not code the storage of doc/arch id in TOA1.
But to run this successfully document type with BO SOFM is used.
Below video link show how it is achieved.
Please feel free to ask any queries.
Thanks,
Kolusu
Nice document.......
Keep sharing 🙂
Rgds,
Nayeem.
Thanks Nayeemur- I will try to post some good stuff. ~Kolusu
Hello,
Is it same thing that can be done with Note 1634908 ? I am not able to understand the difference.
Regards
S S B
Hello SSB,
Firstly, wish you HAPPY NEW YEAR 2016! 🙂
I had peeked through note I found no info about how that it can be routed to OTAS. Please correct if I am wrong.
Thanks,
Kolusu
Hello Kolusu,
Thanks for your wishes. Wish you Happy and Prosperous new year 2016 🙂 .
OTAS is Open Text Archive Server ? If yes , You can create a repository in the system with transaction OAC0 which will point to Open Text server. You can configure the repository to store the documents on Open Text repository.
Regards
S S B
Hello SSB,
After going through those notes, no info on storing the content on the external data store is provided. The whole point is to store content n OTAS instead of database to avoid performance/maintenance issue. Hope I had conveyed it well, please let me know if some thing needs the correction.
Thanks,
Kolusu
Dear Kolusu,
1) Create repository with 'OAC0' which will point to Open Text Content Server
2) Create storage category with 'OACT' pointing to newly created content repository
3) Point the document class SOFFPHIO to newly created storage category with 'SKPR08'
When the documents created after this, The contents will be saved in Open text server.
Is that requirement ?
Regards
S S B
Hello SSB,
Is your concern - saying that it’s already provided in note 1634908 or something else?
Thanks,
Kolusu
Hello Kolusu,
SSB is absolutely correct, GOS attachments can be rerouted to external archive servers through OAC0/OACT settings.
-Create a content Repo using T-code OAC0 (document area- DMS)
-Create a document category using T-code OACT, make sure you point this category to this        content repo you created above.
-Go to T-code SOFFPHIO and change the default document category from SOFFPHIO to this document category.
[Note: if the entry for SOFFPHIO class is not displayed in SKPR08,please apply note 668271]
Now the new incoming GOS attachments will move to this external server.
Madan, From you notes above..
You mentioned "Go to T-code SOFFPHIO"  , isnt SOFFPHIO a SAP Table ? and not a T-Code ..
Hi Kolusu, can you please shae the code for EXECUTE?
Super Post