Monday, July 6, 2009

BizTalk Light and Easy Viewing Series - SAP Adapter

A couple months back Mick Badran, a BizTalk MVP from Australia, got a few MVPs and other BizTalk experts together to put on a series of webcasts that cover various topics in BizTalk Server 2009.One of the topics that I decided to tackle was the new SAP Adapter ( as found in BizTalk Adapter Pack). In this webcast I cover the following topics:
  • SAP Background Information
  • Why do companies use SAP
  • Challenges with integrating with SAP
  • Previous SAP Adapters
  • BizTalk Adapter Pack 2.0
  • Demos

Alan Smith has launched a site that will host the Light and Easy series in addition to other Microsoft related webcasts. If you are interested in seeing this webcast here is the link: http://www.cloudcasts.net/ViewWebcast.aspx?webcastid=2521554266599869567

If you have any questions or comments about the webcast, feel free to leave a comment on the blog.

2 comments:

Todd Hensley said...

We are a new SAP shop, and we will be using the SAP Adapter with BizTalk. Nobody seems to know what permissions the developers will need in SAP to use the adapter effectively. Apparently SAP_All isn't an option ;-)

Is there a recommended group, role, or specific permissions that you think BizTalk developers should have on the SAP side?

Thanks!

Kent Weare said...

Hi Todd, I am going to get a better answer for you as our BASIS team does set this up but I can tell you that it is not "SAP_All".

For the BizTalk user itself:
I do know that we create parter profiles for each BizTalk app that we have and then we assign which IDocs that BizTalk is allowed to call within this Partner profile. You do have the ability to distinguish between the IDOcs we are allowed to send and the IDocs we are allowed to receive.

For BizTalk developers who are logging into the SAP GUI: we have been put into an "ABAB Support" group. You will want access to WE02 (IDoc search screen). You will also want access to other transactions as required(CIC0). We have tried to get SM58 access (RFC Queue) but were unsuccessful

Stay tuned...