Client Export Process- Production Client Data using DSM tool / EPI-USE method

[ashwani1]

Introduction:

As explained the complete process involved in the client copy back using EPI-USE method in my previous blog post <Process Overview of Client Refresh using EPI-USE method> . I'll now go over Phase 2 of my earlier blog post, which describes how to export production data using the DSM tool.

Pre-requisite:

SAP Production Downtime: - During this entire process, we need downtime of production system in order to export the production client data. The idea is, there shouldn't be any open transactions when the production system data is exported.

Execution Steps: - 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.

T-Code: SA38 or SE38 -> Run report BTCTRNS1 -> F8/Execute 

• Lock all business users, make sure your user ID should not be locked.

T-Code: SU10 or EWZ5 you can lock mass users.

• Run DSM DB Optimization Jobs

T-Code: /n/USE/CS

• 
  
  
  
  • Click on Environment Menu > Administration.
  
  
  • Select Optimization Program
  
  
  • Execute in Background in all OLTP systems.
  
  
  
  

• Run DSM DB Consistency Check Jobs

T-Code: /n/USE/CS

• 
  
  
  
  • Click on Environment Menu > Administration.
  
  
  • Select Database Consistency Check.
  
  
  • Execute in Background in all OLTP systems.
  
  
  
  

• IMPORT client sync grouping file., To maintain the list of tables to be included and excluded from Client Sync with the Client Sync Groupings

T-Code: /n/USE/CS

• 
  
  
  
  • Click on Environment Menu > Administration.
  
  
  • Select Client Sync Grouping à
  
  
  • Select the grouping profile, it may be in txt or excel template, you need to select and import it.
  
  
  • After importing click on Save.
  
  
  
  

• Generate All Groupings and Generate all Profiles manually.

• Time Slice - For Client sync export you need to agree from the customer for how many month data to be exported. For example, last one years or last two year it’s totally depend on customer requirement.

• BAU Client Data Export - Source System Client Sync export

          T-Code: /n/USE/CS

• 
  
  
  
  • Click on Client Sync
  
  
  
  

• 
  
  
  
  • Give Description
  
  
  • Client Sync Profile: Select Transactional Data
  
  
  • Select Time Slice under Application Data as decided by customer.
  
  
  • Select check mark Resolve incomplete document flows.
  
  
  • Select Master Data
  
  
  • And keep selection check mark as per below screenshot.
  
  
  
  

• 
  
  
  
  • Click on execution option.
  
  
  • Select Transfer type: File Export Sync
  
  
  
  


• 
  
  
  
  • Click Parallel processing and increase some number if background work process is available and click set details.
  
  
  
  

• 
  
  
  
  • Click on Scheduling and click Immediate and Click on Execute Sync
  
  
  
  

                It will now run in the background and take some time, depending on the size of the database and the time slice.

---------

                  After finishing the Client export it will show as below screenshot

Finished Client Export Data from Production Client.

---

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

• Unlock all business users.

T-Code: SU10 or EWZ5 you can lock mass users.

• Release batch jobs.

T-Code: SA38 or SE38 -> Run report BTCTRNS2 -> F8/Execute 

---

Conclusion:

Using the EPI-USE/DSM tool, I have discussed production client data export methods and execution procedures in this blog. You may finish the entire production client data export process with the help of this blog.

----------------------

I hope this blog post is useful to you. Your thoughts and suggestions are welcome.

Thanks for reading this article !