1 2 3 7 Previous Next

Duet Enterprise

96 Posts

Read on if you are a Duet Enterprise customer attending SAPPHIRE NOW + ASUG!

 

SAPPHIRE
NOW + ASUG ANNUAL CONFERENCE

Orange County Convention Center

Orlando, Florida

May 14-16, 2013

 

 

We look forward to seeing you in Orlando for the SAPPHIRE NOW + ASUG ANNUAL
CONFERENCE 2013, at the Orange County Convention Center, May 14-16, 2013! In
addition to the main SAPPHIRE NOW program, we would like to invite you to meet
other SAP customers using critical SAP 3rd party solutions, offered by SAP. The
roundtable sessions connect you with customer experts and community members, so
that you can gain insight and inspiration.

 

 

You are cordially invited to participate in one or more Reference Customer Roundtables.

 

 

INVITATION-ONLY l REFERENCE CUSTOMER ROUND
TABLES


A customer round table will provide you with a forum to interact with a current
customer who has already completed the decision-making process and followed
through with a successful implementation. Seating is limited to 10 to 12
attendees to ensure interaction and to maintain the intimacy of the event. The
sessions are designed to facilitate an open dialogue surrounding the decision
process, key value, and the successful implementation. Full descriptions of
each roundtable can be found below.

 

 

May
14 Round Table: Register here

 




15:30 - 16:45 |


 

Dr Pepper Snapple Group  l Duet Enterprise


Dr Pepper Snapple Group is a  leading producer of flavored beverages in North America and the Caribbean.
  Their success is fueled by more than 50 brands that are synonymous with  refreshment, fun and flavor. The company's integrated business model enables
  the company to manage the entire value chain from innovation to the store  shelf. Over the past 3-5 years Dr Pepper Snapple Group has invested heavily
  in their SAP transactional business systems. In order to deliver a solution  that has a familiar Microsoft style user interface Dr Pepper Snapple Group
  implemented a new mobile purchase requisition approval process utilizing Duet  Enterprise. Learn how Dr Pepper Snapple Group has been able to increase  adoption, speed in the process, increase accuracy of purchase orders, and  increase productivity. This session is limited to 8-12 customers to allow for  an interactive discussion and help you to better understand the challenges  faced, selection process, implementation, lessons learned, and key successes.


 

 

 

Assumption: Outlined Deployment options are for Gateway 2.0 SP06 with SharePoint 2010 and SharePoint 2013 only (with everything On-Premise).

 

Integrating SharePoint 2010 with SAP Business Suite

Here, in this case, Duet Enterprise 1.0 FP1 must be used with Gateway 2.0 SP06 

 

Gateway Deployment Approach:  Here, all 3 Types of Gateway Deployment Approaches can be used i.e.

a) Central Hub (IW_FND, GW_CORE) with IW_BEP (Backend Event Publisher) in the Backend

b) Central Hub (IW_FND, GW_CORE) along with IW_BEP in Gateway System itself.

c) Embedded Installation (IW_FND, GW_CORE, IW_BEP in Business Suite Server itself)

However, careful selection must be made while choosing one of these options depending on version of your backend business suite system and underlying NetWeaver layer.

 

If you choose to go for option b and c, you must install component for Backend Event Publisher (IW_BEP) in Business Suite System (For Ex. ERP, CRM etc.). Minimum requirement for installing this Add-On in the SAP Business Suite backend system is SAP NetWeaver 7.00 Support Package 18.

Details of Minimum requirements for each Gateway component with Pro and Cons of each deployment types can be found here:  http://help.sap.com/saphelp_gateway20sp06/helpdata/en/88/889a8cbf6046378e274d6d9cd04e4d/frameset.htm

 

If you decide to use Embedded Installation, extra care must be taken while doing the Duet Enterprise Configuration such as Self Pointed RFC Destinations (while doing connection settings between Gateway and Backend) , configuring system to accept Assertion/Logon Tickets (really needed?) etc.

 

SSO and Security Approach: In Duet Enterprise 1.0, calls from SharePoint 2010 to Gateway 2.0 are provisioned through SOAP/HTTP. HTTP messages are encrypted via SSL. Technology used for Single-Sign-On in this case is SAML 2.0 (Recommended by SAP for SSO with Cross Site Applications i.e. Applications existing in different domains).

 

Web Service Development Approach:  Exchange of information between SharePoint and Gateway happens through SOAP Calls via HTTP because SharePoint 2010 does not support consuming OData services out-of-the-box. But ideally this should not deter us from using OData Channel. OData services are light weight and are suitable channel for all types of devices.

Hence, with Duet Enterprise 1.0’s Feature Pack 1, an extension for the development tool “BDC Browser” is provided .This provision is called “SOAP Bridge” (Logical Name). It facilitates conversion of OData Output to SOAP Output.  This means that you can do OData development with latest version and deployment of Gateway (using SEGW). Then, at the end, when you want to expose it to SharePoint 2010, you can use the SOAP Bridge in between to convert the OData output to SOAP output (Flattened Service Output).

The main advantage of using this approach is minimum disruption when you upgrade to SharePoint 2013. SharePoint 2013 supports OData Service Consumption out-of-the-box. When you upgrade, you just have to get rid of the SOAP Bridge and thus, no change would be required in already done developments. However, Generic channel is also supported for developments already done. But, this channel is not recommended for planning new developments.

 

Integrating SharePoint 2013 with SAP Business Suite

Here, in this case, Duet Enterprise 2.0 must be used with Gateway 2.0 SP06

 

Gateway Deployment Approach:  Here, in this case as well, all 3 Gateway Deployment Approaches can be used.  All the details are same as I mentioned above.

 

SSO and Security Approach: As of now, OData doesn’t support SAML 2.0 which is ideal for cross domain SSO. Best fall back option in this case is using X.509 client certificates. Thus, in Duet Enterprise 2.0, SSO is engineered via X.509 certificates issued by its SharePoint Add-on. Here again IDP lies on SharePoint. As in SharePoint 2010, Messages (HTTP), here as well, are secured using SSL.

 

Web Service Development Approach: Here, as I mentioned above, we must prefer OData Service Development via Gateway Service Builder (SEGW) because SharePoint 2013 support OData consumption out- of-the-box. However, again, Generic channel is supported for developments already done but not recommended for new developments.

 

What Changes with NetWeaver 7.40?

 

Below is the noteworthy extract from: http://help.sap.com/saphelp_gateway20sp06/helpdata/en/88/889a8cbf6046378e274d6d9cd04e4d/frameset.htm

 

“As of SAP NetWeaver 7.40, the core software component for SAP NetWeaver Gateway is SAP_GWFND, which contains the composite functional scope of IW_FND 250, GW_CORE 200, IW_BEP 200, and IW_HDB 100.

Consequently, if you have an SAP NetWeaver 7.40 installation, you can use SAP NetWeaver Gateway without having to install any additional software components.

If you have an SAP NetWeaver 7.40 installation and you have previously created services for the Generic Channel that are still in use, you must install the software component IW_FNDGC 100. You only need to install this optional component if you have existing Generic Channel services.”

 

To me, this all sound like a clear message that, in Future SAP landscapes, NetWeaver Gateway will become THE technology for exposing SAP data to all types of devices and platforms and Duet Enterprise should definitely benefit from it.

Hello,


This blog is in continuation to my earlier blog (http://scn.sap.com/community/duet-enterprise/blog/2013/04/01/duet-enterprise-infrastructure-setup-difficult-really)  where I listed some important points to consider while setting up Duet Enterprise for SAP and SharePoint Integration.


In this blog, I would try a feature wise call stack dissection for Duet Enterprise 1.0 FP1. It is strictly applicable for 1.0 FP1 scenarios only where integration between SAP and SharePoint 2010 is required. Currently, this information is scattered between Duet Enterprise and Gateway’s configuration guides and it becomes difficult to understand the big picture.

This might results into higher configuration costs. Hence, a level of clarity in big picture is a MUST before you start your Duet Enterprise Configuration.


So, let’s try to understand (feature wise) connectivity behind every call processed in your SAP Landscape. The software components to be used and version details could be found here (http://scn.sap.com/thread/1984980)

 

 

Starter Services and CRUD + Q Operations (This is Online or Synchronous Request/Response Cycle)

 

Request Cycle

SharePoint to Gateway/Duet Enterprise Server: HTTPS Calls with SAML Tokens for SSO (Utilizing User Mappings done in Gateway or LDAP)

 

Gateway/Duet Enterprise Server to SAP Backend:

  1. a)      Trusted RFC Calls (Type 3 RFCs - ABAP Connections)with current user for SSO for custom RFCs(CRUD) and some of Starter Services.
  2. b)      HTTP Calls (Type H RFCs - HTTP Connection to ABAP Systems) with Logon Tickets for SSOfor some Starter Services. Both backend and Gateway must be enabled to create/accept Logon Tickets.

Response Cycle

SAP Backend to Gateway/Duet Enterprise Server:

     a) Online Trusted RFC Response (Type 3 RFCs - ABAP Connections) for custom RFC Calls (CRUD) and some of Starter Services.

     b) Online HTTP Response (via already opened HTTP Connection) with Logon Tickets for SSO for some of the Starter Services.

 

Note 1: If you want to use SSL for these HTTP Calls here, then exchange certificates betweenBackend and Gateway Server but make sure to secure your RFCs with SNC too!

(Courtesy – Holger Bruchelt from Duet Enterprise Solution Management)

 

Gateway/Duet Enterprise Server to SharePoint:  HTTPS response utilizing User Mappings in Gateway/LDAP

 

 

Reporting Feature: Request and Publishing

(This is generally Offline or Asynchronous Request/Response Cycle)

 

Request Cycle

Report Request from SharePoint to Gateway/Duet Enterprise Server: HTTPS Calls with SAML Tokens for SSO (Utilizing User Mappings done in Gateway or LDAP)

 

Gateway/Duet Enterprise Server to SAP Backend: Trusted RFC Calls (Type 3 - ABAP Connections) with current user for SSO.

The report request ends here. As the next step, response is built in the format specified in the Reporting Configuration (Excel, PDF etc.).

Advantage for making this setup asynchronous is that SharePoint doesn’t have to wait in case of bulky SAP Reports and it doesn’t choke your network bandwidth (No Waiting/Open HTTP Connections while processing inside Gateway/Backend). Though, it poses some challenges from monitoring/failure analysis point of view but we have a few good tools from Gateway here:

  1. a)      /iwfnd/apps_log (This log clearly shows every call in both backend and Gateway with directions)
  2. b)      srtutil or /iwfnd/error_log
  3. c)      A special guide from SAP on tracing problems in this feature (Check Duet Enterprise Self-Paced Learning Page)

 

Having said that, this is how the response cycle looks like in this case:

 

Response Cycle

Report Publishing from Backend to Gateway: A new HTTP Call (Type H - HTTP Connection to ABAP Systems) with Logon Tickets for SSO. Please refer Note 1 in this case too.

 

Report Publishing from Gateway/Duet Server to SharePoint: A new HTTP Call to SharePoint’s OBA File Receiver Web Service via a specific Report Publisher User in the Gateway System. Web Service details and publisher user’s credentialscould be setup via setting up endpoints in consumer proxy during Reporting configurations on SAP side.

 

 

Workflow Feature: Workitem Publishing from SAP to SharePoint

(In this case process is initiated by SAP Backend Mostly, and then there could be separate calls from SharePoint to publish decisions on workitems)

 

Workitem Publishing from Backend to Gateway/Duet Enterprise Server:

HTTP Calls (Type H - HTTP Connection to ABAP Systems) with Logon Tickets for SSO. Note 1 applies in this case too.

 

Workitem Publishing from Gateway/Duet Enterprise Server to SharePoint:

HTTP Calls to SharePoint’s OBA File Receiver Web Service via a specific Workflow Publisher User in the Gateway System. Web Service details and publisher user’s credentials could be setup via setting up endpoints in consumer proxy during Reporting configurations on SAP side.

 

Propagation of Decision (with Information) on Workflow Tasks from SharePoint to Gateway /Duet Enterprise: These published tasks are when acted upon by decision makers who are using SharePoint UI, a new HTTP connection (and uses SAML Tokens for SSO) is created to propagate this tasks level information to Gateway.

 

Propagation of Decision (with Information) on Workflow Tasks from Gateway/ Duet Enterprise to SAP backend: Trusted RFC Calls (Type 3 - ABAP Connections) with current user for SSO.


 

Role Synchronization/Propagation from SAP to SharePoint

 

SAP Backend to Gateway/Duet Enterprise: In Gateway System, Roles, which are configured for use in SharePoint as a consumer,are brought in from backend via a System Alias (Type 3 RFC Destination).

 

Gateway/ Duet Enterprise to SharePoint: This call is performed by a Timer Job on SharePoint, which reads Gateway’s User-Role Table named /IWFND/D_RS_DATA via a HTTP Call (Web Service) via a fixed mapped backend Service User in Gateway. Thus, mapping the background service user is also important for setting up Role Synchronization.

 

There is one more connection which exists in this landscape but not included in this call stack for the sake of keeping it simpler – Gateway to ESR. Web Service definitions (data types etc.) come from the ESR system, which is hosted by either your NetWeaver PI or CE System. This is again an HTTP Connection. ESR, in turn, could be connected to SLD (Software component versions could be imported from SLD as well).

 

I hope this would be valuable information while starting your SAP and SharePoint 2010 Integration. In next and last blog of this series I would try to dissect Duet Enterprise 2.0 call stack.

 

Lastly, I would say, if you feel I have missed or misunderstood anything, you are more than welcome to use comments section below for more interesting discussions.

 

To be continued...

 

Thanks,

Saumil Jyotishi

This week's ASUG News article written by Thomas Wailgum offered a rare introspect to the dynamics of when "elephants dance" - namely the deep relationship between SAP and Microsoft and the architectures that join the two together.  It poses the age-old question: can two large companies, vying for overlapping market space, come together and collaborate in the same market waters.

 

There can be no question that Microsoft is the dominant player in office management application software.  I cited in my recent SCN post to this very Duet Enterprise page that 3/4 of all large enterprise customers either use Microsoft SharePoint or plan to do so in the future.  That's a heady number.  So what drives SharePoint adoption without the exclusion of other web-based portal environments like SAP?  In short: SharePoint is easy to use, secure to store large amounts of documents in repository fashion, with helpful plug-ins to native Microsoft platforms (like Microsoft Project) that drive the need to get work done.  And we all use them.  Even if we are working on an enterprise risk management (ERM) initiative using SAP RM10, or a project plan using SAP Project Schedule (PS), we have the smart ability to output to Microsoft platform tools.  Even SAP's Planning and Consolidation tool (formerly known as BusinessObjects BPC) runs natively on a Microsoft Excel environment as a ribbon plug-in.  The integration is quick, intuitive, painless and in a native environment that everyone has and knows how to use.

 

SAP's major offensive push is to create a low-cost of entry user adoption scenario for large enterprise customers who already have Microsoft SharePoint as a user interface investment well established in their user groups with the need to access SAP Business Suite and LOB solutions.  This reduces user ramp-up and training costs (no need to learn SAP GUI or web-based environments) and provides incremental sales in SAP base user licenses (BULs). "Power users" who have more administrative and higher governance roles inside of customer organizations will likely still see the need to purchase full user licenses (FULs) however this is an incremental expense for some rather than a high expense for all.

 

Another key point is that SAP needs a defensive strategy as well for Microsoft, particularly as its flagship AX offerings start to move up-market and Business Suite - with clearly defined and easy to implement All-in-One (A1) solutions - move down-market and out to subsidiaries.  In a recent conversation with a Microsoft partner, it was clear that their business plan with Microsoft would run in conflict with the opportunities to build new solutions bridging the platforms via Duet Enterprise.  This is not surprising - while customers can "menu select" how best to deliver business processes to their various user groups, partners need to be more deliberate in their go to market solution strategies.  The SAP and Microsoft alliance can be problematic for some Microsoft partners who are well-established in the small to mid-size business (SMB) and lower end of the large enterprise customers space. 

 

This should not deter SAP customers from considering a leveraged hybrid environment with Microsoft using Duet Enterprise.  More pre-configured solutions are becoming available over time on the SAP marketplace to cut development cycles to implementation.  However, SAP customers should "pick their bets" carefully both for the specific business scenario they are considering for a hybrid solution, as well as the partner who may inadvertently bring any channel conflict into their implementation efforts.  Just like sound due diligence practices should be considered for any project effort, so too should careful planning be made when working in a joint Microsoft and SAP environment. This will help to ensure high expected benefits of reduced deployment cycle time and costs may be realized.

Hello fellow NW Gateway/Duet Enterprise enthusiasts ,

 

In my previous blog http://scn.sap.com/community/duet-enterprise/blog/2013/03/25/positioning-of-duet-enterprise-20-for-sap-sharepoint-integration, I tried to address a very common request about distinct positioning of Duet Enterprise 2.0 for those customers who already have or planning to have  NetWeaver Gateway in their SAP Landscapes.

 

In this blog, I would like to focus on another very common question/comment coming up these days, "Hey, this configuration is bit difficult!"

This comment, specifically, from technical community generally (May be arising from the sentiments of the customers who had not so pleasant experiences from Duet Enterprise 1.0/1.0 FP1 Configuration).

I admit Duet Enterprise 1.0 or Duet Enterprise 1.0 FP1 Configuration Guides/Wizards from SAP weren't so very perfect from the aspect of an SAP Administrator who is following them almost blindly. But again, why do so?


My first advice for you if you are planning to install and configure Duet Enterprise would be first to STOP and ask yourself some very basic questions:

 

For Example:

Do you know what features of Duet Enterprise you would classify as must have for your Project/POC? I mean do you really need all the features of Duet Enterprise in your landscape? (For Ex: Do you need Starter Services to be fully configured? Is there any way to check configuration quickly without enabling starter services?)

 

Do you know what components of gateway and Duet Enterprise you want to install, and where? Check your Netweaver version.

 

Have you gone through prerequisites/required notes available for the installation? And this sounds silly but do you really know if your SAP Landscape is ready for this installation?

 

Have you talked with your Network Teams, your SharePoint Administrators and agreed on which Ports would you like to use for HTTP/HTTPS communication with SharePoint Application? Are these ports opened on Firewall? (Is there is any!?)

 

If ports are opened have you checked the two way connectivity from browser inside SAP Server? From SM59? From browser inside SharePoint Server?

 

Do you have SLD for this configuration? Do you have ESR installation? (Applies to Duet Enterprise 1.0 FP1) Which ESR installation you would like to use? CE or PI? Have you thought about enabling HTTPS communication from your ESR system to your Gateway Server?

 

Is there any Load Balancer/Reverse Proxy such as Web-dispatcher in your landscape? If yes, have you configured it? How many dialogue instances are there?

 

So on and so forth… You got the point!

 

We have seen that a lot of problems arise because of lack of clarity (to people configuring Duet Enterprise) about such information and lack of co-ordination with SharePoint Administrators. If you think you don’t know this stuff, my second advice, think about a partner. There are companies in the Market who can assist very well!   

So the point is, let’s not blame SAP-Microsoft for something which was in some way supposed to be our homework

 

Moreover, if you see Duet Enterprise 2.0 Config Guide, its simple and clear! We @ Tieto ourselves offer now Duet Enterprise Configuration (Basis + Duet + SharePoint) in much lesser time! Kudos to Duet Enterprise Team for this guide + making simpler configuration with 2.0!

 

Lastly, my third advice for all Duet Enterprise SAP community, Keep your SAP Team close but keep your SharePoint Team closer

 

Above discussion now brings us to a new series of 2 blogs, where I will discuss how each and every call is processed in 3 System Architecture (SAP backend, Gateway, SharePoint) for all features of Duet Enterprise, with special focus on SAP Side of the story.

This series of Blogs could also be taken as a Pre-configuration Guide before you start

 

1. Duet Enterprise 1.0 Feature Pack 1 configuration

2. Duet Enterprise 2.0 Configuration

 

To be continued…

Hello Fellow Duet Enterprise Enthusiasts ,

 

Recently we came across a customer who asked us "Hey, I have SAP NetWeaver Gateway. I can build services with Gateway Service Builder and can consume those services via SharePoint BCS very nicely. so why should I use/invest in this one more product Duet Enterprise? I can develop many Interfaces with just Gateway and SharePoint BCS!"

 

I personally feel that this question might come up often in Duet Enterprise related discussions with Customers who do not know about this product deeply.

 

Below is a list with explanation as what exactly you will NOT get when you use only NetWeaver Gateway for SAP and SharePoint integration scenarios.

This might not be a comprehensive list and I might have missed something but lets just use the comments section below for more interesting discussions!

I will also not go into licensing part of Duet Enterprise here.

 

So here it goes:

 

1) Authentication (Duet Enterprise Add-ons for SSO): 

a) With SharePoint Duet Add-on we get an extension for BCS called Duet Enterprise Odata Extension Provider. This component takes SharePoint user’s identity, interacts with SharePoint Secure Store Service to extract the Duet Root Certificate. Then, this component creates X.500 user certificate (supported technology by SAP NetWeaver) and sends to BCS Runtime. BCS Runtime then embeds this certificate to the HTTP request header and sends to NetWeaver Gateway.


b) SAP NetWeaver Gateway Duet Enterprise Add-on (which creates a Consumer ID for SharePoint) then reads this user’s identity, extract the User Context by using mapping tables of gateway. Gateway, then, translates SharePoint User’s context to SAP User Context (All processing is done by a background user in gateway system).

Gateway mapping tables are populated with Duet Enterprise out-of-the-box User Mapping options (Transactions/IMGs which also include Mapping Options using direct AD Attribute for SAP User names, if maintained of course!)

 

2) Authorization (Duet Enterprise Add-ons for Authorization):

a) Duet Enterprise SharePoint Add-on provides:

    Out-of-the-box Web parts which Read SAP Roles

    Extension of people picker feature to provide options to give permissions for SharePoint sites/lists with these SAP Roles

    Extension of User Profile Store with field for SAP Roles

    Timer Job to Synchronize SAP Roles to SP user Profile Store

 

b) Duet Enterprise SAP Add-on provides:

    Already created SP consumer ID for Gateway

    Options to assign and synchronize roles to Consumer ID

 

3) Reporting Capability: SAP and SharePoint add-ons for Duet Enterprise, provide out-of-the-box reporting capabilities (Asynchronous). This means that SAP ERP and BW Reports could be exposed to SharePoint as the defined formats of your choice (such as excel and PDFs ) and could be seen as documents in SharePoint reporting site. 

These reports are response to an Asynchronous report request made from SharePoint. Report delivery could be configured in Gateway/Duet Enterprise Server (For Central Hub Deployment of Gateway). Currently, drill-down reports are not supported out-of-the-box (but, I assume it will come in near future).

 

4) Duet Enterprise Workflow Add-on: This is one of the most widely used features of Duet Enterprise. This add-on, again both on SAP and SharePoint, provides a mechanism on Gateway system (Central Hub) to configure workflow tasks to be sent to SharePoint and receive this contextual information of SAP workflow in the form of a SharePoint tasks. This is a deep form of people-process integration between SAP and SharePoint.

 

5) Tools support in SAP and SharePoint such as

     a) Tracking of every request/reports from SharePoint all the way to your Backend

     b) Duet Enterprise 2.0 Configuration Wizard (Available from Duet Enterprise 2.0 SP2 Onwards)

     c) DE Check Configuration Tool

     d) Mapping options between different workflow status in SAP and SP

     e) Reporting and Workflow Administration options

     f) Out-of-the-box support for SharePoint Online

6) Firm Road-Map and commitment from SAP and Microsoft for Feature Enhancements (for new features in Next Releases)

    (Note: Below list is the outcome of only my guess and should not be taken as any commitment from SAP and Microsoft)

     a) Deep Integration with MS Office Products

     b) Out-of-the-box support for SAP BO

     d) Enhanced Reporting and Workflow/Logging/Monitoring capabilities

     e) Advantage from Gateway Road-map

 

7) Out-of-the-box (but not enabled) OData Services for some scenarios (For Ex: Customer, Inquiry etc.)

 

 

To conclude this Blog, I would just say, its not mandatory to use Duet Enterprise and you can use gateway/bcs only for SAP-SharePoint Integration. BUT, if you have a good road-map for both SAP and SharePoint in your organization, it will certainly take a lot of investment/planning/maintenance for building such a foundation which has been built on enterprise wide best practices and has grown rapidly in terms of features in such a short span of time.   

For our German speaking audience we will have two discussion forums in April and beginning of May.

 

In these sessions we will show how you can get the best out of focusing on a dual vendor strategy with Microsoft and SAP. We will talk about how Duet Enterprise can help you integrate SAP data in SharePoint 2013, SharePoint Apps or Office 365.

We will also talk about Windows 8 and new features of SQL Server 2012.

 

Since this event will be in German here are all the relevant details (in German :-)). Feel free to register for the free event in Munich or Cologne.

 

 

Die Einführung des modernen Arbeitsplatzes ist geprägt von den Megatrends Mobility, Social Media, BI, Big Data und Cloud. Wie kann eine Dual-Vendor-Strategie auf der Basis von SAP- und Microsoft-Produkten helfen, effektive und effiziente Prozesse erfolgreich weiterzuentwickeln?

 

Erfahren Sie, wie Sie mit verschiedenen Formen der Human Collaboration einer größeren Anzahl Mitarbeitern den engeren Kontakt mit Kunden, Partnern und Lieferanten ermöglichen. Cloud-Lösungen wie Office 365 in Verbindung mit Duet Enterprise oder SharePoint-Apps erlauben den mobilen Mitarbeitern den Zugriff auf Daten und Dokumente von überall.

 

SQL Server mit den neuen BI-Funktionen sorgt sowohl für zusätzliche Auswertungsmöglichkeiten als auch für die schnelle Bereitstellung von SAP-Informationen. Mit SQL Server 2012 lassen sich sogar herkömmliche Verfahren und die modernen In-Memory-Techniken kombinieren.

 

Zu einem modernen Arbeitsplatz gehört auch ein modernes User Interface. Erfahren Sie, wie SAP und Microsoft zusammen die neuen Stärken von Windows 8 für ein produktiveres Arbeiten nutzen.

Sichern Sie sich am besten gleich die Teilnahme an unserem kostenfreien FORUM „Dual Vendor Strategy mit Microsoft und SAP“.

 

 

Termine
17. April 2013, München
8. Mai 2013, Köln

 

Wir bieten Ihnen einen Tag voller informativer Beiträge und interessanter Gespräche und freuen uns sehr darauf, Sie in Köln oder München zu begrüßen!

 

Agenda:


Thema

Empfang und Registrierung

Begrüßung, Partnerschaft SAP und Microsoft

Moderner Arbeitsplatz

Duet Enterprise

Pause

Partnerlösugen mit Duet Enterprise

Microsoft BI & Big Data für SAP

Mittagessen

Private Cloud für SAP

Kundenreferenz

Moderne und Mobile User Interfaces - Windows 8 (Apps)

Zusammenfassung

Networking Event

 

Looking forward to meeting you there!

 


SharePoint Online

Most significant in SharePoint 2013 is that it is ‘built for the cloud [1] [2]’. The motiviation for Microsoft to focus on cloud-enablement is market-demand: a considerable subset of its SharePoint customer-base struggles with hosting and operating SharePoint themselves on premise. And because of this struggle, a lot of SharePoint-using organizations are reluctant to upgrade their SharePoint deployment. Via the Cloud / on demand offering, Microsoft aims to reach 2 goals: relieve organizations from the burden of SharePoint operations, and enable those same organizations to stay on par with the feature progress in the SharePoint and Office platform. Microsoft plans an upgrade release cycle of every 90 days for SharePoint 2013 Online.

 

Duet Enterprise 2.0 Online

The SharePoint 2013 cloud offering also has positive implication for Duet Enterprise deployment options. In addition to the existing on premise installation option, Duet Enterprise 2.0 offers a cloud / on demand alternative. Extend the reach of your SAP data into the Microsoft cloud. In such infra architecture, the SAP landscape is on premise, but Microsoft SharePoint 2013 is serviced in the cloud.

 

The Duet Enterprise hybrid infrastructure setup imposes following requirements on the local and remote + shared environments:

  • Each customer organization must [still] deploy the Duet Enterprise 2.0 SAP Add-On in own on premise SAP landscape; installed on the SAP NetWeaver Gateway 2.0 system
  • SharePoint 2013 Online must include the Duet Enterprise 2.0 SharePoint Add-On
  • The connectivity between on premise SAP Add-On and cloud hosted SharePoint Add-On requires a ‘light’ local SharePoint 2013 node. This node functions as intermediate layer ('broker') from internal SAP Gateway to SharePoint online and vice versa.
  • Mutual trust-relationship between the on premise SAP Add-On and the on premise or cloud hosted SharePoint Add-On is based on X.509 certificates; no longer on SAML. The X.509 certificates are provisioned by the Duet Enterprise SSO Generator on the ('light') SharePoint 2013 node on premise.

Duet Enterprise 2.0 Hybrid Architecture.png

 

Availability

Duet Enterprise 2.0 is already General Available for on premise deployments, but not yet for the cloud. It necessary follows upon the public availability of SharePoint 2013 Online, with the inclusion of Duet Enterprise 2.0 SharePoint Add-On. Microsoft has not yet announced the release date, but realistic expectation is ‘somewhere’ Q1/Q2 2013. Then also more details will be communicated on how to configure and operate Duet Enterprise 2.0 in a potential multi-tenancy SharePoint Online context.

Recognizing Excellence by for Our Joint Partners


The SAP-MICROSOFT Unite Partner Connection program is built on the three-way collaboration of SAP, Microsoft and our joint service partners. With the dedicated resources, creativity and development of innovative solutions by our partners, the technologies of Microsoft and SAP reach their optimal potential for improving efficiencies, increasing ROI on technology investments and enhancing customers’ technical capabilities to enable them to meet the challenges of the ever-changing business climate.

 

NEW for 2013 – TWO Awards!

Amazing solutions have been developed to answer our customers’ toughest challenges and demands and we want to recognize the best solutions that have been built on Microsoft and SAP technologies over the past year. The top three finalists for each award will be highlighted by Microsoft and SAP at SAPPHIRE NOW in Orlando in May 2013!


SAP-MICROSOFT Unite Partner Connection Innovation Award - One solution will be awarded for showing the greatest level of innovation and imagination to answer a customer’s challenge.


SAP-MICROSOFT Unite Partner Connection Customer Impact and Value Award - One solution will be awarded the for a solution that not only significantly improved a customer’s business process(es) but also provided greater ROI on their Microsoft and SAP investments by implementing the solution.


Attached you will find the complete list of requirements and the criteria by which all solutions will be judged.

 

Partners are encouraged to submit multiple solutions for consideration. The same solution cannot win both awards.

 

Award Recognitions

 

As part of the award recognition, the winning partners will:

  • Present the solution to the attendees during an award ceremony at the SAP-MICROSOFT Unite Partner Connection Executive Breakfast in Orlando on May 15th
  • See their solution featured by Microsoft at SAPPHIRE NOW Orlando, including having a company representative highlighting their latest innovations at a dedicated station in the booth
  • Receive SAP certification of their solution
  • Receive invitations to participate in regional and online activities with Microsoft and SAP field teams
  • …and much more!

 

Submission deadline

 

Deadline to submit solutions is 12:00 pm PST, April 3, 2013

 

To Submit a Solution for Consideration

  1. Complete the attached solution brief
  2. Complete the attached solution template
  3. Strongly Recommended – provide video link or file showcasing your solution. Finalists will be required to submit a video file.
  4. Strongly Recommended – secure customer reference for the submitted solution


Winner Notification

 

The winner of the SAP-MICROSOFT Unite Partner Connection Innovation Award will be announced via email to all partners who submitted solutions for consideration and publicly announced. The decision of the judges is final.

 

Additional Information

Please see the attached documents for full details and information about the SAPPHIRE NOW Madrid Partner Innovation Award.

If you have additional questions, email the Unite Program Office.

No extensions to the deadline will be offered and solutions submitted after the deadline will not be considered for the award

 

For More Information, download the attachments here :

http://sdrv.ms/RMKAHx

 

- Author: Peter Ng


On February 5th, 2013, a very interesting customer facing event took place at the Executive Briefing Center in Palo Alto. This event, SAP NetWeaver User Interaction Customer Summit: 'Intuitive User Experience MadeReal', was well attended by SAP customers and partners.  Here is a link to the FB page with some of the post-event networking reception pictures.

    

One of the challenges that SAP is facing is that the power of SAP applications means the complex functionality which gets in a way of wide adoption throughout the enterprise.  The complexity is a challenge especially for so called occasional or infrequent users of SAP systems. The summit focused on solutions that address this problem, and by presenting them side-by-side did a great job of co-positioning them to eliminate confusion and help customers navigate a great variety of offerings. 

   

 

Together with customers we enjoyed presentations on HTML 5, SAP NetWeaver cloud portal and consumption of portal on mobile devices, partner solutions around Adobe Forms and Open Text Integration with Portal, listened to a few customer success stories, learned about security offerings.  And we had a great opportunity to share our stories - how Duet Enterprise and Gateway help customers and partners build solutions that make casual users' experience with SAP so transparent, that they often do not realize that they are indeed interacting with SAP!   Examples of web and mobile applications providing real-time interactive access to the SAP data presented in the most creative and modern looking user interface, caused lots of interest for SAP NetWeaver Gateway in the audience.  I covered the Gateway story while Agnes Dimayuga presented the story of Duet Enterprise where  workflow approvals,  team collaboration in SAP workspace, creating activities and logging hours in SAP backend systems, all done directly from Microsoft Outlook or SharePoint, highlighted the capabilities of Duet Enterprise to enable intuitive end user solutions.  On the picture below you see Agnes presenting at the summit.  Agnes.jpg

    

Existing solutions cover a number of scenarios.  For example, just published article at SAP SCN http://scn.sap.com/community/duet-enterprise/blog/2013/02/11/create-a-simplified-user-experience-for-purchasing-using-duet-enterprise
showcases Duet Enterprise based SRM integration and we will continue talking about the most popular scenarios around solutions focused on other lines of
business.   

 

We are looking forward to more opportunities to share our stories and help new customers expand the power of SAP to their entire employee base!

Abstract: Duet Enterprise provides a rich, easy-to-use environment which extends SAP core capabilities to customer groups via the Netweaver Gateway directly to Microsoft Outlook and SharePoint. Learn how purchasing groups can take advantage of Duet Enterprise capabilities, including partner developed solutions certified by SAP.

 

Duet Enterprise is a jointly developed SAP and Microsoft interoperability platform layer between SAP and Microsoft applications to make it faster and easier to give SharePoint and Office users transparent access to SAP data and processes. Customers can leverage the underlying capabilities of Duet Enterprise and SAP NetWeaver Gateway to extend interoperability to Microsoft Office and other new Microsoft solutions as well as leverage an ecosystem of partners offering Duet Enterprise accelerators for different business scenarios, including enterprise purchasing.

 

Create a Simplified User Experience for Purchasing using Duet Enterprise

 

Effects of the Great Recession have left many company departments facing “do more with less” situations.  Support areas of the enterprise, including such functions as human resources, marketing and purchasing have been hardest hit.  The State of New Mexico recently announced a 14% staff reduction for 2013, while DuPont has announced a 2% staff reduction over the next two years.[1]


The impacts of reduction in workforce are twofold when it comes to enterprise support functions.  First, workers near retirement age – typically Baby Boomers who have made climbing the corporate ladder their life focus – leave and are replaced by younger, less experienced, and less expensive staff.  Second these new workers learn and work in much different ways than their older colleagues.  This creates a need to make the workplace more engaging, and technology can be a constructive answer to reduce complexity and increase worker productivity.


Today's labor force is different. If supervisors don’t take responsibility for their own employee retention, they could be left without enough good employees to replace workers leaving organizations.  Millennial workers (born 1979 through 1999) grew up learning how to play, and fun was part of their learning pedagogy in their educational upbringing and remains so today. So you need to make work fun and easy, and gamification is a big part of this.  Older Baby Boomer workers may dismiss this as wasting time, but that’s how millennial workers “get things done.”


A 2011 white paper by Enterprise Strategy Group[2] found that nearly two in three (64%) North American and Western European organizations are currently using Microsoft SharePoint, while an additional 12% plan to do so in the near future (Figure 1).  As a common platform, Microsoft SharePoint can allow access to complex, business critical information through a user interface that most organizations already own.

 

DE Figure 1.png

Figure 1 User adoption rates of Microsoft SharePoint (survey of over 3,000 sampled businesses IT users conducted by Enterprise Strategy Group, 2009-2011).

 

Content being directed at a common, easy to use platform is on the rise.  While most Microsoft SharePoint sites manage content in the 100s of Gigabytes, the same 2011 study found that content level will grow to 10s or 100s of Terabytes by 2015. With increased capabilities of SharePoint content management and data handling, the ability to scale SharePoint as a common platform in the advent of global, big data enterprises becomes real.

 

Engaging the Purchasing Community

 

The purchasing community can serve the organization as a perfect opportunity for bringing collaboration, information sharing, gamification and even fun to the workplace.  Why is this?  So many new requirements – Dodd Frank and conflict mineral compliance – and continuing requirements – such as quality management and cost-reduction goals – have placed purchasing in the center of enterprise risk management and profitability initiatives.  A consequence of this shift requires purchasing professionals to perform numerous and broad ad hoc inquiries as well as scheduled reporting, demanding access to broad enterprise and supplier information.  This is a heady responsibility for the purchasing organization.  Without a dramatic change in work and attitude at work, traditional actions of the purchasing group will not meet management expectations given these new and demanding requirements.  Flexibility and a sense of humor are required, and this is where an engaging, fun and “gamified” work environment can create productivity and accuracy gains in the organization, reducing risk and increasing profit.

 

Note

For more information on the impact of the Dodd-Frank Act on conflict minerals in the supply chain, read the recent Ethisphere magazine article,Addressing New Conflict Minerals Requirements: Keys Success Factors for Processes and Reporting.”

Through a joint partnership with Microsoft, SAP introduced Duet Enterprise several years ago to leverage Microsoft Office and Microsoft SharePoint as common, “friendly” and easy-to-use collaboration platforms that could access complex SAP enterprise data across the organization without the need to train SAP business users on how to use the SAP GUI or browser-based versions.  Companies taking advantage of Microsoft tools for team and functional collaboration can leverage what they presently own while enjoying the benefits of a unique system of record provided by SAP.  SAP has recently recognized purchasing solutions which have been developed using Duet Enterprise 2.0 which can address the opportunity for greater productivity in the workplace using Microsoft SharePoint as a common business platform in on-premises, cloud computing, or hybrid environments.

 

Note

Duet Enterprise is general available (GA) software, and requires SAP NetWeaver Gateway server license as well as Microsoft SharePoint 2013 Enterprise licenses.  This will be explained in more detail in the next section.

 

In the next section I show how to create the appropriate Duet Enterprise environment and what components of SAP Supplier Relationship Management (SAP SRM) can be used to create a common and effective purchasing environment.

 

Establish the Purchasing Environment across SAP SRM, Microsoft SharePoint

 

In order to create a cohesive purchasing environment leveraging the capabilities of Duet Enterprise, several architectural and human resource components are required. On the people side of the equation, purchasing should be very familiar with Microsoft SharePoint and its configuration for collaboration and project teams.  Since SharePoint is a highly intuitive and easy to learn environment this is often more of a benefit versus a requirement.  The purchasing department needs to be of a qualified size as well since presently Duet Enterprise licenses are sold in bundles of 100 to match-off to SharePoint users defined in the system.  On the IT side the team must be familiar with the business processes of the purchasing department, including requisitions, cataloguing, spend analysis, and vendor selection.  This helps the mapping of transaction requests inside Duet Enterprise to the core SAP vendor master and SAP SRM functions.

 

Note

The Duet Enterprise 2.0 SharePoint Add-on is installed on servers that run SharePoint Server 2013 Enterprise Edition. The Duet Enterprise 2.0 SAP Add-on runs on top of SAP NetWeaver ABAP 7.02 SP08 running the SAP NetWeaver Gateway 2.0 SP4 component. For more information about the SAP environment, see the SAP Master Guide on SAP Service Marketplace.

 

Figure 2 provides the overall topology of the Duet Enterprise environment.  Essentially the department leverages its Microsoft SharePoint environment as the user experience and interface.  Duet Enterprise is loaded as part of the SharePoint environment and brokers the communication to SAP NetWeaver Gateway via HTML mapping.  Once a transaction request is received by SAP NetWeaver, the request is distributed natively to the proper location and master data required (for example, vendor inquiry to the vendor master record or part availability to the part master record).  Once the information is received by SAP the result is transmitted via the topology back to the SharePoint user.

 

DE Figure 2.png

Figure 2 An example topology for Duet Enterprise supporting Purchasing function (figure SAP America as modified by Newport Consulting Group).


 

Why consider a Duet Enterprise based solution? I am fond of saying that inside the SAP ecosystem there is often “more than one way to skin a cat.” So deployment teams have options.  If your organization is already heavily invested in the Microsoft Office platform for other desktop functions, you can utilize an interface they already know and already own.  SAP web-based GUI applications, particularly the financial applications in the BusinessObjects stack, are highly intuitive as well and some applications such as Spend Performance Management go deep into SAP SRM to extract and manipulate large data relationships (essentially a “mini BI cube” comes with the application or you can use a full BI approach to analysis).  Where such detailed analysis is not necessary – for the average user for example – using a Duet Enterprise solution can reduce license costs while still creating a solid transaction environment for broad department and large company use.

 

Note

For more on SAP BusinessObjects Spend Performance Management, see my Toolbox article and summary on the SAP Experts site.

 

There are obviously some challenges as well when creating a multi-application environment.  First, historically SAP NetWeaver Gateway has had capacity issues for large numbers of complex transactions executed simultaneously. While NetWeaver Gatway has benefited from many enhancements designed to improve performance, your best optimizing the transaction rate at 100s of transactions versus 1000s based on my discussions and experiences with customers.  These rates are quite optimal for using NetWeaver Gateway and its OpenData (Odata) protocols to extract information from back office core SAP systems (ERP, SRM, SCM, etc.)

 

SAP customers have a number of options to create their own solutions or to leverage pre-configured solutions developed by other companies available on the SAP Marketplace.  In the next section I will show you two different examples of the Duet Enterprise and the purchasing solutions available via the SAP Certified Partner program.


 

Examples of Purchasing Solutions using Duet Enterprise

 

There are a number of purchasing solutions available from the SAP Marketplace and broad ecosystem which leverage the Duet Enterprise platform. Recently SAP and Microsoft jointly awarded Cordis Solutions its 2012 UNITE Award for Partner Innovation for its work to develop the Harmony platform of applications.  As you can see in Figure 3, the Cordis Harmony set includes a number of Human Resource, Purchasing and Finance applications available from the Harmony jump page.  The jump page takes advantage of the Windows 8 tile format for either on-premises or tablet use of the application.

DE Figure 3.png

Figure 3 Jump page for the Cordis Harmony application set including myPurchase.


Once the user selects the myPurchase application, the user is brought to a workspace shown in Figure 4.  From here the purchasing agent or employee can requisition materials available in a catalogue, all of which is summarized from SAP back-end systems.  In this case the employee would like to request a pen, which is placed in a shopping cart very similar in use to many online retail stores. 

 

Users accustomed to gamified environments will appreciate the simplicity of the application.  You can manipulate your shopping cart at will and determine how to best allocate your budget. The easy user interface almost believes you are shopping on-line and not just at the company store.

 

Once the request is completed, the user can review its cart (Figure 5).  In this example, items less than £100 are automatically approved.  However the new desk has a higher limit so the user must wait for management approval before the item is purchased.  The Cordis information uses myGuidedBuy to house available items in its company catalogue.  As such, this framework can be extended to capital expenses (CAPEX), lease requests, or any other transaction supported by the back-end SAP system.

 

 

DE Figure 4.png

Figure 4 Requisitions using a simple shopping cart approach in myPurchase.

 

The CS Procurement Portal developed by SAP Certified partner Campana-Schott, allows for deep visibility into trends and purchasing requests based on information contained in SAP back-end systems.  The availability of rendered visualizations of purchasing spend history by category can be extremely helpful in managing spend across the organization (Figure 6).


 

DE Figure 5.png

Figure 5 Items pre-approved are ordered, items above a threshold are sent to management for approval.

 

Summary

 

With workplace demographic trends requiring more and more solutions that are easy to use and require low capital investment particularly in support functions such as purchasing, Duet Enterprise offers a number of unique approaches to leverage information systems assets which the company may already own. Given that the most expensive component of any business is its people, leveraging the Microsoft environment to provide a pleasant and familiar work experience in the purchasing and other support functions of the organization can offer a high-value, competitive advantage while increasing workplace retention and productivity.



 

 

DE Figure 6.png

Figure 6 The CS Procurement Portal provides rendered visualizations of purchasing and spend history using Microsoft SharePoint and Duet Enterprise.

 

 


[1] “DuPont Announces 2% Staff Reduction as Global Sales Decline,” International Business Times, October 23, 2012. “Office Space Expands while Workforce Declines,” Santa Fe New Mexican, September 26, 2012.

[2]Babineau, Brian and Lundell, Bill. “Managing SharePoint as a Business-critical Application,” Enterprise Strategies Group, August 2011. http://www.microsoft.com/en-us/download/details.aspx?id=28133



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.

In case you missed our blogs from 2012 events, here is a list of links to our previous postings on other SCN pages.  We had an extensive coverage of events such as Americas, EMEA and APJ SAPPHIRE, TechEd and Microsoft SharePoint conference.  Hope you find these helpful:

 

Duet Enterprise sessions at TechEd in Las Vegas!

 

Duet Enterprise at SharePoint Conference November 12-15

 

Duet Enterprise at SAPPHIRE and TechEd Madrid:

When you create in transaction Duet Enterprise Business Data Connectivity Publisher a BDC Model from GSDO Type, behind the scenes multiple entities are created in the SAP landscape. Visible for Duet Enterprise developers are the service interface in SPRoxy; but also webservice, message types, and data types are created. Important to be aware is that the items visible in SProxy are only proxy objects; the webservice itself plus messages types are created within the ESR.

 

Upon need to regenerate a Duet Enterprise BDC Model, it appears as if the BDC Browser does not directly support this designtime action. The menu does not display an option to regenerate from GSDO type.

Screen Shot 2013-01-19 at 10.40.45 PM.png

A pragmatic action is then to delete the created BDC model itself; however also for that the menu action is missing. Only possible action in BDC Browser appears to delete the Business Scenario in its entirity, so that you can next recreate it from scratch including the service generation. But remember that the initial generation created a service proxy, so this too should be deleted. And to be complete, also delete all used objects:

Screen Shot 2013-01-19 at 10.41.43 PM.png

We applied with success multiple times the above approach when needed to regenerate the Duet Enterprise service (Gateway Generic Channel). However, it left us with a dissatisfied feeling as the approach is cumbersome and requires multiple and different steps.

Another issue is when the business scenario contains multiple BDC Model generations; these would then all be deleted and required to generate again. This while you are only editing a single GSDO Type, and thus would only regenerate the BDC Model for that type.

Screen Shot 2013-01-19 at 10.42.41 PM.png

I confronted Alexander Puettner with this dissatisfying Duet Enterprise development experience, and asked whether it can be done in simpler approach. Luckily there is. Upon the need to regenerate a BDC Model, do not delete the business scenario. Right-click on it, select again the option to ‘Create BDC Model’, and enter exact the same input as in the previous generation. In most cases, this will regenerate everything.

Screen Shot 2013-01-19 at 10.44.50 PM.png

I have now applied this simpler approach multiple times, each time successfully. Alex however warned that occassionally the approach could fail. A reason can be that another developer generated the BDC Model plus service artifacts before, and now has locks on the previous generated entities that prevent you to overwrite them. If this occurs, release those locks and/or the transport requests. Another issue may be that intermediate entities (the webservice, messages, datatypes) are locked in changelist on ESR system; under user account associated with SAP_PROXY_ESR RFC connection. And for some reason, it fails to overwrite; despite the same RFC user account. To resolve this situation, log on to the ESR, and release the ESR changelist entries. And then retry.

A third issue can be that the service endpoint is not recreated. This is a known bug. Most times it is resolved when retry to regenerate BDC Model. If that still doesn’t recreate the endpoint, then open SOAMANAGER, look up the Business Scenario, delete it and recreate. The administration in Duet Enterprise BDC Browser can be maintained; regenerate will reestablish the service definition plus endpoint in SOAMANAGER. Note that in case the Business Scenario contained more service definitions, you have to regenerate for each of them within Duet Enterprise BDC Browser.

Screen Shot 2013-01-19 at 10.45.42 PM.png

 

Summarized, best practices:

  1. In most case it is sufficient to regenerate in BDC Browser; and simple ‘ignore’ that the BDC Model is already present from previous creation.
  2. If possible, stay away from explicitly doing something in ESR. Normally, the Duet Enterprise design tools handle this transparently. But as soon as you interfere, things can get ugly and mess up your Duet Enterprise design time landscape.
  3. If messed up in ESR, don’t be afraid to cleanup the changelist in ESR
As of Duet Enterprise FP1 SP3, the Duet Enterprise product team now clearly positions OData Channel as the recommended approach for new developments of custom Duet Enterprise scenarios:
Feature Pack 1 for Duet Enterprise 1.0 Development Introduction
Generic Channel remains supported, also within Duet Enterprise 2.0; but will not be enhanced with new features and capabilities. Message: OData is the way to go. Main reason is that OData has much more potential for consumption outside the SAP Business Suite boundaries, and therefore the Duet Enterprise team is focusing its resources on supporting that more prospective channel.

Consequence for Duet Enterprise custom development: learn new approach + tools

Although one thus still has the option to utilize the Generic Channel development approach, the signal send by Duet Enterprise team is clear. OData development has the momentum and the future. Consequence for custom Duet Enterprise development is that on SAP side the programmer must transition to develop Gateway OData Services instead of GSDO types. The concepts and steps of the 2 are somewhat comparable, but the tools and execution + coding are different. For GSDO the ABAP programmer uses SE80 and /IWFND/GWO_GEN; OData development is performed mainly within the new Service Builder (SEGW). Within both approaches you have the options to generate the data provider class through mapping to RFC and BOR, or to manual handcraft it. Once the data provider class is ready (OData DPC or Generic Channel GSDO), you expose it as SharePoint 2010 callable entity. For OData DPC, the BDC Browser tool is extended with the capability to convert OData Services into Gateway SOAP web service. At runtime, Gateway applies for this the Duet Enterprise FP1 SP3 OData-SOAP Bridge. The existence of the OData-SOAP Bridge is transparent for the SAP Duet Enterprise developer. One simple utilizes the BDC Browser as before for GSDO type, to now expose the OData Service for consumption within SharePoint 2010.
Noticeable is that for SharePoint 2010 development side, nothing changes. You still import the BDC model generated via BDC Browser containing one or more External Content Types that refer to Gateway SOAP webservice(s). And next utilize the out-of-the-box Business Data UI-controls, and/or the BCS API to develop a custom UI.
See also:
Duet Enterprise FP1 Developer Guide - OData Channel.jpg

Filter Blog

By author: By date:
By tag: