Monster Energy Energizes Its ERP Testing With Panaya

Transcription

1 Orange County Convention Center Orlando, Florida June 3-5, 2014 Monster Energy Energizes Its ERP Testing With Panaya Speakers: Tami Fox Monster Energy Avishai Shafir - Panaya

2 Typical Packaged ERP Systems Massive code base, configuration-centric 25,000 customization tables 160,000 application screens 400,000,000 lines of standard code Avg. 3,000,000 customer lines of code Mission Critical 24 X 365 uninterrupted operation 2

3 Constant Need for Change Rollout to New Sites Functional Enhancements Support Packs System Consolidation Upgrades IT-Driven Business-Driven Mergers & Acquisitions Regulations New Business Processes Enhancement Packages Migrations

4 The change process, today Initiate: Plan: IT Group IT Requirement Prepare Spec & Scope Business Users Business Requirement Build: Test: IT Manual Testing Develop Automatic Testing Off-Shore Testing Limited knowledge of real-life business processes which constantly change! Please test Please test Please test Please Please test test Please test Please test test Please Please test test Please test test Please test

5 The Constraints of Change, Today Compliance Methodologies Sponsor

6 Enable IT and Business to Accelerate Change, Together

7 7

8 Competing Forces of Testing Cost Quality & Risk Time to Market

9 Where are you today? Business Testing 40% IT Testing 30% IT Build 30% Maintenance 65% Innovation 35% Upgrade Functional Release Support Pack Functional Release Enhancement Pack Rollout to New Site

10 Where would you like to be? Business Business Testing Testing 25% 40% IT Testing 15% IT Build 30% IT Build 60% IT Testing 30% Maintenance 35% Maintenance 65% Innovation 35% Innovation 65% Upgrade Functional Release Support Pack Functional Release Enhancement Pack Rollout to New Site

11 The Solution Before Panaya Write Functional Test Scenarios Initial Testing Fix Unit Testing Integration Testing User Acceptance Testing Go-Live With Panaya Test Builder generates regression test suite Initial Testing Change Impact Simulation identifies what will break Automated Code Remediation cuts R&D time Test Scoping pinpoints Unit Testing, performed in Integration Testing focused on identified interface failures parallel to From 6-months to 3-months development Smooth go-live Collaborative Testing accelerates UAT and provides full progress visibility Go-Live

12 Panaya Quality Management Cloud Scope & accelerate the delivery of your SAP projects to ensure continuous quality of your SAP landscape.

13 ACCELERATING CHANGE THROUGH SAAS TECHNOLOGY Pinpoint exactly what to test reduce risk and effort Equip IT & business key-users with easy-touse testing tools accelerate manual testing, increase keyuser cooperation and productivity Govern the business quality process gain control and visibility 13

14 In All industries and Sizes Selling globally in 60+ countries 1,000+ customers 1M+ test cases in past year 14

15 Orange County Convention Center Orlando, Florida June 3-5, 2014 How Monster Energy Company exceled at ERP 6.0 testing with Panaya? Tami Fox

16 About Monster Energy Monster is a leading developer, marketer, sales, and distribution company in the alternative beverage category. HQ in Corona, CA 2,000+ employees across the world Running SAP for 4 years 16

17 SAP Environment - ECC 6.0 EHP 7 Financial Accounting (FI) Controlling (CO) Warehouse Management (WW) Materials Management (MM) Sales and Distribution (SD) Quality Management (QM) Vistex (VX) Business Warehouse(BW) Vertex RWD Uperform Opentext BPC Web Channel Enablement 17

18 The Challenge Upgrade from ECC 6.0 Ehp 5 to ECC 6.0 Ehp 7 Tracking progress and users assigned tasks Old excel scripts not kept up to date ~1500 changes 11 new companies No dedicated testing team Short window to implement upgrade (9 weeks) 18

19 The Solution Our Upgrade: Panaya s trial convinced us we could save time: Would streamline our test documentation Would allow super users to get involved Would allow us to focus our testing Manage a decentralized team Insight to what needed to be fixed and what we should test Ease of implementation and use of the tool 19

20 Implementation Analysis of System/Scoping Export of our Production Environment Compared to Panaya s Baseline EHP 7 20

21 Implementation The entire project was managed by the Panaya solution, including code corrections, testing, and user-defined tasks Step 1: Code Corrections (no pre-testing) 352 code corrections 21

22 Implementation Step 2: Unit Testing 326 tasks covering 240 transactions 22

23 Implementation Step 3: User Acceptance Testing 2,887 tasks, 5400 test runs 23

24 Implementation Step 4: Report & Monitor 24

25 Future Needs for Panaya Rollout to New Sites Functional Enhancements Support Packs System Consolidation Upgrades IT-Driven Business-Driven Mergers & Acquisitions Enhancement Packages Regulations New Business Processes Migrations

26 The Results Upgrade completed in 7 weeks vs 6 months Increased visibility to management Non-event go live Documentation of testing for Sox Compliance Test scripts for future use 26

27 Advice Advice Use a testing tool that will tell you what will break and what to test Use a tool which will prioritize tasks based on use Use a testing tool that is so easy to use that it allows everyone to get involved and to take some ownership of your upgrade Use a testing tool that will allow you to track testing results and report status 27

28 QUESTIONS?

29 FOLLOW US

30 THANK YOU THANK YOU FOR PARTICIPATING Please provide feedback on this session by completing a short survey via the event mobile application. SESSION CODE: 0811 For ongoing education on this area of focus, visit