SAP Certified Application Associate - Supplier ... · Bonn Boston Bryan Bee SAP Certified Application Associate — Supplier Relationship Management with SAP SRM 5.0 272.book Seite

Bonn � Boston

Bryan Bee

SAP Certified Application Associate — Supplier Relationship Management with SAP SRM 5.0

272.book Seite 3 Mittwoch, 6. Mai 2009 1:47 13

Contents at a Glance

PART I General Introduction

1 SAP Global SRM Application Certification Track — Overview ...................... 27

2 SRM Courses and Experience ...................................................................... 41

PART II Exam Preparation

3 SAP SRM Implementation Scenarios and ERP Integration ............................. 49

4 SAP SRM Landscape Concept ...................................................................... 71

5 Business Value of SAP SRM ......................................................................... 87

6 Self-Service Procurement — Processes ......................................................... 103

7 Service Procurement — Processes ............................................................... 131

8 Plan-Driven Procurement — Processes ........................................................ 145

9 Sourcing — Processes .................................................................................. 159

10 SAP Bidding Engine and Auction Processes .................................................. 179

11 SAP Supplier Self-Services — Processes ....................................................... 205

12 SAP SRM Catalog Concept Plus SRM-MDM and SAP CCM Basics ................ 225

13 SAP SRM Server Contract Management ....................................................... 243

14 SAP E-Sourcing and SAP CLM ...................................................................... 261

15 System Communication RFC, ALE, Number Ranges, and Documents Types ........................................................................................ 285

16 Organizational Structure and User Management .......................................... 301

17 Workflow Implementation and Features ...................................................... 323

18 Master Data Synchronization ....................................................................... 349

19 Connecting OCI Catalogs ............................................................................. 369

20 Scenario Determination ............................................................................... 389

21 Possibilities of Sourcing Transactions and How to Configure Them .............. 401

22 Bidding with Weighting ............................................................................... 415

23 Monitoring Documents ............................................................................... 431

24 Accounting and ERP Integration .................................................................. 447

25 Business Add-In Concepts ........................................................................... 463

26 SAP NetWeaver MDM Catalog Repositories and Technology ....................... 477

27 Upload of Different Files and Mapping in the MDM Import Manager .......... 497

28 Manage Data in MDM Data Manager and Utilize Workflow ........................ 517

29 SAP NetWeaver MDM Web User Interface Configuration and OCI Interface .............................................................................................. 535


7

Contents

Acknowledgments ......................................................................................... 17Preface .......................................................................................................... 19

PART I: General Introduction

1 SAP Global SRM Application Certification Track — Overview ................................................................................... 27

Certification Objectives and Benefits ............................................................. 28Certification Improvements ........................................................................... 29Becoming an SAP Certified Application Associate — SRM 5.0 ....................... 31

SAP SRM Associate Defined ...................................................................... 32SAP SRM Associate Exam Structure ........................................................... 33

Becoming an SAP Certified Application Professional or Master — SRM 5.0 ... 35SAP SRM Professional Defined .................................................................. 36SAP SRM Master Defined ......................................................................... 37SAP SRM Master and Professional Exam Structure .................................... 37

Summary ....................................................................................................... 40

2 SRM Courses and Experience ................................................... 41

SAP SRM Training Courses ............................................................................ 42Experience Expectation ................................................................................. 44Additional Sources of Information ................................................................. 45Summary ....................................................................................................... 46

PART II: Exam Preparation

3 SAP SRM Implementation Scenarios and ERP Integration ...... 49

Objectives of this Portion of the Test ............................................................ 51Key Concept Refresher .................................................................................. 52

Stand-Alone Scenario ................................................................................ 52Classic Scenario ......................................................................................... 54Extended Classic Scenario ......................................................................... 55Decoupled Scenario .................................................................................. 57SAP SRM and ERP Integration .................................................................. 59


Contents8

Practice Questions ......................................................................................... 64Practice Question Answers and Explanations ................................................. 66Take Away ..................................................................................................... 67

Tips ........................................................................................................... 69Summary ....................................................................................................... 70

4 SAP SRM Landscape Concept ................................................... 71

Objectives of this Portion of the Test ............................................................. 73Key Concepts Refresher ................................................................................. 73

SAP SRM Component Overview ................................................................ 73SRM Components per Business Scenario ................................................... 76


Tips ........................................................................................................... 85Summary ....................................................................................................... 85

5 Business Value of SAP SRM ...................................................... 87


Benefits of SAP SRM ................................................................................. 89SAP SRM Value Chain and Common Issues ............................................... 94


Tips ........................................................................................................... 101Summary ....................................................................................................... 101

6 Self-Service Procurement — Processes .................................... 103

Objectives of This Portion of the Test ............................................................ 105Key Concepts Refresher ................................................................................. 105

Shopping Cart Process ............................................................................... 105Direct Procurement ................................................................................... 113Confirmation of Goods Receipt .................................................................. 115Invoice Processing ..................................................................................... 117Procurement Card Integration ................................................................... 120

Practice Questions ......................................................................................... 124


Contents 9

Practice Question Answers and Explanations ................................................. 126Take Away .................................................................................................... 127

Tips .......................................................................................................... 129Summary ....................................................................................................... 129

7 Service Procurement — Processes ........................................... 131


Shopping Carts with Services .................................................................... 133Requests for External Staff ........................................................................ 136

Practice Questions ........................................................................................ 139Practice Question Answers and Explanations ................................................. 141Take Away .................................................................................................... 142

Tips .......................................................................................................... 143Summary ....................................................................................................... 143

8 Plan-Driven Procurement — Processes .................................... 145


Plan-Driven Procurement Overview .......................................................... 147Selection of Requirements to Transfer ....................................................... 150Plan-Driven Procurement Organizational Model Impact ............................ 152


Tips .......................................................................................................... 157Summary ....................................................................................................... 158

9 Sourcing — Processes ............................................................... 159


Sources of Supply ..................................................................................... 161Process Purchase Order ............................................................................ 163Sourcing Application ................................................................................. 166Vendor Evaluation .................................................................................... 169

Practice Questions ........................................................................................ 173Practice Question Answers and Explanations ................................................. 174


Contents10

Take Away ..................................................................................................... 175Tips ........................................................................................................... 177

Summary ....................................................................................................... 177

10 SAP Bidding Engine and Auction Processes ............................. 179


Bidding Process Overview ......................................................................... 181Auction Detail Overview ........................................................................... 189Supplier Interaction ................................................................................... 194


Tips ........................................................................................................... 203Summary ....................................................................................................... 203

11 SAP Supplier Self-Services — Processes ................................... 205


SAP SUS Scenarios ..................................................................................... 207Supplier Registration ................................................................................. 213SAP SUS Concept Refresher ....................................................................... 215


Tips ........................................................................................................... 222Summary ....................................................................................................... 223

12 SAP SRM Catalog Concept Plus SRM-MDM and SAP CCM Basics ........................................................................ 225


SRM Catalog Overview .............................................................................. 227SAP SRM-MDM Basics .............................................................................. 229SAP CCM Basics ........................................................................................ 233

Practice Questions ......................................................................................... 238Practice Question Answers and Explanations ................................................. 239


Contents 11

Take Away .................................................................................................... 240Tips .......................................................................................................... 242

Summary ....................................................................................................... 242

13 SAP SRM Server Contract Management .................................. 243

Objectives of this Portion of the Test ............................................................ 245Key Concepts Refresher ................................................................................. 245

SAP SRM Server Contract Basics ............................................................... 245SRM Server Contract Extended Functionality ............................................ 254


Tips .......................................................................................................... 260Summary ....................................................................................................... 260

14 SAP E-Sourcing and SAP CLM .................................................. 261


SAP E-Sourcing Basic Concepts ................................................................. 264Workbench ............................................................................................... 266SAP E-Sourcing Supplier Management ...................................................... 267SAP E-Sourcing Project Management ........................................................ 269SAP E-Sourcing RFx .................................................................................. 269SAP E-Sourcing Auctions ........................................................................... 271Contracts .................................................................................................. 272SAP E-Sourcing and SAP CLM Integration with SAP ERP Overview ........... 275


Tips .......................................................................................................... 282Summary ....................................................................................................... 282

15 System Communication RFC, ALE, Number Ranges, and Documents Types .............................................................. 285


SRM Basic Settings .................................................................................... 287Practice Questions ........................................................................................ 296


Contents12

Practice Question Answers and Explanations ................................................. 298Take Away ..................................................................................................... 299

Tips ........................................................................................................... 300Summary ....................................................................................................... 300

16 Organizational Structure and User Management .................... 301


Organizational Structure Basics .................................................................. 303Organizational Structure Inheritance and Maintenance .............................. 307Detailed Look at Organizational Structure ................................................. 309Attribute Details ........................................................................................ 313


Tips ........................................................................................................... 321Summary ....................................................................................................... 322

17 Workflow Implementation and Features ................................. 323


Workflow Basics ........................................................................................ 326Workflow Customizing .............................................................................. 327Workflow Extended Functionality .............................................................. 330Delivered Workflow Overview ................................................................... 334Important Terminology and Definitions to Remember ............................... 340


Tips ........................................................................................................... 346Summary ....................................................................................................... 346

18 Master Data Synchronization ................................................... 349


Master Data Basics .................................................................................... 351Vendor Master and Replication ................................................................. 352


Contents 13

Middleware and Material Master Replication ............................................ 357Other Procurement Master Data ............................................................... 360


Tips .......................................................................................................... 367Summary ....................................................................................................... 367

19 Connecting OCI Catalogs ......................................................... 369


OCI Basics ................................................................................................. 371Catalog-Specific Information ..................................................................... 379


Tips .......................................................................................................... 386Summary ....................................................................................................... 387

20 Scenario Determination ............................................................ 389


Scenario Determination Overview ............................................................. 391Practice Questions ........................................................................................ 395Practice Question Answers and Explanations ................................................. 396Take Away .................................................................................................... 397

Tips .......................................................................................................... 398Summary ....................................................................................................... 399

21 Possibilities of Sourcing Transactions and How to Configure Them ........................................................................ 401


Sourcing Transaction Basics ....................................................................... 403Sourcing Configuration Considerations ...................................................... 406

Practice Questions ........................................................................................ 410Practice Question Answers and Explanations ................................................. 411


Contents14

Take Away ..................................................................................................... 412Tips ........................................................................................................... 413

Summary ....................................................................................................... 414

22 Bidding with Weighting ........................................................... 415


Dynamic Attributes and Standard Fields .................................................... 417Weighting and Valuation Factor Basics ...................................................... 420


Tips ........................................................................................................... 429Summary ....................................................................................................... 429

23 Monitoring Documents ............................................................. 431


Methods to Monitor Documents ............................................................... 433Troubleshooting ........................................................................................ 438


Tips ........................................................................................................... 446Summary ....................................................................................................... 446

24 Accounting and ERP Integration .............................................. 447


Account Assignment Category Basics ......................................................... 449General Ledger Basics ................................................................................ 453Account Validation .................................................................................... 454


Tips ........................................................................................................... 461Summary ....................................................................................................... 462


Contents 15

25 Business Add-In Concepts ........................................................ 463


Business Add-In Basics .............................................................................. 465BAdI Example ........................................................................................... 469


Tips .......................................................................................................... 475Summary ....................................................................................................... 475

26 SAP NetWeaver MDM Catalog Repositories and Technology ................................................................................ 477

Techniques You’ll Master: ............................................................................. 477Objectives of this Portion of the Test ............................................................ 478Key Concepts Refresher ................................................................................. 479

MDM Catalog Console Basics ................................................................... 479MDM Catalog Repository ......................................................................... 483SAP NetWeaver MDM Catalog Security .................................................... 488


Tips .......................................................................................................... 494Summary ....................................................................................................... 495

27 Upload of Different Files and Mapping in the MDM Import Manager .................................................................................... 497


MDM Import Manager Basics ................................................................... 499MDM Import Manager Mapping and Import Features .............................. 504


Tips .......................................................................................................... 515Summary ....................................................................................................... 515


Contents16

28 Manage Data in MDM Data Manager and Utilize Workflow .................................................................................. 517


MDM Data Manager Basics ....................................................................... 519MDM Data Manager Record Comparison .................................................. 521Check In/Out Functionality ........................................................................ 522Masks and Named Searches ...................................................................... 524Validations and Workflow ......................................................................... 525MDM Data Manager Feature Highlights .................................................... 526


Tips ........................................................................................................... 533Summary ....................................................................................................... 533

29 SAP NetWeaver MDM Web User Interface Configuration and OCI Interface ...................................................................... 535


MDM Web User Interface Basics ............................................................... 537Open Catalog Interface Configuration ........................................................ 543


Tips ........................................................................................................... 549Summary ....................................................................................................... 549

The Author .................................................................................................... 551

Index ............................................................................................................. 553


Chapter 2SRM Courses and Experience

Techniques You’ll Master:

� Training courses available for SAP SRM

� Online knowledge products available for SAP SRM

� The level of experience expected and how it is acquired

� Insight into additional information sources to help you prepare for the exam


Chapter 2 SRM Courses and Experience42

You should have a good understanding of the different levels of certificationoffered for SAP SRM. We’ve covered the definitions and defined the differentlevels in terms of expectations and capabilities in previous chapters. In this chap-ter, we’ll cover the courses available for SAP SRM and provide you with someinsight into what you can expect for the certification exams. It’s important foryou to understand that a two-prong approach is needed for success in certifica-tion, regardless of certification level. The approach must consist of factual con-cepts realized in training combined with real-world application with hands-onexperience.

SAP SRM Training CoursesSAP Education offers several training classes that create a foundation for anySRM professional seeking certification. The training classes give you the abilityto cover concepts, and many also allow you to carry out exercises to apply thoseconcepts. Let’s review the current SAP SRM training courses available:

� SAP Overview (SAP01)Intended for those new to SAP. The course gives an overview of SAP solutionsand introduces you to SAP terminology.

� SAP Procure-to-Pay (SAP210)Intended for those new to SAP. The course gives you foundational under-standing of procurement concepts and processing in SAP.

� SAP SRM E-Sourcing OverviewIntended for those new to SAP E-Sourcing. The course gives a detailed viewof SAP E-Sourcing and its functionality.

� SAP SRM Overview (SAPSRM)Intended for those new to SAP SRM. The course presents an overview of theSAP SRM solution, components, and functionality.

� SAP SRM Configuration (SRM210)Intended for users who will set up SAP SRM systems. The course coversdetails required to configure an SAP SRM system and allows you to carry outhands-on configuration.

� SAP SRM CCM (SRM260)Intended for users implementing SAP Catalog Content Management (CCM).The course reviews the SAP CCM landscape, integration, and setup to workwith SAP SRM.


SAP SRM Training Courses Chapter 2 43

� SAP SRM-MDM Catalog (SRM270)Intended for user who will set up the SRM master data management (SRM-MDM) catalog. The course reviews the components, setup, and maintenancerequired to manage internal catalogs.

In addition to classroom training courses, SAP Education offers classes with allof the materials available online and accessed at your own pace. These are calledOnline Knowledge Products (OKPs), and the lesson maps are often divided byrole. For example, a learning map may be for a solution or technical role. Theseare often used for delta functionality lessons between the different versions. Youmay think the older versions are not valid for you, but these OKPs often havevery helpful information. If we had to select only one, then of course we wouldrecommend the one for SAP SRM 5.0. The current OKP courses available at thetime of writing this book include:

� OKP SRM 3.0 (OSR30S)Delta functionality and knowledge base for SAP SRM 3.0.




� OKP E-Sourcing 4.2 (OES42)Delta functionality and knowledge base for SAP E-Sourcing 4.2.

We’ve covered the training curriculum offered by SAP Education, and as you cansee, several exist if you need to sharpen your skills in any of the areas available.Training is only one input into the certification exams; level of experience is justas important, especially for the professional level and above. We’ll cover someinsights into the level of experience in the next section.

Note

SAP SRM 6.0 had a limited release and was not available to all customers. Somefunctionality developed for SAP SRM 6.0 will carry over to the next planned gen-eral release, SAP SRM 7.0, when it’s available.



Experience ExpectationYou can participate in the training courses and have the concepts down, but youstill need to apply these to be successful at certification. The Associate level examprimarily covers training content, but it also includes application of conceptsrealized via experience. Figure 2.1 illustrates the sequence of the different levelsand summarizes the target experience for each level.

The expected experience includes exposure to the different components of SAPSRM in different implementation cycles. As you begin your SAP SRM journey,you typically focus in a single area, such as SAP Enterprise Buyer (EB) self-serviceprocurement. You may participate in different parts of the implementation cycle

Caution

For the most current listings of the SAP SRM curriculum, please check http://www.sap.com/education. In addition, for details related to OKPs you can accesshttp://services.sap.com/okp.

Figure 2.1 Certification Track Experience Summary

Master7-10 years of experience

Professional3-7 years of experience

Associate1-3 years of experience


Additional Sources of Information Chapter 2 45

such as blueprint or realization, but you don’t benefit from a full lifecycle imple-mentation yet. As you become more experienced, you are involved with moreSAP SRM components and exposed to more lifecycle stages. Eventually, you willrack up the full lifecycle experience. This is important because you see the com-plete view from design to go live. Eventually, you’ll have seen and done it manytimes, to the point where you can strategize and recommend solutions to com-plex issues. You move up the path shown in Figure 2.1.

Additional Sources of InformationThis certification success guide covers the key concepts and acts as a refresher foryou to prepare for the exams. It’s not an exhaustive list of all the information cov-ered in the exams, so in this section we’ll try to give you additional sources out-side of training that can help you prepare for the exam.

� SAP HelpThis sounds simple enough. How many times have you been told or toldsomeone else to check out SAP Help? Well, it’s still valid. You can access SAPHelp via http://help.sap.com. There are no quick links, but drill down via SAP

Business Suite � SRM and select the applicable version.

� SAP Development Network (SDN)The SDN is a community of users across SAP solutions. It includes blogs,white papers, discussion boards, and a host of information. This is a goodresource for problem solving and preparing for the exam, especially for topicsyou are less familiar with. You can access the SDN via https://www.sdn.sap.com/irj/sdn.

� SAP Service MarketplaceThe SAP Service Marketplace is a vast knowledge resource with informationavailable in many different areas for SAP SRM from install guides to scenarioguides to support notes. The Service Marketplace requires IDs to access thisinformation, but all SAP customers and partners have access to this resource.You can access the Service Marketplace via http://service.sap.com.

Tip

It is important, regardless of your level of expertise, that you stay current on dif-ferent versions. This is why the recertification process is so important. Once cer-tified, you need to continue to hone your skills relating to SAP SRM.



� SAP Education CertificationThis is the formal location of resource information related to SAP certifi-cation. You can find sample questions and exam breakdowns here. You canalso register to take the exam from this site. You can access this resource viahttp://www.sap.com/certification.

� SAP PressSAP PRESS has several other SAP books that have useful information on dif-ferent themes or organizations, such as The Consultant’s Guide to SAP SRM.These books can be found at www.sap-press.com.

SummaryIn this chapter, we’ve explained the different training courses available for SAPSRM from SAP Education. We’ve also covered the experience expectations foryou at each certification level. The classroom training and the online knowledgeproducts are invaluable for certification, but as you move up the certification lev-els, the real-world project experience you need in order to pass the examincreases. To help you prepare for the exam, we have also listed additionalresources for SAP SRM information. The information from this success guidecombined with these resources should cover any SAP SRM topic. The next chap-ter begins the second part of the book, where we’ll dive into the key concepts ofthe different exam topics. Let’s get started.


Part IIExam Preparation


Chapter 3SAP SRM Implementation Scenarios and ERP Integration

Techniques You’ll Master:

� Classic, extended classic, and stand-alone implementation sce-narios

� Document flow for each SAP SRM implementation scenario

� Implementation scenario determination criteria

� RFC, ALE, and XML communication method basics

� OCI, OPI, and ITS communication methods and their uses

� BAPI® abstraction layer communication and its components


Chapter 3 SAP SRM Implementation Scenarios and ERP Integration50

As you may know, a company’s software landscape is normally heterogeneousand contains many different systems to support its business. You can integrateSAP SRM with SAP and non-SAP systems based on different implementationoptions, allowing for flexibility in your company’s business process. When youimplement SAP SRM, the integration scenarios impact functionality and how thesystem functions overall.

Typically, the most common difference referenced between SAP SRM implemen-tation scenarios is where the leading purchase order resides, such as in the SAPSRM system or the backend enterprise resource planning (ERP) system.Although this is the primary difference from an abstract view, the integrationscenario can impact many different aspects, from source-of-supply determina-tion to master data synchronization.

The implementation scenario is typically one of the first decisions you mustmake during an SAP SRM implementation. There are driving factors that can beconsidered, but only in conjunction with your customer’s specific businessrequirements. This chapter reviews the following implementation scenarios:

� Stand-alone scenarioAll procurement documents are created locally in the SAP SRM system. SAPSRM is the leading system for procurement documents.

� Classic scenarioThe shopping cart is created locally, but the backend ERP system is the lead-ing system where follow-up procurement documents such as purchase ordersare created.

� Extended classic scenarioThe shopping cart is created locally and must be complete before a copy ofthe purchase order is transferred to the backend ERP system. SAP SRM is theleading system.

� DecoupledThis isn’t officially a scenario. It’s essentially a hybrid of the other three sce-narios, for example, when classic and standalone exist at the same time.

Regardless of the implementation scenario, SAP SRM must integrate into a back-end system. Some scenarios have more integration points than others, but eventhe stand-alone scenario requires a financial or accounting backend systembecause SAP SRM itself does not carry out the functions of a financial system.

Because SAP SRM requires integration into different systems, it must establish acommon set of integration points. It’s well known that SAP offers several com-


Objectives of this Portion of the Test Chapter 3 51

munication methods, including Application Link Enabling (ALE), Remote Func-tion Call (RFC), Extensible Markup Language (XML), and Business ProgrammingApplication Interface (BAPI). You’ll use all of these methods in SAP SRM depend-ing on the context of the business process and data being transmitted. It’s impor-tant to understand the integration methods and how SAP SRM uses them.

Real-World Scenario

You’re starting a new project as an SAP SRM Associate supporting yourclient’s sourcing process. Your client is planning on improving their pro-curement process powered by SAP SRM. You attended the first blueprintkick-off meeting last week, and you and your team are getting organized tobegin the project. The client is excited after seeing the great sales presenta-tions about functionality that and how SAP SRM will benefit their pro-cesses.

Everyone understands that their team’s initial tasks during the blueprintphase pertain to requirement gathering and defining current processes.You assist where needed. As the legacy processes and systems are defined,you begin to be asked questions about how SAP SRM functionality worksfor different scenarios. You’re unable to answer the questions satisfactorilybecause you must preface each answer with the statement, “It depends onthe implementation scenario.” You then explain each case.

The solution is to evaluate the information you currently have regardingyour client’s scope and context for existing systems and processes. A bigclue, for example, is if they already have an established SAP procurementsystem using SAP Materials Management. You should also cross-referencethe main value-driver and requirements for the project to develop a deci-sion matrix on which implementation scenarios best fits their need.Requirements may point to different scenarios, but you must make a deci-sion before you can move forward from the blueprint phase.

Objectives of this Portion of the TestThis section of the exam tests your knowledge of the implementation scenariosand the SAP SRM integration points with an ERP system. The objectives are foryou to be able to:



� Understand the possible implementation options available in SAP SRM

� Explain the major considerations when selecting an implementation scenario

� Explain the different integration points between SAP SRM and an ERP system

Key Concept RefresherThis section contains the actual refresher content, and is broken down into topicareas. We’ll list the key concepts that the exam will require you to know for thischapter content. You’ll learn concepts, terminology, and definitions for eachtopic area. At the end of this section, we’ll summarize important terminologyand key definitions as a refresher, rather than reviewing each topic area.

Stand-Alone Scenario

The stand-alone system is typically what you would consider when the customerhas not implemented the Materials Management component in their SAP ERPsystem, and wants all procurement processing conducted in SAP SRM. You mustconnect SAP SRM to a backend system for the accounting and postings related tothe vendor invoices entered in SAP SRM. When you implement the stand-alonescenario, SAP SRM is the leading system where the purchase order resides, sothis is where buyers conduct their work. The major integration points to thebackend system relate to master data, financial data, and invoice posting. Thestand-alone scenario is determined based on product category configuration. Ifyou require other criteria for control beyond a product category, then a BAdImust be used.

This scenario, and all scenarios described, will be discussed in terms of the mainprocurement documents, such as the shopping cart, purchase requisition, pur-chase order, confirmation, and invoice.

In the stand-alone scenario, product masters and vendors must exist in SAP SRM.This is common to all scenarios, but the sources of supplies that are considered

Tip

With SAP Supplier Self-Services (SUS), you have complete supplier involvementin the stand-alone scenario for all of your operational procurement scenarios.


Key Concept Refresher Chapter 3 53

are also local to SAP SRM and include local contracts and product interlinkages.An interlinkage is a relationship in SAP SRM between a vendor and a productused to specify a price.

The steps in the common stand-alone process are explained as follows and illus-trated in Figure 3.1.

1. A shopping cart is created.

2. Source determination occurs locally in SAP SRM.

3. The approval process takes place in SAP SRM.

4. After approval, the purchase order is either complete or must be processedby the buyer until it is complete.

5. Once the purchase order is complete, a financial commitment posting is madein the backend. The purchase order is sent to the vendor from the SAP SRMsystem.

6. The confirmation is entered directly in SAP SRM.

7. The invoice is entered directly in SAP SRM and results in the financial postingin the financial backend.

Figure 3.1 Stand-Alone Scenario

Create Shopping Cart

Workflow Approval

Purchase OrderComplete/Incomplete

SAP SRM

Shopping Cart Local Source Determination

Commitment Document

SAP or Non-SAPBackend

Confirmation

InvoicePosting to FI

Global BusinessPartner

ProductMaster

Contract

Inter-linkage

Invoice

Message to Vendor

(XML, email, fax)



Classic Scenario

The classic scenario is what you would typically consider for customers who havealready implemented the Materials Management component in their backendSAP ERP system. This scenario relies strongly on the SAP ERP backend systembecause all Materials Management documents (such as purchase orders, goodsreceipts, service entry sheets, and invoices) are located there. The leading pro-curement system is the SAP ERP backend. The majority of the buyer’s work, suchas processing purchase orders, will be done in SAP ERP. This option is popularamong experienced SAP customers who are adding SAP SRM after an SAP ERPimplementation that has already been completed. The classic scenario is deter-mined based on product category configuration. If you require other criteria forcontrol beyond a product category, then a BAdI must be used.

If the customer already has an established SAP ERP backend and does not wantto transition their procurement processes to a new system, the classic scenariobecomes more plausible because they can leverage their existing process.

You may also consider if the customer wants to leverage existing technical inter-faces or infrastructure for activities related only to SAP ERP. For example, if acustomer has complex electronic data interchange and data exchange set up intheir SAP ERP system, then you’ll have to consider these during the scenarioevaluation.

The steps in the common classic scenario process are described as follows andillustrated in Figure 3.2.


2. Source determination may be done in SAP SRM via catalogs or remotelybased on data in the backend ERP system, such as purchasing informationrecords or ERP contracts.

3. The approval process for shopping carts takes place in SAP SRM.

4. After approval, the follow-up document is created. The follow-up documentcan be a purchase requisition, purchase order, or even a reservation in thebackend ERP system based on the customizing setup.

Caution

Only partial functionality is available with SAP SUS in the classic scenario. Busi-ness scenarios for buying materials are supported, but services are not supportedfor the full service procurement scenario.



5. Once the purchase order is created either directly or after a purchase requisi-tion is converted, it is sent to the vendor from the ERP system.

6. The confirmation can be entered directly in SAP SRM or the ERP system.Either way, the goods receipt document (material document) will exist in thebackend ERP system.

7. The invoice can be entered directly in SAP SRM or the ERP system. Eitherway, the invoice receipt document (invoice document) will exist in the back-end ERP system.

Extended Classic Scenario

The extended classic scenario is an extension of the classic scenario, and is gearedtoward customers who want to leverage their ERP backend system and takeadvantage of SAP SRM procurement functionality. In the extended classic sce-nario, the procurement process takes place locally in SAP SRM, and the resultingpurchase order is replicated to the backend system. You may consider this sce-nario for customers who want to take advantage of the sourcing capabilities in

Figure 3.2 Classic Scenario


Workflow Approval

Confirmation

SAP SRM

Shopping Cart Source

Determination

Purchase Order

Confirmation


Purchase Requisition

Invoice Invoice

Contract Info Record


ProductMaster

Message to Vendor

(XML, email, fax)



SAP SRM and at the same time want to leverage the direct material capabilitiesin the backend ERP system. You activate the extended classic scenario in custom-izing, which results in all items following this scenario. If you want certain itemsto follow the extended classic scenario, then a BAdI must be used as described inthe next section, Decoupled Scenario.

If the data in the shopping cart is not complete, it must be completed manuallyin SAP SRM before it’s transferred to the backend system as a purchase order.The purchase order in SAP SRM is the leading purchase order. The complete pur-chase order is replicated to the backend as a read-only copy, and then it providesthe data needed for the creation of goods receipts, service entry sheets, andinvoices in the backend system. Similar to the classic scenario, the goods or ser-vice receipt can be done in either SAP SRM or the backend ERP system.

The steps in the common extended classic scenario process are listed below andshown in Figure 3.3.


2. Source determination occurs locally in SAP SRM.

3. The approval process takes place in SAP SRM.

4. After approval, the purchase order is created locally in SAP SRM. If the datain the purchase order is not complete, it must be completed manually in SAPSRM before a copy is transferred to the backend system. Once the purchaseorder is complete, it’s sent to the vendor from the SAP SRM system.

5. The confirmation can be entered directly in SAP SRM or the ERP system.Either way, the goods receipt document (material document) will exist in thebackend ERP system.

6. The invoice can be entered directly in SAP SRM or the ERP system. Eitherway, the invoice receipt document (invoice document) will exist in the back-end ERP system.

Caution

With SAP SUS, you have partial supplier involvement for your operational pro-curement scenarios. For the extended classic scenario, you have supplier involve-ment for the purchase order and the purchase order response. See SAP Note543544 for more information.



Decoupled Scenario

The decoupled scenario is not officially a scenario like the classic, extended clas-sic, and stand-alone scenarios. The decoupled scenario represents a hybridimplementation of more than one scenario. This is common if some materials areto be purchased one way and others a different way. For example, you may haveimplemented the classic scenario but want to add Pcard functionality. BecauseSAP SRM 5.0 only supports Pcard in the stand-alone scenario, you can have selectsome commodities such as office supplies to follow the stand-alone scenariowhile the others continue to follow the classic scenario. Other examples includethe difference in services versus nonservices.

Usually, the previous scenarios apply here, but depending on the setup they canoccur at the same time. The conditional logic for the classic and standalone sce-narios is based on the product category. For example, product category A can beexecuted in the stand-alone scenario, whereas product category B is executed inthe classic scenario, as shown in Figure 3.4.

Figure 3.3 Extended Classic Scenario


Workflow Approval


SAP SRM

Shopping Cart Local Source Determination

Purchase Order

Confirmation


Confirmation

Invoice


ProductMaster

Contract

Inter-linkage

Invoice

Message to Vendor

(XML, email, fax)



Note

Product category is generally used as the deciding factor for the decoupled sce-nario, but a BAdI, BBP_DETERMINE_LOGYS, exists to implement customer-spe-cific rules.

Figure 3.4 Decoupled Scenario



SAP SRMSAP or Non-SAP

Backend

ConfirmationBusinessPartner

ProductMaster

Contract

Inter-linkage

Invoice

Message to Vendor

(XML, email, fax)

Contract Info Record

Workflow Approval

LocalPurchase Order

Confirmation

Purchase Requisition

Invoice

Product Category

Message to Vendor

(XML, email, fax)

Product Category

Local Backend

Backend

Tip

SAP ERP 6.0 as a backend provides a SRM ERP with one client installation. Theone client targets customers who do not currently use an SAP SRM and onlyhave one backend SAP ERP system. The goal is to have a simple procurementscenario, minimum SAP SRM installation, and lower total cost of ownership. Dif-ferences exist related to master data and processes including limitations. Formore details, you can reference SAP Note 963000.



SAP SRM and ERP Integration

The previous sections have explained the different implementation scenariosand described different points where communication occurs between SAP SRMand the SAP or non-SAP ERP backend. In this section, we’ll discuss the details forthe actual communication methods and point out the key concepts you mustunderstand for the exam.

SAP SRM integration is a direct result of procurement processes being carried outacross multiple systems. Each time a task is processed in SAP SRM that requiresERP or backend interaction, communication is needed between the systems. Theintegration points can be classified in the following main categories:

� Master dataIncludes master data that is replicated from connected backend systems suchas vendor or product masters.

� Configuration elementsIncludes configuration elements such as purchasing groups or general ledgeraccounts that refer to data in a connected backend system.

� Transactional dataIncludes data or processes carried out via a transaction such as a purchaseorder or shopping cart.

SAP Enterprise Buyer can connect to multiple ERP backend systems. This is veryuseful for companies that are looking for purchasing functions to cross multipleprocurement systems. SAP SRM can communicate and coordinate across variousinstances. The communication methods that make this possible can be classifiedin the following categories:

� Application Link Enabling (ALE)Communication between logical systems that can be SAP or non-SAP. ALE isbased on distribution models exchanging intermediate documents (IDocs).An IDoc is essentially a specific data file that both systems know how to inter-pret. Many IDoc types exist, but in SAP SRM you’ll mostly see the following:

� BBPIV — SRM invoice

� BBPCO — Commitment posting

� MBGMCR — Posting of goods movement

� HRMD_ABA — HR organization plan data

� ACLPAY — Accounting postings related to procurement cards



� ACC_GOODS_MOVEMENT — Post goods movement used with procure-ment cards

� Remote Function Call (RFC)Communication when one system calls a function module in a partner sys-tem. The call results are passed back to the calling system. Too many functionmodules exist to list, but this is the primary communication method. EvenALE at its core uses an inbound and outbound RFC call to post the IDocs.

� Extensible Markup Language (XML)Web Service communication that can be used to exchange information. XMLmessages typically require SAP NetWeaver® Process Integration (PI) or mid-dleware layer.

The following documents in SAP SRM can be sent via XML:

� Purchase order and purchase order response

� Confirmation and confirmation response

� Invoice and invoice response

� Bid invitation and bid response

Other communication methods exist that differ from RFC, ALE, and XMLbecause they are focused on a specific function within SAP SRM, whereas theothers are generic communication methods across connected backends. They arestill communication protocols and are included for reference so you can under-stand the integration points available. Details are listed below including theirparticular function:

� Open Catalog Interface (OCI)Communication between SAP Enterprise Buyer and internal or external cata-log systems. OCI enables products and services to be transferred from SAPcatalogs such as SRM-MDM and SAP CCM or any third party OCI-enabled cat-alog.

� Open Partner Interface (OPI)Communication method that allows vendor data do be passed in a similarfashion as the OCI catalog data back to SAP SRM for strategic procurement.

� Internet Transaction Server (ITS)Converts SAP GUI to HTML format via templates to enable Internet users toaccess transaction and functionality.



The different communication methods demonstrate the architectural flexibilitybetween SAP and non-SAP systems. The communication methods are illustratedin Figure 3.5.

ALE, RFC, and XML can call different BAPIs depending on the release level of thebackend system. The abstraction layer encapsulates the BAPI calls in the backendsystem by using the following components:

� DispatcherThe dispatcher is a function module that analyzes the customizing settingsand knows the backend system type and release, and determines the functionmodule that should be called.

� DriverFor each release level, there is a driver module that calls BAPIs in the backendsystem.

� SpoolerThe spooler controls the transfer of documents from SAP SRM to the backendsystem. If an error occurs, the spooler checks the backend and tries to resendthe information at regular intervals based on customizing settings.

Figure 3.5 Communication Methods

XML Messages

SAP Backend

(Release 3.1H or Higher)

Non-SAP(Oracle, JDE,PeopleSoft,

Baan)

Supplier Self

Services

Product / Vendor Catalog

ALE / RFC

XML Messages

OCI / OPI

SAP SRMEnterprise

Buyer

Inte

rnet

Tra

nsac

tion

Ser

ver

(ITS

)

HTTP



The overall process for the dispatcher, driver, and spooler is shown in Figure 3.6.

Several standard background jobs exist for SAP SRM, and many offer integrationbetween SAP SRM and the backend ERP systems. You must set the programs torun at regular intervals. You should be familiar with these common backgroundjobs that follow:

� BBP_GET_STATUS_2This program updates shopping carts to ensure that backend purchase requi-sitions, purchase orders, and reservations are up to date. You should schedulethis report at least daily in SRM EBP.

� CLEAN_REQREQ_UPThis program updates documents asynchronously in the backend systems.You can only process a shopping cart further after the update from this jobhas taken place. For example, it updates the cart with the follow-up documentpurchase requisition or purchase order information. You should schedule thisreport at least daily in SRM EBP.

� RSPPRPROCESSThis report is used to transfer your purchase orders to the vendors, andshould be run at regular intervals. This report is also used to send notifica-tions to suppliers during bid invitations and auctions.

Figure 3.6 Abstraction Layer

Business Object Determined by

Business Process Event

Business Process Triggers

Dispatcher

Determine Target System

Type

Determine Driver Function

Module

Call Local SRM Driver Fucntion

Spooler calls Remote

Function in Backend



Important Terminology and Definitions to Remember

This section is meant for you to refer back to for important definitions and ter-minology. Definitions appear throughout the chapter, but this is a review tohighlight key definitions relevant to this chapter with the highest probability ofbeing in the exam. You’ll find this useful when doing a quick review of the chap-ter.

� Stand-alone scenarioSAP SRM is the leading procurement system, where all procurement docu-ments are created locally.

� Classic scenarioSAP SRM shopping carts are created in SAP SRM, but the ERP system is theleading procurement system, where the purchase order resides.

� Extended classic scenarioSAP SRM is the leading procurement system, and the purchase order residesin SAP SRM. A read-only copy is sent to the backend ERP system.

� Decoupled scenarioThe decoupled scenario represents a hybrid implementation of more thanone scenario such as classic, extended, or standalone.

� Abstraction layerA feature that allows SAP SRM to communicate to multiple backends. Byleveraging the dispatcher, it can call software–version-specific driver functionmodules. It allows encapsulation of BAPI calls.

� Internet Transaction Server (ITS)Converts SAP GUI to HTML format via templates to enable Internet users toaccess transactions and functionality.

� Application Link Enabling (ALE)Communication between logical systems that can be SAP or non-SAP. ALE isbased on distribution models exchanging IDocs.

Caution

When scheduling BBP_GET_STATUS_2 and CLEAN_REQREQ_UP, many custom-ers want to run this more often such as hourly or even every 10 minutes. Notethat it is better to set up variants for these jobs to minimize performanceimpacts.



� Remote Function Call (RFC)Communication when one system calls a function module in a partner sys-tem.

� Open Partner Interface (OPI)Communication method that allows vendor data do be passed in a similarfashion as the OCI catalog data back to SAP SRM for strategic procurement.

� CLEAN_REQREQ_UPStandard batch job used to update shopping cart status such as follow-up doc-uments so carts can be processed further.

� BBP_GET_STATUS_2Standard batch job that goes hand-in-hand with CLEAN_REQREQ_UP. Thejob ensures that the shopping cart is current.

Practice QuestionsWe’ve reviewed the SAP SRM implementation scenarios along with the differentintegration points between SAP SRM and ERP systems. In this section, we’ll pro-vide test questions that mirror the actual certification exam format. As areminder, these questions focus on the content discussed in this chapter. Thisallows you to see how the exam frames questions and gives you actual exposureto the process.

Review each question and use it as practice for the exam. Attempt to answer thequestions before checking the answers.

1. A prospective customer is doing research for procurement capabilities andwants to implement a standard SAP SRM system. The customer asks you toexplain the implementation scenarios.

Which statements concerning implementations scenarios are correct?

There are three correct answers to this question.

Note

The content of the practice questions focuses on content covered in each chap-ter. It’s important to note that other subjects or information directly related maybe used on the exam. The content discussed is a refresher of main points, but isnot an exhaustive list.


Practice Questions Chapter 3 65

� A. The decoupled scenario requires purchase order output from both SAPSRM and the connected backend ERP system.

� B. The classic scenario results in a goods receipt posting in the ERP backendregardless if it was entered in SAP SRM or SAP ERP.

� C. The extended classic scenario does not fully support confirmation andinvoices in SAP SUS without consulting support.

� D. The extended classic scenario possible sources of supply include purchas-ing info records and contracts.

2. A customer has already implemented SAP SRM 5.0 extended classic scenarioand decides to expand SAP SRM to use its standard procurement card(Pcard) functionality for some vendor catalogs.

What impact does the Pcard functionality have in relation to the customer’simplementation scenario for SAP SRM 5.0?

There are two correct options.

� A. There is no impact to the implementation scenario because the extendedclassic scenario supports Pcard because the leading purchase order residesin SAP SRM.

� B. Pcard functionality is not supported in the extended classic scenario, sothe customer must change to the standalone scenario for all procurement.

� C. The implementation scenario should be changed to incorporate a hybriddecoupled scenario.

� D. The product category or business add-in must be used to control Pcardorders to be SAP SRM local orders only.

3. A shopping cart is created in SAP SRM, but an error occurs during the trans-fer of the cart to the ERP backend.

How does the abstraction layer in SAP SRM handle the transfer to the ERPbackend?

� A. An intermediate document (IDoc) will have an error status and will needto be reprocessed after the error is resolved via a transaction.

� B. The spooler will check the backend and resend the shopping cart at reg-ular intervals based on customizing.



� C. The driver function module will make a single call to transfer the shop-ping cart, and then manual intervention is required.

� D. The dispatcher will queue the shopping cart and reprocess the transfer tothe backend via scheduled batch job.

Practice Question Answers and ExplanationsFor each practice question in this chapter, this section gives the answer andexplains why the answer is correct.

1. Correct answer: A, B, C

� Answer A is correct because by definition the decoupled scenario involvesleading purchase orders residing in SAP SRM and in the backend ERP sys-tem. The purchase order output occurs in the leading procurement systemsuch as SAP SRM and SAP ERP.

� Answer B is correct because you can pre-enter a confirmation in SAP SRMor enter goods receipts in the ERP backend, but either way they result in agoods receipt in the connected ERP system.

� Answer C is correct because SAP SUS limitations exist with the extendedclassic scenario. Only the purchase order and purchase order response arestandard with extended classic integration with SAP SUS.

� Answer D is incorrect because the extended classic scenario does not sup-port purchasing info records as a source of supply.

2. Correct answer: C, D

� Answers C and D are correct because the customer is already establishedwith an implementation and does not have to change their complete imple-mentation scenario (which is a large undertaking), but rather has to iden-tify when it makes sense to use Pcard. They can then change to the decou-pled scenario and control the logic with the product category configura-tion, or if that’s not sufficient, use a BAdI to implement custom logic.

� Answer A is incorrect because Pcard functionality is only supported in thestand-alone scenario for SAP SRM 5.0.

� Answer B is incorrect because it states that only one scenario can be imple-mented, and it suggests that the customer must change all procurement tothe stand-alone scenario, which is incorrect.


Take Away Chapter 3 67

3. Correct Answer: B

� Answer B is correct because the spooler is used as the queue for carts. Thespooler tries to contact the connected backend at regular intervals toretransfer the shopping cart.

� Answer A is incorrect because IDocs aren’t used during creation of shop-ping cart follow-up documents.

� Answer C is incorrect because the driver function module calls the spoolerand then passes control to transfer the cart to the backend based on cus-tomizing settings.

� Answer D is incorrect because the follow-up document transfer does notoccur via a scheduled background job.

Take AwayThe practice questions presented in this chapter underscore a portion of the con-cepts that have been explained. This section summarizes the take-away pointsrepresented in the practice questions.

The key take-away points from the practice questions in this chapter are listed inTable 3.1.

Key Concept Definition

Scenario-dependent document output

� The decoupled scenario results in a subset of pur-chase orders (POs) in SAP SRM and a subset of POs in the connected ERP system. By definition, the PO can only be output in the leading system.

� For standalone and extended classic scenarios, the PO is output from SAP SRM.

� For the classic scenario, the PO is output from SAP ERP.

Table 3.1 Key Concepts Refresher



Scenario-dependent source determination

� The classic scenario is the only one that allows info records to be part of source determination.

� The classic scenario allows both purchasing informa-tion records and ERP contracts.

� Both the stand-alone and extended classic scenarios reference local contracts and interlinkages as sources of supply.

Scenario-dependent good receipt entry

� For the classic and extended classic scenarios, a receipt can be entered in Transaction MIGO in SAP ERP or entered in SAP SRM.

� If a receipt is entered in SAP SRM or SAP ERP for the classic or extended classic scenarios, it always results in the goods receipt posting existing in the backend ERP system.

� For the stand-alone scenario, receipts are entered in SAP SRM only.

Scenario integration limita-tions with SAP SUS

� For the extended classic scenario, only POs and PO responses are supported with limitations on confir-mations and invoices.

� For the classic scenario, the service procurement scenario is not fully supported.

Follow-up document creation

� Follow-up documents from SAP SRM to SAP ERP for shopping carts are done via real time BAPI RFC calls and not via IDocs or scheduled background jobs.

SAP SRM 5.0 Pcard scenario dependency

� SAP SRM Pcard functionality is only supported in the stand-alone scenario for SAP SRM 5.0. The extended classic scenario is not supported, even though the leading PO is in SAP SRM.

Scenario decision consider-ation

� A customer with an existing SAP ERP system that has implemented the Materials Management will typically lean toward the classic scenario, but this is just a rule of thumb. All requirements must be con-sidered to make a determination.


Table 3.1 Key Concepts Refresher (cont.)


Take Away Chapter 3 69

Tips

This section gives you additional clues on how to improve your odds of doingwell on the section of the exam covering this topic.

� You can review the SAP SRM 5.0 Functionality Matrix, which lists specificfunctions available to SAP SRM local vs. stand-alone/extended classic. Youcan search for the Functionality Matrix on SAP SDN or SAP Service Market-place.

� SAP Help contains additional information that will be helpful. You can accessthis information by visiting http://help.sap.com. You then navigate to SAP

Business Suite � SAP Supplier Relationship Mgmt � SRM 5.0 English. In theSAP SRM help window that launches, look under Architecture and tech-

nology � Technical scenarios.

Scenario transition � An implementation scenario that has already been implemented can be a large undertaking and a project unto itself to convert to a new implementa-tion scenario such as from the stand-alone to classic scenarios.

� If the requirements allow, it is typically better to have a hybrid solution, but of course all require-ments and processes must be evaluated for the spe-cific situation.

Dispatcher communication � The abstraction layer uses the spooler component to queue the shopping cart and reprocess the transfer to the backend at regular intervals based on cus-tomizing settings.

Note

You could use the search function on the http://help.sap.com website to searchfor the extended classic scenario, for example.


Table 3.1 Key Concepts Refresher (cont.)



SummaryWe’ve discussed the different implementation scenarios and gone through theprocess steps to touch on how the scenarios differ. After comparing the differentimplementation scenarios, you should have a clear understanding of how func-tionality can be impacted. The implementation scenario is a fundamental deci-sion on an SAP SRM project that impacts architectural and process mapping.

In addition, we’ve presented the different communication methods SAP SRMuses to connect to one or more backend systems. The available backend integra-tion options are essential concepts, similar to the implementation scenario. Asyou dive into details on the configuration and technical side, you’ll consistentlycome back to these basic communication methods. We’ll discuss the landscapeconcept for SAP SRM in the next chapter.


553

Index

/CCM/APPROVAL_BADI 236/CCM/CHAR_VALUATION 236/CCM/CSE_ENRICHMENT 236/CCM/CTLG_ENRICHMENT 236

A

a2a 481ABAP runtime error log 440, 442Abstraction layer 61ACC_GOODS_MOVEMENT 60, 122Account assignment category 449Account assignment FAQ 449Account assignment fields 450Account assignment function 453Account validation 454Accountants 118Accounting backend system 50ACLPAY 59, 122Activate extended classic scenario 392Activate sourcing 406Ad hoc functionality 330Adder 194ADDR_SHIPT 314Agent 327Agent determination 326, 340Aggregate demand 166, 173Agreement 273, 277All-in one deployment 234Analysis 36Analyze supplier performance 170Application 36Application Link Enabling (ALE) 59, 63, 438Application log 440, 442Application monitors 436Approval limit 335Approval preview 330Archive/unarchive 480ASN 210Assets 452Assignments 527, 528Associate characteristics 32Associate competencies 33

Associate exam topics 34Associate level 30Associate work experience 32Attachment enhancement 255Attachments 149Attribute 303, 315

Access Rights by Role 309Data type 418Maintenance 308

Auction 182, 197, 271Interface persistence 202Profiles 190Upload 184

Automap functionality 504, 510Automatic extension 193, 198Automatic requirement grouping 406, 410Automation and acceleration of processes 91Availability check 107

B

Backend ERP contract 162Backend follow-up document interval 295BAdI 465, 472

Basics 465Definition view 465, 472Filter-dependent 466Implementation view 465, 472

Bank statement 122Basic contract 248Basic settings 287, 295Basic workflow terminology 327BBP_AUCTION 189BBP_BACKEND_DEST 391BBP_BADI_EXTREQ_OUT 152BBP_BADI_OVERVIEW 466BBP_BID_INV 188BBP_BIDINV_BID 195BBP_BW_SC2 435, 442BBP_BW_SC3 436, 442BBP_BW_SC4 436, 442BBP_CAT_CALL_ENRICH 374BBP_CHANGE_SF_BID 195


Index554

BBP_CONTRACT_CHECK 250BBP_CONTRACT_INITIAL_UPLOAD 248BBP_CTR 252BBP_CTR_BE_CREATE 252BBP_CTR_MON 437, 442BBP_DETERMINE_ACCT 454BBP_DETERMINE_DYNATR 187, 419BBP_DETERMINE_LOGSYS 58, 252, 393BBP_DOC_CHECK_BADI 455BBP_DP_PROD_CHK_BADI 114, 393BBP_EXTLOCALPO_BADI 392BBP_EXTREQ_TRANSER 151, 153BBP_GET_STATUS_2 62BBP_ITEM_CHECK_BADI 455BBP_MON_SC 434, 442BBP_PCARD 122BBP_PCSTAT 122BBP_PD 435, 442BBP_PGRP_ASSIGN_BADI 169BBP_POC 164BBP_PRODUCT_SETTINGS_MW 360, 363BBP_QUOT 195BBP_QUOT_BOB 188BBP_SC_MODIFY_UI 112BBP_SC_TRANSFER_GROUPED 149BBP_SNEW_SYNCVD 354BBP_SP_SUPP_INI 355BBP_SRC_DETERMINE 407, 469BBP_STD_ACC 456BBP_SUS_ATTRIBUTES 209BBP_TARGET_OBJTYPE 408BBP_UPDATE_MAPPING 357BBP_UPLOAD_PAYMENT_TERMS 361, 363BBP_VDSYNC_CUST 354BBP_VENDOR_GET_DATA_JOB 353, 362BBP_VENDOR_SYNC 354BBP_VENDOR_UPDATE_DATA_JOB 354,

362BBP_WFL_APPROV_BADI 332BBP_WFL_SECURE_BADI 331BBP_WFL_SECURITY 331, 341BBP_XPRA_ORGEH_TO_VENDOR_GROUP

356BBPCF02 115BBPCF03 115BBPCO 59BBPERS 119

BBPGETVD 353, 362BBPIV 59, 120BBPIV01 118BBPIV02 117BBPIV03 118BBPMAININT 354BBPPCO01 165BBPSC01 111, 123, 137BBPSC02 108, 123BBPSC03 110, 123BBPSC04 112, 117, 137BBPSC18 137BBPSOCO01 147, 166, 403BBPUM02 308, 316BBPUPDVD 354, 362BBPV_SRC_DET 151BBPWLRA01 169BD14 355BD87 438, 443Bid decrement 192Bid evaluation 423Bid invitation 137, 182, 197

Profiles 188Template 183

Bid monitoring 192Bid Response 182, 197Bid response handling 185Bid validation 190Bid/auction process overview 185Bidder score 423Bidding with weighting 415Bidding/auction data flow 186Binding date 187, 198BLAORD 253BLAREL 253BMECAT 235Boolean logic 329BPPACCLOAD 457Budget check 452BUS2121 148BUS2209 165Business document 265, 277Business document (BDoc) 357Business object 292, 296, 326Business partner 294, 296

Concept 352Number 374


Index 555

Business partner (cont.)Number range 355Relationship 353Role 352

Business Server Pages 215

C

Cascading line items 193Catalog 106, 161, 164, 172Catalog Authoring Tool (CAT) 106, 233, 237,

314, 372Catalog call structure additional functions

374Catalog ID 372Catalog integration 228Catalog management 76Catalog performance 233Catalog Search Engine (CSE) 234, 238Catalog user role 538Central contract 251Central goods recipient 115Central person 306, 316Certification improvements 29Certification objectives 28Change tracking 233, 489Changing an auction 194Characteristic 237Check in/out functionality 522Check partner profiles 438, 443Check shopping cart status 112Checkout options 522Checkout protection 523CI_OCI_CUSTOMER_EXTENSION 379Classic scenario 54

Process 54Clause 273, 278CLEAN_REQREQ_UP 62, 64Clone fields 500Collective invoice 118COMCPRFORMAT 360, 363COMM_HIERARCHY 359, 361Common sourcing transactions 403COMMPR01 162, 359, 361Compare 541Competency level 22Competitive advantage 28

Completion workflow 175Complex prices 188Complex pricing and scales 202Complex service hierarchies 229COND_A 253Confidential 249Configuration elements 59Confirmation and invoice 136Confirmation control 210Connection properties 500Console hierarchy pane 479Contact person 209, 353Content import 235Contract 136, 162, 172, 272Contract (local) 246, 256Contract alert categories 254Contract authorization concept 249Contract distribution to catalog 248Contract document 273, 277Contract fulfillment 251Contract fulfillment and document creation

overview 252Contract generation 274Contract hierarchy 249, 256Contract management 76, 245

Process overview 247Contract monitoring 253Contract negotiation 250Contract preparation 247Contract search 249Contract standard reports 253Contract types 246Contract upload/download 249Cost distribution 452Cost reduction and process optimization 92Create a bid invitation/auction 183Create attributes 420Create auction 167Create bid invitation 166Create contract 166Create hierarchy field 509CRMRFCPAR 360, 363Cross-catalog search 375Currency 361, 363Custom fields 216Customer benefits 28


Index556

Customizable text for account assignment 451

Customize display 541Customize search 542

D

Data groups 505Decoupled scenario 57Default for valuation records 420, 425Default user 538Defaults for limit items 136Define account assignment categories 449Define backend system per product cate-

gory 391, 392Define backend systems 291, 296, 391, 455Define G/L account 453Define objects in backend system 408Define output format of product IDs 360,

362Define start conditions 329Delivered account assignments 449Delivered confirmation and invoice workflow

337Delivered shopping cart workflows 334Delivery complete 117Delta download 359Deployment scenarios 208Destination hierarchy pane 503, 510Detailed price information 188Determine follow-up documents 408Direct procurement 113, 124, 148, 393

Prerequisites 114Disclosure of information 191Disparate procurement systems 91, 97Dispatcher 61, 208, 217Display and resend IDoc 438, 443Display workflow work items 439Distribute weights 423Distributed scenario 1 234Distributed scenario 2 235Distribution model 291, 296Distribution model example 292DNL_CUST_BASIS3 358Document template 265, 277Document type 265, 277DP_PROC_TY 114

Drill-down search 519Driver 61Dynamic attribute configuration 419Dynamic attribute groups 418, 424Dynamic attribute required 417Dynamic attributes 186, 198, 417

E

Enable partner strategy 28End date 187, 198Enhancement packages 91Enter invoice/credit memo 117Entry channel 152, 311

Requirement 156EPROFILE 156EPRTRANS 151Establish connection 500Evaluated receipt settlement (ERS) 119

Flag 119Evaluation 37Evaluation criteria 170Exam topic 22Excel upload 184Exchange rate 361, 363Exclusive checkout 523Export/import 527, 529Express confirmation 117Express invoices 118Extended classic process 56Extended classic scenario 55Extensible Markup Language (XML) 60External catalog 370, 383External procurement 408, 410External requirement 148, 153, 311

Approval 147External requirements 168

F

Factored cost bidding 194, 198Field-level settings 506Fill in the blank 24Fixed 422, 425FLT_VAL 466Follow-up documents 105Forward auction 271, 278


Index 557

FORWARD_WI 333Free-form 107Free-form search 520Fully distributed scenario 235

G

General configuration tab 538General ledger basics 453General ledger determination 461General task 330General troubleshooting tools 440Global outline agreement (GOA) 246, 251,

256Goods receipt (GR) flag 106Group conditions 255

H

Hard-coded OCI 544Head of own organizational unit 311Hierarchal form 137Hierarchy mode 521, 528HOOK_URL 374HR replication 307HRMD_ABA 59HRP1000 308HRV1222A 308HTTP 371Human Resource 305Hyperlink field for images 527, 528

I

IDoc status list 438, 443IDoc test tool 438, 443Implementation scenarios 50, 166, 405Import/export parameter 469Importing objects 505Improved supplier collaboration 93Inbound catalog return 372, 384Inbound OCI call return 375Inbound/outbound queue 440Indirect material 113, 124Individual benefits 29Industry solutions 91Info records 68

Infotypes 304Inheritance 307Initial download 357Integrated call structure 372Integration advantages 100Interlinkage 53, 142Internal catalog 370, 383Internal procurement 408, 410Internet Transaction Server (ITS) 60, 63, 84Invoice only 136Invoice workflow summary 338Invoicing party 208, 217Is Purchaser of 311IS_COMPANY 305, 315IS_PGR 305, 316IS_POR 305, 316Item category 134, 139Item category determination 142Item display criteria 538Item-based shopping cart approval 332

J

Java Applet 189Java Web Application Servers 73Job roles 30Join tables 500

K

Key concept refresher 21Key mappings 508, 511Knowledge recall 36KNT 451

L

Last Delivery 117LDAP 313Leading account assignment 450Level 1 122Level 2 122Level 3 122Limit item 112, 123Limit item service 132, 139Limit items 135

Multiple 136


Index558

Linear 422, 425Link 527Live Auction Cockpit (LAC) 74, 81Local account validation 454Local contract 251Logical system 289, 296Lots 187, 198Lower TCO 28

M

Main editing pane 503, 510Maintain local accounting data 456Maintain prefix numbers 327, 341Maintain standard settings for workflow

328, 341Maintain Transactions 441Manage content 235Manual 422, 425Map checkbox 505Masks 524, 528Masks and named searches 524Master agreement 273, 277Master data 59Master level 30Master level competencies 38Master-slave concept 482Match class 507Match type 507Matching fields 507, 511Matching mode 521, 528Matching records 507, 511, 527, 529Material and material group filters 360, 363Material Group 150, 357Material Master 357Material Type 357Materials Management documents 54MBGMCR 59, 116MDM Catalog Console 479MDM CLIX 483, 490MDM constraints 488MDM Data Manager

Basics 519Main window 520Record comparison 521

MDM Import ManagerBasics 499

MDM Import Manager (cont.)Main window 504

MDM import steps 500MDM privileges 488, 491MDM repository 480MDM role 488, 491MDM user 488, 490MDM Web User Interface basics 537Measure competency 28Message maintenance 441Microsoft Visio 526Middleware and material master replication

357Middleware tables 360, 363Middleware troubleshooting 358MIGO 68Missing goods receipt 119Mitigate risk 28Modifying repository fields 486, 490Modifying repository tables 485, 490Monitor Business Partners 438Monitor Contract Distribution 437Monitoring Shopping Cart 434, 442Mount MDM Server 480Mount the repository 480Movement type 122 117Multiple account assignments 452Multiple choice 24Multiple ERP backend systems 59Multiple response 23Multiple service items 135Multiplier 194Multi-valued mapping 505, 510

N

Named searches 524, 528NetWeaver 7.0 73NetWeaver Process Integration (PI) 60Nonexclusive checkout 523Number ranges 294, 296

O

OCI Fields tag 545OCI Mapping 543Offline approval 333, 341


Index 559

OKP E-Sourcing 4.2 (OES42) 43Old purchase orders and templates 107One-time vendor 120Online approval 333, 341Online Knowledge Products (OKP) 43

SRM 3.0 (OSR30S) 43SRM 4.0 (OSR40S) 43SRM 5.0 (OSR50S) 43SRM 6.0 (OSR60S) 43

Open Catalog Interface (OCI) 60, 229, 370, 383Required fields 378Standard inbound fields 376

Open Catalog Interface configuration 543Open Partner Interface (OPI) 60, 64, 168,

214Opening date 187, 198Operational contracts 244Operational procurement 94Operational purchaser 163Order as direct material 113Order processor 208, 217Organization unit address 306Organizational structure objects 306Organizational unit 305, 315Outbound catalog call 371, 383Outbound catalog call structure 372Outlines 187, 198Output conditions 209Output medium 165

P

Parameter IDs 304Parametric import 499Parametric search 499, 500Partner benefits 29Payment terms 361, 363PDF skills profile 137Pearson VUE 31Perform task-specific customizing 328, 341Permit proxy bidding 188Plan-driven procurement (PDP) 76, 146, 153

Deployment scenarios 148Limitations 149

Plants 361, 363PLM integration 188

PO output 67Position 306, 316Possible local accounting data 456PPOCA_BBP 308PPOCV_BBP 356, 361PPOMA_BBP 308, 316PPOMV_BBP 356, 361PPOSV_BBP 356, 361Practice question answer and explanation 21PRCAT 321Predefined users 537Price conditions 165Price determination 163, 172Procurement card (Pcard) 120

Classic scenario 121Limitations 121Masters 122

Procurement catalogs 235Product 107Product category 57, 382, 393, 406Product category hierarchy 255, 256Product interlinkage 161, 172Product type 134, 139Professional characteristics 36Professional competency level 38Professional level 30Professional purchaser 164Propose attributes 420Propose sources of supply 167Proxy bidding 193, 198Public bid invitations 182, 197Publish catalog 235Purchase document creation 185Purchase order output 164Purchase order process 164Purchase order response (POR) 165, 212Purchaser roles 163Purchasing group 150, 404Purchasing group responsibility 310Purchasing organizations 356Purchasing responsibility 404Purchasing workload 404

Q

Qualified table 486Qualifiers 486


Index560

Question hint 23Question media 24Question stimulus 23Quota arrangement 162, 172, 253

R

R3AM1 358RBBP_NOTIFICATION_OFFAPP 333Read-only option 502, 510Ready to Import 501Real-time validation 454Reassign Workload 169Recertification 45Record mode 520, 528Registration key 214Remote Function Call (RFC) 60, 64, 289, 296Remote key 509Remote systems 508, 511Remove rejected suppliers 214Rendered 527Replacement approver 338Repository 233, 479Repository modes 520REQUESTOR 112Requests for external staff 136Requisite 233Restore Defaults 541Restricted bid invitations 182, 197Return URL 374, 384Reverse auction 271, 278Review source schema 500Reviewer 330RFI 182, 197RFP 182, 197RFQ 182, 197RFx creation 184RHOMATTRIBUTES_REPLACE 309RM06BZ10 152ROS 213

Questionnaire determination 222ROS_BUPA_DATA_CHECK 213ROS_DELETE_REJECTED_BP 214RSCONN01 333RSPPRPROCESS 62RSWUWFMLEC 333RZ20 436

S

SALE 289SAP Bidding Engine 74, 81SAP Business Suite 91SAP Contract Lifecycle Management (CCM)

262, 277Catalog data flow 241Components 233Deployment components 234

SAP CRM Middleware 357SAP Development Network (SDN) 45SAP Education Certification 46SAP Enterprise Buyer (EB) 73, 74, 81SAP ERP Human Capital Management 305SAP E-Sourcing 275

Basic concepts 264Benefits 262

SAP E-Sourcing integration 101SAP Help 45SAP Internet Pricing and Configurator (IPC)

74SAP NetWeaver Application Server (AS) 73SAP NetWeaver Business Warehouse (BW)

74SAP NetWeaver MDM

Console 230, 237Data Manager 230, 237Import Manager 230, 237Server 230, 237

SAP NetWeaver MDM catalog security 488SAP NetWeaver Portal 74, 79SAP NetWeaver Process Integration (PI) 74,

78, 232, 238, 354Requirement 84, 241

SAP Overview (SAP01) 42SAP Procure-to-Pay (SAP210) 42SAP Service Marketplace 45SAP SRM 6.0 43SAP SRM CCM (SRM260) 42SAP SRM Configuration (SRM210) 42SAP SRM E-Sourcing Overview 42SAP SRM Overview (SAP SRM) 42SAP SRM standard business objects 293SAP SRM-MDM 74

Architecture 232Standard components 241


Index 561

SAP SRM-MDM Catalog (SRM270) 43SAP Supplier Relationship Management 88SAP Supplier Self-Service 74, 81, 137SAP SUS 354

In classic scenario 54Purchaser role 215

SAP SUS/SRM user interface 221SAP_BBP_STAL_ACCOUNTANT 118SAP_BBP_STAL_OPERAT_PURCHASER 163SAP_BBP_STAL_PURCHASER 164SAP_BBP_STAL_RECIPIENT 115SAP_BBP_STAL_STRAT_PURCHASER 164SAPconnect 333Save import map 508, 511Save Search 521SCC4 289Scenario determination process flow 394Schema 237Schema import 481, 490SE19 469SE91 441SE93 441Search 540Search catalog 236Search help 452Sections 274, 278Sections of all contracts 250Self-service 312Self-service process 106Self-service procurement 76, 123Sequence/ranking 24Server-oriented architecture (SOA) 91Service confirmation 135Service entry sheet 117Service item spilt 135Service Master 357Service procurement 76, 138Service types 132Service-oriented architecture (SOA) 211Shop-on-behalf 112, 123Shopping cart check status 435, 442Shopping cart full functionality 111, 123Shopping cart simplified form 110, 123Shopping cart transactions 108Shopping Cart Wizard 108, 123Shopping carts per cost center 436, 442Shopping carts per product 436, 442

Shopping lists 541Shopping options 538Simple service 132, 139Simulate workflow 439SLAPPROVER 336SLG1 440, 442SM21 441, 442SM59 290SMARTFORMS 165SMOEAC 360, 363SMQ1 151, 358, 441SMQ2 358, 440SMW01 359Source determination 54Source hierarchy pane 503, 510Source of supply 137, 161, 172, 405

For external staff 142Object to implementation scenario 405

SourcingAlways carried out 406, 409Application 166Application overview 166Carried out for items without a source of sup-

ply 406, 409Cockpit 403Concept 413Follow-up documents 413Hub 146Never carried out 406, 409Transaction basics 403Via vendor list 412

Sourcing/product search 375Spend analysis 76Spending limits 335Spooler 61SRM curriculum 44SRM Server 5.5 73, 81SRM-MDM 237SSCR 466ST22 440, 442Staged production environment 482Stand-alone process 53Stand-alone scenario 50, 52Standalone scenario 137Standard call structure 372Standard SAP SRM roles 109Start conditions 326, 340


Index562

Start date 187, 198Start the MDM Server 480Step 422, 425STR 450Strategic procurement 95Strategic purchaser 164Strategic sourcing 76Strategy and compliance improvement 92Submit to grouping 168, 173Supplier administrator 208, 217Supplier bidder 209, 217Supplier collaboration 96Supplier enablement 76, 77Supplier hierarchy 254, 256Supplier performance 170Supplier preselection 213Supplier registration 213

Process overview 214Supplier scorecards 268, 278Supplier screening 214Surrogate bidding 188, 198Survey templates 170SUS 1

N 208, 217SUS supplier roles 208SUS User Management 216, 217

Engine 209SUS with extended classic 56SUS-EBP 208, 217

Process flow 211SUS-MM 208, 216

Confirmation control 221, 222IDoc reference 210

SUS-specific role attributes 209SWI1 439SWI2_FREQ 439Switch Framework 91SWU_OBUF 439SWUD 439Synchronize buffer 439Synchronize Slave 483Synthesis 37System connection 289

Overview 290System Log 441, 442System type 291

T

T77OMATTR 309Table types for MDM repository 484Take away 21Take vendor from external list 168Task 327Taxonomy mode 521, 528Templates 274, 278Temporary contact person 214Temporary labor 132, 139Text Retrieval and Information Retrieval

(TREX) 75, 78, 234Tied rank 192Tiered exam approach 30Tolerance group (TOG) 119Tolerance POR 165Topic introduction 21Transaction type 293, 296Transactional data 59True/false 24

U

UI user-centric 538Understanding 36Unit of measure 362, 382User Error Log 374User ID 306, 316User profile 303USERS_GEN 152, 312, 316

V

V_BBP_DET_LOGSYS 392V_T160EX 150, 153V_T160PR 150, 153Validation of a product 375Validation properties 525Validations and workflow 525Valuation function 421Value chain 94Value conversion filters 506Value drivers 90Value mapping 505Vendor comparison 170Vendor contacts 268


Index 563

Vendor evaluation (VE) 169, 173Data flow 171Process 170

Vendor groups 355Vendor list 162, 172, 408Vendor Management 267Vendor portfolio analysis 171Vendor replication customizing 355VENMAP 215, 355Version management 164

W

Waiting preceding document 119WE05 438, 443WE19 438, 443Weighted bidding 272Weighting and ranking 421Weighting functions 416WF-BATCH 174, 328Wild cards 392Winner determination 185Work item 326, 340Work list integration 166Workbench 266, 277

Channel types 266Workflow 439

Builder 327Container 326, 340

Workflow (cont.)Definition 324, 340Events 324Explorer 327Security 331Security-level setting 332Triggering events 526

WRK 321WS10000031 334WS10000060 334WS10000129 334WS10000271 330WS10000276 334WS10400002 337WS10400009 338WS10400010 337WS14000044 176, 335WS14000109 334WS14000133 334WS14500015 335WS14500020 339

X

XML 60, 115, 376XML external requirements 149XML invoice 119, 339XML POR 165XML schema import 482
