what are the adv and disadv of using SRM as an addon?

[Former Member]

Hi Friends

what are the adv and disadv of using SRM as an addon

Regards

Simha

[Former Member]

Hello Simha,

the One Client scenario (or call it 1C) is interessting if you do not plan to make use of all SRM scenarios and you have only 1 ERP system. Than you can save the hardware costs, install the Addon to your existing ERP system. If you would like to use Service Procurement with Service hierarchies, Central Contract Management and/or Sourcing you have to use SRM as standalone system, as these sceanrios are not support with 1C. Self-Service Procurement, SUS and Service Procurement - External Staffing is supported with one Client.

best regards

Markus

[Former Member]

thanks koushik

[Former Member]

Hi Simha,

Here are my view points on SRM and ECC one client deployment: The decison to have one client for SRM and ECC is more driven by the business model of the client and functionalities one need out of SRM .Following points needs to considered before deployment:

1) ERP and SRM as an add-on does not support any multiple-backend functions or hub deployment for procurement.

2) Upgrade or migration from SRM system to ERP with SRM as add-on is not supported

3) Strategic sourcing scenarios in SRM are not used by clients with such deployments

4) Although SRM is running on the same client as ECC the purchasing organization have to be maintained in both MM and SRM system

5) From HR Orgstructure stand point there is no additional benifit in same client deployment as compared to seperate deployment

6) From Security stand point its better to have a seperate client for SRM-vendor registration as this functionality is exposed to outside world and internet.

7) Master Data Synchronization is a positive point which is only available within the SRM Add-on deployment with ECC

😎 For SRM and ECC (seperate) master data management remains asynchronous and unidirectional

Thanks,