My name is Chris Keyser.  I’m the Group Program Manager for Duet.  We’ve kicked off our blog, and it’s just the start of establishing a richer dialog with our customers.  We want to hear from you about what you think about Duet, what you think about Office Business Applications, and what you’d like to see coming in the future.  And if something is preventing you from becoming a Duet customer, we’d like to hear about that too.  You can reach me at ckeyser@microsoft.com.

 

I moved into my current role in Microsoft about six months ago.  I took the opportunity because I believe that Office Business Applications will transform the way that many users interact with line of business systems and think about the value of Office.  I am enthusiastic about partnering with the leader in enterprise line of business application, SAP, to develop the richest set of enterprise class Office Business Applications on the planet.  We want to make you and your company more effective in the way you execute your job today, and open up new ways for you to innovate and collaborate on driving your business moving forward – to not just talk about, but actually enable bridging the way that people interact and collaborate every day more effectively and broadly with valuable data and processes in back end business systems.

 

We’ll be giving you more and more technical content moving forward via this blog.  Delivering a joint product between two big companies presents challenges, but SAP and Microsoft are committed to working together making  our Duet product a success.  Part of that is figuring out how we jointly support our product.  Along those lines, I thought the first tidbit from one our technical specialists will actually be about a tool for validating a SAP backend prerequisites for Duet:

 

The Check Tool is delivered when you install the ECC-SE 500 add-on (for ECC 5.0) or ECC-SE 600 add-on (for ECC 6.0) into your ABAP system with Support Package 03.  Add-on’s are installed using transaction SAINT.  Support Packages are installed using transaction SPAM.

   

To launch the tool, go to transaction SE38 and execute program /OSP/CHECKTOOL.  From the list above, you can see there are many fixes to the tool that have to be implemented using transaction SNOTE.  Fixes are downloaded from the SAP Service Marketplace Notes section using the SAP Download Manager and applied via SNOTE in SAPGUI.