Hi Vel
I suggest that instead of checking the possibility of implementing any combined scenario's like how you have asked ( Classic+Extended classic scenario).
You need to map the Business requirement and how the Business teams wanted to handle the PO ,GR etc and accordingly you have to plan for implementation scenario. You can' customise the standard SRM delivered options for these scenario . I t is advisable to either go for Classic or Extended classic. But combination of Classic & stand alone scenario is possible.
for your ready reference i have given below capabilities of all scenarios, which you may already know..
Key implementation scenarios
u2022 Classic
o Implement EBP and one or more ERP system . All shopping carts refer to MM process in your ERP backend, your ERP is the leading system. GR (Confirmations and invoices can be entered in Enterprise Buyer or ERP back end system
u2022 Extended classic
o Purchase order is created locally within EBP system , if the data in the shopping cart is insufficient to generate a complete purchase order. The data is supplemented manually within the enterprise buyer system EB is the leading system , GR,IV can be done in both EBP and ERP system.
u2022 Decoupled
o Combination of classic and standalone scenario ,some items are locally handled, some items are transferred to the ERP back end system
o We are able to send PO from both the system.
u2022 Standalone
o Your SC items create local procurement only, this means all the follow on doc like GR,IV will be done at EB system only.
o Only commitment & invoice posting will be done at ERP backend
You can get the final Business requirement and plan.
Regards
Narahari
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.