The Consultant´s Guide to SAP® SRM 1

THE CONSULTANT´S GUIDE

TO SAP® SRM

Submitted By:
Ankit Goyal-09609025
Priya Srivastav-09609056
Ankita Jain-09609098
Chandrika Chauhan-09609119

12/08/21
 SAP SRM Deployment Scenario
2

The Consultant´s Guide to SAP® SRM 12/08/21

 SAP SRM Deployment Scenario
3

The Consultant´s Guide to SAP® SRM 12/08/21

4

The Consultant´s Guide to SAP® SRM 12/08/21

 Important Settings That Determine the Classical
Scenario
5

The Consultant´s Guide to SAP® SRM 12/08/21

 The Extended Classic Scenario
6
• In an extended classic scenario, the procurement process takes place in the
SAP SRM system. The purchase order is created in the SAP SRM system
and a read only copy of the purchase order is replicated to the backend
system.

Applicability of the Extended Classic Scenario

Applicable to customers who want sophisticated procurement functionalities

in SAP SRM.
• Purchase order response from the vendor can be captured in SAP SRM.
• The full sourcing capabilities of SAP SRM are available in the extended
classic scenario.
The Consultant´s Guide to SAP® SRM 12/08/21
7

 Direct material procurement is enabled in the extended classic scenario

only.
 Sophisticated workflow functionality is available in SAP SRM.
 Entry of confirmation is easier in SAP SRM compared to backend ERP.
 Procurement card functionality is available in the extended classic and
standalone scenarios only.

The Consultant´s Guide to SAP® SRM 12/08/21

 Process Flow
8

The Consultant´s Guide to SAP® SRM 12/08/21

9

The extended classic scenario process flow:

 An employee searches the catalogs and creates an online shopping cart for
his requirements.
 The system triggers an approval workflow based on the workflow start
conditions defined in the configuration settings. The workflow is routed to
the mailbox of the approving manager, who approves or rejects the
shopping cart.
 If the shopping cart is approved, the system creates a purchase order in the
SAP SRM system. If the data is incomplete, the shopping cart is moved to
the sourcing cockpit for further action.
The Consultant´s Guide to SAP® SRM 12/08/21
  Purchase orders can be created in the following ways:
 From a shopping cart.
10
 From an external requirement created in the backend system and transferred to
SAP SRM.
 Directly in SAP SRM from the Transaction “Create purchase order”.
 From the winning bid in a bidding or reverse auction process.

 The purchase order is created in the SAP SRM system. A copy of the
purchase order is replicated to the backend system.
 The purchase order response from the supplier can be entered directly in
SAP SRM or updated automatically via XML communication.

The Consultant´s Guide to SAP® SRM 12/08/21

11

 The goods receipt for materials or service entry sheet for services is
created directly in the backend system.
 Invoices can be entered directly in the backend system. Alternatively,
users can create invoices in the SAP SRM system

The Consultant´s Guide to SAP® SRM 12/08/21

 Important Settings that Determine The Extended
Classic Scenario
12

At least one backend materials management system

and accounting system is connected to the SAP SRM
system.
 Product categories from the backend procurement system are replicated and used
in the SAP SRM system.
The extended classic scenario is activated in the configuration setting “Activate
Extended Classic Scenario”.

The Consultant´s Guide to SAP® SRM 12/08/21

 Important Settings that Determine The
Extended Classic Scenario (Contd)
13

 If the backend system is an SAP R/3 version

lower than 4.6B, you must define local purchasing
organizations and purchasing groups.
 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the
purchasing group used in the purchase order to the backend purchase group.
 If a purchasing group and purchasing organization are used, then a valid backend
purchasing group is assigned to the RFC user.

The Consultant´s Guide to SAP® SRM 12/08/21

 The Decoupled Scenario
14

 SAP SRM officially does not have a scenario

called decoupled.
 The scenario is loosely used to indicate the ability to use the other three scenarios
in parallel.
 SAP recognizes that the procurement strategy for each category of purchases can
be different.
 Any procurement solution should offer flexibility during implementation to cater
to all requirements.
Hence, SAP SRM provides the flexibility to implement all three scenarios in
parallel, based on customers’ requirements.

The Consultant´s Guide to SAP® SRM 12/08/21

 Applicability of the Decoupled
Scenario
15

 Companies that wish to fully leverage the flexibility

offered by SAP SRM use the decoupled scenario.

For example, a company might want to use the standalone scenario for
certain indirect materials and routine services, the classic scenario for stock
materials so that inventory and planning capabilities of backend materials
management system can be utilized, and the extended classic scenario for
purchases where flexibility and greater collaboration with suppliers is
required in purchase order responses.

The Consultant´s Guide to SAP® SRM 12/08/21

 Process Flow
16
The process is as follows:

 An employee searches the catalogs and creates an

online shopping cart for his requirements.
 The system triggers an approval workflow based on the
workflow start conditions defined in the configuration setting.
 The workflow is routed to the mailbox of the approving manager, who approves
or rejects the shopping cart.
 The system verifies whether the product category used is a local SAP SRM
product category.

The Consultant´s Guide to SAP® SRM 12/08/21

 Process Flow (Contd)
17
 If the product category is a backend product category, the
system verifies whether the target system defined in the configuration setting
“Define backend system for product category” is a local SAP SRM.
 On approval of such a shopping cart, the system creates a purchase order in the
SAP SRM system.
 Goods receipts or service confirmations and invoices are created in SAP SRM.
 If the shopping cart does not belong to a standalone scenario, the system verifies
whether the extended classic scenario is activated in the configuration setting
“Activate extended classic scenario.”

The Consultant´s Guide to SAP® SRM 12/08/21

 Process Flow (Contd)
18

 If the extended classic scenario is not activated, the system checks whether the
BAdI to control the extended classic scenario is implemented.
 If the BAdI is implemented then the system verifies the shopping cart data with
the conditions specified in the BAdI.
 If the extended classic scenario does not apply to the shopping cart, then the
system processes the shopping cart as per the classic scenario process.

The Consultant´s Guide to SAP® SRM 12/08/21

 The Consultant´s Guide to SAP® SRM 19

DEPLOYMENT SCENARIO
IMPLEMENTATION
SETTINGS
12/08/21
 1. Standalone
20

Settings Remarks
• The product category used in the • If a product category created in
shopping cart should be local. the SAP SRM system, then it is
• In the configuration setting called local.
Define backend systems for
product category OR in
BAdIBBP_DETERMINE_LOGS
YS, the target system should be
the SAP SRM system.

The Consultant´s Guide to SAP® SRM 12/08/21

 2. Classic
21 Settings Remarks
• The product category used in the shopping • If a product category is
cart should be the backend product category. replicated from the backend
• In the configuration setting Define backend system into the SAP SRM
systems for product category OR in system, then it is called the
BAdIBBP_DETERMINE_LOGSYS, the backend product category.
target system should be the backend system.
• The extended classic scenario should not be
activated in the configuration setting
Activate Extended Classic Scenario.
• If the extended classic scenario is activated
in configuration setting Activate Extended
Classic Scenario, then BAdI
BBP_EXTLOCALPO_BADI should be
implemented.
The Consultant´s Guide to SAP® SRM 12/08/21
 3. Extended classic
22

Settings
• The product category used in the shopping cart should be the backend.
• In the configuration setting Define backend systems for product category,
the target system should be the backend system OR the target system
determined in BAdI BBP_ DETERMINE_LOGSYS should be the backend
system.
• The extended classic scenario should be activated in the configuration
setting Activate Extended Classic Scenario.
• If the extended classic scenario is not activated in the configuration setting
Activate Extended Classic Scenario, then BAdI BBP_
EXTLOCALPO_BADI should be implemented.

The Consultant´s Guide to SAP® SRM 12/08/21

 4. Decoupled scenario
23

Settings
• BAdI BBP_EXTLOCALPO_BADI should be implemented

along with the settings described for the previous scenarios.

The Consultant´s Guide to SAP® SRM 12/08/21

 The Consultant´s Guide to SAP® SRM 24

COMPARISON OF
DEPLOYMENT
SCENARIOS
12/08/21
 Item Classic Extended Classic Standalone

25 Indirect material procurement (requirement with account assignment)

Shopping cart Created in SAP Created in SAP Created in SAP

SRM. SRM. SRM.
Shopping cart Done in SAP Done in SAP Done in SAP
approval SRM. SRM. SRM.

Shopping cart Purchase Purchase order in Purchase order in

follow-on requisition, SAP SRM; SAP SRM.
documents reservation, or purchase order
without purchase order in copy is available
sourcing the in the backend
backend system. system.

The Consultant´s Guide to SAP® SRM 12/08/21

 Item Classic Extended Classic Standalone
External Purchase Purchase Purchase requisition
26 requirements requisition requisition is created in the
is created in the is created in the backend
backend backend system and
system and system and transferred
transferred transferred to SAP SRM as
to SAP SRM as to SAP SRM as a shopping cart in
a shopping cart in a shopping cart in the
the the sourcing cockpit.
sourcing cockpit. sourcing cockpit.
Approval of Only approved Only approved Only approved
external purchase purchase purchase
requirements requisitions are requisitions are requisitions are
transferred from transferred from transferred from the
the the backend. No
backend. No backend. No approval
approval approval in SAP SRM.
in SAPThe
SRM. in SAP SRM.
Consultant´s Guide to SAP® SRM 12/08/21
 Item Classic Extended Classic Standalone
Purchase order Purchase order is Purchase order is Purchase order is
creation created created in SAP SRM created
27
in the backend from the shopping in SAP SRM
system from the cart process, from the only.
shopping cart sourcing process, or
process directly from the
or from the sourcing “Create purchase
process. order” transaction. A
copy is created in the
backend.
Purchase order Purchase order is Changes can be done Changes can be
change maintained only in only in SAP SRM. done only in SAP
the backend system. SRM.
Purchase order Complete document Both SAP SRM and SAP SRM only.
display in the backend the backend system.
system & important
data in the shopping
cart follow-on
The Consultant´s Guide to SAP® SRM 12/08/21
documents.
 Item Classic Extended Classic Standalone
Goods receipt or Backend system Backend system Confirmations are
28 service entry (can (can entered in SAP
be entered as be entered as SRM
confirmation confirmation only.
in SAP SRM in SAP SRM
also). also).

Invoice Backend system Backend system Entered in SAP

(can (can SRM
be entered in SAP be entered in SAP only
SRM also). SRM also). (accounting
document
is created in the
backend).
Use of Not supported Supported from Supported.
procurement SAP
cards SRM 2007. on.
The Consultant´s Guide to SAP® SRM 12/08/21
 Item Classic Extended Classic Standalone
Direct material procurement (requirement without account assignment
i.e., order as direct material)
29
Shopping cart Created in SAP Created in SAP SRM Not
SRM with ‘Order as Direct applicable.
with ‘Order as material.’
Direct material.’
Shopping cart Purchase order in Purchase order in SAP Not
follow-on SAP SRM; purchase SRM; purchase order applicable.
documents order copy is copy is available in the
without available in the backend system.
sourcing backend system.
External Purchase requisition Purchase requisition is Not
requirements is created in the created in the backend applicable.
backend system and system and transferred
transferred to SAP to SAP SRM as a
SRM as a shopping shopping cart in
cart in sourcing.
sourcing.
The Consultant´s Guide to SAP® SRM 12/08/21
 Item Classic Extended Classic Standalone
Approval of Only approved Only approved Not applicable.
30 external purchase purchase
requirements requisitions are requisitions are
transferred from transferred from
the backend. No the backend. No
approval approval
in SAP SRM. in SAP SRM.
Purchase order Purchase order is Purchase order is Not applicable.
creation created in SAP created in SAP
SRM. A copy is SRM. A copy is
created in the created in the
backend. backend.
Purchase order Purchase order Purchase order Not applicable.
change can be changed in can be changed in
SAP SRM only. SAP SRM only.

The Consultant´s Guide to SAP® SRM 12/08/21

 CONCLUSION
31

• SAP SRM can be flexibly integrated with backend ERP systems.

• Customers can choose the level of integration depending on their
organization’s requirements.
• This flexibility ensures that customers are not left with rigid rules in their
procurement processes and they can choose the processes based on the
requirements of each product category.

The Consultant´s Guide to SAP® SRM 12/08/21

32

Thank You!!

The Consultant´s Guide to SAP® SRM 12/08/21