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

2. Improving SAP UsabilitywithInfoPath and Winshuttle Kristian Kalsing - Winshuttle

3. What I’ll cover Slide 3 Introduction to ERP usability challenges Business user solutions with InfoPath and Winshuttle Example scenario Success factors and benefits Key points to take home Questions

5. 57% of SAP customers don’t believe they’ve achieved a positive ROI from their implementation(Nucleus Research) Slide 4

6. Example of a complex of transaction process Slide 5 Creating a new employee in SAP requires the user to enter data into 25 separate screens

7. Example of a complex of transaction process Slide 6 With a consolidated form the process can be reduced from approximately 20 mins to 2 mins

8. Business user solutions Slide 7 Constant Business user solutions Complex Program TransactionProcess Rate of Change Manual Simple Dynamic 10 10 Million Records

10. InfoPath forms can bepublished to SharePoint asweb-enabled forms

11. Forms can be processed bySharePoint workflows

12. Data collected from users canbe posted to most businesssystems using web services Slide 8

13. Posting data to the ERP system Slide 9 Web Services Form ERP

14. Requesting web services from IT Slide 10 That sounds great, but we need to revisit our enterprise architecture first Can I please have a web service? You shouldn’t be doing that! Sorry, we don’t have the time or resources now

17. Example Slide 13 Build an alternative interface to SAP without writing a single line of code SAP transaction PA30 Add dependent(family member)to personnel

18. Example: Record transaction with Winshuttle Slide 14

19. Example: Complete transaction in SAP GUI Slide 15

20. Example: Transaction recorded successfully Slide 16

21. Example: Map relevant fields Slide 17

22. Example: Publish transaction as web service Slide 18

23. Example: Design form with InfoPath Slide 19

24. Example: Select web service Slide 20

25. Example: Fields automatically imported Slide 21

26. Example: Add fields and design visuals Slide 22

27. Example: Publish form to SharePoint Slide 23

28. Example: A new UI for an SAP transaction Slide 24

30. Populate dropdowns with data directly from web services

31. Minimise the replication of business rules

32. If the solution ends up with IT, then InfoPath probably isn’t the right tool

33. But an InfoPath prototype is often a great way to explain IT what you want

34. In SharePoint 2010, use the InfoPath Form Web Part to make forms an integral component of SharePoint sites Slide 25

35. Benefits of business user solutions Shortening of the solution development cycle Continuous optimisationand acceleration of business processes Outside-in approach as opposed to inside-out (role-specific solutions) Decentralisation of innovation,servingthe long tail of specialisedneeds Slide 26

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. In order to design InfoPath forms that submit data to the ERP system, business users need easy-to-understand reusable web services

39. The key challenge is defining a service enablement strategy that empowers business users to build the entire solution Slide 27

40. Key points to take home Usability improvements are not about esthetics but about accelerating business processes SharePoint and InfoPath provide UI tools for building alternative interfaces to standard ERP Service enablement is usually the real bottleneck for using InfoPath forms to post data to ERP There are a large number of use cases that are best served by solutions which are built entirely by business users Slide 28

41. Questions Slide 29 How to contact me… Kristian Kalsing Email: kristian.kalsing@winshuttle.com Blog: http://kalsing.blogspot.com Twitter: @kalsing