on 04-04-2008 6:46 AM
SRM Gurus,
We are in the verge of installing SAP SRM system. Our main focus will be on :
1. SSP
2. Contract Management
3. Catalog Management
Please clarify what are the pros and cons of using SRM as ADD-on or SRM as seperate instrance.
If we can use contract management with SRM addon as a leading contract system without creating them in ECC6.0
Kaushik
The SRM AddOn is targeting on customers that are aiming on a simple procurement scenario, do not yet use mySAP SRM, are using only one Backend (ECC) system and aim to install SRM with a low TCO.
The following scenarios are released within the SRM AddOn:
Service Procurement (local deployment)
Self-Service Procurement (classic deployment)
SUS in connection with both scenarios mentioned above
Catalog Content Management
This also includes:
operational usage of contracts (e.g. for the assignment of sources of supply)
RFP - as far as known from the Temporary Labor scenario
Please be aware that the following deployment and migration constraints apply:
ERP 2005 with SRM as an add-on does not support any multiple-backend functions or hub deployment for procurement
Upgrade or migration from an existing SRM system to ERP 2005 with SRM as an add-on is not supported.
SAP does not offer migration paths from an SRM AddOn deployment to a deployment with a standalone SRM system.
The extended classic deployment is not supported.
The SRM as an add-on is only supported in the release combination ERP 6.0 and SRM 5.0. Other release combinations are not supported. Also future SRM releases will not run as an add-on on ERP 6.0
for more info
Read note 963000
and thread
BR
Dinesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.