SAP SRM supports four deployment scenarios based on the level of integration required with Back end ERP. The scenario you choose will dictate where (SRM or ERP) actions will be taken and follow on documents will be created. So choosing the implementation Scenario is the first and most critical step, you would need to take before implementing SAP SRM.
The four deployment scenarios are:
- Classic Scenario - The classic system depends heavily on strong back end ERP system. Clients who have implemented SAP ERP and use MM module can go for Classic scenario. Requisitions in classic scenario are created in SRM and PO is created in ERP. Confirmations and invoices can be created in either ERP or SRM
- Extended classic - Extended Classic is similar to Classic scenario except that PO is also created in SRM and then replicated in ERP. Everything else remains same.
- Standalone - Standalone scenario is usually used when strong ERP is not there. In Standalone scenario, all the documents are created in SRM and only invoice is sent to ERP system. Clients who have not implemented SAP ERP can go for standalone scenario.
- Decoupled - While decoupled is not an official scenarios, the term is used to specify scenario when a combination of above three scenarios is used based on product category.
Comparison of ScenariosThe primary difference among difference scenarios is the level of integration between ERP and SRM. As a result, the key difference is where documents are created and maintained. The differences are listed in table below.
|Purchase Order Copy||Display Copy||NA||ERP||NA|
|Goods Reciept/Confirmation||Create||SRM, ERP||SRM, ERP||SRM|
|Invoice||Create||SRM, ERP||SRM, ERP||SRM|