10542292 sapsrm overview

SAPSRMmySAP Supplier Relationship

ManagementmySAP Supplier Relationship Management

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 2005 Q2Course Duration: 3 Day(s)Material Number: 50074659

An SAP course - use it to learn, reference it for work

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Copyright

Copyright 2005 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server areregistered trademarks of Microsoft Corporation.

IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX,S/390, AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation.

ORACLE is a registered trademark of ORACLE Corporation. INFORMIX-OnLine for SAP and INFORMIX Dynamic ServerTM are registered

trademarks of Informix Software Incorporated. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, MultiWin and other Citrix product names referenced herein are trademarksof Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, WorldWide Web Consortium, Massachusetts Institute of Technology.

JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.comare trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks oftheir respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDINGWITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANYKIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOSTPROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDEDSOFTWARE COMPONENTS.

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal (in this documentation) and external (inother locations, such as SAPNet).

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2005/Q2 2005 SAP AG. All rights reserved. iii

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

About This Handbook SAPSRM

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructorspresentation.

iv 2005 SAP AG. All rights reserved. 2005/Q2

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

ContentsCourse Overview ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Course Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Unit 1: mySAP SRM Overview ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1SRM Architecture and Software Components .. . . . . . . . . . . . . . . . . . . . .2mySAP SRM Scenarios... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Unit 2: mySAP SRM Operational Procurement .... . . . . . . . . . . . . . . . 35SRM Master Data and Organization Plan .. . . . . . . . . . . . . . . . . . . . . . . . 37Self-Service Procurement: Shopping Carts .. . . . . . . . . . . . . . . . . . . . . . 65Self-Service Procurement: Confirmations .. . . . . . . . . . . . . . . . . . . . . . .109Self-Service Procurement: Invoices .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Plan Driven and Manual Direct Procurement .. . . . . . . . . . . . . . . . . . .145Service Procurement ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162Operational Purchasing ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182

Unit 3: mySAP SRM Strategic Purchasing and Sourcing ..... 199Spend Analysis and Reporting in SRM .... . . . . . . . . . . . . . . . . . . . . . . .201Sourcing of Requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210Contract Management.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233Bidding Engine .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245SAP Catalog Content Management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .284

Unit 4: my SAP SRM Supplier Collaboration ..... . . . . . . . . . . . . . . . . 293Supplier Collaboration .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294

2005/Q2 2005 SAP AG. All rights reserved. v

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Contents SAPSRM

vi 2005 SAP AG. All rights reserved. 2005/Q2

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Course OverviewSAPSRM provides an introduction to the mySAP SRM Solution, as well asconcentrates on the key functionality of the Enterprise Buyer Professional. Thecourse begins with a high-level overview of Enterprise Buyer Professional and theother mySAP SRM Solution components. Since this course is a prerequisite forthe Enterprise Buyer Configuration course, a vast majority of the course focuseson the heart of the solution, Enterprise Buyer Professional, and its applicationfunctionality, roles and processes. The course also provides participants withhands-on experience with Supplier Self-Services and Live Auction.

Target AudienceThis course is intended for the following audiences:

Customers who want an overview of SAP Supplier Relationship Managementand the corresponding processes

SAP consultants and partners

Course PrerequisitesRequired Knowledge

Knowledge of Microsoft Windows and Internet browsers Basic knowledge of the procurement process

Recommended Knowledge

SAP01

Course GoalsThis course will prepare you to:

Outline the purpose and function of mySAP SRM and its softwarecomponents.

Understand the business scenarios of the mySAP SRM solution Understand the software components utilized by the mySAP SRM solution

and their integration points

Course ObjectivesAfter completing this course, you will be able to:

Describe the architecture of mySAP SRM

2005/Q2 2005 SAP AG. All rights reserved. vii

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Course Overview SAPSRM

Describe the application and technical components of mySAP SRM Explain the business and technical scenarios of mySAP SRM Describe the key master data and roles within my SAP SRM Execute processes within Enterprise Buyer, Supplier Self-Services and the

Bidding Engine.

SAP Software Component InformationThe information in this course pertains to the following SAP Software Componentsand releases:

viii 2005 SAP AG. All rights reserved. 2005/Q2

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit 1mySAP SRM Overview

Unit OverviewThis unit will introduce you to the SRM solution and its software components. Italso provides an overview of the SRM business scenarios as well as master data.

Unit ObjectivesAfter completing this unit, you will be able to:

Describe the SRM application components and their purposes Describe the SRM integration components and their purposes Explain the integration of SRM with other solutions Explain the SRM business scenarios Describe the roles utilized in different business scenarios Explain the different SRM technical scenarios

Unit ContentsLesson: SRM Architecture and Software Components .. . . . . . . . . . . . . . . . . . . . . .2

Exercise 1: SRM Components.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Lesson: mySAP SRM Scenarios ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Exercise 2: Self-Service Procurement Cycle .. . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2005/Q2 2005 SAP AG. All rights reserved. 1

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit 1: mySAP SRM Overview SAPSRM

Lesson: SRM Architecture and Software Components

Lesson OverviewThis lesson will provide an overview of the different software components thatmake up the mySAP SRM solution.

Lesson ObjectivesAfter completing this lesson, you will be able to:

Describe the SRM application components and their purposes Describe the SRM integration components and their purposes Explain the integration of SRM with other solutions

Business ExampleYou company will be implementing mySAP Supplier Relationship Management(mySAP SRM) and you have been assigned to the project team. As a project teammember, you need to become familiar with the different software components thatmake up this solution and their integration points.

mySAP SRM Application Components

Figure 1: mySAP Supplier Relationship Management

mySAP Supplier Relationship Management (mySAP SRM) is part of the mySAPBusiness Suite. mySAP SRM covers the full supply cycle, from strategic sourcingto operational procurement and supplier enablement, leveraging consolidatedcontent and master data. With mySAP SRM, you can collaborate with all

2 2005 SAP AG. All rights reserved. 2005/Q2

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

SAPSRM Lesson: SRM Architecture and Software Components

suppliers for all purchased goods and services. This means you can constantlyoptimize supplier selection, compress cycle times, and devise focused sourcingand procurement strategies.

Figure 2: mySAP SRM is Better Supply Management

mySAP SRM is comprised of different software components. Your requirementsdetermine which of these software components you will deploy. The currentrelease of the mySAP SRM solution is 4.0. Each software component within thesolution has its own release.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 3: SRM 4.0 Bill of Material

SAP Enterprise Buyer 5.0

SAP Enterprise Buyer is the central component of mySAP SRM. Itis a separate SAP system that you can use in a heterogeneous systemenvironment. SAP Enterprise Buyer can communicate with one or moreEnterprise Resource Planning (ERP) systems, which can be SAP R/3 ornon-R/3. Implement SAP Enterprise Buyer if you want to use an Internetsolution to map the complete procurement process for both direct andindirect materials and services.

Internet Pricing and Configurator 4.0

You can use the Internet Pricing and Configurator (IPC) to configure andprice products in a Web environment using master data downloaded fromSAP R/3 or product master data maintained directly in mySAP SupplierRelationship Management (mySAP SRM). This product master data isautomatically available in IPC and does not require an additional download.In the SAP Enterprise Buyer classic scenario, pricing can occur without theIPC in certain circumstances. You can find more information in SAP Note539720 (Simplified Pricing: Classic scenario).

Bidding Engine 3.0

Purchasers can use the SAP Bidding Engine to create and process bidinvitations and live auctions for products and services. Bidders can usethe SAP Bidding Engine to submit bids in response to bid invitations andauctions.

Live Auction Cockpit 2.0

Live Auction Cockpit provides a real-time environment for direct bidding onreverse live auctions, which are typically fast-paced and highly competitive.Live auctions simulate the experience of an actual auction by utilizingtechnology to provide instantly-updated information on all auction activity.Live auctions are handled by a J2EE-compliant applet that is fully integratedwith SAP Bidding Engine and that cannot be implemented independently.

SAP Supplier Self-Services 3.0

Supplier Self-Services (SUS) is a hosted system for suppliers that canbe accessed easily using a Web browser. SUS provides full processingcapabilities for goods and service orders and integrates suppliers into theprocurement processes of large buying organizations. Such suppliers do notrequire their own sales systems to offer products and services; all they needis Internet access in order to have hosted order and content managementfunctionality.

SAP Business Information Warehouse 3.5


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


The SAP Business Information Warehouse (SAP BW) is a system that allowsyou to analyze data from operative SAP applications and all other businessapplications and external data sources, such as databases, online services, andthe Internet. SAP BW reports can be executed from within SAP EnterpriseBuyer and Supplier Self-Services if the user has the appropriate role.

The SAP Business Information Warehouse (SAP BW) provides structuredanalyses for mySAP SRM. SAP BW is used for both operational andstrategic analysis:

Operational analysis: Data is provided on individual document levelwith document header and document item information. OperationalData Store (ODS) objects for purchase orders, confirmations, invoices,contracts, bid invitations, and bids are defined on the basis of ODStechnology in SAP BW.Strategic analysis: Data is provided on an aggregated level. It ispossible to analyze data aggregated according to time, vendor, product,and product category, as well as according to account assignment. TheInfoCubes defined for this are supplied with information from theODS objects.

SAP Catalog & Content Management 1.0

SAP Catalog Content Management can be used to upload, manage, andsearch in procurement catalogs as part of your mySAP Supplier RelationshipManagement (mySAP SRM) procurement processes.

Figure 4: SRM 4.0 Components Overview


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


mySAP SRM is Powered by SAP NetWeavermySAP SRM is delivered with SAP NetWeaver. This provides access to an entirerange of software infrastructure capabilities, many of which can be leveragedto manage supply management processes not typically covered by other SRMsolutions. For example, embedded portal technology can be used to providesupplier access to internal systems and content. SAP NetWeaver also providespowerful document exchange capabilities with support for industry-specificXML standards. These capabilities allow you to achieve high levels of processintegration at costs far lower than those associated with traditional electronicdata interchange (EDI) techniques. With these and other capabilities at hand,you can extend beyond core SRM functionality to manage a wider range ofsupply processes in a manner that accelerates cycle times and boosts competitiveadvantage.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 5: mySAP SRM is Powered by SAP NetWeaver

SAP Enterprise Portals 6.0

SAP Enterprise Portal offers a single point of access to information,enterprise applications, and services both in and outside your organization. Itprovides you with tools to manage this knowledge, to analyze and interrelateit, and to share and collaborate on the basis of it. With its coherent interface,role-based content, and personalization features, the portal enables you tofocus exclusively on data relevant to your daily decision-making processes.

SAP Exchange Infrastructure 3.0

SAP Exchange Infrastructure (SAP XI) enables you to implementcross-system business processes. The aim of the SAP ExchangeInfrastructure is to integrate different versions of SAP and non-SAP systemsimplemented on different platforms (Java, ABAP, and so on). SAP XI isbased on an open architecture, uses open standards (in particular those fromthe XML and Java environments) and offers services that are essentialin a heterogeneous and complex system landscape, namely a runtimeinfrastructure for message exchange, configuration options for managingcollaborative processes and message flow;, and options for transformingmessage contents between the sender and receiver systems.

SAP Enterprise Buyer uses SAP XI for communication with otherapplications and components. SAP XI links SAP Enterprise Buyer with bothinternal and external components.

SAP Web Application Server 6.40

The underlying technology for almost all mySAP.com e-business solutions,formerly called SAP Basis. In addition to the known SAP programmingmodel, the SAP Web AS provides:

Native support for HTTP, HTTPS, SMTP and other Internet protocols Server-side scripting in ABAP and JavaScript A development environment for Internet applications

Internet Transaction Server 6.40 (integrated) and Internet TransactionServer 6.20 (external)

TREX 6.10

TREX is a component that offers standard retrieval functions such as exactand error-tolerant search, phrase search, Boolean search, and attribute search.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 6: SAP Enterprise Portal 6.0

Figure 7: ITS Standalone vs. ITS Integrated


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Integration with Other Solutions

Figure 8: SRM-PLM Integration

mySAP SRM works with any supply chain management (SCM), product life cyclemanagement (PLM), or enterprise resource planning (ERP) solution from SAP orany other vendor. You will be able to:

Reduce buffer inventory by integrating with SCM systems; this enablesupdates made in collaborative planning and inventory management systemsto automatically trigger plan-driven procurement

Accelerate product development cycles by integrating design and PLMsystems with mySAP SRM to facilitate supplier selection for engineeredgoods and materials

Synchronize back-office functions, such as invoice approval, purchaseorder creation, and payment, by integrating with corporate finance and ERPsystems

Increase the efficiency of buy-sell transactions by directly integrating yoursuppliers e-selling solutions


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 9: Supply-Side Collaboration with mySAP SRM

ERP-SRM Integration

In the Self-Service Procurement area of mySAP ERP, employees can create andmanage their own ordering transactions. In this way, the extensive administrativetasks of the purchasing department are reduced and the procurement process isaccelerated. To enable your employees to use the applications in the Self-ServiceProcurement area, you implement the mySAP ERP business scenario, Self-ServiceProcurement and mySAP Supplier Relationship Management. The applications inthis area enable your employees to perform the following tasks:

Purchase goods and services Every employee can purchase individuallythe goods and services he or she requires for his or her work area.

Confirm goods and services Every employee can confirm individually thegoods and services that he or she has ordered.

Check status In this application, your employees can check the overallstatus of the shopping cart or the status of the individual items it contains.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 10: mySAP ERP Integration with mySAP SRM

The Supplier Order Collaboration Process within mySAP ERP is where theMM system sends a purchase order for indirect materials to the SAP SupplierSelf-Services (SUS) system via SAP Exchange Infrastructure (XI). The suppliercan then create a purchase order response which is sent back to the MM systemvia XI. The goods recipient confirms the goods receipt in the MM system and thenthe supplier can create an invoice in SUS.

Catalog Content Management scenario in mySAP ERP can be used to create,manage, and search in catalogs. SAP Catalog Content Management consists of thefollowing components:

SAP Catalog Authoring Tool SAP Catalog Search Engine


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly



Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercise 1: SRM Components

Exercise ObjectivesAfter completing this exercise, you will be able to: Differentiate between the different software components that make up SAP

SRM

Business ExampleAs a project team member, you need to clearly understand the softwarecomponents in mySAP SRM and their related functionality.

Task: SRM Software ComponentsIdentify the mySAP SRM software components

1. Which mySAP SRM software component allows you to analyze data fromSRM, other SAP applications, other business applications, and externaldata sources?Choose the correct answer(s). A Internet Pricing Configurator B SAP Bidding Engine C SAP Enterprise Portals D SAP Content Integrator E SAP Business Information Warehouse

2. Suppliers can access this mySAP SRM component from a Web browser toreceive POs created in SAP Enterprise Buyer or SAP R/3.Choose the correct answer(s). A SAP Bidding Engine B SAP Exchange Infrastructure C SAP Supplier Self-Services D Requisite eMerge

Continued on next page


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


3. This mySAP SRM component enables you to integrate different versionsof SAP and non-SAP systems and to exchange XML documents betweenbusiness partners.Choose the correct answer(s). A SAP Enterprise Buyer B SAP Exchange Infrastructure C SRM Connector D Content Integrator E Requisite BugsEye

4. offers a single point ofaccess to information, enterprise applications, and services both in andoutside your organization.Fill in the blanks to complete the sentence.

5. SAP Enterprise Buyer can only be integrated with one ERP system, whichmust be SAP R/3.Determine whether this statement is true or false. True False

6. Purchasers can use the to createand process bid invitations and live auctions for products and services.Fill in the blanks to complete the sentence.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solution 1: SRM ComponentsTask: SRM Software ComponentsIdentify the mySAP SRM software components

1. Which mySAP SRM software component allows you to analyze data fromSRM, other SAP applications, other business applications, and externaldata sources?

Answer: E

SAP Business Information Warehouse is the SRM component used forreporting and analysis. SAP BW reports can be executed from within SAPEnterprise Buyer, Supplier Self-Services, and SAP Enterprise Portals,depending on the role of the user.

2. Suppliers can access this mySAP SRM component from a Web browser toreceive POs created in SAP Enterprise Buyer or SAP R/3.

Answer: C

Supplier Self-Services (SUS) allows suppliers without EDI or XMLdocument exchange capabilities to participate in e-commerce by accessing ahosted environment using only a Web browser.

3. This mySAP SRM component enables you to integrate different versionsof SAP and non-SAP systems and to exchange XML documents betweenbusiness partners.

Answer: B

The SAP Exchange Infrastructure (SAP XI) enables you to implementcross-system business partners.

4. SAP Enterprise Portals offers a single point of access to information,enterprise applications, and services both in and outside your organization.

Answer: SAP Enterprise Portals

5. SAP Enterprise Buyer can only be integrated with one ERP system, whichmust be SAP R/3.

Answer: False

SAP Enterprise Buyer can be integrated with multiple ERP systems, eitherSAP R/3 or non-R/3.

6. Purchasers can use the SAP Bidding Engine to create and process bidinvitations and live auctions for products and services.

Answer: SAP Bidding Engine


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Lesson Summary

You should now be able to: Describe the SRM application components and their purposes Describe the SRM integration components and their purposes Explain the integration of SRM with other solutions


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

SAPSRM Lesson: mySAP SRM Scenarios

Lesson: mySAP SRM Scenarios

Lesson OverviewThis lesson provides an overview of the SRM business scenarios and technicalscenarios.


Explain the SRM business scenarios Describe the roles utilized in different business scenarios Explain the different SRM technical scenarios

Business ExampleYou need to identify the business and technical scenarios of SRM that will bestmeet your companys requirements.

mySAP SRM Business ScenariosSRM can be implemented using different business scenarios, whereby SAPEnterprise Buyer represents the central procurement system.

Figure 11: mySAP SRM Business Scenarios


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Operational ProcurementOperational procurement is the process of buying direct materials and services(those used in production) or indirect materials and services (those used formaintenance, repair, and operations). Capabilities include:

Self-service procurement Empower employees to easily procure needed materialsusing a Web-based shopping cart that enforces compliance with corporatepurchasing policies. By decentralizing procurement in this way, you will reduceoverhead and allow purchasing professionals to focus on managing relationshipsinstead of transactions.

The process typically involves the following steps:

Create Shopping Cart Approval Ordering Goods received Invoice handling Payment Accounting

Service Procurement Reduce administration and processing costs associated withprocuring a wide range of services such as consulting and contract labor.


Requisition Approval Ordering Service entry Invoice handling Payment Accounting

Plan-driven procurement Streamline and automate the procurement of materialsused in core business processes by integrating purchasing with any supply chainmanagement system.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly



Planning Requisition Sourcing Ordering Goods received Invoice handling Payment Accounting


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Strategic Purchasing & SourcingStrategic purchasing and sourcing is the process of developing a sound supplystrategy and executing it by finding qualified sources to fulfill supply needs,negotiate purchase agreements, manage contracts, and evaluate supplierperformance. Capabilities include:

Supply strategy development Develop solid supply strategies that fit theneeds of the respective business units and are in-line with overall corporategoals. You can achieve this by employing a variety of different tools andmethods that may be unique to each commodity and supply market. Thestrategy upon which you will then execute provides specific details, suchas recommended suppliers, length and type of contract, local or globalsuppliers, and so on.

Spend Analysis Improve your visibility into global spend and supply-basedata by mapping and cleansing commodity and vendor information anddistributing it to internal systems, electronic catalogs, and data warehouses.This enables you to identify and rationalize redundant supply relationshipsand analyze spend patterns throughout the enterprise while putting yourcompany in a better position to negotiate contract terms and controlprocurement costs.

Supplier selection Minimize purchase risk, improve supply-basemonitoring, and more easily assess supplier performance. Doing this helpscompanies focus on suppliers that match specific needs and add businessvalue while providing information on those suppliers that need improvement.Then, it is easy to compress sourcing cycle times by collaborating withpreselected suppliers. You can accomplish this by using a variety ofelectronic auction and bidding tools that match supplier capabilities withsourcing requirements. Tight integration with product life-cycle managementsolutions from SAP or any third party enables superior supplier collaborationin engineered goods and materials sourcing processes.

Contract Management ensures compliance with negotiated terms andconditions. Centralized contract management enables dispersed purchasingdepartments in different business units to reuse pre-existing contracts forspecific product categories shared throughout the company. This helpsincrease global purchasing productivity.

Catalog Management Create and manage a unified e-commerce catalog,using tools that import data from external sources, maintain consistentschemes, and index items for faster search capabilities.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Supplier CollaborationSupplier collaboration provides a cost-effective way for suppliers to connect toa number of processes along the supplier relationship life cycle. Using a Webbrowser, suppliers can gain access to a supplier portal that could serve as acentralized hub for all supplier-related activities. Capabilities include:

Supplier registration Through supplier registration, purchasers have accessto supplier-managed information for better sourcing decisions. Suppliers canmanage their own company information, such as a business address, andcan provide information about their capabilities in answer to requests forinformation. Once registered, suppliers can assign numerous users at theirrespective company to a supplier portal.

Order collaboration This streamlines procurement processes by providingsupplier access to internal order management systems for processingorders, delivery schedules, managing invoices, and updating specificationselectronically. The performance-reporting features of the supplier portalcan also help suppliers manage catalog information and analyze importantdata such as inventory turnover, open purchase orders, contract history, orinformation on expiring contracts.

Design collaboration You can shorten product development cycles bypermitting employees from different trading partners to effectively sharerelevant product and project information that is consistently and convenientlymaintained at a central location, while keeping supporting and detailedinformation within the enterprise. This enables collaboration on designobjects like specifications and bills of materials.

Collaborative replenishment Optimize supply-chain performance byenabling suppliers to access customer inventory data and making themresponsible for maintaining the inventory levels required by customers on anexception-based replenishment process. This reduces costs and increases theoverall velocity and accuracy of the supply network.

Supplier connectivity Connect with suppliers of different sizes andcapabilities using Extensible Markup Language (XML)-based documentexchange.

Roles Within mySAP SRMRoles describe the activities that internal employees or external business partnersperform in a business scenario. Independent of the role, all users need a usermaster record in order to be able to log on to the system. After logging onto thesystem, users see all functions that they need to process their tasks.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 12: Roles in EBP Business Scenario

Occasional users do not access the system very often or do so only to approveor review content.

Employees (anyone in a company) can procure the goods and services thatthey need for their work area. To do this, they search for and order goods andservices using electronic catalogs. They can check the procurement status atany time. Once the goods have been delivered or the service performed, theycreate a confirmation and enter the invoice for their purchase order. Theycan also change some of their user data. They cannot, however, conductthese tasks on behalf of other users.

The employee role serves as a basis role for all internal users in a company.It provides basic functionality as well as the necessary authorizations. Usingcomposite roles, the employee role is mixed with other specialist roles(this does not apply to roles for external users, such as vendor and bidder).

Managers are responsible for approving the requirement coverage requestsof their employees, including the approval of settlements for procurementcards. Managers can change the attributes for all employees within theirorganizational unit. Provided SAP Business Information Warehouse (SAPBW) is available, the manager can also use specific analysis functions. Themanager role holds only one more transaction than the employee role, buthas more authorizations to perform management tasks within SRM.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Professional users need SRM for their daily tasks and form part of the valuechain in which they are working.

Content managers are responsible for importing and processing productdata from external content providers and exporting the data to a SRMpurchasing catalog.

Operational purchasers can create public and restricted bid invitations andmanage the bids received. They can process incomplete purchase orders,view contracts, and approve and manage business partner data. ProvidedSAP BW is available, they can also use specific analysis functions.

Strategic purchasers create public and restricted bid invitations andmanage the bids received. They can process incomplete purchase orders,create and process contracts, and approve and manage business partner data.Provided SAP BW is available, they can also use specific, enhanced analysisfunctions, such as strategic sourcing.

Components planners process maintenance and service orders, and planthe materials needed to execute these orders

System administrators are responsible for setting up and monitoring theSAP Enterprise Buyer system. They are responsible for analyzing andsolving problems that occur in the system itself in the interfaces to thebackend system and in the applications. System administrators also manageuser master records for internal employees and external business partnersand change the attributes for all employees within their organizational unit.

Professional users with limited authorization access mySAP SRM periodicallyduring the week and do not form part of the value chain in which they are working.

Purchasing assistants and other designated employees, such as secretaries,perform central functions. They can, for example, search for requiredproducts in catalogs and order them for a limited group of persons.

Internal dispatchers (formerly called recipients) work at the loadingpoint, receiving goods for purchase orders and distributing them to theactual recipients. They can also confirm goods receipt and service entriescentrally and verify invoices. Provided SAP BW is available, they can alsouse specific analysis functions.

Accountants are responsible for entering invoices in SAP Enterprise Buyerin cases where ordinary employees, secretaries, office assistants, or vendorshave not already done so. Provided SAP BW is available, they can also usespecific analysis functions.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Suppliers are considered as being third-party employees and are generallycategorized as professional users with limited authorization

Bidders and vendors provide the goods and services that are procured.In mySAP SRM, suppliers can confirm that they have delivered goods orperformed services. They can also enter invoices for their purchase orders.Competing with other suppliers, they can submit bids in response to bidinvitations.

Supplier administrators assign roles and maintain supplier settings,customer data, and product data.

mySAP SRM Technical ScenariosmySAP SRM is a solution that you can implement in a heterogeneous systemenvironment that includes SAP systems and/or other enterprise resource planningsystems as backend systems. You must have the Financial Accounting andControlling components in your system environment. There are different businessscenarios that you can apply depending on your role as a user and the kindof business you wish to conduct using mySAP SRM. Each of these businessscenarios can be deployed using one of four different technical scenarios.

The scenarios you choose depends on the system in which your purchasingdepartment wants to work and, consequently, where the follow-on documentsare to be created.

You can also run these scenarios in parallel. To do this you choose, on the basis ofthe product category, how you want the goods or services to be processed. Thissuits customers who already have a productive materials management backendsystem, but wish to handle the procurement of some supplies locally and otherswithin the backend system. This makes sense, for example, if you have alreadydefined a communication interface, such as EDI, to a particular supplier.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 13: Classic Scenario

The Classic Scenario

The shopping cart is created and approved in SAP Enterprise Buyer. Theremainder of the procurement process takes place in the backend ERP system(s)and all other follow-on documents, such the purchase order, goods receipt/serviceentry sheet and invoice, are located there. With SAP Supplier Self-Services,you have partial supplier involvement for the operational procurement businessscenarios when buying materials. There is no support for services.

This scenario suits customers:

Who want a wide user group, for example employees not necessarilyworking in the purchasing department, to be able to enter their requirementsquickly and easily. SAP Enterprise Buyers functionality and ease ofnavigation allow this, as it requires only minimal training

Who want their purchasing department to operate solely with thefunctionality offered by the backend system(s)

For whom a transfer of purchasing activities to SAP Enterprise Buyer isnot viable


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 14: Extended Classic Scenario

The Extended Classic Scenario

The shopping cart is created in SAP Enterprise Buyer. The purchase order andfollow-on documents are also created there and then replicated to the backendsystem. The purchase order in SAP Enterprise Buyer is the leading purchase orderand cannot be changed in the backend system. Goods receipts and invoices can bepre-entered in SAP Enterprise Buyer or entered directly in the backend system.With SAP Supplier Self-Services, you have partial supplier involvement for allyour operational procurement scenarios. In these scenarios, you have supplierinvolvement for the purchase order and the purchase order response.


Who want their purchasing department to save time and money by using thestreamlined purchasing functionality of SAP Enterprise Buyer

Who want to use the full sourcing capabilities offered by SAP EnterpriseBuyer, yet who also want to be able to confirm and invoice direct materials

Who want the flexibility of being able to pre-enter confirmations andinvoices in SAP Enterprise Buyer


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 15: Standalone Scenario

The Standalone Scenario

The shopping cart and purchase order are processed directly in SAP EnterpriseBuyer. You have no materials management functions in your ERP system and,instead, use those in SAP Enterprise Buyer for all procurement processes.The final invoice is sent to a backend accounting system. With SAP SupplierSelf-Services, you have complete supplier involvement for all your operationalprocurement scenarios.


Who do not have a productive materials management system and want tohandle the entire process locally within SAP Enterprise Buyer, integratingonly to an accounting system

Who do not necessarily want to create product master data, but rather allowsuppliers to maintain their own product data in their catalog, thus relievingthe purchasing department of content management responsibilities

Who want to alleviate the backend system of all purchasing activities bytransferring a specific group of users to SAP Enterprise Buyer

Who want to use the streamlined purchasing functionality of SAP EnterpriseBuyer for specific product categories, typically, indirect materials, andservices

Who want to use Procurement Cards to order items in SAP Enterprise Buyer.

The following table gives an overview of the differences between each of thesescenarios in terms of where the main processes occur:


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Enterprise Buyer Technical ScenariosClassic Extended Classic Standalone

Shopping Cart SAP EnterpriseBuyer

SAP EnterpriseBuyer

SAP EnterpriseBuyer

Approval SAP EnterpriseBuyer

SAP EnterpriseBuyer

SAP EnterpriseBuyer

Purchase Order Backend system SAP EnterpriseBuyer (leadingsystem) andbackend system

SAP EnterpriseBuyer

Goods Receipt Backendsystem (can bepre-entered inSAP EnterpriseBuyer)

Backendsystem (can bepre-entered inSAP EnterpriseBuyer)

SAP EnterpriseBuyer (noaccounting postingmade in backendsystem)

Invoice Backendsystem (can bepre-entered inSAP EnterpriseBuyer)

Backendsystem (can bepre-entered inSAP EnterpriseBuyer)

SAP EnterpriseBuyer (accountinginformation sent tobackend system)


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercise 2: Self-Service ProcurementCycle

Exercise ObjectivesAfter completing this exercise, you will be able to: Perform a basic self-service procurement scenario

Business ExampleTo gain a basic understanding of the e-Procurement process, you want to testEnterprise Buyer by ordering an item from the internal catalog, posting theconfirmation of receipt, and entering the vendors invoice.

Task 1: Create a Shopping Cart Using the WizardAs an employee, use the shopping cart wizard to order an item from the internalcatalog.

1. Order a two-pack of AA alkaline batteries from the vendor ARAMI-15 usingthe BugsEye (own window) catalog.

2. Check the status of the shopping cart and make a note of the resultingfollow-on document.

Task 2: Express ConfirmationPerform confirmation of goods receipt using the express confirmation feature.

1. You have now received the batteries you ordered. Enter a confirmation ofthis receipt.

Task 3: Invoice EntryEnter a vendors invoice in Enterprise Buyer.

1. Enter the invoice from the vendor that supplied the batteries.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solution 2: Self-Service ProcurementCycleTask 1: Create a Shopping Cart Using the WizardAs an employee, use the shopping cart wizard to order an item from the internalcatalog.

1. Order a two-pack of AA alkaline batteries from the vendor ARAMI-15 usingthe BugsEye (own window) catalog.

a) Launch SAP Enterprise Buyer via the Web browser and enter thefollowing information

User ID SAPSRM-##Password learn (reset to learn)Client 300

Choose Logon. If password learn does not work, enter init and changeit to learn..

b) Select Shop from the menu options.

Hint: Do not use any of the Microsoft Internet Explorerstandard buttons, such as Back , Forward, or Refresh ,as thiswill cancel your transaction in SAP Enterprise Buyer. Only usethe menu options and buttons within SAP Enterprise Buyer.

c) Select the BUGS EYE 4.0 (OWN WINDOW) catalog.

d) Enter AA batteries in the Search text field and then choose Search.

e) Choose the Add to Shopping Cart icon for Alkaline Batteries, "AA",2/Pack from the vendor ARAMI-15..

The item has been added to the BugsEye shopping cart.

f) Chose Order Items.

The item has been transferred from the catalog to the shopping cartin SAP Enterprise Buyer.

g) Choose Continue.

h) Enter Batteries## for Name of Shopping Cart.

i) Choose Order.



Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


2. Check the status of the shopping cart and make a note of the resultingfollow-on document.

a) Select Check Status from the menu options.

b) Expand the shopping cart named Batteries##

c) Choose the description Alkaline Batteries, "AA", 2/Pack.

d) Scroll down to Follow-On Documents and note the result.

There should be a purchase order as the follow-on document. This POwas created in the backend system.

Hint: There is a report running in EBP every two minutesthat updates the shopping carts when follow-on documentsare created on the backend ERP system. If you dont see aPO number right away, wait a minute or two and repeat stepsA-D to refresh the data.

Task 2: Express ConfirmationPerform confirmation of goods receipt using the express confirmation feature.

1. You have now received the batteries you ordered. Enter a confirmation ofthis receipt.

a) Choose Check Status from the menu options.

b) Expand the shopping cart named Batteries##.

c) Choose the Create Confirmation icon under the Actions column.

You will receive a message that your confirmation was saved. ClickOK to acknowledge this message.

d) Choose the description Alkaline Batteries, "AA", 2/Pack.

e) Scroll down to Follow-On Documents and note the result.

There should be a confirmation in the list of follow-on documents.This is the number of the resulting material document created in thebackend system.



Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Task 3: Invoice EntryEnter a vendors invoice in Enterprise Buyer.

1. Enter the invoice from the vendor that supplied the batteries.

a) Choose Enter Invoice/Credit Memo from the menu options.

b) Choose the Enter Invoice icon.

c) Select Calculate Total Amount.

d) Enter 1700-## as the vendors invoice number.

e) Choose the Post button.

You will receive a message that an invoice was created for the purchaseorder. Click OK to acknowledge this message.

f) Choose Check Status from the menu options.

g) Choose the description Alkaline Batteries, "AA", 2/Pack.

h) Scroll down to Follow-On Documents and note the result.

There should be an invoice in the list of follow-on documents. This isthe number of the resulting invoice document created in the backendsystem.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Lesson Summary

You should now be able to: Explain the SRM business scenarios Describe the roles utilized in different business scenarios Explain the different SRM technical scenarios


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit Summary SAPSRM

Unit SummaryYou should now be able to: Describe the SRM application components and their purposes Describe the SRM integration components and their purposes Explain the integration of SRM with other solutions Explain the SRM business scenarios Describe the roles utilized in different business scenarios Explain the different SRM technical scenarios


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit 2mySAP SRM Operational Procurement

Unit OverviewThis unit will introduce you to self-service procurement, plan-driven procurementand service procurement within SRM.

Unit ObjectivesAfter completing this unit, you will be able to:

Explain business partners Explain the use of product masters Describe role of product categories Explain the role of the Organization Plan in Enterprise Buyer Describe the different ways to create a shopping cart in SAP Enterprise Buyer Explain the purpose and value proposition for using catalogs in SAP

Enterprise Buyer Describe the approval workflows for shopping carts Outline the different scenarios for confirmations in SAP SRM Define the roles and their functions for processing confirmations Explain the different approval workflows available for confirmations Outline the different scenarios for invoices in SAP SRM Define roles and their functions for processing invoices Explain the different approval workflows available for invoices Describe the Plan Driven Procurement process within SRM Explain the manual direct procurement process flow in SAP Enterprise Buyer Explain the sourcing integration with direct procurement Describe the process for ordering temporary labor within mySAP SRM Explain the roles in SAP Enterprise Buyer that can order temporary labor Detail the options for entering confirmations for services Process Local Purchase Orders in Enterprise Buyer Create Local Purchase Orders without reference to a Shopping Cart.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit 2: mySAP SRM Operational Procurement SAPSRM

Unit ContentsLesson: SRM Master Data and Organization Plan .. . . . . . . . . . . . . . . . . . . . . . . . . 37

Exercise 3: Create a New User in SAP Enterprise Buyer withAdministrator .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Exercise 4: Check the Availability of a Product. . . . . . . . . . . . . . . . . . . . . . . . . . 53Exercise 5: Create a Shopping Cart with Local and Back-End ProductCategories ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Lesson: Self-Service Procurement: Shopping Carts.. . . . . . . . . . . . . . . . . . . . . . . 65Exercise 6: Create a Shopping Cart as an Employee .. .. . . . . . . . . . . . . . . 83Exercise 7: Create a Shopping Cart as a Purchasing Assistant . . . . . . 91Exercise 8: Create a Shopping Cart on Behalf of Another User ... . . . 95Exercise 9: Review Shopping Cart.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Exercise 10: Approving a Shopping Cart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Lesson: Self-Service Procurement: Confirmations.. . . . . . . . . . . . . . . . . . . . . . . .109Exercise 11: Create a Confirmation as a Central Receiver . . . . . . . . . . .117Exercise 12: Enter a Goods Receipt in the ERP system.... . . . . . . . . . .121

Lesson: Self-Service Procurement: Invoices .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Exercise 13: Create an Invoice as an Accountant . . . . . . . . . . . . . . . . . . . . .135Exercise 14: Enter an Invoice in the ERP system.... . . . . . . . . . . . . . . . . . .139

Lesson: Plan Driven and Manual Direct Procurement ... . . . . . . . . . . . . . . . . . .145Exercise 15: Manual and Plan-Driven Direct Procurement .. . . . . . . . . .153

Lesson: Service Procurement.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162Exercise 16: Create Request for External Services .. . . . . . . . . . . . . . . . . .171Exercise 17: Time entry for Temporary Labor .. . . . . . . . . . . . . . . . . . . . . . . . .175Exercise 18: Procurement of External Services in Classic Scenario 177

Lesson: Operational Purchasing... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182Procedure: Processing Local Purchase Orders ... . . . . . . . . . . . . . . . . . . . . .187


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

SAPSRM Lesson: SRM Master Data and Organization Plan

Lesson: SRM Master Data and Organization Plan

Lesson OverviewIn this lesson, you will learn about the various master data utilized in SRM.


Explain business partners Explain the use of product masters Describe role of product categories Explain the role of the Organization Plan in Enterprise Buyer

Business ExampleYour company needs to utilize the vendors and materials that already exist in itsERP system within SAP Enterprise Buyer. Therefore, you need to explore theoptions for creating and utilizing this master data in SAP Enterprise Buyer. Youalso need to understand the role of the Organization Plan in Enterprise Buyer.

Business PartnersSAP Enterprise Buyer uses the SAP Business Partner concept. An internalor external business partner is created in Enterprise Buyer for every person,organization, or group of people that could be involved in a business transaction.Within the context of business transactions (a bid invitation or a purchase order,for example) business partners can adopt various partner functions, as long as theyhave fulfilled the relevant requirements.

Internal business partners are created for organizational units or employees inthe organizational structure (with the exception of the location). When a businesspartner is created for an employee, this business partner is assigned to the relevantorganizational unit within the organizational structure. The employee relationshipto the business partner of the associated organizational unit is created for theinternal users business partner. For example, when creating the business partnerfor employee LOUIE, the employee relationship to the business partner of theorganizational unit MAINTENANCE is defined. The employee relationshipcovers the employees business address that is used when goods are delivered,for example.

External business partners with vendor or bidder roles are created in theorganizational structure underneath the central organizational unit for a vendoror bidder. For every external employee of a vendor or bidder, a contact personis created in addition to the business partner for that company. When you createa bidder or a vendor you can also define a contact person. An EBP user is then


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


created for the contact person. You can then send the user his/her user ID andpassword via e-mail. The relationship of the contact person covers the businessaddress of the corresponding contact person.

For example, a vendor, purchasing group, and user can be included in a shoppingcart before it can be saved. Each of these three elements will have its own businesspartner record maintained in the Enterprise Buyer system.

Figure 16: Business Partners in Shopping Cart

Each business partner is assigned a role that describes its purpose. Businesspartners can be linked to other business partners to describe their individualrelationships. Some roles in the EBP system include:

Vendor Bidder Contact person Employee Organization Unit

Business partners can be linked to other business partners to describe theirindividual relationships. Two examples of relationships in EBP are:

Organization Unit has the Employee Vendor has Contact person


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


For example, a person is hired by a companys purchasing department. A businesspartner is created in SAP Enterprise Buyer for this new worker and the masterrecord is assigned to the role of employee. Since this purchasing department hasits own business partner, the two business partner records are linked using theHas the Employee relationship.

Note: In SAP Enterprise Buyer, business partners that represent abusiness organization, such as departments, employees, vendors, orvendor employees (contacts), can be maintained in the Maintain BusinessPartner or Maintain Organizational Model.

Figure 17: Business Partner Relationships: Vendor and Contact Person

Maintaining a Vendor Master via a BrowserCreation In SAP Enterprise Buyer, system administrators or professionalpurchasers can use the Manage Business Partners application to manage masterdata, such as company data for vendors and bidders.

If the company is not yet registered, external employees can submit a registrationapplication for the company as a vendor, bidder, or portal bidder, and can submita registration application for themselves as a contact person. Registrationapplications are forwarded via a workflow to the responsible purchaser or systemadministrator, who can approve or reject the application. If the application is


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


approved, the purchaser must create the appropriate master data or user data.Contact persons can also submit additional employees from their company to beregistered as contact persons in SAP Enterprise Buyer.

Figure 18: Creating a Business Partner

Change, Display, and Delete Purchasers and system administrators can chooseto display or process a bidder, vendor, portal provider, or contact person. Dataincludes the Dun & Bradstreet number, your account number at the vendor, andmultiple addresses. Bidders may be adapted as vendors. Business partners canbe deleted if they are not being used.

Addresses All addresses and address types are saved with the business partner.You can only add standard addresses to the system via the master data maintenanceoption Manage Business Partner.

Purchasers can set ordering, ship-from, and invoicing party addresses for vendors.The system administrator can also set the ship-to address and the invoice recipientaddress for your own company. To do so, choose Edit Internal Addresses or EditExternal Addresses from the initial screen.

Vendors can be given permission to change their own addresses.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Address Type DescriptionOrdering The purchase order goes to this addressShip-from The goods are sent from this addressInvoicing party The invoice is sent from this addressShip-to Goods are delivered hereInvoice recipient The invoicing party sends the invoice

hereGoods recipient Internal address of the receiving party

Figure 19: Business Partner Data Maintenance

Replicating VendorsThere are transactions and programs in Enterprise Buyer that facilitate thereplication of vendor data from R/3. The prerequisites are:

Enterprise Buyer system: The organizational plan must be set up, and mustcontain an organizational unit to assign the external business partner. Eachpurchasing organization must be in an organizational unit.

Backend system: The vendor must be assigned to a purchasing organization.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Your system administrators use standard reports and transactions to replicatethe data to SAP Enterprise Buyer. You can change the data after replicating it.However, you should not copy over any vendors.

BBPGETVD: This transaction copies the vendor master data needed by SAPEnterprise Buyer. You can specify whether the vendor numbers are to be copiedfrom the internal or back-end systems. The logical system is part of the key todistinguish between multiple back-end systems.

BBP_UPLOAD_PAYMENT_TERMS: You use this report to copy the paymentterms used by vendors from the back-end system.

BBP_VENDOR_SYNC: You can schedule this program as a job to automaticallysynchronize vendor master data. This program only starts the synchronizationfor modified or added vendor masters.

Maintaining Internal Business Partners via a BrowserEmployee business partners can be created via a Web browser. Employees canbe given the option to create their own SAP Enterprise Buyer user records. Anadministrator possesses the ability to both create and maintain the various userrecords.

Figure 20: Create Employees with Administrator


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


ProductsA product is a master record in SAP Enterprise Buyer that either represents a good(such as office supplies or a computer) or a service (such as maintenance of acomputer). The product master provides information on the item being purchased.SAP Enterprise Buyer allows transactions to include goods or services that do ordo not have product masters.

This information is stored in individual product master records, and can include:

Header information Description Product category General and purchasing data Units of measure

Replicating Data and Content ManagementMaterial master records from SAP R/3 can be transferred to the product masterby the content manager or system administrator using middleware. Customizinginformation, which is transferred first, determines how the product ID is stored inthe product master and which data can be created for a product. To check whetherthe material types, material groups, and service categories have arrived in theEnterprise Buyer system, call transaction COMM_HIERARCHY. You shouldsee all the required data.

When initially downloading business objects from your SAP R/3 back end, youcan optionally define filters to restrict the variety of materials to be replicated. Tocheck products, use transaction COMMPR01 or choose Master Data Products Product Workbench from the SAPCRM menu in SAP Enterprise Buyer.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 21: Products in the Shop Transaction.

Product CategoriesProduct categories are a way to group individual products or services togetheraccording to different criteria (for example, computers, electrical, or officesupplies). The primary function of the product category is to determine in whichsystem a purchasing document will be created after an SAP Enterprise Buyershopping cart is saved.

Product categories originate in either SAP Enterprise Buyer or SAP R/3. Productcategories are either manually maintained in the Enterprise Buyer system or theyare SAP R/3 material groups that are replicated to Enterprise Buyer. TheMaterialgroup field is required in material master and service master records in SAP R/3.Product categories must be included on each line of a shopping cart whether thereis a product master or free text description. Product category configuration rulesthat are established in SAP Enterprise Buyer determine the following:

Product categories determine the target system for follow-on documents. Combined with account assignment categories, product categories can

determine default account assignments.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 22: Product Categories in Shopping Cart

For example, electronics and office materials are two available product categories.Electronics is configured to create purchasing documents in the back-end system,which is SAP R/3. Office materials is configured to create local purchasingdocuments in the Enterprise Buyer system. A shopping cart is created with twoline items. Line item one is a calculator, which is assigned to product categoryelectronics, and line item 2 is pens, which is assigned to product category officematerials. After the cart is saved and approved, a purchase order is created inSAP R/3 for the calculator and another is created locally in Enterprise Buyerfor the pens.

Organization PlanThe Organization Plan in Enterprise Buyer serves many important functions.It is mapped to the structure of your Organization in terms of companies,locations, departments and groups. A hierarchy of Organization Units are createdto represent these entities. The users in Enterprise Buyer are assigned to oneof the Organization Units. The Organization Plan must be maintained by theAdministrator as the structure of your enterprise changes. The Organization Plancan be created and maintained manually in Enterprise Buyer or may be replicatedfrom an SAP R/3 Human Resources Organization Structure.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 23: Organization Plan in Enterprise Buyer

Attributes are predefined values that are maintained for the various OrganizationUnits.

Company Codes Plants Storage Locations Account Assignment Categories Cost Centers Catalogs Purchasing Document Type

Attributes maintained at the Root Node in the Organization Plan are usuallyinherited by the nodes below it. Changes or additions to inherited attributes atthe lower nodes is also possible. The attributes are utilized by users creatingshopping carts. It may be possible for a user to have multiple values for a giveattribute. For example, a user may more than one account assignment category tochoose from when creating a shopping cart, such as Cost Center, Asset and WBSElement. In this case they could set one of these as their default and choose fromthe other options as needed.

Enterprise Buyer automatically determines the responsible purchasing organizationand purchasing group for every shopping cart item. This is made possible bythe assignment of organization responsibility to every purchasing group. Forexample, purchasing group 010 is assigned responsibility for department 1, whilepurchasing group 011 is assigned responsibility for department 2. In addition


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


to assigning organization responsibility you may also assign Product Categoryresponsibility to the purchasing groups. If the system determines there is morethan one possible purchasing group for a shopping cart item the requestor wouldhave the options of choosing one of them.

Depending on what technical scenarios you implement, you may have some LocalPurchasing Groups who are responsible for processing Local Purchase Orders. Inthis case you will need to assign users with a Purchaser role to these PurchasingGroups. These Purchasers will be assigned to the Local Purchase Orders created,depending on their Organizational and Product Category responsibilities. ThesePurchasers will be responsible for processing the Local Purchase Orders andRequirements that are incomplete.

Figure 24: Purchasing Group Responsibility

SAP Business Workflow utilizes the Organization Plan to determine theresponsible approver(s) for shopping carts and new users created using theself-service scenario. For example, if you are using the standard one stepworkflow for shopping cart approval, the system determines the approver to be themanager of the requestors organization unit. In the case of the two step workflowfor shopping cart approval, the first approver is the manager of the requestorsorganization unit and the second approver is the manager at the next level of theorganization structure. If you are using the ad-hoc feature, it may be possible for arequestor to change the approver(s) determined by the system.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly



Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercise 3: Create a New User in SAPEnterprise Buyer with Administrator

Exercise ObjectivesAfter completing this exercise, you will be able to: Create new users assigned to organizational units and roles that determine

how a person can work within Enterprise Buyer

Business ExampleYou are a Web administrator and you need to add a new user to the system.

Task: Create a New UserAs a Web administrator, create an employee user for a department within Phoenixorganization via the Web browser.

1. As a Web administrator, create an employee user with the following data:User ID: TEAM##; Name: Mr. Grover Cleveland; Country: USA; Building:1, Room number: 1; Telephone number: 645-452-2511; Fax number:645-452-2288; e-mail: [email protected]; initial password: init; department:PH1 Operations 1; User role: SAP_BBP_STAL_EMPLOYEE.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solution 3: Create a New User in SAPEnterprise Buyer with AdministratorTask: Create a New UserAs a Web administrator, create an employee user for a department within Phoenixorganization via the Web browser.

1. As a Web administrator, create an employee user with the following data:User ID: TEAM##; Name: Mr. Grover Cleveland; Country: USA; Building:1, Room number: 1; Telephone number: 645-452-2511; Fax number:645-452-2288; e-mail: [email protected]; initial password: init; department:PH1 Operations 1; User role: SAP_BBP_STAL_EMPLOYEE.

a) Launch Enterprise Buyer via the Web browser and enter the followinginformation:

User ID WEBADMINPassword learnClient 300

Choose Logon.

b) Select Manage User Data.

Hint: Do not use any of the Microsoft Internet Explorerstandard buttons, such as Back, Forward, or Refresh, as thiswill cancel your transaction in Enterprise Buyer. Only use themenu options and buttons within Enterprise Buyer.

c) Choose Create users.

d) Enter TEAM## in the User ID field

.

e) Enter Dear Mr. or Dear Ms. in the User ID field.

f) Enter Grover in the First name field.

g) Enter Cleveland in the Last name field.

h) Enter USA in the Country field.

i) Enter BLDG1 in the Building code field.

j) Enter 1 in the Room number field.

k) Enter 645-452-2511 in the Telephone number field.Continued on next page


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


l) Enter 645-452-2288 in the Fax number field.

m) Enter [email protected] in the E-mail address field.

n) Enter init in the New Password field.

o) Enter init in the New Password field.

p) Select PH1 Operations 1 in the Organizational Unit field, using thescroll down button

q) Select SAP_BBP_STAL_EMPLOYEE in the User Role field.

r) Choose date format and decimal notation of your choice

Hint: For existing users date formats and decimal notationscan be changed by going to Settings Address Data

s) ChooseSave.

This message will appear at top of screen if it saved:SUCCESSFULUser TEAM## created.

t) Choose Log off.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly



Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercise 4: Check the Availability of aProdu