1. Managing Change in Production BW at General Mills Mike Ruesewald Cindy Burlet Chris Gunn

2. So, you’ve just implemented your first BW application…… Congratulations! ……Now the hard part begins.

3. Dealing with nonstop change… BW patches SEM, APO, CRM OSS Notes New BW development R/3 upgrades Plug-in releases Database upgrades New Hardware While keeping production alive

4. Agenda Setting the stage – the BW environment at General Mills Change from outside your company Self-inflicted change Final thoughts Our goal: to share what we’ve learned – the good and the bad – in two year’s work with BW

5. General Mills BW at Go Live Driver – parallel with big-bang R/3 implementation April 2001 Team – 4 internal + 3 consultants BW 2.0B patch…. Plug-in 2001.1 Oracle 8.0 12 ODS tables, 0 cubes 250 GB

6. General Mills BW today Driver – decommissioning of legacy platforms Team – 10 internal + 10 consultants BW 3.0B patch 10 Plug-in 2002.2 patch 2 (R3 4.6C) Oracle 8.1.4 20 ODS tables, 15 cubes, 1 TB SEM (live), APO (summer 03)

7. General Mills BW by next ASUG Driver – deliver new reporting solutions Team – more internal, a lot less consulting! BW 3.1B patch…. Plug-in 2003.2 (R/3 Enterprise) Oracle 9i 25 ODS ~30 cubes, 1+ TB SEM (more), APO (more), R/3 Enterprise

8. Instance Environment Q/AParallel test Production Development R/3 SEMAPO BW Full size

9. Cindy Burlet cindy.burlet@genmills.com External Change What others do to us

10. External Change Patches and Plug-ins BW Version Upgrades Basis Upgrades R/3 Hotpacks OSS Notes Oracle Hardware Operating System SAP GUI APO & SEM Third Party Scheduler

11. External Change Many external changes to track and coordinate. Try to coordinate as many upgrades/ changes as possible to avoid constant flux of environment. Patch and plug-in upgrades scheduled every 6 months with the release of new plug-in. Allows us to schedule a project that will require one resource to test both patches and plug-in

12. External Change BW is a fast changing environment requiring flexibility. We are able to put these in a separate environment off of the transport path for extensive testing. Rate of change is greater than for R/3.

13. External Change Need to ensure coordination happens between BW and additional SAP components (APO, SEM, CRM, etc.) Need defined processes and test plans for all external change.

14. External Change Initial Assessment Current Environment Where you’re going Conflicting activities

15. External Change Prior to an Upgrade Setup a separate instance off of the transport path Setup test load schedule including; Master Data, Transaction Data, COPA realignment, ABAP’s and Cubes Perform baseline timings on loads BEx Queries and Reports identified with baselines Setup issue log

16. External Change Setup tests for external software (Datastage) Identify tests for Report Agent SEM and APO BEx functionality Statistics Cube Apply additional OSS notes

17. External Change UPGRADE PLAN Before Plug-in Need to ensure the setup tables are empty - can check these running the ABAP - RMCEX_SETUP_ENTRIES (via se38 in the ER* environment). If there are entries - delete them using LBWG by component (ie - 02 - Purchasing, 08 - Shipments, etc...) then run the ABAP again to ensure these are clear. After the ERP is down-run V3 updates (LBWE) to clear SM13. Pull the extractors into BW to clear R3 delta queue(RSA7)

18. External Change After R3 Plug-in – Perform BW tasks Replicate All Data Sources Activate Transfer structures (RS_TRANSTRU_ACTIVATE_ALL) Activate Infosets and Datasources Transfer Application Component Apply additional OSS notes Perform Post Upgrade Testing Validate data integrity using compare ABAP’s

19. External Change Summary BW is a very integrated system impacted by many external environments Communication, Communication, Communication Coordination Detailed implementation and test plans

20. External Change The art of progress is to preserve order amid change and to preserve change amid order. Alfred North Whitehead Alfred North Whitehead

21. Internal Change Chris Gunn What we do to ourselves

22. Internal Change BW Development Methodology One Developer –Designing –Coding –Testing –Transporting –Implementing

23. Internal Change Multiple projects touching the same objects No Source Control

24. Internal Change What if there wasn’t any Change Control? Lots of Questions. No Answers

25. Internal Change What does change control do? Answers Questions. Provides Tracking

26. Internal Change Change Control Process Communication Transport Management

27. Internal Change Process Document Change Requests (Data Base). Easy to user Simple for the reader Right to the point

28. Internal Change Documentation Impact Responsibility Change Details Object Transport

29. Internal Change

30. Communication Team – Object Migration Customers - Problems

31. Internal Change Team Communication

32. Internal Change Customer Communication Date Situation Action Estimate Time of Completion Data Integrity Issues Contact

33. Internal Change Customer Communication

34. Internal Change Transport Management Automated Import to Q & S Instances Collision Awareness – Stop problems before they start Custom ABAP – Reports Objects in multiple transports

36. Future Opportunities for Customers & SAP Mike Ruesewald

37. Our Next Opportunities Measuring impact of change, over time, on stability –Use of Change Management DB to assess change & incident correlation Measuring impact of change on performance –Tracking batch & query times –Example: master data loads slowed as more cubes added navigational attributes

38. Change Control Wish list for SAP Transport mechanisms adapted to BW Delivered data audit capabilities Source version control & back out ability Zero down-time changes for V3 extractors (Delta Update) Ability to compare objects between instances ( Production vs. Development)

39. Thank you for attending! Feel free to email us with questions mike.ruesewald@genmills.com cindy.burlet@genmills.com chris.gunn@genmills.com mike.ruesewald@genmills.com cindy.burlet@genmills.com chris.gunn@genmills.com Please remember to complete and return your evaluation form following this session. Session Code: 311