Optimising a testing landscape for Edwards with Data Sync Manager Mike Ellis Edwards Tim Barker EPI-USE Labs

Transcription

1 Optimising a testing landscape for Edwards with Data Sync Manager Mike Ellis Edwards Tim Barker EPI-USE Labs

2 Contents slide Who are Edwards Edwards Changing world SAP in Edwards Normal Landscape Challenges for Test systems Additional Test s

3 Market leader in vacuum & abatement

4 Edwards Changing World 2006 to 2014 Time line Major SAP Projects 2006 Move of Financial Year End SAP rollout to SE Asia SAP rollout Taiwan, SAP rollout Korea Move out of BOC data centre SAP rollout China, SAP rollout Japan SAP Upgrade, Re-implement CRM Change of Intercompany Pricing, Mobilisation for Manufacturing Project Rebuild SAP Security Purchase EPI-use 2013 Implement SAP SCM 2014 Move to IBM Cloud,SAP Manufacturing implemented Eastbourne Align Accounts to Atlas Copco

5 SAP at Edwards SAP ECC, CRM, BW and SCM implemented Each system single global Client Operational in 20 Countries 9 Languages loaded Approximately 1100 users Operational 24x7 (maintenance Saturday evening) s run from IBM SCE+ (Cloud) Unix & DB2 DR disk mirroring across data centres Interfaces to Manufacturing systems Approximately 3000 batch transfers per day Currently moving Manufacturing into SAP

6 Edwards SAP Normal Landscape TAE TAC CRM v6 Training DAE DAC DAB BI V7 DAA APO V5.1 Transport from Client 050 to 050 SAE SAC SAB BI V7 SAA APO V5.1 Transport from Client 050 to 050 PAE PAC CRM v6 PAB BI V7 PAA APO V5.1 Development s Test (Copy of Production) Production

7 Challenges for Test s Multiple Projects running in parallel All demanding Test systems (copies of production data) At peak we had requirements for 4 Test systems (one with 2 clients) Additional Hardware now had real commercial cost Previously it was an Internal cost based upon revenue 4 copies of Production (ECC & CRM) would require 10TB of data Projects needed differing amounts of transactional data between 1 18 months of transactional data Projects on differing timelines Require refresh of Test data at different times Refreshing full copies of production took 1 week per system and required our hosting partner to do work (chargeable)

8 Peak Additional Project s XAE XAA SCM v5.1 SCM Test YAE YAC CRM v6 XAE XAC BAU Test FAE FAC Finance and Security Test BAU Development s Copy of D systems CAE CAC Conversion Test (2 clients) DAE DAC DAB BI V7 DAA SCM V5.1 Transport from Client 050 to 050 SAE SAC SAB BI V7 SAA SCM V5.1 Transport from Client 050 to 050 Transport from Client 050 to 750 TAE TAC CRM v6 PAE PAC CRM v6 PAB BI V7 PAA SCM V5.1 Development s Test (Copy of Production) Training Production

9 Use of Data Sync Manager Previously the process to copy Production data to Test systems had been based on a full copy using traditional backup / restore methods. After we implemented DSM copy all Master data Takes a time slice of Transactional data Run Extract over Saturday evening/ Sunday morning Extract written to Unix Extract can be scheduled in advance status when running Refresh of Test environment reduced to 1 2 days Depends upon amount of data & size of test server Test systems between 320 GB (1 month) to 500GB (18 Months) Total SAN saved 7.5TB

10 Edwards Training Strategy: Historic Training s system had 2 Clients Golden Client Training Delivery Weekly Copy Golden to Delivery Client copy scheduled over weekend Manual Post processing Monday morning before training For Asia Testing Manual processes have to be done Sunday Golden Client 320GB Training Delivery 320GB Training Weekly Refresh

11 Edwards Training Strategy: Using DSM Build New Golden Training Client DSM copy 1 month Data from production Update with New Configuration New Programs Add converted data Set up links Set up User IDs Build DSM extract of whole new Golden Save to Unix Schedule weekly import of DSM exact Advantages 260GB saved No weekly post processing All scheduled Weekly DSM import Training Client 320GB Unix Table 60GB Training 1 off DSM Extract

12 Thank You Any Questions? Contact me: