How do I decide between SRM classic or extended?

How do I decide between SRM classic or extended?

How do I decide between SRM classic or extended?

    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

This question has a couple of different responses. Check out the links below to see which response is right for your situation.

"The selection of implementation scenarios in SRM is really two-fold –- business requirements driven and implications on the technical environment. Additionally, certain SRM functionality is only available based on the scenario implemented.

Having said that, unfortunately there is not an answer that fits all..."
Click here to read the rest of the response...

"The following scenarios are supported for EBP/SRM:
Classic Scenario:
"The majority of SAP SRM implementations today in the US are implemented as a Classic Scenario. Here is a very tight integration with the SAP R/3 system. The Leading Purchase Order document is created in the R/3 system. A number of organizations have chosen this implementation scenario as it provides the advantage of having the least impact on your existing backend processing..."
Click here to read the rest of the response...

This was first published in July 2005