O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Accelerating SAP Transactions with SharePoint and InfoPath

2.772 visualizações

Publicada em

Presentation from SAPPHIRE NOW and the ASUG Annual Conference 2011. Combining SharePoint and InfoPath with the Winshuttle Usability Platform provides an end-to-end framework for accelerating SAP transactions.

Publicada em: Tecnologia
  • Seja o primeiro a comentar

Accelerating SAP Transactions with SharePoint and InfoPath

  1. 1. Accelerating SAP transactions with SharePoint and InfoPath<br />Kristian Kalsing<br />Product Manager, Winshuttle<br />
  2. 2. 2<br />Overview<br />Accelerating processes<br />Example scenario<br />Introducing SharePoint and InfoPath<br />Demo solution<br />Best practices and benefits<br />Key learnings<br />Questions<br />
  3. 3. Accelerating Business Processes<br />3<br />
  4. 4. Complex Business Process<br />4<br />Creating a new employee in SAP requires the user to enter data into 25 separate screens<br />With a consolidated form the process can be reduced from approximately 20 mins to 2 mins<br />
  5. 5. Business User Solutions<br />5<br />Constant<br />Business user solutions<br />Complex<br />Program<br />TransactionProcess<br />Rate of Change<br />Simple<br />Dynamic<br />Manual<br />10<br />10 Million<br />Records<br />
  6. 6. Example<br />Ahab Coffee Company<br />6<br />Rollout of Health Benefit Scheme by HR<br />
  7. 7. Situation<br />Ahab 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.<br />7<br />
  8. 8. Problem<br />Ahab 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.<br />8<br />HR 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.<br />
  9. 9. Solution Requirements<br />Data entry of single records<br />Add dependent to personnel (PA30)<br />Remote enablement<br />Devolve task to managers andteam leaders<br />UI simplification<br />Users not trained in SAP HR<br />Alternative simple interface required<br />Short timeframe<br />No complex custom development<br />9<br />
  10. 10. Collecting Data with SharePoint and InfoPath<br />Business user tool for creating electronic data entry formswithout writing code<br />InfoPath forms can bepublished to SharePoint asweb-enabled forms<br />Forms can be processed bySharePoint workflows<br />Data collected from users canbe posted to most businesssystems using web services<br />10<br />
  11. 11. Posting Data to SAP<br />11<br />Web Services<br />Form<br />SAP<br />
  12. 12. Requesting Web Services from IT<br />12<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 />
  13. 13. Web Services Authored by Business Users<br />Empowering business users to author and deploy their own web services removes the bottleneck for rapid development of creative business solutions<br />These web services can then be utilized in any UI design tool which understands web services such as InfoPath<br />13<br />
  14. 14. Solution<br />Simple InfoPath form pushing data to SAP through Winshuttle deployed via SharePoint to Managers<br />14<br />
  15. 15. Example: Record transaction with Winshuttle<br />15<br />
  16. 16. Example: Complete transaction in SAP GUI<br />16<br />
  17. 17. Example: Transaction recorded successfully<br />17<br />
  18. 18. Example: Map relevant fields<br />18<br />
  19. 19. Example: Publish transaction as web service<br />19<br />
  20. 20. Example: Design form with InfoPath<br />20<br />
  21. 21. Example: Select web service<br />21<br />
  22. 22. Example: Fields automatically imported<br />22<br />
  23. 23. Example: Add fields and design visuals<br />23<br />
  24. 24. Example: Publish form to SharePoint<br />24<br />
  25. 25. Example: A new UI for an SAP transaction<br />25<br />
  26. 26. Combining SharePoint, InfoPath and 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 />InfoPath 2007/2010<br />Create InfoPath Form<br />Fill out and submit form<br />Select<br />Design<br />Publish<br />PublishForm<br />SharePoint2007/2010<br />26<br />
  27. 27. 27<br />Best Practices<br />Preserve the ERP system as the “single source of truth”<br />Populate dropdowns with data directly from web services<br />Minimize the replication of business rules<br />If the solution ends up with programmers in IT, then InfoPath probably isn’t the right tool<br />But an InfoPath prototype is often a great way to explain IT what you want<br />Leverage a no-programming platform for service enablement<br />Empower functional analysts and power users in the business to create and deploy web services<br />
  28. 28. Benefits of Business User Solutions<br />Solution development on business timeframes<br />Continuous optimization and acceleration of business processes<br />Outside-in approach as opposed to inside-out (role-specific solutions)<br />Decentralization of innovation, serving the long tail of specialized needs<br />28<br />
  29. 29. 29<br />Key Learnings<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 is a large number of use cases that are best served by solutions which are built entirely by business users<br />
  30. 30. ]<br /><ul><li>Thank you for participating.</li></ul>Please remember to complete and return your evaluation form following this session.<br />For ongoing education in this area of focus, visit www.asug.com.<br />SESSION CODE: <br />2205<br />