Process Overview of Client Refresh using EPI-USE method

Introduction:

The EPI-USE Labs‘ Data Sync Manager (also called as DSM Tool) suite is the simplest, most effective way to copy and mask data between and within any SAP ABAP stack landscape. With DSM, you can rapidly create new non-production systems, reduce the footprint when refreshing existing test clients or creating new ones, and copy selected data on demand, all with integrated scrambling of data for security, which will help you to get real SAP data into non-production systems for testing, training, and support. A client copy back involves refreshing the data of the existing target client (from Production to Quality or pre-prod).

Data Sync Manager (DSM) is certified by SAP for ‘Integration with SAP S/4HANA’ and ‘Integration with SAP S/4HANA Cloud’. DSM5 also ‘works with RISE with SAP’.

Benefits of Data Sync Manager:

• Shrink your test systems by 75%.
• Reduce your manual workload.
• Increase scrambling coverage by 80%.
• Always have relevant, up-to-date data in non-production system.
• Copy data consistently across system landscapes and include cross system and cross application transaction flows.
• None of the lengthy post-processing time.
• Time-slice of data from production while in exporting data.
• Ensuring data accuracy.

Challenges in the standard refresh procedures like:

• In the standard client copy is lengthy refresh process on SAP systems.
• It also requires equal amount of storage on the target system.
• Taking more downtime of target systems.
• Database team involvement requires.
• It requires more planning with Database, Infra & SAP Basis Team.

Note – This blog post does not cover about the installation and setup of Data Sync Manager. It is license-based product most of the configuration part will be taking care by the authorized vendor.

Planning, Preparation and Execution:

Generally, customer data is required to test in the quality system example like during HRSP UAT, so customer always insist to copy the production data into quality system. Therefore, I am going to perform client copy of SAP ECC from Production Client to Quality Client. To execute the process, I have separated in multiple phases as below.

Phase 1 – Preparation – SOURCE & TARGET Systems

• Prepare storage where data going to export. It will be already configured the location so before taking export date check the disk space.
• Read write permission on the location where data is exporting.
• User and authorization check on source and target for TCode: /n/USE/CS
• Basis & Functional Pre-checks need to be started in this phase only.

Phase 2 – Client Export – SOURCE (Production Client) System

• Batch Job Suspension, there should not be any active jobs, if any wait for completion or if very long running job cancel it after taking approval from process owner.
• Lock all business users, make sure your user ID should not be locked.
• Run DSM DB Optimization Jobs
• Run DSM DB Consistency Check Jobs
• IMPORT client sync grouping file.
• Time Slice – For Client sync export you need to agree from the customer for how many month data to be exported.
• BAU Client Data Export – Source System Client Sync export

Phase 3 – Post Client Export – SOURCE (Production Client) System

• Unlock all business users.
• Release batch jobs.

Phase 4 – Preparation – TARGET (Quality Client) System

• Delta TR list: Prepare the TR list, which TR is imported into quality client but not in production client, those TR list you need to send the list to the customer and take confirmation which transport request to be reimported into QAS.
• Send outage notification to customer.
• Batch Job Suspension, there should not be any active jobs, if any wait for completion or if very long running job cancel it after taking approval from process owner.
• Lock all business users, make sure your user ID should not be locked.
• SAP System shutdown.
• Take Database backup.
• Put DB in Simple recovery model in MS-SQL or if you are using other database in simple switch off the data archive.
• Detach cluster from DB, Remove Availability Group, if cluster is configured in your environment.
• SAP System start.
• Take SAP file system, profile backup.
• Remove child from CUA if configured in your landscape.
• User master export – SAP_USER, Using EPI-USE Method.
• Deactivate the System from ChaRM if configured in your landscape.

Phase 5 – Client Delete – TARGET (Quality Client) System

• Check profile parameter for SAP* login and change in the value as 0 (zero) if not set.
• SAP System shutdown/start to activate the profile parameter if you changed.
• Delete SAP* user from the client, which you want to delete the client, if required delete from DB level.
• Perform client delete using EPI-USE method.

Phase 6 – Client Import – TARGET (Quality Client) System

• Client sync media transfer if necessary.
• Check permissible directory.
• Import Client Sync Groupings.
• DSM Client Sync import of Production data into Quality client.

Phase 7 – Post Client Import – TARGET (Quality Client) System

• Perform user master import.
• Perform R3trans script import.
• Execute redbook entries for Basis.
• Perform post activities, BDLS & SGEN SecStore etc.
• Reset Table Buffer – /$TAB.
• Run report RSUSR405.
• Check / Clean up Batch Jobs.
• Clean up Security Audit Log files.
• NUMBER_RANGE check report.
• Activate workflow processing.
• Ensure SAP Standard Jobs are released.
• Clean up Source System History.
• Clean up Central Performance History.
• Check SLD settings and connection.
• Change System settings – SE06, Change to Not Modifiable and Save.
• Update Login Screen with Client Information.
• Check Short Dumps.
• SCOT Mail Configuration.
• Import Delta TRs.
• Set password for DDIC & SAP* in all clients.
• License Check.
• Validations and Post-checks – Basis scope.
• Revert SAP Profile Parameter, login/no_automatic_user_sapstar = 1
• SAP System shutdown.
• Put DB in Full recovery model.
• Take Full DB Offline backup from Primary DB server.
• Restore DB Offline backup in Secondary DB server.
• Attach cluster from DB, Add in Availability Group Database if cluster configured.
• SAP System start.
• Functional users unlock and send email to the functional team to check and validate post client copy.
• User ID unlock for UAT.
• Post Database backup.
• Sign-Off from the customer.
• All business users unlock.
• Release batch jobs.

Conclusion:

In this blog I have covered execution procedures and explained about client refresh using EPI-USE tool. With this blog you can execute from planning to completion of client refresh.

In the upcoming days, I will also cover the step-by-step instructions for client export, client delete, and client import procedures.

————————

Hopefully this blog post will help you. I look forward to your comments and feedback.

Thanks for reading this article !

Regards,

Ashwani Kumar

Reference: DSM Tool Process Guide