Problem solve
Get help with specific problems with your technologies, process and projects.
Can I extract one module and continue another module?
We are running SD, MM, FI, and CO on release 6.2 but we are going to stop the SD and MM application soon. The current database size is 4TB which includes 95% of SD and MM data. Maintaining a 4TB database for FI/CO only is inefficient and very expensive so we are considering an archiving solution but it will take us several months to get the system to a smaller size. Can I migrate the FI/CO module only to a new instance and continue the FI/CO application on the new instance without loosing any FI/CO data? If yes, would you recommend it? What are the risks?
We are running SD, MM, FI, and CO on release 6.2 but we are going to stop the SD and MM application soon. The current database size is 4TB which includes 95% of SD and MM data. Maintaining a 4TB database for FI/CO only is inefficient and very expensive so we are considering an archiving solution but it will take us several months to get the system to a smaller size.
Can I migrate the FI/CO module only to a new instance and continue the FI/CO application on the new instance without...
Continue Reading This Article
Enjoy this article as well as all of our content, including E-Guides, news, tips and more.
Step 2 of 2:
loosing any FI/CO data? If yes, would you recommend it? What are the risks?
All SAP modules are integrated into each other. You cannot extract one without compromising data integrity. The only solution to reclaim disk space is to archive what you no longer need and reorganize the database.
This was last published in May 2005
Dig Deeper on SAP Basis administration and NetWeaver administration
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.
Meet all of our SAP administration / development experts
View all SAP administration / development questions and answers
Start the conversation
0 comments