Kristian Kalsing

Export SAP data to SharePoint with Winshuttle Query

noreply@blogger.com (Kristian Kalsing) — Thu, 16 Feb 2012 23:28:00 +0000

When business users are automating processes by essentially building applications in SharePoint, there are often use cases where a solution needs to include data from SAP. It could be mash-up scenarios between SharePoint content and SAP data or it could be simple use cases where having SAP data in SharePoint for easy access makes sense.

There are many ways of achieving this through custom programming. However, what I wanted to bring to your attention here is a new feature of Winshuttle Query which effectively empowers a business user to create an SAP data query and export the extract to a SharePoint list without writing any code.

I have recorded a five-minute video that demonstrates how this works. The video shows the desktop approach which is handy for quick prototypes and ad-hoc requirements. There is also an enterprise version of this functionality where the data queries can be scheduled to run regularly on a server, automatically keeping the SharePoint lists in sync with the SAP tables. Apologies if my voice sounds a bit muffled on the video. I blame Camtasia’s voice optimisation.

Speaking at the European SharePoint Conference in Berlin

noreply@blogger.com (Kristian Kalsing) — Thu, 13 Oct 2011 10:03:00 +0000

After an awesome few days at the WUG conference in Chicago, I’m headed for Berlin next week to speak at the European SharePoint Conference. I’ll be talking about how SAP customers can utilise SharePoint as a platform for optimising SAP-centric business processes. Although my talk is centered around SAP, the issues and solutions discussed are relevant to any large ERP back-end. Here’s the session outline:

Accelerating SAP Transactions with SharePoint and InfoPath
Data entry into SAP can in many cases lead to complex business processes taking up unnecessary time and resources throughout the organisation. Enterprises can achieve significant cost-savings by providing alternative interfaces that simplifies data entry and increases user adoption.
Considering SharePoint's popularity amongst business users, it provides an immense opportunity for delivering SAP transactions to the broader user base. As an integrated part of the SharePoint platform, InfoPath is a tool for creating electronic forms which can be utilized by business users to rapidly create fit-for-purpose user interfaces for SAP.
In this session, you will learn what it takes to surface SAP transactions in SharePoint solutions following an approach that is entirely driven by business users. In particular you will see specific examples of how a business user can utilize SharePoint and InfoPath to build alternative user interfaces for SAP, with no programming involved.

I’ll be keen to connect with anyone at the conference who wants to discuss SAP/SharePoint integration and/or workflow for SharePoint in general. I will also be looking for a SharePoint talent to join our European team. Just ping me on Twitter (@kalsing) and we can arrange to meet. I look forward to meeting you!

Wrap-up from the Winshuttle User Group conference in Chicago

noreply@blogger.com (Kristian Kalsing) — Wed, 12 Oct 2011 20:15:00 +0000

The annual Winshuttle User Group (WUG) conference has been the sole focus of my attention the last few days. After the inaugural event in New Orleans last year and follow-up events in London and Paris earlier this year, the WUG has grown exponentially into a sizable affair with more than 400 Winshuttle enthusiasts gathered to share experiences, attend customer presentations, participate in training classes and engage with the Winshuttle Partner Network.

The show was kicked off Monday with a keynote that included a solution demo by Winshuttle Co-Founder Vikram Chalana and a very inspirational talk by Harold Hambrose on software design and usability. Vikram’s demo showcased an expense claim process automated in SharePoint and fully integrated with SAP. It was a great example of all the Winshuttle products working nicely together to provide a complete, yet simple solution. In 15 minutes he demonstrated both the end user experience and gave an overview of how it was all put together. Perhaps the most impressive aspect of this demo was the fact that the entire solution was built in under four hours on a flight from Seattle to Chicago.

Following the keynote, I attended a couple of customer presentations focused on the Central governance platform. Both sessions sparked some hectic debates between business users and IT representatives. Like any other business user-oriented software platform, such as Microsoft SharePoint or SAP Business Objects, the Winshuttle suite aims to empower the business without compromising IT governance requirements. It is a balancing act that sometimes can create some internal friction in organisations. However, consensus was that it is something that cannot be ignored and business units seeking more autonomy in solution development need to partner with IT every step of the way to ensure success. It is clear that business user tools must have good governance and control features to be relevant in an enterprise context.

At the end of the first day, I facilitated a panel discussion on master data governance. Again, all attendees were very open to share their experiences and some valuable lessons were passed on. Probably less than half of the companies represented had reached a maturity level where master data governance is centralised with an executive sponsorship. This is what everyone is striving for though and it is increasingly becoming an area of high priority.

Tuesday was all dedicated to training and overall the event was a massive success. Like other industry events, the WUG provides a perfect opportunity to collect feedback from customers and partners alike. And there is no doubt the customer-to-customer interaction was well appreciated by everyone. Large enterprises face many of the same challenges and taking out a few days to learn how other companies are dealing with these challenges is invaluable. And as a Product Manager, I have certainly come away with a long laundry list of first-hand customer feedback and ideas that will feed into both short term product improvements and long term roadmaps.

SharePoint rock star wanted for Europe

noreply@blogger.com (Kristian Kalsing) — Mon, 03 Oct 2011 15:56:00 +0000

Following the success of Winshuttle’s product suite as an effective way of utilising the SharePoint platform for SAP process optimisation, we are ramping up our global SharePoint competencies. We have an immediate opening for a highly motivated SharePoint rock star in Europe.

We are looking for a consultant with solid SharePoint experience who can work directly with business units to compose solutions. Are you interested? You will be helping customers to optimise SAP processes through the use of Winshuttle and SharePoint technologies. Prior experience with SAP is desired but not a must.

This is an awesome role where you will be part of a strategically important Acceleration Team where the primary objectives are customer readiness and enablement. As such, your focus will be on short and sharp engagements that prove the value of Winshuttle software and help customers to hit the ground running.

Key responsibilities include project scoping, solution architecture and proof-of-concept delivery. Expect to be working with many different customers across Europe. Ideally, you should be based out of our EMEA head office in London, but we would be willing to consider other arrangements.

I’ll be in Berlin for the European SharePoint Conference, 17th through 20th of October, and in London during the first week of November. If you are interested, please drop me a line (kristian dot kalsing at winshuttle dot com) and we can arrange to meet up for a chat. This will be a lot of fun!

Keynote summary from SAP TechEd in Las Vegas

noreply@blogger.com (Kristian Kalsing) — Tue, 13 Sep 2011 20:30:00 +0000

The 15th anniversary edition of SAP TechEd has kicked off in Las Vegas and the keynote was delivered this morning by Vishal Sikka on stage, introduced by Hasso Plattner connecting through from Germany. In addition, various technical leads were called in to add their two cents’ worth in their respective areas of expertise. If there was one common theme throughout the keynote, it was certainly HANA. Actually, there was barely a single sentence during the 1.5 hours that didn’t include the magic word, HANA!

Before Vishal Sikka came on for the main act, Hasso Plattner briefly summarised the vision for HANA which was painted at SAPPHIRE earlier this year. Back then, a great deal of attention was given to the ‘what’ and the ‘why.’ Now, after 12-18 months of proving the technology with early adopters and after three months of general availability, it’s time to get down to business and concentrate on the ‘how’. The inherent challenge will be to bring a highly disruptive technology to the market without causing major disruptions in the installed base.

Vishal Sikka started out by emphasising that the intention with HANA is not to add more complexity to an already crowded mishmash of application layers in the SAP technical landscape. Nor are they “replacing the litter with a different kind of litter.” HANA is all about “bringing together the grand simplification.” Delivered on the next generation of commoditised hardware, HANA will provide a unified infrastructure for future applications. A new consolidated layer of in-memory data and application logic will “provide businesses with the freedom to innovate.”

There were lots of lofty promises as you would expect from a keynote, but halfway through the presentation there was a reality check when the attendees were asked to raise their hands if they were considering embarking on a HANA project. Less than 5% of the audience put their hands up. Despite all the hype surrounding HANA, most customers are still battling with much more mundane aspects of realising the return of their existing investments in SAP technology.

Moving on to future developments of the HANA platform, the most immediate introduction to the market will be the launch of BW for HANA (Project Orange) on November 7. Customers will basically be able to run BW directly on top of HANA, eliminating the databases currently underpinning BW and introducing unprecedented performance improvements. With HANA, SAP is in general betting on traditional data marts and data warehouses going away in the future.

The keynote also had some brief updates from the major SAP platforms of NetWeaver, BusinessObjects and Sybase. The key message here was that all technologies are undergoing a renewal and support for HANA is added wherever it makes sense. Capabilities for managing HANA in the SAP landscape will be added to Solution Manager. Technologies such as PI, BPM and Gateway will all be extended to support HANA. BusinessObjects universes will be natively optimised for running on HANA.

Finally, the keynote was concluded by a series of demos and examples of applications built on various UI platforms underpinned by the HANA infrastructure, accompanied by the usual customer testimonials of how easy it was to implement. However, the final verdict of the promised simplicity will have to wait until we have heard the experiences of customers that were not carefully nurtured as early adopters. All in all, it was a keynote that was reinforcing SAP’s strong commitment to HANA and driving the message of “bringing on the grand simplification of the layers.”

More evidence of a less SAP-centric approach

noreply@blogger.com (Kristian Kalsing) — Wed, 03 Aug 2011 16:11:00 +0000

It is not more than two or three years ago that the prevailing view within SAP was that customers should adopt a wall-to-wall SAP strategy. In the mish mash of technologies called NetWeaver there would be an answer for everything. Any application or integration need around the SAP Business Suite could be addressed with “something” from the NetWeaver mixed bag.

This viewpoint has been changing significantly over the last few years and there is now less of a push to solve every problem with an SAP product. This is particularly evident in SAP’s release of the Gateway product, which will make it much easier for developers to build front-ends to SAP using non-SAP technologies.

At the annual summit of the SAP Australian User Group (SAUG) held in Sydney this week, there was even more evidence of customers complimenting their SAP landscape with non-SAP technologies for specific purposes. In R “Ray” Wang’s event report a few points stand out:

There is an increase in technology spending despite reductions in IT budgets. In other words, the business is buying.
65% of attendees are considering solutions outside the SAP sphere.
For collaboration solutions SharePoint appear to have gained mindshare.
CRM remains dominated by Salesforce.com and Microsoft CRM.
Analytics discussions include many non-SAP products such as IBM Cognos, Oracle Hyperion and QlikTech.

The ironic aspect is that allowing other platforms to seamlessly integrate with the core SAP system will potentially make companies more SAP-centric from a data perspective. If organisations can deploy their own user interfaces and tools of choice, fully integrated with SAP, then there will be much less demand for buying other industry-specific solutions. I suspect this is what SAP is finally realising too.

Top 20 SAP transactions and quick wins using SharePoint

noreply@blogger.com (Kristian Kalsing) — Tue, 02 Aug 2011 16:58:00 +0000

Over the last few years one of my colleagues, Jim O’Farrell, has done some excellent work in terms of working with Winshuttle customers and calculating the ROI of business process acceleration. Part of this work includes looking at customers’ logs in the SAP Workload Monitor (ST03N). These logs keep a tally of all transactions handled in the system and provide valuable insights into usage patterns in SAP. Usage logs from individual customers are highly confidential, but analysing the data in aggregate is quite interesting. For example, the table below lists the top 20 transactions based on actual usage data aggregated from more than 250 SAP customers worldwide.

Rank	Tcode	Description
1	VA02	Change Sales Order
2	IQ02	Change Material Serial Number
3	CAT2	Time Sheet: Maintain Times
4	VA01	Create Sales Order
5	FBL5N	Display Customer Line Items
6	ME23N	Display Purchase Order
7	IQ01	Create Material Serial Number
8	VL02N	Change Outbound Delivery
9	FBL1N	Display Vendor Line Items
10	MD04	Display Stock/Requirements Situation
11	LM13	Put Away Clustered
12	MIGO	Goods Movement
13	ME21N	Create Purchase Order
14	FBL3N	Display G/L Account Line Items
15	VA03	Display Sales Order
16	MIRO	Enter Incoming Invoice
17	QE51N	Results Recording Work List
18	IW32	Change Order
19	VL03N	Display Outbound Delivery
20	FB03	Display Document

A really interesting aspect of this list is that it includes eight display transactions. In other words, some of the most frequent use of the SAP GUI is simply to retrieve information and not perform any updates on the system. We are all familiar with the well-known usability issues of the SAP GUI. Having to navigate and master this generic interface for quick lookups and retrieval of business data, often while performing work in other tools, is an unnecessary burden on productivity.

I am often asked about how to qualify business scenarios for SAP/SharePoint solutions, which is primarily focused on extending the reach of SAP and serving casual users in their tools of choice. Building such solutions involves various degrees of complexity and effort, but the table above helps you identify the quick wins. There is obviously a lot less complexity and effort involved in creating an interface in SharePoint that is merely reading information from SAP. These eight frequently used display transactions is a good place to start when considering how to realise productivity gains by surfacing SAP through SharePoint.

Three points to consider when using the SharePoint BCS

noreply@blogger.com (Kristian Kalsing) — Wed, 20 Jul 2011 16:23:00 +0000

The SharePoint Business Connectivity Services (BCS) is an integration feature of SharePoint 2010 which provides read/write access to line-of-business data in external systems. Once an external system has been modelled in the BCS, a SharePoint user or developer can compose solutions that use external data directly without having to possess expert knowledge about the API of the back-end system.

There are many options when it comes to architecting a SharePoint solution that is integrated with an external system. In some scenarios the BCS will be a valuable constituent of a solution, in other cases it may not be a good fit. If you are looking to connect SharePoint with an ERP system or other line-of-business system, there are some important points to consider when deciding whether the BCS should be part of your solution architecture.

Up to 20 operations need to be supported
The BCS provides a back-end neutral framework for integration by requiring the API of the back-end system to be mapped to 20 stereotyped operations. Many APIs of business applications are not very BCS-friendly and it may require substantial effort to distill the APIs into services that can be mapped to the stereotyped BCS operations. This is not a problem when connecting to simple data sources like SQL Server databases, but more complex business applications often have APIs that are very hard to decipher for outsiders (e.g. SAP has a very granular generic API which presents a significant challenge in this regard).

Data is retrieved on-demand
Business data accessed through the BCS is exposed through what is called external lists in SharePoint. These external lists share many of the characteristics of the traditional SharePoint lists. However, one important difference is that the data is not stored in SharePoint. This is often a positive thing because you generally do not want to replicate business data across multiple storages unless you have to. But there are also common scenarios where data caching is required. For example, the administrator of your ERP system might not be too happy if you are frequently hitting the system live to retrieve data that rarely changes.

Workflows cannot be associated with external lists
SharePoint workflow generally works by reacting to items in a list being added or changed. Items in external lists are fetched on-demand and are not stored in SharePoint and therefore workflows cannot be directly associated with external lists. If you consider a use case where you want to trigger a business process every time a new item is added to a table on the back-end then the BCS is not a good option. You can still query data in an external list as part of a workflow running on a document library or an “internal” list, but items in an external list cannot be the primary object of the workflow.

These are all important things to consider when deciding whether the BCS should be part of your solution architecture. There are solutions where the BCS is a natural fit and there are solutions where you will have to come up with an alternative way of bringing the line-of-business data into SharePoint. As always, if you have any experiences with this please share your thoughts below.

Webinar on surfacing SAP through SharePoint

noreply@blogger.com (Kristian Kalsing) — Tue, 12 Jul 2011 03:30:00 +0000

At the European SharePoint Conference in Berlin in October, I will be speaking about accelerating business processes with an SAP/SharePoint integrated approach to solution development. In particular, the session will focus on leveraging business user-oriented tools such as InfoPath and the Winshuttle usability suite to automate business processes that involve interaction with SAP.

Leading up to the conference there is a pretty solid schedule of regular webinars, free for all, providing brief introductions into the topics covered at the conference. Wednesday this week, I will be delivering a session on surfacing SAP through SharePoint. It won’t be a deep technical dive but rather an introduction into why SharePoint should be considered in the context of SAP and what the main challenges are. This is the outline:

Surfacing SAP through SharePoint
40% of ERP implementations have user adoption issues resulting in limited ROI from initial investments in ERP. Complex generic interfaces that are not intuitive for casual users of line-of-business systems such as SAP continue to slow down business processes. The popularity and rapid adoption of SharePoint provide a tremendous opportunity for bringing core SAP functionality out to more users while meeting usability expectations.
This session outlines why surfacing SAP through SharePoint is beneficial to the business and provides an overview of the key challenges in implementing SAP/SharePoint integrated solutions.

You can sign up for the webinar here and also check out all the other upcoming webinars. These are 20-30 min sessions on some very relevant topics where you will also have the opportunity to ask questions.

Speaking at SAPPHIRE NOW and the ASUG Annual Conference 2011

noreply@blogger.com (Kristian Kalsing) — Tue, 10 May 2011 02:26:00 +0000

Next week it is time for the biggest show in the world of SAP. Over 10,000 attendees will descend on Orlando in Florida to experience and explore the latest and greatest in SAP-based business and technical solutions and strategies. Additionally, SAP hopes to reach another 4,000 people worldwide at connected events that will receive real-time feeds or content from Orlando.

In recent years, SAP has been ramping up the use of social media during their events. So, if you are unable to attend you can still follow the event on Twitter, Facebook, LinkedIn and YouTube. SAP will even have dedicated social media reporters who will be covering specific topics. For attendees, they have also promised a snazzy mobile app (for Android, iOS and BlackBerry) which will include venue details, floor plan, searchable agenda, profiles of exhibitors, daily updates and links to the social media sites.

Now that it is less than a week away, I am starting to get excited. I am looking forward to reunite with many friends and colleagues from around the world. The event is also a unique opportunity, as a product manager, to learn about customers’ challenges and verify product hypotheses. I will also be delivering a presentation on the Tuesday at 11 am with the following abstract:

Accelerating SAP Software Transactions with SharePoint and InfoPath
In many cases, data entry into SAP software can lead to complex business processes that take up unnecessary time and resources throughout an organization. Enterprises can achieve significant cost-savings by providing alternative interfaces that simplify data entry and increase user adoption.
SharePoint's popularity with business users provides an immense opportunity for delivering SAP software transactions to the broader user base. As an integrated part of the SharePoint platform, InfoPath is a tool for creating electronic forms which can be utilized by business users to rapidly create fit-for-purpose user interfaces for SAP software.
In this session, you will learn what it takes to surface SAP software transactions in SharePoint solutions following an approach that is entirely driven by business users. In particular you will see specific examples of how a business user can utilize SharePoint, InfoPath, and Winshuttle to build alternative user interfaces for SAP software with no programming involved.

Apart from speaking at the event, I will be well busy as a booth bandit for Winshuttle. We will have eight demo stations showcasing our complete usability platform for SAP and as usual we will have some exciting new things to show, so don’t hesitate to drop by. Just look for the giant “Brushy.”

Using the SharePoint 2010 Service Application Framework for vertical solutions

noreply@blogger.com (Kristian Kalsing) — Tue, 05 Apr 2011 20:53:00 +0000

SharePoint 2010 introduces the concept of Service Applications. It is effectively a replacement for the Shared Services Provider (SSP) in the previous version of SharePoint and the new architecture offers a modular approach which has a lot of benefits from an administration and manageability perspective. The plumbing for the Service Application Framework is baked into SharePoint Foundation and many of the server capabilities provided by both SharePoint Foundation and SharePoint Server are in fact Service Applications. These services include, but are not limited to Search Services, Excel Services, InfoPath Forms Services, Visio Services, User Profile Services, PerformancePoint Services and Managed Metadata Services.

There is a quite a bit of coverage out there about what Service Applications mean for administrators and the benefits they bring to the management of a SharePoint farm. There are also some high-level articles about what opportunities the framework brings to application development on the SharePoint platform. For example, check out Andrew Connell’s general introduction and Spencer Harbar’s coverage of the core concepts. There is also a section about the Service Application Framework on MSDN, although this is still a bit light on actual content.

What I wanted to explore here is the opportunity for ISVs to leverage the Service Application model since it is an open framework that third-parties can take advantage of. This means that third-party applications can potentially offer a lot more capabilities than was the case in SharePoint 2007. A Service Application can take advantage of the following:

Use a custom database for application specific data and have the database managed by SharePoint.
Host and manage middle-tier web services.
Perform scheduled operations with a service-scoped timer job infrastructure.
Store application settings within a configuration store in the SharePoint configuration database.
Take advantage of claims-based security.
Rely on SharePoint infrastructure for scalability, performance and availability.

All of above offer some interesting opportunities for ISV applications. When you combine a custom database, a middle-tier of web services and timer job infrastructure, quite advanced functionality can be built leveraging these core server capabilities. This may significantly increase the scope of vertical applications deployed through SharePoint. Potentially, ISVs can develop more server products based on the SharePoint foundation rather than building everything from scratch. The primary benefit being that ISVs can focus on what they are truly good at, namely building functionality for their domain of expertise, and spend less resources on implementing core server components.

There certainly are vendors that have advanced products based on the SharePoint 2007 platform which include databases, web services and timer jobs. However, with the Service Application Framework, these products can potentially be redesigned to be less of a patchwork and more aligned with standard SharePoint infrastructure. It also offers new opportunities for deeper integration between SharePoint and various third-party applications. For example, some of the BPM and ECM vendors have been providing a SharePoint integration option for years for both SharePoint 2003 and 2007. These vendors, along with others, now have an opportunity to take this integration to a new level using the Service Application Framework.

From a cloud computing perspective, the Service Application Framework compliments the Sandboxed Solutions in a multi-tenant SharePoint environment. Sandboxed Solutions are well suited for building add-on functionality to SharePoint itself. However, with limitations such as no web services, no application pages, etc., they are not adequate for building vertical solutions. If you rely on those capabilities and want to build a multi-tenant ready application, then the Service Application Framework is your answer.

It all sounds good. The big question, of course, is how mature is this framework at this point in time? Third-party Service Applications are not yet supported on SharePoint Online (SharePoint Online Standard Developer Guide), so the framework hasn’t been truly tested in a large-scale multi-tenancy environment yet. For on-premise solutions, I am also yet to come across ISVs where they are building their products based on the Service Application Framework. It’s an interesting and promising architecture that could potentially take SharePoint to the next level in terms of vertical integration, but the technology is still in its infancy and time will tell whether it’ll be a successful platform for third-party products.

Duet Enterprise at the Australian SharePoint Conference

noreply@blogger.com (Kristian Kalsing) — Sat, 26 Feb 2011 01:58:00 +0000

The Australian SharePoint Conference coming up in only a few weeks from now will have a broad coverage on anything SharePoint. This will also include some goodies for SAP/SharePoint enthusiasts. I have just heard on the grapevine that Microsoft will be delivering a session on the newly released Duet Enterprise. It’s yet to be published in the agenda, but they’ll definitely be there.

Slide deck from Share 2010 on improving SAP usability with InfoPath and Winshuttle

noreply@blogger.com (Kristian Kalsing) — Fri, 03 Dec 2010 06:01:00 +0000

Earlier this week, I delivered a presentation on using InfoPath to address SAP usability issues at the Share 2010 conference in Sydney, Australia. Ten years after SharePoint technologies first hit the market, Share 2010 was really the first dedicated SharePoint conference entirely devoted to covering the business challenges around the SharePoint platform. Speakers included early evangelists of a more business-oriented approach to SharePoint such as Paul Culmsee, Michael Sampson, Dux Raymond Sy and Erica Toelle. Overall, Share 2010 was a resounding success and the vibe was unlike anything I have ever seen at the more technical SharePoint events around the world.

Considering Share 2010 was aimed at the SharePoint community, I wasn’t sure beforehand how big of an audience I would get to a session about a specialised topic such as SAP usability. But as it turned out, the positive feedback was overwhelming. Oxygen and IQX also delivered a presentation on SAP/SharePoint interoperability solutions and both sessions were very well attended. Since most attendees were from the business side, many were also regular users of SAP. If your business runs on SAP and SharePoint is your portal platform of choice, then it makes perfect sense to explore ways of surfacing SAP through SharePoint.

In my session, I went through how we can leverage the Winshuttle 10 platform to rapidly build data entry forms in InfoPath which post data directly to SAP. Data collected in these forms are posted to SAP via web services which are authored and deployed by business users with Winshuttle. I am not aware of any other technologies in the current marketplace that will effectively empower business users to build their own web services for SAP without writing a single line of code. The slide deck below provides some insight into how this works.

Improving SAP Usability with InfoPath and Winshuttle

View more presentations from Kristian Kalsing.

As a Product Manager for key components of the Winshuttle platform, I am obviously very keen to hear your feedback on all this. It is an approach which can be applied to hundreds of common use cases which are currently not very well supported by the more developer-centric and resource intensive options out there. I look forward to your comments below.

General availability of Duet Enterprise

noreply@blogger.com (Kristian Kalsing) — Thu, 02 Dec 2010 00:46:00 +0000

The long anticipated development platform for SAP/Microsoft interoperability solutions, Duet Enterprise, is slated for general availability later this week. To mark this milestone, there will be a Duet Enterprise Launch Summit on the 1st of February 2011. The summit will have physical events in Frankfurt and Orlando, but you can also attend the event online at no cost.

For companies that run on SAP and utilise SharePoint as the broad collaboration platform within the enterprise, Duet Enterprise provides interoperability infrastructure and a development framework for building solutions that span across both technology stacks. It supports all versions of SAP from 4.6c and up, but does require NetWeaver 7.02 and SharePoint 2010 (and optionally Office 2010 for offline scenarios).

Presenting on ERP usability at Share 2010

noreply@blogger.com (Kristian Kalsing) — Fri, 26 Nov 2010 03:29:00 +0000

Next week, the inaugural Share 2010 will see the light. Share 2010 is the first SharePoint conference focusing entirely on the business aspects of SharePoint. I will be presenting on how business users can use SharePoint and InfoPath to improve ERP usability. In particular, I will be showing some of the cool new solutions business users are able to build by leveraging the Winshuttle 10 platform.

Improving ERP usability with SharePoint and InfoPath
Monday 29 November | 16.30 – 17.25 | Track
40% of ERP implementations have user adoption issues resulting in limited ROI from initial investments in ERP. Usability issues for the casual user of core systems such as SAP often lead to complex business processes taking up unnecessary time and resources throughout the organisation.
Considering SharePoint has become the de facto collaboration platform for many organisations and proven popular amongst business users, it is worth asking the question: Is the time ripe for taking SharePoint to the next level and utilise the platform for improving business processes that involve interactions with the ERP system?
In this session, we will discuss what it takes to surface ERP functionality in SharePoint solutions following an approach that is entirely driven by business users. In particular we will see specific examples of how a business user can utilise SharePoint, InfoPath and Winshuttle to build alternative user interfaces for SAP, with no programming involved.

Throughout the conference I will be keen to catch up with anyone who wants to discuss SAP/SharePoint solutions. Bringing SAP into SharePoint provides an excellent opportunity for taking SharePoint to a whole new level. Just ping me on Twitter (@kalsing) or call my mobile number on the conference networking list.

SAP Project ‘Gateway’ and lightweight consumption

noreply@blogger.com (Kristian Kalsing) — Tue, 19 Oct 2010 08:27:00 +0000

SAP has for quite some time been working on a new integration technology, codenamed Project ‘Gateway.’ They have kept their cards close but SAP TechEd has revealed a few details and one important point has become clear. It is not a replacement for existing integration technologies such as Enterprise Services. Project ‘Gateway’ provides an additional way of exposing SAP data to other platforms and it is specialised for lightweight consumption. Enterprise Services will remain the preferred option for heavier integration. Richard Hirsch has posted an excellent overview of the concepts of lightweight consumption versus heavyweight integration.

The ‘Gateway’ technology attaches to existing SAP systems, even older versions. Developers will then be able to build lightweight front-ends in various web technologies including ASP.NET, PHP and Ruby on Rails as well as targeting mobile platforms such as Android, Windows Phone, BlackBerry and iPhone. In developing ‘Gateway,’ SAP has primarily been working with three partners: Microsoft, IBM and RIM. As such, it is the underlying technology of the latest iterations of both Microsoft’s Duet Enterprise and IBM’s Alloy. There is also a new product on its way built for BlackBerry.

From an interoperability perspective, it is potentially a disruptive technology as it opens up unprecedented opportunities for reaching new users with SAP. The idea of a lightweight consumption pattern will be well received by most customers who are looking for more agile ways of delivering business applications. Project ‘Gateway’ is definitely another sign of the changing tide at SAP where third-party platforms are increasingly seen as an opportunity for enlarging the footprint of SAP rather than a threat to their dominance of the technical landscape.

SharePoint leading Gartner’s Magic Quadrant for horizontal portals

noreply@blogger.com (Kristian Kalsing) — Tue, 12 Oct 2010 13:31:00 +0000

Gartner has for quite some time positioned Microsoft as a leader when it comes to providing portal-type capabilities. Now Microsoft SharePoint is taking the absolute lead in the recently updated version of the Magic Quadrant for horizontal portals. Compared to the 2009 edition, Microsoft has just edged past IBM. There are few changes to the rest of the quadrant with the other major players having retained their existing positions relative to each other.

Improvements in SharePoint 2010 could well push SharePoint beyond being just a basic intranet and document collaboration tool. It is now a more capable platform for creating and delivering composite applications, which means we will start seeing more business data surfaced in SharePoint. It is also worth noting that Microsoft is the only significant portal vendor in the magic quadrant which has a multitenant, elastic cloud-based portal offering. SharePoint Online is already proving to be a huge success with a 300% growth this year alone and more than 40 million paid seats in total.

SAP has also retained a leadership position in the magic quadrant, but I dare say this is based on the success of SAP ERP rather than the portal and user experience capabilities of NetWeaver Portal itself. The vast majority of NetWeaver Portal deployments are vertically focused, enabling SAP applications in a web environment. NetWeaver Portal does have improved features for content management and collaboration with Web Page Composer and Enterprise Workspaces, but only time will tell whether more customers will start using the product for more than as a web enabler for SAP business applications. Even the latter is no longer a given considering that Enhancement Pack 5 has decoupled core business packages such as ESS and MSS from the NetWeaver Portal.

On the whole, this updated magic quadrant is a positive read for SAP/SharePoint interoperability enthusiasts. SharePoint is maturing and becoming a true enterprise-level platform with enhanced capabilities for composite business applications. NetWeaver Portal, despite being a solid product, has a hazier future in SAP’s growing array of UI technologies including Duet Enterprise for Microsoft SharePoint. More than ever, enterprise portals are being evaluated for their potential as complete usability platforms providing users with a unified experience across disparate applications. Considering SAP is rarely the only significant back-end system in a large enterprise, SharePoint is compelling because it is largely agnostic with respect to business applications.

Current hot topics for SharePoint business users

noreply@blogger.com (Kristian Kalsing) — Fri, 13 Aug 2010 03:30:00 +0000

During three days in Sydney later this year (29 November-1 December 2010), the inaugural version of Share 2010 will take place. Share 2010 is essentially a much anticipated new SharePoint conference aimed entirely at business users. Until now, business users driving SharePoint within their respective organisations have not had a conference solely focused on the non-technical business-oriented aspects of SharePoint. This conference will fill that gap.

I have been involved in some research work for Eventful Management, the organisers behind Share 2010, to help identify and prioritise the current hot topics for SharePoint business users. The research is based on inputs from more than 100 SharePoint customers across Australia and New Zealand as well as thought leaders from around the world. Below is the consolidated list of hot topics that came out of this research in order of priority:

Governance
User Training and Change Management
Business Process Automation and Workflow
Information Architecture
Information Discovery (including Search)
Collaboration
Document and Records Management
Reporting and Analytics (Business Intelligence)
Integration with other Systems
Resourcing and Support
Social Networking
Selling the Value and Demonstrating ROI
Security
Going 2010
Extranet Collaboration with External People
Third-Party Partners and Products

The conference content and format is being put together using this hotlist of topics as guidance. You can read more about the essence of each individual topic on the Share 2010 website.

Facilitating round table discussions for new SharePoint conference in Australia

noreply@blogger.com (Kristian Kalsing) — Sat, 17 Jul 2010 01:30:00 +0000

Another new SharePoint conference is being launched in Australia. Later this year, Share 2010 will be a conference with a different format and focus than previously seen in Australia and New Zealand, focusing entirely on the business issues and challenges of SharePoint. It's being organised by Eventful Management who for many years have been running some great events in the SAP space. I have been fortunate enough to have been involved in many of their conferences, both as a speaker and as a vendor, and they have always exceeded expectations.

The conference content and format will be driven by the people at the coal face. At the moment, Eventful is running round table discussions in Sydney, Auckland, Melbourne, Canberra, Brisbane and Perth with local people who play a key part of their organisations' SharePoint journey. Based on the outcome of these round table discussions, the conference agenda will be set and speakers invited accordingly. In total, more than 100 community opinions will feed into building the inaugural conference content and style of delivery.

I will be facilitating the round table discussions in Brisbane this coming Thursday. Please provide your input in the comments below if there's something you think should absolutely be part of the conference. What are the biggest pain points you are currently experiencing with SharePoint? In particular from a business and change management perspective? What format would you like to see sessions delivered in? I’ll make sure all your comments and ideas are taken into consideration.

SAP/Microsoft interoperability and the composition challenge

noreply@blogger.com (Kristian Kalsing) — Mon, 05 Jul 2010 23:59:00 +0000

The best of both worlds approach is appealing. Leveraging SAP as the transactional backbone and surfacing business data in the Microsoft collaboration and productivity tools that everyone is so familiar with. So why isn't everyone doing it? Because, it is not that straight forward. There is one particular challenge that always needs to be addressed and here I will explain what the fundamental problem is.

When SAP opened up for a more service-oriented approach, they basically just took the lid off the box exposing a rather complicated mess of wires, called RFCs and BAPIs. You can achieve almost anything connecting to these wires but it takes a specialised SAP professional to do so. To overcome this challenge, these wires need to be combined into understandable and reusable sockets which outsiders, such as .NET developers or increasingly business users with the right tools, can easily plug in to.

In other words, connecting directly to RFCs and BAPIs will not get you far if you require anything but the simplest of read-only integration. So, has SAP overcomplicated it by making the API so granular? Not really. Because SAP is one large generic product built to work in pretty much any conceivable industry, it has to be this way. At least when considering the core product.

We have all heard users expressing their frustration with the standard SAP GUI. A lot of that frustration is a consequence of a generic user interface that is not targeted at that particular user's role or industry. It is exactly this same frustration developers experience when connecting directly to the SAP services. The issues users are having with the SAP GUI are reflected in the integration layer when developers are facing the underlying API. Granularity is the culprit in both instances.

There are many tools and technologies which can be employed in the services tier or even to help with point-to-point integration. However, regardless of whether you are using SAP Enterprise Services, SAP Connector for .NET, SAP PI, Microsoft BizTalk, your own custom interoperability components or any combination of the above, you will still encounter the same challenge: Composing easy consumable services from the granular SAP API.

The good news is that this is a problem that can be solved. And it can be solved elegantly. The less positive news, however, is that the reality dictates a wide range of solutions depending on many factors that are specific to your requirements, circumstances and environment. But hopefully this post has helped you focus on where you need to concentrate your effort, particularly when you design your architecture or evaluate various third-party tools and technologies. Always ask the question, "how is this going to make service composition easier?"

Thanks for reading and please do share your thoughts below. Many people out there are eager to hear your professional view on this.

SAP is seeking participants for the beta shipment of SAP Connector for .NET 3.0

noreply@blogger.com (Kristian Kalsing) — Mon, 28 Jun 2010 01:39:00 +0000

After abandoning new developments on the SAP Connector for Microsoft .NET, SAP has now announced that a new version 3.0 is planned to be released in December 2010. A beta version will be made available to selected partners and customers during the second half of 2010. By participating in the beta release, you can gain early hands-on experience and get special project support from the product team.

Development on the SAP Connector for .NET was previously withdrawn with a view to put more focus on SAP Enterprise Services as the preferred framework for integration. However, the reality is that customers want options. Enterprise Services may not be the preferred web services layer or web services may not be part of the architecture at all for certain solutions.

If you have access to the SAP Service Marketplace you can find more details here about the beta shipment and how to apply for participation. Note, you are not allowed to use the beta software for production solutions and there is no migration from version 1.0/2.0 to the beta version of release 3.0.

Qualifying business scenarios for Duet Enterprise

noreply@blogger.com (Kristian Kalsing) — Thu, 29 Apr 2010 00:53:00 +0000

Further unveiling the potential of Duet Enterprise, the next step is to explore what business scenarios qualify for the platform. The Duet Enterprise product itself will provide a foundation of core capabilities upon which scenarios can be implemented to meet specific business requirements. The success of Duet Enterprise will ultimately depend on the value realised by the solutions built on top of the platform.

The actual product release is still some time away and only limited details about the features have made it to the public domain. But given the conceptual architecture and what we know about the core capabilities, it is worth trying to identify the characteristics of business scenarios that would be a natural fit for Duet Enterprise.

Many are calling out Duet Enterprise as a way of addressing usability issues with SAP. But I would argue it is not necessarily all about usability issues in the existing user base. The biggest opportunity is the potential to reach people that are not currently using SAP at all by giving these people direct access to SAP in the environment they are already comfortable in, i.e. SharePoint and Office.

I would also like to encourage everyone to consider the platform from a much broader perspective than HCM, which seems to be an area that always comes up when discussing SAP/SharePoint solutions. No doubt, there is a lot of potential here and it makes perfect sense if your user base is already using SharePoint. But the idea of empowering a new group of users “further out” to access information and perform transactions directly on the system can be applied to most functional areas, not just HCM.

Assuming your business runs on SAP, SharePoint is your horizontal collaboration platform and you have a well-defined business problem, what are some of the questions you should be asking to qualify a problem as a scenario that can be addressed with a Duet Enterprise solution? At the very least, ask the questions below. The more yes answers, the more suitable your scenario is for Duet Enterprise.

Are non-SAP users involved?

Are the users you are trying to reach not currently using SAP? Do they spend the majority of their day in other tools such as SharePoint and Office?

The current base of SAP power users are generally satisfied with the SAP GUI and a number of new innovations including the Business Client will further serve this user base. I acknowledge that there can be user adoption issues even amongst the core users, but the general overhaul of the UI that SAP is doing with all the new redesigned Web Dynpro interfaces will address this in due course. The point is, you don’t want to simply be redeveloping SAP’s UI as is. Leave that to SAP.

The opportunity with Duet Enterprise is to go beyond the traditional SAP users. These users are often referred to as casual or occasional users of SAP. If the process being considered involves people that are not currently SAP users and these users are already using SharePoint, then Duet Enterprise can bring SAP to them rather than the other way around.

If you are targeting people that are not currently using SAP, then there will obviously be licensing implications. We’re still waiting for more details on this, so there is not much point in speculating about licensing at this stage. But if SAP really wants to reach 1 billion users by 2014, then the licensing model obviously needs to facilitate this.

Is there currently a reliance on SAP power users?

Are users requesting information from SAP users in order to carry out their work tasks? Are they producing or capturing information which ultimately ends up with SAP users who enter the data in the system through the SAP GUI?

A reliance on power users is often streamlined with paper-based forms. The vast majority of paper-based forms are really just a workaround interface to a system that the user does not have access to. The humble paper-based leave form falls into this category. Because the staff member does not have a direct interface to the HR system, a form is filled in which ultimately ends up with an SAP power user in the HR department who will manually key the data into the system. Think about other functional areas where there are scenarios similar to this.

SharePoint, with its forms rendering capabilities and underlying workflow engine, can be utilised as a platform for automating some of these paper-based processed. With External Content Types provided by Duet Enterprise these interfaces can expose data directly from the SAP system. The Federated Search capability of Duet Enterprise is another great way of minimising reliance on power users by opening up access to SAP data to a larger user base, still respecting security.

Does the scenario involve collaborative activities?

Is input required from many people? Is it an iterative feedback process where an artefact circles through the same steps many times? Is the collaborative part of the process evolving and as a result required to be tweaked on an ongoing basis?

SharePoint's core strength is around collaboration, so it makes sense to manage the more collaborative part of a business process within SharePoint. It’s a case of using the best tool for purpose, which organisations are already doing. But there is typically a complete disconnect between the transactional and collaborative activities. Duet Enterprise will open up an opportunity to bridge that gap.

The Enterprise Collaboration core capability of Duet Enterprise empowers users to create collaboration sites around SAP business data entities and the Contextual Workflow capability allows SAP workflows to be extended within SharePoint to cover the collaborative part of an end-to-end business process.

Is there manipulation of unstructured data (i.e. documents)?

Does the business process include editing one or more Office documents? Would the users be more productive using tools like Word or OneNote to collate data for the business transaction? Are document artefacts being produced as part of the process?

SharePoint is tightly integrated with the Office client tools providing a seamless experience for working with and collaborating on documents. With a Duet Enterprise solution you can give document authors easier access to business information in SAP from within the authoring tools (e.g. Word, etc.), eliminating the need to switch to another interface or request the information from someone else.

Duet Enterprise also makes it possible to create sites with 360 degree views of SAP business data entities. On these sites you can mix structured data from SAP with unstructured content managed in SharePoint. You can view and create unstructured data without losing the context of the core business process.

Are role-specific interfaces required?

Should information be presented in different ways to different users? Would the interface be more logical to the users if it was targeted at their specific roles?

Leveraging the audience targeting features, most objects in SharePoint can be targeted at specific groups of users. Views of data can be customised to what a specific role requires and whole blocks of functionality (web parts) can be shown or hidden depending on the audience. With Duet Enterprise, these audiences can be defined based on SAP roles.

Role-specific interfaces are a result of an outside-in approach as opposed to an inside-out approach. Applications are designed around the needs of the business role rather than from the perspective of one single system.

There is also an opportunity to empower business users to assemble interfaces for other users. The web part framework is SharePoint provides a highly flexible UI which is easily configurable by the end user. A savvy business user can add or remove web parts, lay out the screens and change basic configuration settings.

Is the business data sourced from SAP as well as from other databases?

Is the scenario touching data that resides in line-of-business systems other than SAP? Are you aggregating information from multiple sources? Are parts of the captured data required to be stored in non-SAP databases?

SharePoint is an agnostic platform that can potentially connect to any back-end system. This makes it ideal as a platform for mashing up content from various sources. SharePoint’s BCS which play a fundamental part of Duet Enterprise is designed to work generically with almost any data source.

In all its essence, it is about providing a better alternative for the “swivel chair users” so they no longer have to turn from system to system to system to gather what data they need to complete a business task.

A Duet Enterprise solution would provide the SAP piece of the puzzle. SharePoint web parts exposing SAP data can be designed to connect easily with other web parts on the same page. We are then using SharePoint as a platform for enterprise mash-ups aggregating information from various data sources.

Is business data accessed or updated offline?

Will the users be taking the business data with them to access it outside of network connectivity? Will they be updating the data while they are on the road? Do you currently have to use other products for storing this data offline?

Offline scenarios are currently hard to cover with standard SAP technologies alone. The problem is usually solved either by cumbersome paper-based processes or by deploying third-products that includes a standalone database. This introduces overheads in the form of comprehensive manual data entry or integration challenges with third-party applications.

Baked into the SharePoint and Office platform (2010) is a comprehensive framework for managing data offline and synchronising it with the system of origin. This means that SAP data surfaced through Duet Enterprise can be taken offline with either Outlook or SharePoint Workspace and even be updated while disconnected. The framework will automatically manage the synchronisation with the SAP back-end whenever there is connectivity.

I hope the questions above have provided you with some guidelines for qualifying scenarios for Duet Enterprise. It will be interesting to follow in the years to come. I expect we will see some innovative solutions that will boost the ROI of SAP, which is the ultimate goal. I would be keen to hear from you if you have been exploring what business processes can be improved with a Duet Enterprise solution.

Slide deck from SharePoint Saturday India

noreply@blogger.com (Kristian Kalsing) — Tue, 27 Apr 2010 01:48:00 +0000

I had the pleasure of delivering a session at SharePoint Saturday India on the weekend, an online event featuring speakers from all over the world. Kudos to Rajendra Shekhawat for taking the initiative to bring this popular community-driven concept to India. It was definitely a success and well-attended.

Last Saturday was only the first of many SharePoint Saturdays coming to India. There is already another one planned for the 8th of May 2010 which you can sign up for here. Don’t miss this opportunity for lots of free SharePoint goodness.

My session was about SAP/SharePoint interoperability. I discussed some of the motivations behind surfacing SAP through SharePoint and provided an overview of how it can be achieved with SharePoint 2007 and SharePoint 2010 as well as the upcoming Duet Enterprise platform.

SharePoint Saturday India - SAP/SharePoint Interoperability

View more presentations from Kristian Kalsing.

How is Duet Enterprise an improvement to previous versions of Duet?

noreply@blogger.com (Kristian Kalsing) — Mon, 19 Apr 2010 23:19:00 +0000

A vast majority of large enterprises have a heterogeneous solution stack with substantial investments in both SAP and Microsoft products. For those companies, the concept of surfacing SAP through the broadly deployed Microsoft UIs resonates very well. In that context, the initial release of Duet got many of these companies excited. However, it is fair to say that Duet 1.0 and 1.5 have never become the huge success that many had hoped for. After all, it was the first attempt to unite two completely different worlds, both technically and culturally.

The upcoming release of Duet Enterprise has the potential to change this. It is a complete revamp of the technical architecture from the ground up which has some significant improvements to previous versions of Duet. The focus has also shifted away from delivering specific vertical scenarios to providing a platform of base capabilities. The following three improvement areas will all contribute to a renewed interest in Duet Enterprise.

Rationalised architecture based on standard components

Currently, Duet is reliant on a proprietary Duet Server for handling the communication back to the SAP system. Apart from installing additional bits on the SAP NetWeaver Web Application Server, an additional server is required to host the Duet Server.

Duet Enterprise will no longer have an additional server component and will purely be based on the SAP NetWeaver stack and the SharePoint platform. With the Business Connectivity Services (BCS) in SharePoint 2010, new and improved capabilities for accessing business data have been baked into the SharePoint platform itself, providing Duet Enterprise with what it needs to communicate with SAP.

Not only will no additional infrastructure be required, the ongoing maintenance will leverage the existing mechanisms of both NetWeaver and SharePoint for managing upgrades and other maintenance tasks. With a landscape of standard components, the total cost of ownership is significantly reduced.

No additional client footprint

Duet 1.5 requires comprehensive configuration of all end user PCs. The required client components include the client runtime, SQL Server Express, Visual Studio Tools for Office and Office 2003 Web Components. This is another contributor to a relatively high cost of ownership.

The majority of the functionality in Duet Enterprise will be accessible through SharePoint, only requiring a browser on the client side. In other words, Office is no longer a necessary prerequisite for deploying Duet Enterprise. It is only required to cover offline scenarios.

Thanks to the symmetric architecture of the SharePoint BCS on the client side in Office 2010, the optional offline capabilities for Duet Enterprise will ship as part of Office 2010 itself, effectively meaning that having Office installed is enough to enable the offline scenarios. Furthermore any custom code required by the clients is managed and deployed through SharePoint Server.

Foundation capabilities and tools

In the current version of Duet, the pre-canned scenarios cannot be customised or extended. In contrast, the emphasis in Duet Enterprise is on providing a foundation of core capabilities upon which organisations can build their own business scenarios as required. The technical interoperability is provided out-of-the-box and companies can concentrate on delivering the business functionality following the principles and guidelines of a supported framework and using the existing development tools in the respective technology stacks.

This is a very important improvement for a couple of reasons. Firstly, because it allows organisations to build and customise solutions to meet their specific business requirements. Particularly in the big end of town, this is going to make Duet Enterprise vastly more attractive than its predecessors. Secondly, this foundation will provide an opportunity for partners to develop vertical solutions in specific industries. A healthy eco-system of partners will foster the ongoing innovation required to make the platform a success on the long term.

What happened to the .NET Connector for SAP?

noreply@blogger.com (Kristian Kalsing) — Fri, 26 Mar 2010 09:36:00 +0000

This is not really news but I get this question fairly regularly, so I thought I would clarify a few things. There seems to be a bit of confusion around whether the SAP .NET Connector is still supported and how it relates to the Enterprise Services Explorer for .NET.

The .NET Connector is an SAP product based on Microsoft .NET technologies which provides the technical interoperability required to build .NET applications interacting with SAP. Many companies use this approach for point-to-point integration with SAP where a custom interface is required and .NET is the preferred development platform. It is also commonly used in Office Business Applications (OBAs) such as Excel add-ins that communicate with SAP.

The .NET Connector interacts with SAP via BAPIs, RFCs, IDocs or asynchronous web service calls and is fully integrated with Visual Studio .NET 2003. At design time, you can generate .NET proxy classes using the integrated Proxy Wizard. Your applications will then communicate with SAP through the .NET Connector runtime using RFCs or HTTP/SOAP/XML.

After SAP released the Enterprise Services Explorer for .NET, development on the .NET Connector was discontinued. Using Enterprise Services is definitely more compliant with service-oriented architecture principles, but many, if not the vast majority, of companies running SAP are yet to deploy the Enterprise Services Repository and Registry which ships with NetWeaver 7.1, Process Integration (PI) or Composition Environment (CE).

The .NET Connector is based on version 1.1 of the .NET Framework and is only supported for Visual Studio 2003. Because the .NET Connector has been discontinued, SAP will not provide newer versions for Visual Studio 2005 and 2008. There is, however, a suggested workaround which should work for both.

Theobald Software has been quick off the mark to offer a replacement for the .NET Connector with their ERPConnect product. Similar to the .NET Connector, the runtime is a lean assembly which communicates directly with SAP. The design time experience is slightly different using standard wrapper classes rather than a proxy class generator. It works with any version of Visual Studio.

Despite being discontinued, many companies still use the .NET Connector. But now there is a commercial alternative using Theobald's ERPConnect which has recently achieved SAP certification too.

Update: SAP has announced release 3.0 of the SAP .NET Connector. Public availability is planned for December 2010.