1 / 17

Migrating to mySAP: Pitfalls and Lessons

Migrating to mySAP: Pitfalls and Lessons. Presented by: Krishna Kumar, Vice President , Ness Technologies. Introduction. Ness Technologies Global SAP Partner Over 600 consultants, globally 100s of customers in multiple IS solutions

abrianna
Download Presentation

Migrating to mySAP: Pitfalls and Lessons

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Migrating to mySAP: Pitfalls and Lessons Presented by: Krishna Kumar, Vice President , Ness Technologies

  2. Introduction • Ness Technologies • Global SAP Partner • Over 600 consultants, globally • 100s of customers in multiple IS solutions • Specific domain expertise in CPG, Retail, Public Sector, Consumer Electronics and Life-sciences • Presence in over 13 countries • Productivity tools that help in blueprint validation, accelerated implementation

  3. Presentation Objectives • Why mySAP • Broad migration guidelines • Who should migrate • Building a case • mySAP sample business cases • Tips on building a mySAP Case • Tips and Lessons • Implementation best practice • Typical pitfalls • Tiding over implementation issues

  4. mySAP Landscape Industry Breadth Value Chain Solutions

  5. Associating with User Pain “You can only be smart at hindsight” “C” Costly Business Sponsor Tactical System NOT Strategic Project Manager Process Gaps Incomplete Blueprint Lengthy implementations IT Member Complicated system, Too Generic, Unpredictable

  6. mySAP Migration • Identify • The correct BW architecture • Right mySAP processes • Master-slave data flow • Integration strategy • Benefit benchmarks • Master data strategy • Portal strategy • KPIs that measure success

  7. New implementations Maintenance runs out Technical upgrade Functional upgrade mySAP Implementation Reasons

  8. CORE R/3 Upgrade I KNOW what functionality to expect I KNOW the impact to the landscape I CAN plan my resources I CAN estimate my ROI strategic notional mySAP migration What in the mySAP suite should I implement? How can I benefit from better analytics? How do I know what data to aggregate? What is my ROI? Can I incrementally grow my mySAP landscape? Data = “Jack goes to Italian restaurants 4 times a week” tactical well-defined Information = “Jack likes Italian food” The philosophy behind mySAP Core R/3 Core R/3 Upgrade is ‘Technical’ in nature with Basic Functionality changes mySAP Suite Core R/3 Functionality enhancement is immense and intricate

  9. mySAP at a glance BW – SEM Stack Service Mgmt Market Analytics Consumer profiles Order Fulfillment Opportunity Mgmt Product Association Capacity Planning Plan to Actions Inventory Mgmt Order Fulfillment Demand Planning Global Availability Market price Procurement trends Vendor Scorecard Spend Analysis CRM APO SRM

  10. Business Case • A watch manufacturer wants to plan production based on BOM • Plan based on end consumer demographics • Minimize supply-chain latency Building a Case: mySAP APO • Problem • His SOP (operations planning) only supports 9 characteristics • His Supply Network has no visibility certain component demand • Solution • mySAP SCM – DP – Demand planning supports 256 attributes • But is his APO investment worth the returns?

  11. Building a Case: mySAP APO $45M worth of orders created with unplanned variants His planning exposure is $45M

  12. Building a Case: mySAP CRM • Business Case • Internet Service Provider wants to reduce returns processing • Profile his install base better • Reduce the cost of reverse processing • mySAP CRM Service offering • What ? When ? Where ? How?

  13. Building a Case: mySAP CRM MDX MDX MDX Increase in Returns

  14. After Before $63 M lost Churn reduced to $23 M Incentive cost = 6 M Potential Savings = 34 M$ CFO VP Sales Return value / Product Value = 1.9 % 0.6 % EPS = 0.03 VP Product Mgmt 0.1 % Return value / Investment = 0.4% VP Engg Building a Case: mySAP CRM

  15. mySAP Tip: Best Practice Profiling Assessment Execution Advice Implement

  16. mySAP Migration Tip: Know what you want • Upgrade reasons • Maintenance expiration , if 4.5 or below • Planning on EAI expansion – think NetWeaver • Think “one-stop-shop” – SAP has them all • Unicode them: Multi-lingual, global IT compliance • Business expansion • Explore mySAP ERP + NetWeaver : Complete IT pack • Mitigate collateral impact, validate your blueprint with data • Functionality expansion • Think BW first. Your value chain is only as good as the intelligence • Validate your mySAP goals with historical data

  17. “Look before you Leap” • Plan • Your mySAP “must-haves” • Your data flow • Your BW • Implement • Your value chains • Analytics • Optimize • Your consumer connections • Information pervasiveness

More Related