Classic Vs Extended Classic

[Former Member]

Hi MM/SRM experts

We have ECC 6.0 and SRM 5.0 for a manufaturing industry which has stock and non stock purchases. What are advantages and disadvantages going for classic or extended classic scenarios.

Regards

Mani

[Former Member · Accepted solution]

Hi,

Difference between extendend and classic scenario:

When Extended is set to on, Enterprise Buyer generates a local purchase order for each item in the schopping cart. All follow-on documents are created in the backend system as well as locally in SRM.

When You have Classic Scenario, Enterprise Buyer processes the schopping cart items with classic scenario. All follow-on documents (including the purchase order) are created in the backend system.

on service.sap.com/instguides -> mySAP Business Suite App. -> SRM 5.0 -> Scenario Specific documents.

• Self-Service Procurement

• Plan-Driven Procurement

• Service Procurement

• Catalog Content Management

• Strategic Sourcing

• Spend Analysis

This PDFs describes most important things about SRM Scenarios.

Also look in:

http://help.sap.com/saphelp_srm50/helpdata/en/8d/f6a93e08503614e10000000a114084/frameset.htm

Regards,

Marcin Gajewski

[Former Member · Accepted solution]

Hi ,

Many thanks .Have gone thro all these docs already . Would like to know from the previous project experience.

Regards

Mani

[Former Member · Accepted solution]

Hi,

Mostly my clients use Ext. Classic Scenario with BADI BBP_EXTLOCALPO_BADI.

Advantages of that way is:

- All follow-on documents are posted do backend

- You may use backend Business Warehouse to reporting SRM SC, PO's etc.

- if You have more than one backend, You may post follow-on document to different R/3 system basing on product type, product, product category

- if You have more than one organisation in PPOMA, You may control posted documents

- if You create a SC in SRM, system check your stock and decide what of follow-on document create (Reservation, Requirement, POrder) - You may control that in BADI

Disadvantages:

- posted follow-on documents to backend are read-only.

Regards,

Marcin

[Former Member · Accepted solution]

Thank you very much for sharing your experience

1) I feel advantages can be met with using the Classic scenario itself . and we can levaerage more funcitonalities of purchase order in backend system

a) PO release based on the various characteristics(price, doc type, pur group etc) - i am not sure wr this can be done in SRM

b) Pricing conditions and pricing procedure ,intergration with FI . - I am sure this can't be done in SRM

c) Tax procedures - I am sure this can't be done in SRM.

2) In case of manual reservation creation , how the movement type will be determined. how the goods issue to cost centre, project or PM will be differentiated in case we decide to use single web based front ent system to capture the requirement

What are other advantages for the business in using ECS in stead of CS

Regards

Mani

[Former Member · Accepted solution]

1) For eg. pricing in SRM is so-called Carry Out Sourcing (source of supply). You can create PO basing on proposing sources of supply (many vendors, vendor list, prices).

Pricing conditions You can maintain in COMMPR01 transaction for any material. There is a vendor price, default price, scales etc. In our system vendors maintain there own prices for product via ms excel (see these two blogs:

/people/kathirvel.balakrishnan2/blog/2005/09/07/remote-function-call-to-sap-system-using-microsoft-excel

/people/kathirvel.balakrishnan2/blog/2006/05/08/data-upload-into-sap-from-microsoft-excel-150-abap-part) You can use XI too.

Tax procedures is in SPRO -> SRM -> ... -> Cross-Application Basic Settings -> Tax Calculation. You can control it from BADI.

Advantages Classic Scenario:

- in Self-Service Procurement - SC is created in SRM (no GUI - Web interface) and post to backend. Purchasers create PO in backend basing on replicated SC.

Classic Scenario is combined with Indirect Procurement. Within the Indirect Procurement (Classic) scenario, the purchase order is not created in the Enterprise Buyer system.

Regards,

Marcin