Sourcing / SUS - classic versus extended classic

[former_member214648]

Hi all

I'm looking for a comprehensive comparison of the functionality of sourcing (RFX reverse auctions) when the scenario is classic versus extended classic - so is all functionality available regardless of scenario.

Also the same for SUS - does the functionality in SUS change depending on scenario?

Any help much appreciated!

[former_member214648]

We are running SRM 7.0, so my question is, can we use SUS on an extended classic SRM system for ALL in direct procurement including services? 

I've been doing some additional research, and am even more confused!  Maybe someone can please help.

In the SAP Press Book Enhancing Supplier Relationship Management with SAP SRM it shows a diagram on page 212 of Service Procurement with Supplier Integration.  Looks nice. 

We will not be using plan driven procurement so the plant driven scenario from MM - SUS isn't idea for us.

Page 276

says The classic scenario does not allow for a PO to be sent o SUS from MM in SAP.... Supplier enablement is not support in SUS when using the Classic scenario.

Further Page 282 say if the extended classic scenario is implemented, only the PO can be communicated between SAP EB and SUS the follow on document such as PO confirmation or invoice entry cannot be communicated between SAP EB and SUS.

So slightly more confused, when would you implement SUS?

There is a further note on page 223 that says, The self - service procurement scenario using MM-SRM and SUS in the standard SRM system is only available beginning with SAP SRM 7.0.....

Is there a simple answer to the question above?

Many thanks!