Adequately Account for Business Requirements and Avoid Archiving Anarchy

  • by Dr. Rolf Gersbacher, Performance, Benchmark, and Data Archiving Department, SAP
  • January 15, 2003
SAP's archiving tools make data archiving relatively simple from a technical perspective, but don't let this lull you into a false sense of security - it's not enough to simply locate large tables, identify the archiving objects, and then run the archiving programs. These actions only touch the surface of the broader issues involved, including which data objects are archivable from a business perspective, what business processes require access to these data objects, whether there are previous or subsequent documents referenced by these data objects, and how the archived data is to be accessed later. Using the central Logistics sales order process as an example, this article shows archiving teams how to account for these critical considerations.

Dr. Rolf Gersbacher

Dr. Rolf Gersbacher joined SAP in 1994, where he was engaged in the implementation of business process reengineering projects using workflow technology. Since 1998 he has been a member of SAP’s Performance, Benchmark and Data Archiving (PBA) department, where he is responsible for conducting extensive analysis and has co-written projects in the area of data archiving. Together with Helmut Stefani, Rolf developed the best practices guide “Managing SAP Data Archiving Projects.” 

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.