Data Archiving - System Prerequisites

Hi,
We are planning to ARCHIVE some of the tables to reduce the TCO. (Total cost of Ownership)
In this regard, I would like to know the following:
On the Basis side, I want to check for any prerequisites etc (like Minimum SP LEVEL, Kernel version, Import Notes to be applied etc)
Are there any document which clearly talks about these prequisites for preparing the System in order to be able to carry out the Archive work without any issues.
(Note: We are not using ILM solution for Archiving)
I am mostly concerned with the SAP Notes that are considered to be the prerequisites.
Best Regards
Raghunahth L
Important System information :
Our system version is as follows :
System -> ERP 2005 (Production Server)
OS      -> Windows 2003
DB      -> Oracle 10.2.0.2.0
SPAM    -> 7.00 / 0023
Kernel -> 7.00 (133)
Unicode -> Yes
SP Info:
SAP_BASIS 700(0011)
SAP_ABA 700(0011)
PI_BASIS 2005_1_700(0003)
ST-PI 2005_1_700(0003)
SAP_BW 700(0012)
SAP_AP 700(0008)
SAP_HR 600(0003)
SAP_AP 700(0008)
SAP_HR 600(0013)
SAP_APPL 600(0008)
EA-IPPE 400(0008)
EA-DFPS 600(0008)
EA-HR 600(0013)
EA-FINSERV 600(0008)
FINBASIS 600(0008)
EA-PS 600(0008)
EA-RETAIL 600(0008)
EA-GLTRADE 600(0008)
ECC-DIMP 600(0008)
ERECRUIT 600(0008)
FI-CA 600(0008)
FI-CAX 600(0008)
INSURANCE 600(0008)
IS-CWM 600(0008)
IS-H 600(0008)
IS-M 600(0008)
IS-OIL 600(0008)
IS-PS-CA 600(0008)
IS-UT 600(0008)
SEM-BW 600(0008)
LSOFE 600(0008)
ST-A/PI 01J_ECC600(0000)
Tables we are planning to archive
AGKO,     BFIT_A,     BFIT_A0,     BFO_A_RA,     BFOD_A,     BFOD_AB,     BFOK_A,     BFOK_AB,     BKPF,     BSAD,     BSAK,     BSAS,     BSBW,     BSE_CLR,     BSE_CLR_ASGMT,     BSEG_ADD,     BSEGC,     BSIM,     BSIP,     BSIS,     BVOR,     CDCLS,     CDHDR,     CDPOS_STR,     CDPOS_UID,     ETXDCH,     ETXDCI,     ETXDCJ,     FAGL_BSBW_HISTRY,     FAGL_SPLINFO,     FAGL_SPLINFO_VAL,     FAGLFLEXA,     FIGLDOC,     RF048,     RFBLG,     STXB,     STXH,     STXL,     TOA01,     TOA02,     TOA03,     TOAHR,     TTXI,     TTXY,     WITH_ITEM,          COFIP,     COFIS,     COFIT,     ECMCA,     ECMCT,     EPIDXB,     EPIDXC,     FBICRC001A,     FBICRC001P,     FBICRC001T,     FBICRC002A,     FBICRC002P,     FBICRC002T,     FILCA,     FILCP,     FILCT,     GLFLEXA,     GLFLEXP,     GLFLEXT,     GLFUNCA,     GLFUNCP,     GLFUNCT,     GLFUNCU,     GLFUNCV,     GLIDXA,     GLP0,     GLPCA,     GLPCP,     GLPCT,     GLSP,     GLT0,     GLT3,     GLTP,     GLTPC,     GMAVCA,     GMAVCP,     GMAVCT,     JVPO1,     JVPSC01A,     JVPSC01P,     JVPSC01T,     JVSO1,     JVSO2,     JVTO1,     JVTO2,     STXB,     STXH,     STXL,     TRACTSLA,     TRACTSLP,     TRACTSLT,
in addition we have some Z Tables to be archived.

Hi,
Pre-requisites for search OSS notes or BC Sets depends upon the program that is used in archive, delete or read.
If there is no proper selection criteria in write variant selection,
If the program is getting terminated due to long processing time,
If percentage of data archived for your selection is less even after data meeting minimum criteria,
If system allows user to change archived data,
With all the above scenarios we will search for OSS notes. If SAP has released BC sets then we will implement these.
If you have any problem while archiving and based on the archiving experience if you think that some of the oss notes will help then take a call on implementing it.
With the tables you have mentioned i can say that archiving objects such as FI_DOCUMNT, FI_SL_DATA, EC_PCA_ITM, EC_PCA_DATA, CHANGEDOCU, ARCHIVELINK.
You have to search any latest release BC sets or OSS notes for your system application.
-Thanks,
Ajay

Similar Messages

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 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

System crash during data archiving

Gurus:
We have a serious concern that is if our R3 server crash during our data archiving runs:
1) if crash happens at write phase, can we simply remove the generated archive , restart the write job?
We are NOT sure if the second run will archive those records that were archived in the failed first run.
2) if crash happens at delete phase, a simple restart of the same delete job will be enough? (We use "store before delete").
Because this archiving is too important to us, please help.
Thanks a lot!

Christoph:
Thank you for your reply.
This crash has not happened yet.
We are making a plan about how to cope with this possibility.
But we do not have experience with any crash during archiving process.
Therefore we ask for people's experience about following scenarios:
1) if crash happens at write phase, can we simply remove the generated archive , restart the write job?
We are NOT sure if the second run will archive those records that were archived in the failed first run.
2) if crash happens at delete phase, a simple restart of the same delete job will be enough? (We use "store before delete").
Would you please help?
Thank you again.

Any pre-requiste for data archiving

hi,
is there any pre-requiste for data archiving..
i.e., for a particular data we have to archive..
or any condition
regards
sree

Hi
Archive Selection
Use
For some archiving actions it is necessary to select individual archive files or whole archive sessions and make them available for the relevant action. You do this in the Archive Selection screen, which is accessible from the initial screen of the relevant action.
Archive selection is relevant for the following actions:
Delete
Read
Build index
Reload
Postprocessing
Prerequisites
Depending on the action, there are four different criteria for whether archiving sessions and archive files are displayed in the archive selection:
Criterion 1
Archive file status
Action
Criterion
Delete
Archive file status
Archived or
Stored (if sequence "Store before deletion" has been selected in Customizing)
Read
Archive file status Archived
or
Deleted
or
Saved
Build index
Archive file has the status Deleted and the file is in the file system
Reload
Archive file is in file system and the session has the corresponding status (see criterion 5)
Postprocessing
All archive files have status Deleted
Criterion 2
The archive file must contain at least one data object. If you have performed an archiving session and maintained the variants so that no data objects were archived, the archive file is automatically deleted and no longer offered for selection.
Criterion 3
If a file is not accessible in the file system, the file is not offered for selection. A file is only offered for read if all the files in a session are accessible.
While checking the accessibility of a file, the system performs a read access for each file. This check process can take a long time if there are a lot of files. To optimize this process the access check can be de-/activated according to archive files in file system and archive files in an optical archive in archiving object-specific Customizing.
Criterion 4
For client-dependent archiving objects only the sessions for the current client are offered.
Criterion 5
An archiving session can only be reloaded if it has the status Complete or Archiving session is reloaded.
Features
In the Archive Selection screen, which you can access by choosing Archive Selection from the initial screen of the archiving action, you can either select complete archive sessions or individual archive files.

How do I create an archive system for a blog created with a custom app?

I had to create a blog using a custom app, because I needed an image to show up in the list view (a feature I can't believe does not exist in the blog module). Anyways, I am wondering how can I create an archive system? Do I need to create categories for each month/year and then classify the post each time we create one. Then manually create links each month to pages that filters listing by that category? This is the system I tried, but I was wondering if there was a better way.
Also, I would like to have a sidebar that shows all the authors/contributors of the blogs and have a count under their photo that shows how many blogs they have contributed to, and have this update dynamically each time they create a new post. I was wondering if a data source tag is the way to do this but I don't have enough information on how the data source tag even works, to really know how to do this.
I have searched google for hours, and even signed up for BC gurus tutorials with no real luck. I thought BC gurus was going to have the answer but it wasn't quite detailed enough. Any help would be much appreciated. Thanks!

You can use classifications but there is no auto feature to archive like that on web apps.
In terms of the blog, Like I have said to everyone that has posted about blog preview images:
http://www.prettypollution.com.au/business-catalyst-blog
Just one example of an image at the start of the blog post rendering out, not hard at all.

Business Partner Data Archiving - Help Required

Hi,
Am New to Data Archiving and need help to Archive Business Partner in CRM. I tried to Archive some BP's but it was not archiving. Kindly throw some light on it.
Problem we face are:
1) When we try to write a Business Partner to an Archive File the Job Log Shows finished but no files are created in the System.
2) When we try to delete the BP from Data Base it doesn't show the Archived BP's that could be deleted (I guess this is because there are no archived file).
Archive Object Used is CA_BUPA. We have created a Variant and set the Time as Immediate and Spool to LOCL.
Kindly let us know if there is any step we are missing here and if we are on the wrong track.
All answers are appreciated.
Thanks,
Prashanth
Message was edited by:
        Prashanth KR

Hi,
To archive a BP following steps are to be followed.
A. Mark the BP to be archived in transaction BP >status tab
B. Run dacheck
FYI : Steps on how to perform dacheck :
1. In transaction DACONTROL change the following parameter to the
values : for CA_BUPA .
No. calls/packages   1
Number of Objects   50
Package SizeRFC     20
Number of Days       1 (if you use mobile client it should be more)
2.If a business partner should be archived directly after the
archiving note was set, this can be done by reseting the check
   date with report CRM_BUPA_ARCHIVING_FLAGS.
   here only check (set) the options :
   - Archiving Flag
   - Reset Check Date
Reset all options should be unchecked.
3. go to dacheck and run the process
4. This will change the status of the BPs to 'Archivable'
   *Only those bp's which are not involved in any business transactions,
    install base, Product Partner Range (PPR) will be set to archivable
The BP's with status 'Archivable' will be used by the archiving
     run.
Kindly refer note 646425 before goint to step C ***
C.Then run transaction CRM_BUPA_ARC.
- Make sure that the "selection program" in transaction "DACONTROL"
   is maintained as " CRM_BUPA_DA_SELECTIONS"
Also create a variant, which can done by excecuting
CRM_BUPA_DA_SELECTION and enter the variants name for the field
Variant. This variant is the buisness partner range.
- Also please check note 554460.
Regards, Gerhard

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

How to read open customer items from Archive system i.e BSID & BSAD tables

Hi,
We have a requirement to get the customer line items data that were open as of key date from archive system and present it as customer aging through a custon report. Example,in SAP R/3 we have data for last 3 yrs and beyod that the data is in archive system. Based on teh Key date, we need to got o archive system get the customer open items i.e from BSID & BSAD tables.
If you anyone has already dealt with this kind of requirement, please help me out with directions like simple way to ge the data. There is a standard report FBL5N with the option to choose datasources as , Database or archive system which used the logical database DDF.
Regards,
Abhi

- First take a look at the [Archive Development Kit (BC-CCM-ADK)|http://help.sap.com/SAPHELP_NW04S/helpdata/en/2a/fa0391493111d182b70000e829fbfe/content.htm] and for coding sample at [Archiving Class|http://help.sap.com/SAPHELP_NW04S/helpdata/en/2a/fa03f9493111d182b70000e829fbfe/frameset.htm] and report BC_SFLIGHT_READ_DB_AR_BY_INDEX.
- Look also at archive object FI_DOCUMNT via transaction AOBJ.
Regards,
Raymond

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

Data archival and purging for OLTP database

Hi All,
Need your suggestion regarding data archival and purging solution for OLTP db.
currently, we are planning to generate flat files from table..before purging the inactive data and move them to tapes/disks for archiving then purge the data from system. we have many retention requirements and conditions before archival of data. so partition alone is not sufficient.
Is there any better approach for archival and purging other than this flat file approach..
thank you.
regards,
vara

user11261773 wrote:
Hi All,
Need your suggestion regarding data archival and purging solution for OLTP db.
currently, we are planning to generate flat files from table..before purging the inactive data and move them to tapes/disks for archiving then purge the data from system. we have many retention requirements and conditions before archival of data. so partition alone is not sufficient.
Is there any better approach for archival and purging other than this flat file approach..
thank you.
regards,
varaFBDA is the better option option .Check the below link :
http://www.oracle.com/pls/db111/search?remark=quick_search&word=flashback+data+archive
Good luck
--neeraj

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

The best practice for data archiving

Hi
My client has been using OnDemand for almost 2 years, there are around 2M records in the system(Activities), so just want to know what is the best practice of data archiving, we dont care much about the data in the 6 month ago.

Hi Erik,
Archival is nothing but deletion.
Create a backup cube in BW. Copy the data from your planning cube to the backup cube, and then delete that data region from your planning cube.
Archival will definitely improve the performance of your templates, scripts, etc; since the system will now search from a smaller dataset.
Hope this helps.

Best Practise for Data Archiving

Hi All,
I have query in SAP that when business will do the data archving in their R3 systems.
On which basis they will do data archiving?
Is there any minimum period that data need's to be archived?
before doing the data archiving what they will do ?
Regards
Srini

Hi Srini,
1. SAP suggestes to implement data archiving strategy as early as possible to manage database growth .
However pople think of archiving when they realise the problems like large data volumes,slow system resonse time,performance issues etc...
2. There is a proper way to implement Data Archiving . Database has to be anaylzed first for getting the top DB tables and Archiving objects.
3. Based on the DB analysis ,Data archiving plan has to be implenemted according to data management guide.
4. There is a minimum period known as residence time has to be completed before any data to be archived. Once the document is business completed and serverd its minimum required period in the Database ,it can be archived.
5, Before going for data archiving there are many steps to be followed like analysis,configuration etc that you can see in details at the link below :
http://help.sap.com/saphelp_47x200/helpdata/en/2e/9396345788c131e10000009b38f83b/frameset.htm
let me know if this helps you .
-Supriya
Edited by: Supriya Shrivastava on May 4, 2009 10:38 AM

Business Intellience and Data Archiving

Once you have implemented Data Archiving, what are the possible ways of allowing BI standard and custome extractors to look at both SAP ECC online and archived data (the archived data sits on Open text). How do you deal with BI complete reload and refresh requirement for a specific data if the data has been already been archived?

Is there any addiotional things we need to do at info source level after activating the content? Selecting the correct data source etc.
If there is a enhancement to the extraction structure then what all steps manually we need to do at info source level? When we replicate the data source which has been enhanced, will it create the infoobjects automatically so that they can be used in infosource communication structure?
As I am new to the system, I am running in to all these questions.
Appreciate any help in step by step how things will work.
Thanks.

Data Archiving - System Prerequisites

Similar Messages

Maybe you are looking for