Regarding data Archiving

Hi,
       All
               my client needs to archive Data in SAP 8.8 each year having only 1 year completed.Can we archive data
               less than 3 year?
Thanks in Advance

There will not be any technical problem if the archiving is done as per the instructions set by SAP (I suggest you go through DATA Archiving Session from SAP), What I meant was that any data which is less than 3 year old may still be considered as new data and if this is archived you are left with no choice to modify anything in this data as this becomes read-only. If the client is looking for extra space on server by Data Archiving you can suggest other step as well . Again as I said it is the client's call afterall.
regards
johnson

Similar Messages

Appropritate forum to put queries regarding data archiving

Hi All,
Which one is the appropriate forum to put queries regarding data archiving?
Thanks in advance.
Vithalprasad

Yes you can use this forum, also there is one forum for Data Transfers.
Regards,
Altaf Shaikh

Regarding data archiving for SD objects.

Hi All,
Can you please help me to learn data archiving of SD objects.
I am very new to SDN and this is my first thread.

Hi Hariprasad,
You can find a lot of information relating to archiving SD data in SAP Help.
Here is the link you need
<a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/d1/90963466880c30e10000009b38f83b/frameset.htm">Archiving SD data</a>
Hope this helps
Cheers!
Samanjay

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

HR PA Data Archiving

Hi,
We are undergoing the archiving project for HR module. For PD data, we can use object BC_HROBJ, for PCL4 data, we can use PA_LDOC. What about 2000 series infotypes data, such as PA2001, PA2002, PA2003, etc.? Because all changes to these infotypes are stored in PCL4 cluster LA, we only need to purge the data from these tables. What is the best way to purge PA2xxx data? We cannot use transaction PA30/PA61 to delete records because user exit edits prevent any action against old data beyond certain time frame.
Thanks very much,
Li

This is not directly related to SAP NetWeaver MDM. You may find more information about data archiving on SAP Service Marketplace at http://www.service.sap.com/data-archiving or http://www.service.sap.com/slo.
Regards,
Markus

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

Data archiving for Write Optimized DSO

Hi Gurus,
I am trying to archive data in Write Optimized DSO.
Its allowing me to archive on request basis but it archives entire requests in the DSO(Means all data).
But i want to select to archive from this request to this request.(Selection of request by my own).
Please guide me.
I got the below details from SDN.Kindly check.
Archiving for Write optimized DSOs follow request based archiving as opposed to time slice archiving in standard DSO. This means that partial request activation is not possible; only complete requests have to be archived.
Characteristic for Time Slice can be a time characteristic present in the WDSO, or the request creation data/request loading date. You are not allowed to add additional infoobjects for semantic groups, default is 0REQUEST & 0DATAPAKID.
The actual process of archiving remains the same i.e
Create a Data Archiving Process
Create and schedule archiving requests
Restore archiving requests (optional)
Regards,
kiruthika

Hi,
Please check the below OSS Note :
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_whm/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31313338303830%7d
-Vikram

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

Vendor Master Data Archiving

Hi,
I wanted to archive vendor master data. I got program - SAPF058V which gives FI,Vendor Master Data Archiving: Proposal list.
This program checks whether and which Vendor Master data can be archived or not. I am getting error message after running this program with selection of one of the Vendor saying that "Links stored incompletely". Can someone pls help on this
Thanks...Narendra

Hi,
Check if you have an entry in table FRUN for PRGID 'SAPF047'. Other option is set the parameter 'FI link validation off'' with the flag on (ie: value 'x'). Check the help for this flag, surely this vendor have a code of customer. Perhaps you must try to delete this link in customer and vendor master before.
I hope this helps you,
Regards,
Eduardo

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

Can I add multple tables to a single Flashback Data archive

Hi ,
I want to add mutilple tables of a schema to a single Flashback Data archive . Is this possible ?
I dont want to create multiple Flash back archives for each table
Also can i add an entire schema or a tablespace to a flash back archive created ?
Thanks,
Sachin K

Do adding multiple tables to a single flashback archive feasible in terms of space ?Yes, you can use. Multiple tables can share the same policies for data retention and purging. Moreover, since an FBDA consists of one or more tablespaces (or subparts thereof), multiple FBDAs can be constructed, each with a different but specific retention period. This means it’s possible to construct FBDAs that support different retention needs. Here are a few common examples:
90 days for common short-term historical inquiries
One full year for common longer-term historical inquiries
Seven years for U.S. Federal tax purposes
20 years for legal purposes
How is the space for archiving data to a flashback archive generally estimated ?[url http://docs.oracle.com/cd/E18283_01/server.112/e16508/process.htm#BABGGHEI]Flashback Data Archiver Process (FBDA)
FBDA automatically manages the flashback data archive for space, organization, and retention. Additionally, the process keeps track of how far the archiving of tracked transactions has occurred.
It (FBDA) wakes up every 5 minutes by default (*1), checks Tablespace quotas every hour, creates history tables only when it has to and rests otherwise if not called to work. The process adjusts the wakeup interval dynamically based on the workload.
(*1) *1 Contradicting observations to MOS Note 1302393.1 were made. The note says that FBDA wakes up every 6 seconds as of Oracle 11.2.0.2, but a trace on 11.2.0.3 showed:
WAIT #140555800502008: nam='fbar timer' ela= 300004936 sleep time=300 failed=0 p3=0 obj#=-1 tim=1334308846055308
5.1 Space management
To ease the space management for FDA we recommend following these rules:
- Create an archive for different retention periods
o to optimally use space and take advantage of automatic purging when retention expires
- Group tables with same retention policy (share FDAs)
o to reduce maintenance effort of multiple FDAs with same characteristics
- Dedicate Tablespaces to one archive and do not set quotas
o to reduce maintenance/monitoring effort, quotas are only checked every hour by FBDA
http://www.trivadis.com/uploads/tx_cabagdownloadarea/Flashback-Data-Archives-Rechecked-v1.4_final.pdf
Regards
Girish Sharma

What is the major use of TAANA in data archiving?

People say that TAANA can give the distribution profile of the table entries over different
table field.
I do not see how come this can help us doing data archiving.
Please help.
Thanks a lot!

Hi Jennifer,
I use TAANA all the time to help determine what data is in a particular table. For example, I use it to try and determine how many records there are for a certain document type, per fiscal year, etc. This information can then be used to determine how many archive runs you will need. If there are millions of rows for a fiscal year, then you will more than likely want to break that up into months, or quarters (depending on volume).
Hope this helps.
Best Regards,
Karin Tillotson

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.

"No list available" - Spool message - Data Archiving

Hi ,
I am facing problem in CRM Data Archiving .
Now I am Archiving the Arc Object >> PRODUCT_MD .
All the parameters i have given correctly.
when i execute the job, in the spool message it says <b>"No list available".</b>
I thought the problem with the input.
then i executed this tcode - "COMMPR01" (based on the help.sap.com for this archiving object.)
I selected some of the "Material" in that and set the product status as
<b>"To archive".</b>
Any Idea on this .
expecting your valuable inputs .
Regards
Ganesh

When ever we execute logic in batch mode, the ALV list will be populated to the spool. The error says that, there is not data coming up via list output of the report. Hence there is no spool being created.
Regards,
Chiranjeevi.

Data archiving and data cleansing

hi experts,
Can any one tell me step by step guide for Data archiving and Data cleansing of SAP-ISU Object.
what is the difference between Data archiving and Data cleansing .
Thanx & Rgds

Data Archiving: So many objects are there you can look some of them..........
ISU_BBP IS-U Archiving: Budget Billing Plan
ISU_BCONT Business Partner Contacts (Contract A/R + A/P)
ISU_BILL IS-U Archiving: Billing Document Header
ISU_BILLZ IS-U Archiving: Billing Line Item
ISU_EABL IS-U Archiving: Meter Reading Results
ISU_EORDER IS-U Archiving: Waste Disposal Order
ISU_EUFASS Archiving of Usage Factors
ISU_FACTS Installation Facts
ISU_INSPEC IS-U Archiving: Campaigns for Inspection List
ISU_PPM Prepayment Documents
ISU_PRDOCH IS-U Archiving: Print Document Header
ISU_PRDOCL IS-U Archiving: Print Document Line Item
ISU_PROFV IS-U Archiving: EDM Profile Values
ISU_ROUTE IS-U Archiving: Waste Disposal Route
ISU_SETTLB Settlement Document
ISU_SWTDOC Archive Switch Document
Go to SARA t-code and enter the object CA_BUPA for business partner then Press F6 you will get step by step documentation. please follow the procedure for all the objects.
Regards,
Siva

Regarding data Archiving

Similar Messages

Maybe you are looking for