Skip to Content
avatar image
Former Member

SLO Data Integrity check


Currently we have 10 company codes in our production system (e.g. Company Code P01 ~ P10)

However, there is a requirement that 1 (one) of them need to be separated/migrated into separated system (eg. Company code P10)

The idea is to copy client using SLO, then purge the data so the copy client will only contain the data of Company code P10.

Can anybody give me advise on how to test the data integrity efficiently in the copy client after data purging processes?

I am afraid that there will be data corruption exist during the data purging.

Additional information, we have 11 SAP modules involved.

Thanks in advance.


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jun 25, 2014 at 03:08 AM

    Hi Arif,

    We faced a similar scenario andSLO was used in separating on of our company code's data.

    There was no data corruption nor any major issue. However, we designed a testing cycle included all other teams comprising people from all modules to design test cases and scenarios.

    From Basis perspective, SLO was done from SAP and post-processing was standard verification done from our side.



    Add comment
    10|10000 characters needed characters exceeded