Skip to Content
avatar image
Former Member

Best Practice : Archivelink and Content Server

We have one content server up and running with one repository for purchasing documents. We are about to turn on archivelink functionality for some SD outputs. What is the best practice, one content server with many repositories (i.e Z1 (purchasing) Z2(sales orders) Z3(invoices) or a different content server/repository for each module such as purchasing and sales and distribution.

If you use Archivelink/Content Server, I would appreciate any feedback regarding your landscape and how many content servers or repositories you have.

Thanks,

Carla Matczak

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Aug 18, 2009 at 03:46 AM

    Dear

    for Archivelink & Content Repository, following link will be useful for you

    http://help.sap.com/saphelp_nw04s/helpdata/en/5e/566039b85f9443e10000000a114084/frameset.htm

    Regards

    Tushar Dave

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 18, 2009 at 01:42 PM

    Standard practice is to create repositories by module or by retention. The concept of logical repositories came from the years where optical media was used and you wanted the ability to put a whole lot of documents together that had the same retention period and be able to remove the media from the jukebox because the cost of storage space was expensive. This would mean people would typically create F1, F2, F3 etc as they filled optical disks.

    These days most people just break it up by module and create one per area. I.e. F1 for Financial, S1 for SD, H1 for HR, D1 for Data Archiving

    Incidentally, this is one area that most people don't follow the Z naming convention for SAP.

    Edited by: Athol Hill on Aug 18, 2009 11:42 PM

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      You may want to consider the configuring the content repositorieswith respect to the retention periods as well. This will help you to manage the retention of the documents. As the retention management of the archivelink document is only though the SAP link table entries in TOA* tables, even if you delete the link table entries the documents will still be available in your content server. If you configure your content repositories based on retention periods you can runs scripts with in the content server to delete the actual stored documents

      It is also recommended that you create one document type per your output type. Typically you would have multiple output types based on different legal entity (if your SAP is supporting multuple countries and SBU's).

      Hope this help

      Suji