Deployment Scenarios of SRM
There are 4 standard Deployment Scenarios in SRM.
Confirmation & Invocing can be posted from the SRM or from the R/3 System.
In Extended Classic Scenario (ECS) the leading system will be the SRM System. Here the Shopping cart is created and the PO is created locally. Replica of the PO will be transferred to the backend system.
Confirmation and Invoicing can be done in SRM and in R/3
In this scenario there will be a SRM System and there will be no MM Backend system. Everything happens in the SRM System. So the leading system is also SRM System.
There are 4 standard Deployment Scenarios in SRM.
- Classic
- Extended Classic
- Standalone
- Decoupled
Classic:
Classic Scenario is a scenario where the leading System will be the Backend R/3 System. Here the Shopping carts gets created in SRM and the PO will be created in R/3.Confirmation & Invocing can be posted from the SRM or from the R/3 System.
Extended Classic:
In Extended Classic Scenario (ECS) the leading system will be the SRM System. Here the Shopping cart is created and the PO is created locally. Replica of the PO will be transferred to the backend system.
Confirmation and Invoicing can be done in SRM and in R/3
Standalone:
In this scenario there will be a SRM System and there will be no MM Backend system. Everything happens in the SRM System. So the leading system is also SRM System.
De-Coupled.
This scenario is a mix of Classic + Extended Classic Scenario. You can configure few product categories behave as "Classic" and other Product categories behave as "Extended Classic" scenario.
For this Badi "BBP_EXTLOCALPO_BADI" needs to be coded.
For this Badi "BBP_EXTLOCALPO_BADI" needs to be coded.
No comments:
Post a Comment