Having said that, unfortunately there is not an answer that fits all. Just because an organization has chosen to implement a classic scenario, it is not to say that they could have not implemented extended classic. This decision is entirely based on the business processes being implemented, their current environment (eg. SAP or legacy?), and the critical assessment of user acceptance.
On all my projects, I usually utilize the business blueprint phase to help determine the implementation scenario, as it best allows us to capture the true requirements of the organization. In situations where a decision for classic or extended has already been made prior to blueprint, I utilize the blueprint phase to challenge and finalize the implementation scenario.
You might want to review the "SRM Functionality Matrix".
Dig deeper on SAP supplier relationship management software
Related Q&A from Sachin S. Sethi
An SAP SRM user is looking to update an SRM URL process when implementing or changing a catalog in a live environment in SAP SRM.continue reading
An SAP SRM user wants to know how to set Confirmation and Invoice as the default options in a limit-order shopping cart.continue reading
An SAP user wants to know the benefits of implementing SAP SRM, and if it's necessary to also implement SAP BI, XI and MDM at the same time.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.