The Infosys global supply chain management blog enables leaner supply chains through process and IT related interventions. Discuss the latest trends and solutions across the supply chain management landscape.

« Supply Chain - A strategic lever in a weak economy | Main | Is there confusion with SAP SRM suite positioning after acquisition of Frictionless commerce (now rebranded SAP E-Sourcing)? – Part 2 »

Is there confusion with SAP SRM suite positioning after acquisition of Frictionless commerce (now rebranded SAP E-Sourcing)? – Part 1

The last 7-8 months have been the most demanding phase for SAP to position the SAP SRM suite offering.
As a consultant, I am still trying to understand why this acquisition? Am trying to logically place these questions to arrive at an answer
Whats the confusion?
SAP SRM (version 5.0 and lower) was always ranked low in comparison to what “best of breed” offers for Sourcing and Contract management functionalities.
However, to overcome this, they acquired Frictionless commerce (now rebranded SAP E-Sourcing) to bridge this gap. They had a strategy to sell it as an On-demand solution only they have been successful in selling the on-demand solution. But they realized the need to make the on-premise solution available for customers who where skeptical in parting with data, but however the On-premise solution brought with it major confusion, leaving the suite offering with heavy questions, reasons stated below.
SAP has also provided integration with SAP ERP for customers who already have an SAP ERP shop and are looking forward for a sourcing application to sit on top of the ERP application. The definition of such customers would be those who haven’t yet implemented SAP SRM or some one who might have opted to use Best of Breed to do the sourcing bit and flush results back into the ERP to feed operational procurement instead of investing in SAP SRM licenses.
With the release of SAP SRM 7.0, SAP had announced that the gap has been bridged, however, not all the extended functionalities that came as a part of Frictionless acquisition have been made available, reasons could be many.
Some known gaps with SAP SRM, version 5.0 (limited to Strategic sourcing process only)
-          Contracts in SAP SRM are limited to Operational contracts; Contract Authoring process is a limitation, limited collaboration features b/w Buy-Sell side.
-          Complex Sourcing processes for RFx and Auctions cannot be handled via SAP SRM in comparison to what the “best of breed” offer.
-          Category Management with SAP SRM can be addressed with implementing cProjects and is not functionality with in the tool.
-          Forward / Dutch Auctions capability isn’t available.
In my next blog, I will talk about “why is it difficult to convince customers to have both these applications operational in the same landscape?”
…also what is xCLM and the confusion that came with it and the benefits it pumped in.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles

Infosys on Twitter