SharePoint SAP Integration via NetWeaver, OData and Layer2 BDLC
You can connect and synchronize native SharePoint lists with SAP data via NetWeaver, OData and the Layer2
Business Data List Connector codeless in just minutes. No SAP licenses
required for users. All SharePoint list features available without any
restrictions, e.g. search, metadata, attachments, mobile and offline access,
change notifications, workflows.
In a first step, please create the SharePoint list that will cache the SAP data
on the SharePoint side as shown below. In this case a custom list used, but you
can use any list type you want.
Fig.: Create the SharePoint list
that will host the synchronized SAP data
After creating the list, please go to
the List Settings. Find "Connect to external data source" under General
Settings. If this link does not appear, the Layer2 Business Data List Connector
for SharePoint is not installed or not activated for the current site
collection. Please register,
download, install and activate.
Fig.: Connect your list to an
external data source simply in the General List Settings dialog.
Following the link "Connect to external data source" leads to the BDLC List
Settings dialog. You simply have to:
- Select a data provider (OData in this case). The provider is part of the
BDLC package. Please install the provider manually if it does not appear in the
list. More information about the Layer2 Data Provider for OData
you will find here.
- Enter an OData connection string. In this case the SAP NetWeaver Demo Portal
is used to showcase the connectivity. Parameters are required for Url,
Collection, Authentication, User and Password.
Fig.: You only have to provide an
appropriate connection string to connect the current list to SAP.´
We have used the following
connection string to access the collection Travel Agencies using Windows
Collection=TravelAgencies; Authentication=Windows; User=myUser;
You can use your web browser to explore available collections and data
fields in web service description.
Please verify the connection. Next please display the data preview.
Fig.: SAP data preview. The
agencynum is used as a primary key (unique column).
You can additionally enter an OData
query to reduce data fields or filter data as described here.
You can use the "Add Columns" button to create the required columns in your
SharePoint list automatically from the data source. The source fields are mapped
to the target columns automatically by names (internal column name in SharePoint
- not column title). You can modify the SharePoint column title or column type
(e.g. string to number), if required. You can remove columns and re-create with
another data type, if required.
Alternatively you can custom mapping, to map certain data source fields to
certain SharePoint columns. Custom mapping allows to make use of pre-configured
SharePoint lists like contacts, tasks or calendar data without changing column
name in data source.
Fig.: Custom field / column mapping
is used to assign pre-defined columns, e.g. for a contact list.
A primary key (column with unique values) is required for effective updates.
Please enter agencynum in this case. It is mapped to the SharePoint Title column
Fig.: SAP data synchronized with a
native SharePoint list that caches the data inside SharePoint.
If it's all set, please use the
update button for first data insert. That can take a while, depending on amount
of data and configuration. Don't forget to save your list settings before. To
verify your settings, please press update again in list settings. There should
be no updates in case of no SAP data is changed. Only changed data from source
will cause inserts, updates or deletes in SharePoint.
If all works as expected you can:
- Update on-demand using the ribbon button "Update List Items".
- Setup automatic background update with an appropriate interval (one hour by
default). You can also add error notifications by email, in case something goes
wrong for any reason. A timer Job is used to keep your list current.