Improving SAP UsabilitywithInfoPath and Winshuttle<br />Kristian Kalsing - Winshuttle<br />
What I’ll cover<br />Slide 3<br />Introduction to ERP usability challenges<br />Business user solutions with InfoPath and ...
ERP usability challenges<br /><ul><li>More than 40% of ERP implementations experience user adoption issues or lack signifi...
57% of SAP customers don’t believe they’ve achieved a positive ROI from their implementation(Nucleus Research)</li></ul> S...
Example of a complex of transaction process<br /> Slide 5<br />Creating a new employee in SAP requires the user to enter d...
Example of a complex of transaction process<br /> Slide 6<br />With a consolidated form the process can be reduced from ap...
Business user solutions<br /> Slide 7<br />Constant<br />Business user solutions<br />Complex<br />Program<br />Transactio...
Collecting data with InfoPath<br /><ul><li>Business user tool for creating electronic data entry formswithout writing code
InfoPath forms can bepublished to SharePoint asweb-enabled forms
Forms can be processed bySharePoint workflows
Data collected from users canbe posted to most businesssystems using web services</li></ul> Slide 8<br />
Posting data to the ERP system<br /> Slide 9<br />Web Services<br />Form<br />ERP<br />
Requesting web services from IT<br /> Slide 10<br />That sounds great, but we need to revisit our enterprise architecture ...
Web services authored by business users<br /> Slide 11<br /><ul><li>Empowering business users to author and deploy their o...
These web services can then be utilisedin any UI design tool which understands web services such as InfoPath</li></li></ul...
Example<br /> Slide 13<br />Build an alternative interface to SAP without writing a single line of code<br />SAP transacti...
Example: Record transaction with Winshuttle<br /> Slide 14<br />
Example: Complete transaction in SAP GUI<br /> Slide 15<br />
Example: Transaction recorded successfully<br /> Slide 16<br />
Example: Map relevant fields<br /> Slide 17<br />
Example: Publish transaction as web service<br /> Slide 18<br />
Example: Design form with InfoPath<br /> Slide 19<br />
Example: Select web service<br /> Slide 20<br />
Example: Fields automatically imported<br /> Slide 21<br />
Example: Add fields and design visuals<br /> Slide 22<br />
Example: Publish form to SharePoint<br /> Slide 23<br />
Example: A new UI for an SAP transaction<br /> Slide 24<br />
Critical success factors	<br /><ul><li>Preserve the ERP system as the “single source of truth”
Populate dropdowns with data directly from web services
Upcoming SlideShare
Loading in …5
×

Improving SAP Usability with InfoPath and Winshuttle

4,851 views
4,658 views

Published on

Business user solutions utilising SharePoint, InfoPath and Winshuttle to provide alternative user interfaces for SAP, with no programming involved.

Published in: Technology, Design
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,851
On SlideShare
0
From Embeds
0
Number of Embeds
810
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Improving SAP Usability with InfoPath and Winshuttle

  1. 1.
  2. 2. Improving SAP UsabilitywithInfoPath and Winshuttle<br />Kristian Kalsing - Winshuttle<br />
  3. 3. What I’ll cover<br />Slide 3<br />Introduction to ERP usability challenges<br />Business user solutions with InfoPath and Winshuttle<br />Example scenario<br />Success factors and benefits<br />Key points to take home<br />Questions<br />
  4. 4. ERP usability challenges<br /><ul><li>More than 40% of ERP implementations experience user adoption issues or lack significant ROI(AMR research)
  5. 5. 57% of SAP customers don’t believe they’ve achieved a positive ROI from their implementation(Nucleus Research)</li></ul> Slide 4<br />
  6. 6. Example of a complex of transaction process<br /> Slide 5<br />Creating a new employee in SAP requires the user to enter data into 25 separate screens<br />
  7. 7. Example of a complex of transaction process<br /> Slide 6<br />With a consolidated form the process can be reduced from approximately 20 mins to 2 mins<br />
  8. 8. Business user solutions<br /> Slide 7<br />Constant<br />Business user solutions<br />Complex<br />Program<br />TransactionProcess<br />Rate of Change<br />Manual<br />Simple<br />Dynamic<br />10<br />10 Million<br />Records<br />
  9. 9. Collecting data with InfoPath<br /><ul><li>Business user tool for creating electronic data entry formswithout writing code
  10. 10. InfoPath forms can bepublished to SharePoint asweb-enabled forms
  11. 11. Forms can be processed bySharePoint workflows
  12. 12. Data collected from users canbe posted to most businesssystems using web services</li></ul> Slide 8<br />
  13. 13. Posting data to the ERP system<br /> Slide 9<br />Web Services<br />Form<br />ERP<br />
  14. 14. Requesting web services from IT<br /> Slide 10<br />That sounds great, but we need to revisit our enterprise architecture first<br />Can I please have a web service?<br />You shouldn’t be doing that!<br />Sorry, we don’t have the time or resources now<br />
  15. 15. Web services authored by business users<br /> Slide 11<br /><ul><li>Empowering business users to author and deploy their own web services removes the bottleneck for rapid development of creative business solutions
  16. 16. These web services can then be utilisedin any UI design tool which understands web services such as InfoPath</li></li></ul><li>Introducing Winshuttle<br />Author<br />Run<br />Host<br />Create Web Service<br />Governance Platform<br />Web Service Directory<br />SAP Credentials<br />Web Service Engine<br />PublishWebService<br />Record<br />Map<br />Publish<br />SelectWebService<br />Create InfoPath Form<br />Select<br />Design<br />Publish<br />Fill out and submit form<br />PublishForm<br /> Slide 12<br />
  17. 17. Example<br /> Slide 13<br />Build an alternative interface to SAP without writing a single line of code<br />SAP transaction PA30<br />Add dependent(family member)to personnel<br />
  18. 18. Example: Record transaction with Winshuttle<br /> Slide 14<br />
  19. 19. Example: Complete transaction in SAP GUI<br /> Slide 15<br />
  20. 20. Example: Transaction recorded successfully<br /> Slide 16<br />
  21. 21. Example: Map relevant fields<br /> Slide 17<br />
  22. 22. Example: Publish transaction as web service<br /> Slide 18<br />
  23. 23. Example: Design form with InfoPath<br /> Slide 19<br />
  24. 24. Example: Select web service<br /> Slide 20<br />
  25. 25. Example: Fields automatically imported<br /> Slide 21<br />
  26. 26. Example: Add fields and design visuals<br /> Slide 22<br />
  27. 27. Example: Publish form to SharePoint<br /> Slide 23<br />
  28. 28. Example: A new UI for an SAP transaction<br /> Slide 24<br />
  29. 29. Critical success factors <br /><ul><li>Preserve the ERP system as the “single source of truth”
  30. 30. Populate dropdowns with data directly from web services
  31. 31. Minimise the replication of business rules
  32. 32. If the solution ends up with IT, then InfoPath probably isn’t the right tool
  33. 33. But an InfoPath prototype is often a great way to explain IT what you want
  34. 34. In SharePoint 2010, use the InfoPath Form Web Part to make forms an integral component of SharePoint sites</li></ul> Slide 25<br />
  35. 35. Benefits of business user solutions<br />Shortening of the solution development cycle<br />Continuous optimisationand acceleration of business processes<br />Outside-in approach as opposed to inside-out (role-specific solutions)<br />Decentralisation of innovation,servingthe long tail of specialisedneeds<br /> Slide 26<br />
  36. 36. Taking SharePoint to the next level<br /><ul><li>SharePoint is increasingly becoming a de facto standard in the Office environment where information workers feel comfortable
  37. 37. Until now SharePoint has mainly been utilised as an intranet and collaboration platform with limited or no vertical integration into core business systems
  38. 38. In order to design InfoPath forms that submit data to the ERP system, business users need easy-to-understand reusable web services
  39. 39. The key challenge is defining a service enablement strategy that empowers business users to build the entire solution</li></ul> Slide 27<br />
  40. 40. Key points to take home<br />Usability improvements are not about esthetics but about accelerating business processes<br />SharePoint and InfoPath provide UI tools for building alternative interfaces to standard ERP<br />Service enablement is usually the real bottleneck for using InfoPath forms to post data to ERP<br />There are a large number of use cases that are best served by solutions which are built entirely by business users<br /> Slide 28<br />
  41. 41. Questions<br /> Slide 29<br />How to contact me…<br />Kristian Kalsing<br />Email: kristian.kalsing@winshuttle.com<br />Blog: http://kalsing.blogspot.com<br />Twitter: @kalsing<br />

×