We’ve expanded our Duet Enterprise Self-Paced Learning offering. 

Access Duet Enterprise Self-Paced Learning using the following link.

Developing your own applications using Duet Enterprise

How can custom applications be developed using Duet Enterprise to expose SAP data to Microsoft SharePoint 2010 and Microsoft SharePoint 2013? 

Sessions from this track have been developed by both Microsoft and SAP to cover the different developer points of view.

Feature Pack 1 For Duet Enterprise 1.0 for SAP and Microsoft SharePoint 2010 

This online training uses the SAP NetWeaver Gateway OData paradigm for development and includes over 100 minutes of recorded lessons and demos as well as additional pdf guides. 

i)          Four lessons which are recorded presentations provide an overview on requirements and how to develop an application.  Hard copies of the presentations are available in pdf form.

ii)          Six demo videos show online step by step instructions on how to create an end-to-end solution using the SAP EPM Sales Order. It ranges from creating an OData service using SAP NetWeaver Gateway, using the Duet Enterprise BDC model, importing the generated model into Microsoft SharePoint 2010 and then utilizing Client OM or simple JavaScript to further enhance the application on Microsoft SharePoint 2010.    

iii)         Exercises are based on Feature Pack 1 for Duet Enterprise 1.0 Developer Guide

Duet Enterprise 2.0 for SAP and Microsoft SharePoint 2013

Creation of an OData service in SAP NetWeaver Gateway for a Purchase Order scenario supported by Microsoft SharePoint 2013 will be covered.   The standard methodology of bringing in an OData service to Microsoft SharePoint 2013 can then be used.

Additional In-Depth Duet Enterprise 2.0 Content

With the introduction of Duet Enterprise 2.0 in Q4 of 2012, a full curriculum covering the new version has been added under the various categories. Over 160 minutes of how to videos and additional how-to pdfs will give students well-rounded training on Duet Enterprise 2.0.

i)          Installation & Configuration: How to guides covering Duet Enteprise 2.0 on-premise and online, as well as setting up Role Synchronization.

ii)         Workflow:  Videos and guides ranging from how to expose an SAP Workflow using Duet Enterprise 2.0 to extending workflow capabilities.

iii)        Reporting: Videos and guides covering report configuration and available features and functions.

iv)        Tracing: Videos demonstrating how to troubleshoot Duet Enterprise 2.0 

Further Links

The Introduction to Duet Enterprise Self-Paced Learning blog introduces the Duet Enterprise Self-Paced Learning concept and initial offerings.

Getting Support

For additional support on Duet Enterprise, post your questions on the Duet Enterprise forum which is monitored by various experts.

As part of the installation and configuration of Duet Enterprise 1.0, a user mapping step is required to determine which Microsoft Sharepoint User Id is mapped to which SAP User Id in the Service Consumption Layer (Netweaver 7.02).    

• User Mapping configuration is always required regardless if the user ids in SAP and SharePoint are the same.
• The mapping configuration is done on the Service Consumption Layer (Netweaver 7.02) of the Duet Enterprise Landscape.  

The following diagram shows how users may exist in a standard Duet Enterprise Landscape: 

1)      In most cases Sharepoint Users are Active Directory Service Users   and probably do not have the same user ids as the SAP UserID

2)      There could be multiple backend systems attached to the landscape.  In this example, we will assume an SAP ERP system and a BI system have been configured in the landscape.  

a. SAPUSER2 and SAPUSER3 will be authorized to run applications in Duet Enterprise from the SAP ERP system. 

b. SAPUSER1 and SAPUSER2 will be authorized to run BI Reports in Duet Enterprise

c. All 3 of the SAP users must exist on the Service Consumption Layer.

3)      When calls are made from Sharepoint, the requests are sent to the Service Consumption layer.  Since the SCL was set up as a separate system (recommended), Sharepoint does not make direct calls to the SAP Backend systems, only to the SCL.  On the Service Consumption layer, the table VUSREXTID is used to determine the SAP user id based on the Sharepoint user who made the call.

Here are 3 example of how User mapping can be performed for Duet Enterprise:

1) User Mapping with an LDAP connection (recommended for production) 

• This method can be used when Sharepoint and SAP user ids are different.  Mapping is done using an LDAP attribute from the ADS which will store the SAP ID
• This method can also be used when Sharepoint and SAP user IDs are the same.  The LDAP attribute sAMAccountName will be used

For more information refer to the following post:

Duet Enterprise User Mapping with an LDAP connection

2) User Mapping without an LDAP connection 

• This method will only work if Sharepoint and SAP user ids are the same. This method is generally used for Proof of Concept projects.

For more information refer to the following post:

Duet Enterprise User Mapping without an LDAP connection where Sharepoint and SAP User Ids are the same

3) User Mapping using a file upload

• This is an alternative method to use when there is no LDAP connection available and Sharepoint and SAP User IDs are different.

For more information refer to the following post:

Duet Enterprise User mapping using a CSV File