In the realm of SAP Supplier Relationship Management (SAP SRM), choosing the right deployment scenario is critical for aligning procurement strategies with business objectives. Two of the primary deployment options in SAP SRM are the Classic Scenario and the Extended Classic Scenario. Both approaches have unique architectures, integration methods, and use cases. Understanding their differences is essential for system architects, procurement leads, and SAP consultants.
SAP SRM supports multiple deployment scenarios that determine how procurement documents such as Purchase Orders (POs) and Goods Receipts (GRs) are created and processed between the SRM system and the ERP backend system (like SAP ECC or S/4HANA).
The three main scenarios include:
This article focuses on comparing Classic and Extended Classic scenarios.
In the Classic Scenario, the actual procurement transactions—such as purchase orders, goods receipts, and invoices—are created and processed directly in the backend ERP system. The SRM system is primarily used for shopping cart creation and approval workflows.
The user creates a Shopping Cart in SAP SRM.
After approval, the system transfers the request to the ERP backend, where:
Updates and status messages are sent back to SRM for user display.
In the Extended Classic Scenario, the Purchase Order is created and managed within the SRM system itself. The ERP system is updated only for accounting and logistical postings (such as goods receipt or invoice posting).
User creates and approves a Shopping Cart in SAP SRM.
A Purchase Order is generated in SRM.
The PO is replicated to the ERP backend for:
| Feature | Classic Scenario | Extended Classic Scenario |
|---|---|---|
| PO Creation | In ERP backend | In SRM system |
| PO Management | In ERP | In SRM |
| Workflow Handling | Mainly in ERP | Fully in SRM |
| Supplier Communication | Via ERP | Via SRM (e.g., XML, email) |
| Change Version Handling | Limited | Full versioning in SRM |
| Backend Dependency | High | Lower |
| Implementation Complexity | Moderate | High |
| Best For | Centralized procurement models | Decentralized or flexible procurement |
Both Classic and Extended Classic Scenarios offer significant capabilities within SAP SRM, and the choice between them depends on organizational structure, integration needs, and the level of process centralization. As SRM continues to evolve alongside SAP S/4HANA and Ariba solutions, understanding these core deployment options remains essential for successful SRM implementations.