Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
1.SAP (Master+Transactional) data is 1.5 (TB)terra bytes.
This should not be a problem. You can always specify variants which will break this up into multiple doucments, which can be stored into separate files
2.The data has to be archived into external storage devices .
SAP provides the Archivelink for this. You will need to configure the same in your system. Here is the link that will help you do the same:
3.if there are any open sales orders then how to handle the data cause in this case archiving can be done only when the sales order is closed .. sameways in FI/MM/SD/CO
etc ..
It is NOT possible to archive open documents. SAP will not let you archive any of the above documents (or the other documents linked to them, eg, delivery, invoice etc)till they are in closed status.
When archiving of Idocs is performed, Idocs are selected from the R/3 database based on user defined criteria and written to an archive file by the archiving program. After Idocs have been written to the archive file, a delete program can be run that will read the archive file and delete all Idocs that have been successfully archived. This ensures that Idocs are only deleted after they have successfully been written to an archive file.
Optionally the archive file can then be backed up onto a backup device or using SAP’s optical archiving facility.
Bluesky
