Classic Scenario

[trradhakrishnan]

Dear experts,

PLs can u anybody explain what is Classic Scenario, extended classic scenario, standalone scenarion, Decoupled....

Regards

D Ganesh

[trradhakrishnan]

Dear all,

Thank u..now i clearly understand the process

regards

D GANESH

[pedro_santos6]

shyamasundar,

We have a lot of information in the forum talking about the sceneries.

Or see that link: [http://wiki.sdn.sap.com/wiki/display/SRM/Technical%20Scenarios |http://wiki.sdn.sap.com/wiki/display/SRM/Technical%20Scenarios]

Rgs,

Pedro Marques

[Former Member]

Hi again,

Sorry I didn't see the end of your question.

Standalone Scenario:

Your shopping cart items create local procurement documents only. This means that all follow-on processes, such as confirmation or invoice have to be performed in SAP SRM Server.

The Decoupled Scenario:

This is not a scenario itself, but is a combination of more than one scenario, for example, a combination of the classic and standalone scenarions. Some items are handled locally, while others are transferred to the ERP backend.

For more information you can also check the following link

Link: [http://help.sap.com/saphelp_srm50/helpdata/en/bc/07f73b7803b009e10000000a114084/frameset.htm]

Hope this helps,

Kind Regards,

Matthew

[Former Member]

Hi Shyam,

CLASSIC SCENARIO :

You implement Enterprise Buyer and one or more back end systems (SAP or Non-SAP). All Materials Management is mapped in the ERP system. All materials management documents (such as purchase orders, goods receipts, service entrysheets, and invoices) exist in the back end system.When the shopping cart is ordered, a workflow is triggered that checks whether approval is necessary. If approval is required, a work item is sent to the Inbox of the relevant approver.If approval is not required, the necessary purchase requisitions, purchase orders or reservations are created for the shopping cart. Which documents are created, and in which back end system, depends on the information in the shopping cart and on the settings in Customizing for Enterprise Buyer.

EXTENDED CLASSIC SCENARIO :

This scenario is an extension of the classic scenario. In the classic scenario,all Materials Management takes place in the back end system, while in the extended classic scenario, the complete procurement process takes place locally.Communication between Enterprise Buyer and the back end system is via RFC.The purchase order is created locally in Enterprise Buyer at first. If the data in the shopping cart is insufficient to generate a complete purchase order, the data is supplemented manually within Enterprise Buyer before being transferred to the back end system. The purchase order in Enterprise Buyer therefore is the leading purchase order. The plant is the criterion used for splitting shopping cart items into different purchase orders because the purchasing organization is determined in the back end system on the basis of the plant. Goodsreceipts (confirmations) and invoices can be entered in Enterprise Buyer or the back end. If the data in the shopping cart is sufficient to generate a complete purchase order,

this purchase order will be copied to the according back end system automatically.

STANDALONE SCENARIO :

The customer does not have a productive Materials Management system and wants to handle the entire process locally within the Enterprise Buyer, integrating only to an accounting system. Accounting processes (including FI, CO, and AM) must still be handled by a back end system. Validations and approvals are handled directly within Enterprise Buyer rather than in a back end system.

A shopping cart is created locally and will be further processed locally in principle.

DE-COUPLED SCENARIO :

You have a productive MM back end system, but want to handle parts of the process locally and other parts within the MM system. This means that specific shopping basket items create POs or requisitions with all follow-on processes in the back end MM, while others are processed locally.For example, office supplies could be processed locally while all items for plant maintenance goods are processed in the back end system.Whether the system creates a PO in the back end system or locally depends on the product category. You have to define in the customizing whether the product category is a local product category or a back end product category. By using a BADI, you can define your own rules.

Edited by: Pbponikhil on May 17, 2010 2:07 PM

Edited by: Pbponikhil on May 17, 2010 2:08 PM

[Former Member]

Hi there,

Classic Scenario:

You implement SRM Serbver and one or more ERP systems. All shopping carts refer to materials management processes in your ERP back-end system. Your ERP system is the leading system. Goods Receipts (confirmations) and invoices can be entered in SRM Server or in the ERP backend system.

Extended Classic Scenario:

The purchase order is created locally within SRM Server and a copy sent to the backend. If the data in the shopping cart is insufficient to complete a purchase order, the data is supplemented manually within SRM Server before being transferred to the backend system. The purchase order in SRM Server is the leading purchase order. Goods receipts (confirmations) and invoices can be entered in SRM Server or in the backend.

Hope this helps,

Kind Regards,

Matthew