SAP SharePoint Integration

SAP data can be integrated codeless with native SharePoint lists using the Layer2 Business Data List Connector via SAP NetWeaver and OData. Please take a look here for more supported systems and applications. In case you are looking for SharePoint Online data integration, you will find the right tool here.

Benefits of SAP Integration in SharePoint

• Very easy to setup in a few minutes: Create a SharePoint list, click "Connect to external data source" in the list settings, select the Layer2 Data Provider for Odata, enter connection settings and data query as shown below. That's it - no programming, no changes in SAP, no additional tools.
• Connected data always up-to-date: The connected data updates automatically in background (via SharePoint Timer Job), or alternatively, on-demand (Action Menu / Ribbon Button, URL, via workflow, API).
• One-way and optional two-way connection: You can write-back the changes made in SharePoint to the external data source automatically with full CRUD (Create / Update / Delete) functionality. The SharePoint list can act as a full-featured front-end for a SAP OData query.
• 100+ external systems supported: Layer2 Data Providers included (e.g. for SharePoint/Office 365, Exchange, Dynamics, OData, XML/RSS, SOAP), vendor specific data providers can be used (e.g. SQL Server Oracle, mySQL etc.), 3rd party data providers also supported, e.g. for ERP/CRMs, Facebook or Twitter. See here for supported systems and applications.

• Well-known BCS "external list" issues and limitations are completely solved: ALL list features are to you. Views, sorting and grouping, filters, calculated fields, search, managed metadata. Lookups, additional columns and attachments can be created as normal. All kind of lists can be used, e.g. contacts, tasks, calendar, or custom lists. You can take external data offline via Outlook.

• SharePoint workflows and notifications on SAP data change: List workflows and change notifications per RSS or email can be used to take business actions in SharePoint, when external business data records are changed.

• Application logging, reporting, and notifications: A SharePoint list ist used to store settings and log information. SharePoint item versioning and workflows can be used to manage reporting and notifications. Direct notification per email in case of errors is supported as well.

• Highest Security, best performance, easy to maintain: SharePoint Secure Store can be used to store security relevant configuration information safely in one central place. Users are working with the SharePoint lists as an external data cache with highest security and performance.

SAP Specific Configuration Settings

Basically, you can start with the Layer2 Business Data List Connector when you are able to see valid OData (some kind of XML data) in your browser. If you are not familiar with both, OData and SAP, take a look here to learn more.

In the Layer2 Business Data List Connector, the data source must be configured as follows to connect to SAP.

Figure 1: Sample connection configuration to connect to SAP via Layer2 Data Provider for OData

Please note the following about settings, features and possible issues

• Select the Layer2 Data Provider for OData to connect. The provider is part of the Layer2 Cloud Connector ADO.NET provider package and should be already installed with BDLC. You will find an OData Provider specification here.
• Generally, you can use a connection string like this to connect:url=https://mysapportal.mydomain.com/pathtomycollection; Collection=myCollection; User =myDomain\myUser; Password=myPassword; Authentication=Windows

• SAP offers free access to a demo system to verify Layer2 Cloud Connector connectivity. Please register here. To connect to the SAP demo system you can make use of a connection string similar to this:

  url=https://sapes5.sapdevcenter.com/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT/; Collection=TravelAgencies; Authentication=Windows, SAPCsrfHeader; User=P********;

• Please replace the user token with your specific account and add a password to the password field.

• Several different authentication methods are generally supported. See provider specification linked above for more.
• You can make use of OData to query your data as supported by the data provider and source system. For any specification of supported queries see SAP Netweaver documentation. You can browse OData collections in the web browser. Simply paste your url from there.
• You can map your data fields to specific external fields in the Layer2 Business Data List Connector. Please take care about data types (simple type conversions are supported).
• Please enter an appropriate primary key (column with unique values), depending on the query (see data preview for this).
• No installation or changes are required at the SAP data source.
• Data synchronization can be started manually in SharePoint or scheduled in the background by the Layer2 Business Data List Connector. Only data changes are processed (no delete/bulk import).
• No programming required to setup a connection and sync. No touch of the SAP system.
• If you don't have OData access to your SAP data yet, you can alternatively connect and sync via database queries or intermediate text / csv files created by scripts.

Do you have any issues to connect? Please contact sales@layer2solutions.com for next steps.

SAP Connection Details

​​​Provider:
Layer2 Data Provider for OData

Connection string sample:
Url=https://sapes1.sapdevcenter.com/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT/; Collection=TravelAgencies; Authentication=Windows; User=myUserId; Password=myPassword

Select Statement sample:

SAP Data Integration Known Issues

• Depending on requirements there are some steps on the SAP-side to connect to specific data entities. Please find  an intro here.
• You can use the connection for uni- or bi-directional synchronization. In case of inserts (full CRUD) via external systems please take care of the primary key. SAP-side IDs will not work in his case.
• OData via SAP Netweaver Gateway Introduction:
  http://www.sapyard.com/odata-and-sap-netweaver-gateway-part-i-introduction/
• Step-by-step guide to build a custom OData Service based on SAP RFCs:
  https://blogs.sap.com/2012/10/26/step-by-step-guide-to-build-an-odata-service-based-on-rfcs-part-1/

Ready to go next steps?