Beruflich Dokumente
Kultur Dokumente
Bonn Boston
SAP_154-0.book Seite 5 Freitag, 1. Februar 2008 1:22 13
Contents at a Glance
Contents
Dedications ............................................................................................... 17
Acknowledgments ..................................................................................... 17
Preface ...................................................................................................... 25
Purchasing has experienced a sea of change in recent years and is poised to undergo further transformation in the coming decade. Purchasing is becoming more strategic and procurement strategies are becoming vital in extending a company’s competitive advantage. 29
7
SAP_154-0.book Seite 8 Freitag, 1. Februar 2008 1:22 13
Contents
Mapping a company’s organizational structure to organizational elements in SAP applications and defining master data are the first steps in the design of a good SAP implementation. In this chapter, we will discuss the basic settings required for these steps in SAP SRM implementations. 61
8
SAP_154-0.book Seite 9 Freitag, 1. Februar 2008 1:22 13
Contents
SAP SRM is flexibly integrated with backend planning, inventory, and accounting systems. In this chapter, we will discuss in detail the different deployment scenarios possible to enable different levels of integration with backend ERP systems. 103
SAP SRM operational procurement enables companies to automate the requisition- to- pay process, and self- service procurement empowers all employees to procure their routine requirements with very little or no training while companies retain control on spend. In this chapter, you will learn about different scenarios in operational procurement and the
implementation of self- service procurement. 119
9
SAP_154-0.book Seite 10 Freitag, 1. Februar 2008 1:22 13
Contents
10
SAP_154-0.book Seite 11 Freitag, 1. Februar 2008 1:22 13
Contents
SAP SRM plan- driven procurement enables companies to transfer procurement requirements from external planning systems, like SAP ERP, to SAP SRM to reap the benefits of centralized procurement. 183
SAP SRM Invoice Management System (IMS) provides companies with advanced, collaborative, invoice exception- handling functionalities. Companies can also automate their invoicing and payment processes using procurement cards functionality in SAP SRM. 197
Workflow is defined as the systematic routing of documents to the users responsible for processing them. It is the way people, tasks, controls, and documents interact to ensure a smooth flow of business processes. 221
11
SAP_154-0.book Seite 12 Freitag, 1. Februar 2008 1:22 13
Contents
Catalog items are considered master data by many organizations and are now an integral part of the master data management strategy. SRM- MDM Catalog enables consistent product master data between SRM- MDM Catalog, SAP SRM, and SAP ERP, and supports consolidation of catalog data from suppliers and procurement systems. 249
Sourcing refers to a number of procurement practices, aimed at finding, evaluating, and engaging suppliers of goods and services. Global sourcing is a procurement strategy aimed at exploiting global efficiencies in production. 283
Procurement of services differs significantly from procurement of materials and is more complex. Requirements for services are largely undefined at the time of requisition — the scope is not fully known until the service is actually performed. SAP SRM supports the services procurement with flexible, collaborative capabilities for managing the cost constraints and
variability associated with procuring services such as temporary labor, consulting, maintenance, marketing, printing, and facility management. 317
12
SAP_154-0.book Seite 13 Freitag, 1. Februar 2008 1:22 13
Contents
13
SAP_154-0.book Seite 14 Freitag, 1. Februar 2008 1:22 13
Contents
Supplier Self- Services with SRM enables organizations to exchange documents with suppliers easily. While SUS with Materials Management (MM) facilitates collaboration with direct material suppliers, SUS with SRM EBP facilitates collaboration with indirect materials suppliers and service providers. 401
SAP NetWeaver is the technical foundation for all SAP applications. It is a comprehensive integration and application platform that works with a customer’s existing IT infrastructure to enable and manage change. SAP SRM provides innovative applications to customers by leveraging the strengths of the NetWeaver platform. 423
Any packaged application can satisfy only 60% — 80% of a customer’s requirements. However, applications built on open and flexible technologies can be molded to satisfy all customer requirements. To that end, SAP SRM is built on the SAP NetWeaver platform and provides great flexibility to define customer processes. 467
14
SAP_154-0.book Seite 15 Freitag, 1. Februar 2008 1:22 13
Contents
491
15
SAP_154-0.book Seite 103 Freitag, 1. Februar 2008 1:22 13
103
SAP_154-0.book Seite 104 Freitag, 1. Februar 2008 1:22 13
We will now discuss the four deployment scenarios in more detail, examining for
each the applicability of the scenario, the process flow, and, with the exception of
the decoupled scenario, the important settings that determine the scenario.
104
SAP_154-0.book Seite 105 Freitag, 1. Februar 2008 1:22 13
Create
Purchase Order
Commitment in
Controlling
Create
Invoice
Accounts Payable
Invoice
왘 Customers who want to use all of the functionalities in the service procure-
ment scenario.
왘 Customers who want to involve suppliers in procurement transactions using
Supplier Self- Service (SUS) integration with SAP SRM.
Note
From SAP SRM 2007 on, the procurement card functionality is also available in the
extended classic scenario.
1. An employee searches the catalogs and creates an online shopping cart for
his requirements.
105
SAP_154-0.book Seite 106 Freitag, 1. Februar 2008 1:22 13
2. The system triggers an approval workflow based on the workflow start con-
ditions defined in the configuration settings. The workflow is routed to the
mailbox of the approving manager, who approves or rejects the shopping cart.
3. 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 a
purchaser’s worklist in sourcing (commonly referred to as the sourcing cock-
pit) from where the purchaser creates the purchase order.
4. The goods receipt for materials or service entry sheet for services is created
in the SAP SRM sytem as confirmation.
5. An invoice is created in the SAP SRM system, which creates an accounting
document in the backend system.
왘 Product categories are created in SAP SRM directly, that is, local product cat-
egories.
왘 The SAP SRM system is defined as the local system in the configuration set-
ting Define Backend Systems.
왘 An accounting system is defined as the backend system in the configuration
setting Define Backend Systems.
왘 The target system for the product category should be the SAP SRM system in
the configuration setting Define Backend System for Product Category. You
can also use the standalone scenario using backend product categories with
this setting. Optionally, BAdI BBP_DETERMINE_LOGSYS is implemented to
determine the target system as the SAP SRM system.
106
SAP_154-0.book Seite 107 Freitag, 1. Februar 2008 1:22 13
as one- time- vendor purchase order, partner functions, external services with
many outline levels, and complex pricing with delivery costs, then the classic
scenario is recommended. Classic scenario is also recommended for customers
who want to involve suppliers in procurement transactions using SUS integra-
tion with Materials Management (MM).
1. An employee searches the catalogs and creates an online shopping cart for his
requirements. The employee can also view the stock status for the material.
2. The system triggers an approval workflow based on the workflow start con-
ditions defined in the configuration settings. The workflow is routed to the
mailbox of the approving manager, who approves or rejects the shopping cart.
Output to supplier
(XML/Email/Fax/Print) Create Purchase
Order
Budgets &
Commitments
In Controlling
Create Create & Approve
Goods Receipt Confirmation
Goods receipt &
invoice can
be created in
backend or in SRM
Create Create
Invoice Invoice
Accounts Payable
왘 If stock for the material is available on the requested date in the backend sys-
tem, you can specify that a reservation (material issue requisition) is created.
107
SAP_154-0.book Seite 108 Freitag, 1. Februar 2008 1:22 13
왘 Settings can be configured in such a way that the system always creates a
reservation if the material belongs to a material type that is subjected to
inventory management in the backend system.
왘 Settings can also be configured in such a way that the system never creates a
reservation and always creates either a purchase requisition or purchase
order.
왘 Settings can be configured to always create purchase requisitions in the
backend system.
왘 The system can be configured to create a purchase order, if the shopping
cart data is complete. If the data is not complete, the system creates a pur-
chase requisition.
왘 Optionally, you can use customer- specific rules to determine the backend
object by implementing BAdI BBP_TARGET_OBJTYPE.
108
SAP_154-0.book Seite 109 Freitag, 1. Februar 2008 1:22 13
왘 Purchase order response from the vendor can be captured in SAP SRM. Dif-
ferences between purchase order and purchase order response, if any, can
be approved by the purchaser in an interactive user interface.
왘 The full sourcing capabilities of SAP SRM are available in the extended clas-
sic scenario.
왘 Direct material procurement is enabled in the extended classic scenario only.
1. An employee searches the catalogs and creates an online shopping cart for
his requirements. The employee can also view the stock status, if the material
used is a stock material.
109
SAP_154-0.book Seite 110 Freitag, 1. Februar 2008 1:22 13
2. The system triggers an approval workflow based on the workflow start con-
ditions defined in the configuration settings. The workflow is routed to the
mailbox of the approving manager, who approves or rejects the shopping
cart.
3. 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 from the purchaser.
4. In the extended classic scenario, purchase orders can be created in the fol-
lowing ways:
왘 From a shopping cart
왘 From an external requirement created in the backend system and trans-
ferred to SAP SRM
왘 Directly in SAP SRM from the Transaction “Create purchase order”
왘 From the winning bid in a bidding or reverse auction process
Requisition replicated
to SRM for sourcing Create & Approve Sourcing Cockpit
Create & Approve
Requisition Shopping Cart Item or Bidding
Replication of
purchase order
Create Purchase Create
Order (Copy) Purchase Order
Output to supplier
(XML/Email/Fax/Print)
Budgets & Replication of
Commitments Purchase changes Change
In Controlling Order changed Purchase Order
5. 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 in SAP SRM is
the leading purchase order, and any changes to the purchase order can only
be made in SAP SRM. The data replicated to the backend system can be influ-
enced by implementing BAdI BBP_ECS_PO_OUT_BADI. For example, a pur-
chasing organization in SAP SRM can be mapped to a purchasing organiza-
tion in SAP ERP using this BAdI.
110
SAP_154-0.book Seite 111 Freitag, 1. Februar 2008 1:22 13
6. The purchase order response from the supplier can be entered directly in
SAP SRM or updated automatically via XML communication. The supplier
may indicate a different delivery date or a different price in the response. The
differences can be approved or rejected by the purchaser in an interactive
user interface. A workflow can also be activated for purchase order response
approvals.
7. The goods receipt for materials or service entry sheet for services is created
directly in the backend system. Alternatively, users can also create the con-
firmations in the SAP SRM system and the system automatically creates a
goods receipt in the backend system.
8. Invoices can be entered directly in the backend system. Alternatively, users
can create invoices in the SAP SRM system, which in turn creates an invoice
document in the backend system.
111
SAP_154-0.book Seite 112 Freitag, 1. Februar 2008 1:22 13
1. An employee searches the catalogs and creates an online shopping cart for
his requirements. The employee can also view the stock status for the mate-
rial.
2. The system triggers an approval workflow based on the workflow start con-
ditions defined in the configuration setting. The workflow is routed to the
mailbox of the approving manager, who approves or rejects the shopping
cart.
112
SAP_154-0.book Seite 113 Freitag, 1. Februar 2008 1:22 13
External
Assign Source of Supply
Requirement Sourcing
/Complete
from Backend Cockpit
Bidding/Auction process
System
Yes
A B
NO
Approval
Yes Workflow
Extended
1) Configuration settings in Define Classic ?
backend system for product
category No (Classic Scenario) SRM
Invoice
2) BADI BBP_DETERMINE_LOGSYS No Direct Yes
Material ?
B Approval
YES Workflow
Stock
1) Activate Extended Classic Exists?
Scenariosetting C Reservation
in backend
2) BADI BBP_EXTLOCALPO_BADI NO
Copy of PO
(BBP_ECS_PO_OUT_BADI)
Data Yes
C Complete ?
C
1)Configuration settings in Define
objects in backend system (Puch Purchase
No
req,reservations, purchase C Requisition
in Backend
Order in
Backend
orders)
2) BADI BBP_TARGET_OBJTYPE
1) Purchase Order and all follow-on documents are created in SRM system in local scenario
2) Purchase Order is created in backend system in classic scenario
3) Purchase Order is created in SRM in extended classic scenario and a copy is created in backend system.
4) Confirmations or Goods receipts and invoices can be created either in SRM or in backend system in classic & extended classic scenarios
113
SAP_154-0.book Seite 114 Freitag, 1. Februar 2008 1:22 13
tions in the BAdI are met, then the system processes the shopping cart as
described in the extended classic scenario.
7. 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.
114
SAP_154-0.book Seite 115 Freitag, 1. Februar 2008 1:22 13
Shopping cart Created in SAP SRM. Created in SAP SRM. Created in SAP SRM.
Shopping cart Done in SAP SRM. Done in SAP SRM. Done in SAP SRM.
approval
Approval of external Only approved pur- Only approved pur- Only approved pur-
requirements chase requisitions are chase requisitions are chase requisitions are
transferred from the transferred from the transferred from the
backend. No approval backend. No approval backend. No
in SAP SRM. in SAP SRM. approval in SAP SRM.
115
SAP_154-0.book Seite 116 Freitag, 1. Februar 2008 1:22 13
Purchase order Purchase order is cre- Purchase order is cre- Purchase order is cre-
creation ated in the backend ated in SAP SRM from ated in SAP SRM
system from the the shopping cart only.
shopping cart proc- process, from the
ess or from the sourc- sourcing process, or
ing process. directly from the
“Create purchase
order” transaction. A
copy is created in the
backend.
Purchase order Purchase order is Changes can be done Changes can be done
change maintained only in only in SAP SRM. only in SAP SRM.
the backend system.
Purchase order dis- Complete document Both SAP SRM and SAP SRM only.
play in the backend sys- the backend system.
tem and important
data in the shopping
cart follow-on docu-
ments.
Goods receipt or Backend system (can Backend system (can Confirmations are
service entry be entered as confir- be entered as confir- entered in SAP SRM
mation in SAP SRM mation in SAP SRM only.
also). also).
Invoice Backend system (can Backend system (can Entered in SAP SRM
be entered in SAP be entered in SAP only
SRM also). SRM also). (accounting docu-
ment is created in the
backend).
Use of SUS Use SUS with MM. Not supported fully. Use SUS with SAP
(Refer to Chapter 13). Refer to SAP Note SRM (refer to Chap-
543544. ter 14).
Use of account Not supported (See Not supported (See Not supported (See
assignment catego- SAP Note 586231). SAP Note 586231). SAP Note 586231).
ries with special
stocks in SAP ERP
116
SAP_154-0.book Seite 117 Freitag, 1. Februar 2008 1:22 13
Summary 4.7
Direct material procurement (requirement without account assignment i.e., order as direct
material)
Shopping cart Created in SAP SRM Created in SAP SRM Not applicable.
with ‘Order as Direct with ‘Order as Direct
material.’ material.’
Shopping cart Purchase order in SAP Purchase order in SAP Not applicable.
follow-on docu- SRM; purchase order SRM; purchase order
ments without copy is available in copy is available in
sourcing the backend system. the backend system.
Approval of external Only approved pur- Only approved pur- Not applicable.
requirements chase requisitions are chase requisitions are
transferred from the transferred from the
backend. No approval backend. No approval
in SAP SRM. in SAP SRM.
Purchase order Purchase order is cre- Purchase order is cre- Not applicable.
creation ated in SAP SRM. A ated in SAP SRM. A
copy is created in the copy is created in the
backend. backend.
Purchase order Purchase order can Purchase order can be Not applicable.
change be changed in SAP changed in SAP SRM
SRM only. only.
Use of SUS Not supported fully. Not supported fully. Not applicable.
Refer to SAP Note Refer to SAP Note
543544. 543544.
4.7 Summary
In this chapter, you learned that SAP SRM can be flexibly integrated with back-
end 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.
117
SAP_154-0.book Seite 118 Freitag, 1. Februar 2008 1:22 13
118
SAP_154-0.book Seite 505 Freitag, 1. Februar 2008 1:22 13
Index
505
SAP_154-0.book Seite 506 Freitag, 1. Februar 2008 1:22 13
Index
506
SAP_154-0.book Seite 507 Freitag, 1. Februar 2008 1:22 13
Index
E F
eClass 251 Factored- cost bidding 298
ECLViewer 451 Freight 154
Electronic Data Interchange (EDI) 197, Frequently Asked Questions (FAQs) 361,
355, 368 441
Electronic Request for Quotation/Proposal Full text search 337
(eRFx) 283 Function type 173
Email 201
Email integration 311
Enhancement framework 475 G
Enhancement spot
BBP_BDI_MAPPING_SAPXML1 471 GL account 160
Enrich product 252 Global contract 34
Enterprise Buyer Professional (EBP) 34, Global Outline Agreement (GOA) 166,
46, 48, 65, 426 331, 462
Enterprise Resource Planning (ERP) 29 Global spend analysis 432
Enterprise Services Architecture (ESA) Globalization 33
423 Goods receipt 106, 108, 111, 124, 360
EPRTRANS 192 Goods receipt (GR) notification 374
ERP 30 GR notification 360
ERS 370 Group condition 164
E- sourcing 331 GSVERF 371
Evaluated Receipt Settlement (ERS) 404
Evaluation ID 230
Event 229
H
Linkage 225, 237
HR 460
Schema 142, 346
Exception 200
Exchange rate 71 I
Exchange rate thresholds 336
Exits IDoc 359
ACCID001 219 ACC_GOODS_MOVEMENT02 215
BBPPC001 219 ACLPAY 219
CL_BBP_SMTP_INBOUND_INV 212 ACLPAY01 215
EXIT_SAPL2012_001 134 BBP_PCSTAT01 214, 218
EXIT_SAPL2012_002 134 STPPOD.DELVRY03 374
EXIT_SAPL2012_003 134 Import manager 252
EXIT_SAPL2012_004 134 Import server 252
EXIT_SAPLACC1_031 219 Inbound delivery 360
EXIT_SAPLEINM_002 374 Inbound mail 311
MCDOKZNR 170 India 447
MEREQ001 220 India localization 360
MM06E001 374 Indirect materials 37
MM06E005 220 Info record 289, 349
Expression 230 Initial upload 335
Expression of Interest (EOI) 293 Integrated call structure 274
Extended classic scenario 59, 104, 109, Integration Builder 269, 387, 428
134, 212 Integration directory 269, 387, 428
External requirement 185 Integration engine 266, 377, 408, 430
External web service 129, 263, 274 Integration Repository 270, 388, 428
Integration scenarios 269, 387
507
SAP_154-0.book Seite 508 Freitag, 1. Februar 2008 1:22 13
Index
508
SAP_154-0.book Seite 509 Freitag, 1. Februar 2008 1:22 13
Index
509
SAP_154-0.book Seite 510 Freitag, 1. Februar 2008 1:22 13
Index
UXS_ADD_MISSING_XSLT_NAME 312, S
456
W3_PUBLISH_SERVICES 78, 454 SAP Catalog Content Management (CCM)
Project Systems (PS) 192 250
Proxy 430 SAP CCM catalog 193
Proxy bidding 298 SAP ERP 6.0 253
PS 194 SAP NetWeaver 423
Purchase order 108, 128 Adobe Document Server (SAP NetWeaver
Purchase order response 111, 178 ADS) 67
Purchase request 32 Application Server (AS) 424
Purchase requisition 108, 128 Application Server (SAP NetWeaver AS)
Purchasing control 56 66
Purchasing group 86, 111 Business Intelligence (BI) 46
Purchasing organization 86, 111, 379 Business Intelligence (SAP NetWeaver BI)
66, 338, 361, 423
Exchange Infrastructure (SAP NetWeaver
Q XI) 171, 253, 359, 384, 423
Exchange Infrastructure (XI) 51, 66, 468
qRFC 460 Master Data Management (MDM) 55,
Quantity variance 180, 205 425
Questionnaire 307 Master Data Management (SAP
Queue 83 NetWeaver MDM) 250, 423
Quota arrangement 290 Portal 66
Text Retrieval and Information Extraction
(TREX) 66
R SAP NetWeaver BI 305
SAP NetWeaver MDM ports 259
Raw materials 38
SAP NetWeaver Portal 324, 363, 406, 424
Rebilling 473
SAP NetWeaver XI 338, 418
Region 88
SAP R/3 Plug- In 67
Register queues 266, 378, 409
SAP SRM Server 65
Rejection 147
SAP Web Dispatcher 69, 406
Remote Function Call (RFC) 67
SAP xApp Contract Life Cycle Management
Replication 81
(xCLM) 52
Report
SAPSLDAPI 265, 377
/SAPSRM/WF_CFG_ANALYSIS_001 247
Scheduling agreement 360
Repository 251, 257
Search User Interface (UI) 277
Repository schema 261
Self- registration 375
Repository structure 261
Self- service procurement 48, 120, 123
Request for Information (RFI) 47, 293
Service 82
Request for Proposal (RFP) 47, 293
Category 82
Request for Quotation (RFQ) 32, 47, 293
Order 473
Reservation 107, 127
Procurement 49, 120
Responsible agent 230
Shared services model 197
Return delivery 147, 176, 360
Shop on behalf of 91
Reverse auction 46, 66, 283
Shopping cart 107, 123
Reviewer 242
Simplified pricing 161
RFC destination 74, 265, 364, 376, 377,
Single sign on (SSO) 424, 459
407
Site 79
RFC user 73
Slave repository 263
Role 72, 375
SLD 409
SAP_EC_BBP_ACCOUNTANT 205
SmartForm 167
Z_IMS_ROLE 211
BBP_BIDINV_BID 305
510
SAP_154-0.book Seite 511 Freitag, 1. Februar 2008 1:22 13
Index
511
SAP_154-0.book Seite 512 Freitag, 1. Februar 2008 1:22 13
Index
512