SAP SRM - Deployment Options
SAP SRM can be integrated with SAP ERP for backend processing for procurement, inventory and financial management. It can integrate with SAP ERP applications and non-ERP systems.
There are four different deployment scenarios that you can use with SAP SRM −
Standalone Deployment
In a Standalone Deployment model, all the procurement processing is performed in SAP SRM system and backend accounting system is used for invoice financial processing.
In a Standalone Deployment scenario, purchase order management, shopping cart and goods receipt and invoices are processed in SRM system.
This scenario is suggested for the following customers −
When there is no operational backend system for material management and there exists only financial accounting systems in landscape.
When you want to move all procurement activities in SAP SRM system and hence allow companies to decrease the work load on the backend procurement system by transferring buyers which are interested to procure from selected options.
It is recommended for customers who want to maintain only minimal product data and only rely on supplier catalogs.
Classic Scenario
In a classing deployment model, you process the shopping cart in SAP SRM and supporting documents are processed in backend ERP system.
You can perform goods receipt or invoices in any of the systems.
This deployment model is suggested for those customers who have a strong backend procurement system and where buyers do not want to use multiple systems for their operations.
Extended Classic Deployment
In this deployment model, procurement process takes place in SAP SRM system and PO is generated in SRM system and a read only copy is created in backend ERP system.
You can perform goods receipt or invoices in any of the system as in the case of classic scenario.
This model is recommended where you want few of procurement functionalities in SAP SRM like PO response, etc.
You can implement direct material in extended classic deployment scenario.
Decoupled Deployment
When you use all the three scenarios parallel, this is called decoupled scenario. When customers want to utilize all the functionalities of each component, SAP SRM allows to use all the above scenarios in parallel.
Example
Consider a customer who wants to use the standalone deployment model for certain indirect materials and routine services, the classic scenario for stock materials to utilize inventory and planning capabilities of backend materials management system, the extended classic deployment scenario to perform effective supplier management to provide response for PO’s.
