SAP Data Archiving in R/3 4.6C and ECC 6.0.

Hi Guys,
Need some suggestions,
We currently working on SAP R/3 4.6 and have plans to upgrade it to ECC 6.0,
In the mean time there is an requirement for SAP Data Archiving for reducing the database size and increase system performance.So wanted to know if its better to do Data Archiving before upgrade or after. Technically which will be comfortable, Also wanted to know if any advanced method available in ECC 6.0 compared to SAP R/3 4.6.
Please provide your valuable suggestion.
Thanks and Regards
Deepu

Hi Deepu,
With respect to archiving process there will be no major difference in 4.6 and ECC 6.0 system. However you may get more advantage in ECC6.0 system because of Archive routing and also upgraded Write, Delete programs (upgraded program will depend on your current program in 4.6 system). For example In 4.6 system for archive MM_EKKO write program RM06EW30, archiving of purchase document is based on company code in the selection criteria and there is no preprocessing functionality. In ECC 6.0 you can archive by purchase organization selection criteria and preprocessing functionality will additional help in archiving of PO.
In case if you archive documents in 4.6 and later upgrade it to ECC 6.0, SAP system will assure you to retrieve the archived data.
With this i can say that going with archiving after upgrade to ECC 6.0 system will be better with respect to archiving process.
-Thanks,
Ajay

Similar Messages

New to SAP Data Archiving

Hi,
Is it a must to have third party tool/ software for SAP Data Archiving
OR
SAP has its own solution for (CREATE archive files, WRITE archive files and DELETE from database).
Any pointers for some more information on different stages of SAP Data Archiving project. (Any links to how-to documents would be great help.)
Regards,
Rehan

You have posted your query in a wrong forum.
This space is for discussion on SAP TDMS topics.
You may check in the forum Information Lifecycle Management
for any available information.

Access SAP Data Archival file from outside SAP

Hello Everyone,
I have a requirement to archive the SAP data, dump that outside SAP in some other system like ILM or BI and build a reporting tool on top of that data.
So, basically customer want to shutdown the SAP and want to retain data for legal and audit pourpose.
I was doing some RnD and done archiving of MM_EKKO using SARA. the file got generated with extention .ARCHIVE. I donwnloaded teh file but it is encoded file with all special character in it.
My question is:
1. How can I read the archieved SAP data from outside SAP system.
2. Can we decode the .ARCHIVE file to get it in .DAT format?
3. Or Is there any other way to access the SAP data outside SAP in a report format.
Thanks,
Chintan SOni.

Hi Chintan,
1. How can I read the archieved SAP data from outside SAP system.
For this you could refer SAP Note 460620 - Migrating archive files
2. Can we decode the .ARCHIVE file to get it in .DAT format?
As per my knowledge,it's not possible to decode or move to .DAT format.
3. Or Is there any other way to access the SAP data outside SAP in a report format.
Refer my first response & the SAP note.
Hope this will help you.
Good luck !!
Gaurav

SAP Data Archival Project Documentation Report

hi,
Do any one can send me the documentation report on Data Archival .It ll be more helpful 2 me...Plz send me ASAP...
Thanx in advance..

Hi Kota,
Check this link
http://www.opentext.com/2/sol-products/sol-pro-extensions-sap/pro-ll-sap-dataarchiving.htm
http://help.sap.com/saphelp_47x200/helpdata/en/2e/9396345788c131e10000009b38f83b/frameset.htm
<b>Regards,
Jackie.</b>

SAP Data Archiving

I have question on Archiving Statistics.
I get some statistical information in the spool file of the archive run. And also I can see some additional statistical information when clicked on the "Statistics" button under the SARA transaction.
I am trying to understand the relation, primarily, among:
1) Size of Archiving Session in MB
2) Occupied Database space in MB
3) Deleted Database space in MB
Which of these numbers or a combination would reflect the actual disk space emptied by the Archiving run from Database?
This information is critical for the upper management.
Your help is highly appreciated.
Regards,
Srinivasa

Hi Juan,
Appreciate your inputs. Even though the performance improvements is the primary objective for implementing archiving, containing the data growth as well is an objective. I am not sure if there are any methodoligies to quantify the performance improvements resulting from archiving. Currently I am concerned about quantifying the containment of data growth as a result of archiving.
I have been also looking at documentation on archiving statistics. SAP says data archiving does a 5:1 compression for non-cluster tables, and no further compression for cluster tables.
When SAP is providing the statistical information (from the spool file of an archive session and also the "Statistics" button under the SARA transaction), I believe that should be CORRECT. And I am confused as to what the numbers in the statistics really reflect.
Here are the numbers from a production run of CO_ML_IDX (which archives data from CKMI1 table):
From the spool file the numbers are:
Size of Archiving Session in MB   -    700.900
Occupied Database Space in MB     - 10,827.569
From the statistics display the numbers are:
Disk Space         -   700.9
DB Space (Write)   - 10827.57
DB Space (delete) -     0
Did this archive run free up 3504.5 MB (which is 5*700.9)
or 10827.57 MB (the DB Space written)? Should the "DB Space (Delete)" not reflect the space deleted from the database? If so it should have some non zero value.
How are these three values related to actual disk space freed up in the database as a result of this archive run?
Appreciate for sharing your findings.
Regards,
Srinivasa

SAP Data Archiving in R/3 Ecc6.0, MS-SQL 2008 Server:

We are using MS-SQL 2008 Database, these days our production database growing quite faster. I want to setting up Data Archiving using T'Code DB15. Can anyone give steps to setup Data Archinving using DB15?
Edited by: Ahsan's on Jul 19, 2010 11:44 AM

Archiving data is bound to legal things depending on the country and the company you work. Setting up archiving is not following a few steps, you'd need to have a system where to put the archiving data.
Markus

SAP Data Migration from R/3 4.6C to ECC 6.0

Hey All
We are planning to upgrade SAP R/3 4.6C to ECC 6 in near future. I am aware that data migration is not an issue as upgrade takes care of it all. What we are concerned with is that if after a few days of upgrade when the system is functional and users have performed some quantum of transactions on it, in case if the system fails then and we have to revert back to R/3 4.6C how can we get back all the information that we processed on ECC back to R/3.
I would like to know if anyone who has performed an upgrade, had some kind of fail over strategy for such a situation. Is there some tool we can use for this purpose?
Regards
Bilal Nazir

> What we are concerned with is that if after a few days of upgrade when the system is functional and users have performed some quantum of transactions on it, in case if the system fails then and we have to revert back to R/3 4.6C how can we get back all the information that we processed on ECC back to R/3.
Simple answer: not possible.
> I would like to know if anyone who has performed an upgrade, had some kind of fail over strategy for such a situation. Is there some tool we can use for this purpose?
No - there is no tool.
Table structures change, update programs changed - it's not possible to "roll back" that to a date and re-do it on 4.6c again.
Do minimize the risk I would copy the production system to a sandbox, do the upgrade and let the (key-) users test their functionality intensively.
Markus

SAP Support for Data Archiving

Hello,
We just wanted to confirm if SAP will support issues if we encounter issues while restoring data archived via SARA. For example, if in the process of restoring archived data a defect is found, is this still supported by SAP?

Hi
Supported and the SAP Data Archiving Support Tools are SARA , DART and SARI
SARA --- SAP Archive Administration
All data archiving activities commence with Archive administration (transaction SARA). SARA provides the overall administration of archiving schedules and manages the archiving sessions. The process includes customization of objects, their conversion to archived sequential archived files and most importantly, their overall management. In addition to these, the archive administration process also retrieves the archived files and converts the data through an automated process, if there is a change in software, hardware or the data structure. The data archiving process is streamlined and simplified through the Central command of archiving administration
DART --- Data Retention Tool
A data retention strategy is required for retaining enterprise information for long periods of time. The Data Retention Tool (DART) provides this functionality. It is capable of extracting data, which is period-specific as well as any supporting information. DART transforms database objects into flat files that can be read by any third-party software designed for flat files. It is available as an add-on for older versions of SAP R/3, but is an integrated feature of the recent versions of SAP R/3.
SARI --- SAP Archive Information System
SARI provides much-needed retrieval capabilities against previously archived data. It requires the archive files be loaded into new tables in the database. In this approach, AS requires detailed, technical knowledge of the database table structure and field layouts. Database structure of an enterprise needs to be flexible and dynamic to be able to quickly adapt to organisational changes. It might happen that the current database structure is not compatible with the structure of database when archive files were initially generated. Archive Information System is a standard tool delivered by SAP that facilitates customized access to the archived data
Regards
Venkat

Put Together A Data Archiving Strategy And Execute It Before Embarking On Sap Upgrade

A significant amount is invested by organizations in a SAP upgrade project. However few really know that data archiving before embarking on SAP upgrade yields significant benefits not only from a cost standpoint but also due to reduction in complexity during an upgrade. This article not only describes why this is a best practice but also details what benefits accrue to organizations as a result of data archiving before SAP upgrade. Avaali is a specialist in the area of Enterprise Information Management. Our consultants come with significant global experience implementing projects for the worlds largest corporations.
Archiving before Upgrade
It is recommended to undertake archiving before upgrading your SAP system in order to reduce the volume of transaction data that is migrated to the new system. This results in shorter upgrade projects and therefore less upgrade effort and costs. More importantly production downtime and the risks associated with the upgrade will be significantly reduced. Storage cost is another important consideration: database size typically increases by 5% to 10% with each new SAP software release – and by as much as 30% if a Unicode conversion is required. Archiving reduces the overall database size, so typically no additional storage costs are incurred when upgrading.
It is also important to ensure that data in the SAP system is cleaned before your embark on an upgrade. Most organizations tend to accumulate messy and unwanted data such as old material codes, technical data and subsequent posting data. Cleaning your data beforehand smoothens the upgrade process, ensure you only have what you need in the new version and helps reduce project duration. Consider archiving or even purging if needed to achieve this. Make full use of the upgrade and enjoy a new, more powerful and leaner system with enhanced functionality that can take your business to the next level.
Archiving also yields Long-term Cost Savings
By implementing SAP Data Archiving before your upgrade project you will also put in place a long term Archiving Strategy and Policy that will help you generate on-going cost savings for your organization. In addition to moving data from the production SAP database to less costly storage devices, archived data is also compressed by a factor of five relative to the space it would take up in the production database. Compression dramatically reduces space consumption on the archive storage media and based on average customer experience, can reduce hardware requirements by as much as 80% or 90%. In addition, backup time, administration time and associated costs are cut in half. Storing data on less costly long-term storage media reduces total cost of ownership while providing users with full, transparent access to archived information.

Maybe this article can help; it uses XML for structural change flexiblity: http://www.oracle.com/technetwork/oramag/2006/06-jul/o46xml-097640.html

SAP Upgrade 4.6C to ECC 6.0 EHP5 system customer is using Data Archiving

Dear All,
I am planning to do SAP Upgrade from 4.6C to ECC 6.0 EHP5, in the source system customer is using SAP DATA ARCHIVING. As per some of the SAP Notes before downtime phase we need to disable all the dataarchiving jobs .
1) My question is do we need to do any presteps before starting the upgrade related to SAP DATA ARCHIVING ?
2) After the upgrade if customer wants to use the old archiving objects etc... whether they will able to do it. For this do we need to raise any message with SAP regrading the dataarchiving before the upgrade
Please let me know if you have any ideas on the above questions.
Thanks & Regards
Ravikiran

Hi,
I would suggest you to do the data archiving after upgrade project or finish data archiving before upgrade project. As lots of new archiving objects has been delivered in ECC.
Also, its true that before starting downtime project you need to stop all your jobs. Also, SAP has recently introduced new retention management technique for data archiving starting from EHP4 onwards to manage data archiving more efficiently. If you are interested, you can explore this further on http://sdn.sap.com/irj/sdn/ilm or http://service.sap.com/ilm.
Thanks
Sunny

No sap data found in the database SID !

Hello All,
While doing BI system copy activity, we are getting message as no sap data found in the database <SID>! and we could not able to proceed further.
We have MS SQL 2005 as DB and Windows 2003 STD as our OS. We are doing the system copy through homogeneous system copy method (Backup / Restore).
Before running SAPint we had deleted the old database then restored the database from the backup which we had taken of our production system.
We also ran the SQL script user_change.sql as per the note # 551915 but in SAPint we are getting above mentioned error.
Could you please help me in this regard ?
Best Regards,
Amit Vaij

Hi at all, I have the same error. But I'm wondering about the assumption, that the schema renaming should be the root cause.
I'm trying to copy a BI dual tack system on Windows/MSSQL database specific (http://scn.sap.com/thread/3380228)
Now I'm defining the parameters in SAPINST (SoftwareProvMngr), so at the moment in no step I've to set up any old schema. Also I'm not at the step of defining the JAVA export.
At the moment the SAPINST tool is trying to connect the main SAP DB.
I attached and renamed the ABAP part of the DB. I will now try to detach the DB, I assume the SAPINST Tool will install to an empty DB. So if you attach a DB with a wrong schema it can not find any tables in the instance shema of the SID defined in SAPINST and it work... we will see...
Detach was the wrong Idea... it seems there is any issue with the permissions...
but R3trans -d works

Sap table differences between 4.6C and ECC 6.0

how do i find out which sap tables has been changed between 4.6C and ecc 6.0 version. Is there a program I can run? website?

Hi,
You have to check with the Relese Notes provided by SAP for the Latest changes of the SAP versions.
But in that also, it will not be clearly mentioned by Table name, that it was changed. Only during the Upgrade of the SAP versions, all those problems will come into picture, which has to addressed and solved one by one.
Regards,
Anji

What is data archiving and DMS(Data Management System) in SAP

what is data archiving and DMS(Data Management System) in SAP
Welcome to SCN. Before posting questions please search for available information here and in the web. Please also read the Rules of Engagement before further posting.
Edited by: kishan P on Aug 31, 2010 1:06 PM

Hi,
Filtering at the IDoc Level
Identify the filter object (BD59)
Modify the distribution model
Segment Filtering
specify the segments to be filtered (BD56)
The Reduced IDoc Type
Analyze the data.
Reduce the IDoc type (BD53)
Thanks and regards.

SAP CRM Data archiving

Hi Experts,
We identified top 50 Big tables in our SAP CRM production. We need to archive this tables. I am new this archiving methodology. Can any one guide me how to do this.
Regards,
Rao

Hi Srinivasarao,
In CRM most of the standard applications have their own archiving objects and these can be archived using the transaction SARA.
There would be certain prerequiest for this and also some techincal setting such as file server configuration etc which needs to be done. Please contact your basis support guys and they will be able to help you.
For basic understanding of data archiving please look at
http://help.sap.com/erp2005_ehp_02/helpdata/en/2e/9396345788c131e10000009b38f83b/frameset.htm
Regards,
Kiran

MACRO4 for SAP BI Data Archiving

Hi All,
Can any one please tell me that can we use sap bi data archiving by using tMACRO4??

To answer your question Macro4 is a content server certified to work with archivelink so will archive BI data using the standard functionality within SAP.
From Nick Parkin Proceed Archiving Solutions

SAP Data Archiving in R/3 4.6C and ECC 6.0.

Similar Messages

Maybe you are looking for