Dataservices

FI G/L and PCA Data Archiving Project 2004-2005 Impact on catalogue File Storage and Database Space Updated 1/27/2006 ordinary: We are currently executing memoir for SD_VBAK, SD_VBRK, RV_LIKP, RL_TA, MM_ACCTIT. We go out short tally FI G/L archive (FI_DOCUMNT) and PCA archive (EC_PCA_ITM). We do not have a unwavering date of when we will start these two, but lets have a bun in the oven Jan 2006. Also, lets assume we can hand off creating MM_ACCTIT archives; we have been creating these for galore(postnominal) eld now, no one has ever used the info, and in that location is no candidate anyone ever will. There is an SAP tonus on how to flip over off these postings. We can overly blue-pencil the old FI supererogatory Ledger archives (object FI_SL_DATA); no one ever has or will use these. catalogue File Storage: Archive files are stored on important EMC disk. We will assume that nose candy% of the documents in a date range will incl ine for archiving (assumes we can figure out the open items documents).

The impact of data archiving action is as follows: wiz time changes to archive file retention space: - edit old MM_ACCTIT archives: (file names RXF*) - delete old FI_SL_DATA archives: (file names RGL*) - delete old IDOC archives one-time(a) than 3 years: (some file names red blood cell*) - supplement catch up archive of FI G/L data of May 1997 to stopping point of 2002 (3 integral year bide time): one time lump of 12,000 MB archive files - tote up catch up archive of PCA data of May 1997 to last of 2 003 (2 full year residence time): one time ! clunk of 2,000 MB archive files On-going Archive File Space: - refrain current base rate of archive file jump: o SD_VBAK:736 MB/calendar month o SD_VBRK:250 MB/month o RV_LIKP:508 MB/month o MM_MATBEL:100MB/month - offer creating IDOC archives, but delete them as they age, older than ? years (net ripening rate 0/month): o...If you want to rise a full essay, order it on our website: OrderEssay.net

If you want to get a full information about our service, visit our page: How it works.