Business Scenario Config Self Service Procurement

Business Scenario Configuration Guide

SRM®

Self-Service Procurement 3.0

Using SAP Enterprise Buyer 4.0

Document Version 1.8 - September 15, 2003

SAP AG Neurottstraße 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

JAVA® is a registered trademark of Sun Microsystems, Inc. © Copyright 2002 SAP AG. All rights reserved.

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

J2EE™ is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

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

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and Commerce One. All other product and service names mentioned are the trademarks of their respective owners.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic Server

TM are

trademarks of IBM Corp. in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation. Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components.

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

LINUX is a registered trademark of Linus Torvalds and others. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

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

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

Documentation in the SAP Service Marketplace You can find this documentation at the following address: http://service.sap.com/instguides

Terms for Included Open Source Software

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names:

For the HTTPClientStack library, the following conditions apply: HTTPClientStack - a library to enable an easy programmatic access to the HTTP protocol stack

Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs) written by James Random Hacker.

Copyright © 2001 Ronald Tschalär This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

<signature of Ty Coon>, 1 April 1990 Ty Coon, President of Vice

This library is distributed by in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. SAP’s warranty and liability is subject to your end user license with SAP. These warranties and liabilities are only on SAP’s behalf and not on behalf of any other contributors. On behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits is expressly excluded. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Ronald Tschalär [email protected]

THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

For the Jakarta Apache tool, the following conditions apply: This product includes software developed by the Apache Software Foundation (http://www.apache.org/). The Apache Software License, Version 1.1 Copyright © 2000 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright

notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above

copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see http://www.apache.org/.

3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)."

Portions of this software are based upon software originally written by Daniel F. Savarese. We appreciate his contributions.

Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.

4. The names "Apache" and "Apache Software Foundation", "Jakarta-Oro" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

SAP and/or its distributors may offer, and charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of the software. However, SAP and/or its distributors may do so only on its/their own behalf, and not on behalf of the Apache Software Foundation or its contributors.

5. Products derived from this software may not be called "Apache" or "Jakarta-Oro", nor may "Apache" or "Jakarta-Oro" appear in their name, without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

For the JDom tool, the following conditions apply: This product includes software developed by the JDOM Project (http://www.jdom.org/)." Copyright © 2000 Brett McLaughlin & Jason Hunter. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright

notice, this list of conditions, and the following disclaimer. 2. Redistributions in binary form must reproduce the above

copyright notice, this list of conditions, and the disclaimer that follows these conditions in the documentation and/or other materials provided with the distribution.

This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally created by Brett McLaughlin ([email protected]) and Jason Hunter ([email protected]). For more information on the JDOM Project, please see http://www.jdom.org/.

3. The name "JDOM" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior written permission from the JDOM Project Management ([email protected]).

In addition, we request (but do not require) that you include in the end-user documentation provided with the redistribution and/or in the software itself an acknowledgement equivalent to the following: "This product includes software developed by the JDOM Project (http://www.jdom.org/)." Alternatively, the acknowledgement may be graphical using the logos available at http://www.jdom.org/images/logos.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS `ÀS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

For the Jython tool, the following conditions apply: HISTORY OF THE SOFTWARE JPython was created in late 1997 by Jim Hugunin. Jim was also the primary developer while he was at CNRI. In February 1999 Barry Warsaw took over as primary developer and released JPython version 1.1. In October 2000 Barry helped move the software to SourceForge where it was renamed to Jython. Jython 2.0 is developed by a group of volunteers. The standard library is covered by the BeOpen / CNRI license. See the Lib/LICENSE file for details. The oro regular expresion matcher is covered by the apache license. See the org/apache/LICENSE file for details.

JYTHON CHANGES SOFTWARE LICENSE

JPYTHON SOFTWARE LICENSE. Copyright © 2000, Jython Developers IMPORTANT: PLEASE READ THE FOLLOWING AGREEMENT CAREFULLY.

All rights reserved.

BY CLICKING ON THE "ACCEPT" BUTTON WHERE INDICATED, OR BY INSTALLING, COPYING OR OTHERWISE USING THE SOFTWARE, YOU ARE DEEMED TO HAVE AGREED TO THE TERMS AND CONDITIONS OF THIS AGREEMENT.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright

notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above


JPython version 1.1.x 1. This LICENSE AGREEMENT is between the Corporation for

National Research Initiatives, having an office at 1895 Preston White Drive, Reston, VA 20191 ("CNRI"), and the Individual or Organization ("Licensee") accessing and using JPython version 1.1.x in source or binary form and its associated documentation as provided herein ("Software").

- Neither the name of the Jython Developers nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

2. Subject to the terms and conditions of this License Agreement, CNRI hereby grants Licensee a non-exclusive, non-transferable, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use the Software alone or in any derivative version, provided, however, that CNRI's License Agreement and CNRI's notice of copyright, i.e., "Copyright ©1996-1999 Corporation for National Research Initiatives; All Rights Reserved" are both retained in the Software, alone or in any derivative version prepared by Licensee.

3. Alternatively, in lieu of CNRI's License Agreement, Licensee may substitute the following text (omitting the quotes), provided, however, that such text is displayed prominently in the Software alone or in any derivative version prepared by Licensee: "JPython (Version 1.1.x) is made available subject to the terms and conditions in CNRI's License Agreement. This Agreement may be located on the Internet using the following unique, persistent identifier (known as a handle): 1895.22/1006. The License may also be obtained from a proxy server on the Web using the following URL: http://hdl.handle.net/1895.22/1006." In the event Licensee prepares a derivative work that is based on or incorporates the Software or any part thereof, and wants to make the derivative work available to the public as provided herein, then Licensee hereby agrees to indicate in any such work, in a prominently visible way, the nature of the modifications made to CNRI's Software.

4. Licensee may not use CNRI trademarks or trade name, including JPython or CNRI, in a trademark sense to endorse or promote products or services of Licensee, or any third party. Licensee may use the mark JPython in connection with Licensee's derivative versions that are based on or incorporate the Software, but only in the form "JPython-based ___________________," or equivalent.

5. CNRI is making the Software available to Licensee on an "AS IS" basis.

CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS.

6. CNRI SHALL NOT BE LIABLE TO LICENSEE OR OTHER USERS OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. SOME STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY SO THE ABOVE DISCLAIMER MAY NOT APPLY TO LICENSEE.

7. This License Agreement may be terminated by CNRI (i) immediately upon written notice from CNRI of any material breach by the Licensee, if the nature of the breach is such that it cannot be promptly remedied; or (ii) sixty (60) days following notice from CNRI to Licensee of a material remediable breach, if Licensee has not remedied such breach within that sixty-day period.

8. This License Agreement shall be governed by and interpreted in all respects by the law of the State of Virginia, excluding conflict of law provisions. Nothing in this Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between CNRI and Licensee.

9. By clicking on the "ACCEPT" button where indicated, or by installing, copying or otherwise using the Software, Licensee agrees to be bound by the terms and conditions of this License Agreement.

THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT

For the RegEX Apache tool, the following conditions apply: This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." The Apache Software License, Version 1.1 Copyright © 1999 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see http://www.apache.org/.

3. The end-user documentation included with the redistribution, if any, must include the following acknowlegement:

"This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." SAP and/or its distributors may offer, and charge a fee for, warranty,

support, indemnity or liability obligations to one or more recipients of the software. However, SAP and/or its distributors may do so only on its/their own behalf, and not on behalf of the Apache Software Foundation or its contributors.

Alternately, this acknowlegement may appear in the software itself, if and wherever such third-party acknowlegements normally appear.

4. The names "The Jakarta Project", "Jakarta-Regexp", and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

5. Products derived from this software may not be called "Apache" nor may "Apache" appear in their names without prior written permission of the Apache Group.

For SAX, the following conditions apply: SAX 2.0 I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release all of the SAX 2.0 source code, compiled code, and documentation contained in this distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of fitness for any purpose. David Megginson, [email protected] 2000-05-05

For the Struts Apache tool, the following conditions apply: This product includes software developed by the Apache Software Foundation (http://www.apache.org/). The Apache Software License, Version 1.1 Copyright © 1999-2001 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright

notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above


3. The end-user documentation included with the redistribution, if any, must include the following acknowlegement: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowlegement may appear in the software itself, if and wherever such third-party acknowlegements normally appear.

4. The names "The Jakarta Project", "Struts", and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

5. Products derived from this software may not be called "Apache" nor may "Apache" appear in their names without prior written permission of the Apache Group.

THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see http://www.apache.org/. SAP and/or its distributors may offer, and charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of the software. However, SAP and/or its distributors may do so only on its/their own behalf, and not on behalf of the Apache Software Foundation or its contributors.

Typographic Conventions Icons Type Style Represents

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.

Cross-references to other documentation

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

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

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

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

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Self-Service Procurement: Configuration Guide ..................................................................... 14 mySAP.com Solution and Business Scenario Documentation Landscape ......................... 16 SAP Notes............................................................................................................................ 18 General Settings .................................................................................................................. 19

Aligning Units of Measurement, Currencies, and Exchanges Rates ............................... 19 Scheduling Reports .......................................................................................................... 20 Setting the Control Parameters........................................................................................ 21 Defining Update Intervals ................................................................................................. 21 Starting Application Monitors............................................................................................ 22 Setting Up the SAP Internet Pricing Configurator ............................................................ 22 Configuration for Sending Internet Mails (SAPconnect) .................................................. 22 Setting up Attachments .................................................................................................... 24

System Connections ............................................................................................................ 25 Making Settings for the Internet Transaction Server........................................................ 25

Starting SAP Enterprise Buyer (Start URL) .................................................................. 27 Making Entries Needed for Generating Application URLs ............................................... 27 Defining the RFC Destination and Making ALE Settings ................................................. 28 Defining Backend Systems .............................................................................................. 30 Installing the SAP Integrated Catalog with SAPinst ......................................................... 31 Configuring SAP Integrated Catalog ................................................................................ 33

Checking the Server Configuration............................................................................... 34 Mapping Parameters .................................................................................................... 35 Configuring Customer Fields ........................................................................................ 36 Checking the BugsEye Configuration........................................................................... 37 Defining the Internal Call Structure in SAP Enterprise Buyer....................................... 38 Displaying Contract Data .............................................................................................. 39 Displaying Multiple Contract Data ................................................................................ 40

Data replication .................................................................................................................... 40 Replication of Materials from R/3 Backend Systems ....................................................... 40

Customizing Material Replication in Enterprise Buyer ................................................. 41 Setting the Middleware Parameters ............................................................................. 42 Downloading Customizing Objects............................................................................... 43 Downloading Business Objects .................................................................................... 44

Business Customizing.......................................................................................................... 46 Organization Configuration............................................................................................... 46

Regenerating Role Profiles........................................................................................... 46 Creating the Organizational Plan.................................................................................. 47 Making Settings for Create Internal User ..................................................................... 49

SAP Business Scenario Configuration Guide 16.09.2003

Maintaining the User Attributes .................................................................................... 50 Managing Business Partner Addresses ....................................................................... 51 Making Settings for Locations and External Business Partners................................... 51

Process Configuration ...................................................................................................... 53 Setting Up SAP Business Workflow ............................................................................. 53 Defining Transaction Types.......................................................................................... 58 Defining Number Ranges ............................................................................................. 59 Making Settings for Account Assignment ..................................................................... 60 Creating Payment Conditions....................................................................................... 61 Making Settings for Product Categories ....................................................................... 62 Confirmation and Invoice Verification ........................................................................... 62

Making Settings for Invoices ..................................................................................... 62 Configuration of BW for use with Enterprise Buyer ............................................................. 65

Self-Service Procurement SRM 3.0 13


Self-Service Procurement: Configuration Guide Purpose This document describes the configuration steps required to set up the self-service procurement scenario as illustrated in the scenario description graphic, within the system landscape that has already been installed using the corresponding SRM Master Guide for installation. It is based on new configuration and does not cover any changes relevant to existing implementations.

This guide describes a typical example of self-service procurement, but does not represent the entire functionality that SAP Enterprise Buyer offers for the procurement of indirect materials. The business scenario configuration guide should be used in connection with the application help for SAP Enterprise Buyer.

This document focuses on the process flow within the SRM components. Details of the flow in and between R/3 MM and R/3 FI/CO are not shown.

General Assumption: One Enterprise Buyer system is connected to a single SAP Materials Management system. The SAP MM backend system and the Enterprise Buyer system can be identified, based on data in business documents exchanged between supplier and buyer.

The settings described at the end of this guide with regard to the SAP Business Information Warehouse are OPTIONAL, you do not have to perform them if you are not using SAP BW for reporting.

Target Group The Business Scenario Configuration Guide: SRM Self-Service Procurement is intended to be used by both Basis and Application consultants.

It is a prerequisite that consultants have completed all the relevant training classes before starting to work with this guide.



The Self-Service Procurement scenario covers the following process steps:

Backend ERP SAP Enterprise Buyer Catalog BugsEye

Create Shopping Cart[1]

Search in catalog[2]

Select items & add to SC[3]

Display overview[4]

Account assignment ischecked

[5]

Display account assignment[6]

Order SC[7]

Check status of SC[8]

Approve SC by manager[9]

Requisition is created[11]

Check status of SC afterapproval

[10]

PO is created[12]



Create invoice (accountant)[15]

LO invoice posted[17]

FI doc. Created[18]

Payment notification sent[19]

Goods receipt posted

[14]

Create confirmation by SCrequester

[13]

Approve invoice bymanager

[16]

mySAP.com Solution and Business Scenario Documentation Landscape Purpose SAP has designed a special documentation landscape for implementing mySAP.com solutions and business scenarios. An overview of the individual documents follows. Always use the current documents in your implementation.

Current documents

Document Quick Link to the SAP Service Marketplace (service.sap.com)

Master Guide, Installation and Upgrade Guides installation → Installation and Upgrade Guides ibc

Business Scenario Description ibc

Business-Scenario Configuration Guide ibc

Implementation Guide (IMG) Note: in the SAP system, not in SAP service market place

SAP Library helpportal with all releases of a mySAP.com component

Note: available in the SAP system under Help → SAP Library



The following information supplements the individual documents:

Current supplementary information

Information Quick Link to the SAP Service Marketplace (service.sap.com)

SAP notes notes to the note search

instguides listed by installation and upgrade guide

Technical infrastructure (for example hardware sizing, platforms, network security)

ti

All quicklinks are listed in the SAP Service Marketplace under the service.sap.com/quicklinks.

Features The following documents are available for a mySAP.com solution.

Master Guide, Installation and Upgrade Guides These documents describe how you install or upgrade the system landscape required by a business scenario. The central initial access document for each mySAP.com solution is the Master Guide. It lists the mySAP.com application components and third-party applications required by each business scenario, and refers to their installation and upgrade guides. These are component installation guides, business scenario upgrade guides and component upgrade guides.

Business Scenario Description This document describes how a business scenario runs once all components have been installed and configured. It comprises a text (business scenario documentation) and a graphic (component view).

Business-Scenario Configuration Guide This document describes the settings you use to configure the mySAP.com application components and third-party applications required for a business scenario. This involves a system connection, middleware and data replication, and customizing and master data. The business scenario configuration guide specifies the configuration activity sequence, and their dependencies. Configuration activities can be IMG activities, SAP system transactions, organizational activities, etc.

Implementation Guide (IMG) This tools adjusts SAP systems to customer requirements. The IMG contains the IMG activities for all mySAP.com components, and general documentation. The structure is component oriented, without reference to a business scenario. The IMG is taken from the business scenario configuration guide and is business scenario-specific. The configuration guide identifies the positions in the IMG where you find the (general) IMG activity documentation, but it does not specify actual settings for the business scenario.

SAP Library This is the set of functional documentation of all mySAP.com components. It does not refer to business scenarios.



SAP Notes Definition This section lists all SAP Notes quoted in this Business Scenario Configuration Guide.

SAP Notes

Note Number Title Referenced in Section

100740 Set up pcANYWHERE connection in OSS

Making Settings for the Internet Transaction

609277 ITS Version for Enterprise Buyer 4.0

Making Settings for the Internet Transaction

656633 Search help requires dialog users

Defining Backend Systems

309734 CRM/EBP server: General analysis of initial load

Replication of Materials from R/3 Backend Systems

430980 CRM Server: Analysis in delta data exchange R/3 → CRM

Setting the Middleware Parameters

607541 Middleware consumer entry for EBP 4.0 in the R/3


519794 EBP: Replication of materials with purchasing view


614940 DataSources for the Enterprise Buyer

Configuration of BW for use with Enterprise Buyer

161570 User ALEREMOTE in the BW: Dialog user or system user


150315 BW-Authorizations for Remote-User in BW and OLTP


397208 BW: Authorizations for HR data extraction


336351 Maintaining the source system ID


352814 Loading data from Enterprise Buyer into BW


481283 Initializing the delta method in the EBP


401367 Calling the BW WebReports via the EBP launch pad


520131 Activation of SRM Roles for BW and SRM Decision




General Settings Purpose This section contains general information that you need to start the business scenario configuration.

Familiarize yourself with the documentation landscape for the mySAP.com solutions and business scenarios. mySAP.com Solution and Business Scenario Documentation Landscape [page 16] describes the types of documentation provided by SAP, and how to get its current versions.

Prerequisites • The system landscape is installed.

Using the mySAP.com solution master guides, and the mySAP.com component and business scenario installation and upgrade guides.

• You are familiar with the relevant SAP notes about installation, configuration and upgrade.

For more information, see SAP notes.

Procedure Perform the steps in these guidelines in the sequence in which they appear.

Aligning Units of Measurement, Currencies, and Exchanges Rates Use You have to make sure that the units of measure, currencies, and exchange rates in the SAP Enterprise Buyer system correspond to those in the backend system.

Procedure Activity Description For more information, see

Checking units of measurement

The contents of the Customizing table "Unit of measurement" must be identical in SAP Enterprise Buyer and in the backend system.

Path in the Implementation Guide (IMG):

SAP Web Application Server → General Settings → Check Units of Measurement

Aligning currencies and exchange rates

To align the currencies and exchange rates in the backend system with those in SAP Enterprise Buyer, run the reports BBP_GET_CURRENCY and BBP_GET_EXRATE whenever currencies and exchange rates are updated in the backend system.



Allocating ISO codes

You must also allocate the relevant ISO codes, in particular if you are connecting to catalogs.

Scheduling Reports

Scheduling Reports

Report Name Description For more information, see:

RSPPFPROCESS In order that your purchase orders are transferred to the vendors, schedule this report to run at regular intervals.

Do not schedule this report if, in the IMG activity: Define Actions for Purchase Order Output, you have selected Processing when saving document for the Action Profile. This setting is made under Action Definition on the tab card Action Settings, field Time of Processing.

Processing Purchase Orders in the documentation SAP Enterprise Buyer

Path in the IMG: Supplier Relationship Management →SRM Server → Cross-Application Basic Settings → Set Output Actions and Output Format → Define Actions for Purchase Order Output

BBP_GET_STATUS_2 This report updates shopping carts.

To ensure that information on the status of purchase requisitions, purchase orders, and reservations is up-to-date, schedule this report to run daily in the SAP Enterprise Buyer system.

Defining Update Intervals [page 21] and the report documentation

CLEAN_REQREQ_UP (and START_CLEANER)

Updating of documents (purchase requisitions, purchase orders, reservations) is executed asynchronously in the backend system. You can only process the shopping cart in the SAP Enterprise Buyer system further after the update has been carried out.



You schedule report CLEAN_REQREQ_UP to run periodically using transaction SA38.

If you previously used the report START_CLEANER, you can alternatively schedule this report using SA38.

BBPERS If you use Evaluated Receipt Settlement (ERS) for local purchase orders for which confirmations exist, you have to start BBPERS.

See Evaluated Receipt Settlement (ERS) in the documentation SAP Enterprise Buyer.

BBP_DELETE_LOCAL_ACCOUNT This report updates account assignment tables and deletes those account assignment objects that are no longer valid, that is when the expiry date has passed.

See also Making Settings for Account Assignment [page 60].

Setting the Control Parameters Set the following control parameters in Customizing:

• SPOOL_JOB_USER

• SPOOL_LEAD_INTERVAL

• SPOOL_MAX_RETRY

For information about these parameters, see the Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Technical Basic Settings → Set Control Parameters

See also: Defining Update Intervals [page 21]

Defining Update Intervals You cannot continue processing a requirement request in SAP Enterprise Buyer until the corresponding documents have been created in the backend system.

At intervals defined by you, the system checks whether the documents have been created. After they have been created, the requirement request is updated and can be processed further. For this reason, you schedule the report CLEAN_REQREQ_UP to run periodically using transaction SA38.

You should also schedule report BBP_GET_STATUS_2 (updating requirement coverage requests) to run daily in the Enterprise-Buyer-system, so that information on the status of purchase requisitions, purchase orders, and reservations is up-to-date. For more information, see the report documentation.



Starting Application Monitors Use You start the application monitors during the installation of your SAP Enterprise Buyer system. This will display any system error that may occur when running an SAP Enterprise Buyer application.

Procedure

Perform this step once when installing SAP Enterprise Buyer.

For more information, see the Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Start Application Monitors

Setting Up the SAP Internet Pricing Configurator Use For information on how to set up the SAP Internet Pricing Configurator (IPC), see section Installation Scenario with Enterprise Buyer in The IPC Installation Guide.

In certain cases, you can use the simplified pricing function as an alternative to the IPC. For more information see the SAP Implementation Guide under Supplier Relationship Management → SRM Server → Business Add-Ins for SRM Server (BAdIs) → Pricing → Switch On Simplified Pricing (Classic Scenario).

Configuration for Sending Internet Mails (SAPconnect)

Use Before you can send e-mails via the mail server, you need to have configured certain settings to ensure external communication with R/3 systems. For example, you need to have enabled the Internet (SMTP) communication method in R/3 before you can successfully carry out notification workflows in the SRM Server.

Procedure 1. Install RFC Destination

a. Transaction SM59



b. Create TCP/IP connections (connection type), for example, Sendmail_Q00

Connection Type T

Activation Type Start on Explicit Host

Program /mail/sap/out/mlunxsnd

Target Host mailsig.wdf.sap.corp

Save As IP Address

c. Gateway Options

Gateway Host mailsig.wdf.sap.corp

Gateway Service sapgw88

d. Test Connection

2. Maintain SAPconnect Information

a. Call Transaction SCOT: Nodes → Create

Node Mail

Description Internet Mail

b. Select Continue

c. Select RFC Node and then select Continue

RFC Destination Sendmail_Q00

d. Select Continue

e. Select Internet and then select Continue

Address Area *sap.com

f. Select Continue

g. Select Continue

h. Select Continue

Set Further Address Types N

i. Select Continue

j. Select Continue

k. Select Continue

l. Select Node is Ready for Use

m. Select Continue to complete creation of the SAPconnect node

Version 4.5B

Call transaction SCOT via Goto → Customizing → Communication Methods: Set Typ INT to SAPCONNECT

Or transaction SE16 to maintain the SXADDRTYPE table: ADDR_TYPE INT → METHOD SAPCONNECT

Additional Information

The SCOT data is client-dependent.



You can define who receives the e-mails:

• For example, if you enter *SAP.COM, all users of the domain sap.com can receive the e-mail.

• If you enter *EXCHANGE.SAP-AG.DE, e-mails can also be sent to D-users, for example [email protected]

• If you enter a full address, for example [email protected], only Matthew Le Tissier can receive e-mails.

3. Adjust User Data

a. Call SU01

b. Maintain the Internet mail addresses for the relevant users

4. Send a Test E-mail

a. Call SO01

b. Send a test e-mail to your own address

5. Start Send Process

a. Start manually: Transaction SCOT: Utilities → Start Send Process or Start automatically via batch job: Schedule via SM36

Job Name SAPCONNECT INTERNET MAIL

Program RSCONN01

Variant INT

Period Value For example: Every 15 minutes

b. The batch job can also be scheduled via the SCOT transaction: View → Jobs → Schedule Job.

Setting up Attachments Use You have to make the following settings if you want to use attachments in combination with your purchasing documents.

Procedure ...

1. To display attachments in your Internet browser, carry out transaction SICF and make one of the following settings in the HTTP Service Tree under <Virtual Host> → sap → ebp → docserver:

Enter a user in the log-on data.

Configure Single-Sign-On


mailto:[email protected]

mailto:[email protected]


See the path in the SAP menu: Architecture and Technology → System Administration → Administration → Network → HTTP Service Hierarchy Maintenance

2. For the Single-Sign-On configuration, do the following:

Carry out transaction SMICM (and use menu path Goto → Services) for the HTTP configuration of the application server

Make sure to use identical domain names for the SAP Web Application Server and the SAP Internet Transaction Server, for example, washost.<sap.corp>:4711/… and itshost.<sap.corp>:0815/…

Set the profile parameter login/create_sso2_ticket of your Enterprise-Buyer-system to value 2

Set the profile parameter login/accept_sso2_ticket of your Enterprise-Buyer-system to value 1

Following a system restart, carry out transaction SSO2 with the RFC destination NONE

System Connections Purpose This section contains information about connecting the systems in a mySAP.com system landscape.

This involves, e.g.:

• Defining logical systems and assigning clients in the Online Transaction Processing System (OLTP)

• Determining the systems, servers, clients, distribution models, etc. in the system in which the mySAP.com application component is installed

• Completing the configuration settings and performing other activities required for the interactions in a mySAP.com system landscape


Making Settings for the Internet Transaction Server Use To ensure high availability and high performance, we recommend that you install two ITS (Internet Transaction Server) servers. In each case, the WGate is linked via load balancing to all available AGates. If one AGate crashes, operation switches automatically to the remaining



AGates. To prevent failure of the WGate, you should use an external HTTP load balancer. For detailed information about installation, refer to the SAP@Web Installation Guide for Release 4.6D. For more information, see also the ITS Administration Guide.

We strongly recommend that you provide us with a pcANYWHERE connection to your ITS server. For information about how to do this, refer to SAP Note 100740.

Alternatively, you can use Microsoft Terminal Services Client.

Prerequisites Before installing the ITS, you have to install the SAP GUI for HTML (WebGUI) that is shipped with your ITS version.

Procedure

To make sure you use the latest ITS version, do not install the ITS shipped on the CD. Install the version recommended in SAP Note 609277.

...

1. Install the version of the ITS recommended in SAP Note 609277 (ITS for SAP Enterprise Buyer 4.0). This Note also contains other information about ITS-related topics. You will find the ITS documentation at http://www.saplabs.com/its.

a. Change the parameter maxframes to Hex 20 or Dec 32. You can do this in the following places:

In the registry in the path HKLM\software\sap\its\2.0\<your_virtual_ITS_instance>\programs\agate\maxframes

Via the ITS administration interface. Log on using ITSADMIN and choose < your_virtual_ITS_instance > → Configuration → Registry → Programs → Agate → maxframes.

2. Create a dialog user for global.srvc

a. If you do not want to define the ITS dialog user (login and password) in the ITS global service files, you have to define it in the following service files: bbpat03, bbpat04, and bbpmainnew. You maintain the login information using the ITS admin instance or SAP@Web Studio.

b. If you define the user using Notepad or transaction SE80, the password is not encrypted. Some companies may regard this as a security problem, since the user is a dialog user.

3. Using transaction SE80, define the client of the component system in the ~client parameter in the service files bbpstart, bbpvendor, bbpat3, bbpat04, and bbpmainnew. If the client is not defined in these service files, add parameter ~client=XXX to the SAP Enterprise Buyer start URL.

http://<hostname>.<domain_name>:1080/scripts/wgate/bbpstart/!?~language=<language>&~client=<client>

If you have not defined the client, you will not be able to log on. For more information see SAP Note 307782 Procedure fails during logon.

If the client is defined in the services files, it cannot be overwritten by the URL for security reasons.



4. If SAP Enterprise Buyer is not running in the workplace, we recommend that you set the parameter ~multiinstanceservices in the global service file global.srvc to 0.

5. If you are not using SAP Business Information Warehouse, set parameter ~mysapcomSSOnoITS 0 in the global service file global.srvc .

6. We recommend that you set the ~exiturl parameter as, for example, http://www.sap.com/. Do not use the bbpstart URL as this opens a new session each time and can block the ITS for other users.

For information about the start URL, see Starting SAP Enterprise Buyer (Start URL) [page 27].

Starting SAP Enterprise Buyer (Start URL) The start URL (Uniform Resource Locator) for the SAP Enterprise Buyer system is:

http://<host_name>.<domain_name>:<port>/scripts/wgate/bbpstart/!?~language=<language> whereby <language> = de or <language> = en

http://p39800.wdf.sap-ag.de:1080/scripts/wgate/bbpstart/!?language=de

Always enter the fully qualified domain name. It is not sufficient to specify just the server name and port or the IP address and port.

The first page is displayed in the relevant language.

Making Entries Needed for Generating Application URLs Use In order that the URLs for the various transactions such as BBPPU99 (Shop) can be generated correctly, you have to make some entries in table view TWPURLSVR.

Procedure ...

1. Using transaction SM30, call the TWPURLSVR in edit mode.

2. Make the entries given in the table below:

Column Entry

LogSystem Name of the SAP Enterprise Buyer logical system, for example AX4CLNT000

Web server Domain of the ITS server including the port, for example pgaec.wdf.sap-ag.de:1080

(Web server) Log HTTP or HTTPS, for example

SAP GUI for HTML ID (Web path) No entry required


http://www.sap.com/


GUI server Domain of the ITS server including the port, for example pgaec.wdf.sap-ag.de:1080

(GUI) Log HTTP or HTTPS, for example

KW server Domain of the ITS server including the port, for example pgaec.wdf.sap-ag.de:1080

(KW) Log HTTP or HTTPS, for example

D&R server No entry required

(D&R) Log No entry required

Defining the RFC Destination and Making ALE Settings Activity Description For more information, see:

Defining the RFC destination The SAP Enterprise Buyer system communicates with the backend system by means of RFC calls. Therefore, you have to define the RFC destination for your backend system and an RFC user with the maximum of authorizations.

As the user’s logon language from the Enterprise Buyer system is used, you do not have to enter a logon language for the backend system.

Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Technical Basic Settings → Define RFC Destinations

Assign RFC destinations dependent on scenario

In this activity, you assign existing RFC destinations to Enterprise Buyer scenarios. The assignment affects

• XML communication with the SAP Business Connector

• Connection of the SAP Document Converter to Enterprise Buyer


Supplier Relationship Management → SRM Server → Technical Basic Settings → Assign RFC Destinations Dependent on Scenario

Making ALE settings As the following Enterprise Buyer applications use the ALE mechanism, you also have to define the ALE settings:

• Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Technical



• Confirmation of materials

• Invoicing

• Financial Accounting posting for procurement cards

• Commitment posting from purchase orders

Basic Settings → ALE Settings (Logical System)

• ALE QuickStart in the SAP Library

Procedure Defining the RFC destinations:

1. Using transaction SU01 define users for the replication. You have to define a user in both the Enterprise Buyer system and in the R/3 backend system. If you have several backend systems, you have to define a user in each of these systems.

2. Log on to the Enterprise Buyer system.

3. Using transaction SM59, define an RFC destination for the R/3 backend System. If you have more than one R/3 backend system, define an RFC destination for each of these systems.

4. Log on to your R/3 backend system. (If you have several R/3 backend systems, you have to log on to each of them in turn.)

5. Using transaction SM59, define an RFC destination for the Enterprise Buyer system. If you have several R/3 backend systems, we recommend that you give the RFC destination for the Enterprise Buyer system the same name in all your R/3 backend systems.

Testing an RFC connection: ...

1. Log on to the Enterprise Buyer system.

2. Call transaction SM59.

3. Under RFC destinations → R/3 connections double-click on the entry for your R/3 backend system.

4. Choose Test connection.

5. If the test was unsuccessful, start by checking the entries under Technical settings.

6. Choose Remote logon. This should cause a window to be opened in the R/3 System. If this does not happen, check the logon data to make sure that the correct user and password were entered. In addition, check the authorization level of the user in the R/3 System. You can also do this by choosing Test → Authorization.

7. If remote logon was successful, you are now logged on to the R/3 System. In this system, call SM59 and, under RFC destinations → R/3 connections, double-click on the entry for the Enterprise Buyer system. Here too, test the connection and try out remote login as described in the previous steps.

Result If a window is opened in the Enterprise Buyer system, the connection is correct for replication. If you are unable to establish a connection, there are a number of possible error causes:

• The entry for the system under Technical settings (transaction SM59) is incorrect

• The user or password was entered incorrectly

• The specified user does not have the required level of authorization



Defining Backend Systems Use This section describes the settings you must make to connect a backend system to your SAP Enterprise Buyer system.

Activity Prerequisites See also:

You define the backend system(s) that you work with.

Furthermore, you define how FI data is validated.

You define a second RFC connection for search help in the backend system (e.g. for account assignment).

• In the step Assign RFC Destination, you have specified the RFC destinations for your systems.

• In the step ALE Settings (Logical System), you have specified the logical system for your systems.

• You have created a second RFC connection for the same backend system.

Note: The user must be a system or dialog user.

Path in the Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Technical Basic Settings → Define Backend Systems

For further information (e.g. authorization) see SAP Note 656633, Search help requires dialog users.

You define the backend system for a product category.

(You specify whether purchase orders and their subsequent documents; confirmations, goods receipts/service entry sheets, and invoices are to be created locally in SAP Enterprise Buyer or in the backend system.)

• You have replicated/created the product categories.

• You have already specified that you work with more than one backend system. Here you specify the backend system that the documents are posted in, depending on the product category.

Path in the Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Technical Basic Settings → Define Backend System for Product Category

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)



Installing the SAP Integrated Catalog with SAPinst Use This procedure tells you how to install the SAP Integrated Catalog with the installation tool SAPinst.

Prerequisites You have installed SAPinst (see Running SAPinst on Windows [Extern] or Running SAPinst on UNIX [Extern]).

Procedure ...

1. To start the installation with SAPinst choose Start -> Programs -> <menu_entry> -> SAPinst server with GUI.

2. The SAPinst GUI starts and the Welcome screen is displayed.

3. Choose Installation of SAP Integrated Catalog.

4. Click Next.

5. Accept the license agreement.

Installing the J2EE Engine ...

1. Select New or Existing SAP J2EE Engine.

If you selected New SAP J2EE Engine, enter the following data:

a. Enter a system name (containing 4-20 characters), e.g. MySRM.

b. Enter a two-digit unique instance number, e.g. 00.

c. Windows only: Choose the installation drive.

d. Confirm or adapt the maximum memory size. It is recommended that you confirm the default value (128 MB).

If you selected Existing SAP J2EE Engine, choose one of the detected SAP J2EE Engines that you want to install.

2. Click Next.

Installing the Software Delivery Manager (SDM)

The SDM is automatically installed.

Connecting to the BugsEye Catalog ...

1. Enter the URL of the server (including the port, if relevant), on which the BugsEye catalog is running, for example http://pmwdf078:80.

2. Enter the ID of the catalog that you want to use, for example /servlet/BugsEyeSAP.

3. Enter the URL of the server, on which the pictures of the products are located, for example http//pmwdf078/requisite/sap/images. If you leave this field blank, the catalog server URL will be used.

4. Enter a user name that is to be used to log on to the BugsEye catalog, e.g. author.

5. Enter a password for the specified user.



6. Confirm the password.

7. Click Next.

Defining the Catalog UI Information ...

1. Enter the default language for the SAP Integrated Catalog screens. Use the following format: en for English, de for German, etc.

2. Specify the start category that you want to use with the BugsEye catalog, for example A or C. If you do not specify any category, all categories will be displayed upon entering the catalog.

3. Click Next.

Entering Logon Information for the SAP Enterprise Buyer System ...

1. Enter your client number (three digits), your user name, your password and confirm your password for the Enterprise Buyer system.

2. You can choose to connect to either a specific Enterprise Buyer host server or to log on via a load balancing group.

If you want to connect to a specific Enterprise Buyer host server, enter the following data:

a. Enter the SAP system number.

b. Enter the name of the Enterprise Buyer host server.

c.

If you want to log on via a load balancing group, select Use Logon Load Balancing for EBP Logon.

d. Enter the SAP system ID.

e. Enter the SAP system logon group.

3. Click Next. A screen is displayed summarizing all of the data you have entered.

Starting the Installation Check the displayed data and click Start to start the installation. The installation progress is displayed.

After the installation has been completed successfully, start the catalog from within your browser.

Please be aware that the URL’s parameters are case sensitive, i.e. CONTENT_LANGUAGE must be in upper case.

Syntax example: http://pmwdf078:8080/ebp/catalog/logonOCI.do?CONTENT_LANGUAGE=en_US

http://[hostname of SAP J2EE Engine]:[SAP J2EE Engine port no.] /ebp/catalog/logonOCI.do?CONTENT_LANGUAGE=[locale supported by the BugsEye catalog]



Result You have installed the BugsEye catalog as an integrated catalog within SAP Enterprise Buyer.

Configuring SAP Integrated Catalog

RequisiteCatalogServer

EBP R/3Server

IntegratedCatalogServer

optional:External Catalog via HTTP OCI-RequestThis method can be used supplementaryto the integrated catalog. Accroding mappingof attributes must be set up in the RequsiteCatalog

Integrated CatalogRFC - Connection to

request contracts

Integrated CatalogConfiguration of Cataloghost and attribute mappingis required (comparecatalog-site-config.xml )

OCI transfer of productsfrom Int Catalog to EBP

( compare fileAddToOCIBasket.jsp )

To make the Integrated Catalog available, both a host and the mapping of attributes for the Requsite catalog must be set up in the file catalog-site-config.xml. The host is set up during the installation procedure. All information is specified both in catalog-site-config.xml file and in web.xml file.

The RFC connection from the Integrated Catalog to the R/3 system is set up during the installation procedure as well. The corresponding setting is saved in the web.xml file of the Integrated Catalog application.



Checking the Server Configuration Procedure The connection between the Integrated Catalog on SAPJ2EE and the Requisite catalog is configured during the installation process.

For information on the installation process of the SAP Integrated Catalog, see the Installation Guide: SAP Integrated Catalog 3.0 at SAP Service Marketplace (service.sap.com/instguides).

To view and check this configuration, please see the following file ../j2ee\j2ee_20\cluster\server\services\servlet_jsp\work\jspTemp\ebp\root\WEB-INF\cfg\catalog-site-config.xml

<Server ID="CatalogServer" type="requisite"> <ServerConfig xmlns:requisite="http:\\www.requisite.com"> <requisite:host>myRequisite.sap.com</requisite:host> <requisite:port>52000</requisite:port> </ServerConfig> <Detail ID="name"> <Value xml:lang="en">Requisite catalog</Value> <Value xml:lang="de">Requisite Katalog</Value> </Detail> <Detail ID="description"> <Value xml:lang="en">Requisite catalog</Value> <Value xml:lang="de">Requisite Katalog</Value> </Detail> <Catalog ID="/BugsEye/BugsEyeSAP"> <Detail ID="name"> <Value xml:lang="en">Simple test catalog</Value> <Value xml:lang="de">Einfacher Testkatalog.</Value> </Detail> <Detail ID="description"> <Value xml:lang="en">Simple test catalog containing only one category</Value> <Value xml:lang="de">Einfacher Testkatalog mit nur einer Kategorie.</Value> </Detail> </Catalog> </Server>



Mapping Parameters Use The Integrated Catalog owns its own attributes that must be mapped to the Requisite catalog. There is no standard setting because all Requisite common attributes vary depending on the namespace given by the purchasing organisation.

Procedure Set up the mapping in the following file

../j2ee\j2ee_20\cluster\server\services\servlet_jsp\work\jspTemp\ebp\root\WEB-INF\cfg\catalog-site-config.xml

The following table explains all key IDs of the integrated catalog that need to be mapped to common attributes in the Requisite catalog.

Integrated Catalog

Key ID Corresponding OCI-field Key Description

Example for Requsite Attribute

product NEW_ITEM-EXT_PRODUCT_ID

This key has been inherited from the SAP sales scenario. To prevent wrong functionality a mapping to the catalogs Global ID should be executed. Global ID

productId NEW_ITEM-EXT_PRODUCT_ID

This key has been inherited from the SAP sales scenario. To prevent wrong functionality a mapping to the catalogs Global ID should be executed. Global ID

productDescription NEW_ITEM-DESCRIPTION

The description of the item to be ordered. Description

productLongDescription NEW_ITEM-LONGTEXT_n:132

Longtext description of an item Long Description

price NEW_ITEM-PRICE Price of the item in the catalog. Price

currency NEW_ITEM-CURRENCY

Must be the ISO code for the currency. Currency

unitOfMeasurement NEW_ITEM-UNIT

Unit of measure of the item. Must be the standard ISO code. UOM

priceUnit NEW_ITEM-PRICEUNIT

The number of units to be purchased at the given price. Price Unit

productCategory NEW_ITEM-MATGROUP

The SAP product (material) group. Mat Group

productTypeIsService NEW_ITEM-SERVICE

A flag which indicates if the product refers to a service or goods. Service



unspsc NEW_ITEM-EXT_CATEGORY_ID

Unique key for a category ID. To be used if you have performed a schema import and are using external product categories or if you have imported external product categories for mapping purposes. eclass

schemaType NEW_ITEM-EXT_SCHEMA_TYPE

This field contains a schema name, as it appears in the procurement system. ECLASS4.0

vendorId NEW_ITEM-VENDOR

If the product is purchased through a multi-supplier catalog, this field contains the business partner number in the buyer system. Sup Name

vendorMat NEW_ITEM-VENDORMAT

The vendor product part number Sup Part Num

manufactId NEW_ITEM-MANUFACT

ID of the manufacturer in the buyer system. Mfg Name

manufactMat NEW_ITEM-MANUFACTMAT

The manufacturer's product part number. Mfg Part Num

MaterialNo NEW_ITEM-MATNR The SAP product master in the buyer system. Material Number

GlobalId NEW_ITEM-EXT_PRODUCT_ID

Internal database key to identify a product in the catalog. Global ID

leadTime NEW_ITEM-LEADTIME

Number of days from today until the product will be delivered. Lead Time

Configuring Customer Fields

Procedure The OCI specification supports several parameters, which are not used in the standard delivered version of the integrated catalog. Nevertheless, these parameters can be set up in file AddToOCIBasket.jsp like the following example illustrates:

<INPUT type="hidden" name="NEW_ITEM-CUST_FIELD1[<%= i %>]" value="<%= item.getAttribute("TAX") %>">

In this example the buyer organisation wants to transfer the value for tax from the catalog to the SAP Enterprise Buyer system. In this case, the customer field 1 is mapped to an attribute in the Requisite catalog named “TAX”.



This mapping is not restricted to OCI parameters, rather different customer specific mappings can be applied at this point.

Checking the BugsEye Configuration

Procedure Check the DB table bugseye_config in the BugsEye catalog.

The following commands must be in the DB table:

Field Content CONFIG_NAME sapcomb

NAME bugq

Entry 1

VALUE com.requisite.bugq.BugQ

Field Content CONFIG_NAME sapcomb

NAME BugQLoadClass

Entry 2

VALUE com.requisite.bugq.BugLoad

If these entries are not present, you may create them using SQL. The following is an example for Oracle Databases:

DELETE FROM bugseye_config WHERE NAME LIKE 'bugq'; DELETE FROM bugseye_config WHERE NAME LIKE 'BugQLoadClass'; INSERT INTO bugseye_config (CONFIG_NAME, NAME, VALUE) VALUES ('sapcomb','bugq','com.requisite.bugq.BugQ'); INSERT INTO bugseye_config (CONFIG_NAME, NAME, VALUE) VALUES ('sapcomb','BugQLoadClass','com.requisite.bugq.BugLoad'); COMMIT;



Defining the Internal Call Structure in SAP Enterprise Buyer Use You need to maintain the internal call structure in the SAP Enterprise Buyer system.

Procedure ...

1. In the SAP Implementation Guide (IMG), go to Supplier Relationship Management → SRM Server → Master Data → Define External Web Services.

Please see the corresponding documentation in the Implementation Guide.

2. Choose Internal Call Structure and New Entries.

3. To define the internal call structure of the SAP Integrated Catalog, make the following entries:

Mandatory Parameters

Name Value Type

http://<HTTP server>:<port>/<your_entry>/catalog/logonOCI.do

URL

username guest Fixed value

password guest Fixed value

LANGUAGE SY-LANGU SAP Field

4. Add the parameter CONTENT_LANGUAGE , if you have different content languages activated in your BugsEye catalog.

Optional Parameter

Name Value Type

CONTENT_LANGUAGE en-US Fixed Value

For additional information regarding content languages in BugsEye, see the documentation located on the Requisite Technology BugsEye™ CD-ROM.

Do not include an entry for ~caller.

Do not run the SAP Integrated Catalog in an external window.

5. Save your entries.



Displaying Contract Data Use You can display details of local contracts when transferring products from the SAP Integrated Catalog. All valid contracts for the chosen product are displayed. The details shown include:

• Contract number

• Item number

• Price

• Vendor

If more than one contract exists for a product, you can navigate from the link Multiple contracts to display a list of corresponding contracts.

Prerequisites You have

• Defined contracts

For further information, please refer to the SAP help portal (help.sap.com) under mySAP Supplier Relationship Management → mySAP SRM E-Procurement → SAP Enterprise Buyer → Procurement Process → Strategic Procurement → Purchase Contracts

• Defined source determination

For further information, please refer to the SAP help portal (help.sap.com) under mySAP Supplier Relationship Management → mySAP SRM E-Procurement → SAP Enterprise Buyer → Procurement Process → Strategic Procurement → Sourcing

Procedure If you wish to have details of local contracts displayed, you need to perform the following activity in the SAP Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Master Data → Define External Web Services.

...

1. On the initial screen, select the integrated catalog.

2. Click the Detail icon. The detail screen is displayed.

3. Under Additional Functions in EBP set flag Add contract data in integrated catalog.

Contract data will now be displayed when transferring products from the integrated catalog.



Displaying Multiple Contract Data Use If more than one contract exists for a product, you can choose to have a complete list of corresponding contracts displayed.

Procedure ...

1. Call up Business Add-In (BadI) Transfer Additional Parameters (BBP_CAT_CALL_ENRICH) .

2. Find the parameter EBP_CAT_SOS.

By default this parameter is set to ‚S‘ (single). Only one contract is displayed at a time.

3. Change the parameter to ‚M‘ (multiple). A complete list of all existing contracts is automatically displayed when transferring products from the integrated catalog.

4. Save your changes.

Data replication Purpose This section contains information about replicating customizing, master data and transaction data.

This involves, e.g.:

• Activities to initially transfer data from the Online Transaction Processing System (OLTP) into the Online Analytical Processing System (OLAP)

• Automatic replication activities

• Manual replication activities, for example because automatic replication is not possible


Replication of Materials from R/3 Backend Systems Purpose You want to replicate materials or service masters from an R/3 backend system or multiple R/3 backend systems. This documentation describes this process. In addition to describing the various procedures involved, it provides information about how to proceed if problems arise during the replication process.

For information about the tools available for monitoring the download of the various objects, see Downloading Customizing Objects [page 43], Downloading Business Objects [page 44], and SAP Note 309734.



Process Flow You have to perform the following steps in the order given: ...

1. Defining the RFC Destination [page 28]

2. Performing Customizing Steps in Enterprise Buyer [page 41]

3. Setting the Middleware Parameters [page 42]

4. Downloading Customizing Objects [page 43]

5. Downloading Business Objects [page 44]

Result The replication of the materials is complete.

For more information, see:

• SAP Note 309734: CRM/BBP: General analysis in the initial load

Customizing Material Replication in Enterprise Buyer Use Before replicating SAP Enterprise Buyer Customizing data and master data from your R/3 backend system(s), you have to perform some Customizing activities in the Enterprise Buyer system.

Prerequisites You have completed the following steps:

• Defining the RFC Destination and Logical System [page 28]

• You have run report BBP_PRODUCT_SETTINGS_MW, see IMG path Supplier Relationship Management → SRM Server → Master Data → Products → Deactivate/Reactivate CRM-Specific Data in EBP System

Procedure ...

1. Perform the Customizing steps for units of measure, currencies, and countries. Make sure that the associated ISO codes are entered in full and that there are no ambiguities (for example, two units of measure with the same ISO code). If you have added your own entries for currencies, units of measure or countries in your R/3 backend system(s), you have to make corresponding entries in the Enterprise Buyer system.

Path in the Implementation Guide (IMG): ...

a. Countries: SAP Web Application Server → General Settings → Set Countries → Define Countries

b. Currencies: SAP Web Application Server → General Settings → Currencies → Check Currency Codes

c. Units of Measure: SAP Web Application Server → General Settings → Check Units of Measurement



Read the documentation for all the fields of the following Customizing transaction with great care. In particular, the decision as to whether you opt for lexicographical or non-lexicographical storage of product IDs is important.

2. Set the output format and storage form for the product IDs. We recommend that you define a length of 18 positions, analogous to the length of the R/3 material number.

Path in the Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Master Data → Products → Define Output Format and Storage Form of Product IDs

Enter only templates in the field Template ID. Do not use this field to enter descriptive texts.

Setting the Middleware Parameters Use You specify:

• The system from which the data is to be replicated

• The data to be replicated (using filters)

Prerequisites The role SAPCRM_MENUE is assigned to your user. (You require this role to display the Middleware menu.)

You have completed the following:

• Defining the RFC Destination [page 28]

• Customizing Material Replication in Enterprise Buyer [page 41]

Procedure Specifying the R/3 backend systems for Middleware Download To specify the R/3 backend systems in the middleware parameters: ...

1. Call transaction SMOEAC (menu path Middleware → Administration → Administration Console).

2. Select object type Sites.

3. Choose Object → Create.

4. Enter the Name, Description, and Type (R/3).

5. To enter the RFC destination of the R/3 backend system, choose Site attributes.

6. Repeat steps 2 to 5 for all further R/3 backend systems.

Making special settings in the R/3 backend system To specify the SAP Enterprise Buyer system (this is the consumer of the R/3 backend system) for the delta download: ...



1. Log on to the R/3 backend system.

2. Call transaction SM30.

3. Verify and, if necessary, change or insert entries in tables CRMCONSUM and CRMRFCPAR as described in SAP Note 430980.

4. To ensure correct filtering of the object MATERIAL, you must insert an entry into table CRMPAROLTP (using transaction SM30):

Parameter name CRM_FILTERING_ACTIVE

Parameter name 2 MATERIAL

Parameter name 3

User CRM

Parval1 X

Parval2

If, in the previous step, you defined an additional consumer or a consumer other than CRM, you must create a corresponding entry per consumer in the table. You enter each separate consumer in the field USER.

Since this table entry cannot be used if there is a connected CRM system with Release 2.0B or 2.0C, this entry cannot be shipped as standard.

See also SAP Note 607541, Middleware-consumer entry for EBP 4.0 in the OLTP.

SAP Note 519794 , EBP: Replication of Materials exclusively for Purchasing.

Downloading Customizing Objects Use After this procedure has been completed, the Customizing for material number conversion, material types, material groups, and service category are available in the SAP Enterprise Buyer system.




• Setting the Middleware Parameters [page 42]

• You have run report BBP_PRODUCT_SETTINGS_MW, see IMG path Supplier Relationship Management → SRM Server → Master Data → Products → Deactivate/Reactivate CRM-Specific Data in EBP System

Procedure Downloading the Customizing Objects ...

1. Call transaction R3AS.



2. Using the multiple selection dialog box for Load Object, choose the Customizing objects:

DNL_CUST_BASIS3 (units of measure, dimensions, and currencies)

DNL_CUST_PROD0 (product categories)

DNL_CUST_PROD1 (product categories)

DNL_CUST_SRVMAS (service categories)

3. Enter the Source Site (that is, the R/3 backend system) and Destination Site (Enterprise Buyer system), which was defined using the administrator console, transaction SMOEAC.

4. To start the download, choose Execute.

Checking the Download is Complete ...

1. To start the Download Monitor, call transaction R3AM1. If all the traffic lights are green, the download was successful. If a traffic light is yellow, select Refresh and observe whether the block number increases. If so, the download is still in progress. If not continue with the next step.

2. In the backend R/3 System, check the outbound queue using transaction SMQ1. For Queue name, enter the correct queue name and choose Execute to display the queue. If the queue is locked, try to release the lock on it and to activate it. If the queue disappears after you select Refresh, the download process has proceeded further.

3. Using transaction SMQ2, check the inbound queue in the Enterprise Buyer system and activate it if necessary.

4. Using the transactions SMWP and SMW01, you can get detailed information about the progress of the download. You start these transactions in the Enterprise Buyer system. Look out for any error messages and correct the errors wherever possible. After calling transaction SMW01, proceed as follows to get information about the download:

...

a. Choose Execute.

b. Select a step and choose BDoc display.

c. Select a line and choose Errors.

5. After eliminating any errors, call transaction SMQ2 and select Queue to activate the queue.

6. To check whether the material types, material groups, and service categories have arrived in the Enterprise Buyer system, call transaction COMM_HIERARCHY. You should see all the required data. If not, check your filter settings again and look at the data in the R/3 backend system. Check whether the tables assigned to the objects contain the necessary data in the R/3 backend system.

Downloading Business Objects Use You use this procedure to perform the initial download of business objects from your R/3 backend system or systems.

You can optionally define filters to restrict the variety of materials to be replicated.



Specify the filter conditions appropriately for the database format of the corresponding fields in the backend system. In particular, material or service numbers must have 18 positions and include leading zeros (unless you specified the lexicographical storage format for material numbers).

After the download, you can check that the business objects have been downloaded correctly. A frequent cause of error is missing units of measure in the SAP Enterprise Buyer system.




• Setting the Middleware Parameters [page 42]

• Downloading Customizing Objects [page 43]

Procedure Downloading Business Objects (Initial Download) ...

1. Log on to your Enterprise Buyer system.

2. If you wish to define filters to restrict the selection of materials to be replicated, choose Middleware → R/3 Data Exchange → Initial Download → Object Management → Business Objects.

3. In change mode, click (filter settings) on the line containing the business object MATERIAL. The Object filter settings screen is displayed.

4. Enter the values for the tables and fields displayed in the input help. Only those materials matching the set values will be replicated. For Source Site Name, choose the name of the corresponding R/3 backend system and select filter type S.

5. To start the download for materials, and the service master (if required), call transaction R3AS and specify object MATERIAL, or object SERVICE_MASTER as appropriate and the Source Site (R/3 backend system) and Destination Site (Enterprise Buyer system).

Checking the Initial Download 1. To start the Download Monitor, call transaction R3AM1. If all the traffic lights are green,

the download was successful. If a traffic light is yellow, select Refresh and observe whether the block number increases. If so, the download is still in progress. If not continue with the next step.

2. In the backend R/3 System, check the outbound queue using transaction SMQ1. For Queue name, enter the correct queue name and choose Execute to display the queue. If the queue is locked, try to release the lock on it and to activate it. If the queue disappears after you select Refresh, the download process has proceeded further.

3. Using transaction SMQ2, check the inbound queue in the Enterprise Buyer system and activate it if necessary.

4. Using the transactions SMWP and SMW01, you can get detailed information about the progress of the download. You start these transactions in the Enterprise Buyer system. Look out for any error messages and correct the errors wherever possible. After calling transaction SMW01, proceed as follows to get information about the download:

a. Choose Execute.

b. Select a line and choose Errors.



5. After eliminating any errors, call transaction SMQ2 and select Queue to activate the queue.

Result Required materials and service masters are available in the SAP Enterprise Buyer system. To check them, use transaction COMMPR01 (SAPCRM_MENUE: Master Data → Maintain Products).

Business Customizing Purpose This section contains information about the Customizing settings in each system. Business Customizing adjusts the company-neutral delivered functionality to the specific requirements of the company.

This involves:

• Organizational Unit Customizing

• Master Data Customizing

• Process Customizing


Organization Configuration Purpose As a prerequisite for the configuration of the business scenario, certain data must already have been entered, for example, the organizational structure and master data. This is described in the following section.

Regenerating Role Profiles Use You have to regenerate the authorizations for each role that you intend to use. This ensures that the profiles belonging to these roles are assigned all the required authorizations.

Path in the Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Roles → Define Roles



Procedure ...

1. Enter the name of the role you want to generate the profile for.

2. Choose Display.

3. Choose Authorizations.

4. Choose Display Authorization data.

5. Choose Generate.

6. Repeat steps 1 to 5 for each role required.

You can also generate multiple profiles in Role Maintenance, PFCG:

If you copy one of the roles delivered by SAP, you need to maintain attribute access rights by role.

See Path in the Implementation Guide (IMG) of Supplier Relationship Management: SRM Server → Cross-Application Basic Settings → Roles → Maintain Attribute Access Rights by Role.

For further information refer to SAP Note 644124. ...

1. Choose Utilities → Mass generation

2. Select Also roles to be adjusted

3. Enter SAP_EC_BBP*

4. Choose

Creating the Organizational Plan

Apart from the very first user, create all other users using the Web applications, not transaction SU01.

...

1. Using transaction SU01, create an R/3 user with profile SAP_ALL. Assign this user the administrator role SAP_BBP_STAL_ADMINISTRATOR.

2. As this administrator, create your organizational plan.

At the very least, you must create a root node for the organizational plan. The remaining organizational units can be created by the employees and managers themselves using the self-service Web application. We recommend, however, that you define your organizational plan to at least departmental level, specify which organizational units are purchasing organizations and purchasing groups, and create the user master records for the managers of the departments using Web application Manage Users:

...

a. Create the root organizational unit. Remember to enter an address for the organizational unit.

Menu path in the SAP Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Organizational Management → Create Organizational Plan



You start to create the organizational plan using the Customizing activity Create Organizational Plan (transaction PPOCA_BBP). After leaving this activity, you make any changes to the organizational plan using the activity Change Organizational Plan (transaction PPOMA_BBP).

b. Create the remaining organizational units.

If you define a company, purchasing organization, or purchasing group you have to select the corresponding indicator on the tab card Function.

You must enter an address for each organizational unit. If you fail to do so, the self-service Web transaction for creating users will not work!

3. Using the Web application Manage Users, create user master records for the departmental managers (users with the role SAP_ BBP_STAL_MANAGER) and assign the managers to the relevant organizational units. Managers have three functions within the organizational plan:

They assign users to organizational units.

They either approve new users or specify a default role that renders approval unnecessary. If a default role is assigned, the approval process can be deactivated.

They maintain important user attributes.

For information about activating or deactivating the approval process, refer to the SAP Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Master Data → Create Users → Set Approval Indicator

Example of how the organizational plan might look after the administrator has finished creating the organizational units for the various departments and the user master records for the managers of these departments:



Root organizational unit

Vendor (root node)

Purchasinggroup 1

Backend purchasing organization

Purchasinggroup 3

Purchasinggroup 2

Administrator

Manager

Manager

Manager

Manager

Company

Department 1 Purchasing department

Local purchasing organization

4. In the same way, create an organizational root node for your vendors.

5. After creating your organizational plan, you can run a report to check that a business partner has been defined for each node in the organizational structure.

Menu path in the SAP Implementation Guide:

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Organizational Management → Integration Business Partner – Organizational Management → Create Business Partner Initially

Select All org units and deselect Only compare existing BP.

Choose Execute.

6. After creating your organizational plan, you can run a report to check that the attributes have been defined correctly in respect to the individual applications allowed for the users: Transaction BBP_ATTR_CHECK or report BBP_CHECK_CONSISTENCY.

Making Settings for Create Internal User Prerequisites You have defined the root organizational unit of the organizational plan. See Creating the Organizational Plan [page 47].

Procedure

• If the superior is to approve the user master record, activate the approval process.

Menu path in the SAP Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Master Data → Create Users → Set Approval Indicator



• In addition, make sure that a manager is assigned to each relevant organizational unit in the organizational plan. (You create the first manager using the Web application Manage User Data.)

Maintaining the User Attributes Prerequisites You must have created the root node of the organizational structure.

Procedure We recommend that system administrators specify values for the main user attributes using the transaction PPOMA_BBP, tab card Attributes. For most attributes they can do this using the Web application Change Attributes. Important attributes include:

• Account assignment: KNT and related account assignment objects

• Product categories: The product responsibilities have to be set on the tab card Extended Attributes (attribute PRCAT)

• Systems: ACS, SYS

• Catalog IDs: CAT

• Document types: BSA

• Role: ROLE. Before managers can approve the creation of new user master records, they must have been assigned the manager role SAP_BBP_STAL_MANAGER.

• Procurement attributes: The procurement attributes define the function (company, purchasing organization, or purchasing group) and the responsibilities of an organizational unit (attributes PURCH_GRP, PURCH_GRPX, PURCH_ORG, PURCH_ORGX, RESP_PGRP, RESP_PRCAT in earlier Enterprise Buyer releases).

Procurement attributes have to be set in the Enterprise-Buyer-system in transaction PPOMA_BBP on the tab cards Function and Responsibility.

• Currency: CUR

• Plant: WRK

• Ship-to address: ADDR_SHIPT

For information about maintaining the attributes for the purchasing organization, see Modeling the Purchasing Organization in the Organizational Plan in Enterprise Buyer. For a complete list of Enterprise Buyer attributes, see Attributes for the Enterprise Buyer Scenario in Enterprise Buyer.

See also:

Maintaining User Attributes in the SAP Enterprise Buyer documentation.



Managing Business Partner Addresses Procedure Activity Description For more information, see:

Defining address types You must have specified the 6 address types shipped with SAP Enterprise Buyer, such as goods recipient (GOODS_REC), to be used in certain business processes.

Menu path in the SAP Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Master Data → Business Partner → Manage Address Types → Define Address Types

See also: Editing Addresses in the SAP Enterprise Buyer documentation.

Assigning transactions to address types

You must have assigned predefined transactions to address types you created. There is a recommended set of assignments, including, for example, the assignment of transaction Ship Goods to the Ship-To address.


Supplier Relationship Management → SRM Server → Master Data → Business Partner → Manage Address Types → Assign Transaction to Address Type

Making Settings for Locations and External Business Partners Use This section describes the settings you need to make for locations and external business partners.


The purchaser or system administrator responsible must have been defined as the processor responsible in the SAP Business Workflow. See the documentation Approval Workflows for Creating External Users in Enterprise Buyer

Define business partner groupings and assigned number ranges You must ensure that at least one standard grouping has been defined and that the standard indicator has been set for external number assignment. See the SAP Implementation Guide under Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings → Define Groupings and Assign Number Ranges.



Define number ranges for address management See the SAP Implementation Guide under Basis → Basis Services → Address Management → Maintain Address and Person Number Range

Define partner functions You can enter the texts you want to use for the partner function for a partner function type. These texts are displayed in the relevant documents for a business transaction. See the SAP Implementation Guide SRM Server →Cross-Application Basic Settings → Define Partner Functions

External Locations You can use the following three routines to download locations from the backend system and store them as business partners in SAP Enterprise Buyer.

BBP_LOCATIONS_GET_ALL Gets all the location numbers from each backend system that is connected.

BBP_LOCATIONS_GET_FROM_SYSTEM Gets all the location numbers from one particular backend system.

BBP_LOCATIONS_GET_SELECTED Gets selected locations

Previously, locations were not given business partner numbers in SAP Enterprise Buyer. If you are configuring an upgrade, you can select from routines BBP_LOCATIONS_GET_FROM_SYSTEM and BBP_LOCATIONS_GET_SELECTED whether you wish to check that the following conversions have been made.

• Conversion of user favorites

• Conversion of user attributes

• Conversion of old documents

The routine BBP_LOCATIONS_GET_ALL checks these automatically.

Once you have run the routines, the location data is available in the SAP Enterprise Buyer system. Table BBP_LOCMAP contains the mapping information, in other words, which business partner number corresponds to which location in which backend system.

External Business Partners

Procedure

You must first create the organizational plan with at least one organizational unit to which the external business partners can be assigned (vendor root node). For more information, see Creating the Organizational Plan [page 47]

...

1. Replicating or creating the vendor master records The vendor master records must exist in the system. They have to be replicated from the backend system and assigned to at least one purchasing organization. Alternatively, they can be created using the application Managing External Business Partners. For more information, see Business Partner in the documentation Enterprise



Buyer Managing External Business Partners in the SAP Enterprise Buyer documentation.

2. Check business partners in the organizational plan. Make sure that a business partner has been defined for each node in the organizational structure. To do this, complete the following in the SAP Implementation Guide under SRM Server → Cross-Application Basic Settings→ Organizational Management → Integration Business Partner-Organizational Management → Create Business Partner Initially:

...

a. Select All org units and deselect Only compare existing BP.

b. Choose Execute.

c. By looking at the table, you will be able to see the organizational units for which business partners already exist. Create the missing business partners and enter the address data.

3. Schedule updating of business partner addresses To schedule the automatic checking and updating of business partner addresses from the organizational plan, see the SAP Implementation Guide under SRM Server → Cross-Application Basic Settings → Organizational Management → Integration Business Partner-Organizational Management → Schedule Periodic Comparison.

Process Configuration Purpose The configuration necessary for the business scenario illustrated in the diagram (see Self-Service Procurement [page 14] is described in this section.

Setting Up SAP Business Workflow Use You have to perform some standard Customizing for SAP Business Workflow.


Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → SAP Business Workflow → Maintain Standard Settings for SAP Business Workflow

Prerequisites • You have created your organizational structure. We recommend that you map your

enterprise structure at least at departmental level. See Creating the Organizational Plan [page 47].

• Before you can assign processors to standard tasks, you must have created the relevant users or regenerated the roles, as appropriate. See Regenerating Role Profiles [page 46].

Procedure ...



1. You have to activate the event linkage for the following workflows:

Workflow template Start conditions required*/ delivered?

WS10000223 (Approve new password)

WS10000192 (Approve new user)

WS10000129 (One-step approval of shopping cart)

delivered

WS10000031 (Two-step approval of shopping cart)

delivered

WS10000060 (Shopping cart without approval) delivered

WS10000276 (One-step approval of shopping cart over value limit)

required

WS14000044 (Completion of shopping cart by purchaser)

required

WS10400010 (Confirmation without approval) delivered

WS10400002 (One-step approval of goods receipt)

delivered

WS10400009 (Two-step approval of goods receipt)

delivered

WS10400020 (Approval of goods receipt by administrator)

delivered

WS10400016 (Invoice without approval) delivered

WS10400017 (One-step approval of invoice) delivered

WS10400018 (Two-step approval of invoice) delivered

WS10400021 (Invoice approval by administrator)

delivered

WS1001048 (Notification w. return delivery)

WS10000244 (Notification w. difference bew. purchase order and order response)

WS10000093 (Procurement card, first approval)

WS10000100 (Procurement card, second approval)

WS10000209 (Approval of bidder or vendor registration)

WS10000202 (Transfer shopping cart to PM system)

WS14000045 (Delete item after application error)

WS10000215 (Resubmit item by administrator)

WS10400022 (Alert workflow for contract)

WS79000010 (Workflow without approval for bid)

delivered



WS79000002 (One-step approval for bid) delivered

WS14000030 (One-step approval of vendor)

WS14000043 (Workflow without approval for vendor)

WS14000045 (Deletion of item after application error)

WS14000075 (Workflow without approval for purchase order)

delivered

WS14000089 (One-step approval purchase order)

delivered

WS14000086 (Workflow without approval for contract)

delivered

WS14000088 (One-step approval contract) delivered

WS14000091 (Notification workflow for external auction)

*required: you have to define your own start conditions for the corresponding event to trigger the workflow(s)


Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → SAP Business Workflow → Perform Task-Specific Customizing

2. If you use the standard approval workflows, you have to define the conditions under which the workflows are started:

Shopping carts (w/o approval WS10000060, one-step approval WS10000129, two-step approval WS10000031)

Confirmation (w/o approval WS10400010, one-step approval WS10400002, two-step approval WS10400009, Administrator approval WS10400020)

Invoice (w/o approval WS10400016, one-step approval WS10400017, two-step approval WS10400018, Administrator approval WS10400021)

Purchase Order (w/o approval WS14000075, one-step approval WS14000089)

Contract (w/o approval WS14000086, one-step approval WS14000088)

Bid (w/o approval WS79000010, one-step approval WS79000002)

The start conditions are shipped by SAP by default in such a way that the workflows are executable. However, you can change the start conditions to fit your requirements.

The delivered or changed start conditions must be activated!



If multiple approval workflow types are activated for a specific procurement scenario (via event linkage), you must prevent these workflows from starting together. You do this by activating the delivered start conditions or by defining your own start conditions! SAP recommends modifying the delivered start conditions to suit your requirements. If you define new start conditions, you must take into account that the start conditions editor uses the rules of Boolean logic. This means that the status that is defined in one start condition is to appear in the reverse form in the other start condition. This ensures that the other condition always shows False when the first one shows True.

Example: Approval Workflow for Purchase Order or Change Version of the Purchase Order:

Workflows WS14000075 (w/o approval) and WS14000089 (one-step approval) react to the same event: Save the change. If the start conditions are not activated, both workflows start together immediately the change version is saved. Therefore, the start condition Workflow-Start WS14000075 defines clearly the prerequisites for starting Workflow WS14000075 - the start condition Workflow-Start WS14000089 defines exactly the reverse circumstances under which only Workflow WS14000089 starts. This ensures that a workflow always starts, but never both together.

For more information, see the Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → SAP Business Workflow → Define Conditions for Starting Workflows

3. You have to assign processors to some standard tasks.

If you want a certain group of persons to be able to approve your work items, you must specify all the possible processors for the task in question. For example, tasks TS10008069 and TS10008127 for standard two-level approval and task TS10008126 for single-level approval. These tasks are normally assigned to the manager role. If required, you can, however, specify these processors differently.

You have to assign a processor to the following tasks:

Task Used in Workflow Processor

TS10008024 Approve new user Manager role or Administrator

TS10008054 Approve New password Manager role or general task

TS10008061 Ask Whether Requester Accepts Rejection

General task

TS10008069 Approval of shopping cart Manager role or general task

TS10008109 Registration of bidder or vendor

Administrator or purchaser

TS10008125 Approve New user 2 Manager role or general task



TS10008212 Review process (WS1000265)

Manager role or general task



(WS1000265)

TS10008214 Approval fragment (WS1000271)


TS10007947 Procurement card General task

TS10107914 Present Changes to Requester

General task

TS10407972 Change rejected shopping cart

General task

TS10407914 Confirmation (one-step) Manager role or general task

TS10407915 Confirmation (two-step) Manager role or general task

TS10407916 Reviewer WF (for Confirmation)


TS10407917 Approval Task for CFApprFragm1


TS10407918 Approval Task for IVApprFragm1


TS10407919 Reviewer WF (for Invoice) Manager role or general task

TS10407920 Invoice (one-step) Manager role or general task

TS10407921 Invoice (two-step) Manager role or general task

TS10407922 2nd Confirmation Approval in 2 Step WF


TS10407923 2nd Invoice Approval in 2 Step WF


TS10407924 Admin approval (Confirmation)

Administrator

TS10407925 Admin approval (Invoice) Administrator

TS10407926 Check Contract General task

TS10407932 Contract Alert Workflow Manager role or general task

TS14007942 Approve Vendor Manager role or general task

TS14007947 Revise Shopping Cart General task

TS14007969 Approve Contract in 1 Step WF


TS14007970 Purchase Order Approval in 1 Step WF


TS79007914 Bid Approval (one-step) Manager role

Authorization to determine the approver or reviewer

In addition, you need to specify who is to be authorized to change/ insert the approver. You do this by specifying the possible processors in the workflow template (Menu: Additional data → Agent assignment → Maintain). In the SAP Enterprise Buyer system this applies to the following workflow templates:

WS10000129 - Approve shopping cart (one-step)

WS10000031 - Approve shopping cart (two-step)



WS10000060 - Workflow without approval (shopping cart)

WS10000271 - Approval fragment for anchor

WS10400002 - One-step approval goods receipt

WS10400008 - Approval fragment for goods receipt

WS10400009 - Two-step approval goods receipt

WS10400010 - Workflow without approval goods receipt

WS10400016 - Invoice without approval

WS10400017 - One-step approval invoice

WS10400018 - Two-step approval invoice

WS10400020 - Approval goods receipt by administrator

WS10400021 - Approval invoice by administrator



You will find a complete list of workflows in the SAP Enterprise Buyer documentation:

Tasks for System Administrators → SAP Business Workflow → Technical Information on Standard Workflows

4. You have to assign authorization to change shopping carts during the approval process.

This is controlled by means of a role-based attribute BBP_WFL_SECURITY, and is set in the transaction PFCG on the tab card Personalization. There are four possible levels of authorization:

High: Workflow is never restarted.

Medium: Workflow is restarted based on start conditions.

Low: Workflow is always restarted.

No: No changes to the shopping cart allowed during approval.

Defining Transaction Types Use You specify the transaction type for all Materials Management documents that are to be created in SAP Enterprise Buyer. This controls the number range intervals that the document numbers are determined from and the status profile.



Procedure

For purchase orders in the backend system, the name of the transaction type corresponds to the name of the document type.


Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Define Transaction Types

Defining Number Ranges Use You specify the number ranges for the materials management documents in the SAP Enterprise Buyer system.

You must specify number ranges for the following local documents:

• Shopping carts

• Purchase orders

• Confirmations for goods and services

• Invoices

Additionally, you have to define number ranges for documents that are to be created in backend systems. You can define different number ranges for different backend systems.

Procedure Menu path in the SAP Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Number Ranges

For the interval number for the shopping cart number range, you must enter the value of Int.No. that you have defined for the transaction type of the shopping cart. See the Implementation Guide (IMG) Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Define Transaction Types

Business Partner Number Ranges You define number ranges (for internal and external number assignment) in central business partner maintenance. See SAP IMG path: Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings → Define Number Ranges.

When replicating vendors from multiple backend systems, the number range for which the standard indicator has been set is used for external number assignment. Therefore, it is recommended that this number range is great enough to cover all number ranges set in the individual backend systems.



See IMG path: Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings → Define Groupings and Assign Number Ranges

Making Settings for Account Assignment Procedure Activity Description For more information, see:

Selecting account assignment categories

You must have selected required account assignment categories from a preconfigured list.

Menu path in the Implementation Guide (IMG)

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Account Assignment → Define Account Assignment Categories

Mapping account assignment categories

R/3 account assignment categories must have been mapped to the SAP Enterprise Buyer categories.


Supplier Relationship Mangement → SRM Server → Cross-Application Basic Settings → Account Assignment → Define Account Assignment Categories

Changing account assignment categories

You can change account assignment categories using Business Add-Ins.


Supplier Relationship Management → SRM Server → Business Add-Ins for Enterprise Buyer → Account Assignment →

• Change Account Assignment Category when Creating Backend Documents

• Change Account Assignment Category when Importing Backend Documents

Defining rules for G/L account determination

• You can specify that the criteria used to determine the G/L account are to be based on the product category and account

Menu path in the Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Cross-Application Basic S tti A t



assignment category.

• Alternatively, you can define your own criteria for determining the G/L account.

Settings → Account Assignment → Define G/L Account for Product Category and Account Assignment Category

Menu path in the Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Business Add-Ins for Enterprise Buyer → Account Assignment → Determine G/L Account

Creating Payment Conditions Procedure Activity Description For more information, see:

Creating payment conditions You can use this setting to define rules used by SAP Enterprise Buyer to determine payment conditions. When processing business documents, you want to select payment conditions via an input help, this step is mandatory. The input help reflects view CRMV_PMNTTRMS for local terms of payment and tables BBP_PAYTERM and BBP_PAYTERM_TEXT for backend payment terms.

Path in the Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Create Payment Conditions

You can create payment conditions in one of the following ways:

• Create local terms of payment manually in SAP Enterprise Buyer.

Even though Description is not a required field in maintenance view CRMV_PMNTTRMS, the input help will display only terms of payment that have a description.

Alternatively, you can initially load the local terms of payment from one of your backend systems using report BBP_UPLOAD_PAYMENT_TERMS. Since the local terms use the days/percentage values only, the result will be just a subset of all backend terms.

• Load terms of payment from all your backend systems.

Do not use report BBPGETVC. Run report

BBP_UPLOAD_PAYMENT_TERMS. When you use this report, not only the day/percentage values but the complete width (as in tables



T052/T052U) is uploaded from your backend systems and is stored in tables BBP_PAYTERM and BBP_PAYTERM_TEXT respectively.

Input helps will display only those terms that have a description in table BBP_PAYTERM_TEXT (backend table T052U).

SAP recommends that you change descriptions in the backend system. There is no update mechanism. Subsequent calls of the report will reload everything and overwrite any texts manually entered in BBP_PAYTERM_TEXT.

Making Settings for Product Categories • For information on replicating materials from R/3 Systems, see Replication of Materials

from R/3 Backend Systems [page 40].

• For information on creating product categories, see Creating Product Categories in the SAP Enterprise Buyer documentation.

Confirmation and Invoice Verification

Currently there is only one setting that refers to confirmation:

You can define tolerances for value- or quantity-based (exceeding) limits for deliveries or invoices. Quantities or values of deliveries or invoices may vary up to these tolerance values, thus allowing documents to still be posted. For more information see menu path in the SAP Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Set Tolerance Checks.

Making Settings for Invoices Procedure Activity Description For more information, see:

Defining backend systems Define the backend Accounting systems and specify that documents are to be created locally in the SAP Enterprise Buyer system.

Defining Backend Systems [page 30]

Defining number ranges Define the number ranges for local invoices.

Defining Number Ranges [page 62]

Defining the transaction type Define the transaction type for invoices.

Defining Transaction Types [page 58]

Making settings for account Make the settings necessary Making Settings for Account



assignment for account assignment. Assignment [page 60]

Define the status profile for the user status

Adjust the status management for your documents.


Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Define Status Profile for User Status

Workflow: Perform task-specific Customizing

Activate the event coupling for the workflow for authorizing the invoice and assign the processor



Define the conditions for starting workflows

Define the start conditions for the workflow.


Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → SAP Business Workflow → Define Conditions for Starting Workflows

Determine the system for tax calculation

Define system for tax calculation. These could be:

• SAP R/3 System

• External tax system, (Vertex or Taxware)

• Tax Transaction Engine (TTE)

• Customer-specific systems


Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Tax Calculation → Determine System for Tax Calculation

For more information, see chapter Tax Calculation in documentation SAP Enterprise Buyer.

Define transaction types Define the transaction type for the local invoice or credit memo.


Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Define Transaction Types

Create payment conditions You want to use your own payment conditions in the Enterprise Buyer system.


Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Create Payment Conditions



Define account assignment categories

Map the account assignment categories that are used in the Enterprise Buyer system to those used in the backend system.


Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Account Assignment → Define Account Assignment Categories

Define G/L account for product category and account assignment category

Specify the G/L accounts that are to be posted in Financial Accounting in the backend system.


Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Account Assignment → Define G/L Account for Product Category and Account Assignment Category

Define nota fiscal categories If you use nota fiscal, for example in South America or Brazil, maintain the nota fiscal categories.


Supplier Relationship Management → SRM Server → Confirmation and Invoice Verification → Nota Fiscal → Define Nota Fiscal Types

Define reasons for rejecting vendor invoices

You want to define reasons that are specified when refusing invoices.


Supplier Relationship Management → SRM Server → Confirmation and Invoice Verification → Define Reasons for Rejecting Vendor Invoices

Set tolerance check for invoice/confirmation

You want to post invoices with amount or value-related alternates. Maintain tolerances.


Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Set Tolerance Checks

Change account assignment category when creating backend documents

You want to assign an account assignment category in the Enterprise Buyer system to multiple account assignment categories in different backend systems.


Supplier Relationship Management → SRM Server → Business Add-Ins for Enterprise Buyer → Account Assignment → Change Account Assignment Category when Creating Backend Documents

Change account assignment You want to assign the Menu path in the SAP



category when importing backend documents

account assignment category documents in the Enterprise Buyer system when importing backend documents.


Supplier Relationship Management → SRM Server → Business Add-Ins for Enterprise Buyer → Account Assignment → Change Account Assignment Category when Importing Backend Documents

Define the FI component used

In order that invoices can be created locally in the Enterprise Buyer system without reference to a purchase order or delivery, the Financial Accounting (FI) component that is used must have been defined in the vendor's user attributes:

• VENDORS_ACS

• BUK

See Attributes for the Enterprise Buyer Scenario in documentation SAP Enterprise Buyer.


Backend ERP SAP EnterpriseBuyer SAP BW

Analyse SC percost center

[20][20]

Assumption forreporting with

BW:A user with a

different role (e.g.purchasing

manager) entersEnterprise Buyerand checks theshopping carts

using BW.

DisplayDisplay shopping shoppingcartscarts[21][21]

Drill downDrill down//printprint/send/send report report

[22][22]

Prerequisites You have installed BW. For installation information, see the installation and upgrade guides for mySAP Business Intelligence on the SAP Service Marketplace under service.sap.com\instguides.



Procedure Settings in the Enterprise Buyer system and R/3 backend systems

Activity Description Further documentation

Setting the system change option

Before you can activate the DataSources in the various systems, you must permit repository changes and cross-client Customizing. You set the system change option for your clients in table T000 using transaction SM 30.

Transferring the application component hierarchy

You must transfer the application component hierarchy.

Path in the BW Implementation Guide (Transaction SBIW ) Business Content DataSources → Transfer Application Component Hierarchy

Activating DataSources EBP system: Activate the DataSources.

FI backend system: Activate all relevant text, attribute and hierarchy DataSources for account assignments.

Path in the BW Implementation Guide (Transaction SBIW ) Business Content DataSources → Transfer Business Content DataSources

For information on which DataSources to activate, see SAP Note 614940.

This action has to take place in the R/3 backend system that you use for FI.

Checking and/or defining background user

You have to make sure that your background user ALEREMOTE has the following authorization profiles:

S_BI-WX_RFC (Business Information Warehouse: RFC users in extraction)

P_PLAN_ALL (to extract master data for 0ORGUNIT – organizational unit)

Use transaction SU01 to check and/or define the user.

For information on creating ALEREMOTE as an interactive user or CPIC user, see SAP Note 161570.

For information on BW authorizations for remote users, see SAP Note 150315.

For information on authorizations for HR data extraction, see SAP Note 397208.

Defining RFC destination You must define the RFC connection for your BW system in transaction SM59.



Creating user for setting up connection between BW and Enterprise Buyer

You need a user with administrator authorization. This authorization can be withdrawn as soon as the connection has been set up.

Settings in BW


Checking and/or defining background user

You have to make sure that your background user BWREMOTE has the following authorization profile:

S_BI-WHM_RFC (Business Information Warehouse: RFC users in the Warehouse).

Use transaction SU01 to check and/or define the user.

For information on BW authorizations for remote users, see SAP Note 150315.

Defining logical systems

You must define the logical systems that you want to extract data from.

Path in the Implementation Guide (IMG) Business Information Warehouse → Links to Other Systems → General Connection Settings → Define Logical System

Defining RFC destinations

You must define the RFC connections for your logical systems in transaction SM59.

Defining source systems

You must define your source systems in the Administrator Workbench (Transaction RSA1). Select the source system tree and then choose Create in the context menu.

We recommend choosing Automatic creation to replicate the DataSources automatically

For further information, see the BW documentation at help.sap.com under Administrator Workbench → Modeling → Source System

For troubleshooting information, see SAP Note 179602.

Transferring global settings

You have to make sure that global settings such as currencies, units of measurement and fiscal year variants are identical in both your source systems and your BW system.

In the Administrator Workbench, choose Modeling → Source Systems. Select your source system and then choose Transfer Global Settings in the context menu.

Since Enterprise Buyer does not use fiscal year variants, you have to transfer these from your FI system. Alternatively, you can maintain the fiscal year variant manually in the BW



Implementation Guide under Business Information Warehouse → General BW Settings → Maintain fiscal year variant.

Installing business content

You must install the business content using the Administrator Workbench.

We recommend selecting the content roles SAP_BW_SRM_VARIOUS_ITEMS and SAP_BW_SRM_MANAGER, and then activating In data flow before.

When activating a selected role, all BW objects belonging to this role (InfoObjects, InfoObjectCatalogues, ODS objects, InfoCubes, update rules, InfoSources, transfer rules, queries, workbooks and Web Templates) are activated.

You have to check that the fiscal year variant (0FISCVARNT) is defined as described in SAP Note 330421 in the update rules and the chart of accounts (0CHRT_ACCTS) and the financial management area (0FM_AREA) are defined as described in SAP Note 330415 in the transfer rules.

For further information, see the BW documentation at help.sap.com under Administrator Workbench → Business Content → Installing Business Content

Defining a source system ID

You must assign a source system ID to the source system in the Administrator Workbench under Tools.

For further information, see SAP Note 336351.

Loading data into BW Data must be loaded in the following order:

Load your master data, texts and hierarchies.

Load your transactional data into ODS objects and update them in the InfoCubes according to the relevant data model.

Use the delta method for loading transactional data.

For information on loading data, see the presentation Infos for consultants on the Service Marketplace under Solution Details\mySAP SRM\Components in Detail\ Business Information Warehouse (SRM Analytics)\Documentation and SAP Notes 352814 and 481283.

For information on loading data in a multiple Enterprise Buyer/backend system scenario, see Analyses in e-Procurement on the Service Marketplace under Solution Details\mySAP SRM\Components in Detail\ Business Information Warehouse (SRM




Analytics)\Documentation.

For information on external product categories, see External Product Categories on the Service Marketplace under Solution Details\mySAP SRM\Components in Detail\ Business Information Warehouse (SRM Analytics)\Documentation.

Defining Reporting authorizations

You have to assign certain reporting authorizations using the BW authorization concept.

For further information on authorizations, see Reporting Authorizations on the Service Marketplace under Solution Details\mySAP SRM\Components in Detail\ Business Information Warehouse (SRM Analytics)\Documentation.

Final Settings in EBP


Importing BW roles and assigning them to Enterprise Buyer roles

After activating the BW role in the BW system, you have to import the BW role SAP_BWC_SRM_MANAGER (customer version) into Enterprise Buyer using transaction PFCG, assign it to the Enterprise Buyer role SAP_BBP_STAL_PURCHASE_MANAGER and activate it.

For further information, see SAP Notes 401367 and 520131, and Regenerating Role Profiles in the Enterprise Buyer documentation.