Tehnical Scenarios
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 backend 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.
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 Enterprise Buyer. The remainder of the procurement process takes place in the backend 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) backend system(s), since all materials management documents, such as purchase orders, goods receipts, service entry sheets, and invoices are located there. (You use SAP Enterprise Buyer to create the shopping cart and obtain approval if required. You can also enter the goods receipt and invoice here. SAP Enterprise Buyer communicates this information to the backend 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 Enterprise Buyer'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 backend system(s)
- For whom a transfer of purchasing activities to SAP Enterprise Buyer is not viable
Extendend Classic Scenario
In the Extended Classic scenario, the shopping cart is created in SAP Enterprise Buyer. The purchase order and follow-on documents are also created there and then replicated to the backend system. The purchase order in SAP Enterprise Buyer is the leading purchase order. Goods receipts and invoices can be pre-entered in SAP Enterprise Buyer or entered directly in the backend system.
This scenario is an extension of the classic scenario. Whereas in the classic scenario, goods and services are processed in the backend system, in the extended classic scenario, the procurement process takes place locally in SAP Enterprise Buyer and the data is replicated to the backend system.
If the data in the shopping cart is insufficient to generate a complete purchase order, you can supplement the data manually in SAP Enterprise Buyer before it is transferred to the backend system. The purchase order in SAP Enterprise Buyer is the leading purchase order. From SAP Enterprise Buyer Release 4.0 with an SAP backend system Release 4.6, the complete purchase order is replicated to the backend. It is a read-only copy and supplies the reference needed for the creation of goods receipts, service entry sheets, and invoices in the backend system.
This scenario suits customers:
- Who want their purchasing department to save time and money by using the streamlined purchasing functionality of SAP Enterprise Buye.
- Who want to use the full sourcing capabilities SAP Enterprise Buyer offers, yet who also want to be able to confirm and invoice direct materialsWho want the flexibility of being able to pre-enter confirmations and invoices in SAP Enterprise Buyer
Standalone Scenario
The shopping cart and purchase order are processed directly in SAP Enterprise Buyer. You have no materials management functions in your ERP system and, instead, use those in SAP Enterprise Buyer for all procurement processes. The final invoice is sent to a backend accounting system. With SAP Supplier Self-Services, you have complete supplier involvement for all your operational procurement scenarios.
Overview table
The following table gives an overview of the differences between each of these scenarios in terms of where the main processes occur.
| Classic | Extendend | Standalone | |
|---|---|---|---|
| Shopping Cart | in EBP | in EBP | in EBP |
| Approval | in EBP | in EBP | in EBP |
| Purchase Order | in backend | in EBP (leading system) and backend system (copy) | in EBP (accounting information sent to backend system) |
| Goods Receipt | in backend (can be pre-entered in EBP) | in backend (can be pre-entered in EBP) | in EBP |
| Invoice | in backend (can be pre-entered in EBP) | in backend (can be pre-entered in EBP) | in EBP (accounting information sent to backend system) |
No comments:
Post a Comment