Updated SAP Sourcing / CLM Release 10 EOM and Release 11 Roadmap Plan!
SAP Sourcing / CLM product management is pleased to announce that the plan and contents of Release 11 have been recently updated. SAP Sourcing / CLM Release 11.0 will now include support for the SAP HANA database as well as support for S/4 HANA integration.
HANA Support
- Enables complete replacement of the Sourcing / CLM database
- Enables lower Total Cost of Ownership (TCO) by eliminating Oracle or DB2
S/4 HANA Integration
- Enables Sourcing / CLM integration to the “next generation” of SAP ERP and SRM
With the addition of these 2 key, customer driven, enhancements to the Release 11 plan, we have extended our estimated GA date by 6 months. We are now targeting to enter the release 11.0 ramp-up phase by mid 2017. This means our estimated GA date is now in the 4th quarter of 2017. While the release delay is regrettable, we feel the addition of these 2 enhancements is worth the wait.
In line with this new plan we have also extended our End-Of-Maintenance support for release 10.0 to 12/31/2019 (previously 12/31/2018). We hope this extension will encourage any customers still on Release 7.x or Release 9.x to upgrade to 10.x, as well as allow those customers already on Release 10 enough time to upgrade to Release 11 when it becomes available. As a reminder Release 7 EOM date is 12/31/2017 and Release 9 EOM date is 12/31/2016.
Please forward any questions to Ed or myself.
Regards,
SAP Sourcing / CLM Product Management
Anne McClelland anne.mcclelland@sap.com
Ed Dunne ed.dunne@sap.com
Hi Anne,
It is good news to hear SAP Sourcing roadmap to be on HANA and integrated with S/4HANA in release 11.0 in 2017. We are looking forward to it.
Guoyu
I only need one word to describe this: EXCITING 🙂 !!
Can i know whether CLM will have OData services enabled in the upcoming release apart from RestFul service?
Also in the roadmap a fiori app is being discussed for approval workflow. Is that standard app is based on Odata service integration or Restful service?.
We have to leverage our existing Fiori Frontend server in conjunction with multiple backends( one is CLM)
Regards
Phani Poorna
Hi Phani,
Support for OData is in the SAP Sourcing/CLM product backlog but has not yet been targeted for a specific release.
The Fiori mobile approval application coming shortly in SAP Sourcing/CLM Release 11.0 uses SAP Gateway to provide OData web services to Fiori by calling SAP Sourcing/CLM RESTful web services from SAP Gateway.
Other customers have also used this SAP Gateway - Sourcing/CLM RESTful web services technique to provide OData web services.
Regards,
Ed
Ok Thank you for the Info. I have a couple of quick queries.
As of now we are able to run custom fiori application for CLM from a Fiori Frontend Server(AS ABAP) using OData. gateway is hosted in that.
Thanks in advance!
Regards
Phani Poorna
Hi Phani,
Re: 1: SAP Gateway cannot be installed on the CLM Netweaver AS JAVA server. It is installed on a NW ABAP server.
Re: 2: The Sourcing/CLM 11.0 new Fiori mobile components will be hosted on the Fiori server as a "My Inbox" Add On.
Regards,
Ed
Superb. Great update
As of now "My Inbox" standard fiori application is available to support workflows of a specific backend and we are using that..
1) Are you integrating the same app with CLM backend also? By providing us to do some confugurations with a new delivery of my inbox app?
2) Or delivering a new app specifically for CLM with new component.
3) How to leverage new functionality of clm if it is delivered with existing "MyInbox" app.
4) Also extensibility is key for any standard app. If it is delivered with existing app, can we have all the possibilities to extend(extension points) like a same fiori app specifically for clm.
Currently we are using My Inbox for backend(AS ABAP) workflows.
Regards
Phani Poorna
Hi Phani,
We are integrating the existing MyInbox ABAP app with CLM workflow approval information so that viewing CLM workflow approval requests and executing CLM work item approvals can be performed from the existing MyInbox app. There will be extensibility capabilities provided by the CLM scripting and query framework. I'm not aware of any limitations to Fiori extensibility that will occur when the CLM MyInbox intrgration is implemented.
Regards,
Ed
Hi Ed,
Thank you for much awaited review on the clm standard fiori app architecture. Now we can take better decision to wait or to go for custom implementation.
-->Seems like this will be tricky and somewhat clumsy in terms of business roles on the front end with myinbox design. As the design itself is to integrate with existing inbox app,@frontend CLM business users will not have their own standard business and catalog role. Instead it can be acheived by lot of launchpad designing and customization of standard app to work with own custom roles(that is not suggested way as well).
--> Also even if we go with the existing delivered frontend roles and all, it seems to be difficult to extend the front end specifically for CLM functionality (as frontend is not specific for clm but many backends).This can also be acheived with lot of customization but not a suggestable way to do. I was in a expectation that CLM will also have fiori apps like SRM standard apps(track shoping cart,appove purchase order etc) with their own delivered standard business role, business catalog and group with a new component all together.
--> Also if a customer has already implemented myinbox for abap workflows and also extended it already by now, then this design seems to be tricky to go.
--> As per that latest version, myinbox can be implemented on fiori cloud using Hana cloud platform(HCP).Does clm also support the same in future?
This is my analysis on this design Ed. Can you tell us the advantages from all ways(including processwise) on why should we integrate clm for My inbox app.Also kindly tell on why should we go for inbox standard app but not custom app interms of all perspectives.
Anyway it was a very nice update.
Regards
Phani Poorna
Hi Phani,
CLM integration to HCP is in our product backlog but it has not been targeted for a specific release yet.
The main requirement that will be met with the CLM integration to Fiori is to provide a mobile Workflow Approval capability.
I'm not a Fiori architect or developer - and so much depends on your specific requirements - that I can't really comment on any tradeoffs between using the standard CLM MyInbox functionality vs. doing something custom.
Regards,
Ed
Hi Ed,
Thank you for the update and it will definitely help us. Regarding Approval capability we achieved it by using the additional methods exposed by CLM Workflow API in 10 Release.
Regards
Phani Poorna
Hi ,
I need a suggestion regarding version upgrade, we are currently using CLM 9.0 version sp24 pack , but whether moving to version 10 .0 or 11.0 ? which one is better and what could be the major differences that impact if we opt any one either 10.0 or 11.0, could you please suggest on this.
Thanks & Regards,
Gopal.
Hello Gopal
Can you contact me via email and I can send you more detailed information on the contents of release 10 and release 11.
As far as the timing of your upgrade and how it aligns with Release 11 you will have to decide if you can wait for release 11 which is tentatively expected to be GA before the end of the year. Our early adopter customers are working on their upgrade now.
Regards, Anne
SAP Sourcing / CLM Product Management.
anne.mcclelland@sap.com
Hi Anne,
Can we install SAP Netweaver and SAP Sourcing together in SAP HANA Database for CLM 11.0
As of now for CLM 10.0 required two seperated Database for AP Netweaver and SAP Sourcing.
Could you please confirm this query.
Regards,
Sridhar Namani
Hello Sridhar
We tested HANA database deployment scenarios in 11.0 where the 2 databases were in separate servers. We are still in the process of working through the scenario where a single HANA database is shared between Netweaver and Sourcing/CLM. We are not ready yet to make a recommendation regarding using a shared HANA database.
If you have follow-up questions it might be best to contact me directly: anne.mcclelland@sap.com
I hope this helps.
Regards,
Anne McClelland – Product Management
Hello Anne,
I read that EOM date for SAP Sourcing CLM 10 is 31/12/2019. Is this date still valid?
Also, could you provide the EOM date for CLM 11, and the roadap plan for CLM 12?
Thank you!
Michel Laberge