Difference between service procurement classic and extended classic?

[Former Member]

I could you find any document for extended classic.

Could anybody help explain what is different between the 2 classics?

Thanks!

[Former Member · Accepted solution]

In the Extended Classic scenario, the entire procurement process takes place locally in EBP (SRM) and a copy of the data is replicated to the back-end system. In essence, this scenario is an extension of the Classic Scenario.

The purchase order in the back-end SAP system (ERP , R/3 System) is a read-only copy that enables goods receipt, service entry, and invoice verification in the back-end system. The back-end purchase order cannot be changed. If you wish to make any changes to the purchase order, you must do so in EBP i.e. SRM system. Once you save these changes, they are transferred to the back-end purchase order.

While in Classic Scenario , The PO is created in the backend ERP system once the SC is approved.

In brief , you can say while in extended classic scenario , the backend ERP system is a read only system and we do everything is EBP (SRM) system only. and in Classic Scenario , ERP system was used to generate the purchase orders.

Hope it clarifies and gives you a little visiblity on what is the difference between both.

[Former Member · Accepted solution]

Thanks a lot!

Just one more quick question. You say:

once the SC is approved.

What is SC?

Regards.

[Former Member · Accepted solution]

HI ,

SC stands for Shopping Cart or you may also call it a requisition

PO stands for Purchase Order.

In SRM, Requistioners raise a SC which goes to the approvers for approval and once approved a buyer need to raise a PO for the same.

rgds

Chetan