1.2. sa pience be_tech_day_2012_-_balta_group_final


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

1.2. sa pience be_tech_day_2012_-_balta_group_final

  1. 1. Building one standardized SAPsolution using Solution Manager Bart Desloover Group ICT Manager Balta Industries Oliver Buyssens Competence Lead SAP Solution Manager SAPience.be Tech Day 2012 1
  2. 2. Expertum Founded begin 2006 Team of 50 SAP Experts and Project Managers Mission : Providing superior long-term customer and employee value Offering expertise in following domains • Finance • Supply Chain Management • Business Intelligence • Product Lifecycle Management • Project Management • SAP Solution Manager • GRC and Security • Netweaver • Own SME Solution: Value4SME SAP Service Partner, Channel Partner, Value Circle Partner SAPience.be Partner SAPience.be Tech Day 2012 2
  3. 3. Balta Group SAPience.be Tech Day 2012 3
  4. 4. Balta Group SAPience.be Tech Day 2012 4
  5. 5. Agenda System Landscape Overview A bit of History Drivers for the Project Why SAP Solution Manager? Overal Strategy Scope of the BPH Building the BPH Facts and Figures Lessons Learned Future Contact Details SAPience.be Tech Day 2012 5
  6. 6. System landscape SAPience.be Tech Day 2012 6
  7. 7. A bit of History 1999 : Start SAP implementation @ Balta Industries • SAP set-up for Broadloom KB Division (SAP 4.0B) 2004 : SAP set-up for Broadloom ITC Division • New SAP implementation based on SAP 4.6C 2 different SAP Broadloom solutions to be supported 2010 : Acquisition of Broadloom DOMO Division • Specific Domo SAP solution implemented  ? Which Solution to implement ? => One new SAP-template set-up fitting all Broadloom divisions SAPience.be Tech Day 2012 7
  8. 8. Drivers for the project Set-up of a Broadloom SAP template Documentation is scattered around • Many different solutions have been used in the passed (Folders / Portals / Wiki / …) Need for a new and clear test strategy and approach SAPience.be Tech Day 2012 8
  9. 9. Why SAP Solution Manager ?SAP Solution Manager is installed: Used for technical topics like EWA, MOPZ, etc Lot’s of information provided by SAP Support advisor on different SolMan functions offering added value SAP services Roadmap • Continuous Quality Checks • Improvement Services • Expert Services • Expert Guided Implementations SAPience.be Tech Day 2012 9
  10. 10. Overall strategy Template 3 Key Governance Concepts Reusability SAPience.be Tech Day 2012 10
  11. 11. Overall strategy SolMan is preferred tool for management of the SAP solution All Business-IT and IT related information and documentation is stored in SAP Solution Manager All End-User related information is stored outside SAP Solution Manager. (incl. integration) The BPH is the central point for both types BPH will serve as a Template for the Broadloom divisions*BPH : Business Process Hierarchy SAPience.be Tech Day 2012 11
  12. 12. Scope of BPH All E2E Business Processes where SAP is involved All interfaces with SAP For division Broadloom Template BPH Individual RollOuts Test Cases and Test Script BC Sets Compare and adjust SAPience.be Tech Day 2012 12
  13. 13. Building a BPH Initially started with a Core Team Build a BPH internally (trial and error) • Module based modeling • Ended up in lot of questions Coaching and Guidance by Expertum • Switch to concept of Services and Responsibilities • Start small with one process Advanced Returns Management Validation of the result by Core Team and Expertum consultants Approval of the Solution Roll out to other business processes SAPience.be Tech Day 2012 13
  14. 14. Levels of BP Management SAPience.be Tech Day 2012 14
  15. 15. Template Management SAPience.be Tech Day 2012 15
  16. 16. BPML Structure BPH based on Business Processes, not SAP modules 3-Level structure Use of Shortcuts for reusability Assignment • Transactions • Configuration + Documents • BC Sets • Test Cases • Test Scripts SAPience.be Tech Day 2012 16
  17. 17. Facts and Figure Lead Time : 1-year Effort : 30-40 mandays How many people in the Core Team : 6 persons How many processes documented : • 14 scenario’s • 77 business processes • 439 process steps SAPience.be Tech Day 2012 17
  18. 18. Lessons Learned Follow the Best Practices Define a clear strategy and scope, considering the E2E process, even when starting with one single functionality Think Big, Start Small to get a final solution BPH is not module based Governance module is a must IT people find it great Solution must be useable by everybody Regular reviews during the process led to changes in the strategy The basis need to be well defined and stable SAPience.be Tech Day 2012 18
  19. 19. Future enhancements Continuous process for enhancing the BPH • Extension for other scenarios like SD and PTP Elaborate on Test Management Perform further Roll Outs to the new plants using the template BPH Business Process Monitoring • Optimization of the Business Processes • Technical follow-up of Jobs, Queues, etc… Introduction of ChaRM process SolMan dashboards to be configured SAPience.be Tech Day 2012 19
  20. 20. Contact DetailsBart Desloover Oliver BuyssensGroup ICT Manager Expertum - CLE bart.desloover@baltagroup.com E oliver.buyssens@expertum.netW http://www.baltagroup.com W http://www.expertum.net M +32 471 60 95 00 SAPience.be Tech Day 2012 20
  21. 21. Thank you! Your logo SAPience.be Tech Day 2012 21