cancel
Showing results for 
Search instead for 
Did you mean: 

Demerger and data archiving

Former Member
0 Kudos

HI,

WE have a situation where there has been a demerger of business.

now in the existing SAP environments there is a need to remove data of some company codes and keep data of other company codes.

Primarily the transaction data is in FI, CO and also some data in SD, MM modules.

what would be the approach to completely archive or delete the data of the company codes , transaction and master data ?

also what customizing settings are required to disable from any further data creation of the unwanted company codes ?

few topics researched  T.code : OBR1

new SAP ILM tools

please suggest an end to end solution that was successfully used  for a client.

MAny thanks in advance,

SAtya

Accepted Solutions (1)

Accepted Solutions (1)

JL23
Active Contributor
0 Kudos

You wont be able to archive the data completely. When companies leave a system then they usually do not clean up. Hence you have a lot open business cases. And as you should know you can only archive data from closed business cases, and only master data that has no usage, which means all transactional data is already archived.

I did such a project 10 years ago and was able to remove about 80% of the data, the rest will stay forever, nobody will ever give you a budget to close all those business cases and make them ready for archiving.

We had recently a huge restructuring project and did this with SLO tools, hereby we defined all data which had to be migrated and identified all organizations that are no longer with us. So we copied and migrated only the active data to the new system while the original data remained in the old system which got decommissioned. This way we could get rid of the unwanted data too.

But this was just a by-product of the reorganization project, otherwise we would still suffer.

Getting rid of data which belongs to inactive companies is often asked in user groups like DSAG, but SAP does not have anything smart to use.

It was said with ILM you can archive even the incomplete business cases, which is probably correct, but it does not remove the data from your system.

Honestly, why should one want to create new data in a company that is gone? If you want to prevent the accidental creation then remove the authorization for those organizations from the user roles.

0 Kudos

Hello,

Juergen's response is correct - with the small execption that the SAP ILM Solution does have functionality that will get rid of data that is not business complete.  When you implement the ILM Retention Management piece and create a policy for an archive object - it enhances the archive write job with a data destruction option.  This option will go out and delete/destroy the data even if it is not business complete.  You have to be really careful with this functionality as this process does not first write out an archive file and then run the delete job.  It does it all in one step and deletes the archive file when complete.  I have not tested this process yet, but, it is there.

Or, you can engage SAP's SLO services and they can carve out the old data as well.

Best Regards,

Karin Tillotson

JL23
Active Contributor
0 Kudos

This is really good to know, thanks Karin, I never understood it this way, that is even a strong argument pro ILM

0 Kudos

Thanks Jurgen - and agree, it is a very good argument to implement SAP ILM as this use case example is specfic for divestitures or old data that has already met its retention, and does not have any legal reasons to hold it, yet, the business does not have time to make the data business complete.

Best Regards,

Karin

Former Member
0 Kudos

Thanks a lot to both of your answers. it provides great insights .

Answers (1)

Answers (1)

Jelena
Active Contributor
0 Kudos

We're also dealing with sort of "demerger" situation and we were recommended the SAP Language Transformation. From what I understand, it removes the unneeded data too. It's additional license though. We haven't started the project yet, so no practical experience, unfortunately.