Srm210 en Col92 Fv Part a4

SRM210 SAP SRM Server Configuration SAP SRM

Date Training Training Center Instructors

Education Website

Participant Participant Handbook Handbook Course Version: Version: 92 Course Duration: 5 Day(s) Material Number: 50095902

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

Copyright Copyright © 2009 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without without the express express permission permission of SAP AG. The information information contained contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Trademarks •

Microsoft®, Microsoft®, WINDOWS®, WINDOWS®, NT®, EXCEL®, EXCEL®, Word®, PowerPoint® PowerPoint® and SQL Server® Server® are registered trademarks of Microsoft Corporation.

•

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

•

ORACLE ORACLE® ® is is a regist registere ered d tradema trademark rk of ORACLE ORACLE Corpor Corporati ation. on.

•

INFORMIX INFORMIX®-OnL ®-OnLine ine for SAP and INFORMIX INFORMIX® ® Dynamic Dynamic ServerTM ServerTM are registered registered trademarks of Informix Software Incorporated.

•

UNIX®, UNIX®, X/Open®, X/Open®, OSF/1®, OSF/1®, and Motif® Motif® are registered registered trademarks trademarks of the Open Group. Group.

•

Citrix®, Citrix®, the Citrix Citrix logo, ICA®, Program Program Neighborhood Neighborhood®, ®, MetaFrame®, MetaFrame®, WinFrame® WinFrame®,, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

•

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

•

JAV JAVA® is a regis register tered ed trad trademar emark k of Sun Micros Microsyst ystems ems,, Inc. Inc.

•

JAV JAVASCRIPT® ASCRIPT® is a register registered ed trademark trademark of Sun Microsy Microsystems, stems, Inc., used under license license for for technology invented and implemented by Netscape.

•

SAP, SAP, SAP Logo, R/2, RIVA, RIVA, R/3, R/3, SAP SAP ArchiveLin ArchiveLink, k, SAP SAP Business Business Workflow orkflow, WebFlow WebFlow,, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

Disclaimer THESE MATERIALS MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, INDIRECT, SPECIAL, INCIDENTAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, WHATSOEVER, INCLUDING WITHOUT LIMITATION LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.

g2009717112754

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

Typographic Conventions American American English is the standard used in this handbook. handbook. The following following typographic conventions are also used. Type Style

Description

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal and external.

2009

Example text

Emphasized Emphasized words or phrases phrases in body text, titles of graphics, and tables

EXAM EXAMPLE PLE TEXT TEXT

Name Namess of eleme element ntss in the the syste system. m. These These inclu include de report names, program names, transaction codes, table names, and individual individual key words of a programming programming language, when surrounded by body text, for example SELECT and INCLUDE.

Exampl Example e text text

Screen output. output. This This includes includes file and directory directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.

Exampl Example e text text

Exact user entry. entry. These are words and characters that you enter in the system exactly as they appear in the documentation.

text>

Variable user entry. entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© 2009 SAP AG. All rights reserved.

iii

About This Handbook

SRM210

Icons in Body Text The 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 Indicates that the item is displayed displayed in the instructor's instructor's presentation.

iv


2009

Contents Course Overview ....... ....... ....... ....... ....... ...... ....... ....... .. vii Course Goals ....... ........ ........ ........ ........ ....... ........ .....vii .....vii Course Ob Objectives ... .... ... .... .... .... .... .... .... ... .... ... .... .... .vii

Unit 1: SAP SRM Server ................................................. 1 SAP SRM ........ ....... ........ ........ ....... ........ ........ ........ .2

Unit Unit 2: Back ack-End End Int Integr egrati ation ... .... ... .... ... .... ... .... ... ... .... ... . 19 Back-End Integration .... ... .... .... .... .... .... .... ... .... ... .... .... 20 .... 20 Back Back-E -En nd Inte Integ grati ratio on Exerc xerciise. .. ... ... .. ... .. ... ... .. .. ... .. ... ... . 39

Unit 3: Organizational Structure and User Management ....... 67 Organizational Plan... .... .... ... .... ... .... ... .... ... .... .... .... .... 68 .... 68 Org Organi anizati zatio onal nal Plan lan Exe Exercis rcise... e... .. ... ... .. ... ... .. ... .. .. ... .. .. ... .. 78 .. 78 User Ma Maintenance .... .... .... ... .... ... .... .... .... ... .... .... .... ... 94 ... 94 User ser Main Mainte ten nance nce Exe Exerci rcise .... .. ... .. ... ... .. ... .. ... .. ... .. ... ...108 ... 108

Unit 4: Workflow ....... ....... ....... ....... ....... ...... ....... ....... .125 Workflow . ....... ........ ........ ....... ........ ........ ........ .......126 .......126 Workflow Exe Exercise .... .... .... ... .... ... .... .... .... ... .... ... .... ...143 ...143

Unit 5: Master Data .....................................................157 ..................................................... 157 Vendor Replication..... ... .... ... .... ... .... .... .... ... .... ... .... ...158 ...158 Vend endor Rep Replica licati tion on Exer Exerci cis se.... .. ... .. ... ... .. ... .. .. ... ... .. ... .. .166 Product Master.......................................................177 Master.......................................................177 Product Master Exercise............................................185 Exercise............................................185

Unit 6: Connection to Catalogs......................................197 Catalogs...................................... 197 Connection to Catalogs .............................................198 .............................................198 Conn Connec ecti ting ng the the SRM-M SRM-MDM DM Cata Catalo log g Exerc Exercis ise. e. .. .. .. .. .. .. .. .. .. . 215

Unit Unit 7: 7: Self Self-S -Ser ervi vice ce Pro Procu cure reme ment nt .... ... .. .. ... .. .. .. ... .. .. ... .. .. .221 Shopping Carts.......................................................222 Carts.......................................................222 Shopping Carts Exercise............................................228 Exercise............................................228 Direct Pr Procurement .... ... .... .... .... ... .... .... .... .... .... .... ... .234 Dire irect Proc Procur urem emen entt Exe Exercis rcise e ... .. ... ... .. ... .. ... ... .. .. ... .. ... ...238 ...238 Confi onfirm rma atio tion of Goo Goods Rece Receip iptt .. ... .. ... ... .. ... .. .. ... ... .. ... .. .244 Confirmation of Goods Receipt Exercise ......................... 248 Invoice.................................................................254 Invoice................................................................. 254

2009


v

Contents

SRM210

Invoice Exercise......................................................261 Exercise......................................................261

Unit 8: Operational and Strategic Procurement .................267 ................. 267 Proc Proces essi sing ng Pu Purch rchase ase Orde Orders... rs... .. ... ... .. ... .. ... ... .. ... .. .. ... .. .269 Proc Proces ess s Purc Purcha hase se Ord Order ers s Exer Exerci cise se ... .. .. .. .. .. .. .. .. .. .. .. .. .. ..276 .. 276 Sourcing...............................................................281 Sourcing............................................................... 281 Sourcing Exe Exercise....... ... .... .... .... .... .... .... ... .... .... .... ...303 ...303 Sou Sourci rcing an and Bid Bidding ing Engi Engine ne .. .. ... ... .. ... .. ... ... .. ... .. ... ... .. 311 311 Supplier List Exercise (Optional)...................................318 (Optional)................................... 318 Exte Extend nded ed Clas Classi sic c Scen Scenar ario io (Opt (Optio iona nal) l) .. .. .. .. .. .. .. .. .. .. .. .. .. ..322 .. 322

Unit 9: Procurement of External Requirements .................335 ................. 335 Procurement of External Requirements...........................336 Requirements........................... 336 Procurement of External Requirements Exercise ............... 345

Unit 10: Service Procurement........................................351 Procurement........................................ 351 Procurement of External Staff (Optional) ......................... 352 Integration with ERP Service Procurement ......................356 ...................... 356 Classic Service Procurement Exercise ...........................364 ........................... 364

Unit Unit 11: Adm Administ istrat ration ion .... ... ... .... ... .... ... .... ... .... ... .... ... ...373 ... 373 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374

Unit 12: Appendix: Procurement for Public Sector (PPS).....407 (PPS)..... 407 APPENDIX: Procurement for Public Sector (PPS) . . . . . . . . . . . . . . 408

vi


2009

Course Overview The goal of this course is to supply the hands-on configuration experience needed for SAP SRM Server implementa implementation tion projects. projects. The SRM210 course is built on a business business process and role-based role-based framework. framework. Participants Participants will be introduced introduced to the various customizing tasks. This course covers the terminology and concepts behind the processes and roles, and the exercises enhance your understanding of the configuration aspect. Participants will be provided with a nearly “blank” client and will configure the client from start to finish. Note: This class has been developed on the following system versions:

SRM 7.0 SP 02 SAP NetWeaver 7.01 SP 03 SAP ERP 6.0 Enhancement Package 4 SP 02 SRM-MDM Catalog 3.0 SP 3

Target Audience This course is intended intended for the following audiences: audiences: •

Consul Consultan tants ts and project project team team m memb embers ers involv involved ed in in SAP SAP SRM SRM project projectss

•

Suppor Supportt or sys system tem admini administr strati ation on m memb embers ers respon responsibl siblee for for the the SAP SAP SRM SRM Server

Course Prerequisites Required Knowledge •

SCM5 SCM500 00 - Proces Processes ses in Procu Procure reme ment nt

•

Or basic basic kno knowle wledge dge of SAP ERP Materia Materials ls Manage Managemen mentt (MM) (MM)

•

SAPS SAPSRM RM - SAP SAP SRM SRM Over Overvi view ew

•

Or basi basicc know knowle ledg dgee of SAP SAP SRM SRM

Recommended Knowledge •

SAPEP SAPEP - SAP NetWeav NetWeaver er Portal Portal Fundam Fundament entals als

Course Goals This course will prepare you to:

2009

•

Build up basic technical technical and applicationapplication-specif specific ic knowledge knowledge to enable you to work successfully on an SRM implementation project

•

Custom Customize ize procur procureme ement nt process processes es with the SAP SRM Server Server


vii

Course Overview

SRM210

Course Objectives After completing this course, you will be able to:

viii

•

Explain Explain the procuremen procurementt processes processes and the responsible responsible roles within the SRM Server

•

Config Configure ure the SAP SRM Server Server to supp support ort Self-Se Self-Servi rvice ce Proc Procure uremen ment, t, Procurement of External Requirements, Service Procurement, Central Contract Management, and (Strategic) Sourcing

•

Monito Mon itorr bus busine iness ss process processes es with SAP SRM Server Server


2009

Unit 1 SAP SRM Server Unit Overview This unit provides a short overview of SAP SRM, the SRM Server concept, and the typical e-procurement processes with SAP SRM Server.

Unit Objectives After completing this unit, you will be able to: •

Expl Explai ain n the the syste system m land landsca scape pe of SAP SAP SRM SRM

•

Draft Draft the pos possib sible le inte integra gratio tion n scen scenari arios os with with the SAP SRM Server Server

Unit Contents Lesson: SAP SR SRM ........ ....... ........ ........ ....... ........ ........ ........ ..2 ..2

2009


1

Unit 1: SAP SRM Server

SRM210

Lesson: SAP SRM Lesson Overview This lesson provides an overview of the SAP SRM system landscape and the concept of SRM Server.

Lesson Objectives After completing this lesson, you will be able to: •

Explain the system landscape of SAP SRM

•

Draft the possible integration scenarios with the SAP SRM Server

Business Example Before installing the productive environment, some core team members need to set up a test environment with some of Phoenix Enterprise’s original organizational data. In a preconfigured client, delivered by SAP Education, they do their first review of the major processes within SRM Server. During this review, they also discuss the structure of the system landscape and the integration of SAP SRM Server into the SAP ERP back-end system.

Component and Scenario Overview

2


2009

SRM210

Lesson: SAP SRM

Figure 1: Evolution from BBP to SRM Server

Starting with Business to Business Procurement in 1999, there was an evolution from a catalog-based Employee Self-Service tool to SRM Server, and further to the multipurpose Supplier Relationship application SAP SRM (Supplier Relationship Management). The technical name of the central procurement component of SAP SRM 7.0 is SRM Server7.0. Note: SAP SRM 6.0 (SRM 2007) was only delivered to some ramp-up customers.This is not a commonly available version of SAP SRM! Note: According the SAP release strategy, there are currently no plans for SRM 8.0. Additional features will be supplied via enhancement packages.

2009


3


SRM210

Figure 2: SRM System Landscape

Note: PI means Process Integration. This is one of the SAP NetWeaver 7.0 components, and is also known as XI (Exchange Infrastructure). Caution: Some details of system communication (for example, RFC versus PI) are dependent on whether the ERP back end is running on ERP 6.0 enhancement package 4 or not.

4


2009

SRM210

Lesson: SAP SRM

Figure 3: SRM_PLUS Package

Note: SRM 7.0, deployed as add-on to ERP 6.0, uses different tables, data elements, and data structures than ERP. As a consequence, the same master data must exist twice; that is, a vendor from ERP also exists as a business partner in SRM. In order to keep the data synchronous, the data exchange between SRM and ERP must be ensured. The data distribution is executed via “Application Platform – Business Partner and Product Part” (Master Data Synchronization), and is performed synchronously and bidirectionally. When a data record for master data or business partner is updated in either system, the other system gets an update immediately. There is no queue for the communication that ensures system availability.

Information about the master data synchronization add-on can be found on the SAP Service Marketplace.

2009


5


SRM210

Figure 4: Enhancement Package Concept

Starting with ERP 6.0, SAP introduced the enhancement package concept. Enhancement packages (EHP) can be installed just like Support Packages. A enhancement package delivers new and additional features across all areas in ERP. To enable those functions, the administrator has to activate so-called “switches” in the IMG. The idea is to provide enhanced features without a system upgrade. There is only some limited testing necessary afterwards. The enhancement packages are currently reworked on a yearly basis (approximately). For additional information, please refer to http://service.sap.com/erp-ehp.

Figure 5: Enhancement Package Concept as of SAP Business Suite 7

6


2009

SRM210

Lesson: SAP SRM

With SAP Business Suite 7, SAP delivers a stable core consisting of ERP 6.0 EHP 4, SCM 7.0, SRM 7.0, CRM 7.0, and so on. Future changes will not be delivered by new product versions, but via enhancement packages. Note: The installation and usage of enhancement packages is not mandatory, but might be necessary for some special processes and functions. Hint: At the time this class was developed, EHP 1 for SAP SRM 7.0 and EHP 5 for SAP ERP 6.0 were in development. Do not forget to check the available enhancement packages for all of your SAP components before you start a project or system installation. Note: If you want to utilize special features, they might depend not only on one enhancement package of one component, but on the versions of several components. For example, some future scenarios might need EHP 1 on SAP SRM 7.0 and EHP 5 on SAP ERP 6.0.

Figure 6: Business Functions Delivered by Enhancement Packages

2009


7


SRM210

Although an enhancement package delivers new or changed features, the installation of the enhancement package does not change any system behavior. To activate the new or enhanced functions, you need to activate the corresponding business functions in the IMG or via transaction SFW5. Transaction SFW5 also contains links to documentation testing hints and release notes for every switch.

Figure 7: Switch Framework

Via transaction SFW5, the administrator enables switches to provide additional functions. Note: Some switches have dependencies, meaning they need the activation of additional switches or they exclude some other switches. Transaction SWF5 contains this information. Caution: Once you have activated a business function in your system, it is not reversible; you cannot undo the activation.

E-Procurement with SAP SRM Company employees are responsible for the procurement of the goods and services that they need for their work area. This takes the pressure off of the purchasing department, who in turn can concentrate on strategic tasks, such as contractual negotiation.

8


2009

SRM210

Lesson: SAP SRM

Figure 8: Common E-Procurement Process / Shopping Cart Process

Managers are involved in approval processes and reporting. Vendors might have system access via Supplier Self-Services (SUS) or SRM Server to work on their documents. They could create confirmations or enter invoices, for example. Employees check the documents that the business partner created and release (or reject) those documents.

2009


9


SRM210

Figure 9: SRM Server Offers More

Operational and strategic purchasers have access to additional transactions in SRM, such as purchase orders, contracts, and RFx. They are also able to create confirmations and invoices centrally, to shop on behalf of someone, or to create templates. Note: Especially together with SAP NetWeaver Portal 7 and SAP ERP 6.0 EHP 4, there are many cross-system options for professional purchasers.

10


2009

SRM210

Lesson: SAP SRM

Integration Scenarios

Figure 10: SRM Server Implementation Scenarios

The Classic Scenario

You implement SRM Server and one or more ERP systems. All shopping carts refer to materials management processes in your ERP back-end system. Your ERP system is the leading system. Goods receipts (confirmations) and invoices can be entered in SRM Server or in the ERP back-end system. The Extended Classic Scenario

The purchase order is created locally within SRM Server. If the data in the shopping cart is insufficient to generate a complete purchase order, the data is supplemented manually within SRM Server before being transferred to the back-end system. The purchase order in SRM Server is the leading purchase order. Goods receipts (confirmations) and invoices can be entered in SRM Server or in the back end. The Standalone Scenario

Your shopping cart items create local procurement documents only. This means that all follow-on processes, such as confirmation or invoice, have to be performed in SAP SRM Server. The Decoupled Scenario

This is not a scenario itself, but is a combination of more than one scenario, for example, a combination of the classic and standalone scenarios. Some items are handled locally, while others are transferred to the ERP back end.

2009


11


SRM210

Figure 11: Classic Scenario

You implement SRM Server and one or more back-end systems (SAP or non-SAP). All materials management is mapped in the ERP system. All materials management documents (such as purchase orders, goods receipts, service entry sheets, and invoices) exist in the back-end system. When the shopping cart is ordered, a workflow is triggered that checks whether approval is necessary. If approval is required, a work item is sent to the inbox of the relevant approver. If approval is not required, the necessary purchase requisitions, purchase orders, or reservations are created for the shopping cart. Which documents are created, and in which back-end system, depends on the information in the shopping cart and on the settings in Customizing for SRM Server. Hint: Although reservations are not mentioned in the graphics, it is also possible to create them from shopping cart items in the case of an internal procurement process.

12


2009

SRM210

Lesson: SAP SRM

Figure 12: Extended Classic Scenario

This scenario is an extension of the classic scenario. In the classic scenario, all materials management takes place in the back-end system; in the extended classic scenario, the complete procurement process takes place locally (in SRM Server). The purchase order is first created locally in SRM Server, and is transferred to the ERP system as soon as the document is complete and approved. If the data in the shopping cart is insufficient to generate a complete purchase order, the data is supplemented manually within SRM Server before being transferred to the back-end system. The purchase order in SRM Server, therefore, is the leading purchase order. The plant is the criterion used to split shopping cart items into different purchase orders because the purchasing organization is determined in the back-end system on the basis of the plant. Goods receipts (confirmations) and invoices can be entered in SRM Server or the back end. If the data in the shopping cart is sufficient to generate a complete purchase order, this purchase order can be copied to the back-end system automatically.

2009


13


SRM210

The following take place in the system landscape: •

Search for source of supply, pricing, and tax determination is performed in SAP SRM Server. Commitments are updated in the back-end system; account assignment and budget check are performed against the back-end system.

•

Data for the Business Information Warehouse is updated partly from SRM Server and partly from the back-end system. Purchase order data is updated from SRM Server; goods receipt and invoice data is updated from the back-end system.

Figure 13: Standalone Scenario

The customer does not have a productive materials management system and wants to handle the entire process locally within the SRM Server, integrating only to an accounting system. Accounting processes (including FI, CO, and AM) must still be handled by a back-end system. Validations and approvals are handled directly within SRM Server rather than in a back-end system. A shopping cart is created locally and is processed locally.

14


2009

SRM210

Lesson: SAP SRM

Figure 14: Decoupled Scenario

Say, for example, you have a productive MM back-end system, but want to handle parts of the process locally and other parts within the MM system. This means that specific shopping basket items create POs or requisitions with all follow-on processes in the back-end MM, while others are processed locally. For example, office supplies could be processed locally, while all items for plant maintenance goods are processed in the back-end system. Whether the system creates a PO in the back-end system or locally depends on the product category (or on a BAdI implementation). You have to define in customizing whether the product category is a local product category or a back-end product category. By using a BAdI, you can define your own rules. Note: The decoupled scenario is not a real scenario; it is a mix of different scenarios. The scenario determination normally takes place on shopping-cart-item level.

2009


15


SRM210

Lesson Summary You should now be able to:

16

•


•



2009

SRM210

Unit Summary

Unit Summary You should now be able to:

2009

•


•



17

Unit Summary

18

SRM210


2009

Unit 2 Back-End Integration Unit Overview This unit will cover the back-end integration of the SRM Server and the necessary customizing settings.


Explain the integration principles of an SAP ERP back-end integration

•

Perform the RFC and ALE settings

•

Schedule background jobs

•

Maintain product categories

•

Define back-end systems

•

Define number ranges and transaction types

•

Perform settings for accounting and tax calculation

Unit Contents Lesson: Back-End Integration.................................................. 20 Lesson: Back-End Integration Exercise....................................... 39

2009


19

Unit 2: Back-End Integration

SRM210

Lesson: Back-End Integration Lesson Overview In this lesson, you will learn about back-end integration of the SAP SRM Server system, including the necessary customizing settings.



Business Example Before starting the SAP back-end integration and configuration steps, the team members need to familiarize themselves with the SRM Server architecture. This includes the OCI interface as well as basic interfacing technology and integration principles such as ALE and RFC and PI/XML communication.

Architecture and Settings for System Integration

Figure 15: Component Architecture

SAP SRM Server is a typical SAP system that contains purchasing applications on SAP NetWeaver.

20


2009

SRM210

Lesson: Back-End Integration

While many administration tools are identical to SAP ERP running on the same SAP NetWeaver version, there are also additional features, for example, Business Rule Framework (BRF) workflow and own tables and structures. The Open Catalog Interface (OCI) describes the data exchange between the SRM Server and external catalog applications. It enables the transmission of selected goods and services from a catalog to the SRM Server. Connectivity to any electronic supplier directory: SAP SRM provides the Open Partner Interface (OPI) to search for matching vendors and as part of the supplier qualification process in strategic procurement. Hint: Until SAP SRM 5.0, the SAP Internet Transaction Server (ITS) was a mandatory component. As of SRM 7.0, SAP ITS is obsolete.

Figure 16: Architectural Flexibility

SRM Server can connect to multiple ERP instances. This is especially useful in larger corporations that have varied functionality spread over multiple servers. For example, different purchasing organizations are often set up on separate back-end systems within one company. SRM Server can communicate and coordinate document creation across these various instances.

2009


21


SRM210

Figure 17: Remote Function Call Principles

A Remote Function Call (RFC) is a function module (routine) call in a partner system. The caller is the RFC client and the called partner is the RFC server. Validation of accounting data– as well as, for example, the creation of purchase requisitions in the ERP back end – takes place via RFC. Caution: Some communications methods might change from RFC to SOA (PI/XML) as soon as you activate business function LOG_MM_P2PSE_1 within the SAP ERP 6.0 EHP 4 back- end.

22


2009

SRM210


Figure 18: Interfacing Technology: IDoc

ALE = Application Link Enabling IDoc = Intermediate Document ALE is a communication between logical systems. Logical systems can be, for example, SAP ERP systems or non-SAP systems. ALE distribution models are based on message types that indicate the appropriate IDoc types. The IDoc interface is used to exchange business data between two different systems. The IDoc interface consists of the definition of a data structure and the processing logic for this data structure. Different message types (for example, goods receipt or invoice) usually have specific formats, the SAP IDoc types. However, several related message types can be assigned to one IDoc type.

2009


23


SRM210

Figure 19: SOA, Enterprise Services, and PI

The usage of PI is optional as long as you:

24

•

Do not connect to an ERP 6.0 back end with an active EHP 4

•

Do not connect to Supplier-Self-Services

•

Do not want to upload data from SRM Server to the SRM-MDM catalog

•

Do not need to receive or send XML documents


2009

SRM210


Figure 20: Example of PI Communication

The following documents can be sent in XML format: •

Purchase order

•

Order acknowledgment

•

Shipping notification

•

Confirmation / Confirmation response

•

Invoice / Invoice response

•

Bid invitation / Bid

Data can be exchanged in XML format between SRM Server and any vendor system. Data can be exchanged either directly using SAP XML or any XML dialect. The figure illustrates the data exchange between the SRM Server system and external systems, including SAP Supplier Self-Services. Note: Whether data is also exchanged between SRM Server and SAP ERP on an XML/SOA basis depends on your use of the new functions with ERP 6.0 Enhancement Package 4.

2009


25


SRM210

Figure 21: Integration – Abstraction Layer

Depending on the specific system versions, you can use various Business Application Programming Interfaces (BAPIs) to implement the business processes in the connected systems. The abstraction layer encapsulates the BAPI calls in the ERP back-end system(s) that are necessary to generate the back-end documents from requirement coverage requests. With SAP ERP 6.0 Enhancement Package 4, the system also might utilize service-oriented communication methods for some documents. The abstraction layer accesses the following sources of information: Dispatcher:

This function module analyzes the Customizing settings and then knows: •

Which driver it must call

•

Which type of back-end system it is communicating with

•

The back-end system release

Driver:

For each release level supported and each abstraction layer, there is a driver module that calls the BAPIs in the back-end system. Spooler:

26


2009

SRM210


The spooler controls the transfer of documents from the SRM Server system to the back-end system. If errors occur during the transfer, for example, if the back-end system cannot be contacted, the spooler is used as the queue for the requirement coverage requests. The spooler tries to contact the back-end system at regular intervals to transfer the documents. Hint: The term “back-end system” in this context does not indicate only an SAP ERP back-end system. SUS or a non-SAP system might be connected as a back-end system.

Figure 22: Check Account Assignment: Procedure in Detail

During the creating of a shopping cart, the systems validates the account assignments. The validation can be performed in the following environments: •

In the SRM Server (local validation of FI data)

•

In the back-end system (real-time validation of FI data) – preferred option

•

Do not validate at all – not recommended Note: The type of validation is defined in the IMG back-end definition.

2009


27


SRM210

Figure 23: Maintain Local Product Categories

Product categories make it possible to group products together according to different criteria. SRM Server customizing settings are very often in relation to product categories, for example, the back-end determination. Back-end product categories are replicated via CRM Middleware; local product categories can be maintained directly in transaction . As of SAP SRM 5.0, it is also possible to activate Product Category Hierarchies in the IMG. This enables you to work with hierarchical product categories in your search helps, as well as in your customizing settings. Caution: If SRM is running on one client with SAP ERP 6.0, the replication of the product categories via CRM Middleware is not supported. In this case, check the relevant IMG documentation for instruction on how to proceed.

Hint: It is also possible to upload Product Category Hierarchies to the SRM system from external files (for example, from UNSPSC files) via SAP Exchange Infrastructure (XI) and the File Adapter. For more information, see SAP Note 831808.

28


2009

SRM210


Figure 24: Back-End Determination Using Product Category

You must perform the following customizing steps to determine different back-end systems for different product categories:

2009

•

Assign the RFC destinations to different back-end systems (and vice versa).

•

Perform ALE customizing (logical systems, distribution model).

•

Perform PI settings (if ERP 6.0 EHP 4 is in use).

•

Define back-end systems and SRM system in IMG.

•

Assign each product category to a back-end system as target (a wildcard “*“ can be used).

•

Implement a BAdI (BBP_DETERMINE_LOGSYS) to change the logic of the standard.


29


SRM210

Figure 25: Technical Basic Settings-Summary

The Implementation Guide (IMG) of the SRM Server displays two different sections for Basic Settings: •

Technical Basic Settings

•

Cross-Application Basic Settings

In Technical Basic Settings, you define technical parameters like:

30

•

System landscape, including communication details

•

Back-end systems determination

•

Information about the spooler

•

Settings for supplier synchronization


2009

SRM210


Figure 26: Number Ranges and Transaction Types

2009


31


SRM210

As SRM Server is the leading system for the document creation, you need to maintain the following number ranges in SRM Server: •

Shopping Cart

•

ERP Purchase Requisition, Purchase Order, and Reservation

•

SRM Purchase Order and Contract

•

SRM Confirmation and Invoice

•

SRM RFx, Auction, and Quotation Note: Although SRM is the leading system, first check in your ERP back end to find which number ranges are still available for SRM integration.

Hint: If you work with multiple back-end systems, it might be difficult to find common number ranges across all systems. In that case refer to the IMG section Define Number Ranges per Backend System for Follow-on Documents. Hint: To utilize internal and external long texts in your SRM documents, maintain a text schema per transaction type. Basic text schemata are pre-delivered and can be maintained and mapped to the ERP back end via IMG settings. Note: You also need to synchronize transaction type, tax, and accounting data.

Figure 27: Cross-Application Basic Settings - Summary

32


2009

SRM210


In Cross-Application Basic Settings, you define application-specific parameters such as: •

Number ranges for the procurement documents in the SRM Server and ERP system

•

Transaction type for all documents that are to be created in the SRM Server

•

Tax codes that can be entered in invoices

•

The rules that the SRM Server system uses to determine the account information and the account assignment categories

•

The documents that are to be created in the back-end system from a requirement coverage request

•

Usage of hierarchies with product categories, contracts, and business partners

•

Settings for tax calculation

•

Special settings for service procurement

•

Configuration of other important areas like workflow, portal settings, and so on

Figure 28: Business Add-Ins for SRM Server

Business Add-Ins (BAdIs) are programmer-defined places in source code where application development, industry sectors, customers, and partners can add their own code, without modifying the original object.

2009


33


SRM210

Business Add-Ins are designed for SAP users who require certain functions that are too specialized to be included in the standard system, but that are needed often and, therefore, have been designed to be integrated into the SAP system. Hint: In SRM Server, BAdIs are deployed to overwrite or replace customizing settings or to change the system behavior without modifications.

Figure 29: Scheduling Reports and Background Jobs

RSPPFPROCESS (optional): To transfer your purchase orders to vendors, schedule this report to run at regular intervals. BBP_GET_STATUS_2: This report updates requirement coverage requests (shopping carts). To ensure that information on the status of back-end purchase requisitions, purchase orders, and reservations is up-to-date, schedule this report to run at least daily in the SRM Server system. CLEAN_REQREQ_UP: Document updates are executed asynchronously in the back-end system. You can only process the shopping cart in the SRM Server system after the update has been carried out. For example, the system updates the shopping cart with the back-end PO information. The system checks whether the documents have been updated. You need to schedule the job periodically, at least on a daily basis. BBPERS (optional): If you use evaluated receipt settlement (ERS) for local purchase orders for which confirmations exist, you have to start BBPERS.

34


2009

SRM210


/SAPSRM/OFFLINEAPPROVALSEND (optional): This report creates e-mails out of existing SRM Server work items so that approvers do not have to check their SRM Server workflow inbox, but only their standard e-mail inbox. The report offers several options, for example, collection of work items, offline approval, or sending of attachments. Note: Depending on your business process, there might some other helpful jobs as well; further information can be found via SAP Solution Manger.

SAP Solution Manager

Figure 30: SAP Solution Manager: Offerings

SAP Solution Manager supports you throughout the entire life cycle of your solutions, from the Business Blueprint through configuration to production operation. It provides central access to tools, methods, and preconfigured content that you can use during the evaluation, implementation, and productive operation of your systems. All phases of the implementation project (Business Blueprint, Configuration) are performed centrally in the Solution Manager system. The content area contains information regarding roadmaps, documentation, notes, and configuration for individual projects.

2009


35


SRM210

Figure 31: Solution Manager: Content

Beside general information, you may use project-dependent information data for system setup and maintenance. At the beginning of your work, you have to specify which content you need and which systems are to be connected. Then you create projects by choosing scenarios and components. On that basis, Solution Manager offers you detailed implementation information, as well as links to all connected systems and further information. Hint: Solution Manager content replaces the former configuration guides from the SAP Service Marketplace. This means you should create your individual configuration guide directly from your project in Solution Manager.

Also check the Installation Guides section of the SAP Service Marketplace: http://service.sap.com/instguides -> SAP SRM

36


2009

SRM210


Figure 32: Solution Manager versus IMG

The figure above shows the links to the IMG of the target system and SRM Server when starting from a project in Solution Manager.

2009


37


SRM210

Lesson Summary You should now be able to: •

38



2009

SRM210

Lesson: Back-End Integration Exercise

Lesson: Back-End Integration Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Perform the RFC and ALE settings

•

Schedule background jobs

•

Maintain product categories

•

Define back-end systems

•

Define number ranges and transaction types

•

Perform settings for accounting and tax calculation

Business Example You need to integrate your SRM Server system with your SAP ERP system. You need to maintain all necessary settings in both systems.

General user information for all exercises

Caution: This note is valid for all exercises; please read carefully.

In this class you will work with two pre-delivered users: SRMCONFIG-## and SRMADMIN-## . Both passwords are supplied by your instructor. During the exercises, you will create additional business users. The default password recommendation for those users is “initial ” (change to “training” during logon). You may also feel free to use your own passwords. Do not change the password of SRMCONFIG-## or SRMADMIN-## if you are not asked to do so, as a background reports resets them every night to the pre-delivered password again.

Exercise 1-1 Locate the RFC destination T90CLNT90 defined for the SAP back end that will be connected to the SRM system. Caution: Log on to your client of the SRM system from the SAP GUI:

2009


39


SRM210

Client:

3##

User ID:

Password:

SRMCONFIG-## (provided by instructor)

Exercise Section 1-1-1 Add the customizing transaction codes SPRO (Customizing – Edit Project) and SM59 (RFC Destinations) to your favorites. Hint: You can display the technical names of the transaction codes by choosing Extras Settings and selecting the Display technical names checkbox. !

Exercise Section 1-1-2 Locate the RFC destination T90CLNT090 defined for the SAP back end that will be connected to the SRM system. Caution: Do not change any RFC settings!

Start transaction SM59 (RFC Destination) (Display/Maintain). ABAP connections

Select Double-click Verify

Select

R3_00_800 R3_00_800

Connection Test

Choose

Back

Return to the SAP Easy Access screen.

Exercise 1-2 Configure the logical system.

Exercise Section 1-2-1 View the logical system definition in the SRM component. Start transaction Customizing – Edit Project (SPRO) from your favorites and select SAP Reference IMG .

40


2009

SRM210


Choose SAP Implementation Guide SAP Supplier Relationship Management SRM Server Technical Basic Settings ALE Settings Distribution (ALE) Basic Settings Logical Systems Define Logical System or call transaction SALE. !

!

!

!

!

Choose Verify that

!

Verify that Choose

!

!

Continue

to confirm the information Table is cross-client

SRM_00_3##

is listed

SRM Client 3##

is the name of the Logical System SRM_00_3##

Back

Exercise Section 1-2-2 Locate your client 3## and logical system assignment and view its details. Choose Technical Basic Settings ALE Settings Distribution (ALE) Settings Logical Systems Assign Logical System to Client . !

!

!

Basic

!

Choose

Continue

Select

your client 3##

Choose

!

to confirm the information Table is cross-client

Details

Verify that

Changes to Repository and cross-client Customizing

are allowed

Verify that

0 (No restriction)

is the Protection level

Choose

Back (twice)

Exercise 1-3 Create a distribution model.

Exercise Section 1-3-1 Create a distribution model for sending IDocs between SRM and the SAP back end. Choose Technical Basic Settings ALE Settings Distribution (ALE) Modelling and Implementing Business Processes Maintain Distribution Model and Distribute Views or use transaction code BD64. !

!

!

!

2009


41


SRM210

Choose

Switch between display and to switch to Change mode edit mode

Choose

Create model view

Enter

SRM_00_3## to T90CLNT090

as the Short text

Enter

SRM3##T90

as the Technical name

Verify

today

as start date

Verify

31.12.9999

as end date

Choose

Continue

Exercise Section 1-3-2 Add message types to your model. Choose

Add message type

Select

SRM3##T90

as the Model view

Select

SRM_00_3##

as the Sender

Select

T90CLNT090

as the Receiver

Select

BBPCO

as the Message Type

Choose

Continue

Hint: To simplify the next steps, expand the model you just created and select the receiver system back end, T90CLNT090.

(To expand the model, choose

on the left side of the text.)

Repeat the following steps for each message type in the table. Select

R3 US Backend (T90CLNT090)

Choose Select

Add message type

Choose Select

42

BBPIV

in the Model each time as the Message type

Continue

MBGMCR


as the Message type

2009

SRM210


Choose

Continue

Choose

Save

What does each of these message types do? ________________________________________________________ ________________________________________________________ ________________________________________________________ ________________________________________________________

Exercise Section 1-3-3 Generate the partner profiles for your model. Select


Choose

Environment Generate partner profiles

in the menu bar

!

Select

SRM3##T90

as the Model View

Select

T90CLNT090

as the Partner System

Select

3

as the Version

Set

Transfer IDoc immediately

as the Output mode

Choose

Execute

For which message types were parameters created? ________________________________________________________ ________________________________________________________ ________________________________________________________ ________________________________________________________ Select

Back (twice)

Exercise Section 1-3-4 Distribute the model to the back-end system.

2009


43


Select

SRM210


Choose Select

Edit Model view Distribute !

in the menu bar

!

as Receiver of model view

T90CLNT090

Choose

Continue

Choose

Back (twice)

Exercise 1-4 Find the distribution model in the customizing of the back-end system. Caution: Log on to the SAP back end:

Client:

800

User ID:

Password:

BACK-##

initial

Change your password to training, or your own password if necessary.

Exercise Section 1-4-1 Add the transaction code SPRO (Customizing – Edit Project) to your favorites in the ERP system.

Exercise Section 1-4-2 Generate the partner profiles for the model view on the back-end system. Start transaction Customizing – Edit Project (SPRO) from your favorites and choose SAP Reference IMG . Choose SAP Customizing Implementation Guide SAP NetWeaver Application Server Idoc Interface / Application Link Enabling (ALE) Modelling and Implementing Business Processes Maintain Distribution Model and Distribute Views. !

!

!

!

!

44


2009

SRM210


Verify that Verify that

Select


is listed

SRM3##T90

is the Description/technical name of SRM_00_3## to T90CLNT090


Choose

Environment Generate partner profiles !

Select

SRM3##T90

as the Model View

Select

SRM_00_3##

as the Partner System

Select

3

as the Version

Set

Transfer IDoc immediately

as the Output mode

Choose

Execute

Choose

Back (twice)

Exercise 1-5 Define the back-end system and set the control parameters. Caution: Log on to your client of the SRM system using the SAP GUI:

Client: User ID: Password:

3##


Exercise Section 1-5-1 Verify the definition of the back-end. Note: There are already some settings from an earlier class version. You need to modify them and to add additional entries.

Start transaction Customizing – Edit Project (SPRO) from your favorites and choose SAP Reference IMG . Choose SAP Implementation Guide SAP Supplier Relationship Management SRM Server Technical Basic Settings Define System Landscape. !

!

2009

!

!


45


SRM210

Check

all entries

for T90CLNT090.

Select

ERP_4.0

as Sys.type

Check

R3_800

as System Landscape Directory Name

Select

Integrated UI

Enter

ECC_800

as System Alias f. POWL Navigation

Note: Existing entries here are pre-delivered for training reasons, so normally you would have to maintain all entries yourself.

Exercise Section 1-5-2 Create a new entry for your SRM logical system and your catalog. Choose

New Entries

Choose

Enter Choose

Choose Set

Select Enter

as the Logical system

Local SRM Server

as the Description

SRM_00_3##

as the RFC Destination

Local B2B System

as the Sys.type

Local indicator

Choose Enter

SRM_00_3##

real-time back-end validation of FI data

as the FI valid

SRM_3##

as System Landscape Directory Name

Integrated UI

SRM_##

as System Alias f. POWL Navigation

Create an entry for the catalog system Choose

46

CATALOG


as the Logical system

2009

SRM210


Enter

Choose

Choose

Catalog

as the Description

Catalog

as the Sys.type

Save (twice)

and Back

Hint: The definition of a back-end system entry for the catalog is not mandatory, but sometimes useful. If you want to upload an SRM contract to your catalog, you must maintain this entry.

Exercise Section 1-5-3 Set the control parameters that facilitate the communication to the SAP R/3 back end. In the IMG, choose SAP Supplier Relationship Management Technical Basic Settings Set Control Parameters.

!

SRM Server

!

!

For SPOOL_JOB_USER enter

SRMADMIN-##

as the Value control record

For SPOOL_LEAD_INTERVAL enter

60


For SPOOL_MAX_RETRY enter

10


Choose

Save

Return to the SAP Easy Access screen.

Exercise 2-1 View the current product categories that reside in the SRM Server and create additional new local product categories.

Exercise Section 2-1-1 Standard SRM determines the appropriate back end based on the product category. View the product categories that are currently housed in SRM. Choose SAP Menu Master Data Products Hierarchies (COMM_HIERARCHY). !

2009

!

!

Maintain Categories and


47


SRM210

Choose

Click on

Expand

Start

on the Find tab

R3MATCLASS

to display this hierarchy

R3MATCLASS

(hierarchy)

(Material group) Expand

R3MATCLASST90CLNT090

(sub-hierarchy)

(Material group R/3 Backend) Note: The ERP back-end product categories are only pre-delivered for training reasons, so normally you would have to perform that step yourself.

The product categories that are included in the sub-hierarchy have been replicated from the SAP back end. Select the product category 001 at the top level and take a look at the tabs underneath.

Exercise Section 2-1-2 Create new product categories under the sub-hierarchy associated with local product categories. Select

Choose

Display

Choose

Change

to switch to the Change mode

New Category LOCAL1

as the Category ID.

Enter

Office Supplies (L)

as the Short text

Choose

Continue

Verify that

Product/ Object Assignment is set Possible indicator

Select

48

!

Continue

Choose Enter

R3MATCLASSSRM_00_3## (Material group EBP Client 3##)

R3MATCLASSSRM_00_3##


2009

SRM210


Choose Enter

to create a new category

New Category LOCAL2

as the Category ID.

Enter

Food and Beverage (L)

as the Short text

Choose

Continue

Verify that


Select

Choose Enter

R3MATCLASSSRM_00_3##

to create a new category

New Category LOCAL3

as the Category ID.

Enter

External Service Staff (L)

as the Short text

Choose

Continue

Verify that


Choose

Save (twice)

and Back

Exercise Section 2-1-3 Add the product hierarchy transaction code, COMM_PRAPPLCAT, to your favorites and start the transaction. Verify that

is assigned to application Purchasing

Hierarchy ID R3MATCLASS

Choose

Back

Exercise Section 2-1-4 Define the back-end system determination based on your product categories. Start transaction Customizing – Edit Project (SPRO) and choose SAP Reference . IMG Choose SAP Implementation Guide SAP Supplier Relationship Management SRM Server Technical Basic Settings Define backend System for Product Category. !

!

2009

!

!


49


SRM210

Choose

New Entries

Select

L*

as the Category ID.

Select

SRM_00_3##

as the Source System

Select

SRM_00_3##

as the Target System

Choose

Enter

Enter

*

as the Category ID

Select

T90CLNT090


Select

T90CLNT090

as the Target System

Choose

Enter

Choose

Save (twice)

and Back

Exercise 2-2 Define the number ranges to be used for shopping carts, purchase orders, requisitions, reservations, and service entry sheets. Choose SAP Implementation Guide SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Number Ranges SRM Server Number Ranges Define Number Ranges for Shopping Carts and Follow-On Documents. !

!

!

!

!

!

Exercise Section 2-2-1 Within the Reqt. Coverage Request number range object, create the number range for Shopping Carts using the following information: Choose

Intervals

to change the intervals

Choose

Interval

to insert a new interval

Enter

01

as the No.

Enter

1000000000

as the From number

Enter

1999999999

as the To number

Choose

Insert

Exercise Section 2-2-2 Within the Reqt. Coverage Request number range object, create the number range for the back-end Purchase Orders using the following information:

50


2009

SRM210


Choose

Interval

Enter

PO

as the No.

Enter

30083##000

as the From number

Enter

30083##999

as the To number

Choose

Insert

Exercise Section 2-2-3 Within the Reqt. Coverage Request number range object, create the number range for the back-end Purchase Requisitions using the following information: Choose

Interval

Enter

RQ

as the No.

Enter

40083##000

as the From number

Enter

40083##999

as the To number

Choose

Insert

Exercise Section 2-2-4 Within the Reqt. Coverage Request number range object, create the number range for the Reservations using the following information: Choose

Interval

Enter

RS

as the No.

Enter

00383##000

as the From number

Enter

00383##999

as the To number

Choose Choose Choose

Insert Save Back (twice)

Note: Confirm potential messages regarding transport of number range intervals.

Exercise Section 2-2-5 Define the number ranges to be used for local purchase orders. Choose Number Ranges SRM Server Number Ranges for Local Purchase Orders. !

2009


!

Define Number Range

51


SRM210

Choose

Intervals

Choose

Interval

Enter

01

as the No.

Enter

2000000000

as the From number

Enter

2999999999

as the To number

Choose

Insert

Choose

Save

Choose

Continue

Choose

Back (twice)

Exercise Section 2-2-6 Define the number ranges to be used for confirmations. Choose Number Ranges SRM Server Number Ranges Define Number Range for Local Confirmations of Services and Goods Receipts. !

!

Choose

Intervals

Choose

Interval

Enter

01

as the No.

Enter

6000000000

as the From number

Enter

6999999999

as the To number

Choose Choose Choose Choose

Insert Save Continue Back (twice)

Exercise Section 2-2-7 Define the number ranges to be used for local invoices. Choose Number Ranges for Local Invoices.

52

!

SRM Server Number Ranges


!

Define Number Range

2009

SRM210


Choose

Intervals

Choose

Interval

Enter

01

as the No.

Enter

7000000000

as the From number

Enter

7999999999

as the To number

Choose

Insert

Choose

Save

Choose

Continue

Choose

Back (twice)

Exercise Section 2-2-8 Define the number ranges to be used for local bid invitations. Choose Number Ranges Range for Local RFxs.

!


!

Define Number

Choose

Intervals

Choose

Interval

Enter

01

as the No.

Enter

8100000000

as the From number

Enter

8199999999

as the To number



Exercise Section 2-2-9 Define the number ranges to be used for local bids. Choose Number Ranges SRM Server Number Ranges for Local RFx Responses. !

2009


!

Define Number Range

53


SRM210

Choose

Intervals

Choose

Interval

Enter

01

as the No.

Enter

8200000000

as the From number

Enter

8299999999

as the To number

Choose

Insert

Choose

Save

Choose

Continue

Choose

Back (twice)

Exercise Section 2-2-10 Change the existing number ranges for SRM contracts. Choose Number Ranges for Purchase Contracts.

!


!

Define Number Range

Select

Intervals

Choose

CHANGE Intervals

Select Interval No

44

Change to

443##00000

as the From number

Change to

443##99999

as the To number

Choose Choose

Save Back (twice)

Hint: In general, there is no business need to change the existing number ranges for contracts. However, due to the specific training landscape concept (30 SRM “systems” connected to a single ERP system) and the usage of central contracts together with ERP, you need to use specific ranges to determine the sending SRM client within the PI integration scenarios.

54


2009

SRM210


Exercise 2-3 ERP back end: Find the number ranges and document types that were created for purchase orders. Caution: Log on to the ERP back end:

Client:

800

User ID: Password:

BACK-##

training or your own password

Exercise Section 2-3-1 Find the number range that corresponds to your number range for purchase orders (PO). Start transaction Customizing – Edit Project (SPRO). Choose SAP Customizing Implementation Guide Materials Management Purchasing Purchase Order Define Number Ranges. !

!

!

Choose Verify that

!

Choose

Intervals

to display the intervals

3004000000 to 3009999999

is the Number range for No. PO

Back (twice)

Exercise Section 2-3-2 Find the number range that corresponds to your number range for requisitions (RQ). Choose Materials Management Number Ranges. Choose Verify that Choose

!

Purchasing

!

Purchase Requisition

!

Define

Intervals

4000000000 to 4009999999

is the Number range for No. RQ

Back (twice)

Exercise Section 2-3-3 Find the number range that corresponds to your number range for reservations (RS).

2009


55


SRM210

Choose Materials Management Inventory Management and Physical Inventory Number Assignment Define Number Assignment for Reservations. !

!

!

Choose

Intervals

Choose

Intervals

Verify that

0030000000 to 0039999999 is the Number range for No. RS

Exercise Section 2-3-4 (Optional) Log off the back-end system.

Exercise 2-4 Maintain the transaction types in the SRM system. Caution: Log on to your client of SRM from the SAP GUI:


3##


Which transaction types are defined for confirmations, invoices, local purchase orders, bid invitations, and vendor quotations? Check that every transaction type has a valid text schema. In the IMG, choose SAP Implementation Guide SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Define Transaction Types. !

!

!

!

Choose

BUS2121 (Shopping Cart)

in the Transaction Object Types list

Double-click

Transaction Types

on the left side of the screen

Select

SHC as Trans. Type

Select

SC

and choose Details as Text Schema

Repeat the steps and maintain the text schema per transaction type as follows: Please also make sure that every transaction type has a short text, if any are missing! Trans. Cat.

56

Trans. Type


Text Schema

2009

SRM210


BUS2121

EXTR

SC

BUS2000113

CCTR

CTR

BUS2000113

GCTR

CTR

BUS2000113

PCTR

CTR

BUS2200

BID

RFQ

BUS2200

BIDX

RFQ

BUS2201

EC

PO

BUS2201

ECDP

PO

BUS2202

QUOT

QUOT

BUS2203

CONF

CONF

BUS2203

RETN

RETN

BUS2205

CRME

CRME

BUS2205

INV

INV

BUS2206

QA

AVL

BUS2206

VL

AVL

Choose

Save and Exit the transaction

Caution: Have you checked that all transaction types have a valid description? Check especially the entry for CCTR “Central Contract.” Note: You could also maintain the text schema for the remaining transaction types.

Hint: The text schema entries are pre-delivered and can be found in the IMG. It is possible to adapt them to your needs.

Exercise 2-5 Define objects to be created in the target system. Choose Cross-Application Basic Settings Define Objects in back-end System (Purch. Reqs, Reservations, Purch. Orders) . !

Define the objects to be created in the SAP back end using the following information.

2009


57


SRM210

Choose

New Entries

Enter

*

as the Purch. Grp

Select

001 (with F4)

as the Category ID

Select

Reservation generated if stock available …

as the Int. Proc.

Select

Purchase order if item data complete …

as the Ext. Proc.

Choose

Enter

Enter

*

Select

002 (with F4)

Select

Reservation generated if stock available …

as the Int. Proc.

Select


as the Ext. Proc.

Choose

for the Purch. Grp

from Category ID

Enter

Enter

*

for the Purch. Grp

Select

003 (with F4)

Select

Always external procurement

as the Int. Proc.

Select


as the Ext. Proc.

from Category ID

Create also entries for product categories 007 and 00107 according the settings of product category 003. Choose

Save

and choose Back (twice)

Exercise 2-6 Financial configuration

Exercise 2-6-1 View the account assignment categories used in the SRM Server system. Choose Cross-Application Basic Settings Account Assignment Categories.

58

!

Account Assignment


!

Define

2009

SRM210


Verify that

AS

is the local counterpart of the back-end account assignment category A

Verify that

CC

is the local counterpart of the back-end account assignment category K

Verify that

FI

is the local counterpart of the back-end account assignment category K

Verify that

NET

is the local counterpart of the back-end account assignment category N

Verify that

OR

is the local counterpart of the back-end account assignment category F

Verify that

SO

is the local counterpart of the back-end account assignment category C

Verify that

WBS

is the local counterpart of the back-end account assignment category P

Choose

Back

Exercise Section 2-6-2 Define the G/L account to be used based on product category and account assignment category. Choose Account Assignment Define G/L Account for Product Category and Account Assignment Category. !

Choose

New Entries

Enter

*

as the Category ID

Select

CC

as the AcctAssCat

400000

as the G/L Account no

Enter

Set the flag for

Default

GoTo

Next line

Enter

*

as the Category ID

Select

CC

as the AcctAssCat

400010


Define

GoTo

Next line

Enter

*

as the Category ID

Select

OR

as the AcctAssCat

410000


Define

Set the flag for

2009

Default


59


SRM210

GoTo

Next line

Enter

*

as the Category ID

Select

AS

as the AcctAssCat

11000


Define

Set the flag for

Default

GoTo

Next line

Enter

*

as the Category ID

Select

WBS

as the AcctAssCat

400000


Define

Set the flag for Choose

Default

and Leave the transaction

Save

Exercise Section 2-6-3 Define the system for tax calculation. calculation. Choose Cross-Application Basic Settings for Tax Calculation. Verify that Choose

!

Tax Calculation

!

Determine System

is selected

No TAX_No Tax Calculation

Back

Note: Company code 3000 of the ERP back-end training system has been set up for external tax t ax calculation. If this software component is not available, you will get a tax error message during the creation of your shopping shopping cart as the back end passes that message to SRM Server. Server. To avoid that problem, do not select tax calculation.

Normally you would set Tax Calculation Occurs in the Backend .

Exercise Section 2-6-4 Define the two tax codes to be used for invoicing. Choose Cross-Application Basic Settings

60

!

Tax Calculation

!

Enter Tax Codes .

Choose

New Entries

Enter

I0 (i zero) zero)

as the Tax ind

Enter

Input Tax 0%

as the Tax Description

Set

No tax indicator


2009

SRM210


Set

indicator Default indicator

Choose

Enter

Enter

I1 (i one)

as the Tax ind

Enter

Input Tax 10%

as the Tax Description

Choose

Enter

Choose

Save

Choose

Back (twice)

Exercise 2-7 Schedule the following background jobs for the SRM component.

Exercise Section 2-7-1 Define the background job CLEAN_REQREQ_UP. Choose System Enter

!

!

Jobs

as the Job name

Immediate

Choose

Period values

Choose

Other period

Define the job to run every

2 Minutes

Choose

Save

Choose

Choose Choose

Define Job.

Start condition

Choose

Enter

!

Cleaner_3##

Choose

2009

Services

(three times)

Step ABAP program

CLEAN_REQREQ_UP

as the name

Save


61


SRM210

Choose

Back

Choose

Save

Choose

Back

Hint: If you are not sure if the job is already planned, watch the system status line of your SAP GUI. You You will get a message there when the job is saved.

Exercise Section 2-7-2 Define the background job BBP_GET_STATUS_2. Choose System Enter

!

Services

!

Jobs

Immediate

Choose

Period values

Choose

Other period

Define the job to run every

2 Minutes

Choose

Save

Choose

Choose

Choose Choose Choose

as the Job name

Start condition

Choose

Choose

Define Job.

GET_STATUS_3##

Choose

Enter

!

(three times)

Step ABAP program

BBP_GET_STATUS_2

as the name

Save Back Save Back

Exercise Section 2-7-3 Check that your jobs are running.

62


2009

SRM210


Choose

System Services Job Overview !

!

Jobs

!

Enter

as the Job name

*##*

Choose

Execute

Check if

your jobs

have the status released

Exercise 3 Perform settings for the PI and service-based communication. Note: These settings might be optional if you do not use any of the service-base service-based d scenarios within ERP 6.0 EHP 4.

Exercise Section 3-1 Activate Error and Conflict Handler. Choose SAP Implementation Guide Cross-Application Components Processes and Tools for Enterprise Applications Enterprise Services and Conflict Handler Activate Error and Conflict Handler . !

!

! !

Error

!

Set the flag for Activate to Activated . Activate FEH for Client to Choose New Entries and set the flag. Choose Save and leave the transaction. transaction.

Exercise Section 3-2 Maintain the communication settings for transaction /SAPPO/PPO2. Start transaction SE16. Enter /SAPPO/LGSYS /SAPPO/LGSYS as Table and choose Create Entries Select

CA-SOA-ESM-SRMPUR

as Component

Select

SRM_00_3##

as OBJLOGSYS

Choose

Save and Back

Choose Create Entries

.

Select

CA-SOA-ESM-ERP-PUR as Component

Select

T90CLNT090

Choose

2009

.

as OBJLOGSYS

Save and Back


63


SRM210

Enter /SAPPO/LGSYS_AS /SAPPO/LGSYS_AS as Table. Choose Create Entries

.

Select

CA-SOA-ESM-ERP-PUR as COMPONENT

Select

T90CLNT090

Select

as OBJLOGSYS

1

OBJCAT

Enter via F4

R3_00_800

as RFCDEST

Enter via F4

R3_00_800_DIA

as RFCDEST DIALOG

Choose

Save and Back

Choose Create Entries

.

Select

CA-SOA-ESM-SRMPUR

as COMPONENT

Select

SRM_00_3##

as OBJLOGSYS

Select

1

OBJCAT

Enter via F4

SRM_00_3##

as RFCDEST

Enter via F4

SRM_00_3##

as RFCDEST DIALOG

Choose

(twice) Save and Back (twice)

service-based communicati communication, on, you will find important important Hint: For service-based information information for error handling handling in transactions SXMB_MONI SXMB_MONI and /SAPPO/PPO2. The settings above are required.

64


2009

SRM210



2009

•

Perf Perfor orm m the the RFC RFC and and ALE ALE sett settin ings gs

•

Sche Schedu dule le back backgr grou ound nd jobs jobs

•

Main Mainta tain in prod produc uctt categ categor orie iess

•

Defi Define ne back back-e -end nd syst system emss

•

Define Define num number ber ranges ranges and transact transaction ion types types

•

Perfor Perform m setting settingss for accoun accountin ting g and tax calcul calculatio ation n


65

Unit Summary

SRM210


66

•

Explain Explain the integr integratio ation n princ principl iples es of of an SAP ERP back-e back-end nd inte integra gration tion

•

Perf Perfor orm m the the RFC RFC and and ALE ALE setti setting ngss

•

Sche Schedu dule le back backgr grou ound nd jobs jobs

•

Main Mainta tain in prod produc uctt cate catego gori ries es

•

Defi Define ne back back-e -end nd syst system emss

•

Define Define num number ber ranges ranges and transac transactio tion n types types

•

Perfor Perform m setting settingss for accoun accountin ting g and tax calcul calculati ation on


2009

Unit 3 Organizational Structure and User Management Unit Overview After you have maintained the basic steps of integration and configuration, you must create the organizational plan in SRM Server. Other topics in this unit include the role of purchasing organizations and groups, and the different tools to maintain users in SRM Server.


Explain the principles of SRM Server Organizational Management

•

Maintain an organizational plan according to your project needs

•

Explain the SAP NetWeaver Portal integration of SAP SRM

•

Demonstrate how to set up, maintain, and check users in an SAP SRM Server system

•

Perform user creation and maintenance in an SRM Server system

Unit Contents Lesson: Organizational Plan ................................................... 68 Lesson: Organizational Plan Exercise ........................................ 78 Lesson: User Maintenance .... .... ... .... .... .... .... .... .... ... .... ... .... .... 94 Lesson: User Maintenance Exercise.. ... .. ... .. ... ... .. ... .. ... .. ... .. ... ...108

2009


67

Unit 3: Organizational Structure and User Management

SRM210

Lesson: Organizational Plan Lesson Overview This lesson discusses the purpose of the organizational plan within SRM Server and teaches you how to maintain the necessary configuration sets.



Business Example You want to familiarize yourself with the Organizational Management settings in SAP SRM Server.

Organizational Plan Maintenance

Figure 33: Organizational Plan Maintenance

The system administrator has to:

68

•

Create or change organizational units, and maintain addresses of organizational units.

•

Maintain attributes of organizational units and positions.

•

Specify access rights for attributes by user roles.

•

Define purchasing organizations and purchasing groups.


2009

SRM210

Lesson: Organizational Plan

Figure 34: Organizational Plan

The organizational structure forms the hierarchy in which the various organizational units of an enterprise are arranged according to tasks and functions. A root organizational unit is the unit at the highest level of an organizational structure. When you build organizational structures, you build them from the root organizational unit down. An organizational unit represents any type of organizational entity found within a company, for example, subsidiaries, divisions, departments, or special project teams. Organizational units are one of the objects that make up organizational plans. Each user attribute represents a value that is stored under a particular name within the organizational structure. You can define multiple and default values for attributes. You must define different values for host-dependent attributes in configurations with back-end systems.

2009


69


SRM210

Figure 35: Organizational Plan

When creating the organizational units, you need to assign a few attributes to give users the values they need to use the Shop functionality in SRM Server. First, you have to create at least one root organization (though it is also possible to create more than one). Afterward, create the organizational units that belong to the root organization underneath the root. When the structure is complete, you can create users. SRM Server users are an integral part of the organizational plan. They belong to a certain organization and have to have a position, a business partner ID, a central person, and an SU01 user ID. Users created as SU01 user only are not able to work from the web UI or to perform any procurement process. So this only makes sense for some technical system administrators and configuration issues.

70


2009

SRM210


Figure 36: SRM Server Attributes

A set of user attributes is required to work with SRM Server. Each user attribute represents a value that is stored under a particular name within the organizational structure. A different set of attributes is required for each user, depending on the user's role. You can define attributes either for a particular user (that is, per position) or for an organizational unit. When maintaining the user attributes, you have to work in the Attributes area as well as in the Extended Attributes area. Special functions of organizational units, like company or purchasing organization, are maintained under the Function tab.

2009


71


SRM210

Figure 37: Attribute Inheritance

Attributes can be defined at any level of the organizational structure. An attribute is inherited by all organizational units below the organizational unit where it was defined. To avoid redundant work, maintain attributes at highest possible level. If there are several values for one attribute, you often can select one as a default. Values for attributes can also be excluded or overwritten. The detailed possibilities depend on the single attribute itself and the associated control table T77OMATTR.

72


2009

SRM210


Figure 38: Attribute Control

To configure attributes used in the organizational plan, go to transaction SM30, and table T77OMATTR. Choose scenario BBP and maintain the type of inheritance, the visibility in PPOMA_BBP, and the description in PPOMA_BBP. Check the table and search function module information in the table column. Caution: Be very careful with major changes in this table, as they might endanger your system stability. You can also maintain your own attributes here and change the inheritance logic for common attributes, depending on your company’s requirements.

Hint: The navigation concept for attribute selection in PPOMA_BPP has changed since SRM 5.0, and you might not be satisfied with the large scroll area. You can mask those attributes you are not interested in, for example, the PM* attributes. Be careful not to deactivate mandatory attributes.

2009


73


SRM210

Figure 39: Finding Purchasing Data

What happens if user US1 orders a material from product category “Office supply” ? 1.

2.

74

The system will check which purchasing organizations can potentially procure for the department of user US1 (oganizational responsibility): •

- Purch GRP DE (responsible for the Org DE [50000002] and all departments below)

•

- Central Purch (responsible for the IDES root [50000001] and all departments below)

The system will look for which product category(s) the potential purchasing organization is responsible (product responsibility). •

Only Central Purch is responsible for Office supplies. This is the purchasing group that will be selected.

•

If system finds several purchasing groups that are responsible for the same department and the same product category, it will use the first in the table.


2009

SRM210


Figure 40: Purchasing Organization and Purchasing Group

Purchasing organizations and purchasing groups are defined as organizational units with additional flags and attributes. Depending on the business scenario, the purchasing groups might contain users (purchasers), but this is not mandatory. If the purchasing organization is located in the ERP back end (classic scenario), these organizational units are used simply to pass the necessary values to the back-end system. In this case, no users are linked to the organizational units.

2009


75


SRM210

Figure 41: Defining User Attributes

Attributes can be defined either for a particular user (that is, per position) or for an organizational unit. System administrators should define the most important user attributes at organizational level using the Customizing activity Change Organizational Plan. Managers and users can make their changes from the SAP NetWeaver Portal using the SRM User Settings application. Employees can change their own attributes (for example, select a default cost center), within their user settings, provided they are authorized. In the Implementation Guide (IMG), you can maintain Attribute Access Rights by Role to control the authorization for changing attributes. If employees are only authorized to view the attributes, they can still set defaults for multiple values.

76


2009

SRM210



2009



77


SRM210

Lesson: Organizational Plan Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •


Business Example You need to set up your company structure in SRM Server and maintain all attributes relevant for your business processes.

Exercise 1 Set up the organizational plan. Caution: Log on to the SRM Server from the SAP GUI:

Client:

3##

User ID:

Password:


Add the transactions PPOCA_BBP Create Attributes and PPOMA_BBP Change Attributes to your favorites list.

Exercise 2 Create the organizational plan. Hint: The table below only intends to provide you an overview over the planned organizational structure. For detailed information on how to proceed, please use the subsequent exercise descriptions. Root Organization

Line Organization

Phoenix Enterprise

Phoenix

78

Organization name

Support

Phoenix Support

PUR Back

PUR Back Processes


2009

SRM210

Lesson: Organizational Plan Exercise

Root Organization

Line Organization

Organization name

PGRP010

PUR Group Davis, L.

PGRP011

PUR Group Edwards PUR Local Processes

PUR Local

PUR Local Processes

PGRP Local

Phoenix Production

Production

Caution: All the following organizational units should have valid address data. Ensure that you maintain the corresponding fields correctly. For example, an e-mail address always needs to contain an “@”, a ZIP code has to be in a certain format, and so on.

Exercise Section 2-1 Create the root organizational unit. Start transaction Create Attributes (PPOCA_BBP) and confirm the validity date message by choosing Enter . Go to

BASIC DATA

tab page

Phoenix

to replace New Organizational Unit

Enter

Phoenix Enterprises Inc.

to replace New Organizational Unit

Choose

Continue

Enter

Go to

ADDRESS

tab page

Enter the following address data:

Choose Enter

2009

Lancaster Ave / 1717

as the House No./Street

Atlanta / 30003

as the City / Postal code

US / GA (Georgia)

as the Country / Region

661-662-12

as the Telephone no.

661-662-13

as the Fax number

Replace

[email protected]

as the E-mail address


79


Select

SRM210

Continue

Choose

Save

Choose

Back

Exercise Section 2-2 Create the Phoenix Support organizational unit. Start the transaction Change Attributes (PPOMA_BBP) from your favorites. If you do not see your root organizational unit here, proceed as follows:

Double-click

Organization Unit

in the Find by area on the left side of the screen

Search for

*

and choose Find

If you see your root organizational unit, start from here:

Double-click on Choose

Phoenix

organizational unit

Create

Select

Is line supervisor of Organizational unit

Go to

BASIC DATA

tab page

Support

to replace “New Organizational Unit”

Enter

Phoenix Support

to replace “New Organizational Unit”

Choose

Continue

Enter

Go to

ADDRESS

tab page

Enter the following address data:

Choose

80

Lancaster Ave / 1717

as the House No./Street

Atlanta / 30003

as the City / Postal code

US / GA (Georgia)

as the Country / Region

661-662-12

as the Telephone no.

661-662-13

as the Fax number

Replace


2009

SRM210


Enter

[email protected]

Choose

as the E-mail address

Continue

Choose

Save

Exercise Section 2-3 Copy additional Organizational Units for Phoenix Enterprises root. Double-click on

Phoenix Support

Organizational unit

Choose

Copy

Enter

PUR Back

as the Object abbr.

Enter

PUR Back Processes

as the Name

Choose

Continue

Double-click on

PUR Back Processes

Choose

Copy

Enter

PUR Local

as the Object abbr.

Enter

PUR Local Processes

as the Name

Choose

Continue

Double-click on

PUR Local Processes

Choose

Copy

Enter

2009

Organizational unit

Organizational unit

Production

as the Object abbr.

Enter

Phoenix Production

as the Name

Choose

Continue

Double-click on

PUR Back Processes

Choose

Copy

Enter

PGRP 010

as the Object abbr.

Enter

PUR Group Davis

as the Name

Choose

Continue

Double-click on

PUR Group Davis

Organizational unit

Organizational unit


81


SRM210

Choose

Copy

Enter

PGRP 011

as the Object abbr.

Enter

PUR Group Edwards

as the Name

Choose

Continue

Double-click on

PUR Group Davis

Choose

Copy

Enter

PGRP Local

as the Object abbr.

Enter

PUR Group Miller

as the Name

Choose

Continue

Choose

Organizational unit

Save

Caution: It is important that all your departments have complete and valid address data, or you will have problems later with the business partners of those organizational units. If you are not sure, please double check. In exercise 5–5, you will also find a transaction for checking organizational units.

Exercise Section 2-4 Assign the organizational units PUR Group Davis and PUR Group Edwards , to the organizational unit PUR Back Processes. Assign the organizational unit PUR Group Miller to the organizational unit PUR Local Processes.

82

Double-click on

PUR Back Processes

Choose

Assign

Double-click


Choose

Start search

Select

PGRP 010

Select

PGRP 011

Choose

Copy

Double-click on

PUR Local Processes

Choose

Assign


Organizational unit

Organizational unit

2009

SRM210


Double-click


Choose

Start search

Select

PGRP Local

Choose

Copy

Choose

Save

Hint: You can also use drag and drop for these assignments.

Exercise 3 Maintain the mandatory organizational attributes to the root Phoenix Enterprises organizational unit.

Exercise Section 3-1 Add the attributes to the root Phoenix Enterprise organization unit. Double-click on


organizational unit

Go to

FUNCTION

tab page

Set

Company indicator

Enter

Choose

as the Company Code

T90CLNT090 (R3 US Backend (LS))

Go to

ATTRIBUTES

tab page

Choose

Chg. Attribute

Choose

Account assignment category

as Attribute

Choose

CC (Cost center)

as Acc. Assignment Cat.

Set Select

2009

3000

Default indicator Line for CC


83


Select

Insert Line

Choose

AS (Asset)

SRM210

as Acc. Assignment Cat.

Note: For the following attributes, assign the listed values in the manner described above. Attribute

Value

Company Code

Cost Center

Choose T90CLNT090 as Source System Enter 3000 as Company Code 1000 T90CLNT090 4140 T90CLNT090

Current ITS of User Default printer

< _portal_URL_provided_by your_instructor >

LP01

Document Type in R/3 System

EC T90CLNT090

Local Currency

USD

Movement type

201 T90CLNT090

System Alias

T90CLNT090 SRM_00_3##

System Alias for Accounting Systems T90CLNT090 User role

/SAPSRM/EMPLOYEE [set Indicator] Default /SAPSRM/SECRETARY /SAPSRM/BIDDER /SAPSRM/SUPPLIER

Transaction Type Contracts

CCTR (Central Contract) PCTR (Purchase Contract)

Choose

Save

Hint: If you want to review the maintained attribute values, choose . Overview

84


2009

SRM210


Exercise Section 3-2 Maintain the extended attributes for organizational unit Phoenix Enterprise. Go to

EXTENDED ATTRIBUTES tab page

Set

Product Categories radio button

under the Extended Attribute tab page

Choose

R3 US Backend (LS)


(T90CLNT090)

Enter

001

as the Product Category

Enter

007

as the To Product Category

Choose

Continue

Choose

SRM_00_3##

as the Src. System

(EBP Client 3##) Enter

LOCAL1


Enter

LOCAL3


Enter with F4

002 (T90CLNT090)

as Default Product Category

Choose

Continue

Set

Select

Locations radio button


R3 US Backend (LS)

as the Src. System

(T90CLNT090)

Enter

3200

as the Plant (Plnt)

Select with F4

as the Partner IDfrom the search help result list

Choose

Continue

Set

Storage Locations radio button


Choose

R3 US Backend (LS)

as the Src. System

(T90CLNT090)

Choose with F4

2009

0001 (in plant 3200)

as the Storage Location


85


Choose

SRM210

Continue

Choose

Save

Double-click on

one of the suborganizational units

under the root organization

Are the attributes inherited from the root Phoenix? How can you see that? ____________________________________________________ ____________________________________________________

Exercise 4 Define the purchasing organizations within the org. structure. The organizational unit named PUR Back Processes will be the purchasing organization for the back-end processes. The organizational unit named PUR Local Processes will be responsible for local processes. Double-click on

PUR Back Processes

Organizational unit

Go to

FUNCTION

tab page

Set Enter

Purch. Organization indicator

Choose

3000

for the corresponding back-end Purchase Organization

T90CLNT090

Double-click on

PUR Local Processes

Organizational unit

Go to

FUNCTION

tab page

Set

Purch. Organization indicator

Choose

Save

Exercise 5 Define the purchasing groups within the org structure.

86


2009

SRM210


Exercise Section 5-1 The organizational units named PUR Group Davis and PUR Group Edwards will be the purchasing groups for the back-end processes. The organizational unit named PUR Group Miller will be responsible for local processes. Double-click on

PUR Group Davis

Organizational unit

Go to

FUNCTION

tab page

Set

Purchasing Group indicator

Enter

010

Choose

for the corresponding back-end Purchasing Group

T90CLNT090

Double-click on

PUR Group Edwards

Organizational unit

Go to

FUNCTION

tab page

Set


Enter

011

Choose

for the corresponding back-end Purchasing Group

T90CLNT090

Double-click on

PUR Group Miller

Organizational unit

Go to

FUNCTION

tab page

Set


Choose

Save

Exercise Section 5-2 Use the appropriate attribute to denote that the purchasing groups under PUR Back Processes are responsible for the entire organization and for certain product categories assigned to the back-end system. Double-click on

PUR Group Davis

Organizational unit

Go to

RESPONSIBILITY

tab page

R3 US Backend (LS)

as the Source Sys. under the Product Responsibility

Choose

T90CLNT090

Enter

2009

001



87


Choose

R3 US Backend(LS) T90CLNT090

SRM210


Enter

003

Choose with F4


Double-click on

PUR Group Edwards

Organizational Unit

Go to

RESPONSIBILITY

tab page

R3 US Backend(LS)


Choose

T90CLNT090


Enter

002


Enter

007


Choose with F4


Choose

Save

Exercise Section 5-3 Use the appropriate attribute to denote that the purchasing groups under PUR Local Processes are also responsible for the entire organization and for certain product categories assigned to the local SRM system. Double-click on

PUR Group Miller

Organizational unit

Go to

RESPONSIBILITY

tab page

SRM_00_3##


Choose

(EBP Client 3##) Enter

LOCAL1


Enter

LOCAL3

as to Product Category

in the frame Organizational Responsibility

Choose with F4

Choose

88

Save


2009

SRM210


Exercise Section 5-4 Check at the root level if the mandatory attributes maintained for Phoenix Enterprise Inc. are complete. Double-click on

Phoenix Enterprise Inc.

Go to

CHECK

tab page

“Check OK”

appears

Ensure that the message

Leave the transaction.

Exercise Section 5-5 Perform a business partner check for your organizational units. Hint: Report HRALXSYNC synchronizes the HR objects Organizational Unit and Central Person with the business partners in SRM. A business partner is required for organization units and users (including the so-called central person). Since not all the business partner data is time-dependent, changes made to HR objects in the future cannot be posted in the business partner immediately. You can update these changes by running the report regularly. When the organizational unit is synchronized, this includes the basic data (name, description) and address.

In a productive environment, you would run report HRALXSYNC daily to ensure synchronized data. Manually trigger the corresponding transaction BBP_BP_OM_INTEGRATE. Start transaction Customizing – Edit Project (SPRO) and choose SAP Reference . IMG f Choose SAP Implementation Guide SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Organizational Management Integration Business Partner-Organizational Management Match Up Organizational Units and Persons with Business Partners . !

!

!

!

!

2009

!


89


Select

SRM210

Organization Unit(s)

Choose

Execute

For red light indicators, select line and choose

Start Repair

Make sure every light is

Green

Choose

before leaving transaction

Back (twice)

Hint: Verify that all address status indicators are green.

If they are not, you have to correct the address data for some of the organization units. To do this, start the transaction Change Attributes (PPOMA_BBP) and select the organizational unit. Please note that you have to use the correct postal code length for the specific country. If you want to copy the address data from a valid organizational unit, select the unit and go to the Address tab page. Use CTRL+Y to select and CTRL+C to copy the address information. Paste ( CTRL+V ) this copied information for the other organizational units. After correcting the address data, you have to synchronize the organizational unit again.

Exercise 6 (optional) Add a delivery and invoice recipient address for Phoenix Enterprise

Exercise Section 6-1 Create the address from the portal user interface. Caution: Log on to the portal as administrator:

90


2009

SRM210


User ID:

SRMADMIN-##

Password:

(provided by instructor)

Client

(will be determined by the portal from your user id)

Hint: Default portal user interface language:

The language of the portal UI depends on the default language of your browser. If you want to change the language, you can change your default Internet Explorer language on the Training WTS, or change the SAP NetWeaver Portal language on a single-user basis. From the top level of the portal (right corner), choose Personalize User Profile Modify Language ..... Change the language and choose Save. !

!

!

!

You might need to log off and log in again afterward. If you need further assistance, contact your instructor. In the portal choose

SRM Administration

from the top level navigation

then

SRM Administration

from the Detailed Navigation area

Choose the query

Purchasing Company

Select

Phoenix and choose Edit

A new window will pop-up.

Close (the error message that appears)

Hint: This is because the user SRMADMIN-## is not yet assigned to an organizational unit in the PPOMA_BBP.

Go to

Address data

tab

Select

Choose

Choose

Enter

from Internal Business Partner

Detail EN

as Language and choose Save

Note: If you see warnings, for example “e-mail address is missing”, complete the missing entries and save again. Choose

2009

Duplicate


91


Set

Ship-To Address

SRM210

in the detailed section Address Type

Enter or choose the following address data: Change the Street / House Number to:

Hasso-Plattner-Avenue / 100

Choose

Save and Close the dialog box

at the top of the screen

To find the address number, navigate as before to the address data tab and write down the newly created address number. Why could you only add an address for the root organization?

_______________________________________________________________ Which address number has the newly created ship-to address?

_______________________________________________________________ Choose

Log off

Exercise Section 6-2 (Optional) Maintain the Address Number for the ship-to-address you just created for the attribute ADDR_SHIPT (Delivery Address) to your support organizational in PPOMA_BBP. Start

PPOMA_BBP

Double-click on

Phoenix Support

root Organization Unit

Go to

ATTRIBUTES

tab page

Choose

Chg. Attribute

Choose

Delivery address

Enter

as Addr. no.

Choose

Save

as Attribute

and Back

Note: You do not need to maintain the delivery address number in PPOMA . But, this could make sense if you want to specify special addresses for some users, like the address of a home office.

92


2009

SRM210



2009



93


SRM210

Lesson: User Maintenance Lesson Overview In this lesson, you will learn about creation and maintenance of SRM Server users. Some specific procedures are necessary to ensure that all users are able to log on to the system.



•


Business Example In the second step of your organizational setup, you need to familiarize yourself with the SRM and NetWeaver Portal user management.

SAP NetWeaver Portal with SAP SRM With SRM 7.0, SAP NetWeaver Portal and WebDynpro for ABAP replaced the older ITS Web transactions. This now implies that SRM user maintenance also means portal user maintenance.

94


2009

SRM210

Lesson: User Maintenance

Figure 42: SAP NetWeaver Portal in SRM

The SAP NetWeaver Portal is the common user interface for all transactions and the approval inbox across all SRM roles. Depending on the tasks (and role) of the user, the portal provides queries for the documents for which the user is responsible, plus some additional services. Portal queries can be adopted by administrators or end users, but enhanced details of the portal look and feel can only be influenced by the administrator. Note: SRM 7.0 requires SAP NetWeaver Portal 7.0 (with SP15) or 7.01 supplied with the related portal content (Business Package for SRM 7.0).

2009


95


SRM210

Figure 43: User Management

96


2009

SRM210


Because SRM 7.0 is delivered together with SAP NW Portal, you have to consider a multistep approach for user management: •

Maintain users, with roles and permissions, directly in the application(s) where they are performing their daily tasks. This supplies them with the sufficient permissions for their primary business transactions.

•

Log on to the portal, not the business application itself (but you might still permit, for example, a SAP GUI logon to ERP). The portal also provides the iViews, Services, and initial navigation. Therefore, the users have to have a portal user with the appropriate portal roles, as well. The portal also takes care of single sign-on to the connected business systems.

•

The portal user management engine (UME) could be connected to an LDAP directory, a local database, or an SAP ABAP system. This needs to be considered for system implementation and user administration.

•

As an option, the entire landscape could be also connected to central user management applications. This might be SAP Central User Administration (CUA), where the users are distributed on an ALE basis, or SAP NetWeaver Identity Management. Hint: LDAP (Lightweight Directory Access Protocol) is a software protocol for enabling anyone to locate organizations, individuals, and other resources, such as files and devices in a network, whether on the public Internet or on a corporate intranet. LDAP is a lightweight (smaller amount of code) version of Directory Access Protocol (DAP), which is part of X.500, a standard for directory services in a network.

2009


97


SRM210

Caution: The user administration concept and questions about installing SAP NetWeaver Portal and the SRM Business Packages, as well as changes in Portal roles and Portal look and feel, should be discussed with an experienced portal consultant. This lesson can only provide an overview. Hint: If you require additional information about the SAP identity and user management concepts, please check:

http://help.sap.com Management

!

SAP NetWeaver or

!

SAP NetWeaver Identity

htt p://sdn.sa p.com SAP NetWeaver Capabilities Identity Management !

!

Security and

htt p://www.sdn.sap.com/ir j/scn/go/ portal/prtroot/docs/li brar y/uuid/fe4f76cc-0601-0010-55a3-c4a1ab8397b1 or search in SDN for “CUA” ABAP Identity Management htt p://help.sa p.com/saphel p_er p60 _s p/hel pdata/EN/52/671126439b11d1896f0000e8322d00/content.htm or search for “Configuration of Identity Management” in the SAP ERP documentation. Central User Management: htt p://service.sap.com/security Library

!

Media

Hint: For SAP NetWeaver Portal education, please seehttp://www.sa p.com/services/education/catalog/netweaver/e p.e px

98


2009

SRM210


Figure 44: SRM210 Training Landscape (simplified)

The figure above provides an overview over the SRM training landscape with a focus on portal connections. Please be aware that a typical customer landscape would look different, but might have similar requirements. The SRM training landscape consists of: •

SRM Client 300 used for Overview and Delta Class

•

SRM Clients 301-330 (3##) used by SRM210 and Delta Class

•

One ERP back end

•

One SAP NetWeaver Portal

•

Some other clients for SRM demo, SUS, PI, Live Auction, and SRM MDM catalog

While the connection to ERP is easy to define because there is only one ERP for all users, the challenge is to direct the SRM users to the correct SRM “system” (SRM client). How does it work? SAP NetWeaver Business Content is delivered with one system alias to system SRM (SAP_SRM). The system alias provides the technical connection to the SRM application. To connect 30 SRM clients, system aliases 00-30 were created from the pre-delivered one.

2009


99


SRM210

In the pre-delivered portal business content the SRM transactions are already linked to the SAP_SRM system. These iViews and transactions are capsulated in portal roles. In the next step, the pre-delivered roles were copied and each of the copies adapted (per mass changes) to the new system alias. As a result, the user's role determines the SRM system to which he or she will connect after logging on to the SAP NetWeaver Portal. Note: There were also some settings performed to create the UWL (universal worklist) connections to the 30 SRM clients. Note: Due to the copy procedure of the portal role, you do not work with the pre-delivered original objects of the portal roles, but with identical training versions.

Hint: For the access to the Universal Worklist (UWL), workitems and Personal Object Worklists (POWL), some RFC permissions are needed. For details, start transaction PFCG and enter /SAPSRM/EMPLOYEE as role. Check the Authorization data and choose Cross-Apllication Authorization Objects Authorization Check for RFC Access. !

!

You also might add the following roles: SAP_BC_UWL_END_USER SAP_BC_BMT_WFM_UWL_END_USER SAP_BC_BMT_WFM_NWBC_END_USER

SRM User Maintenance The SU01-user is the user in the standard SAP system, which can be created and maintained using transaction SU01. This user cannot work in the SRM Server system because much of the important user information is stored as attributes in the organizational model. For this reason, the user must be integrated in the organizational model. This is done using a structure comprising several objects (position, central person, business partner, and SU01 user).

100


2009

SRM210


Figure 45: User Creation and Maintenance

You can create a user in two ways. For single user creation, you can choose Self-Service, where the user can apply for a user ID or the Administrator can create users individually through the Web. If you want to apply for a user, you also need to configure the related workflow for this procedure. This creates an SRM user only– no portal user. An other option is generic user creation via transaction USERS_GEN, where you can choose to create users from a local SU01 user, via RFC, or by uploading a file. Note: The precise functionality of the USERS_GEN transaction is explained later in the course.

Once the user is created, he or she can review (or edit) attributes under SRM User Settings. The attributes are listed by system-independent and system-specific attributes.

2009


101


SRM210

Figure 46: User Creation Toolset

You can import user data as an ASCII file, create new user data generically, create multiple users by means of a Remote Function Call (RFC), or upload from an LDAP directory. Hint: You can only process internal SRM users with this transaction; you cannot use it to process vendor users. You should not assign more than 200 users to a single organizational unit for performance reasons. Caution: If SRM is installed as add-on to an ERP system with HCM in the same client, this transaction is deactivated. In that case, use the HCM transaction to assign employees to user accounts.

102


2009

SRM210


Figure 47: Distribution of Users Between Systems

Building SRM users from an HR system: •

The SRM users are built by distributing the positions and employees from the HR system. This is only possible if the organizational units have were created by distributing them from the HR system using ALE.

Building SRM users from an SRM system: •

If you have an existing SRM system with the complete user data, you can download or upload the data to a different SRM system. This is carried out in two steps: Download from system 1 to file system and upload again to system 2. As the file is in text format, it is very easy to adapt entries before the upload.

Building SRM users from non-SAP systems: •

If you want to create SRM users from a system other than ERP, you must write a program that provides the data accordingly or create a *.txt file from a spreadsheet that contains the necessary data. The file structure is described in the documentation of the USERS_GEN transaction. Note: Do not forget to consider portal user creation as well!

2009


103


SRM210

Figure 48: HR Replication

What needs to be considered for the HR replication ? It replaces manual maintenance of the organizational structure in SRM. It replaces employee creation in SRM. It requires that the SU01 users exist in both systems in advance; therefore, central user management is recommended. It still requires that the administrator maintain attributes in SRM Server. HR is the leading system; all new or changed entries are automatically synchronized to SRM. No updates are possible from SRM to ERP. Distribution happens via ALE scenario. You have to maintain distribution model, iDoc filters, and number ranges for organizational units.

104


2009

SRM210


Replicated data may contain sensitive employee data. This sensitive data needs to be hidden or initialized in the source system by either IDoc conversion rules or BAdI HCMALE00OUTBOUND_IDOC. Hint: Also refer to the following SAP Notes (and the related notes):

312090 - Integration HR - EBP/CRM 550055 - EBP/CRM: New integration for business partner 934372 - SRM/CRM: HR integration for business partner – new features 711852 - Link not created to the SU01 user 724149 - HRALX: Masking sensitive data

Figure 49: Consistency Check for Organizational Plan

The report BBP_CHECK_CONSISTENCY (which can be called up via transaction BBP_ATTR_CHECK) checks the consistency of the organizational plan. It also checks (with reference to an internal control table) whether the attributes for companies, purchasing organizations, purchasing groups, and users are maintained for the individual applications. You can correct the displayed fields in the organizational plan. Red error messages have to be corrected, while yellow error messages are just warnings. You also have the option to check the organizational units and users in the PPOMA under the Check tab; the only difference is that this check is only for the organizational unit or user you selected in the organizational plan.

2009


105


SRM210

Figure 50: Check and Repair Cockpit

With the USERS_GEN transaction, you can also check your internal SRM Server users for consistency and repair them if necessary. You cannot process vendor users with this transaction. You also may start the user check from report HRALXSYNC. If a user has yellow status, you can use this transaction to repair the user. If a user has a red status, you cannot use this transaction to repair the user. It is also possible to delete user accounts and employees from this transaction.

106


2009

SRM210



2009

•


•



107


SRM210

Lesson: User Maintenance Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •


Business Example You want to create users for your SRM and your SAP NetWeaver Portal. You also want to find out if there are possibilities for mass generation.

Exercise 1 Upload user SRMADMIN-## into your organizational structure. Caution: Log on to your client of the SRM system from the SAP GUI:

User ID:

SRMCONFIG-##

Password:


Client:

3##

Caution: Before you create any users, verify that you are out of the organizational plan or that you are in display mode. Otherwise, you might lock yourself.

Hint: Only users integrated in PPOMA_BBP and supplied with the basic attributes are able to work without issues in the Web interface. Therefore, you must first upload user SRMADMIN-## (pre-delivered as an SU01-user only) into your organizational structure.

Start transaction

108

USERS_GEN

in SRM System

Choose

Copy Users and Employee Data from Template

Select

Create Users from existing radio button and choose SU01 Users Execute Action


2009

SRM210

Lesson: User Maintenance Exercise

Search for

Phoenix Support

as Organizational Unit (ID)

Choose

USA

as country

Choose

Continue b

Choose

All users

Choose

Continue

and Select

radio button

SRMADMIN-##

in the list

Choose

Copy

and

verify that

“Activity carried out successfully”

message appears

Choose

Back (twice)

Exercise 2 Create an SRM User via SRM User Administration Service. Caution: Log on to your system via the portal:

User ID: Password:

SRMADMIN-## (provided by instructor)

Exercise Section 2-1 As an SRM administrator working from the portal, create the manager user for the root organization unit Phoenix Enterprise Inc., using the following information: Choose

SRM Administration

Choose

SRM Administration

Choose

Business Partner: Employee

in top level navigation in the Service navigation

Enter the following personal data: Mr

as FoA (Form of Address)

David

as F. Name

Director-##

as Last Name


as Department

in the Position tab Select

2009


109


Choose

Enter

Create

SRM210

beside Position

Director

as Abbreviation.

Enter

Head of Phoenix

as Description

Select


as Department Head of to flag the user as a manger

Enter

any data

for Department Address Details

do not forget to enter

a technical valid e-mail address

e.g.: david.director##@srm210.com

in the User Account tab: Enter

##-DIRECTOR

as User ID

Repeat

a technical valid e-mail address

e.g.: david.director##@srm210.com

Maintain any

time zone, date format, etc.

Ensure that flag

Password deactivated

is marked

Add

/SAPSRM/MANAGER and /SAPSRM/EMPLOYEE

as Roles and do not forget to enter a reasonable validity time frame

Save

and Exit

Choose

Exercise Section 2-2 Now that the director user exists in SRM Server, the administrator has to create the appropriate SAP NetWeaver Portal user. Choose

User Administration

Choose

Create User

in top level navigation

Enter:

Select tab

110

##-DIRECTOR

as User-Id

initial

as password (twice)

David

as First. Name

Director-##

as Last Name

Assigned Roles


2009

SRM210


Search for

*Manager*##*

Select the role

search criteria

Manager_##

and choose

Add

Caution: the user can be directed to your SRM client later only if you have selected the portal role created for YOUR GROUP NUMBER (##). Please be very careful with this step.

Search for

Select the role

*Empl*##*

search criteria

Employee SelfService_##

and choose Add

Save and Log Off

Exercise 2-3 Validate that User ##-DIRECTOR can log on to SRM via the SAP Portal. Caution: Log on to your system via the portal:

User ID: Password:

##-DIRECTOR

initial (change to “training” or your own password)

You should find a tab for Employee Self-Services in your top-level navigation. Try to create a shopping cart for any free text items. If you do not find the Employee Self-Services navigation, check your roles or ask your instructor for support. Note: You should not get any role, permission, or attribute errors here. If you should encounter workflow errors - ignore them first. You still have to perform the workflow settings.

This step is only meant as basic testing of the preceding exercises.

Exercise 3 Create users for manager and employee via SAP GUI in SRM, upload them to your organizational structure, and create the portal users.

Exercise Section 3-1 Create users via transaction SU01. Caution: Log on to your client of the SRM system from the SAP GUI:

2009


111


User ID:

SRM210

SRMCONFIG-##

Password:


Client:

3##

Create the following users: • ##-MANAGER for Mary Manager-## • ##-EMPLOYEE for Edward Employee-## Creation of Mary Manager-##

Start transaction Search for user

SU01

and choose

##-DIRECTOR

Copy

(Shift+F5)

enter

##-MANAGER

in field to and choose Copy

enter

initial

as initial passwords (twice)

do not forget to maintain

title, name, and e-mail

and

Save

fields

Creation of Edward Employee-##

Repeat the steps from above to create user: ##-EMPLOYEE : Maintain

title, name, and e-mail

but do not forget to change the user role to

/SAPSRM/EMPLOYEE only

Choose

Save and Back

fields (as this user should be not a manger)

Exercise Section 3-2 Upload the users ##-manager and ##-employee into your organizational structure.

112

Start transaction

USERS_GEN

Choose

Copy User and Employee Data from template

Execute

Create Users from Existing ( Execute Action) SU01 Users


2009

SRM210


Select Choose

and choose

Phoenix Production

as Organizational Unit and and Continue

##-MANAGER

from the user list

Enter

Repeat the steps accordingly to upload user: ##-employee Note: You should now have two users uploaded into your organizational structure.

Exercise Section 3-3 Check if the users exist in your organizational structure and set the manager flag, flag, which is used for manager determination within the SRM workflow. Star Startt tran transa sact ctio ion n

PPOM PPOMA_ A_BB BBP P

Locate in

Phoenix Production

Double-click

the users ##-manager and ##-employee

##-MANAGER

and activate flag

Head Head of Own Own Organizational Unit

on the Basic Data tab and Save

correctly, the manager should should now wear a red shirt and a hat. Note: if you did it correctly, Exit

the transaction

Exercise Section 3-4 Create the portal users for the employee and the manager. Caution: Log on to your system via the portal:

User ID: Password:


Choose

User Administration

Choose

Create User

Enter:

2009


##-manager

as User-Id

initial

as password (twice) (twice)


113


SRM210

Mary

as First. Name

Manager-##

as Last Name

Assigned Roles

Select tab

Search for

Select the role Search for

Select the role

and do not forget to choose

*Empl*##*

search criteria

Employee Self-Service_##

and choose Add

*manager*##*

in search criteria

Manager_##

and Save Add and

Repeat the steps for user: ##-employee, but assign the Employee role only. Search for

search criteria

*Employee*##*

Select the role

Employee Self-Service_##

and choose

Add and and Save

Caution: The user can be directed to your SRM client later only if you have selected the portal roles created for YOUR GROUP NUMBER (##) . Please be very careful with that step.

Exercise 4 Run the report to check the consistency of the attributes for the entire organizational structure and its users. From the SAP GUI of your SRM client: Choose menu path System Services Reporting !

Enter

BBP_CHECK_CONSISTENCY

Choose

114 114

(or start transaction SA38) as the Program

Execute

Choose Enter

!

Company 50000### (ID of the Root Organization)


as the UTYPE

2009

SRM210


Select

Shopping Cart (SC)

Choose

as the User Attributes for Application

Execute

Are there any messages? ______________________________________ _____________________________________________________ _______________ If yellow lights appear, appear, you probably probably do not have critical errors. For example, the system currently is missing the catalog attribute (CAT) that will be maintained later in the catalog unit.

Hint: As an optional exercise, you could also start transaction USERS_GEN USERS_GEN to check your users.

In the next step, select Check User and Employee Data . Select any user and Execute the program. Alternately, start program HRALXSYNC from transaction SA38.

Exercise 5 (Optional) More user creation options following exercises exercises are not required required for Hint: The users created in the following the course flow; therefore, feel free to deviate from these exercises or omit them. Caution: Log on to your client of the SRM system from the SAP GUI:

User ID:

2009

SRMCONFIG-##

Password:


Client:

3##


115


SRM210

Exercise 5-1 Import user data from a csv file. Hint: In the following exercise, you work with the prepared file user_gen.csv. If you want to create this file yourself, you have to maintain all necessary address address data in a Microsoft Microsoft Excel sheet (or in a text editor) and save this file in csv/txt format.

Exercise Section 5-1-1 Download the file user_gen.csv from your SAP Business Workplace. Enter the SAP Business Workplace. Choose

SAP Business Workplace

Expand

Shared folders

Open folder

SRM210: SRM210 Files

Double-select

SRM210 SRM210 Demo File for USERS_GEN

Go to

Attachments

Select

USERS_GEN_DEMOFILE

Choose

in the SAP Easy Access screen

tab page

Export attachment

to download download the file

Choose

Desktop

as Save in

Choose

Save

to finish the download

Choose

Back (twice)

Exercise Section 5-1-2 Generate users by uploading the user data from the file user_gen.txt. Start transaction Users Generation (USERS_GEN) from your favorites. Before you start with the next steps, verify that you are out of Caution: Before the organization organizational al plan or that you are in display mode.

116 116


2009

SRM210


Choose

Copy Users and Employee Employee Data from Template

Choose

Upload User from File

Choose

Execute Action

Search

Choose

Choose

Start

radio button

USERS_GEN_DEMOFILE.txt

file in your local Desktop directory

Select All

to set all indicators indicators for the Details on File Contents and Continue

Back

(three times)

PPOMA_BBP

and verify that Choose

new Users

were were create created d in the organizational structure

Back

Hint: The upload procedure via transaction USERS_GEN is designed for initial upload only. No delta uploads or user deletion during upload is supported. Note: In the next step, the users would be created in SAP Netweaver Portal as well. This step is omitted here. Feel free to go ahead with portal user creation on your own.

Exercise 5-2 Import users from other systems via RFC. Start transaction Select

Choose

2009

USERS_GEN

in SRM System

Copy Copy Users Users and Employ Employee ee Data from Template

Import Users from from Other System via RFC

Choose Enter

radio button

Execute Action

initial

as Initial Password


117


SRM210

Select

Phoenix Support

as Organizational Unit (ID)

Choose

USA

as Country and Continue

T90CLNT090

as RFC destination

Select

Select User

WOOD or some others

Choose

Copy

Back (twice)

Optional: Verify via PPOMA_BBP

Exercise 5-3 Deletion of users from SAPGUI. Start transaction USERS_GEN once more and select Delete User Accounts and Employees. Execute Execute the selection selection dialog and select a user from the result list. Caution: Delete only users created by the file upload exercise from above, or any other dummy user created by yourself; do not delete any config, admin, employee or manager user! You will need them later.

evaluate how to delete a Hint: If you have some time left, you could also evaluate user via portal and SRM Administration transactions.

Exercise 5-4 Check out the basic portal user export and import features. Caution: Log on to your system via the portal:

User ID: Password:

Choose Enter


User Administration


*##*

as Search Criteria and choose Go

Selec Selectt all all user userss from from Select All the list via and then

Export

You should now find a small window containing the user data in text format

118 118


2009

SRM210


In the next step, open Microsoft Word (or another editor) from your Start menu. menu. Via Copy and Paste

copy the the user user data from the portal window into Word

and Save the file to your Desktop using file type *.txt

Edit the file. For example, rename rename or copy some user data, and save the file. Choose Choose Browse

User Administration


Import

for your file

and choose Upload

You should find status Created in the Import Protocol a a few seconds later. Also check the user changes in the portal user administration section.

Exercise 6 (Optional) Questions

Exercise Section 6-1 Business Partner – Organizational Management What is the purpose of running transaction BBP_BP_OM_INTEGRATE after setting up the organizational structure? _____________________________________ ___________________ ___________________________________ _________________ _____________________________________ ___________________ ___________________________________ _________________ _____________________________________ ___________________ ___________________________________ _________________ _____________________________________ ___________________ ___________________________________ _________________ _____________________________________ ___________________ ___________________________________ _________________

Exercise Section 6-2 Attributes for the organizational units For which purposes do you need the attribute ACS? _____________________________________ ___________________ ___________________________________ _________________ _____________________________________ ___________________ ___________________________________ _________________ _____________________________________ ___________________ ___________________________________ _________________ _____________________________________ ___________________ ___________________________________ _________________

2009


119


SRM210

Exercise Section 6-3 Where in the SRM Server system can you configure the characteristics of attribute values and their inheritance? ____________________________________ ______________________________________________________ __________________ ____________________________________ ______________________________________________________ __________________ ____________________________________ ______________________________________________________ __________________ ____________________________________ ______________________________________________________ __________________ ____________________________________ ______________________________________________________ __________________

120


2009

SRM210


Solutions 6-1 Business Partner – Organizational Management What is the purpose of running transaction BBP_BP_OM_INTEGRATE after setting up the organizational structure? You run this transaction transaction to ensure ensure that all of the business business partners were created created correctly. The system checks the organizational structure for missing data, such as addresses, addresses, and lets you know if inconsistenc inconsistencies ies are discovered. discovered. It is important important to settle those inconsistencies, or they can cause problems later.

6-2 Attributes for the organizational units For which purposes do you need the attribute ACS? The attribute ACS contains the back-end system in which Accounting Accounting has to be checked. checked. You need this attribute value for invoices without PO reference reference or for local invoices.

6-3 Where in the SRM system can you configure the characteristics of attribute values and their inheritance? In table T77OMATTR, you can define the value type for an attribute in the organizational structure, or whether it is mandatory to maintain this attribute in the PPOMA. Also, the rules for inheritance inheritance can be changed here.

2009


121


SRM210


122



2009

SRM210

Unit Summary


2009

•


•


•


•


•



123

Unit Summary

124

SRM210


2009

Unit 4 Workflow Unit Overview This unit introduces configuration of the SAP SRM workflow environment.


Explain the difference between Application Controlled Workflow and Process Controlled Workflow

•

List the mandatory basic workflow settings

•

Use and configure the Process Controlled Workflow

•

Perform basic and application-specific workflow customizing

•

Evaluate some of the pre-delivered SRM Server workflows

Unit Contents Lesson: Workflow...............................................................126 Lesson: Workflow Exercise....................................................143

2009


125

Unit 4: Workflow

SRM210

Lesson: Workflow Lesson Overview The lesson explains the configuration of the SRM Process Controlled Workflow and provides a short comparison to the old Application Controlled Workflow.



•


•


Business Example You decide to evaluate the Process Controlled Workflow for the approval of your SRM procurement documents.

Workflow Overview The SAP SRM workflow enables you to perform approvals of documents electronically. Depending on your document data and your configuration settings, the system determines the necessary approval and completion steps, as well as the requested approvers.

Figure 51: SRM Server Workflow Example

All SRM documents need to have status Approved to create any kind of follow-on document. In other words, workflow configuration in SRM Server is a mandatory task even if you do not want to have approvals performed by real business users.

126


2009

SRM210

Lesson: Workflow

The SRM workflow is based on the SAP Business Workflow engine, but is enriched with an SRM-Server-specific framework.

Figure 52: Application-Controlled Workflow vs. Process-Controlled Workflow

Application-Controlled Workflow

The existing workflow environment from SRM 5.0 and lower – the so-called Application Controlled Workflow– is still supported with SRM 7.0. The concept of this workflow engine is that there are multiple workflow templates, each linked to exactly one business object with its own specific workflow features. For example, WS10000031 controls the two-step approval of shopping carts, while WS140000089 is used for a one-step approval of contracts. As you may often want to utilize different approval processes for each document, start conditions determine which workflow needs to be started. Note: The figures above shows a simplified picture. For example, in the Application Controlled Workflow, there is also a “Changed” event. Process-Controlled Workflow

The Process Controlled Workflow was introduced with SAP SRM 6.0 (which has been delivered to only a few customers). As of SRM 7.0, the Process-Controlled Workflow is the recommend workflow, as this workflow concept offers enhanced features and will be developed further, while the Application-Controlled Workflow only remains in support.

2009


127

Unit 4: Workflow

SRM210

The Process-Controlled Workflow is based on a generic workflow template. The detailed approval procedure is determined via the Process Schema. The process schema itself utilizes the SAP Business Rules Framework (BRF) to evaluate rules and expressions that operate the single workflow steps.

Figure 53: Configuration of Application-Controlled Workflow

Configuration steps for the Application-Controlled Workflow: 1.

Perform basic workflow customizing to enable the SAP workflow engine.

2.

Activate event linkage: Select the workflow template(s) that best reflects your business needs (or create an own template) and activate it. Assign agents to the tasks: Select the tasks belonging to the workflows you want to implement and assign the potential processors (approvers) to these tasks.

3.

128

It is likely that you will need more that one workflow per business object. Maintain start conditions to determine which workflow needs to be started depending on conditions, for example, total value or account assignment.


2009

SRM210

Lesson: Workflow

In general, it is mandatory that each business object has status Approved even if you do not want to utilize document approvals at all. This means you have to activate all workflow templates for automatic approval (system approval) for all of the SRM documents involved in your business processes. Hint: If you need further information about the configuration of the Application-Controlled Workflow, please check the (IMG) documentation or the SRM 5.0 training materials. Note: Even if you decide to use Process-Controlled Workflow in general, there are a few workflows still on the old technology:

WS10400022 – Contract Alert Workflow WS10000192 - Approval Workflow for Internal Users WS10000209 - Approval workflow for new bidder/supplier WS10000093/WS10000100 -Procurement Card Approval PO Response Workflows

Figure 54: Configuration of Process-Controlled Workflow

2009


129

Unit 4: Workflow

SRM210

Configuration steps for the Process-Controlled Workflow: 1.

Perform basic workflow customizing to enable the SAP workflow engine (same procedure as with the Application-Controlled Workflow).

2.

Activate Start Event Triggering for generic workflow template WS40000014 and generalize some tasks.

3.

Define Process Schema (with potential multiple levels) to model your workflow process flow. The Business Rules Framework (BRF) provides events and expressions to evaluate which process schema need to be evaluated and which process level needs to be executed. There is a multiple linkage between process schema and BRF events and expressions. SAP provides pre-defined events and expressions, as well as sample BC sets (Business Configuration Sets) for some approval procedures across all SRM business objects.

Process-Controlled Workflow Configuration Details This following section describes the basic settings for the configuration of the Process-Controlled Workflow.

Figure 55: IMG Settings for Process-Controlled Workflow

130


2009

SRM210

Lesson: Workflow

Selection of Workflow Framework: In this area you can switch from the (old) Application-Controlled Framework to the Process-Controlled Framework. The selection is done on basis of the business objects; however, it makes sense to decide in general about your framework. Basic Workflow Customizing: This enables the SAP Business Workflow engine. These settings are necessary in general and do not depend on the workflow framework. Event Trigger Confirmation: In this Customizing activity, you define that the main workflow approval process template (WS 40000014) can be started with an event. Generalize Tasks: Set all tasks of task groups TG 40000003 and TG 40000007 as “general”. This is necessary for single-dialog and background steps. Optional: Check Event Triger Linkage and Task Consistency: Validate the event-trigger and task-generalization settings from the preceding steps. This is optional. Copy BRF Objects: There are SRM-specific Business Rules Framework (BRF) objects. With this activity, you copy them from client 000 to your client. Caution: If you switched from the application-controlled workflow to the process-controlled workflow framework, there is no support if you switch back to the old application-controlled workflow!

However, you may start your SRM 7.0 project (for example, after the upgrade) with the old workflow first, and switch later to the Process Controlled Workflow. Hint: You can find more information on the SAP Service Marketplace: http://service.sap.com/srm

SAP Developer Network (SDN) http://sdn.sa p.com Forums SAP Solutions SRM - Workflow & User/Vendor/Org. Management !

!

!

or in the BPX Community, which is also located on the SDN.

2009


131

Unit 4: Workflow

SRM210

Figure 56: Process-Controlled Workflow Configuration Blocks

Process overview:

132

•

Ordering a shopping cart (SC) raises an event.

•

Event triggers BRF events and BRF expressions to return the valid process schema.

•

Generic workflow is called, which is linked to further workflow templates.

•

Process schema defines the detailed workflow procedure and may contain multiple process levels.

•

Evaluation of single process levels again is linked to BRF events and expressions.

•

Process level is designed as approval or completion step.

•

Approval or completion is triggered by separate workflow templates.


2009

SRM210

Lesson: Workflow

Figure 57: Process Schema and Levels

A process schema always refers to a business object (for example, BUS2121 Shopping Cart). It encapsulates a draft of the approval process for that business object. You can create multiple process schemata. A BRF event that refers to BRF expressions determines the currently valid process schema first. The process schema at least contains one level: Auto Approval. However, it is likely that there are further levels for real user approvals. Each level determines the type of approval ( approval = without change options, or completion = including change options) and the responsible agents (for example, line managers or users with a specific role). Whether an approval process within a single process level needs to be performed is determined by BRF expressions that are raised by a BRF event. The BRF expressions might be nested and provide the result “true” or “false” at the end. When “true”, the workflow assigned to the according process level is raised. When “false”, the system evaluates the next process level. If no other preceding level leads to a document approval (or declination), the last process level (Auto Approval) approves the document to release the creation of the follow-on documents. The last step could even contain Auto Rejection, if there was no preceding user approval. A process schema contains the entire workflow procedure. The schema may contain n steps which result in (n-1) approval steps, plus at least one auto approval step at the end. Not every step in a process schema will actually end as an approval procedure; this depends on the results of the BRF expressions.

2009


133

Unit 4: Workflow

SRM210

Figure 58: Business Rules Framework

By way of their application class, applications must be registered in the BRF to be able to use BRF services. The BRF tool comprises of a runtime environment and a maintenance environment. The main objects of the BRF are: Event: Calls expressions Expression: Delivers results (“true” or “false”, but also complex results for intermediate calculations within nested expressions)

Groups: Optional possibility to group own customer objects Rule: Evaluations conditions - NOT USED BY SRM Rule Set: Groups rules - NOT USED BY SRM Action/Actions: NOT USED BY SRM

134


2009

SRM210

Lesson: Workflow

Event

Events are points in the program of the application using the BRF, at which there should be the possibility to evaluate current data. BRF events and their relevant contexts are defined by the developers of the application. Within the application, SAP offers hundreds of events that were preconceived by developers and that can be "refined" by customers. Notes on naming conventions [0]EV-[Type]-[Number] : •

0EV refers to the SAP prefix (the SAP namespace for events is either 0 to 9 or A to W, and the customer namespace is X, Y, or Z).

• Type refers either to the evaluation of the process schema of a business object or to the evaluation of the process level (0). • Number refers to the version of the event (two alphanumeric characters). Example: 1EV002 evaluates a process level. Expression

An expression in BRF terms is an object that returns a result of a primitive type. Expressions can also be nested. This means that there are expressions that access other expressions, and expressions that do not access any other expressions (final expressions). Expressions can be split into value requests (VR) and operations (OP) Notes on naming conventions [0]-[Type]-[Business_Object]-[Data type]-[Description]: •

0 refers to the SAP prefix (the SAP namespace is either 0 to 9 or A to W, and the customer namespace is X, Y, or Z).

• Type refers to a constant (C), a value (V), or a constraint (Boolean). •

Business Object refers to the description of the business object type, for example WF (general workflow), SC (shopping cart), US (user), and so on.

•

Data Type describes the data type of the expression: I Integer, N Numeric text, P Packed number, C Text field, F Floating point number, T Time field, D Date field, M Currency amount, B Boole, and R Reference in accordance with ABAP Dictionary type

• Description is a short description of the expression. Example: 0B_SC_XSTFRTXTLNTM checks if a free text item exists.

2009


135

Unit 4: Workflow

SRM210

Figure 59: Process Schema Example

The above figure shows an example of a process schema. The schema is linked to BUS2121 - Shopping Cart. The schema consists of several approval/completion levels, plus a final auto approval step. In every level, the entry for the Evaluation ID raises an event that is linked to one or more expressions determining if the actual level is valid or not. If this level is valid, the system generates a work item for the responsible approvers. Those approvers (agents) are also defined on process level; SRM 7.0 uses a BAdI with pre-delivered examples to determine the agent: - Specific employee - Users of a specific role - Line manager of requester - Manager of previous approver - Manager of purchasing group - Member of responsible purchasing group - Owner of source document case of confirmation or invoice - Depending on spending and approval limit For additional options, the BAdI can be supplemented with customer-specific coding.

136


2009

SRM210

Lesson: Workflow

Steps for configuration of a process schema: 1.

Create an entry for the process schema determination for each of your business objects.

2.

The process schema determination raises an event: create an event in BRF. The event calls one or multiple expressions to determine the process schema to be used.

3.

Create one (or multiple) process schemata per business object.

4.

Enter process level(s) linked to an event that evaluates if the actual level is valid or not. Create the event and expression(s) via BRF transaction. Maintain approval Level Type (Approval or Completion) and also specify the Responsible Resolver Name (Agent) and Decision Type.

5.

Do not forget to insert one level for auto approval if your workflow design does not contain at least one mandatory approval step across all possible scenarios.

6.

Optional: Define default values for ad-hoc approver (depending on BRF expressions).

7.

Optional: Maintain rule for automatic reviewer determination.

8.

Optional: Acceptance by contact person: A person (for example, the requester) gets a work item as soon as the approval process is finished.

Figure 60: Decision Types

The Process-Controlled Workflow delivers four Decision Types to determine how the approval procedure will be conducted: Type 1: Decision for Entire Document (Approval on Header Level) Type 2: Item-Based Decision for Entire Document (On Item Level - all items)

2009


137

Unit 4: Workflow

SRM210

Type 3: Overall Decision for Partial Document (On Header Level - but only for partial document) Type 4: Item-Based Decision for Partial Document (On Item Level - but not for every item) Caution: Only the business object shopping cart supports all decision types. However for “Completion” only, decision types 1 and 2 are available.

Contract and purchase order are also supporting decision type 2. All other documents are supported by type 1 only.

Figure 61: BC Set Activation

SAP delivers example BC sets for an easy configuration of some basic approval processes. Uploading BC sets creates events, expressions, and entries for process schema and process level. For further details, call transaction SCPR20 and use the search help for BC sets in the /SAPSRM/* namespace.

Additional Information BAdIs for Process -Controlled Workflow

Define Agents: /SAPSRM/BD_WF_RESP_RESOLVER You can use this Business Add-In to assign SAP SRM purchasing documents (or separate parts of these documents) to agent groups for (parallel) approval. Define Deadlines for Events: /SAPSRM/BD_WF_DEADLINE You can use this Business Add-In (BAdI) to calculate the different deadlines that are used in a completion or approval process. Configure Process Levels: /SAPSRM/BD_WF_PROCESS_CONFIG

138


2009

SRM210

Lesson: Workflow

You can use this BAdI to build your own runtime version of the process schema on the basis of the design time process schema as defined in customizing. Manage Process Restarts: /SAPSRM/BD_WF_PROCESS_RESTART You can use this BAdI to avoid a complete process restart after a document change. Determine Shopping Cart Value for Purchasing Budget Workflow: BBP_SC_VALUE_GET This BAdI allows you to implement your own method for determination of the value of a shopping cart Adjust Search Help for Ad Hoc Agent: /SAPSRM/BD_WF_ADHOC_AGENT_F4 This BAdI enables you to filter the available users to be inserted Adjust Search Help for Reviewers: /SAPSRM/BD_WF_REVIEWER_F4 This enables you to filter the available users to be inserted. Define Reviewers: /SAPSRM/BD_WF_REVIEWER_RULE. Assign SRM purchasing documents to agent groups for review. Customer Enhancement of Offline Approval: BBP_OFFLINE_APP_BADI

Figure 62: Forwarding Work Items as E-Mail

Program /SAPSRM/OFFLINEAPPROVALSEND allows you to forward work items as e-mail.

2009


139

Unit 4: Workflow

SRM210

The online procedure provides users with a link to the system logon. The offline option only creates an e-mail reply that is sent back to the SRM system. Report /SAPSRM/OFFLINEAPPROVALGET then transfers the offline replies to the appropriate work items. Note: For more information, please also check the Solution Manager configuration guide.

Figure 63: BRF Expression Case Type Example

140


2009

SRM210

Lesson: Workflow

Figure 64: BRF Truth Table Example

Figure 65: BRF Formula Example

2009


141

Unit 4: Workflow

SRM210


142

•


•


•



2009

SRM210

Lesson: Workflow Exercise

Lesson: Workflow Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •


•


Business Example You need to configure the Process Controlled Workflow for your evaluation landscape.

Exercise 1 Select the workflow framework. Caution: Log on to your client of the SRM system:


3##


You want to evaluate the Process Controlled Workflow, so you need to verify that the system settings are activated accordingly. Choose SAP Implementation Guide SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Business Workflow Select Workflow Framework . !

!

!

!

!

To evaluate the new Process-Controlled Workflow, please check that the following entries are existing in the Multiple Selection of the Object Type field.

2009

SAP Business object types

Business Object type Description

BUS2121

SRM Shopping cart

BUS2200

SRM Local Bid Invitation

BUS2201

SRM Local PO

BUS2202

SRM Local Bid


143

Unit 4: Workflow

SRM210

SAP Business object types

Business Object type Description

BUS2000113

SRM Contract

BUS2203

SRM Confirmation

BUS2205

SRM Invoice

Hint: You can select Show Currents Settings and Execute

to check which workflow framework is currently in use. Set the indicator to Process Controlled Workflow De-activate Simulate and choose Execute

.

Confirm the warning message and leave the transaction after the report has finished. Note: If your client has already switched to Process Controlled Workflow (PC WF), you can only display the settings. The button for the switch to the PC WF would be deactivated in that case.

Exercise 2 You need to make certain workflow settings in the system for technical and operational reasons. Verify and complete the necessary settings.

Exercise Section 2-1 Ensure that the basic workflow engine is configured and operating correctly. The Verification Workflow helps you to check that. In the IMG, choose SRM Server Cross-Application Basic Settings Business Workflow Process-Controlled Workflow Technical Configuration Customize SAP Business Workflow Automatically . !

!

!

!

!

Select and expand

Maintain Runtime Environment

root

Choose

Perform Automatic Workflow Customizing (F9)

to maintain all technical standard settings

Run the validation workflow to validate that the basic settings are working:

144

Choose

Start Verification Workflow

and confirm any messages

Choose

SAP Business Workplace

to enter the workflow inbox


2009

SRM210


Double-click on Choose Select

(in column class)

to execute the first step in the Workflow

Execute background step immediately

Update

Verify that

you received two messages

Select

Back (twice)

to leave the basic workflow settings.

Exercise Section 2-2 Check the Event Trigger Configuration. Choose Business Workflow Process-Controlled Workflow Configuration Check Event Trigger Configuration . !

!

Technical

!

Enter

Choose

WS40000014

Select tab

Goto

!

as Workflow and Choose Enter to confirm

Basic data

Start Events

The entries in the Start Events should look like this:

Figure 66: Event Type Linkage

Caution: Do not change the workflow template. Leave without saving.

Choose

Exit (twice)

Exercise Section 2-3 Check Event Type Linkage. Choose Business Workflow Process-Controlled Workflow Configuration Check Event Type Linkage . !

!

Technical

!

2009


145

Unit 4: Workflow

SRM210

Check whether an entry has been added for the main workflow and whether the linkage is active. This entry should contain the following: Hint: For your convenience use the Position icon to search for the data.

Then select via F4

CL (ABAP class)

as Object category

/SAPSRM/CL_WF_PDO

as Object type

READY_FOR_WORKFLOW

as Event

WS 40000014 (main workflow)

as Receiver Type

Choose via Details

Type linkage

Set

Linkage Activated

Choose

Save and Back

Second step: Select via F4

CL (ABAP class)

as Object category

/SAPSRM/CL_WF_PDO

as Object type

READY_FOR_RELEASE

as Event

SRM_PROCESS_START

as Receiver Type

Choose via Details

Type linkage

Set

Linkage Activated Save and Back Note: You cannot maintain the settings from the table overview; always use the navigation details mentioned above. Caution: Before you leave the transaction, verify in the Table Overview that both checkboxes for Type Linkage are activated in fact.

Leave the transaction afterward.

Exercise Section 2-4 Generalize tasks. Choose Process-Controlled Workflow Tasks.

146

!

Technical Configuration


!

Generalize

2009

SRM210


“Generalize” the task groups TG 40000003 and TG 40000007. Choose Enter

Task Group

as Task Type

40000003 [SRM Approval Process Decision Tasks]

as Task

Choose

Execute

Select

All lines

Choose

Generalize

Choose

Back

Repeat the same steps for Task Group 40000007 ! Leave the transaction (choose Back ).

Exercise Section 2-5 Check task generalization (optional). Choose Process-Controlled Workflow Generalization. Select Enter

Choose

!

Technical Configuration

Task Group

as Task Type

40000003

as Task

!

Check Task

Display (F7)

Double-click a standard task from the task group list of Choose from the menu

Additional Data Classification Display

In the area

Classification

!

!

you should see that the task is marked as general task

Leave the transaction

Exercise Section 2-6 Check task consistency (optional). Choose Check Task Consistency .

2009


147

Unit 4: Workflow

SRM210

Enter

Mark

/SAPSRM/WF_CFG

as Package

Extended Check

and

Execute

Leave the transaction You should find all tasks on status “green”.

Exercise Section 2-7 Copy BRF objects. Execute a report to copy Business Rule Framework (BRF) objects specific to SAP SRM in your client. Choose Copy BRF Objects or start transaction /SAPSRM/BRFTRANSPORT. Main selection

Select

SRM_WF

as Application class

Sub-selection and Object Restrictions

Select

A (active)

Select

All objects

Import Status

Operations

Double-check that

000

is maintained as source client

Do not forget to choose

Copy

radio button

Display options

Select

Display Error Messages

De-select

Choose and

Simulation flag Execute

Back

(after you have reviewed the status information)

Exercise 3 Activate BC sets and configure the process schema.

Exercise 3-1 Activate pre-delivered BC sets for your business objects.

148


2009

SRM210


The upload of existing BC sets creates events and expressions, as well as process-schema and process-level settings in the IMG. Upload some pre-defined workflow examples now. Caution: The upload of the BC sets locks some cross-client tables. Therefore, each group (each client) needs to work exclusively on that step, similar to the exercises with the product download.

PLEASE ASK YOUR INSTRUCTOR BEFORE YOU PROCEED! Choose Business Workflow Process-Controlled Workflow Business Process Configuration Activate Sample BC Sets for Process Level Definition or start transaction SCPR20. !

!

!

Select with F4

/SAPSRM/ C_CO_600_000_SP04 (Confirmation without Approval)

as BC Set

Choose

Activate BC Set

to upload the data

Confirm

the dialog box

with its default values

Upload the following BC sets according the procedure described above. Note: Always use /SAPSRM/ as prefix for the BC set name.

and

C_CT_600_000_SP04

Contract Without Approval

C_IN_600_000_SP04

Invoice Without Approval

C_PO_600_000_SP04

Purchase Order Without Approval

C_QT_600_000_SP04

RFx Response Without Approval

C_RQ_600_000_SP04

RFx Without Approval

C_SC_600_001_SP04

Shopping Cart with One-Level Manager Approval

Exit

Note: You can ignore any warnings as long as there is no error message.

In case of error messages, please contact your instructor.

2009


149

Unit 4: Workflow

SRM210

Caution: Please kindly inform your instructor when you are done so that he or she can ask the next group to start the upload.

Hint: Before you upload a BC set, you might be interested to check what would happen if you upload that data set. It is possible to analyze that by choosing Compare with Customizing data .

As long as you do not activate a BC set, you can review those. Be careful not to interfere with other groups who are currently performing their exercises. We recommend that you review the BC set data later, when everyone is done with the exercises. Note: You may feel free to upload additional BC sets (for example /SAPSRM/TH_BO_600_001_SP04) during the course, after everyone has performed the standard exercises.

Please consider: The upload of a new BC set for one or several business objects overwrites existing settings. This might cause your workflow to stop running. In this case, simply switch back the schema evaluation manually to an easy process-level schema or – the simplest way – upload the BC set for “business object without approval” again.

Exercise 3-2 Review the settings for the process level configuration.

150


2009

SRM210


In the IMG, choose Business Workflow Process-Controlled Workflow Business Process Configuration Define Process Levels. !

!

!

1.

Select BUS2121 SRM Shopping Cart.

2.

Select Process Schema Evaluation . Write down the entry for schema evaluation. This must be an event. _____________________________________________________

3.

Call transaction BRF in a new session. Select application class SRM_WF and search for your event in the tree list. What expressions are called by the event ? _____________________________________________________ _____________________________________________________

4.

What is the result of the schema evaluation? Which schema will be called for BUS2121? _____________________________________________________

5.

What kind of approval process for shopping carts is currently active ? _____________________________________________________

6.

Optional: Check the schema evaluation and process levels for all other SRM business objects as well. _____________________________________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________

Exercise 4 Upload users WF-BATCH and TRA_RFC into your organizational structure. Note: According to SAP Note 1268821 (Configuration of Central Contract Management), it is recommend that user WF-BATCH – the technical workflow user – is integrated into PPOMA.

2009


151

Unit 4: Workflow

SRM210

Proceed with the following steps. 1.

Log on as SRMCONFIG-## to your SRM client from SAP GUI.

2.

Call transaction SU01 and add the following roles to user WF-BATCH: /SAPSRM/EMPLOYEE and /SAPSRM/ST_PURCHASER.

3.

Start transaction USERS_GEN and upload WF-BATCH into your local purchasing organization.

4.

In a second step, upload user TRA_RFC into your local purchasing organization (no further role assignment needed). Note: There are a few business scenarios (for example, Central Contracts and External Sourcing/Plan-Driven Procurement) with RFC and PI communication from ERP to SRM.

The communication users involved in this process need to have some attributes, thats the reason why we upload user TRA_RFC into our organizational structure as well.

Exercise 5 Checkout your shopping cart workflow settings. 1.

Log on as ##-EMPLOYEE via the portal. (Password: initial/training or your own).

2.

Create a shopping cart via Employee Self-Services. Describe (Free Text Item) what you need, using one of your product categories (for example, “001” or “LOCAL1”).

3.

Check the approval preview before you order the shopping cart.

4.

If everything is working fine, your manager (##-MANAGER) now should have a work item in his or her inbox. Log on as ##-MANAGER (password: initial/trainingg or your own) and approve the cart.

5.

Create additional shopping carts: Add approvers and reviewers (for example, ##-DIRECTOR or SRMADMIN-##) manually Perform approvals, rejections, changes, and reviews. Also check the shopping cart status and potential notifications.

Exercise 6 (Optional) Advanced workflow exercises.

152


2009

SRM210


Exercise Section 6-1 You want to create an own process schema for shopping cart approval. Note: This optional exercise takes anadditional 45 minutes. If you are interested in an easier one, proceed with Exercise 6-2

Requirements: Step Condition

Approver

1

Free-text item exists OR shopping cart value is higher than 100 USD

Line Manager, Approval with Completion; Decision Type 1

2

If product category of an item equals 00204

SRMADMIN-##, Approval with Completion, Decision Type 2

3

If total value is higher than 20.000

Manager of Manager, Approval, Decision Type 2

Hints: 0B_SC_XSTFRTXTLNTM checks if there is a free text item. 0B_CT_PRCAT_EX_CHECK checks if a special product category exists. 0C_C3_C_TOTALVALUE calculates the total value. Make a draft on a sheet of paper first for all steps; have in mind the schema evaluation and the events for every-level determination and the corresponding expressions. Do not create the entire process completely; start with one level and test. Hint: You can find additional examples and hints in Exercise 6-2.

Exercise Section 6-2 Upload and explore some additional BC set examples for shopping cart approval. Caution: Do not forget that the BC set upload will overwrite existing settings, so you might have some additional work afterwards.

Start transaction SCPR20 and upload /SAPSRM/T_SC_600_000_SP04 (Test Workflow Settings: Shopping Cart). Explore especially schema 9C_BUS2121_EX01. Feel free to check out others as well. Note: As you currently do not yet have a purchaser user, some enhanced workflow testing needs to be postponed until Unit 8.

2009


153

Unit 4: Workflow

SRM210

Solutions Solution 3-2 Review the settings for the process level configuration. From the IMG, choose Business Workflow Process-Controlled Workflow Business Process Configuration Define Process Levels. !

!

!

1.

Select BUS2121 SRM Shopping Cart.

2.

Select Process Schema Evaluation . Write down the entry for schema evaluation. Note this must be an event. 3EV_SC_600_001

3.

Call transaction BRF in a new session. Select application class SRM_WF and search for your event in the list. What expressions are called by the event? 3C_SC_600_001 (Schema Constant)

4.

What is the result of the schema evaluation? Which schema will be called for BUS2121? 3C_SC_600_001

5.

What kind of approval process for shopping carts is currently active? In level 100, Event 3EV_SC_600_001_100 calls expression 3B_SC_600_001_100, which supplies constant “True” . This means, level 100 – manager approval – will be always performed.

_____________________________________________________ 6.

Optional: Check the schema evaluation and process levels for all other SRM business objects as well. All other objects should have entries for schema evaluation linked to the process schema with only one auto approval step.

154


2009

SRM210



2009

•


•



155

Unit Summary

SRM210


156

•

Explain Explain the differenc differencee between between Application Application Controlled Controlled Workflow orkflow and Process Controlled Workflow

•

List the mandat mandatory ory basic basic workfl workflow ow setting settingss

•

Use and config configure ure the Process Process Contro Controlle lled d Workflo orkflow w

•

Perform Perform basic and applicationapplication-specifi specificc workflow workflow customizing customizing

•

Evalua Evaluate te som somee of of the pre-de pre-deliv livere ered d SRM SRM Server Server workfl workflows ows


2009

Unit 5 Master Data Unit Overview This unit explains the purpose of master data in SRM Server, as well as the technique technique and tools to replicate replicate and create objects. objects.


Explain Explain how to replic replicate ate vendor vendorss from from a SAP SAP back-e back-end nd sys system tem

•

Describ Describee the the busine business ss part partner ner concep conceptt for for vendo vendors rs and and v vend endor or users users

•

Replic Replicate ate vendor vendor master master data data form form your your SAP back back-en -end d sy system stem into into SRM SRM Server

•

Creat Createe vend vendor or cont contac actt pers person onss

•

Replica Replicate te produc products ts from from an SAP back-e back-end nd system system

•

Expl Explai ain n the the midd middle lewa ware re basi basics cs

•

Config Configure ure and perfor perform m the the mater material ial replic replicati ation on p proc rocess ess from from the SAP back back end

Unit Contents Lesson: Vendor Replication ...................................................158 ...................................................158 Lesson: Vendor Replication Exercise ........................................166 ........................................ 166 Lesson: Product Mas Master..... .... .... .... ... .... .... .... .... .... .... ... .... ... ..177 ..177 Less Lesson on:: Pro Product uct Mas Maste terr Exe Exerc rciise .. ... ... .. ... .. ... ... .. ... .. .. ... ... .. ... .. .185

2009


157

Unit 5: Master Data

SRM210

Lesson: Vendor Replication Replication Lesson Overview This lesson introduces you to the process of vendor replication from the SAP ERP back-end system to SRM, and the creation of vendor users in SRM Server.


Explain Explain how to replic replicate ate vendor vendorss from from a SAP SAP back-e back-end nd system system

•

Describ Describee the the busine business ss part partner ner concep conceptt for for vendo vendors rs and and vendor vendor users users

Business Example You are currently using an SAP back-end system that contains vendor master data. You want to replicate that data for your SRM procurement processes.

Supplier Master Data

Figure 67: Vendor Master Data in SRM Server and SAP Back End

All master data can be found locally in the SRM system. This data includes product master records, business partner records, and product categories. You can replicate the master data from the ERP back-end system to the SRM Server. Business partner master records correspond to vendor master records in the SAP back end, while products correspond to material master mas ter and service master.

158


2009

SRM210

Lesson: Vendor Replication

Figure 68: SAP Business Partner - Concept and Relationships

The business partners are based on the role concept: concept: •

They They cover cover person personss as well well as organi organizat zation ions. s.

•

There There is a unifor uniform m and and centra centrall busi business ness partne partnerr (BP) (BP) role role conce concept. pt.

•

One One BP can can have have seve severa rall role roles. s.

The business partner relationship:

2009

•

Describ Describes es the the relat relation ionss betwe between en two two busin business ess part partner ners, s, for for exam example ple,, “is “is employee of”

•

Can Can be time time-d -dep epen ende dent nt


159

Unit 5: Master Data

SRM210

Figure 69: External Business Partners

SRM uses the SAP Business partner concept. concept. An internal or external business partner is created in SRM Server for every person, organization, or group of people who could be involved in a business transaction. Within the context of business transactions (for example, a bid invitation or a purchase order) business partners can adopt various partner functions as long as they have fulfilled the relevant relevant requirements. requirements. Business Business partners aggregate aggregate the master data of a person, person, organization, or group of people.

Figure 70: Business Business Partner Integration Integration with Organizational Organizational Management Management

160


2009

SRM210


If you have business partners that are intended for procurement processes in SRM Server, they need to be included in the vendor organizational structure to ensure that they are supplied with necessary attributes. This organizational structure is based on vendor groups containing attributes data. It is possible to have several s everal vendor groups, depending on your attributes. In the the case case of a syst system em upgr upgrad adee from from SAP SAP SRM SRM 4.0 4.0 or belo below w, you you Caution: In have to migrate your old vendor organizational structure to the new vendor group concept via report BBP_XPRA_ORGEH_TO_VENDOR_GROUP. Also check the documentation.

Figure 71: Business Partner Download

Use report BBP_UPLOAD_PAYMENT_TERMS to replicate the terms of payment from the t he back-end system syste m into SRM Server. Report Report BBP_UPLOAD_QM BBP_UPLOAD_QM_SYSTE _SYSTEMS MS can be used to replicate the quality quality management system data (optional). Transaction BBPGETVD triggers the download of ERP vendor information as business partner information in the SRM Server.

2009


161

Unit 5: Master Data

SRM210

You should take the following into account: •

Whethe Whetherr the the SRM SRM Serve Serverr is to assign assign num number berss from from the intern internal al numb number er range for business partners to be created

•

Whethe Whetherr the the vendo vendorr numbe numbers rs are are to be be copie copied d from from the the back back-en -end d system system.. Hint: If an ERP vendor number already exists as the business partner number in SRM Server (for example, for a user or an organizational unit) , the system assigns assigns a number number internally for that vendor. vendor. In this case, configure configure the internal number range so that it does not overlap with the number numb er range in the ERP back-end system.

Figure 72: Business Partner Download (2)

To add, change, or delete purchasing organization entries in your business partner data, you can use transaction BBP_UPDATE_PORG. In multiple back-end scenarios, transaction BBP_UPDATE_MAPPING can be useful, because once vendors have been replicated, they do not need to be replicated again from other back ends if their numbers are equal (top area).

162


2009

SRM210


Figure 73: Business Partner Automated Synchronization

The vendor master data can be synchronized automatically using program BBP_VENDOR_SYNC. This program should be scheduled as job. In advance of the job scheduling, you have to maintain the mentioned configurations steps. Afterward, the program synchronizes changed vendor data automatically. It is also possible to replicate all new vendors form the ERP back end automatically with this program. Nevertheless, for the initial download of vendor master data, you should not use BBP_VENDOR_SYNC, but the initial download transaction. Caution: This report does not support the upload of business partner changes from SRM Server to your SAP ERP back end.

You can use the application monitor to view local business partner changes with a potential transfer option to your ERP back end via SAP PI. Note: If you are using SRM in one client scenario, there is another bidirectional concept for the synchronization of the vendor (and product) master data.

2009


163

Unit 5: Master Data

SRM210

Figure 74: Manual Maintenance of External Business Partners

External business partners (vendors, bidders, portals, and their contact persons) can be maintained in dialog by users with administrator or purchaser roles. From this entry screen, you can also create new contact persons for an existing vendor, bidder, or portal supplier (marketplace). It is also possible to maintain internal business partners like location and company business partner data, or to delete business partners.

164


2009

SRM210



2009

•

Explain how to replicate vendors from a SAP back-end system

•

Describe the business partner concept for vendors and vendor users


165

Unit 5: Master Data

SRM210

Lesson: Vendor Replication Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Replicate vendor master data form your SAP back-end system into SRM Server

•

Create vendor contact persons

Business Example You need to replicate some vendors from your SAP back end to the SRM Server.

Exercise 1 Create a new organization in the organizational plan for vendors. Caution: Log on to your client of the SRM system from the SAP GUI:

Client: User ID:

3##

SRMCONFIG-##

Exercise Section 1-1 Add the transactions PPOCV_BBP (Create Vendor Groups) and PPOMV_BBP (Change Vendor Groups) to your favorites.

Exercise Section 1-2 Create the Vendor Root Organizational Unit. Start the transaction Create Vendor Groups (PPOCV_BBP) from your favorites. Note: Enter through the Validity Period message.

Enter

External BP

to replace Object abbr

Enter

Business Partner @ Phoenix

to replace Name

Choose

166

Save


2009

SRM210

Lesson: Vendor Replication Exercise

Choose

Back

What is the ID of the newly created organization?

Exercise Section 1-3 Add the following attributes to the vendor organization. Start the transaction Change Vendor Groups (PPOMV_BBP) from your favorites. Double-click Go to


Organizational unit

ATTRIBUTES

tab page

Enter the following data: Attribute

Value

Accounting System for Vendor Company Code

T90CLNT090 3000 / Source System T90CLNT90

Current ITS for an External Partner

Local Currency

USD

System Alias for Vendor

T90CLNT090 SRM_00_3##

Choose

Save

and Back

Exercise 2 Replicate the customizing data associated with the vendors in the SAP back-end system.

Exercise Section 2-1 Replicate the terms of payment from the SAP back-end system. Start transaction Execute Program (SA38) from the menu bar. Choose System

2009

!

Services

!

Reporting .


167

Unit 5: Master Data

SRM210

Enter

BBP_UPLOAD_PAYMENT_TERMS

Choose Enter

as Program

Execute

T90CLNT090

Choose

Execute

Choose

as System and confirm the message

Back (twice)

Note: It is not mandatory to check the application log via transaction SLG1 afterward, but if you encounter problems, you can find additional information there.

Exercise Section 2-2 Replicate the quality management systems from the SAP back-end system. Start transaction Execute Program (SA38) from the menu bar. Choose System Enter

!

Choose Enter

Services

!

Reporting .

BBP_UPLOAD_QM_SYSTEMS

as Program

Execute

Choose

T90CLNT090

Execute

Choose

as Data Procurement from System and confirm the message

Back (twice)

Exercise 3 Replicate the vendor master records ARAMI-##, MCCOY-##, and EBP-## from the ERP back-end system to the SRM Server system.

Exercise Section 3-1 Use transaction BBPGETVD and the following information to start the transmission of the vendors ARAMI-##, EBP-##, and MCCOY-##.

168


2009

SRM210


Start

BBPGETVD

via Command field of the Standard Toolbar

R3_00_800

as System

ARAMI-##

as Vendor

Select

Transfer Information Number from Dun & Bradstreet

to transfer potential maintain DUNS-numbers

Select

Take Uniform Resource Location as E-Mail

to transfer the vendors e-mail address

Select

Address Comparison to Identify Duplicates

to check for duplicates

Enter

as Object ID

Ensure that

Only Transfer R/3 Numbers radio button is set

Choose

Start Transfer

Choose

Start Transmission

Choose

Continue

Choose Enter

Choose

to confirm the message

Back

Hint: The number for the Object ID Business Partner @ Phoenix should be in the form of 50000XXX.

Check this via transaction PPOSV_BBP (Display of Vendor Groups).

Exercise Section 3-2 Repeat the replication steps from above for vendors: MCCOY-## EBP-##

Exercise Section 3-3 Display the Application Log with transaction SLG1.

2009


169

Unit 5: Master Data

SRM210

Enter

SLG1

in the Command field of the Standard Toolbar to view Application log.

Enter

BBPGETVD

as Object

Choose

Execute

and Back (twice)

Hint: You can ignore all yellow messages here, even if they are called “Error.....”

Exercise Section 3-4 Verify that the vendors were replicated and assigned to the organization. Start the transaction DISPLAY VENDOR GROUPS (PPOSV_BBP). Double-click on


Verify the created

Organizational Units

in the Organizational Structure

What are the business partner numbers assigned to the vendors?

ARAMI-##:_______________________________________ MCCOY-##:_______________________________________ EBP-##:_______________________________________

Leave the transaction .

Exercise 4 Map the replicated vendors to the local purchasing organization.

Exercise Section 4-1 Map the replicated vendors manually from the Web user interface. Caution: Log on as SRM administrator to the portal:

User ID:

SRMADMIN-##

Use the following information to map each of the replicated vendors to your local purchasing organization:

170


2009

SRM210


Choose

SRM Administration


Choose

SRM Administration

in the Detailed Navigation (left side of the screen)

Select the Query Supplier

and choose Refresh

Select

and choose Edit

ARAMI-##

Select Supplier Data Tab Choose

Add Lines

Select with F4

for Supplier Purchasing Data

Transfer all entries according to those from PUR Back Processes. Select the Company Data tab and then: Contact Data. Choose

Add Lines

for Output Media

and maintain

Output Medium E-Mail

for

Choose

Save and Close

Caution: Ensure that you really maintained a send medium for your local purchasing organization, as this is mandatory for working with local purchase orders. Note: Why add entries for the local purchasing organization? Because you want to use the vendor for classic and local scenarios in this course.

Exercise Section 4-2 Map the replicated vendors with transaction BBP_UPDATE_PORG. Caution: Log on to your client of the SRM system from the SAP GUI:

Client: User ID:

2009

3##

SRMCONFIG-##


171

Unit 5: Master Data

SRM210

Execute

BBP_UPDATE_PORG

in the Command field

Choose

PUR Local Processes

as the New purch.org.entry

Choose

PUR Back Processes

as the Add to purch. org.

Choose

Add

Choose

Continue

Hint: If you are still logged on to the portal, refresh the vendor query. You will find the additional purchasing organization entries in the query result list.

Exercise 5 Create an employee for your replicated vendors. Caution: Log on to the portal:

User ID:

SRMADMIN-##

Exercise Section 5-1 Create an employee for the MCCOY-## vendor using the following information: Choose

SRM Administration


Choose

SRM Administration

in the Detailed Navigation (left side of the screen)

Supplier

and choose Refresh

Select one of the entries for

MCCOY-##

from the query list

and choose

Create Contact Person with Reference

Select the query

Maintain the following data:

172

Ms

as Title

Cindy

as First Name

McCoy-##

as Last Name

English

as Language

USA

as Country


2009

SRM210


Set the indicator

Is Contact Person

Set the indicator

Create User for Contact Person

Enter

##-MCCOY

as User ID

Enter

initial

as Password and Repeat Password

Select

any Date Format and Decimal Notation

Add

/SAPSRM/SUPPLIER

as Role

Select Contact Data tab Enter standard entries for

Telephone Number and E-Mail Adresses

Choose

Save and Close

What is the partner number that was assigned to this contact person? _____________________

Hint: You find the business partner number in the query Contact Person. Do not forget to refresh that query first.

Exercise Section 5-2 Create a second contact person, User ID ##-ARAMI , for your vendor ARAMI-##, referring to exercise 5-1. Maintain all required data. What is the partner number that was assigned to this newly created contact person? _________________________________ Log off.

Exercise 6 Create the portal users for your SRM contact persons. Caution: Log on to your system via the portal:

User ID:

2009

SRMADMIN-##


173

Unit 5: Master Data

SRM210

Exercise Section 6-1 Create a user for supplier McCoy-##. Choose

User Administration

Choose

Create User


Enter:

Select tab

##-MCCOY

as User-Id

initial

as password (twice)

Cindy

as First. Name

##-McCoy

as Last Name

Assigned Roles

Search for

Select the role Search for

*Supplier*##*

search criteria

Supplier_##

and Choose Add

*Bidder*##*

search criteria

RFX_Respondent_##

and Choose Add

Select the role

Save and Exit

Caution: he user can later be directed to your SRM client only if you have selected the portal roles created for YOUR GROUP NUMBER (##). Please be very careful with this step.

Exercise Section 6-2 Create additional supplier users: Repeat the steps from Exercise 6-1 to create a portal user ##-ARAMI for your business partner Arami-##.

Exercise 7 (Optional) Double check that the contact person of your vendor is able to log on to the system. Caution: Log on to the portal:

User ID: Password:

##-ARAMI

initial

Change the password to training (or your own password)

174


2009

SRM210


You should find the following top level menus: - Home - Order Collaboration - RFX and Auctions

Note: You might find documents already in the order collaboration area from preceding exercises.

2009


175

Unit 5: Master Data

SRM210


176

•


•



2009

SRM210

Lesson: Product Master

Lesson: Product Master Lesson Overview The lesson introduces you to the process of product replication from the SAP back-end system and the technical principles of the SAP middleware.


Replicate products from an SAP back-end system

•

Explain the middleware basics

Business Example You want to replicate material master data from your SAP back-end system.

Product Master Data

Figure 75: Master Data in SRM Server and the SAP Back End

Material master data is transferred from the SAP back end to the SRM Server system using middleware. The relevant middleware object is MATERIAL. To replicate service master data, use the object SERVICE_MASTER. Product categories correspond to material groups in the SAP back end, while product subtypes correspond to the ERP material types.

2009


177

Unit 5: Master Data

SRM210

Caution: As a prerequisite for the download of master data, you also need some other objects, such as material groups, material types, or service types (for example,. DNL_CUST_PROD0, DNL_CUST_PROD1, or DNL_CUST_SRVMAS), which are to be replicated from your ERP system first.

For the entire list of SRM middleware objects and additional information about some table settings in SAP ERP, please check the configuration guide from Solution Manager. In a single initial download, the required materials are created in the SRM Server system as products. Subsequent changes (and also new materials) in the ERP back-end system are transferred by delta downloads. Hint: Please consider the storage format of your products to ensure that your SRM and ERP systems are in sync. For further information, please refer to the IMG documentation. Note: If you need to configure a standalone system without any ERP MM integration, you have to create product categories and product types manually in SRM Server (or upload from a file).

Figure 76: Back-End Adapter Objects

There is a particular sequence in which objects have to be exchanged between the various systems. A distinction is made for this purpose between the so-called independent objects and the dependent objects.

178


2009

SRM210


Independent objects can always be processed in parallel, thereby improving performance. A dependent object, however, cannot be forwarded until the associated independent object has been transferred to the other system. First replicate customizing objects, then business objects.

Figure 77: Data Structure - Example

SRM Server Products are identified by GUID. They can refer to an ERP material master (product type 01) or to an ERP service master (product type 02). Assignment to product category and product subtype takes place during the download from the ERP back- end.

2009


179

Unit 5: Master Data

SRM210

Figure 78: Data Flow in SRM Server

The (CRM) Middleware is a set of programs that exists partly in the SRM Server system and partly in the SAP back end. These programs initiate the download of product categories (material groups), product subtypes (material types), UOM, and product masters (material masters and service masters) from the back end. The initial download trigger agent calls the OLTP download trigger agent. This triggering is done via Background RFC (qRFC). This ensures that the download is executed exactly once. The OLTP download trigger agent calls the extractor proxies for the selected business object classes that in turn call the back-end extractors. The RFCs are queued and processed in a restrictive sequence (dependent vs. independent objects). In the SAP back end, a function module call (extractor module call) takes place to extract the requested data according to filter criteria handed over. Moreover, the data containers with the selected data to be sent to the Middleware Server are created. The data is transferred via RFC in the form of tables to the SRM Server.

180


2009

SRM210


In SRM Server, the data containers from the OLTP underlay the Mapping, which results in the creation of a Business Document (BDoc). The BDoc then initiates the update of the database. Note: There are two different download procedures:

Initial download: All data needed from the SAP back-end is downloaded initially. Delta download: Only delta information is downloaded from the OLTP system during normal operation, for example, changes to the product master in the SAP back end. Delta downloads for product data can be automatically triggered by the ERP system.

Figure 79: Delta Download

Different applications can subscribe for the delta event, too (for example, SRM, BI, or APO). This is done with an entry in the back-end table TBE31. Delta download is active for certain objects. Source code is implemented in the update task of the specific business object; queued RFC is then triggered automatically. Make sure that the event interface is set to Active in table TBE11 in your SAP back end. Although the event interface is delivered active, events could have been switched off manually for test purposes. If this is the case, activate the entries for application BC-MID and NDI.

2009


181

Unit 5: Master Data

SRM210

Figure 80: Communication: Middleware and ERP

Ensure that RFC destinations and logical systems are defined in both systems. The CRMRFCPAR parameter file is the main control table used on the back end. It contains control parameters for data exchange with the SRM system.

Figure 81: Administration Console

182


2009

SRM210


Sites are used to exactly specify the Sender and Receiver destinations. SRM needs the back-end destination (type R/3) with the RFC Destination maintained in the site attribute information. When an initial download is performed, business and customizing objects are copied in their entirety from the backend.

Figure 82: Manual Maintenance of Products

The product master contains all replicated and manually created products of your SRM system. Each product master record contains the data required to manage the product.

2009


183

Unit 5: Master Data

SRM210


184

•


•



2009

SRM210

Lesson: Product Master Exercise

Lesson: Product Master Exercise Lesson Overview


Configure and perform the material replication process from the SAP back end

Business Example You want to use the product master within SRM Server, as not all material master data is included in your electronic catalogs. In this exercise, you will replicate the material master from the SAP back end.

Exercise 1 View the products that have already been replicated from material masters in the SAP back end. Caution: Log on to your client of the SRM system from the SAP GUI:

Client : User ID:

3##

SRMCONFIG

Exercise Section 1-1 Add the transaction COMMPR01 (Product Workbench) to your Favorites in the SAP Easy Access menu.

Exercise Section 1-2 Use the transaction COMMPR01 to search for and view the existing products in the SRM Server system. Start the transaction Product Workbench (COMMPR01) from your Favorites.

2009


185

Unit 5: Master Data

SRM210

Go to

Choose

Enter Choose

FIND

tab page

Materials

as Find

*

as ID/Description

Start

What materials are listed?

Note: Those materials have been replicated already in the master landscape as a backup, case there is not enough time for the replication exercise.

Exercise 2 (Optional) Display the material master T-SRM1## in the SAP back end. Hint: If you are experienced with the materials master in ERP, you can skip Exercise 2. Caution: Log on to the back end.

Client :

800

User ID:

Password :

BACK-##

training

Display the plant stock view of the material master T-SRM1## for plant 3200. Choose SAP menu Logistics Materials Management Material Display Display Current . !

!

Enter

T-SRM1##

Material Master

!

as Material

Enter

Select

Plant Stock

Choose

Continue

Enter

!

!

Choose

186

!

3200


as View

as Plant

2009

SRM210


Choose

Continue

What is the description of the material?

How many units of unrestricted use stock are available?

Exercise 3 Before you start the replication process, please check if there are old entries in the inbound queue of your client. Delete all existing items. Caution: Log on to your client of the SRM system from the SAP GUI:

Client :

3##

User ID:

SRMCONFIG-##

Password :


Choose SAP menu Tools Middleware:Basis Monitoring Display Inbound RFC Queues or use transaction SMQ2. !

!

!

!

Queues

Enter

3##

as Client

Enter

*

as Queue Name

Choose

!

Execute

If there are any entries, then ... Choose

Select All

Choose

Delete Selected Objects

Choose

Back (twice)

Note: You delete these entries because old data from other trainings and system work does not fit into this actual scenario and, therefore, could block your planned downloads.

Exercise 4 View the current filter settings in the SRM Server system. Use the following information to change the current filter settings of MATERIAL filters.

2009


187

Unit 5: Master Data

SRM210

Choose SAP menu Tools Middleware:Basis Management Business Objects. !

!

!

Data Exchange

!

Object

!

Caution: Before you save and synchronize your filter, and before you start replicating (as explained in exercise 5-1), notify your instructor. Otherwise you could interfere with other groups.

Select

as Business Adapter Object

Material

Select

in Filter Settings column

Choose

Display

Go to Choose Set

!

Change

FILTER SETTINGS

tab page

R3_00_800

as Source Site Name

Inactive indicator

for the first three existing entries (you might have to scroll to the right to find that entries in the table view)

Add an entry with the following data: MARA

as Table/Structure

MATNR

as Field

BT (Between Low and High Value)

as OP

T-SRM00

as Low

T-SRM430

as High

Inclusive defined set/array

as Incl./Exl.

Hint: Ensure that you entered your filter settings correctly and with capital letters. Caution: Before you save and synchronize your filter, notify your instructor. Do not proceed until you are asked to, as you might interfere with other groups.

If you have to wait right now because other groups are currently replicating, you may proceed with exercise 6 at any time.

188


2009

SRM210


Choose

and confirm the message

Save

Choose


Filter Sync. (R/3)

Choose

Back (twice)

Exercise 5 Replicate the T-SRM* material master records from the SAP back end to the SRM Server system.

Exercise Section 5-1 Start the initial download of the materials according to your filter settings. Choose SAP menu Load Start .

!

Tools

!

Middleware:Basis

!

Data Exchange

!

Initial

!

Choose

Material

Choose

Enter

as Load Object

What sites (Sender) are shown for the data flow and why?

Enter

as Destination Site (Receiver) if necessary

CRM

Choose


Execute

Choose

Back

Caution: Inform your instructor as soon as you have started the replication process. Also contact your instructor if you receive an error message.

Exercise Section 5-2 Verify that the material master records were successfully transferred by viewing the Download Objects Monitor with transaction R3AM1 or by choosing SAP menu Tools Middleware:Basis Data Exchange Initial Load Monitor Objects. !

2009

!

!


!

!

189

Unit 5: Master Data

SRM210

Choose

Select

Material

as Object Name

Execute

What is the status of the material? Choose

Back (twice)

Exercise Section 5-3 View the newly replicated products. Start transaction

COMMPR01

from your Favorites

Go to

FIND

tab page

Choose

Start

Did you find the materials ?

Caution: If your download failed, contact the instructor.

You might also review your filter settings and inbound queue, but never change anything or restart the download without your instructor's knowledge.

Exercise Section 5-4 Replicate product valuation prices from the SAP back end. Start transaction SA38. Hint: This exercise only makes sense if you already have replicated your products. As the product price replication does not utilize the middleware, you do not have to perform this exclusively.

Enter

Select

190

EBP_GET_ BACKEND_PRICES

as program

Execute

Enter

T-SRM00

as (from)Product ID

Enter

T-SRM430

as (to) Product ID

Select

T90CLNT090

as Specify logical system


2009

SRM210


Enter

USD

as Target Currency

Select

Average value of all prices radio button

for Price. Ref. per Prod.

Choose

Execute

Choose

xit

Exercise 6 Maintain a local material with product price in transaction COMMPR01. Choose

Material

Choose

Drinks (MAT_FGTR)

Select

Continue

Enter

MAT##

as Material

Champagne Albert Le Brun

as Description

Enter Go to

GENERAL

tab page

Enter

LOCAL2

as Category ID

Enter

R3MATCLASS

as Hierarchy ID

German

as the second entry for the Language in the area Descriptions

Champagne Albert Le Brun

as the German Product Description

MATERIAL

tab page

Enter

PAL

as Base Unit of Measure

(Optional) Enter

This Champagne, which is composed of 1/3 Chardonnay and 2/3 Pinot grapes from the best villages…...

as Basic text

Go to

PURCHASING

tab page

PAL

as Order Unit

Choose

Enter Go to

Maintain Go to

CONDITIONS

tab page

Select

Purchasing

in Conditions for

01PV

as CCtC (Condition Type)

Select with F4

2009

as Category


191

Unit 5: Master Data

SRM210

Select

SAP118 Product

Enter

65

as Amount

Enter

USD

as Curr

Enter

1

as Per

Enter

PAL

as Unit

Choose

Save

Choose

Exit

Exercise 7 Create a shopping cart in SRM Server with your local product. Caution: Log on to the portal:

User ID: Password:

##-EMPLOYEE

training (or your own)

Select

Shop

Order

MAT##

from the Employee Self-Services

Check the status of your shopping cart Question: What kind of follow-on document did you get and why ?

_______________________________________________________________

Exercise 8 (Optional) Material Master: Your company has a multi-back-end environment where different material masters have the same material master number in each ERP system. How can you use the product information in SRM Server? How can the SRM Server system differentiate the product masters? _______________________________________________________________ _______________________________________________________________ _______________________________________________________________

192


2009

SRM210


_______________________________________________________________ _______________________________________________________________ _______________________________________________________________

2009


193

Unit 5: Master Data

SRM210

Solutions Exercise 8 Material Master: Your company has a multi-back-end environment where different material masters have the same material master number in each ERP system. How can you use the product information in SRM Server? How can the SRM Server system differentiate the product masters? Use the CRM Middleware to replicate the products from each ERP system. The SRM Server system differentiates different products by means of Global Unique Identifiers (GUID). Furthermore, the source system information is included in each product master record ( Goto source system) and in the COMM_PRODUCT table. !

194


2009

SRM210



2009



195

Unit Summary

SRM210


196

•

Explain how to replicate vendors from a SAP back-end system

•

Describe the business partner concept for vendors and vendor users

•


•


•


•


•



2009

Unit 6 Connection to Catalogs Unit Overview This unit introduces the principles of electronic product catalogs and business partner directories. You will also get a first impression of the SRM-MDM Catalog.


Classify electronic product catalogs and business partner directories

•

Connect electronic catalogs to SAP SRM

•

Explain the SAP catalog strategy and the underlying products

•

Connect catalogs to the SRM Server system

Unit Contents Lesson: Connection to Catalogs. .. .. ... .. .. ... .. ... ... .. ... .. ... .. ... .. ... ...198 Lesson: Connecting the SRM-MDM Catalog Exercise .. .. .. .. .. .. .. .. .. .. 215

2009


197

Unit 6: Connection to Catalogs

SRM210

Lesson: Connection to Catalogs Lesson Overview This lessons introduces the principles of electronic product catalogs and business partner directories, as well as in the principles of Catalog Content Management using the SAP SRM-MDM catalog.



•


•


Business Example You want to evaluate the advantage of electronic catalogs and become familiar with the SAP SRM-MDM Catalog.

Connection to Catalogs The full functionality of a supplier’s catalog may include:

198

•

Pictures of offered goods/services

•

Prices relevant to the customer

•

Current availability of goods

•

Supplier shopping baskets


2009

SRM210

Lesson: Connection to Catalogs

Figure 83: Definition and Value of Catalogs

Suppliers may maintain the catalog to ensure up-to-date prices and availability. Negotiated prices are shown so that you can reduce costs. Product displays and correct supplier data ensures “clean” orders are passed to the supplier. Users may be directed to a particular section of a catalog (for example, a search screen) for particular types of goods or services. It is also possible to allow specific employees customized views on particular catalogs (for example, access restricted to office materials product category).

Figure 84: SRM Server Catalog Scenarios

2009


199


SRM210

One of the main advantages of using Web-based procurement software is the integration with online catalogs, enabling easy location of products. SRM Server supports the following catalog scenarios: •

You access the vendor catalog directly from SRM Server via the Internet. The vendor is responsible for setting up the catalog and maintaining the contents.

•

Using the Internet, the purchaser accesses a catalog that combines the offerings of several suppliers. The catalog broker is responsible for setting up the catalog and maintaining the contents. Catalogs (for example, industry-specific catalogs) can be located on marketplaces.

•

The catalog is within the firewall. The company-specific catalog combines the offerings of several vendors. Often, the company itself has to maintain the catalog on the basis of delivered supplier data files.

•

Internal order processing is dealt with using SRM Server. The catalog is based on internal master data, for example, the SAP Product Catalog.

Figure 85: SAP Catalog Strategy

The figure above explains the SAP catalog strategy, from SAP Catalog Content Management to the SAP SRM-MDM catalog and the corresponding product versions. Since the availability of SRM-MDM Catalog 2.0 in autumn 2007, the preferred catalog solution is the SRM-MDM Catalog. SRM-MDM Catalog 3.0 is delivered with SAP SRM 7.0

200


2009

SRM210


SAP Catalog Content Management As of SAP SRM 4.0, SAP delivers its own solution for electronic catalogs and the management of such catalogs: SAP Catalog Content Management. SAP Catalog Content Management is an ABAP / BSP application that can be installed on Web AS 6.40 or higher (Web AS 7.0 is preferred).

Figure 86: Components of SAP Catalog Content Management

The SAP Catalog Content Management (SAP CCM) consists of two main components: While the catalog authoring tool (CAT) enables content managers to manage and edit the catalogs, the catalog search engine (CSE) enables users to search for commodities and transfer them to their shopping carts. Both components are accessed via URL. Note: The preferred solution by SAP is the SRM-MDM Catalog. This product will be developed further. Support for the SAP CCM catalog ends in 2013. Hint: For support of SAP CCM with SRM 7.0, please check SAP Note 1311274 - SAP CCM 2.0 with SRM 7.0.

2009


201


SRM210

SAP SRM-MDM Catalog The SRM-MDM Catalog consists of several separate components. The catalog search application and its look-and-feel configuration (restricted to administrator only) is accessed by a URL. The components for data upload (Import Manager) and data maintenance (Data Manager) require local installation. For server and repository administration, you can use the MDM Console, which is not included in the figures above.

Figure 87: SAP SRM MDM Catalog

202


2009

SRM210


Figure 88: Deployment of SAP SRM-MDM Catalog

The SRM MDM catalog based on SAP NetWeaver MDM 7.1 consists of:

2009

•

MDM Database Server

•

MDM Server and optional MDM Import Server

•

Web Application Server: Enables catalog access via OCI

•

MDM Clients: Local components for content managers only


203


SRM210

Figure 89: SRM MDM System Landscape

The technical view of the SRM-MDM landscape shows the components, as well as the technical interfaces between them. The exchange infrastructure is only mandatory for integration scenarios, such as SRM contract upload or transaction MECCM in SAP ERP.

204


2009

SRM210


Figure 90: Import Manager and Data Manger

Content managers need additional software on their desktop. The MDM Console enables them to administer MDM Server and MDM Repositories. The Import Manager facilitates the upload and mapping of text, Microsoft Excel, or XML data files. The Data Manger allows editing and creation of catalog items and other information.

2009


205


SRM210

Figure 91: Web Dynpro Search User Interface

End users connect to the MDM Server and its catalog content via Web interface only, for example, using the call structure out of SRM Server.

Connecting Catalogs to SRM Server The Open Catalog Interface (OCI) describes the data exchange between the SRM Server system and external catalog applications. OCI enables the transmission of selected goods and services from an external catalog to the SRM Server. The external catalog is located either within the local intranet or somewhere on the Internet.

206


2009

SRM210


Figure 92: SAP Open Catalog Interface

Any catalogs that are used must conform to the OCI specification. This means that instead of goods being ordered directly from the catalog, a button is added to send the shopping cart data back to SRM Server. This triggers a Web request back to SRM Server in the format specified in the OCI. The catalog interface consists of two separate and distinct sections: the inbound section and the outbound section. While the inbound section in SAP SRM Server is pre-delivered, the outbound section of your catalog needs to be configured. The catalog outbound section settings could vary from the catalog software you are using. SAP CCM and SAP SRM-MDM deliver typical OCI fields with their standard installation. For mappings on the inbound section, there is a BAdI available within SRM Server.

2009


207


SRM210

Figure 93: Open Catalog Interface (OCI 4.0) – Inbound Parameters

The inbound section consists of the information that is sent from the catalog application to Procurement. This section contains data on the items selected in the catalog, such as the item descriptions, quantities ordered, and prices. The figure above shows the actual OCI fields in OCI 4.0

Figure 94: Open Partner Interface (OPI 1.0)

208


2009

SRM210


Open Partner Interface (OPI) enables purchasers to search in an external catalog for potential new supplier. This gives you the opportunity to create new business partners on the basis of the external supplier data. The creation of new business partners can be combined with an approval workflow. OPI supports the SAP CCM (Supplier Directory), as well as other supplier catalogs. It is integrated in several procurement processes and transactions, for example, sourcing and biding.

Figure 95: Defining a Product Catalog in SRM Server

Catalog definition: •

Maintain Catalog ID and Catalog name: Note: The name of your catalog is language-dependent.

2009

•

Assign a business partner ID if all items belong to the same vendor. In the case of multi-vendor catalogs, the vendor identification has to be available in the catalog item.

•

The purchasing organization is for information purposes only


209


SRM210

Additional functions and technical settings: •

Do Not Check Products: Products are transferred from the catalog into the shopping cart without checking them in SRM Server. You do not have to replicate these products in the SRM Server!

•

Use Error Log: If this indicator is activated, error messages that occurred during catalog data transfer can be evaluated from the application log.

•

Add Contract Data: You should set this indicator if you wish to supplement the data displayed in the integrated catalog with SRM contract data (not supported with SAP CCM or MDM catalog).

•

Updated Display of Product Data Possible: When this flag is set, you can create an updated display of product detail data and a picture of the catalog in SRM Server. A prerequisite is the mapping of the Global ID and the NEW_ITEM_EXT_PRODUCT_ID field in the OCI.

•

Updated Validation Possible: This Customizing setting checks whether data of items ordered using a stored template is still valid. A prerequisite is the mapping of the Global ID in the OCI.

•

User Error Log: This helps you to analyze inbound transmission problems in the OCI interface, for example, if the catalog delivers an UOM that is unknown by SRM Server. Check transaction SLG1 for detailed information.

Figure 96: SRM-MDM Catalog Call Structure

210


2009

SRM210


You must define the call structure for every single catalog definition. The call structure consists primarily of the catalog’s URL, the user name, and the password required to log on to the catalog. As different catalog users have a different views of the catalog’s content, each catalog definition in SRM Server gives access to only those products restricted to such a view. Thus, several catalog definitions within SRM Server can point to the same physical catalog URL, but depending on the catalog user’s view, only a limited number of constrained products can actually be purchased by the individual user. Note: With SRM-MDM Catalog 3.0, the parameter sap-locale replaces uilanguage.

Note the following when setting up a catalog call structure: •

Many of the field names and values depend on the particular catalog product.

•

The example shows the call structure connecting SRM Server to the SAP SRM-MDM Catalog.

•

Structure the fields in the order shown in the installation guide.

Once the catalog has been assigned to organizational units (attribute CAT), the Customizing in SRM Server is finished.

2009


211


SRM210

Figure 97: Implicit Search Criteria with SRM 7.0 and SRM-MDM Catalog 3.0

Note: Activation of implicit search criteria takes place via the normal OCI Web service definition. In releases lower than SRM 7.0, these criteria can be determined and defined in a catalog call BAdI. Note: In case of plant ID transfer, the SRM-MDM standard repository needs to be enhanced by a new main table flat lookup field with field ID and display field MDMSRM_PLANT_ID.

212


2009

SRM210


Figure 98: Content Providers and Content Management

Before you decide to outsource the catalog to vendors or external providers, or maintain the catalog yourself, consider the following aspects. Content issues: •

Not all suppliers are able to provide electronic catalog data.

•

Supplier catalog data (material number, product categories, UOM) might not fit to your data.

•

Lack of classification standards (Product Categories, UOM)

•

Too many standards means no standard (eClass, UNSPSC, ...).

•

Lack of data format standards (XML, XLS, BME Cat,...)

Catalog issues for content management include:

2009

•

Customers would rather have suppliers maintain catalogs.

•

Customers want to track sensitive data with catalogs, but do not always want suppliers to see this information.

•

While supplier catalogs are attractive, every supplier catalog has its own look and feel, and this creates a chaotic environment for procurement by occasional users.


213


SRM210



•


•


Related Information If you need more information about SAP-SRM Catalog, please refer to SRM270 (SAP SRM-MDM Catalog) training.

214


2009

SRM210

Lesson: Connecting the SRM-MDM Catalog Exercise

Lesson: Connecting the SRM-MDM Catalog Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •


Business Example You want to evaluate the advantage of electronic catalogs in general and learn more about the SAP SRM-MDM Catalog. Therefore, you want to connect a test catalog to your SRM Server system.

Exercise 1 Connect a pre-delivered SRM-MDM Catalog to your SRM Server client. Caution: Log on to your client of the SRM system from the SAP GUI:

Client: User ID:

3##

SRMCONFIG-##

Start transaction SPRO, then choose SAP Implementation Guide Supplier Relationship Management SRM Server Master Data Content Management Define External Web Services. !

!

!

!

!

Define the call structure for the SAP SRM MDM catalog. Choose Enter

New Entries SRMMDMTRAIN

as Web Service ID

Enter

SRM-MDM Catalog Training

as Description

Choose

Product Catalog

as Bus. Type of a Web Service

Choose

2009

Enter

Set the indicator

Do not Check Product

Set the indicator

Display Product Data Again in Catalog


215


SRM210

Set the indicator

Validate Product Data from SAP Enterprise Buyer

Set the indicator

Use Error Log

Choose

CATALOG

Select

as Logical System

Enter

Double-click on

Standard Call Structure

Choose

New Entries

in the Dialog Structure (left side)

Maintain the following call structure data: Seq. Parameter Name

Parameter Value

Type

10

http://j2ee- .wdf.sap.corp:50000/SRMMDM/SRM_MDM

URL

20

username

User1

Fixed Value

30

password

training

Fixed Value

40

server

training-mdm-bs.wdf.sap.corp

Fixed Value

50

catalog

SRM_MDM_Catalog_SRM

Fixed Value

60

sap-locale

SY-LANGU

SAP Field

70

datalanguage

EN

Fixed Value

80

bypass_ outb_handler

X

Fixed Value

90

HOOK_URL

Return URL

100 returntarget

_top

Fixed Value

110 ~caller

CTLG

Fixed Value

120 ~OKCode

ADDI

Fixed Value

Caution: “your_SRM_system_id” refers to the SRM system allocated by your class. Detailed data will be supplied by your instructor. Optional entries, not needed for the SRM-MDM Catalog:

216


2009

SRM210


130 system_alias

SRM_##

Fixed Value

140 usePortalNavigation

X

Fixed Value

Note: The entries “system_alias” and “usePortalNavigation”

are not mandatory for the connection to the SRM-MDM Catalog, but might be helpful if you have to connect to other external catalogs. Choose

Save

Select

Back

(two times)

Exercise 2 Assign your catalog to Phoenix organizational structure. Start transaction CHANGE ATTRIBUTES (PPOMA_BBP). Double-click on

Phoenix Enterprise Inc. (Root Organization)

from Organizational structure

Go to

ATTRIBUTES

tab page

Select

Chg. Attribute

Choose

Catalog ID

Choose

SRMMDMTRAIN

Select

Save

as Catalog ID

and

Back

Exercise 3 Test the catalog connection.

Exercise Section 3-1 Create a shopping cart and search for items in the Catalog. Caution: Log on to the Portal:

User ID: Password:

2009

##-EMPLOYEE

training


217


SRM210

Chose Chose

Employee Self-Service

in the top level navigation

Shop

in the launch pad

Choose

SRM-MDM Catalog Training

Search for

Overhead Projector

Choose and add to shopping cart

Overhead Projector

Select

Check Out

Choose

from your vendor EBP -##

Next and Order

Hint: If you expect to see follow-on documents as well, do not forget to check if your shopping cart needs approval. If yes, feel free to perform the approval.

Exercise Section 3-2 (Optional) Evaluate the features of the SRM-MDM catalog. Check out some features and functions of the catalog you just maintained. For example, you could try hierarchical searches, advanced searches, item comparison, or shopping lists.

218


2009

SRM210



2009



219

Unit Summary

SRM210


220

•


•


•


•



2009

Unit 7 Self-Service Procurement Unit Overview This unit covers the process of using of shopping carts for direct and indirect materials, as well as goods receipt and invoice entry.


Explain the shopping cart process and the possible follow-on documents

•

Create shopping carts and evaluate the follow on documents in the SAP back end

•

Illustrate the direct material process and make the necessary system settings

•

Perform the necessary configuration steps to enable direct procurement with SRM

•

Create a shopping cart containing direct material

•

Demonstrate the confirmation of goods receipt and explain the possible process and document flow scenarios

•

Confirm goods receipts in SRM Server and the ERP system

•

Analyze the ALE communication between SRM Server and the ERP back-end system

•

Explain the possible invoice verification processes and related document flow

•

Enter invoices in SAP SRM Server or the ERP back-end system

•

Evaluate the follow-on documents

Unit Contents Lesson: Shopping Carts .. ... .... .... .... .... .... .... ... .... ... .... ... .... ... ..222 Lesson: Shopping Carts Exercise .. ... ... .. ... .. ... ... .. ... .. ... .. ... .. ... ...228 Lesson: Direct Procurement...................................................234 Lesson: Direct Procurement Exercise........................................238 Lesson: Confirmation of Goods Receipt.....................................244 Lesson: Confirmation of Goods Receipt Exercise..........................248 Lesson: Invoice .................................................................254 Lesson: Invoice Exercise ... .... .... .... ... .... ... .... .... .... ... .... ... .... ...261

2009


221

Unit 7: Self-Service Procurement

SRM210

Lesson: Shopping Carts Lesson Overview This lessons focuses on the shopping cart process for direct and indirect procurement with SAP SRM Server and the follow-on documents depending on the integration scenarios.



Business Example You want to evaluate the shopping cart wizard and the simplified form of the shopping cart.

Shopping Cart Processes

Figure 99: Shopping Cart - Process Flow

222


2009

SRM210

Lesson: Shopping Carts

Figure 100: Classic Scenario

Figure 101: Local Scenario

2009


223


SRM210

Figure 102: Shopping Cart - Data Sources

There are four ways to add an item to a shopping cart: • Catalog: The catalog supplies product ID, product text, product category, price, vendor, and other data. • Product: The product represents either a material or a service master. It can be searched via short description, product ID, product type, or product category.

224

•

Describe what you need: The user describes via text entry what he or she needs; the user fills in a description, unit of measurement, quantity, and product category.

•

Old Shopping Carts and Templates: Refer to existing documents.


2009

SRM210


Figure 103: Shopping Cart - Wizard

The Wizard is the default navigation interface for employees. It helps employees to find, select, and add goods and services to their shopping carts quickly and easily. The user is guided by the transaction through the following four steps:

2009

•

Create an item from catalog, product master, old shopping carts, or templates, or via free text.

•

Display the shopping cart overview, from where the employee can select the item details.

•

Order or save the shopping cart and preview the approval procedure.

•

Completion and overview of the shopping cart.


225


SRM210

Figure 104: Shopping Cart - One Screen

The one-screen (professional) shopping cart is dedicated to semi-professional or professional users like secretaries, purchasing assistants, or purchasers who create shopping carts on a regular basis. All information in this transaction is available on one screen. This includes detailed information like source of supply, cost assignment, and other data.

226


2009

SRM210



2009



227


SRM210

Lesson: Shopping Carts Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •


Business Example To test your system configuration, you need to create shopping carts with catalog items, product masters, and free text items. In the second step, you want to check that the follow-on documents exist as expected.

Exercise 1 Create a shopping cart that does require a one-step approval. The shopping cart will have four line items. Line item one will be selected from the catalog and will create a back-end purchase order. Line item two will be selected from the catalog and will create a local purchase order in SRM Server. Line item three will be entered manually and will create a back-end purchase requisition. Line item four will be a product that was replicated earlier and will create a reservation in the back-end. Caution: Log on to the Portal as an Employee:

User ID: Password:

228

##-EMPLOYEE training (or your own password)


2009

SRM210

Lesson: Shopping Carts Exercise

Exercise Section 1-1 Create a shopping cart via Employee Self-Services: 1.

Choose the SRM-MDM Catalog and select Supplier “Aramingo##” from the supplier lookup table. Select 10 Alkaline Batteries and 10 Water. Transfer the items to the SRM shopping cart.

2.

Add a third item as free text: 1 PC, “X-Phone,” ,Product Category 002, 299 USD .

3.

The fourth item is from product master 1 PC T-SRM-## (do not order the cart yet). Note: You should now have four items in your shopping cart (Alkaline Batteries, Water, X-Phone, and Casing).

Exercise Section 1-2 Split the account assignment of the X-Phone between two cost centers: 75% of the line item will be charged to cost center 1000, and 25% of the item will be charged to cost center 4140. Create an internal note for the X-Phone.

Exercise Section 1-3 Check the approval preview, rename your shopping cart to SSP-##, and Order the cart.

Exercise Section 1-4 If approval is needed, perform the necessary approval steps. Afterward, log on as ##-EMPLOYEE again.

Exercise Section 1-5 Check the status of your shopping cart (see Related Documents tab) and write down the results for each item:

Alkaline Batteries: ________________________________________

Water: ________________________________________

X-Phone:________________________________________

2009


229


SRM210

Casing :________________________________________

Exercise 2 View the documents created. Caution: Log on to the back-end system:

Client:

800

User ID:

Password:

BACK-##

training

Exercise Section 2-1 Find the purchase order that was created for the Alkaline Batteries. Choose SAP menu Logistics Purchase Order Display. !

!

Materials Management

!

Purchasing

!

!

Choose

Other Purchase. Order

Enter

Select

Other document

Who is the Vendor?

Go to the Item Details. Select

ACCOUNT ASSIGNMENT

tab page

Was the accounting information transferred successfully?

Select

TEXTS

tab page

Was the vendor text from the catalog transferred successfully?

Choose

230

Back


2009

SRM210


Exercise Section 2-2 Find the purchase requisition that was created for the X-Phone. Choose SAP menu Logistics Materials Management Purchase Requisition Display. !

!

!

Purchasing

!

!

Select

Other Purchase Requisition

Enter

Choose

Other document

as Purchase Requisition

Who is the tecipient?

Can you see the multiple account assignment?

Choose

Back

Exercise Section 2-3 Find the teservation that was created for the Casing. Choose SAP menu Logistics Materials Management Management Reservation Display. !

!

!

Enter

!

Inventory

!

Select

Enter

What is the movement type used for this material?

Who is the goods recipient?

Exercise 3 Create a shopping cart for only local items. Caution: Log on to the portal as an Employee.

2009


231


User ID: Password:

SRM210

##-EMPLOYEE training (or your own)

Create a shopping cart with a free-text item and a local product. 1.

First item - Free text item:

5000 PC “ball pen with phoenix logo”; 0.69 USD each, LOCAL1 as product category; delivery date in 4 weeks Second item - with product reference :

1 Pallet Champagne, MAT##

Re-name the requistion to “Local SC” and Order . 2.

Perform approval if required.

3.

Check the related documents of your shopping cart items..

Ball pens: ________________________________________

Champagne: ________________________________________

232


2009

SRM210



2009



233


SRM210

Lesson: Direct Procurement Lesson Overview This lesson focuses on the shopping cart process for direct materials.



Business Example You want to test the procurement of stock for materials.

Direct Procurement When talking about electronic purchasing, it is important to define the difference between direct materials and indirect materials, as the process and nature of integration of the procurement software is quite different.

Figure 105: Direct Materials vs. Indirect Materials

Direct materials are used directly in the production process and thus have influence on the value of the final good. This material is mostly held in stock and needs to be kept in inventory management.

234


2009

SRM210

Lesson: Direct Procurement

Indirect material, also known as MRO material, could be office supplies or machine parts, for example. In most cases, indirect material is characterized by high-volume and low-dollar transactions.

Figure 106: Self-Service Procurement of Direct Material

Ordering a direct material means ordering a product that will be received into stock. You have to choose Order as Direct Material in the item detail view. Order as Direct Material replaces the goods recipient with the plant you are ordering for and removes the Account Assignment information. The plants and storage locations are defined in the organizational structure in the extended attributes Locations and Storage Locations. After ordering the material as a direct material, you cannot change back to indirect; if you make a mistake, you have to delete this item.

If you have a valid and definite source of supply, such as a contract, this source will be used. Items without a source of supply are to be completed by the purchaser in the sourcing transaction or in the worklist of incomplete purchase orders. The complete purchase order will then be replicated to the ERP back-end system. Changes to the purchase order are only possible in SRM, which is the leading system for this process. Those changes will be transferred to the ERP back-end then. Note: Although you can create shopping carts for back-end materials, SRM Server is the leading system for direct procurement. This means the system behaves according the extended classic scenario.

2009


235


SRM210

Figure 107: Prerequisites for Direct Material

To use the direct material scenario, you have to refer to products that exist in the back-end system. Therefore, you need to replicate units, product categories, material types, and the interesting products from the ERP back-end(s). In the next step, you have to ensure that your plant appears as a business partner in SRM Server. The easiest way to ensure that is to replicate the plant data via report BBP_LOCATIONS_GET_FROM_SYSTEM from the ERP system. You usually do this already for indirect procurement processes. To ensure that the documents can be transmitted to the backend, you have to maintain corresponding transaction types, document types, and number ranges for purchase orders in SRM Server and in the ERP back-end system.

236


2009

SRM210

Lesson: Direct Procurement


2009



237


SRM210

Lesson: Direct Procurement Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •


•


Business Example SRM Server supports the end-to-end procurement of direct materials. You need to make the necessary settings for the manually triggered direct procurement process and test your settings by creating a shopping cart.

Exercise 1 Configuration of the Direct Procurement process: Caution: Log on to your client of the SRM system.

Client:

3##

User ID:

SRMCONFIG-##

Password:


Exercise Section 1-1 For the Direct Procurement process, define a new transaction type DP##. In the IMG, choose Cross-Application Basic Settings

Define Transaction Types.

Select

BUS2201 Purchase Order

Double- click on

Transaction Types

in the Dialog Structure (left site)

Mark the

ECDP

row

Select Enter ,m

238

!

Copy As ...

DP##

as Transaction Type

04

as Int. Number Range


2009

SRM210

Lesson: Direct Procurement Exercise

Select

Copy (Enter)

Confirm the warning message.

Do not forget to maintain Choose

a valid text schema

Save (twice)

and Back

Note: You only copy the existing transaction type ECDP to individual ones to distinguish between the several SRM clients. Normally, you do not need to do this.

Exercise Section 1-2 Maintain the number range 04 for transaction type DP##. Choose Cross-Application Basic Settings Number Ranges SRM Server Number Ranges Define Number Range for Local Purchase Orders. !

!

!

Select

Intervals

Select

Interval

Enter

04

as the No.

Enter

403##00000

as the From number

Enter

403##99999

as the To number



Exercise Section 1-3 (Optional) Check the corresponding document types and number ranges in the back end. Caution: Log on to the ERP system:

2009


239


SRM210


800

BACK-##

training

Add SPRO to your favorites list and start the transaction. Go to the SAP Reference IMG. Materials Management Choose SAP Customizing Implementation Purchasing Purchase Order Define Document Types. !

!

Find your document type

!

!

in the list.

DP##

Which is the external number assignment? ____________________ Choose

Back

Choose Materials Management Number Ranges.

!

Select

Intervals

Find the number

##

Purchasing

Check your number 403##00000 to range 403##99999 Choose

!

Purchase Order

!

Define

of your external number range in the list. in the list.

Back

Exercise Section 1-4 Define transaction type DP## as value for the attribute DP_PROC_TY in your organizational structure. Caution: Log on to your client of the SRM system:

240


2009

SRM210


Client:

3##

User ID:

Password:


1.

Start the transaction CHANGE ATTRIBUTES (PPOMA_BBP).

2.

Double-click root organization Phoenix Enterprises Inc.

3.

Select attribute Transaction Type: Create PO Manually

4.

Maintain DP## as a Trans. Type.

5.

Choose Save and Back .

Exercise Section 1-5 As direct purchase orders are technically local purchase orders, add the responsibility for product category 001 to your local purchasing group Start transaction Select Go to

Select Select

PPOMA_BBP

PGRP Local (Miller)

organizational unit

RESPONSIBILITY

tab page

001 (T90CLNT090)

as Product Category

Save

and

Back

Exercise 2 Create a shopping cart for a direct material. Caution: Log on to the Portal:

2009


241


User ID:

SRM210

##-EMPLOYEE

1.

Create a shopping cart item using product T-SRM##.

2.

In the Item Details, select Order as Direct Material .

3.

Rename the shopping cart to “Direct Shopping Cart” and Order

4.

Check the item status.

What did you get ? ____________________________________________

5.

Can you find that document in the ERP back-end system ?

Why or why not? ____________________________________________

242


2009

SRM210



2009

•


•



243


SRM210

Lesson: Confirmation of Goods Receipt Lesson Overview In this lesson, you will learn about the process of confirmation of goods and services.



Business Example You want to evaluate the document flow and user opportunities during the confirmation of goods receipt.

Confirmation of Goods Receipt Both goods receipt and service entry are handled by one confirmation scenario.

Figure 108: Create and Process Confirmation

244


2009

SRM210

Lesson: Confirmation of Goods Receipt

The workload for the confirmation is determined by the user's role. Employees only can confirm goods or services if they ordered those goods themselves, or if they are the recipient of the goods or services. Vendors only can confirm purchase orders addressed to themselves, whereas central roles, like the central recipients or purchasers, can perform confirmations for all purchase orders. Classic scenario: Automatically creates goods receipt in the ERP back end by passing an IDoc. Goods receipt can either be entered in the ERP system or in SRM Server. Local scenario: Purchase order and confirmation are entered and stored in SRM Server. There is no information passed to the ERP systeml. Delete/Cancel Confirmations: Confirmations can be physically deleted if the document status is Saved or Awaiting Approval . If the goods receipt is already posted in the ERP system, the confirmation needs to be canceled (only possible if an invoice has not yet been posted). Return delivery: For back-end processes, a separate material movement document with movement type 122 will be posted; for local processes, a local return document will be posted. For a return delivery, you also should maintain texts for reason of return in the IMG.

Figure 109: Confirmation - Possible Scenarios

Confirmations that refer to classic (or extended classic) purchase orders: Transfer of the goods receipt by iDoc, so ALE distribution has to be configured. Apart from that, service entry sheets are transferred via RFC to the ERP system.

2009


245


SRM210

Confirmations that refer to local purchase orders: No information is passed to the ERP back end.

246


2009

SRM210

Lesson: Confirmation of Goods Receipt


2009



247


SRM210

Lesson: Confirmation of Goods Receipt Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •


•


Business Example You want to test how the confirmation of goods receipt will fit your procurement requirements.

Exercise 1 Perform a confirmation for the purchase order associated with the Alkaline Batteries from shopping cart SSP-##. Caution: Log on to the portal:

User ID: Password:

248

##-EMPLOYEE

training


2009

SRM210

Lesson: Confirmation of Goods Receipt Exercise

Create a confirmation for the Alkaline Batteries as follows: 1.

From the Shopping Carts tab in your Shopping Area , select the Alkaline Batteries item and choose Create Confirmation. Alternatively, choose Create Confirmation, but do not select an item beforehand. Search for your purchase order. Select the purchase order you want to confirm and choose Start .

Alternatively, Open the shopping cart. In display mode, you can directly post the confirmation (express confirmation) after you have selected the item.

2.

Choose Copy Outstanding Quantities or enter a quantity manually. Enter Batteries-##/01 as Confirmation Name.

3.

Choose Confirm and Close.

Exercise 2 Check the PO history of your purchase order in the ERP system and find the iDoc for the SRM confirmation. Caution: Log on to the ERP back-end system:

Client:

800

User ID:

Password:

Back-##

training

Exercise 2-1 Check the ERP back-end purchase order history. Find the purchase order that was created for the Overhead Projector to view the accounting details. Choose SAP Menu Logistics Materials Management Purchase Order Display or use transaction ME23N. !

!

!

Purchasing

!

!

2009


249


SRM210

Choose

Other Purchase order

if necessary

Enter

as Purch. order

Select

Other document

Choose

Purchase order history

tab page in the item details

Ensure that there is a material document like

<50000****>

in the history

Leave the transaction

Exercise 2-2 Check the iDoc in SAP ERP as result of the SRM confirmation. 1.

Start transaction WE05 in your ERP system

2. Execute the iDoc list using the default entries. 3.

Search or filter for “LS/ SRM_00_3##” in the Partner column.

4.

Double-chock the iDoc with Basic Type MBGMCR01.

5.

Browse the entries in the Data Records area. Hint: If there are too many results, restrict date and time selection before you execute transaction WE05.

Exercise 3 The water arrived at the office of Edward Employee. Perform a confirmation for the local purchase order. Note: You should be still logged on to the portal as ##-EMPLOYEE.

Exercise 3-1 Create a confirmation for the water. Refer to Exercise 1 for a step-by-step description.

Write down the approximate time when you created that confirmation: ________

250


2009

SRM210


Exercise 3-2 Check your iDocs in SRM Server 1.

Log on to your SRM client from SAP GUI as SRMCONFIG-## (if necessary).

2.

Call transaction WE05 in your SRM client.

3.

Identify the iDocs for iDoc type MBGMCR*.

4.

Can you find an iDoc that fits the time when you created the confirmation for the water? Why or why not ? ____________________________________________

2009


251


SRM210

Exercise 4 (Optional) Check out partial deliveries performed by different parties:

252

1.

Create a shopping cart for the Alkaline Batteries-## and (optional) additional items like Targus Wireless Optical Notebook Mouse-## , with quantities of 10 or more each.

2.

Confirm partial delivery as ##-Employee in SRM.

3.

Confirm partial delivery as ##-ARAMI Suplier in SRM.

4.

Create additional SRM User ##-RECIPIENT . a)

Create User ##-RECIPIENT in your SRM client with role /SAPSRM/RECIPIENT and /SAPSRM/EMPLOYEE and organizational unit Phoenix One, Production.

b)

Log on to the portal as SRMADMIN-## and create the portal user ##-RECIPIENT with the matching portal role (search for role *recip*##*).

5.

Log on as ##-RECIPIENT to the portal and check out the Central Confirmation and Notify Recipient functions.

6.

Log on to the ERP back-end as ERP-## and enter a partial delivery via transaction MIGO.

7.

Logon to the portal as ##-EMPLOYEE and check the Confirmation tab within your Shopping area. Review the confirmations and post a Return Delivery or Cancel a confirmation.

8.

Review the purchase order history in the ERP system using transaction ME23N.

9.

Analyze the iDocs in SRM or ERP using transaction WE05..


2009

SRM210



2009

•


•



253


SRM210

Lesson: Invoice Lesson Overview This lesson introduces the process of invoice verification within SAP SRM.



Business Example You want to examine the possibilities of invoice verification within SRM Server and its integration into SAP ERP.

Invoices Invoices, credit memos, and subsequent credits/debits can be entered for the following scenarios:

254

•

Invoices are entered locally in the SRM Server without reference to a purchase order or delivery.

•

Classic or extended-classic purchase orders can be entered in the ERP back-end as follow-on documents to SRM shopping carts.

•

For purchase orders created directly in the ERP back-end system, you need permission for Central Invoice Entry in SRM.

•

Local purchase orders and confirmations are entered in SRM Server.


2009

SRM210

Lesson: Invoice

Figure 110: Invoice and Credit Memo

The purchase order history data is read from the system in which the purchase order was created. This can be SRM Server or SAP ERP. When the document is posted and approved, the payment information is transferred to the corresponding back-end system that contains the Financial Accounting (FI) and Controlling (CO) components. The workload for the invoices is determined by the user's role. Employees can only confirm goods or services that they ordered or if they are the recipient of these goods/services. Vendors can only confirm purchase orders addressed to themselves, whereas central roles like the accountant or purchasers can perform invoices for all purchase orders. It is also possible to post collective invoices, as long as the purchase orders refer to the same:

2009

•

Vendor

•

Invoice recipient (this also means company code)

•

Back-end system


255


SRM210

Figure 111: Tolerances for Invoice/Confirmation

Using the attribute TOG, you can assign tolerance groups to organizational units. The tolerance group consists of pre-delivered tolerance keys with limits specified as value, percentage, or day. The following tolerance keys are used for confirmations (CF) and/or invoices (IV). CF: Over/underdelivery in the confirmation: You use this tolerance to check how the confirmation deviates from percentage limits for overdelivery and underdelivery. First, the system checks in the confirmation against the tolerances created in the purchase order. If none exist, the system checks against the tolerances in the relevant tolerance group (for example, the vendor's tolerance group). If you select the value Unlimited , no tolerances apply. The system displays a controllable message when a tolerance is not reached or is exceeded DA: Exceed value (cumulated): You use this tolerance for both confirmations and invoice entry. You can define an actual value or a percentage for the upper limit. The system checks whether the cumulated invoice value (that is the value of all previous invoice documents plus current invoice documents) exceeds the order value. The check is always made against the purchase order. If a confirmation is expected for an order item, a second tolerance check is made to determine whether the cumulated confirmation value (value of the previous confirmation documents plus current confirmation) exceeds the order value. DQ: Quantity variance (converted to currency amount) : You use this tolerance for both confirmations and invoice entry. If a confirmation is expected for an order item and has already been posted, the system multiplies the net order price by quantity invoiced - (total quantity delivered - total quantity invoiced) . If no confirmation is expected, the system multiplies the net order price by

256


2009

SRM210

Lesson: Invoice

quantity invoiced - (quantity ordered - total quantity invoiced) . The system compares the outcome with the absolute upper and lower limits defined. This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amounts. You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured LA: Amount of limit purchase order : You use this tolerance both for confirmations and invoice entry. The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice, and compares it with the value limit of the purchase order. It then compares the difference with the defined upper percentage and absolute tolerances. LD: Limit purchase order; time limit exceeded : You use this tolerance for both confirmations and invoice entry. The system determines the number of days by which the invoice is outside the planned time interval. If the posting date of the invoice is before the validity period, the system calculates the number of days between the posting date and the start of the validity period. If the posting date of the invoice is after the validity period, the system calculates the number of days between the posting date and the end of the validity period. The system compares the number of days with the absolute upper limit defined. PP: Price variance (value variance from expected value): You only use this tolerance for invoice entry. The variance from the expected value is checked here, based on the preceding document (purchase order price or confirmation value). The system determines by how much each invoice item varies from the product of quantity invoiced, multiplied by the order price. It then compares the variance with the defined upper and lower limits (absolute limits and percentage limits). TX: Tax variance. You use this tolerance exclusively for invoice entry. You define tolerances for tax amounts that are used with the tax calculation.

2009


257


SRM210

Figure 112: Evaluated Receipt Settlement (ERS)

Using ERS, SRM Server automatically posts the invoice on the basis of the purchase order and the confirmation. ERS must be specified on the business partner master record. Purchase orders generated in the back-end system can be settled using the ERS functionality within this back end as usual. ERS is only recommended when you and your vendor have a clear agreement on the conditions.

258


2009

SRM210

Lesson: Invoice

Figure 113: Invoice/Credit Memos - Possible Scenarios

As soon as the invoice/credit memo for a back-end purchase order is posted (and approved) in SAP SRM Server, the following occurs in the back-end system: •

An invoice/credit memo document is created in materials management and is visible in the purchase order history.

•

An accounting document is written in Financial Accounting.

•

A controlling document is written in Controlling.

As soon as the invoice/credit memo for a local purchase order is posted in SAP SRM Server, the following occurs in the back-end system:

2009

•

The invoice/credit memo is posted in SRM Server.

•

An accounting document is written directly in Financial Accounting.

•

A controlling document is written directly in the Controlling component.


259


SRM210


260



2009

SRM210

Lesson: Invoice Exercise

Lesson: Invoice Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •


•


Business Example You want to evaluate the invoice possibilities within SAP SRM Server. Therefore, you check out some invoice scenarios and analyze the communication between the systems.

Exercise 1 Enter an invoice for the Alkaline Batteries from SSP Shopping Cart. Hint: For the following exercise, you have to decide whether you want to post the invoice in the ERP back end or in the SRM Server system. You can only perform one of the two exercises: 1-1 or 1-2. either:

Exercise Section 1-1 in the ERP system with the transaction MIRO

or:

Exercise Section 1-2 in the SRM Server system

Exercise Section 1-1 SAP ERP back-end invoice verification. Caution: Log on to the back-end system:


2009

800

BACK-##

training


261


SRM210

Choose SAP menu Logistics Verification Document Entry !

!

!

Materials Management Enter Invoice.

!

Logistics Invoice

!

Note: If necessary, enter 3000 as company code by choosing Edit Switch Company Code or F7 .

Enter

as Invoice date

Enter

SSP-##

as Reference

Choose

Purchase Order/Scheduling on the tab page PO Agreement reference

Enter

Select

!

in the next field

Enter

Check and enter

Taxes

Enter

Verify that

Balance is 0,00

Choose

only if your tax code equals not “zero” and that there is no tax error

Post

Check the Invoice Document. Choose

Other Invoice Document

Select

Continue

Choose

Show PO structure

View the documents in accounting. Choose

Follow-On Documents

Double-click on

Accounting document

What are the numbers of the G/L accounts? _________________________________________________________ _________________________________________________________ Check the status of shopping cart SSP-## in the SRM system.

262


2009

SRM210


What is the invoice number displayed in the follow-on documents of your SSP shopping cart item for the Alkaline Batteries? _________________________________________________________

Exercise Section 1-2 SRM Server Invoice Process Caution: Log on to the portal:

Client:

##-EMPLOYEE

Create an invoice in SRM Server as follows: 1.

In the Shopping area, select the Invoices/Credit Memos tab.

2.

Choose Create Invoice, select Invoice as Invoice Document Type, and choose Start .

3.

Choose Find beside the Purchase Order Number field to search for matching purchase orders.

4.

Identify your purchase order form the SSP shopping cart and add it to the invoice.

5.

Enter all mandatory fields and ensure that there is no balance.

6.

Choose Check and Post the invoice.

Alternative (easy) option to enter a invoice:

1.

Select a shopping cart with at least one item “open for invoice” from the Shopping Cart query in the Shopping area.

2.

The shopping cart should be displayed. Choose Create Invoice and the system creates an invoice automatically using the data from the purchase order and the confirmation(s).

3.

Refresh the Invoices/Credit Memos query - you should find your invoice there. Hint: You can also create an invoice without purchase order reference. Simply choose the Create Invoice symbol and proceed with the mandatory invoice data.

Exercise 1-3 View the purchase order history in the back-end system. Choose SAP menu Logistics Purchase Order Display. !

!

Materials Management

!

Purchasing

!

!

2009


263


SRM210

Choose

Other Purchase Order

Enter

as Purchase order and confirm

Select

Purchase order history

tab page in the item details

What is the Invoice Number? _________________________________________________________ Leave the transaction.

Exercise 1-4 (Optional) Enter an invoice for the local PO in the SRM Server system. Proceed as described in Exercise 1, but now refer to the purchase order for the water from your SSP-## shopping cart.

Exercise 1-5 Analyze the invoice iDocs. Log on via SAP GUI to either SRM Server or to your ERP back end. Call transaction WE05 and analyze your invoice iDocs. Hint: If you analyze the iDocs in the ERP system, keep in mind that you also will find data of the other groups here as well. It might help you to filter via your logical partner system.

264


2009

SRM210



2009

•


•



265

Unit Summary

SRM210


266

•


•


•


•


•


•


•


•


•


•


•



2009

Unit 8 Operational and Strategic Procurement Unit Overview This unit shows the purchaser's daily work when completing incomplete requisitions. You will also learn about the different sources of supply and the possibilities to control them. Since bidding and auction are important for strategic purchasing, you will also get an impression of those functions.

Unit Objectives After completing this unit, you will be able to:

2009

•

Complete, issue, and change local purchase orders

•

Explain version management and shopping on behalf

•

Complete incomplete purchase orders in SAP SRM Server

•

issue local purchase orders

•

shop on behalf of someone

•

Describe SRM Contract Management

•

Explain the advantage of the sourcing transaction

•

Discuss the bidding and auctioning processes

•

Use conditions and SRM contracts

•

Evaluate central contracts

•

Create bids

•

Implement the vendor list

•

Set up and work with the sourcing application

•

Set up and use the Supplier List for sourcing and shopping cart

•

Explain the principles of the extended classic scenario

•

Configure the SRM Server and the ERP back end for the extended classic scenario

•

Consider the sourcing application and sources of supply for that scenario


267

Unit 8: Operational and Strategic Procurement

SRM210

Unit Contents Lesson: Processing Purchase Orders .......................................269 Lesson: Process Purchase Orders Exercise.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..276 Lesson: Sourcing ...............................................................281 Lesson: Sourcing Exercise ....................................................303 Lesson: Sourcing and Bidding Engine ... .. ... ... .. ... ... .. ... .. ... ... .. ... ..311 Lesson: Supplier List Exercise (Optional) . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..318 Lesson: Extended Classic Scenario (Optional) .. .. .. .. .. .. .. .. .. .. .. .. .. .. .322 Exercise 1: Configuration of Extended Classic Scenario . . . .. . . .. . . . .325

268


2009

SRM210

Lesson: Processing Purchase Orders

Lesson: Processing Purchase Orders Lesson Overview This lesson shows how a purchasers can handle local purchase orders in SAP SRM Server.



•


Business Example You are testing the possibilities for an operational purchaser working with SAP SRM Server.

Purchaser There are two different Purchaser roles in SRM:

2009

•

The Operational Purchaser (SRM role: /SAPSRM/OP_PURCHASER) is responsible for daily work, for example, incomplete local purchase orders, sourcing processes, bids, and auctions.

•

The Strategic Purchaser (SRM role: /SAPSRM/ST_PURCHASER) is responsibile for strategic issues, such as creation of contracts, global outline agreements, and vendor lists.


269


SRM210

Figure 114: Purchaser Roles

Hint: With the introduction of SAP NetWeaver Portal, you should consider more than only the roles within SRM. Please also refer to the portal and ERP roles. It is very likely that you will utilize combined SRM/ERP roles.

Figure 115: Processing Saved (Incomplete) Purchase Orders

270


2009

SRM210


Shopping carts containing local or extended classic items might need purchaser action. Those items will either show up in the sourcing worklist, or they will appear as Saved (incomplete) purchase orders. Operational purchasers have to complete those local purchase orders in the SRM Server system. A purchase order is incomplete if no vendor exists, or if a price is missing. In the header data, the operational purchasers can add a vendor or change a desired vendor. In the item area, they can add or change prices and other data. They may add or delete items, too. In their worklist, purchasers receive saved purchase orders for the employees' approved shopping carts. Some functions of the operational purchaser in SRM Server are: •

Display basic data (for example, purchasing organization and document date), or change the purchasing group, currency, or partner details (requester, goods recipient, vendor).

•

Add or change price conditions on item level for single or all items.

•

Maintain goods receipt and invoice settings per item, for example, when no invoice is expected.

•

Display and process purchase order texts or internal notes. If the purchase order is to be sent, then only the purchase order texts are of importance, not the internal notes.

•

Enter phased delivery schedules.

•

Maintain expected values and overall limits that may not be exceeded by the cost for unplanned goods or services. Display confirmed and calculated value.

•

Choose a different communication medium, if required. The prerequisite being that the relevant fax, e-mail, and XML data exists in the vendor master record.

•

Display and define the follow-on documents. Note: You should be aware that processing saved purchase orders is not a very effective way to complete incomplete shopping carts.

Example: You create a shopping car with three free-text items and will get three purchase orders, with one item each with status Saved. This is because there might be three vendors necessary to cover the request. But even if one vendor would be sufficient, you would have to work on three purchase orders. This is not very satisfying for professional purchasers. Therefore, the sourcing application was developed for more effective completion of shopping carts.

2009


271


SRM210

Figure 116: Issuing the Purchase Order

In SRM Server, it is possible to issue purchase orders, contracts, credit memos, bid invitations, bids, and auctions. First you should define output settings in the vendor data, meaning the output medium. Perform advanced settings in the IMG under Set Output Action and Output Formats . Individual output settings and preview are also possible in the single purchasing document. You can utilize the following output media: •

Print

•

E-mail

•

Fax

•

XML

Beneath the output configuration in the IMG, you also need to maintain your personal output forms in transaction SMARTFORMS. Note: You can also print shopping carts, confirmations, and invoices for internal purposes.

Purchase Order Response SRM Server offers the possibility to work with purchase order responses. This means a vendor will be able to inform you about his or her acceptance and delivery status of your purchase order.

272


2009

SRM210


Usually, the vendor creates the purchase order response within Supplier Self-Services, or sends you that information as an XML document. The system shows all purchase order responses in the corresponding query. There are separate queries, depending on the document status, such as Partly Confirmed , Rejected , and so on. As a purchaser, you can also create purchase order responses manually.

Version Management SAP SRM Server provides you with version management for purchasing documents like purchase orders, contracts, RFX, RFX response, auction, and invoice. The system creates a new document version in the background if you change and issue a document, for example, if you change the delivery date in a purchase order. Independently from the output of the documents, the system also creates change documents (no versions) to track your document changes in total. In contrast to the change documents that retain a change history, a version displays the status of a document at a specific point in time. You cannot change or output versions. This is only possible for the active document. Note: To activate document versions, maintain Switch On Version Control for Purchasing Documents in the IMG.

Hint: Version control can be combined with the workflows settings. For example, you define that if accounting data has been changed, or if the total amount changed more that $500, a purchasing manager has to approve a purchase order or contract.

2009


273


SRM210

Figure 117: Shop on Behalf Of

Secretaries and purchasers can request products on behalf of other users, such as a manager. To shop on behalf of someone, the user specifies the person for whom he or she wants to place a shopping cart before entering any item information. Note: The users for whom secretaries or purchasers are able to shop must be specified as values for the REQUESTER attribute in the organizational structure. The attribute values can be populated by either several users (USEMPLOYEE01) or organizational units (O 50000###).

274


2009

SRM210



2009

•


•



275


SRM210

Lesson: Process Purchase Orders Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •


•


•


Business Example Your purchasers want to evaluate purchase order handling with SAP SRM Server. You need to create a user to evaluate the completion of saved purchase orders and other processes.

Exercise 1 As the administrator, create a purchaser to handle the local incomplete (saved) purchase orders and other purchasing documents. Note: For our convenience, we will create a very powerful purchaser user in the next exercise step. It is likely that in a real situation, you would split the responsibilities across several purchasing users.

276


2009

SRM210

Lesson: Process Purchase Orders Exercise

Create an SRM purchaser, ##-PURCHASER Polly Purchaser-##, using the following data: 1.

User ID: ##-PURCHASER User name: Polly Purchaser-##

2.

SRM roles: a)

/SAPSRM/ST_PURCHASER

b)

/SAPSRM/OP_PURCHASER

c)

/SAPSRM/EMPLOYEE

3.

Assign the ##-PURCHASER user to organizational unit LOCAL Purchasing Group Miller.

4.

Add the entry EC for attribute Transaction Type: Create PO manually to the LOCAL Purchasing Group Miller.

5.

Create a portal user as well, and add the matching portal roles: (Search for the following roles and Add the result.) a)

*emplo*##* (Employee_##)

b)

*core*op*## (Operational Purchaser ##)

c)

*strat*##* (Strategic Purchaser ##)

Exercise 2 Process the incomplete purchase orders from the shopping carts you created. Caution: Log on as purchaser to the portal:

Client: User ID:

##-PURCHASER

initial (change to training or your own)

Exercise Section 2-1 Use the query for saved purchase orders to work on purchase orders waiting for completion. Select Choose Choose

2009

Purchasing

from the Top Level Navigation

Purchasing

in the Detailed Navigation

Saved Purchase Orders query

to look for saved purchase orders and Refresh


277


SRM210

Select the saved purchase order for the “ball pens with phoenix logo” from the shopping cart “Local SC”. Enter

EBP-##

as Supplier

Feel free to check and change other values as well Then

Check and Order

Repeat the same procedure for the shopping cart containing the direct material T-SRM##. What happens after you complete the direct material shopping cart ?

_______________________________________________________

Caution: If you should experience errors referring to the output of the purchase order, it is likely that your vendor does not have a valid send medium in his master data. In that case, correct the send medium before you continue with the exercise.

Exercise Section 2-2 (Optional) Create a local purchase order without a preceding shopping cart. 1.

You should be still logged on to the system as ##-PURCHASER .

2.

In the Purchasing area, navigate to Services. Select Purchase Order under Create Documents.

3.

Select EC as Purchase Order Type and press Start .

4.

Maintain all mandatory data and Order the PO.

Exercise 3 (Optional) Are you interested in the combined SRM/ERP purchaser roles in the portal? Until now we only have seen the SRM portal purchasing roles. If you are interested to see the combined roles, proceed with this exercise. While the plain SRM portal roles are named something like com.sap.pct.srm.core.ro_operationalpurchaser, the combined roles are named com.sap.pct.srm.suite.ro_operationalpurchaser.

278


2009

SRM210

Lesson: Process Purchase Orders Exercise

There are two possibilities to evaluate the combined roles: •

Extend existing user ##-PURCHASER with the combined role

•

Create a new purchaser user in SRM, Portal, and ERP, using the combined portal role.

To identify the combined portal role copied for your group, search in the portal user administration area for role “*suite*op*##.” Note: If you perform the first option, you'll get a second navigation area, Purchasing , as a result of the new role. The content will be similar but not identical; be careful not to confuse yourself.

Hint: Do not forget to consider that a combined portal role also means that you have a role in the ERP back end, not only in SRM server.

Prepare the user of the combined role with matching ERP permissions. You can do this by adding any *MM* Roles in ERP. Or, for a quick approach, you can also grant this test user SAP_ALL profile in the ERP backend.

2009


279


SRM210


280

•


•


•



2009

SRM210

Lesson: Sourcing

Lesson: Sourcing Lesson Overview This lesson discusses the enhanced features of the sourcing transaction and helps you to understand how to work with contracts, bidding, and auctioning.



•


•


Business Example You want to evaluate the enhanced features for professional and strategic procurement with SAP SRM. Further, you need to understand the possibilities of sourcing and the determination of sources of supply.

Sources of Supply

Figure 118: Sources of Supply

2009


281


SRM210

Condition for a product and a vendor : Within the Product Workbench, it is possible to maintain a net price for a product in relation to a vendor. This price can be used as source of supply in the shopping cart, the purchaser’s worklist, and the sourcing transaction. Contract for a product or a product category : The contract contains a vendor, net prices and – optionally – conditions for a product or a special product category. The contract is often used for a long-term source of supply. Bid Invitation/Auction: If there are no sources of supply, or if you are looking for new sources of supply, you can create a Bid Invitation or Auction. Your business partners are able to submit their quotations within SRM Server or via SUS. You can accept bids and create purchase orders or contracts.

Hint: For source-of-supply determination, the SRM system always evaluates the scenario first.

Be aware that not every source of supply is valid for all scenarios. Utilizing the classic scenario for example, it makes no sense to maintain product-vendor price in COMMPR01, because the ERP system is the leading system.

Figure 119: Conditions in Product Workbench

Conditions can be maintained manually or uploaded from an ERP back end (valuation prices for materials only). All conditions in the product workbench are net prices.

282


2009

SRM210

Lesson: Sourcing

If there is a price for the material only, it can be used as valuation price for the workflow, but not for purchasing itself. In any case, it usually helps you to calculate calculate the rough cost. If there is price and vendor data, the prices are vendor-specif vendor-specific ic and can be used as a local source of supply. To enable these vendor conditions, you must maintain a vendor relationship for this product, the so-called interlinkage. Otherwise, the system cannot find the condition. If the source of supply is unique, it can be determined by the system. If is not unique, the employee or purchaser can select the source of supply manually. Contract Types in SRM

•

Centra Centrall Contra Contract ct - Trans Transact action ion Type CCTR: CCTR: New as of SRM 7.0 and ERP Enhancement Package 4. This contract works as a local SRM contract first, but can be also distributed on item and purchasing purchasing organizati organization on basis to one or multiple SAP ERP back-end systems. systems. The leading contract contract for price determinatio determination n is the SRM contract. contract. The distributed technical contract to ERP is a special type of contract and looks different than a standard ERP contract from Materials Management (MM), but works as a similar source of supply in SAP MM.

•

SRM Contra Contract ct - Trans Transacti action on Type PCTR: PCTR: Contract Contract created in SRM and only valid as local source of supply. In other words, this is only helpful for the local and extended classic scenarios.

•

Global Global Outline Outline Agreem Agreement ent - Trans Transacti action on Type GCTR: GCTR: Contract created in SRM and distributed to one (or more) ERP contract(s) in SAP MM. This type of contract is not a valid source of supply in SRM (MM only). contract combines the advantages advantages of the local SRM Note: The central contract contract contract with the contract distributed distributed to ERP MM. Hint: You only can utilize the central contract with SRM 7.0 and SAP ERP 6.0 Enhancement Package 4 or higher. The MM-specific functionality is delivered by business function LOG_MM_P2PSE_1

2009


283


SRM210

Figure 120: Central Contract

Purchase contracts are enhanced sources of supply. Strategic purchasers can create purchase contracts in SRM Server. The item category defines the type of the item. The item can be a product (item category Normal) or a product category . You can enter a target quantity or a target value. To be a valid source of supply, the contract has to be released. Depending on the system configuration, this might require a manager approval .

284


2009

SRM210

Lesson: Sourcing

SRM 7.0 offers three different contract types: •

Report Report BBP_CO BBP_CONTR NTRACT ACT_CH _CHECK ECK enable enabless you you to mon monito itorr if the target target quantity quantity or value of your contracts is close to being reached.

•

Central Central Contra Contracts cts and and Local Local SRM SRM Cont Contrac racts ts can can be be also also integ integrate rated d into into a contract hierarchy to achieve better prices.

•

Contra Contract ct Mass Mass Chan Changes ges helps helps you you to to updat updatee a lar large ge numb number er of of contr contract actss on header and item basis with a few steps.

•

You can can also also uplo upload ad and and d down ownloa load d your your cont contrac racts ts to Micros Microsoft oft Excel. Excel. For details, details, check SAP Notes 734060 734060 and 734946. Hint: SAP Note 790860 addresses frequently asked questions concerning Excel uploads and downloads of SRM documents. Note: As a prerequisite for the use of contract hierarchies, you have to activate them in the IMG, section Activate Hierarchies for Product Categories, Vendors and Contracts .

Figure 121: Group Conditions

Group conditions offer the possibility for value or volume discounts across some or all items in a purchase order. The group discount is automatically calculated if there are items in the purchase order referring referring to the same contract contract item.

2009


285


SRM210

Customizing settings for group conditions (Pricing node in the IMG):

1.

Set Group condition indicator indicator per condition condition type, for an existing existing or an own condition type.

2.

Make sure that this this conditi condition on type type is included included in in your your calculat calculation ion schema.

3.

Make sure sure that that it is also included included in the corresp correspondin onding g condition condition group, group, for example, 0100 for contracts. purchasing conditions conditions with a Hint: It is also possible to achieve better purchasing special contract condition: Condition type 01AG release base rebate. Example: Contract offers a header discount of 3% from $10,000 release value. •

First First purcha purchase se order: order: $6,0 $6,000 00 - no header header rebate rebate

•

Second Second purcha purchase se order: order: $4,5 $4,500 00 - no header header rebate rebate

•

Thir Third d purc purchas hasee orde order: r: $1,0 $1,000 00 - 3% rebate because aggregated contract value $10,000 has been reached

•

Foll Follow owin ing g purc purcha hase se orde orders rs:: 3% reba rebate te

section of the IMG documentation. Note: Also read the Pricing section

Figure 122: Supplier List

286


2009

SRM210

Lesson: Sourcing

The supplier list is integrated into all applications applications that contain a vendor vendor search help and in which you can display sources sources of supply. supply. Requesters Requesters can use a supplier list during shopping cart creation when they search for sources of supply for their shopping cart items. Purchasers Purchasers can also use supplier supplier lists for the completion completion of shopping shopping carts within sourcing, or for the creation of RFx. Supplier Supplier lists are created for products products or for product product categories. categories. The lists can also contain back-end contracts.

Figure 123: Supplier List Creation

Supplier Supplier lists can be created created with reference reference to a product product or a product product category. category. The priority is only a text information information and does not control control the source source of supply determination of the SRM Server. In the sourcing application, you can see all sources of supply coming from the supplier list including their priority.

2009


287


SRM210

During source determination, the supplier list for products are from higher priority than supplier list for the product category only, which is less specific. Hint: Using hierarchically assigned product categories (for example eCl@ss or UNSPSC), you can create a supplier list for a sub-tree of a product category hierarchy. hierarchy.

Maintaining supplier supplier lists does not restrict the use of suppliers. Note: Maintaining Also, sources of supply not contained in supplier lists are visible first. If you want the supplier list to be binding, choose Cross-Application Basic Settings Sourcing Define Sourcing via Supplier List Only in the IMG. !

Purchasers working in the sourcing transaction are always free to select any source of supply, independent of the supplier list and system configuration.

Figure 124: Quota Arrangements

288


2009

SRM210

Lesson: Sourcing

A quota arrangement has the highest priority in the sourcing process. It guarantees that contracts contracts contained contained in that quota arrangement arrangement are used as source of supply for a predefined predefined percentage. percentage. There are two phases during the validity period of a quota arrangement: 1.

Fulfill Fulfillmen mentt of guaran guarantee teed d minimu minimums ms Before the system assigns contracts based on target percentages, the quota arrangement ensures that all guaranteed minimums of contracts participating in that quota arrangement are fulfilled. The sequence in which the guaranteed minimums are fulfilled is determined by the target percentages defined in the quota arrangement. Guaranteed minimums are defined in the contract.

2.

Assignment Assignment of contracts contracts based on target target percentages percentages Once all of the guaranteed guaranteed minimums minimums of contracts contracts participating participating in a quota arrangement have been fulfilled, the system continues to automatically assign contracts based on the target percentages defined in that quota arrangement. The winning contract is then determined by the relative difference between the actual release value and the target value of the quota arrangement.

Figure 125: Price Determination in Shopping Cart

Caution: Beside the priorities, the implemented scenario also needs to be considered. considered. The figure above shows the system behavior when SRM is the leading system. system.

Priorities for price determination are contract, catalog, vendor price, and product price. If no price is found, users can enter a price manually. manually.

2009


289


SRM210

Source-of-supply determination is used to find applicable contracts and conditions in the leading system. If you have products in your shopping cart referring to your back end, the system displays info i nfo records and back-end contracts as additional information, but without price. You should also consider your supplier list settings, especially if you activated in the sourcing customizing. Define Sourcing via supplier list in If the system cannot propose a source of supply, or if you want to have a different source of supply, you can fill in a desired vendor as requester.

Figure 126: Sourcing Application Application

The Sourcing process process is a central central concept in SAP SRM where open requirements requirements from local or ERP back-end back-end systems are assigned assigned sources of supply supply either in the Sourcing application or via the SAP Bidding Engine. The resulting document document (a purchase purchase order or contract) contract) resides either in the local system or the back-end system, depending on the scenario (classic, extended classic, or standalone). The Sourcing application integrates with the Bidding Engine, Auctioning Engine, Contract Management, and SAP Business Information Warehouse.

290


2009

SRM210

Lesson: Sourcing

Figure 127: Sourcing Application

The requirement list contains all internal (shopping cart) and external (plan-driven procurement/external sourcing) requirements. Once you create a follow-on document, document, it no longer appears in Sourcing. Sourcing. With report BBP_SC_TRANSFER_GROUPED, it is possible to group many requisitions into one purchase order or bid invitation using the same vendor and source of supply. You can use Submit to Group to add requirements from the sourcing transaction transaction to this grouping grouping process. The purchase purchase orders and bid invitations assigned to a background grouping process are generated by the report, report, not directly directly from the sourcing transaction. transaction. Purchasers Purchasers can also perform dialog-based bundling of requirements within sourcing.

2009


291


SRM210

Figure 128: Sourcing - Customizing

If sourcing for product categories is not configured, the system creates local purchase orders in the local or extended classic scenario for the requirements. In the classic scenario, the system creates purchase requisitions (or purchase orders) in the ERP system. If you require additional control options, for example, the ability to control processing at product level, you can use BAdI Define Execution of Sourcing . Sourcing is never carried out : This is the default setting. SRM Server does not transfer any items to the purchaser's sourcing application. Sourcing is always carried out: SRM Server transfers each item to Sourcing. Sourcing is carried out for items without a source of supply : If requirements have multiple sources of supply (but none are assigned), or if there is no source of supply for the requirement, SRM Server transfers the requirements to Sourcing. Automatic Creation of Bid Invitations without a source of supply : SRM Server creates a bid invitation for all requirements that do not have a source of supply assigned. Automatic requirement grouping, sourcing for items without assigned source of supply: If a source of supply is assigned to a requirement, the report BBP_SC_TRANSFER_GROUPED automatically groups requirements together for the creation of a PO or an RFx. If the requirement does not have a source of supply, it appears in the worklist of the sourcing application for manual assignment. Once you have assigned a source of supply, you can submit the requirement to the report.

292


2009

SRM210

Lesson: Sourcing

Automatic grouping; sourcing is never carried out : If a source of supply is assigned to a requirement, report BBP_SC_TRANSFER_GROUPED automatically groups requirements together for the creation of a PO. If the requirement does not have a source of supply, an incomplete PO is created. Automatic grouping and creation of bid invitation for items without a source of supply: SRM Server creates a bid invitation for all requirements that do not have any source of supply. If a source of supply is assigned to a requirement, the requirements will be grouped. Define Sourcing via supplier list only: In this activity, you can define that source-of-supply determination for shopping carts is carried out exclusively via the vendor list. Otherwise, the system considers all available sources of supply.

Figure 129: Redistribute Workload

You have two options for changing the assignment of requirements, purchase orders, bid invitations, and contracts to a different purchasing group:

2009

1.

Automatic Assignment: Automatically assign these documents to another purchasing group by defining rules in BAdI BBP_PGRP_ASSIGN_BADI.

2.

Manual Assignment: Reassign these documents manually within the application.


293


SRM210

Bidding and Auctioning Bidding and Auctioning make it possible to search for new sources of supply or to renegotiate existing contracts. Auctioning is restricted to, for example, a few hours, while bidding is an offline process that can take longer. Auctioning also requires installation of the Live Auction Engine. In an RFx, you are often interested in more than prices and delivery dates. With RFx questions on item and header level, you can inquire about additional information that is important for your decision making. Such questions can be also grouped and held in templates. Together with a predefined weighting scale, the questions provide a supplier score for the comparison of the quotations. It is also possible to create lots for your bid invitation. By using lots, you are able to accept only parts of a bid on single-lot levels. It is also possible to print and preview bids and bid invitations. This is helpful if a bidder is not able to create a bid invitation in SRM Server. In this case, you have to permit Surrogate Bidding in the Business Partner Settings of that bidder, which enables a purchaser to enter a bid in the name of that business partner.

Figure 130: Bidding Engine: Submit Bids

Bidders access the Bidding Engine by choosing Submit Bid from the menu. On the initial screen, the bidder can search for a new bid invitation or auction and create a bid, or search for bids they have already created.

294


2009

SRM210

Lesson: Sourcing

Bidders can download bid invitations to Microsoft Excel. Bids can be held so that changes are saved and they can be processed later before they are submitted. Submitted bids are binding. Withdrawing a bid is only possible if the bid has not been accepted or rejected and the submission deadline has not been reached. Once the opening date has passed, the purchaser who created the bid invitation sees that bids have been received and can display them. If bidders are not yet sure about their participation, they can register and communicate a bid intention, which is also visible to the purchaser. It is possible to download bid invitations as Excel files to a local PC. A macro for Excel is provided for customers via SAP Note 734060.

Figure 131: Supplier Selection - Bid Invitation Profiles

Bid invitation profiles allow you to create and tailor processes that meet your business requirements for bid invitations. By customizing of the transaction types in SRM Server, you can modify the behavior of your bids and the possible follow-on documents. Sample transaction types for bid invitations are delivered as part of the standard system. You can modify and delete them, or create new ones.

2009


295


SRM210

Figure 132: Weights and Scores

Weighting and scoring enables you to evaluate more than the bid prices to determine the best vendor. You may evaluate own attributes as well, such as quality certification or references. For each single attribute, you can define your own evaluation functions and values. In the Implementation Guide (IMG), you can include standard fields (such as Incoterms) as dynamic attributes of bid invitations (the Price field is defined by SAP). You can also define attributes as templates, group them, and link them to specific product categories. For details, see IMG section RFX .

296


2009

SRM210

Lesson: Sourcing

Figure 133: Valuation Functions

The above figure shows the possible valuation functions for the weighting of own attributes. Using weights, you have to ensure that the weighting of all items, plus the header values, adds up to 100%. All attributes in the header, or all attributes belonging to a single item, have to add up to 100% as well.

Figure 134: Compare Bids in SRM Server - Example

2009


297


SRM210

This figure shows an example of a response comparison with prices and scores.

Live Auction Purchasers use the Bidding Engine to initiate auctions for products and services. The live auction itself takes place in a Java applet.

Figure 135: Bidding Engine: Live Auction Process

You can create a live auction:

298

•

Manually, as an initial step in the Bidding Engine

•

By converting a bid invitation to a live auction: If you convert a bid invitation to an auction, any attributes on bids that have already been submitted will not be transferred. Bid invitations for which the detailed price indicator has been set cannot be converted to a live auction.

•

From the sourcing transaction: If you create an auction from the sourcing transaction, you cannot add new items.


2009

SRM210

Lesson: Sourcing

Figure 136: Bidding Engine: Live Auction Roles

Both purchasers and bidders can monitor the auction and bidding activity in real time. Real-time charts and graphs provide a visual representation of the auction data. The chat function provides instant messaging capability. The connection status of each invited bidder is indicated in the applet for the purchaser. For the bidder, the indicator refers to the connection status of the purchaser. A bid calculator provides bidders with an overall total bid price before they submit their bids. Live auctions are started, ended, and extended automatically according to the time parameters set by the purchaser when creating the auction.

2009


299


SRM210

Figure 137: Auction Example: Purchaser’s View

Figure 138: Auction Example: Bidder’s View

300


2009

SRM210

Lesson: Sourcing

Figure 139: Live Auction - Factored-Cost Bidding (FCB)

Using factors within the auction allows the purchasing department to consider information that cannot be handled during the auction procedure itself. For example, you can enter an advantage for a bidder who is very reliable and always offers very high quality.

2009


301


SRM210


302

•


•


•



2009

SRM210

Lesson: Sourcing Exercise

Lesson: Sourcing Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •


•


•

Create bids

•


Business Example You intend to migrate some purchasing processes from your ERP back-end systems to your SRM system. Therefore, your want to evaluate the sourcing and bidding processes within SRM Server.

Exercise 1 Maintain a product price in the product workbench. Caution: Log on to the SRM system from the SAP GUI:

Client:

3##

User ID:

SRMCONFIG-##

Start transaction COMMPR01. Choose Enter

Choose

Double-click on Go to Choose

Find

tab page

MAT##

as ID/Description

Start

MAT##

in the list

CONDITIONS

tab page

Purchasing

as Conditions for

Maintain a price with reference to the vendor EBP-##. Choose

2009

01PV

as C Type. in the empty field of the last row


303


Choose

SRM210

Vendor/Product

as Key Combination

EBP-##

as Vendor

Enter

60

as Amount

Choose

USD

as Currency

Enter

1

as Per

Choose

PAL

as Unit

Choose

Continue

Enter

Choose

Relationships

at the top of the screen

Go to

VENDORS

tab page

Enter

EBP-##

as Business Partner

Choose

Save

and Back

Exercise 2 Log on as a purchaser and create a shopping cart for MAT##. Caution: Log on to the portal as a purchaser:

User ID: Password:

##-PURCHASER

training

1.

Create a shopping cart for local product MAT##.

2.

Check if there is a source of supply.

3.

Order and, if necessary, approve the cart.

4.

What did you get as a follow-on document? Why? ___________________________________________________ ___________________________________________________

Exercise 3 Create a local contract in the SRM Server and perform a contract call-off.

Exercise Section 3-1 Create a local SRM contract via the portal as user ##-PURCHASER .

304


2009

SRM210


In the area

Strategic Purchasing

choose

Contract Management

and then

Contract

under Create Documents

Select

PCTR

as Contract Type to create a local SRM contract

Enter

ARAMI-##

as Supplier

First item:

100 Pal MAT##; 70 USD per pallet; Target Quantity 100 In the Item Conditions maintain a discount of 20% via Add Condition and add a Scale value of 25% starting from 10 . Second item:

Create an item with catalog reference. Transfer the catalog item Water from vendor ARAMI-## from the SRM-MDM Catalog by choosing Add Item. Then change the price 11, supplied by the catalog, to 8 becuase the supplier grants you as special price. Change target quantity to 1000.

Check and Release your contract Note: This contract– controlled by transaction type PCTR – works as local contract and therefore as a local source of supply only.

Hint: If local contracts are interesting for you because you want to implement the local or extended classic scenario, you might also add a third item to your contract referring to a local product category.

2009


305


SRM210

Exercise Section 3-2 Create a shopping cart as purchaser or employee to check out the contract usage. 1.

First item:

8 Pal of MAT## Second item:

Search for *water* in the SRM-MDM Catalog and transfer it to the SRM system. Caution: It is important to use the water from the same vendor as in the contract.

2.

Check the Sources of Supply for the Champagne and assign the contract as source of supply. Increase the order value to 12 Pal and check wether the price changes or not.

3.

Check the source of supply for the water as well.

4.

Order (and, if needed, Approve) the shopping cart.

5.

Display the contract again and check the contract release information.

Exercise 4 Examine the advantages of a central contract. In contrary to the SRM contract and the distributed SRM contract (Global Outline Agreement), a central contract is a valid source of supply in both SRM and ERP.

306


2009

SRM210


Exercise Section 4-1 Create a central contract. 1.

Choose Create Central Contract from the contract creation section.

2.

Select CCTR as contract Document Type.

3.

Enter MCCOY-## as Supplier and Central Contract-## as Contract Name. Enter 1000 of product T-SRM## as item 1 with price 89 USD / PC.

4.

Open the Item Details and choose the Distribution tab (or choose the Assign Distribution button). In the Release-Author. Purchasing Org. field, use F4 to select the business partner for PUR BACK Processes . Distribute 5000 PC (Field Target Quantity) and Target Value 445000 USD.

5.

Maintain a rational Header Target Value and check the target value for the distribution in the Header subsection Distribution . Choose Calculate to adopt the target value.

6. Check and Release your contract. Note: You receive warnings because you only distributed 50% to the ERP back end. You could also distribute all.

7. Refresh your contract a few seconds later and check the Tracking tab. What did you find ?

__________________________________________________________________

Hint: Did you notice the Contract Type in Target System field in the Item Details, Distribution tab?

Here, you can determine if a contract or scheduling agreement will be created in the ERP system.

Exercise Section 4-2 Check the distributed contract in the ERP system.

2009

1.

Log on to your ERP system as BACK-##.

2.

Call transaction ME33K and enter < your central contract number > or use the Search Help for Central Contracts (F4).


307


SRM210

Exercise Section 4-3 Create a contract release order form the ERP system. 1.

Call transaction ME21N. Enter 3000 as Purchasing Organization and as Company Code , enter 0## as Purchasing Group.

2.

In the first line of the item overview, enter the number of the Central Contract plus the item number (or the corresponding ERP Outline Agreement plus item number) in the matching fields. Choose Enter and complete the item with 1000 PC T-SRM## for Plant 3200.

3. Save the purchase order. 4.

Start transaction SXMB_MONI in ERP or/and SRM and Execute Monitor for Processed XML Messages. You should find the system communication for the contract distribution as well as the release order information.

5.

Refresh your central contract from the portal and check the Tracking tab. Did you find the contract document numbers and contract release information?

__________________________________________________________

308


2009

SRM210


Exercise 5 (Optional) Other contract management options: 1.

Mass Changes:

Copy your local contract several times or create some new contracts and check out the mass change features. For example change payment terms and conditions afterwards. 2.

Contract Hierarchy:

Set up a contract hierarchy that contains your local contract from exercise 3-1 as a subordinate contract. Create a contract call-off via a shopping cart. Check the contract call-off information in the single contracts. Use the following list as guidance. a)

Activate contract hierarchies in the SRM Server IMG by choosingCross-Application Basic Settings Activate Hierarchies for Product Categories, Suppliers, and Contracts. !

3.

b)

To create a Basis Contract, choose contract creation again and set the Basis Contract indicator.

c)

Edit your local SRM contract from exercise 3-1 and, via Header Hierarchy, enter the number of the basis contract as Superordinate Contract .

!

Quota Arrangements

Create at least one additional contract for MAT##. Maintain a corresponding quota arrangement for both contracts. Create shopping carts for MAT## and check the quota arrangement status. Note: The creation of quota arrangements requires a number range. Create a new entry in the IMG by choosing Number Ranges Define Number Ranges for Supplier List . !

2009


309


SRM210


310

•


•


•

Create bids

•



2009

SRM210

Lesson: Sourcing and Bidding Engine

Lesson: Sourcing and Bidding Engine Lesson Overview



Business Example You want to activate the sourcing functionality for some product categories. Therefore, you need to create a shopping cart with several items and process them via the sourcing transaction.

Exercise 1 Activate the sourcing of requirements in the IMG. Enter a shopping cart to be completed within the sourcing transaction.

Exercise Section 1-1 Set up Sourcing for product categories LOCAL2 and 003 . Caution: Log on to your client of the SRM system from the SAP GUI:

Client: User ID:

3##

In the IMG, choose SRM Server Categories.

2009

SRMCONFIG-## !

Sourcing

!

Define Sourcing for Product

Choose

New Entries

Select with F4

LOCAL2 (Food & Beverage (L)

as Category ID

Choose

Sourcing Always Carried Out

as Sourcing


311


SRM210

Select with F4

003 (Bulbs)

as Category ID

Choose

Sourcing Carried Out for Items Without Ass. Source of Supply

as Sourcing

Choose

Save

and Exit

Exercise Section 1-2 Order a shopping cart with three items that will create requirements in the sourcing transaction. Caution: Log on to the portal as an employee:

User ID:

##-EMPLOYEE

Create a shopping cart and enter the following data: Item 1 MAT##

as Goods / Service

as Required on

3

as Quantity

Halogen bulb 150W

as Description

003 (Bulbs)

as Category

as Required on

100 EA (Each)

as Quantity / UOM

3 USD

as Price

Standard bulb 60W

as Description

003 (Bulbs)

as Category

as Required on

24 EA (Each)

as Quantity

Item 2

Select

Item 3

Select

312


2009

SRM210


Enter

1 USD

as Price

Sourcing

as Name of Shopping Cart and Order the cart

Note: Do not forget to approve the shopping cart, if required.

Exercise Section 1-3 As a purchaser, process the shopping cart items within the sourcing transaction. Caution: Log on to the portal as purchaser:

User ID:

##-PURCHASER

Choose

Purchasing

Choose

Purchasing

Choose Choose

Carry Out Sourcing

from the Top Level Navigation from the Detailed Navigation from Central Functions

Search

Hint: you could also search for special values, requesters and so on

Select

< the three items from the Employee's Sourcing shopping cart >

and Choose Next

Choose

Select All

and then Propose Sources of Supply

Select

as source of supply

and Choose Assign and Create Draft PO

Choose Select

Previous

< both bulb items >

and Choose Create Draft

!

RFX

You should now see a draft for the purchase order with one item and a draft for the bid invitation containing two items.

2009


313


SRM210

Select via search help

EC: (E-Procurement)

as Transaction Type for the PO

Select via search help

BID: (RFX)

as Transaction Typefor the bid invitation

Choose

Process all Drafts

You should get the message, that a PO and an RFx have been created. Note the document numbers: ________________________________________ Close

Exercise 2 Complete the bidding process for both bulb items.

Exercise Section 2-1 Complete the saved RFx created from the sourcing transaction. Note: You should be still logged on to the portal as ##- PURCHASER . Optional:

If you want to enhance this exercise, consider working with attributes and weighting on header and item level. For example you could ask for reference customers, warranty time, shock resistance, or whatever else you prefer. Hint: When working with weighting, do not forget to ensure that all of your weighting adds to 100% in each item.

Choose

Then and

Purchasing or Strategic Purchasing

form the Top Level Navigation

Sourcing and Strategic Sourcing

Refresh

the RFX Query

Select and Edit the saved RFx: Enter:

Add Choose

314

Bulbs-## as Name, and today + one week for Submission Deadline

ARAMI-## and MCCOY-##

as Bidders

Check and Publish


2009

SRM210


Exercise Section 2-2 Extend the roles of your vendors' contact persons. To ensure that your vendors' contact persons have permission to submit bids, they also need assignment to the role /SAPSRM/BIDDER. Add the role /SAPSRM/BIDDER to the vendor users ##-ARAMI and ##-MCCOY by one of the following: •

SAP GUI and transaction SU01

•

Portal service SRM Business Partner Administration

Exercise Section 2-3 Create Quotations. 1.

Log on to the portal as ##-ARAMI and (afterward) ##-MCCOY.

2.

Select RFX and Auctions

3.

Refresh the Query E-RFX and select the RFx. Choose Create Response.

4.

Enter prices and (optional) additional data and Submit the bid. Note: Do not forget to create a bid for both suppliers.

Exercise Section 2-4 Compare the submitted bids as purchaser. 1.

Log on to the portal as ##-PURCHASER .

2.

Refresh the RFx Query, and select your RFx.

3.

Choose Responses and Awards.

4.

Choose Response Comparison tab and then Compare all Responses.

5.

Choose Edit , Accept the cheapest offer, Reject the other, and Save.

6.

Go back to the Response Comparison and select the response you just accepted.

7.

Choose Create Purchase Order .

8.

What did you get? Validate the follow-on document in the target system. __________________________________________________________

2009


315


SRM210

Exercise 3 (Optional) Check out the grouping features of SRM Server. 1.

Activate grouping for the product category of your local MAT##.

2.

Create several requirements with a valid source of supply assigned for your product. Hint: If you do not have a unique source of supply, group the requirements in the sourcing application first.

3.

316

Create the follow-on purchase order(s) using the grouping report BBP_SC_TRANSFER_GROUPED.


2009

SRM210



2009



317


SRM210

Lesson: Supplier List Exercise (Optional) Lesson Overview This is an optional exercise, that explains the Supplier List features.



Business Example You need to prepare the Supplier List in the IMG. Then, you want to maintain a Supplier List with two entries.

Exercise 1-1 Setup the Supplier List (VL) Customizing Hint: There have been several name changes in the last few years. The terms “Vendor List”, “Supplier List”, and “Approved Supplier List” all refer to the same document. Caution: Log on to the SRM from the SAP GUI:

Client:

3##

User ID:

SRMCONFIG-##

From the IMG, choose SRM Server Cross-Application Basic Settings Number Ranges SRM Server Number Ranges Define Number Ranges for Supplier List . !

!

!

Choose

Intervals

Enter

01

as the No

and Interval

to insert a new interval

Enter

9500000000

as the From number

Enter

9509999999

as the To number

Choose

318

!

Save

and Back


2009

SRM210

Lesson: Supplier List Exercise (Optional)

Exercise 1-2 Verify that the transaction type VL exists for the SRM Supplier List (BUS2206 Vendor List). Choose Cross-Application Basic Settings

!

Define Transaction Types.

Enter a valid text schema for the vendor list.

Exercise 1-3 Maintain the Supplier List for the product MAT##. Caution: Log on as purchaser to the portal:

User ID:

##-PURCHASER

Choose

Strategic Purchasing

Choose

Business Partner

Choose

Supplier List Query

and Create Supplier List

MAT##

as Product Nr

ARAMI-## and EBP-##

as source of supply

Enter

Add your vendors Maintain

form Top Level Navigation from Detailed Navigation

a high priority for the contract vendor, and a lower one for the product price Check and Release

the supplier list

Hint: If there is an issue with a supplier, you do not need to delete the supplier from the supplier list; simply deactivate the Supplier is Active flag instead.

You can try this later as an optional exercise step.

2009


319


SRM210

Exercise 1-4 Create a shopping cart for MAT## and check if the supplier list entries are displayed. 1.

Add an item for MAT##.

2.

Check if the supplier list entries are displayed.

3.

Do not assign a source of supply.

4.

Order the shopping cart.

Exercise 1-5 Complete the shopping cart via the sourcing transaction.

320

1.

Start the sourcing application.

2.

Search for the shopping cart with the item MAT##.

3.

Select the cart and choose Propose Sources of Supply .

4.

Check the supplier list entries, assign a source of supply, and create the purchase order.


2009

SRM210

Lesson: Supplier List Exercise (Optional)


2009



321


SRM210

Lesson: Extended Classic Scenario (Optional) Lesson Overview This lesson will deepen you understanding of the extended classic scenario by focusing on the exercises. You will also have the opportunity to assess your knowledge of some basic configuration settings.



•


•


Business Example You want to examine what the procurement processes would be like if you implement the extended classic scenario instead of the classic scenario.

The Extended Classic Scenario

Figure 140: Extended Classic Scenario Document Flow

322


2009

SRM210

Lesson: Extended Classic Scenario (Optional)

What are the rules of the extended classic scenario, and how do you configure it in the system? •

The extended classic scenario can be determined via central customizing settings or via BAdI implementation.

•

The SRM system is the leading system and the documents are local at first.

•

The SRM system only considers local sources of supply.

•

As soon as the local purchase orders are complete, they are transferred to the ERP system.

•

To transfer documents, you have to think about number ranges, document types, and other settings. Note: If you are not sure what to do in the following exercises, rework the lessons about back-end integration and direct procurement processes.

2009


323


324


SRM210

2009

SRM210


Exercise 1: Configuration of Extended Classic Scenario Exercise Objectives After completing this exercise, you will be able to: •

Set up the extended classic scenario for your client

•

Examine the system behavior according your customizing settings

Business Example Your company is still discussing whether the classic scenario or the extended classic scenario better fits their needs. You want to examine the extended classic scenario in detail.

Task 1: Set up the Extended Classic Scenario. Perform the customizing settings to activate the extended classic scenario 1.

Log on as user SRMCONFIG and activate the extended classic scenario in the IMG. Furthermore, adjust the number ranges for the local purchase order and change the BSA attribute in your organizational structure.

2.

Activate the extended classic scenario in the IMG.

3.

Check the number ranges for local purchase orders in SRM Server.

4.

Check the transaction types for local purchase orders.

Task 2: Maintain transaction type for the back-end purchase order in the organizational structure. The transaction type in SRM Server for the purchase order in the back-end system needs to be synchronized with the ERP purchase order settings in Materials Management. 1.

Start transaction PPOMA_BBP from your favorites.

2.

Select your root organizational unit and go to the Attributes tab.

Task 3: Create a shopping cart for the extended classic scenario. Check out the extended classic scenario in your role as purchaser. 1.

Log on as ##-PURCHASER via the portal. Continued on next page

2009


325


2.

SRM210

Create a Shopping cart with two items: First item: Alkaline Batteries from your catalog

Second item: Free-text item Metal Halide Lamp from category Bulbs (003) and price 10 USD. 3.

Order your shopping cart

4.

Check the follow-on documents for both items. What is the Batteries / document number? ____________________ What is the Metal Halide Lamp / document number ? ____________________

Task 4: Complete the item with the metal halide lamp. As purchaser, complete the second item of your shopping cart from the sourcing transaction. 1.

Select the sourcing transaction from the menu.

2.

Search via Product Category “003” for the metal halide lamp item.

3.

Enter one of your vendors and a price 100 USD, and choose Create Draft Purchase Order . Select document type DP## in the draft purchase order overview. Choose Process all Drafts and write down the number of your follow-on document. Number of follow-on document: ____________________

Task 5: Check the follow-on documents in the ERP system. You want to ensure that both purchase orders exist in the back-end system. 1.

Log on as user BACK-## to client 800 of your ERP system . Enter ME23N as transaction code and display your purchase orders from the last shopping cart. Try to switch to change mode. Did you successfully change the purchase order ? Why or why not ? ______________________________

Continued on next page

326


2009

SRM210


Task 6: Enter Goods Receipt and Invoice with reference to your purchase orders. Create follow-on documents with reference to your purchase orders. 1.

For your first purchase order, enter confirmation and invoice in SRM Server.

2.

For the second purchase order, enter goods receipt and invoice in the ERP system.

3.

Check the follow-on documents of the purchaser orders and the shopping cart.

Task 7: Optional: Examine the determination of source of supply in the extended classic scenario. You want to check how the extended classic scenario can handle sources of supply for products that are replicated from your ERP system. 1.

Create a product and vendor condition (interlinkage) for one of the replicated products, such as 100-100 or T-SRM1##. Create a shopping cart, check the calculated price and the source of supply, and order. Analyze the follow-on documents.

2.

Same procedure as step 1, but now use a different product and create an SRM contract in advance as a source of supply.

3.

Imagine additional scenarios utilizing vendor list, quotation, sourcing, and central contract.

Task 8: Reset the system to classic scenario. Caution: If you have finished all exercises for the extended classic scenario, de-activate this scenario in the IMG. Also, switch back to the value EC for the BSA attribute in PPOMA_BBP.

2009


327


SRM210

Solution 1: Configuration of Extended Classic Scenario Task 1: Set up the Extended Classic Scenario. Perform the customizing settings to activate the extended classic scenario 1.

Log on as user SRMCONFIG and activate the extended classic scenario in the IMG. Furthermore, adjust the number ranges for the local purchase order and change the BSA attribute in your organizational structure. a)

Enter the following information. User ID

2.

SRMCONFIG-##

Password

Client

3##

Activate the extended classic scenario in the IMG. a)

From the IMG, choose SRM Server Cross-Application Basic Settings Activate Extended Classic Scenario. !

!

b) 3.

Enable Extended Classic Scenario Active .

Check the number ranges for local purchase orders in SRM Server. a)

In the IMG, choose Cross-Application Basic Settings Number Ranges SRM Server Number Ranges Define Number Ranges for Local Purchase Orders. !

!

b)

!

Select Display Number Ranges and check that you already have maintained a number range, 04 , starting from 403##0000. Hint: This is the number range youused for the direct material scenario, which typically behaves as extended classic scenario. Therefore you already have ensured that the number range 04 has a matching number range in the back end.

If you do not find that number range, it is likely that you missed the exercise for the Direct Procurement lesson in unit 7.

Continued on next page

328


2009

SRM210


4.

Check the transaction types for local purchase orders. a)

In the IMG, choose SRM Server Define Transaction Types.

!

Cross-Application Basic Settings

!

b)

Select BUS2201 Purchaser Order .

c)

Double-click Transaction Types and check that DP## with internal number range 04 exists. Hint: This is the transaction type you used for the direct material scenario, which typically behaves as extended classic scenario. You maintained transaction type DP## in SRM Server as well as document type DP## in the ERP back end.

If you do not find that transaction type, it is likely that you missed the exercise for the Direct Procurement lesson in unit 7.

Task 2: Maintain transaction type for the back-end purchase order in the organizational structure. The transaction type in SRM Server for the purchase order in the back-end system needs to be synchronized with the ERP purchase order settings in Materials Management. 1.

Start transaction PPOMA_BBP from your favorites.

2.

Select your root organizational unit and go to the Attributes tab. a)

Choose Document Type in R/3 System in the attributes drop-down box. Change the document type from EC to DP## and save your settings.

Task 3: Create a shopping cart for the extended classic scenario. Check out the extended classic scenario in your role as purchaser. 1.

Log on as ##-PURCHASER via the portal.

2.

Create a Shopping cart with two items: First item: Alkaline Batteries from your catalog

Second item: Free-text item Metal Halide Lamp from category Bulbs (003) and price 10 USD. 3.

Order your shopping cart

4.

Check the follow-on documents for both items. Continued on next page

2009


329


SRM210

What is the Batteries / document number? ____________________ What is the Metal Halide Lamp / document number ? ____________________

a)

You should find a local purchase order for the batteries.

b)

You should see that the metal halide lamp is in the Purchaser's worklist.

Task 4: Complete the item with the metal halide lamp. As purchaser, complete the second item of your shopping cart from the sourcing transaction. 1.

Select the sourcing transaction from the menu.

2.

Search via Product Category “003” for the metal halide lamp item.

3.

Enter one of your vendors and a price 100 USD, and choose Create Draft Purchase Order . Select document type DP## in the draft purchase order overview. Choose Process all Drafts and write down the number of your follow-on document. Number of follow-on document: ____________________

Task 5: Check the follow-on documents in the ERP system. You want to ensure that both purchase orders exist in the back-end system. 1.

Log on as user BACK-## to client 800 of your ERP system . Enter ME23N as transaction code and display your purchase orders from the last shopping cart. Try to switch to change mode. Did you successfully change the purchase order ? Why or why not ? ______________________________ a)

You cannot change the purchaser order in the ERP back-end system due to the rules of the extended classic scenario.

Task 6: Enter Goods Receipt and Invoice with reference to your purchase orders. Create follow-on documents with reference to your purchase orders. 1.

For your first purchase order, enter confirmation and invoice in SRM Server. Continued on next page

330


2009

SRM210


2.

For the second purchase order, enter goods receipt and invoice in the ERP system.

3.

Check the follow-on documents of the purchaser orders and the shopping cart.

Task 7: Optional: Examine the determination of source of supply in the extended classic scenario. You want to check how the extended classic scenario can handle sources of supply for products that are replicated from your ERP system. 1.

Create a product and vendor condition (interlinkage) for one of the replicated products, such as 100-100 or T-SRM1##. Create a shopping cart, check the calculated price and the source of supply, and order. Analyze the follow-on documents.

2.

Same procedure as step 1, but now use a different product and create an SRM contract in advance as a source of supply.

3.

Imagine additional scenarios utilizing vendor list, quotation, sourcing, and central contract.

Task 8: Reset the system to classic scenario. Caution: If you have finished all exercises for the extended classic scenario, de-activate this scenario in the IMG. Also, switch back to the value EC for the BSA attribute in PPOMA_BBP.

2009


331


SRM210


332

•


•


•



2009

SRM210

Unit Summary


2009

•


•


•


•


•


•


•


•


•


•


•

Create bids

•


•


•


•


•


•



333

Unit Summary

334

SRM210


2009

Unit 9 Procurement of External Requirements Unit Overview This unit explains how to work on external requirements from other systems in SRM Server. You will learn how to transfer a purchase requisition from the ERP back end to the sourcing application, where the purchasers complete the requirement. You will also learn about the deltas with SAP ERP 6.0 Enhancement Package 4.


Explain how purchase requisitions from your SAP back end can be transferred to SRM Server

•

Describe the possible business processes and the deltas with SAP ERP 6.0 Enhancement Package 4

•

Transfer purchase requisitions to SRM Server

•

Complete the requirements in the sourcing cockpit

Unit Contents Lesson: Procurement of External Requirements ...........................336 Lesson: Procurement of External Requirements Exercise .. . . . .. . . . .. . . . .345

2009


335

Unit 9: Procurement of External Requirements

SRM210

Lesson: Procurement of External Requirements Lesson Overview This lessons illustrates in detail how to work on external requirements within SAP SRM Server.



•


Business Example You want to evaluate the possibility of working on ERP back-end requirements in SRM Server.

Procurement of External Requirements Procurement of External Requirements supports working within SRM Server on external requirements. Requirements out of SAP back- ends are replicated to SRM Server. Depending on the version of the ERP system, the system communication is RFC or XML (SOA). Requirements from non-SAP systems can be integrated as well. The requirements coming from an SAP back-end system can result from different applications like PM or PS, or can be created manually.

336


2009

SRM210

Lesson: Procurement of External Requirements

Figure 141: Procurement of External Requirements - System Landscape

Typically, the purchaser starts his or her follow-up actions from the sourcing application. With SAP ERP 6.0 Enhancement Package 4, it is also possible to create a saved RFx directly in SRM.

Procurement of External Requirements Before ERP 6.0 Enhancement Package 4 The figure below shows an example of an external requirement out of an SAP back-end system, in SAP ERP 6.0 Enhancement Package 3 or lower.

2009


337


SRM210

Figure 142: Plan Driven Procurement - SAP Requirement

In this example, a MRP run causes a purchase requisition referring to a reservation. Based on the settings in the V_T160EX and V_T160PR views, the requisitions are determined to be transferred to the corresponding SRM Server. Report BBP_EXTREQ_TRANSFER in the back-end system transfers the requisitions (via RFC) to the SRM system.

338


2009

SRM210


Figure 143: Plan Driven Procurement - Sourcing in SRM

Note: This figure still shows screens from SRM 5.0, as this is the standard procedure with SRM 5.0, also known as Plan-Driven Procurement. The technical principles are also valid for SRM 7.0, as long as your ERP system is not on Enhancement Package 4.

Figure 144: Plan Driven Procurement until ERP 6.0 EHP 4 - Prerequisites

2009


339


SRM210

Besides the settings for the direct material process, there are some additional necessary steps: •

Using an entry channel, the requisitions are transferred to SRM Server. This channel must have at least one entry user.

•

Corresponding to this entry user, you have to set up an RFC connection from the ERP back end to SRM Server by using this special RFC user.

•

To get the requisitions in the work list for purchase orders, or in sourcing, a required local purchasing group is responsible for the entry channel and the product category of the back-end requisitions.

•

Customizing of sourcing or a BAdI decides if the sourcing transaction or the work list for purchase orders will be used

•

View V_T160EX in the ERP back end determines which material groups and purchasing groups are grouped into a profile. View V_T160PR determines which profile targets to which RFC connection.

•

The transfer itself is carried out by report BBP_EXTREQ_TRANSFER. This can be scheduled, for example, once a day.

Figure 145: Technical Settings in SAP Back End until ERP 6.0 EHP 4

340


2009

SRM210


This figure shows the steps as described in the Plan Driven Procurement: Prerequisites figure. Note: This process allows you to group line items (either services or materials) and to transfer customer fields on item level to SRM Server (for example, fields in account assignment). Service items belonging to an unique service specification are grouped at standard. Materials can be grouped based on a customer-specific logic. Therefore, a BAdI is offered in the back-end system: BBP_BADI_EXTREQ_OUT

This process does not include the transfer of service hierarchies; only “flat” service requisitions are supported!

Procurement of External Requirements with SRM 7.0 and ERP 6.0 Enhancement Package 4 As soon as business function LOG_MM_P2PSE_1 within ERP 6.0 Enhancement Package 4 is activated, the transfer of purchase requisitions from ERP to SRM is controlled by BAdI ME_REQ_SOURCING_CUST.

Figure 146: External Requirements with SRM 7.0 and ERP 6.0 EHP 4

This BAdI controls: The possibility to transfer purchase requisitions via CPPR from ERP to SRM sourcing application manually (with purchaser interaction).

2009


341


SRM210

The possibility to transfer purchase requisitions via CPPR from ERP into SRM Bidding Engine as a saved RFx, again manually. The possibility to transfer purchase requisitions automatically via PI message from ERP to SRM sourcing application; no purchaser interaction needed.

Figure 147: Central Processing of Purchase Requisitions (CPPR)

The figure abouve shows an example of CPPR, which is an optional feature and requires portal integration for ERP. You do not have to utilize CPPR if you only want to transfer purchase requisitions to SRM automatically.

342


2009

SRM210


Figure 148: Control of Automatic Transfer and CPPR

To activate the transfer of purchase requisitions in ERP 6.0 EHP 4, activate the event linkage for BUS2105, as shown in the figure above, and implement the following BAdI. In the IMG, choose Materials Management Purchasing Portal Business Add-Ins for Purchasing Portal BAdI: Activate Sending of Purchase Requisition to Ext. Procurement System. !

!

!

!

Note: For the BAdI implementation, you have to consider four blocks:

cv_aut_sourcing = cl_mmpur_constants=>yes. Activates external sourcing in general cv_ext_rfx_ind = cl_mmpur_constants=>yes. Activates SRM RFX cv_ext_sc_ind = cl_mmpur_constants=>yes. Activates transfer to SRM sourcing IF is_req_item-ekgrp = '001' ... cv_ext_sourcing = cl_mmpur_constants=>yes [Example for the control of the auto transfer to SRM] Note: Before performing the corresponding PI configuration, refer to SAP Note 1263876 and solution Manager information.

2009


343


SRM210


344

•


•



2009

SRM210

Lesson: Procurement of External Requirements Exercise

Lesson: Procurement of External Requirements Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •


•


Business Example You want to validate and perform some configuration steps to transfer purchase requisitions to SRM Server.

Exercise 1 Check the ERP settings for the transfer of purchase requisitions to SRM Server. Note: The following process is only valid if your back-end system runs on ERP 6.0 Enhancement Package 4 or higher. For lower versions, refer back to the unit. Caution: Log on to client 800 of the back end from the SAP GUI:

Client: User ID:

800

BACK-##

Exercise Section 1-1 (Optional) Check the event type linkage for BUS2105 in SAP ERP. Note: This exercise step is optional, as the settings in ERP have been already performed to enable this scenario also for other classes.

Start transaction SWETYPV and search for BUS2105 as object type. Check that the following entries exist:

2009


345


SRM210

Object Type

Event

Receiver Type

Type Linkage

BUS2105

CREATED

WS53800009

X

BUS2105

CHANGED

WS53800009

X

Exercise Section 1-2 (Optional) Check the implementation of Business Add-Ins. Choose Activate Sending of Purchase Req. to Ext. Proc. System (ME_REQ_SOURCING_CUST) to automatically send purchase requisitions to SAP SRM. Call transaction OLME and choose Portal Business Add-Ins for Purchasing Portal BAdI: Activate Sending of Purchase Requisition to Ext. Procurement System. !

!

Display enhancement implementation Z_MFE_ME_REQ_SOURCING_CUST. Caution: Do not change the BAdI Implementation; you would affect other participants and classes!

Select Implementing Class on the left side and the method IF_EX_ME_REQ_SOURCE_CUST~CHECK_EXTERNAL_SOURCE . You will find the criteria for the automatic transfer of purchase requisitions from ERP to SRM there. What did you find ?

__________________________________________________________

__________________________________________________________

Note: There are additional settings needed in the PI area, and also within SRM server, especially if you want to transfer service hierarchies.

Exercise 2 Configuration settings in SRM Sever Caution: Log on to your SRM client from the SAP GUI:

346


2009

SRM210


Client: User ID:

3##

SRMCONFIG-##

Exercise Section 2-1 Transfer the user TRA_RFC via USERS_GEN into your organizational structure. Note: User TRA_RFC is used by the PI connection that transfers the purchase requisition to SRM Server. This user needs to be integrated into the organizational structure, as he or she is the creator of the resulting shopping cart.

Hint: You already uploaded the user TRA_RFC in the Workflow unit, together with WF-BTACH.

Exercise Section 2-3 Set up sourcing for your product category. You want to have all products from category 00107 in your SRM sourcing cockpit. From the IMG, choose SRM Server Categories.

!

Sourcing

!

Define Sourcing for Product

Select

New Entries

Choose with F4

00107

as Category ID

Select

Sourcing Always Carried Out

as Sourcing Option

Choose

Save

and leave the transaction

Exercise 3 Create a purchase requisition for the material T-SRM4##. Execute transaction ME51N (Create Purchase Requisition) in the ERP back end. Request 1000 PC of material T-SRM4## for plant 3200. Save the document and record the document number: _________________

2009


347


SRM210

Which purchasing group is responsible? ___________ Hint: Does the ERP actually know which SRM client to send the requisitions to? No, it does not. While the old V_T* tables also controlled the RFC connection to the SRM server, in the new scenario with ERP 6.0 EHP 4, the PI routing settings determine the receiver system of the requisitions.

Exercise 4 Perform sourcing in SRM Server Caution: Log on to the portal as purchaser:

User ID:

##-PURCHASER

Identify your requirement in the sourcing transaction. 1.

Log on as ##-PURCHASER to the Portal.

2.

Start the Sourcing application.

3.

Search for your requirement and complete the process. You have two options: a)

Initiate an RFx process, which ends up as purchase order.

b)

Complete the requisition directly in the sourcing transaction and search for a valid source of supply, or enter vendor and price manually. Caution: In both cases, select DP## as transaction type for the purchase order, as this is a direct material scenario. Note: As an optional exercise step, you could also transfer purchase requisitions with materials or free-text items with account assignment into SRM sourcing. They will then be procured in the classic scenario.

Exercise 5 Check the purchase requisition status. Start transaction ME53N in the ERP system and double check External Source of Supply in the item details. What did you find? ___________________________________________________________

348


2009

SRM210



2009

•


•



349

Unit Summary

SRM210


350

•


•


•


•



2009

Unit 10 Service Procurement Unit Overview This unit focus on the principles of service procurement with SAP SRM. Again, we will demonstrate the deltas with ERP 6.0 Enhancement Package 4.


Illustrate the process for the procurement of external staff

•

Explain service procurement with integration with materials management in your SAP back-end system.

•

List the additional possibilities with ERP 6.0 Enhancement Package 4

•

Create shopping carts with classic service items

•

Perform sourcing of ERP purchase requisitions with hierarchical service specifications in SRM Server

Unit Contents Lesson: Procurement of External Staff (Optional)..........................352 Lesson: Integration with ERP Service Procurement .. .. .. .. .. .. .. .. .. .. ..356 Lesson: Classic Service Procurement Exercise .. .. .. .. .. .. .. .. .. .. .. .. .. ..364

2009


351

Unit 10: Service Procurement

SRM210

Lesson: Procurement of External Staff (Optional) Lesson Overview This lessons shows the procurement of external staff. The process starts with a service request at an external service provider, and ends with the confirmation of times performed.



Business Example You plan to request external staff directly at the potential service providers, and want to find out how SAP SRM can support you.

Procurement of External Staff A request for external staff utilizes the Bidding Engine. The request can be created from the shopping cart user interface, or directly from the RFx transcation (Purchasers only). The requester specifies a supplier and, optionally, a favored service provider who is an employee of this supplier. If there is no entry for the supplier, the incomplete purchase order is sent to the purchaser’s work list or to the sourcing application.

352


2009

SRM210

Lesson: Procurement of External Staff (Optional)

Figure 149: Procurement of External Staff

Limit positions within the service request enable you to set a provision for unplanned services that are not precisely definable in amount or duration. This combines planned and unplanned positions that belong together in a single temporary-labor shopping cart. Confirmations for services can be created and invoiced within a predefined limit. The detailed type of service can be specified at the time of service entry. This guarantees cost monitoring.

2009


353


SRM210

Figure 150: Create Bid Response and Create Time Sheet

The requester (or purchaser) can analyze the answers of the potential service providers. He or she is informed by e-mail if there is an answer. As soon as one of the bids is accepted, the system creates a purchase order. Confirmations can be entered by the service provider, the requester, or a central role in SRM. Iif the service providers maintain the time sheets themselves, it makes sense to let them create the time sheets within Supplier Self-Services (SUS), not SRM Server. Note: This is basically a local scenario. Using other scenarios, you have confirmations, but not the time sheet option.

Hint: The process described above is not binding. You can also utilize classic service items from ERP MM-SRV in an RFXxand confirm services performed in SRM Server, ERP, or SUS.

354


2009

SRM210

Lesson: Procurement of External Staff (Optional)


2009



355


SRM210

Lesson: Integration with ERP Service Procurement Lesson Overview This lesson demonstrates how the procurement of “classic” services can be handled between SAP ERP and SRM Server.



•


Business Example You want to evaluate how existing service master data of your SAP back end and the corresponding materials management processes can be integrated with SAP SRM, and vice versa.

Shopping Carts for Services in Classic Scenario SRM Server supports the procurement of services with integration into the back-end service processes of materials management (MM-SRV).

356


2009

SRM210

Lesson: Integration with ERP Service Procurement

Figure 151: Integration into MM-SRV

Shopping carts might contain service items replicated from the back-end service master. But it is also possible to work with free-text items or catalog-service items. Depending on the configuration settings and existing sources of supply, you will get a purchase order or purchase requisition in the ERP back end. If a purchase requisition is created, the back-end purchaser has to complete this document first. Of course, it is also possible to work on such classic service requirements within the sourcing transaction.

2009


357


SRM210

Figure 152: Integration into MM-SRV (2)

The service confirmation may happen in SRM Server, SAP SUS, or the ERP back end. In all cases, the back-end purchase order history will be updated, along with the shopping cart history. Note: The service configuration within SUS is not included in the figures above.

Limits in Shopping Cart and Purchase Order Shopping with Limit Items is available, for example, to purchasing roles and, possibly, for local and back-end product categories.

358


2009

SRM210


Figure 153: Shop with Value Limit

The amount of the expected value in the shopping cart with limit is used for the approval workflow. The follow-up actions determine if there will be an invoice only or a confirmation and an invoice. You can enter the account assignment in the shopping cart, the confirmation, or the invoice, unless the follow-on documents are to be created in the ERP system. The limit items as well as the Follow-Up Actions and the accounting data are also visible in the subsequent purchase order in either SRM Server or in ERP. Note: Limit items may be combined with planned items, such as material, free text, or service items.

2009


359


SRM210

Service Procurement Classic with ERP 6.0 Enhancement Package 4 Enhanced service procurement with SAP SRM 7.0 and ERP 6.0 delivers: 1.

Creation of purchase requisition with outlines in ERP

2.

Automatic or manual transfer of the purchasing requisition to SRM (either into sourcing application or as saved RFx into bidding engine)

3.

Sourcing and bidding procedure in SRM

4.

Follow-on document is always classic - a purchase order or contract in SAP ERP

5.

If SUS is in use, the classic ERP purchase order is also transferred to SUS, where the supplier can download and confirm the purchase order.

6.

Service confirmation and invoice can be entered in SRM Server, ERP ,or SUS.

Figure 154: Enhanced Service Procurement – Classic

Caution: To utilize this scenario, it is mandatory that you implement SRM 7.0 together with ERP 6.0 Enhancement Package 4 or higher.

360


2009

SRM210


The additional features are delivered by business function Procurement-SRM Integration (LOG_MM_P2PSE_1). Note: The creation of a shopping cart with a hierarchical structure of line items is currently not supported.

Figure 155: Transfer of ERP Purchase Requisition to SRM

Any purchase requisition (as long as master data has been synchronized) can be transferred to SRM Server. In the new classic service procurement scenario, it is likely that you will want to use the capabilities of the bidding engine, so it makes sense to transfer the requisition directly into the bidding engine. For technical reasons, the system also creates a shopping cart as intermediate document. Note: If you perform a search for sources of supply for a service requisition within the sourcing cockpit, the system considers only ERP sources of supply. Therefore, remember the corresponding MM-SRV settings in the ERP IMG, transaction OLMSRV Source Determination and Default Values. !

Hint: There will be additional features and functions for service procurement with EHP 1 for SRM 7.0 and EHP 5 for ERP 6.0; please check the SAP Service Marketplace for updates.

2009


361


SRM210

Figure 156: Configuration for Enhanced Service Procurement – Classic

Note: The configurable item numbering scheme was introduced by the Public Sector Procurement industry solution. Therefore, you will find entries for long procurement document numbers in the IMG.

You only need to check/adopt the hierarchy entries as shown in these figures. Menu paths for the configuration settings in the figure: 1.

Maintain Hierarchy Template for transaction type SAP Supplier Relationship Management Cross-Application Basic Settings Service Procurement Activate Service Procurement !

!

2.

!

Define Configurable Item Numbering Scheme: SAP Supplier Relationship Management Cross-Application Basic Settings Configurable Item Numbering Define Configurable Item Numbering Scheme , then Rules and Rule Assignment for Item levels !

!

362

!


2009

SRM210




•


Related Information For all ERP settings, please refer to the external procurement unit. Check SAP Note 1269445 and related notes for additional information.

2009


363


SRM210

Lesson: Classic Service Procurement Exercise Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •


•


Business Example Exercise 1 Create a shopping cart for services in the classic scenario and analyze the follow-on process.

Exercise Section 1-1 Order services for metal processing. Caution: Log on to the portal:

User ID:

##-EMPLOYEE

Create a shopping cart with a free-text item for classic services: 1.

Start the shopping cart transaction.

2.

Create a free text item: a)

Product Type: Service

b) Description: Derust metal construction

3.

c)

Product Category: 001

d)

10 HR (Hours) and Price: 35 USD / HR

e)

Enter a valid performance date.

Order your shopping cart and check the follow-on document: Follow-On document: _____________________________________________

Exercise Section 1-2 Analyze the follow-on document in the SAP back-end system.

364


2009

SRM210

Lesson: Classic Service Procurement Exercise

Caution: Log on to the ERP system:

Client:

800

User ID:

BACK-##

View the purchase requisition that were created. Use transaction

ME53N (DISPLAY PURCHASE REQUISITION)

Select

Other requisition

Enter

Select

Other document

Choose

Exit

to display the purchase requisition

as Purchase Requisition

Exercise Section 1-3 Create a back-end purchase order with reference to the purchase requisition. Use transaction

ME21N (CREATE PURCHASE ORDER)

to create a purchase order with reference

Enter

MCCOY-##

in field vendor

Select Enter

to open the header of the purchaser order

Enter Enter

3000

as Purch. Org

0##

as Purch Group

3000

as Company Group

Item overview: Scroll to the right in the item overview

until you find the columns for: Purch. req. and Requisn. item

2009

Enter

< your purchase requisition number >

in the column Purch. req

Enter

< the item no. of your purchase requisition >

in the column Requsin. item


365


Choose

SRM210

Enter

Confirm any messages. Save the Purchase Order but do not leave the transaction! Purchase Order number:

Exercise Section 1-4 Confirm services performed in SAP SRM and ERP.

Exercise Section 1-4-1 Log on again to the portal as ##-EMPLOYEE. Check that the purchase order number occurs in the follow-on documents section of your shopping cart.

Exercise Section 1-4-2 Confirm the service performed for 7 hours derusting in SRM Server as Employee. Use transaction Confirm Goods / Service Performed in SRM Server

Exercise Section 1-4-3 (Optional) Create a service entry sheet in the ERP back end. If you are experienced with MM-SRV, use transaction ML81N to create a service entry sheet for the remaining 3 hours of work.

Exercise Section 1-4-4 View the purchase order history in the ERP back end. Select

Other Purchase Order

for your P.O. to refresh the displayed data

Enter

as Purchase Order

Expand

Item Detail

Choose

Purchaser Order History

Select and display

Select

Exit

tab page

(two times)

Exercise 2 Sourcing of ERP service requirements with hierarchical service directories.

366


2009

SRM210


This exercise outlines the possibilities of souring purchase requisitions containing service hierarchies within SRM Server.

Exercise Section 2-1 Create a purchase requisition with service hierarchies in SAP ERP. Create a purchase requisition with service items for category Service- 00, relevant plant, and purchasing group for direct transfer to SRM. Caution: Log on to the ERP system:

Client:

800

User ID:

BACK-##

Execute transaction ME51N (Create Purchase Requisition). In the

Item Level

Enter

K

as Account assignment

Enter

D

as Item Category

Enter

Services for SRM RFX

as Short Text

Enter

3200 (Atlanta)

as Plant

Do not forget to Enter

X##

as Purchasing group

In the Service Tab , choose Select

Full Scr. Services

Services Selection

to open the service specifications screen on top left section of the screen

In the dialog box, ensure that the MSS button is selected. Search for

and choose

RKT-CONS

as MSS

Complete Hierarchy (Adopt All)

This will open a new dialog box, where you need to enter the Account Assignment Data. Enter

2009

1000

as the Cost Center


367


SRM210

Auto Repeat AA

and choose Choose

Save and Back

Purchase Requisition Number: __________________________________________________ Display the purchase requisition again and check External Source of Supply :

_______________________________________________________________________

Exercise Section 2-2 Identify your requirement in the SRM sourcing transaction. 1.

Log on as ##-PURCHASER to the SRM Portal.

2.

Start the sourcing application.

3.

Search for your requirement and complete the process. You have two options: a)

Create an RFx process, which ends up with a classic purchase order.

b)

Complete the requisition directly in the sourcing transaction to create a classic PO.

Exercise Section 2-3 Check the status of the purchase requisition in ERP Call transaction ME53 and select your purchase requisition again. Check External Source of Supply in the item details. What did you find?

___________________________________________________

Exercise 3 (Optional) If your are already experienced with Materials Management and services in SAP ERP, you can also examine the processes with replicated services.

368


2009

SRM210


Caution: To avoid interference with other groups, please contact your instructor before you perform this exercise.

1.

Ask your instructor first whether it is currently possible to download service master data from the ERP system. If yes, your instruct r will release you in the back-end control table CRMRFCPAR.

2.

In R3AC1, maintain the following for object service master : ASMD as Table MATKL as Field EQ as OP 007 for Low

2009

3.

Save and synchronize your filter settings.

4.

Start the download via transaction R3AS.

5.

Check in transaction COMMPR01 that your services are available. If not, contact your instructor for further assistance.

6.

Proceed according to Exercise 1. Create a shopping cart, check follow-on documents, and create a classic purchase order and service entry.

7.

You may also think about sourcing and bidding scenarios.


369


SRM210


370

•


•



2009

SRM210

Unit Summary


2009

•


•


•


•


•



371

Unit Summary

372

SRM210


2009

Unit 11 Administration Unit Overview This unit contains a conglomeration of useful transactions and hints for troubleshooting, as well as a short summary of some techniques.


Report and analyze your documents

•

Perform middleware diagnoses

•

Report and analyze your work items

Unit Contents Lesson: Administration.. .... .... .... .... ... .... ... .... .... .... ... .... .... .... ..374

2009


373

Unit 11: Administration

SRM210

Lesson: Administration Lesson Overview This lesson supplies you with some additional information and will help with troubleshooting, reporting, and analyses.



•


•


Business Example You want to learn how to troubleshoot and analyze SRM Server and the ERP follow-on processes.

Document Monitoring and Miscellaneous Administration Using the application monitors requires that you activate them in the IMG. Choose Cross-Application Specific Settings Start Application Monitors. !

The monitors are beneficial to find erroneous documents, to track them, and to identify the problem.

374


2009

SRM210

Lesson: Administration

Figure 157: Application Monitor

In the Application Monitor: •

Select a line with a red light to get more information about the error.

•

Select an error message to display a list of available tools.

•

If the error is fixed, select it and choose Delete Selected Error Message. Note: There are also monitors for changed business partner data and contract distribution.

2009


375


SRM210

Figure 158: Shopping Cart Reporting

You can monitor shopping carts as administrator from the portal. This is more interesting from the business point of view, for example, who ordered what. Hint: Sometimes it is also interesting to perform the analysis from the SAP GUI. In this case, start transaction BBP_BW_SC2.

376


2009

SRM210


Figure 159: Generic Document Analysis

To get detailed information about a Shopping Cart (or any other procurement document) and its related objects, use transaction BBP_PD. Double-click to navigate forward. You will also find the table names there. ALE Monitoring

Useful ALE transactions: •

Check inbound and outbound parameters

•

Check ports

• •

IDoc status lists Display and resend IDoc

Check partner profiles Open the partner type LS and select either your back end or your SRM to check which IDocs are coming in or going out. Check the details for the IDocs. All parameters you see in this transaction were generated from the distribution model. Check To see whether a port has been created correctly, select Transactional RFC and choose the Port to get details. IDoc status lists: Display and re-send IDocs:

2009


377


SRM210

PI- and Service-Oriented Communication

•

Check PI messages via transaction SXMB_MONI. Review error information and payload in ERP, SRM, and PI system.

•

If there is an error with PI messages, check transaction /SAPPO/PPO2 (Postprocessing Desktop) and search for Mode of Postprocessing Order with values “0” to “3.”

•

The error information in /SAPPO/PPO2 might refer to a UOM, currency, or master data issue; follow up that information with the appropriate transaction.

Archiving SRM Documents

•

•

The following documents can be archived: –

Shopping cart

–

Purchase order and purchase order Rresponse

–

Confirmation and invoice

–

Contract or global outline agreement

–

Auction, bid, and bid invitation

–

Procurement Card Statements

Restrictions: –

Not possible to restore the archive files to the file system

–

You cannot process/change archived documents

–

See SAP Note 726509

Aligning UoM, Currencies, and Exchange Rates

378


2009

SRM210


Figure 160: Aligning UoM, Currencies and Exchange Rates

The reports mentioned on above figure are helpful to align currencies and exchange rates with your ERP system. It is recommended that you run them regularly. Transaction CUNI contains the units of measurement (UoM). Take note of your ISO codes within catalog scenarios and, especially, for the classic service procurement processes. You need to be sure that the UoM are in synch between ERP, SRM Server, Catalog, and SUS. Interesting SAP Notes

2009

•

Note 547601 – FAQ workflow, runtime environment, and troubleshooting

•

Note 322526 – Analysis for workflow problems

•

Note 815849 – FAQ: Account assignment system response

•

Note 520717 – Budget check in EBP

•

Note 828231 – Commitments and SRM

•

Note 548862 – FAQ: EBP user administration

•

Note 402592 – EBP in the environment of Central User Administration

•

Note 1328088 – PPO: Text not available in logon language

•

Note 1268821 – Configuration of Central Contract Management

•

Note 455140 – Configuration of e-mail, fax, paging, or SMS using SMTP

•

Note 1261825 – SAP SRM uses Roles Matrix

•

Note 1003026 – Prerequisites for OCI Integration in SAP SRM 6.0

•

Note 1270081 – Troubleshooting SOA Services


379


SRM210

Links on SAP Service Marketplace

•

Always begin with http://service.sa p.com (user ID required – can be requested from here).

•

/instguides – Installation Guides

•

/releasenotes – Check Release Notes

•

/notes – Check for Notes (Corrections)

•

/securityguide – Information about system security

•

/srm – Common SRM information Hint: Example: http://service.sap.com/instguides SRM installation guides

!

SAP SRM for the

Master Data Master Data – Vendor and Materials:

•

Check Vendor Master Data Transfer –

•

Check log after initial download

Check Product Master Data Replication –

Monitor download objects

–

Check inbound queue for incoming master data (SRM Server)

–

Check outbound queue for outgoing master data (ERP)

–

Check errors with BDocs or

Vendor master data transfer: To check whether all vendors have been replicated correctly after the initial download, use transaction with BBPGETVD as application object. Product Replication: Use transaction to check progress in the process of replicating master data. The traffic light will be green if replication was successful.

Use transactions and to check the system queues. It can be also helpful to check the BDoc status.

380


2009

SRM210


Workflow Reporting, Troubleshooting, and Additional Information Useful Transactions for Analysis

•

SLG1 - Search for BRF messages during schema evaluation

•

BB_PD - Display document to find the related work item number

•

SWI1 - Selection and analysis of single work items

•

SWI2_FREQ - Work items per task

•

SWI2_DIAG - Workflow diagnosis for erroneous work items

•

SWI6 - Display work item

•

SWIA - Process work item as administrator

•

SWE2 - Check event type linkage

•

SM58 - Transactional RFCs - check related to WF-BATCH

•

SWU_OBUF - Synchronize workflow runtime buffer

Figure 161: BRF Logon transaction SLG1– Example

2009


381


SRM210

Figure 162: Web Dynpro Application – Document Approval Analytics

Note: Before you can work with the Document Approval Process Analysis, activate the service as shown in the figure above.

To execute the analysis, log on with a user supplied with sufficient permissions to run the transaction. As soon as the screen appears, you can search for your documents and start investigations.

382


2009

SRM210


Figure 163: Workflow Notifications

Define Recipient of Notifications:

For each scenario (shopping cart, confirmation, invoice), select the user roles to receive e-mail. In the details per item, define which events trigger the e-mail. Hint: If you need advanced workflow control and information, please check the IMG documentation Define Deadlines for Events. Here you can define deadlines for reminders with reference to several business objects. The system works like this:

1.

There are pre-delivered event schemata, similar to text types.

2.

Maintain an event schema entry per transaction type, for example “SC” for BUS2121.

3.

Enter deadlines per events with reference to the business object, event schema and specific event, for example, WF_APPR_LATEST_START (Workflow Approval latest start).

UI and Field Control This section contains some hints about UWL, POWL, customer fields, and Web Dynpro. Query and POWL Adjustments

2009


383


SRM210

Figure 164: Refresh of Portal Queries

Use transaction POWL_QUERY to define the layout of queries centrally. Hint: Report POWL_D01 enables administrators to delete personal user settings for the queries. This might be helpful for the central distribution of new adapted queries.

Figure 165: How to Change Buttons and Columns in POWL

384


2009

SRM210


Start transaction /SAPSRM/POWL_CUST or, in the IMG, choose Cross-Application Basic Settings POWL and Advanced Search Adjust POWL Layout, Search Criteria and Pushbuttons. !

!

Other important transactions regarding POWL configuration: POWL_TYPE POWL_TYPER POWL_QUERY

Figure 166: How to Change Buttons and Columns in POWL (2)


2009


385


SRM210


If you do not know the technical feeder type name, you can find out by starting to change a query. The object type name (description) is displayed in the header line. Look up that name in transaction POWL_TYPE, column Description. If you find more than one entry, you can compare field catalog content or try some changes. If you are authorized to access portal content, you could also look up the application (APPLID) and check entries in transaction POWL_TYPER to verify that you selected the correct type. For the Shopping Cart, there are two entries, SAPSRM_FEEDER_SC_PROF (shown in the figures) and SAPSRM_FEEDER_SC (for queries in Employee Self Service).

386


2009

SRM210




Influencing Field Properties and Customer Fields

2009


387


SRM210

Figure 171: Changing Business Object Field Properties

Additional documentation about this topic has been attached to activities in IMG. Choose Cross-Application Basic Settings Extensions and Field Control (Personalization). !

Figure 172: Changing Business Object Field Properties (2)

You have the option to create classes or methods to arrange visibility based on conditions (see examples in the Class Name column, as shown above). In the case of conflicting entries in SAP-owned or customer-owned tables for the same field name, the more restrictive entry is valid (generated entries in table /SAPSRM/C_MDF_IL evaluated at runtime).

388


2009

SRM210


Figure 173: Changing Business Object Field Properties (3)

If there is no entry in the customer-owned table /SAPSRM/V_MDF_IC, the entry in the SAP-owned table /SAPSRM/V_MDF_IT for the CURRENCY field will determine field appearance. After entering the CURRENCY field into the customer-owned table /SAPSRM/V_MDF_IC with ‘Vis’ (= Visible) and ‘EBD’ (= Enabled) set to Inactive, the field will not be visible, as these entries are more restrictive than those in the SAP-owned table /SAPSRM/V_MDF_IT.

Figure 174: Adding a Field to a Business Object

2009


389


SRM210

Figure 175: Adding a Field to a Business Object (2)


From the IMG, choose Cross-Application Basic Settings Control (Personalization) Configure Customer Fields Fields on Item Level .

!

!

390


Extensions and Field Define Customer

!

2009

SRM210




2009


391


SRM210

For item data, use the view /SAPSRM/V_MDF_IC. From the IMG, choose Extensions and Field Control (Personalization) Configure .Field Control Configure Control for Fields on Item Level Metadata for Fields on Item Level !

!

!

Hint: You will find the content entered into customer fields in table BBP_PDISC for item fields (like in this example) and in table BBP_PDHSC for header fields. You can define that content of customer fields is copied from one document to its follow-on document, for example, from SC to PO. Referring to this example, you would have to execute step 1 (create append) for the PO structure and step 3 (metadata table entry) for business object type BUS2201. If the field name and type of both business objects is exactly the same, the content will be transferred from SC item to PO item whenever a PO is created out of an SC. Control of Tabs and Fields in a Business Object

Figure 179: Hiding a Tab in a Business Object Screen

392


2009

SRM210


Figure 180: Hiding a Tab in a Business Object Screen (2)


2009


393


SRM210



394


2009

SRM210


Figure 184: How to Move Fields in a Business Object

Figure 185: How to Move Fields in a Business Object (2)

2009


395


SRM210

Figure 186: How to Move Fields in a Business Object (3)

Hint: System control variables like SY-TCODE and SY-UCOMM used in customer BAdI implementations are no longer supported with SRM Web Dynpro. For a workaround, please check SAP Note 1334202 – How to get current action ID and transaction group.

Additional Information About Service-Based Communication

Figure 187: Enterprise SOA Enabling

396


2009

SRM210


Figure 188: Business Suite 7 Enterprise Services for Suite Excellence

Figure 189: Interoperability: Semantic and Technical

2009


397


SRM210

Figure 190: What is an Enterprise Service?

An enterprise service: Is a callable entity that provides business functionality Is structured according to a harmonized enterprise model based on global data types (GDTs), process components, and business objects Is published by SAP in the Enterprise Services Repository guarantees quality and stability Is documented Is based on open standards

398


2009

SRM210


Figure 191: SAP NetWeaver 7.1 Process Integration (PI)

SAP NetWeaver Process Integration (PI) 7.1 is one of the key building blocks of the enterprise SOA technology offered by SAP NetWeaver. Used for middleware consolidation in customer landscapes, this release will mainly leverage functionalities for service enablement and service and process orchestration. There will be no major changes from an architectural point of view, but the underlying application server will be based on the JEE5 and ABAP server. This also means that all the improvements in sizing and memory consumption will also be applied to the Process Integration capabilities. The Enterprise Services Repository (ESR) is the central SOA repository for storing all your SOA artifacts based on particular business semantics. The ESR is enhanced with objects that will enable customers to service-enable their applications based on SAP’s process-component-modeling methodology. The ESR contains information in the form of a yellow pages to have one central place where all the services in the customer’s landscape can be discovered. The Services Registry is based on a UDDI V3.0 server. This is enhanced further with business classifications, based on the same methodology that is used at design time.

2009


399


SRM210

Figure 192: SOA Middleware

Figure 193: Enterprise Services Repository and Services Registry

400


2009

SRM210


Figure 194: Enterprise Services Repository and Services Registry (2)

Figure 195: Suite Excellence Enterprise Services

2009


401


SRM210

Figure 196: Suite Excellence Sourcing Enhancement

Figure 197: Scenario with Direct Service Call

402


2009

SRM210


Figure 198: Postprocessing Desktop

2009


403


SRM210


404

•


•


•



2009

SRM210

Unit Summary


2009

•


•


•



405

Unit Summary

406

SRM210


2009

Unit 12 Appendix: Procurement for Public Sector (PPS) Unit Overview Unit Objectives After completing this unit, you will be able to: •

List some specific functions of SAP PPS with SRM 7.0

Unit Contents Lesson: APPENDIX: Procurement for Public Sector (PPS)...............408

2009


407

Unit 12: Appendix: Procurement for Public Sector (PPS)

SRM210

Lesson: APPENDIX: Procurement for Public Sector (PPS) Lesson Overview This lesson shows some selected details from Procurement for Public Sector.



Business Example You want to evaluate the benefits with SRM PPS for customers from the public sector.

Smart Document Number

Figure 199: Smart Document Number - Example

408


2009

SRM210

Lesson: APPENDIX: Procurement for Public Sector (PPS)

Figure 200: Smart Document Number - Example (2)

Figure 201: IMG Section for Smart Document Number Configuration

2009


409


SRM210

Figure 202: Numbering Schema

Figure 203: Components and Classes

410


2009

SRM210


Figure 204: Rules

Figure 205: Numbering Types and Default Rules

2009


411


SRM210

Figure 206: Setup of Smart Number

Figure 207: ERP Configuration for Smart Numbers

412


2009

SRM210


Figure 208: Customer-Specific Configuration Overview

Figure 209: Customer-Specific Configuration

2009


413


SRM210

Figure 210: Customer-Specific Configuration (2)


414


2009

SRM210




2009


415


SRM210

Figure 214: Number Ranges

Figure 215: Smart Numbers in ERP

416


2009

SRM210


Document Builder

Figure 216: Document Builder Overview

Figure 217: Document Builder Overview (2)

2009


417


SRM210

Figure 218: Document Builder Integration

Figure 219: Document Creation Dialog

418


2009

SRM210


Figure 220: Document Summary

Figure 221: Creating a Clause

2009


419


SRM210

Figure 222: Edit a Clause in Microsoft Word

Figure 223: Insert a Standard Document

420


2009

SRM210


Figure 224: Rules Configuration

Figure 225: Preview Document and Reports

2009


421


SRM210

Figure 226: Sample Output

Tendering Topics

Figure 227: Tendering Overview

422


2009

SRM210


Figure 228: PQQ Configuration

Figure 229: PQQ Configuration (2)

2009


423


SRM210

Figure 230: PQQ Example - Purchaser's View

Figure 231: Tender Fee Processing

424


2009

SRM210


Figure 232: Configuration of Tender Fee

Figure 233: Tender Fee Example - Purchaser's View

2009


425


SRM210

Records Management

Figure 234: Records Management Overview

Figure 235: Records per Object Type

426


2009

SRM210


Figure 236: Structure of a Record

Figure 237: Record Example - PO

2009


427


SRM210

Figure 238: Record from Purchase Requisition

Figure 239: Accessing SRM Documents from Record

428


2009

SRM210


Subcontracting

Figure 240: Subcontracting Process

Figure 241: Subcontracting Process (2)

2009


429


SRM210

Figure 242: Subcontracting Activation

430


2009

SRM210



2009



431

Unit Summary

SRM210

Unit Summary You should now be able to: •

432



2009

SRM210

Test Your Knowledge

Test Your Knowledge

2009


433

Test Your Knowledge

SRM210

Answers

434


2009

SRM210

Course Summary

Course Summary You should now be able to: •

Explain the procurement processes and the responsible roles within the SRM Server

•

Configure the SAP SRM Server to support Self-Service Procurement, Procurement of External Requirements, Service Procurement, Central Contract Management, and (Strategic) Sourcing

•

Monitor business processes with SAP SRM Server

Related Information •

SAP Service Marketplace: http://service.sa p.com/srm (no user is necessary for SAP Service Marketplace).

•

Documentation: http://help.sap.com/saphelp_srm70/helpdata/en/74/344c430fab4d0bbc30996d56cc293a/frameset.htm If the URL does not work, use http://help.sap.com SAP Supplier Relationship Management .

2009


!

SAP Business Suite

!

435

Course Summary

436

SRM210


2009

Srm210 en Col92 Fv Part a4

Recommend Documents