Difference between Classic Scenario and Extended Classic Scenario

[Former Member]

Hi Expers,

I need your help again........:-)

I just want to know what is the differne between classic and Extended Classic Scenario.

Points will be rewarded

Thank you

sam

[Former Member · Accepted solution]

Hi Sam,

(explaination frm a previous thread)

Difference between scenarios

WIth classic scenario, the SC following document is to be created in your R/3 backend(s). Thus you can get an PO, a PR or a stock reservation in R/3.

With extended classic the following document is to be found in SRM itself. Thus from a SC item you can get a complete PO, an incomplete PO or depending on your customizing a Sourcing cockpit (now called Sourcing Application) requirement. Additional FM are called when you tick the box "Enable Extended classic" in the IMG activity, enabling you to get a local PD.

If you need to get a stock reservation in R/3 with extended classic, you will have to switch back to classic scenario for the particular category or product with a dedicated BADI ("Control extended classic ").

Be aware that with extended classic, the PO created in R/3 is not exactly a replication. That is a "copy" with that crucial difference that the SRM PO will use a different Purchase Organization that of R/3. It enables you to centralize your purchasing. In SRM you can create a "local" Purch. Org for EMEA zone for instance while in R/3 that is rare you can purchasing above a country (because in the backend you have to produce legal documents related to one company). Those "local" (=SRM) Purch. Org. are required to enable extended classic and it makes simpler Contract management for instance (in classic scenario contracts may need to be replicated to your R/3 back end and adjusted for each back end and each Purch Org in R/3, and even for each plants).

In a nutshell with extended classic you have a PO in SRM, and this PO is assigned to a different Purch Org that of R/3. Purch Org in R/3 are determined on the basis of the "LOcation" (R/3 plant you have replicated from your backent into SRM).

Extended classic is required for service purchasing when you want your requesters to be able to adjust the PO price while they can not access R3. In extended classic, PO is issued from SRM and not from R3.

Please check this too:

http://help.sap.com/saphelp_srm40/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/content.htm

BR,

Disha.

[former_member99480]

Hi Disha

can you explain how a Reservation is created in ECS ?

when you say Control Ext BAdI , u mean EXTLOCALPO_BADI ?

Steps done -

1. Activated ECS with the above BAdI

2. selected "Reservation generated if Stock Available, otherwise ext procuremet" in spro -Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders).

Result -

the ECS product cat always lands up in Purchaser's list , even though Availability Check works fine and Stock in available.

The Purchasing Grp , automatically selected is local and is un changeable in S cart.

Thanks!

Vivek

[imthiaz_ahmed]

The answers are aplenty in this forum, please do a search.

Regards, IA

[Former Member]

also read the documentation for BADI to control the extended classic scenario

under SRM IMG->SRM->SRM server->Business Add ins->

with this exit you can specify yr logic to control the behaviour of SRM for ECS/CLASSIC

BR

Dinesh

[former_member183819]

Before we go to to Business Scenario ,we have to freeze the technical implementation scenario .

In Classic Scenario , The PO will be created in Backend system.

In Extended Classic scenario, the PO will be created in EBP system as well as the image copy of PO will be send it to backend system.For ECS EBP is a leading system. You can edit PO only in EBP system not in R/3.

For more details ...

http://help.sap.com/saphelp_srm50/helpdata/en/d6/4def8242df214aa27644e41da65d07/frameset.htm