SAP integration into Office 365 and SharePoint is a typical project requirement, but sometimes not easy to solve. It is not only about data migration, it is about permanent integration in a hybrid scenario. And integration is not about displaying data in SharePoint, e.g. using Web Parts or BCS. It's about FULL integration, e.g. in SharePoint search, content categorization, change notifications, workflows to start business processes right in SharePoint in case of external data changes in SAP. This article shows how easy full SAP to SharePoint and Office 365 integration is today using the Layer2 Cloud Connector and the Layer2 Data Provider for OData via SAP NetWeaver without any coding. It just needs a few minutes of configuration.

How-to-connect-SAP-to-SharePoint-Office-365-YouTube.jpg

SAP SharePoint and Office 365 Integration via NetWeaver / OData

In this example we are going to create a new connection in the Layer2 Cloud Connector, or copy from the existing SAP to SharePoint sample connection. It should be uni-directional SAP to SharePoint. Generally bi-directional connections are supported as well. You can enable background scheduling later on to update the SharePoint list automatically.

At this time the connection should look like this:

SAP-Office-365-SharePoint-Integration-NetWeaver-OData-01.png

 Fig. SAP to SharePoint connection defined in the Layer2 Cloud Connector.


We are going to use the new SAP NetWeaver demo portal as a data source. Please note that you must register to gain access. You will find a service description here after login. If you don't have access yet, please register here before. Now it is easy to configure the SAP data source in the Layer2 Cloud Connector. It should look like this:
 
SAP-Office-365-SharePoint-Integration-NetWeaver-OData-02.png

  Fig.:SAP data source defined in the Layer2 Cloud Connector.

 
To access the SAP data please select the OData Provider from the list of available providers. If not available, please install. It comes as part of the Layer2 Cloud Connector installation package (license is included). Please specify URL, collection, authentication method, user and password in the connection string section. You will find a specification of supported attributes in the Layer2 Data Provider for OData specification. You can also use valid OData expressions as a select statement to filter the source data for specific criteria or remove unwanted fields. Please verify the connection string.
 
In case of the SAP Demo portal we are using:
 
URL=https://sapes1.sapdevcenter.com/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT/; Collection=TravelAgencies; Authentication=Windows; User=P***; Password=***
 
You can also add parameters to the query like this:
 
URL=https://sapes1.sapdevcenter.com/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT/FlightCollection(carrid='AA',connid='0017',fldate=datetime'2013-05-01T00%3A00%3A00')
 
After successfull verification, please display the data preview. As you can see, there is a unique ID field agencynum in the data set. Please set as primary key for data synchronization as shown above.
 
Note - Connecting to SAP may require an additional authentication method: SAPHeader. This secondary authentication re-enables writing access to SAP systems after the addition of the cross-site request forgery token. It has to be attached to an existing authentication as it won't work by itself. See the User Documentation included with the Connector for more details.
Example: Authentication=Windows;SAPHeader;
 
Now lets connect the data destination, a SharePoint Online contact list in Office 365 in this example. SharePoint 2010 / 2013 on-premises and SharePoint Foundation are supported as well (with different connection strings). Please select the CSOM provider to connect. Please add a connection string that contains the URL to the SharePoint site, list and view, also the authentication method and user / password. See a full CSOM connection string specification here.
 
SAP-Office-365-SharePoint-Integration-NetWeaver-OData-03.png
Fig. SharePoint Online list as data destination for SAP queries defined in the Layer2 Cloud Connector. 
 
The list must be created manually before connect in SharePoint. As in our sample we have address data, we create a new contact list to have some more contact-specific features later on - like Outlook offline replication or mobile access. We additionally create a column SAP-ID to have any hint, where the item data exactly comes from. No primary key must given for SharePoint, item ID is always used automatically by the provider. Please verify the connection.
 
Now we have to map the SAP data fields with the SharePoint list columns. We cannot use the auto-mapping feature of the Layer2 Cloud Connector in this case, because SharePoint contact columns have specific names, different from SAP.
 
The mapping section should look like this (you can map more columns later):
 
SAP-Office-365-SharePoint-Integration-NetWeaver-OData-04.png
Fig. Field / Column mapping for data source and destination in the Layer2 Cloud Connector.
 
Please note the field "name" is mapped to the SharePoint "title" column (actually the Lastname of a SharePoint contact list). Also our primary key agencynum is mapped to our additional column SAP-ID. Please verify the mapping before continue.
 
Now we are prepared to run the first sync. The Layer2 Cloud Connector now talks to SAP (via Netweaver/Odata) and to SharePoint / Office 365 (via CSOM) and syncs the data entities as required.
 
SAP-Office-365-SharePoint-Integration-NetWeaver-OData-05-600.png
 
 Fig. First sync of SAP data source and SharePoint list via the Layer2 Cloud Connector.
 
Now take a look at our connected SharePoint list.
 
SAP-Office-365-SharePoint-Integration-NetWeaver-OData-06.png
 
Fig. Native SharePoint contact list connected to SAP data via the Layer2 Cloud Connector. The contact list can be connected to Microsoft Outlook for offline sync and has all other features of a native SharePoint list.
 

SAP & SharePoint Synchronization via Layer2 Cloud Connector - Benefits

​Please keep the following in mind about this integration approach:

  • All SharePoint features are fully available for the list, because it's simply a native list (no BCS): Views, search, metadata, lookups, change notification via RSS or email, workflows on SAP data change, offline and mobile access etc.
  • SharePoint list data is updated scheduled in background or on-demand via secure connection. It's not about bulk import, the items are safely updated. Addional unmapped columns or attachments are being kept. In case of no or a few changes only appear, the sync should be very fast.
  • No access from outside to the corporate network is required. The Layer2 Cloud Connector operates from inside the company network. No 3rd party involved.
  • No installation or changes in any system required, not in SAP, not in SharePoint.
  • Users work with synced data copies in SharePoint (or in the cloud) as some kind of cache with best performance, availability and security. No access to SAP required (means no licenses). That really simplifies the architecture.
  • Bi-directional operations are fully supported. Please use the SAP OData Generator to create the CRUD operations required (in more complex situations).
  • The Cloud Connector does not only support OData. It can connect to almost any data sources, including databases, XML or the local file system, to sync with SharePoint.

SAP Integration with SharePoint Online or On-Premises - Documentation

SAP-SharePoint-Office-365-Integration.jpg
Fig. Please click the image for a SAP - SharePoint / Office 365 Integration full-screen presentation.

SAP Integration with SharePoint Online or on-premise - Next Steps

​​Please register and download your evaluation copy today on the Layer2 Cloud Connector product page. Contact [email protected] directly in case of any questions.
Share this site on Xing
Share this site on Google+
Share this site on LinkedIn

This tool fills an open gap with SharePoint integrating external data sources. I've tried - Oracle, MS SQL, and others. And it's really fast! A must-have for any SharePoint implementation, whether standalone or Office 365. You can't live without.

 

 Download & Evaluation

 
Please register to receive your free personal download link via email to your valid company email address.
Name: 
Company: 
Country: 
Phone: 
E-mail: 
Yes, I accept the licensing terms and conditions
Contact
Frank Daske

Frank Daske

Business Development Manager
+49 (0) 40 28 41 12 - 30
[email protected]

Please note that the 011 exit code must be dialed first for all international calls made from the USA, Canada and Australia.

Related News

Layer2 now connects 100+ commonly used IT systems with Twitter via its Layer2 Cloud Connector

The Layer2 Cloud Connector is now able to connect Twitter to integrate data to a wide range of IT backend systems including Office 365, SharePoint, SQL, ERP/CRM.

New Microsoft Teams Connectors: Layer2 adds 100+ typically used backend systems

​The Layer2 Cloud Connector is now able to connect to Microsoft Teams to quickly integrate more than 100 IT backend systems including local SQL, ERP/CRM.
Related Downloads
PDF Image

Cloud Connector Instruction

Download this step-by-step instruction to connect and sync your corporate or cloud data sources bi-directional to any native SharePoint 2010/2013/2016 list or library, including Microsoft Office 365.
PDF Image

Feasibility Study: Connecting local SQL Server to SharePoint Online

The study compares different approaches for SharePoint Online data integration regarding performance, features, security and investment.
PDF Image

Flyer: Layer2 Partner Program

Partner with us as a software distributer, reseller or SharePoint, Office 365 or Azure service provider. We are offering a free Partner Program with up to 30% Discount, free NFR licenses etc. Please download for more.
PDF Image

Layer2 Case Study: Cloud Connector helps ChemWerth to integrate the Microsoft Office 365 Cloud

"The Cloud Connector’s interface is easy to understand and use. Anyone familiar with utilities in the Microsoft stack will be productive immediately. Our recommendation: The Layer2 Cloud Connector is a no brainer.”
NoDoc Image

Layer2 Cloud Connector PAD File

This XML-based PAD file offers a Layer2 Cloud Connector product description for resellers to download and publish.
PDF Image

Office 365: How to sync with MS Dynamics CRM

You can sync any CRM data with native lists in SharePoint on-prem or online to make it available offline with Outlook.
PDF Image

Office 365: How to sync with SAP?

You can connect SharePoint and Office 365 with SAP via NetWeaver and OData.
PDF Image

Office 365: How to sync your local file share?

When you are moving to the cloud, there are a lot of reasons to keep your local file system. But you don't have to miss the benefits of the cloud.
PDF Image

Product Flyer: Cloud Connector for Microsoft SharePoint & Office 365

Flyer with features, benefits & pricing info for download as PDF.
PDF Image

Product Flyer: SharePoint Online Local File Server Sync

You can centrally migrate, synchronize, or backup your local file server department shares and home drives very flexible with SharePoint Online to close known gaps and overcome limitations of the Microsoft OneDrive for Business client.
PDF Image

Solutions Flyer: Data Integration with SharePoint, Office 365 and 100+

FileMaker can be integrated with 100+ other sources codeless using the Layer2 Cloud Connector.
Related Links

Layer2 Cloud Connector Community Group @ LinkedIn

​Are you already @ LinkedIn? Please join the Cloud Connector Community Group to share your experience.

Microsoft Partner Story Book for Office 365 about Cloud Connector

​Know more about a Layer2 Cloud Connector customer reference at the Microsoft Office web site.

Purchase Layer2 Cloud Connector via ComponentSource

​ComponentSource has offices in the USA, UK and Japan supporting over 125,000+ Customers, in over 180 Countries. They are also an approved Federal Government supplier through the GSA Schedule.

 

cs-award-top-100-publisher-2014-15-large.gif

Sign Up for Layer2 Product Newsletter

We keep you up-to-date about new Layer2 product releases, added features and fixed issues.