Data Archiving - System Prerequisites
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.
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
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.
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.