Important aspect of applying SAP-Microsoft interoperability within a company IT landscape, is how to start. Almost always the Microsoft and SAP departments form their own community in the company, with only limited contacts and co-operation between them, and no clear understanding of each others platforms, technologies and capabilities. See also earlier posts of Kristian Kalsing [1] and of myself [2] addressing this issue.
Raymond Smith [Microsoft Corporation] published an interesting article on this: Building an SAP/Microsoft Interoperability Team. In his article he distinguishes and details on the following aspects:
Aspects of Building an SAP/Microsoft Interoperability Team
- Build a SAP Interoperability Lab
- Determine a Proof of Concept Business Process
- Build Your Interoperability Team
- Cross Train Developers
- SAP Interoperability Training
- Determine Architecture
- Security
- SAP Architecture
- SharePoint/.NET Architecture
- POC Development
I recognize [most of] these steps from own experiences with SAP / MS interoperability implementations. For the details, I strongly advice to read Raymond's article.
No comments:
Post a Comment