If you are looking for a real-world application that showcases how to expose data from SAP using the 2007 Microsoft Office system here's one:
Long story short, the Microsoft IT department designed and implemented a Price Exception Management application using a custom Office Business Application solution. This solution exposes and synchronizes real-time data in SAP, and provides a workflow routing and approval component that helps provide a consistent user interface (UI) for approvers.
I had the opportunity to work with some of the developers and program managers of this application. We thought it would be quite interesting to share with the developer community how this application was built and what can be accomplished by creating custom Office Business Applications that help solve business problems. Office Business Applications are a new breed of applications that use the Microsoft Office system to find and surface LOB information. Office Business Applications enable businesses to extend the Microsoft Office clients and servers into business processes running in LOB applications.
What is a pricing exception management solution?
Sales employees in the field can request special deals and discounts for products for different markets. Depending on the promotion, an approval request can be routed to different managers. If a request is approved, the price change and request should be synchronized to a pricing system (SAP) and the sales employee that requested the promotion should be notified of approval.
To create this workflow, the Microsoft IT department used different technologies including ASP.NET, Windows Workflow Foundation, Windows Communication Foundation, Windows SharePoint Services 3.0, Microsoft Office SharePoint Server 2007, Excel 2007, and the Open XML File Formats.
One of the most interesting components of this application is a set of Excel 2007 spreadsheets used to store notification and routing rules. These spreadsheets are used as decision tables and a workflow routing and approval process component reduces the time of the importing those rules by parsing the underlying Open XML File Formats files that make up an .xlsx file.
Because this is an application running in a production environment, we couldn't disclose detailed implementation details. However, we were as thorough as we could to share with you the architecture details of this solution.
We also created a video that walks you through the overall workflow and different components that make this solution.
Watch video in full screen
We hope this article and video can help you understand how OBAs can enable businesses to extend the Microsoft Office clients and servers into business processes running in LOB applications.
Visual Studio Tools for the Office system (3.0) is the key developer technology that enables you to create scalable, LOB solutions for Microsoft Office by using the Office development features included with Visual Studio 2008.
Steve Fox and I thought it would be a great idea to write an article that talks about the evolution of Visual Studio Tools for Microsoft Office and Office Development, how it all relates to Office Business Applications, the different business productivity solutions you can build using VSTO, and a brief overview of the rich set of features with which to build and deploy customized Office Business Applications using VSTO. We also provided links to resources that provide a deep dive to each feature.
The figure below shows the benefits of VSTO 3.0:
I really recommend reading our article. It is a good resource that will help you get started with Office development in Visual Studio 2008.
Also, if you are looking for detailed code samples, videos, and articles related to VSTO 3.0, please explore our MSDN technical articles, Visual How Tos, and reference documentation. Of course. the VSTO team blog is a must see.