on 05-08-2023 10:48 AM
hi team
in SAP ECC , in data migration, you could request a new environment to start with a fresh data set when the current environment was getting polluted with trial and error data
in S/4 public, the 2 tier situation was blocking and data cleansing
now SAP has launched S/4 3 tier architecture/environment set up. keep in mind, the same situation will occur, we have migration cockpit data being optimized and loaded, alongside keyuser and end user functional transactions, how to (periodically) cleanse the eco system
any experiences/tips and trics?
Thanks & regards
Bert
Hi Bert,
Thank you for your question. SAP S/4HANA Cloud, 2-system landscape, has a Test Data Refresh service that can be purchased with a yearly subscription (https://help.sap.com/docs/SAP_S4HANA_CLOUD/a630d57fc5004c6383e7a81efee7a8bb/426ffb7ccc58439b805dc2c68c259904.html). However, this service is not available for 3-system landscape yet. It is currently in a pilot program.
I would recommend you use your starter system to test data loading as much as possible before starting to load into the development system, so that you do not require as much data cleansing.
Best,
Aanchal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aanchal,
thanks for the swift answer, any alternatives in the intermediate period before test data refresh service is available, how do other project rinse their eco system, any mass update functionality (like in ECC) so you can flag them or make it recognizable or flagged for deletion or so...
thanks & warm regards
Bert
Hi vincent.zhu was wondering,
is there a possibility to cleanse migration data from Test
and....
can you create multiple test mandants/environments in the test system (like in on prem Sap)
looking forward to your answer....
best regards
Bert
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi chriszhu , thanks for your answer!
this implies the D system is also connected to other systems as well, to functionally test the results of the data migration (especially tier 3data ; transactional)
still remains the question of cleansing the data. I think there is only 1 instance in D and T (not multiple mandants) , so how to cleanse this, only once a year, or on demand (monthly) . or smart removal/de-activation
please do respond
Regards
Bert
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
with 3SL, I would recommend to do migration test in D system as many as enough.
And only migrate the production-like data into T system, as we would like to maintain the T system as close to P system as possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
105 | |
8 | |
6 | |
6 | |
5 | |
5 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.