The document discusses the acceleration of SAP transactions using SharePoint and InfoPath, presenting a scenario in which a company reduces data entry time significantly. It outlines a solution where business users can create electronic forms and post data to SAP without complex coding, thus resolving the challenge of adding family members' data for a new health benefit scheme. Key learnings highlight the importance of usability and business user empowerment in developing solutions that enhance process efficiency and innovation.

1. Accelerating SAP transactions with SharePoint and InfoPathKristian KalsingProduct Manager, Winshuttle

2. 2OverviewAccelerating processesExample scenarioIntroducing SharePoint and InfoPathDemo solutionBest practices and benefitsKey learningsQuestions

3. Accelerating Business Processes3

4. Complex Business Process4Creating a new employee in SAP requires the user to enter data into 25 separate screensWith a consolidated form the process can be reduced from approximately 20 mins to 2 mins

5. Business User Solutions5ConstantBusiness user solutionsComplexProgramTransactionProcessRate of ChangeSimpleDynamicManual1010 MillionRecords

6. ExampleAhab Coffee Company6Rollout of Health Benefit Scheme by HR

7. SituationAhab Coffee Company’s management team has decided to roll out a health benefit scheme for all of the company’s 3,000 employees and their immediate family. The scheme should be effective starting two months from now. The HR Manager has been tasked with ensuring the SAP HR system contains all the necessary information to support the scheme.7

8. ProblemAhab Coffee Company has not previously been tracking family members of employees in the SAP system. In order to roll out the benefit scheme, the HR Manager is faced with the challenge of adding family members to 3,000 employees in SAP within a very short timeframe.8HR does not have the resources to manually collect and enter the data. On the other hand, the two-month timeframe does not allow enough time for IT to develop a fully automated solution.

9. Solution RequirementsData entry of single recordsAdd dependent to personnel (PA30)Remote enablementDevolve task to managers andteam leadersUI simplificationUsers not trained in SAP HRAlternative simple interface requiredShort timeframeNo complex custom development9

10. Collecting Data with SharePoint and InfoPathBusiness user tool for creating electronic data entry formswithout writing codeInfoPath forms can bepublished to SharePoint asweb-enabled formsForms can be processed bySharePoint workflowsData collected from users canbe posted to most businesssystems using web services10

11. Posting Data to SAP11Web ServicesFormSAP

12. Requesting Web Services from IT12That sounds great,but we need to revisit our enterprise architecture firstCan I please have a web service?You shouldn’t be doing that!Sorry, we don’t have the time or resources now

13. Web Services Authored by Business UsersEmpowering business users to author and deploy their own web services removes the bottleneck for rapid development of creative business solutionsThese web services can then be utilized in any UI design tool which understands web services such as InfoPath13

14. SolutionSimple InfoPath form pushing data to SAP through Winshuttle deployed via SharePoint to Managers14

15. Example: Record transaction with Winshuttle15

16. Example: Complete transaction in SAP GUI16

17. Example: Transaction recorded successfully17

18. Example: Map relevant fields18

19. Example: Publish transaction as web service19

20. Example: Design form with InfoPath20

21. Example: Select web service21

22. Example: Fields automatically imported22

23. Example: Add fields and design visuals23

24. Example: Publish form to SharePoint24

25. Example: A new UI for an SAP transaction25

26. Combining SharePoint, InfoPath and WinshuttleAuthorRunHostCreate Web ServiceGovernance PlatformWeb Service DirectorySAP CredentialsWeb Service EnginePublishWebServiceRecordMapPublishSelectWebServiceInfoPath 2007/2010Create InfoPath FormFill out and submit formSelectDesignPublishPublishFormSharePoint2007/201026

27. 27Best PracticesPreserve the ERP system as the “single source of truth”Populate dropdowns with data directly from web servicesMinimize the replication of business rulesIf the solution ends up with programmers in IT, then InfoPath probably isn’t the right toolBut an InfoPath prototype is often a great way to explain IT what you wantLeverage a no-programming platform for service enablementEmpower functional analysts and power users in the business to create and deploy web services

28. Benefits of Business User SolutionsSolution development on business timeframesContinuous optimization and acceleration of business processesOutside-in approach as opposed to inside-out (role-specific solutions)Decentralization of innovation, serving the long tail of specialized needs28

29. 29Key LearningsUsability improvements are not about esthetics but about accelerating business processesSharePoint and InfoPath provide UI tools for building alternative interfaces to standard ERPService enablement is usually the real bottleneck for using InfoPath forms to post data to ERPThere is a large number of use cases that are best served by solutions which are built entirely by business users

30. ]Thank you for participating.Please remember to complete and return your evaluation form following this session.For ongoing education in this area of focus, visit www.asug.com.SESSION CODE: 2205