Tips for Archiving Data in an SAP System
- by Gagan Pareek, Senior Associate Consultant, Infosys Limited
- March 10, 2014
Receive key data archiving tips from a consultant’s direct involvement in a data archival project for an SAP system. Learn how to decode object functionalities related to FI, managerial accounting (CO), and project system (PS).
By reading this article, you will learn how to:
- Proceed with the requirement analysis of a data archiving project
- Decode some object functionalities related to FI, managerial accounting (CO) and project system (PS).
- Develop an integration testing strategy for data archiving projects
- Follow techniques to form a go-live strategy
Requirement analysis (RA) in relation to data archiving can be defined as a strategy for segregating an SAP system’s redundant historical data areas and mapping a correct residence period depending on a legal and statutory compliance policy and thereby mapping SAP-provided objects to move data from an online system to static files for finalized SAP tables that are growing at alarming rate.
Recently, I completed a data archiving project for a client, and I want to share some knowledge gleaned during my experience. I highlight important decisions that you need to make during the life cycle of an archiving project. You need to make these decisions at stages ranging from requirement analysis (RA) to actual implementation. I also discuss a few important transaction codes and their relevance in this process.
I focus primarily on decision making and the internal process during the archiving.
What Should You Archive?
During the RA phase of a project in which I was involved, the company had project system, FI- CO, materials management (MM), and sales and distribution (SD) consultants who compiled a list of archiving objects that cater to tables growing at an alarming rate. The company’s Basis team provided all the year’s records along with each table’s growth rate data using transaction code DB02. This information sheet acts as a basis for all future scope decisions.
Because data from modules such as MM, SD, FI, Asset Accounting (AA), and SAP ERP Human Capital Management flows to the controlling (managerial accounting [CO]) module, it’s difficult to archive CO data. For example, CO tables might contain certain data for the Work Breakdown Structure (WBS), cost center, profit center, or internal order depending on landscape configuration. To find out which objects should be used to archive CO data, SAP has provided two analysis programs: RARCCOA1 and RARCCOA2. When my client’s consultants executed these programs, they were able to understand the company’s CO objects selection.
Would you like to see this full item?