Skip to end of metadata
Go to start of metadata

Purpose

The main purpose of this page is to explain the concept of the SRM technical scenarios and provide more information about document processes across the scenarios. 

Overview - Technical Scenarios

 

See also the Decision Matrix and Scenario CV.

This is a collection of information, which is required for the implementation of a specific SRM technical scenario.SAP SRM is a solution that you can implement in a heterogeneous system environment that includes SAP systems and/or other Enterprise Resource Planning (ERP) systems as back-end systems. You must have the components Financial Accounting and Controlling in your system environment.
There are different business scenarios that you can apply depending on your role as a user and the kind of business you wish to conduct using SAP SRM. You can deploy each of these business scenarios using one of three different technical scenarios.

Classic Scenario

In the Classic scenario, the shopping cart is created and approved in SAP SRM. The remainder of the procurement process takes place in the back-end ERP system(s) and all other follow-on documents, such as the purchase order, goods receipt/service entry sheet and invoice, are located there. This scenario relies strongly on the Enterprise Resource Planning (ERP) back-end system(s), since all materials management documents, such as purchase orders, goods receipts, service entry sheets, and invoices are located there. (You use SAP SRM to create the shopping cart and obtain approval if required. You can also enter the goods receipt and invoice here. SAP SRM communicates this information to the back-end system where the active documents are created.)

This scenario suits customers:

  • Who want a wide user group, for example employees not necessarily working in the purchasing department, to be able to enter their requirements quickly and easily. SAP SRM's functionality and ease of navigation allow this, as it requires only minimal training
  • Who want their purchasing department to operate solely with the functionality offered by the back-end system(s)
  • For whom a transfer of purchasing activities to SAP SRM is not viable

For more information about Classic Scenario refer this link.

Extended Classic Scenario

In the Extended Classic scenario, the shopping cart is created in SAP SRM. The purchase order and follow-on documents are also created there and then replicated to the back-end system. The purchase order in SAP SRM is the leading purchase order. Goods receipts and invoices can be pre-entered in SAP SRM or entered directly in the back-end system.

This scenario is an extension of the classic scenario. Whereas in the classic scenario, goods and services are processed in the back-end system, in the extended classic scenario, the procurement process takes place locally in SAP SRM and the data is replicated to the back-end system.

If the data in the shopping cart is insufficient to generate a complete purchase order, you can supplement the data manually in SAP SRM before it is transferred to the back-end system. The purchase order in SAP SRM is the leading purchase order. From SAP SRM Release 4.0 with an SAP back-end system Release 4.6, the complete purchase order is replicated to the back-end. It is a read-only copy and supplies the reference needed for the creation of goods receipts, service entry sheets, and invoices in the back-end system.

This scenario suits customers:

  • Who want their purchasing department to save time and money by using the streamlined purchasing functionality of SAP SRM.
  • Who want to use the full sourcing capabilities SAP SRM offers, yet who also want to be able to confirm and invoice direct materials
  • Who want the flexibility of being able to pre-enter confirmations and invoices in SAP SRM

For more information about Extended Classic Scenario refer this link.

Standalone Scenario

The shopping cart and purchase order are processed directly in SAP SRM. You have no materials management functions in your ERP system and, instead, use those in SAP SRM for all procurement processes. The final invoice is sent to a back-end accounting system. With SAP Supplier Self-Services, you have complete supplier involvement for all your operational procurement scenarios.

For more information about Extended Classic Scenario refer this link.

Overview table

The following table gives anoverview of the differences between each of these scenarios in terms of where the main processes occur.

 

Classic

Extended

Standalone

Shopping Cart

in SRM

in SRM

in SRM

Approval

in SRM

in SRM

in SRM

Purchase Order

in back-end

in SRM (leading system) and back-end system (copy)

in SRM (accounting information sent to back-end system)

Goods Receipt

in back-end (can be pre-entered in SRM)

in back-end (can be pre-entered in SRM)

in SRM

Invoice

in back-end (can be pre-entered in SRM)

in back-end (can be pre-entered in SRM)

in SRM (accounting information sent to back-end system)