233045811 srm self service procurement cookbook

Self-Service Procurement: Configuration Guide

Release 500 AD

DO

N.S

RM

_IP

CO

NG

UID

E

08.12.2004

Self-Service Procurement: Configuration Guide 2

Copyright © Copyright 2004 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. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint 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, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

08.12.2004


Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help → General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation. Example text Emphasized words or phrases in body text, graphic titles, and table

titles.

EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and 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. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

08.12.2004


Self-Service Procurement: Configuration Guide ....................................................................... 6 Documentation Landscape for SAP Solutions and Business Scenarios............................... 9 SAP Notes............................................................................................................................ 11 General Settings .................................................................................................................. 13

Aligning Units of Measurement, Currencies, and Exchanges Rates ............................... 14

Scheduling Reports .......................................................................................................... 15

Making Settings for Tax Calculation................................................................................. 17

Setting the Control Parameters........................................................................................ 22

Starting Application Monitors............................................................................................ 23

Setting Up SAP Internet Pricing and Configurator ........................................................... 24

Configuration for Sending Internet Mails (SAPconnect) .................................................. 25

Setting up Attachments .................................................................................................... 27

Configuration for Attachment transfer .............................................................................. 28

System Connections ............................................................................................................ 29 Making Settings for the Internet Transaction Server........................................................ 30

Starting SAP Enterprise Buyer (Start URL) .................................................................. 32

Defining Logical Systems and RFC Destinations (SSV & SRC)...................................... 33

Creating a Distribution Model ........................................................................................... 35

Defining Backend Systems .............................................................................................. 36

Making Entries Needed for Generating Application URLs ............................................... 37

Configuring SAP Catalog Content Management.............................................................. 38

Mapping Catalog Characteristics to OCI Fields............................................................ 39

Configuring Customer-Specific OCI Fields................................................................... 41

Defining the Integrated Call Structure in SAP Enterprise Buyer .................................. 42

Assigning Call Structure IDs to Users and Organizations ............................................ 45

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

Customizing Material Replication in Enterprise Buyer ................................................. 48

Setting the Middleware Parameters ............................................................................. 49

Downloading Customizing Objects............................................................................... 51

Downloading Business Objects .................................................................................... 53

Business Customizing.......................................................................................................... 55 Organization Configuration............................................................................................... 56

Regenerating Role Profiles........................................................................................... 57

Creating the Organizational Plan.................................................................................. 58

Making Settings for Create Internal User ..................................................................... 63

Maintaining the User Attributes .................................................................................... 64

Shopping on Behalf of Other Users.............................................................................. 65

Managing Business Partner Addresses ....................................................................... 66

08.12.2004


Making Settings for Locations and External Business Partners................................... 67

Process Configuration ...................................................................................................... 69

Setting Up SAP Business Workflow ............................................................................. 70

Defining Number Ranges ............................................................................................. 79

Defining Transaction Types.......................................................................................... 81

Making Settings for Account Assignment ..................................................................... 82

Creating Payment Conditions....................................................................................... 83

Making Settings for Product Categories ....................................................................... 84

Making Settings for Confirmations................................................................................ 85

Making Settings for Invoices......................................................................................... 86

Procurement Card................................................................................................................ 89 Navigation Interfaces of Shopping Cart ............................................................................... 90 Configuration of BW for use with Enterprise Buyer ............................................................. 92

08.12.2004


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.

08.12.2004


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

SAP Catalog Search Engine

Employee

SAP EBP

Accountant

SAP R/3 Enterprise

Create Shopping Cart

Search in catalog

Select items & add to Shopping Cart

Display ov erv iew

Account assignment is

checked

Display account assignment

Order Shopping Cart

Check Shopping Cart status

Receive notification on

work item

Create RequisitionCheck status after

approv alCreate PO

Manager

SAP BW

Approv e shopping cart

Check BW Report (optional) Display BW report

08.12.2004


SAP Catalog Search Engine

Employee

SAP EBP

Accountant

SAP R/3 Enterprise

Invoice posted

GoodsGoods receiptreceiptpostedposted

Createconfirmation

Create invoice

Paymenttriggered

Manager

SAP BW

08.12.2004


Documentation Landscape for SAP Solutions and Business Scenarios Purpose This documentation gives you an overview of the major sources of information available to you on SAP solutions and business scenarios. Always use the current documents in your implementation.

Current documents

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

Master Guide, Installation and Upgrade Guides instguides

ibc

Business-Scenario Configuration Guide ibc

Implementation Guide (IMG) Note: This is in the SAP System, not in SAP Service Marketplace

Business Scenario Description ibc

SAP Library helpportal with all releases of a SAP component

Note: Available in the SAP System under Help → SAP Library

The following information supplements the individual documents:

Current supplementary information

Information Quick Link on 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

Features The following documents are available for a SAP 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 SAP solution is the Master Guide. It lists the SAP 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 Configuration Guide This document describes the settings you use to configure the SAP application components and third-party applications required for a business scenario. It contains information specific to business scenarios for the particular IMG activity. It does not reiterate the IMG documentation but makes reference to particular IMG texts.

08.12.2004


Implementation Guide (IMG) This tool adjusts SAP systems to customer requirements. The IMG contains the IMG activities for all SAP components, and general documentation. The structure is component oriented, without reference to a business scenario. The Business-Scenario Configuration Guide establishes the link between the IMG and the various business scenarios.

Business Scenario Description This document describes how a business scenario runs once all components have been installed and configured. All the business processes of a business scenario are represented graphically in the component view, which illustrates the process steps of each SAP component.

SAP Library This contains the entire documentation of SAP components and business scenarios. The Business Scenario description is part of the SAP Library.

08.12.2004


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

Ensure that you read the information contained in the Release Information Note (RIN) for the current support package.

SAP Notes

Note Number Title Referenced in Section

723129 (RIN) Support Package 00 for SRM 4.0

750433 (RIN) SRM 4.0 SP stack 08/2004: Release and information note

759473 (RIN) SRM 4.0 SP stack 09/2004: Release and information note

741822 TAX. Problems w/ Backend tax indicator and jurisdiction code

Making Settings for Tax Calculation

673372 Short dumps UNCAUGHT_EXCEPTION in SRM 3.0 (EBP 4.0)

Setting Up the SAP Internet Pricing Configurator

455140 Configuration E-mail, fax, paging/SMS via SMTP

Configuration for Sending Internet Mails (SAPconnect)

100740 Set up pcANYWHERE connection in OSS

Making Settings for the Internet Transaction Server

723509 ITS version for SRM Server 5.0

Making Settings for the Internet Transaction Server

307782 Procedure fails during logon Making Settings for the Internet Transaction Server

642202 EBP user admin: RFC user profile in back end/plug-in

Defining Logical Systems, RFC Destinations and ALE Settings

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

720819 Middleware consumer entry for SRM 4.0 in the OLTP


519794 EBP: Replication of materials with purchasing view


644124 EBP: Managing access rights Regenerating Role Profiles

08.12.2004


to attributes per user

563180 Locations for EBP 4.0 – plant replication

Making Settings for Locations and External Business Partners

322526 Analysis for workflow problems

Setting Up SAP Business Workflow

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


179602 BW?! Source system connection


330421 Fixed value for 0FISCVARNT in update rules


330415 Fixed value for 0CHRT_ACCTS & 0FM_AREA in transfer


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


08.12.2004


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

Familiarize yourself with the documentation landscape for SAP solutions and business scenarios. For a description of the types of documentation provided by SAP and where to find the current versions, see Documentation Landscape for SAP Solutions and Business Scenarios [page 9].

Prerequisites • The system landscape is installed, using the SAP solution master guides, and the SAP

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.

08.12.2004


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.


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

08.12.2004


Scheduling Reports 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 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 table below.

Scheduling Reports

Report Name Description Required/

optional

For more information, see:

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 (for example every 2 minutes) using transaction SA38. Create a variant with only logical system name, and schedule this job with this variant.

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

Required

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 periodically (for example every 2 minutes) in the SAP Enterprise

Required

08.12.2004


Buyer system using transaction SA38. Create a variant and schedule this job with the variant.

RSPPFPROCESS If the purchase orders shall be 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.

Optional 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

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

Optional 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.

Optional See also Making Settings for Account Assignment [Extern].

08.12.2004


Making Settings for Tax Calculation Use You can calculate sales tax in SAP Enterprise Buyer. The system calculates tax when you create a shopping cart, a purchase order, or enter an invoice or a credit memo.

You can use the tax calculation functions in the following applications:

• Shop

The system determines a tax indicator. You can change the default tax indicator. You can display the tax amounts for each item individually and as total amount. You can define whether the system takes tax amount into account in the approval process.

• Create Purchase Order

You can change the default tax indicator. The system calculates the tax on the basis of the current data. You can display the tax amounts for each item individually and as total amount.

• Enter Invoice/Credit Memo

You can change the default tax indicator. Depending on the legal requirements, the system calculates the taxes either for each item individually or as a total amount. In addition, you can enter the taxes manually for each tax code or as total tax amount.

• Evaluated Receipt Settlement

The system recalculates the tax. You define the tax code in the purchase order.

You can use the following systems for tax calculation:

• SAP R/3 system (tax calculation takes place in the financial accounting system)

If you already have an SAP R/3 financial accounting system, we recommend that you use the existing tax calculation provided by the R/3 system. You do not need to make any additional Customizing settings for tax calculation.

• External tax system (Vertex or Taxware)

If you do not have an SAP R/3 financial accounting system, you can use an external tax system, such as Vertex or Taxware (suitable for large customers only). This type of tax calculation is only valid for the USA and Canada.

If an external tax system is connected to the SAP R/3 system, it is called up automatically from the R/3 system.

• Customer-specific implementation (tax calculation in SAP Enterprise Buyer)

If you do not have an SAP R/3 financial accounting system, you can use a customer-specific implementation for simple tax calculation (for example, if you only have two tax codes).

• SAP Transaction Tax Engine [Extern] (TTE)

If you use SAP Supplier Self-Services or need to calculate taxes for several countries, you have to use SAP Transaction Tax Engine which is part of IPC.

08.12.2004


If more than one country is involved and each country has its own tax code, it will not be possible for Enterprise Buyer to connect directly to an external tax system.

For example, if both US tax and European tax are needed, you have to use TTE or R/3 for tax calculation.

Define the systems in the Implementation Guide (IMG):

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

Prerequisites Settings for tax calculation

Setting Menu path in the Implementation Guide (IMG)

You define the system for tax calculation.

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

You define the allowed invoice verification tolerances for the variances between calculated tax amounts and tax amounts entered manually (optional).

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

You define whether taxes for the total freight costs (that is, for all company codes) are to be calculated with a separate tax code (optional).

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Tax Calculation → Define Tax Calculation for Freight Costs

You define whether taxes for freight costs for specific company codes are to be calculated with a separate tax code (optional).

Supplier Relationship Management → SRM Server → Business Add-Ins (BAdIs) → Tax Calculation → Calculate Tax for Freight Costs

Procedure Tax Calculation in the SAP R/3 Financial Accounting System If you choose to calculate tax in the SAP R/3 system, tax calculation takes place in the respective financial accounting system (depending on the attribute of the user System Alias for Financial Accounting Systems in the organization model). The SAP R/3 system has to be defined as financial accounting system.

The system determines the tax code from the entries in the tables and fields, for example, from the product category, country of goods recipient, or the domestic/international indicator.

08.12.2004


If the tax indicators in SAP Enterprise Buyer do not match the tax indicator in the financial accounting system, you can map them to the tax indicators of the financial accounting system.

The following table gives an overview of all settings you can make:

Settings in Enterprise Buyer for R/3 as the tax calculation system

Setting Menu path in the Implementation Guide (IMG)

You can maintain tax codes.

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Tax Calculation → Enter Tax Code

You can map tax codes that have different names in the FI system and in SAP Enterprise Buyer to each other.

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Tax Calculation → Assign Enterprise Buyer Tax Code to FI System

You can use individual tax code determination.

Supplier Relationship Management → SRM Server → Business Add-Ins (BAdIs) → Tax Calculation → Determine Tax Code

You can change or supplement the data used to calculate tax depending on the system selected for tax calculation.

Supplier Relationship Management → SRM Server → Business Add-Ins (BAdIs) → Tax Calculation → Change Tax Data

You can specify a tax code for country and product category (optional).

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Tax Calculation → Determine Tax Code for Country/ Product Category

Tax Calculation with Vertex or Taxware

This type of tax calculation is only valid for the USA and Canada.

1. Define the destination of the external system, for example EXT_DEST.

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

2. Define the backend system. The external system is used directly for tax calculation.

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

Required entries:

Logical system, for example VERTEX

Name, for example VERTEX

Destination, for example EXT_DEST

System type: Tax external system

08.12.2004


Customer-Specific Implementation You can carry out customer-specific tax calculation by replacing the function module “NOR3_TAX_CALCULATION” with your own function module:

Go to table BBP_FUNCTION_MAP, in the Object field enter “TAX”. Find Method = Calculate_NOR3, Type = LOCAL, and Function “NOR3_TAX_CALCULATION”. You can then change this entry with your own function module.

The interfaces of the new customer function module must be the same as the default function module (i.e. Import/export parameters, tables and exceptions… etc.)

SAP Transaction Tax Engine (TTE) ...

1. Configure SAP Transaction Tax Engine according to the Configuration Guide.

For more information, see the SAP Service Marketplace at service.sap.com/srm → mySAP SRM in Detail → Scenarios in Detail → Supplier Enablement → Implementation Information → Config. Guide for TTE. If you have access to SAP Solution Manager, you can also use the configuration information there.

Only continue once you have successfully configured SAP Transaction Tax Engine.

2. Define the destination of the TTE system, for example TTE_DEST.

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

3. Define the backend system.

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

Required entries:

Logical system, for example TTE

Name, for example TTE

Destination, for example TTE_DEST

System type, TAX External System

4. Edit the business partners.

a. In the SAP Easy Access menu choose Master data → Business Partners → Process business partner.

b. Enter the business partner (BusPartner), for example, the company that the goods are to be delivered to.

08.12.2004


You must specify a business partner because the business partner is used to determine the location. Verify that the Company attribute for the business partner in the organizational model has been maintained.

c. On the Number for Tax and Reporting tab page, make the following entries:

Tax category, for example DE0 for the VAT registration number in Germany

Name

Tax number; this is checked depending on the tax category selected

d. On the Tax Classifications tab page, maintain the following data for countries that you work with:

Country, for example DE

Region

Tax type, for example VAT

Tax group, for example FULL

5. Edit all products that are to be checked.

a. In the SAP Easy Access menu choose Master data → Products → Maintain Products.

b. Enter the ID/short text for a product and click on Start.

c. Choose the General tab page. Make the following entries:

Country, for example DE

Tax type, for example VAT

Tax group, for example HALF

See also:

SAP Note 741822, TAX. Problems w/ Backend tax indicator and jurisdiction code.

08.12.2004


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

SPOOL_JOB_USER

User that executes spool job <AdminUser>

SPOOL_LEAD_INTERVAL

Interval by which the retry time incr.

<number of seconds>

SPOOL_MAX_RETRY

Max. number of retries for writing BAPIs

<number>

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

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

08.12.2004


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 after the installation of SAP Enterprise Buyer.

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

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

08.12.2004


Setting Up SAP Internet Pricing and Configurator Use For information on how to set up SAP Internet Pricing and Configurator (IPC), see section Enterprise Buyer Professional in the SAP IPC 4.0 Server Installation Guide.

See the Installation Guide at SAP Service Marketplace under service.sap.com/instguides → Installation → Installation & Upgrade Guides → mySAP CRM → SAP CRM 4.0 → E-Commerce Installation Guides → IPC 4.0 Server 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 (BAdIs) → Pricing → Switch On Simplified Pricing (Classic Scenario).

If a short dump occurs while you are creating or changing purchase documents, refer to SAP Note 673372, Short dumps UNCAUGHT_EXCEPTION in SRM 3.0 and SRM 4.0.

08.12.2004


Configuration for Sending Internet Mails (SAPconnect)

Use The SRM system uses automatic and manual mail communication at various points of the procurement process. Before you can send e-mails, you need to have configured certain settings to ensure communication between your SRM Server and your mail server.

Prerequisites • Your mail server is SMTP-compatible

• You have configured the SAP Web Application Server and SAPconnect according to the information provided in the Quick Guide to SMTP Configuration. To view this document, go to transaction SCOT and choose Help → Application Help. See also SAP Note 455140.

When configuring SAP WAS, maintain the application server’s profile parameters and activate the usage of SMTP on this server. Carry out the other configuration steps described in the SMTP configuration guide.

When configuring SAPconnect in transaction SCOT, pay particular attention to:

Creation of default domains You create a default domain and enter this domain manually in transaction SCOT under Settings → Default Domain.

Creation and configuration of SMTP nodes

Procedure ...

1. Adjust User Data

a. Call SU01

b. Maintain the Internet mail addresses for the relevant users in their user master records.

You must either maintain a valid e-mail address for the user or leave the field blank. If an SAP user, who does not have an e-mail address in the user master record, sends an e-mail, a sender address is generated automatically from the SAP user name and the default domain of the system, for example, [email protected].

2. Send a Test E-mail

a. Call SO01

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

3. Start Send Process

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

08.12.2004


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.

08.12.2004


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, make the relevant settings in the Internet Communication Framework in transaction SICF.

2. If you want to have several clients in the system, create an alias for each client, with the alias pointing to /default_host/sap/ebp/docserver.

3. In the tab page Service Data, create the client number in the Client field under the logon data.

4. Choose one of the following options for logon. SAP recommends that you choose the first option.

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

Go to transaction SMICM and choose Goto → Services.

View the domain name that is being used for SAP Web Application Server and check against the domain name being used in the webserver for SAP Internet Transaction Server. The same domain name must be used for both, for example, washost.<sap.corp>:4711/… and itshost.<sap.corp>:0815/…

Go to transaction SS02, enter RFC destination NONE and execute. Check that the profile parameters login/create_sso2_ticket and login/accept_sso2_ticket of your Enterprise Buyer system are set to value 1 (ticket including certificate). If this is not the case, go to transaction RZ11 and change the values accordingly. This means that the ticket generated when the user logs on to the ITS can be accepted by the HTTP service.

Change ITS service to GLOBAL. This allows the generation of a ticket to be requested during logon.

Ensure that the parameter ~mysapcomgetsso2cookie is set to the value 1.

Publish the service

b. Define a user in the HTTP service. If you are only using one client, define the user in the Docserver node. If you have several clients, define a user in the Alias node. We recommend that you choose user type Communication.

08.12.2004


Configuration for Attachment transfer Prerequisites In order to store shopping cart attachments in the backend system, you must first activate the transfer by creating an active method and by setting the indicator for parameter CV_ATTACH_TRANSFER_ACTIVE in BAdI BBP_CREATE_PO_BACK (for purchase orders) or BAdI BBP_CREATE_REQ_BACK (for purchase requisitions).

See Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Business Add-Ins (BAdIs) → Follow-On Document Generation in the Backend-System → Purchase Order in Backend System

Or

Supplier Relationship Management → SRM Server → Business Add-Ins (BAdIs) → Follow-On Document Generation in the Backend-System → Purchase Requisition in Backend-System

Procedure Then you must configure the R/3 Document Management System (DMS) in transaction DC10: ...

1. Create document type SRM. Note that no flag is set in any of the columns.

2. Double click in the detail view to define the new Doc. type desc. = SRM Documents. Set the Use KPro indicator.

Enter 1 in the Number assignment field.

Enter an internal number range interval. You can use an existing interval or create a new one in transaction CV90. The internal number range must be used, because the GUID of the SRM attachments has more digits than the number in the backend system.

Maintain the number exit. The number exit is a program exit for document number. It controls number assignment and version numbering for documents. The default setting is MCDOKZNR. If you want to control the number assignment or the version increment via a USER_EXIT, then you have to replace the program MCDOKZNR with a company-specific program. You can find further information in the field help for number exit.

In the screen area Field selection enter – in the field Document Status.

3. Go to the Dialog Structure and double-click on the entry Define object links. Define the new object links EKPO and EBAN. Maintain object link descriptions for EKPO (Purchase order item; Scr.no. 248) and EBAN (Purchase req. item; Scr. no. 247)

4. Define the workstation application in transaction DC30.

All required file types should be included in this list.

08.12.2004


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

This involves, for example:

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

• Determining the systems, servers, clients, distribution models and so on, in the system in which the SAP application component is installed

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


08.12.2004


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.

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.

For detailed information about installation and administration, refer to the SAP@Web Installation Guide and the ITS Administration Guide. See SAP Service Marketplace at service.sap.com/instguides → SAP Web Application Server.

For more information, also refer to the following:

• ITS documentation, see SAP Help Portal help.sap.com → SAP NetWeaver (Release 04) → ABAP Technology → Web UI Technology.

• service.sap.com/sap-its

Procedure

To make sure to use the correct ITS version, install the version recommended in SAP Note 723509, ITS version for SRM Server 5.0.

...

1. Install the ITS version recommended for use with SRM Server 5.0.

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, bbpat03, bbpat04, and bbpmainnew. If the client is not defined in these service files, add parameter ~client=XXX to the SAP Enterprise Buyer start URL.

08.12.2004


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 32].

08.12.2004


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.

08.12.2004


Defining Logical Systems and RFC Destinations (SSV & SRC) Use This section describes the settings you must make to connect an RFC destination / a logical system to your system.

Prerequisites If you wish SAP Enterprise Buyer to communicate with your backend system, you have defined your backend system as a unique logical system. For more information, see Defining Backend Systems.

To enable search help in the backend system, you have created a second RFC connection for the backend system and you have ensured that the user is a system or dialog user. For more information, see SAP Note 656633.

Procedure Defining the logical system Go to transaction SPRO and choose Supplier Relationship Management → SRM Server → Technical Basic Settings → ALE Settings (Logical System) → Distribution (ALE) → Basic Settings → Logical Systems → Define Logical System.

Defining the RFC destination SAP Enterprise Buyer communicates with a backend system using RFC calls. Therefore, you have to define RFC destinations for these systems and an RFC user with appropriate authorizations. For information about the recommended profile for the RFC user, see SAP note 642202 (Enterprise Buyer user admin: RFC user profile in backend/plug-in).

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

You can define the RFC destination by going to transaction SPRO and choosing Supplier Relationship Management → SRM Server → Technical Basic Settings → Define RFC Destinations. ...

1. Use transaction SU01 to define RFC users to communicate between the systems. You have to define a user in both SAP Enterprise Buyer and in the R/3 backend system. If you have several backend systems, you have to define a user in each of these systems.

The user must be a system or dialog user. For information about the recommended profile for the RFC user, see SAP note 642202 under Enterprise Buyer user admin, RFC user profile in backend/plug-in. Use this profile also for the RFC connection from the backend system to SAP Enterprise Buyer.

2. Log on to SAP Enterprise Buyer.

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.)

08.12.2004


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

Defining a second RFC connection You define a second RFC connection for search help in the backend system (for example, for account assignment).

For more information regarding authorization for the search help RFC connection, see SAP Note 656633.

Search help requires dialog users.

Testing an RFC connection ...

1. Log on to SAP Enterprise Buyer.

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 SAP Enterprise Buyer. Here too, test the connection and try out remote login as described in the previous steps.

Result If a window is opened in SAP Enterprise Buyer, the connection is correct for system communication. 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

08.12.2004


Creating a Distribution Model Use The applications that communicate with each other in your distributed systems are specified in the distribution model. The distribution model consists of separate model views where you can define system-wide message flows.

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

Supplier Relationship Management → SRM Server → Technical Basic Settings → ALE Settings (Logical System) → Distribution (ALE) → Modelling and Implementing Business Processes → Maintain Distribution Model and Distribute Views

You can define the partner profiles for all outbound and inbound messages based on the information in the distribution model.

See the Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Technical Basic Settings → ALE Settings (Logical System) → Distribution (ALE) → Modelling and Implementing Business Processes → Partner Profiles → Generate Partner Profiles

08.12.2004


Defining Backend Systems Use This section describes the settings you must make to connect one or more backend systems to SAP Enterprise Buyer.

Prerequisites • You have defined your backend systems as unique logical systems. For more

information, see the section Defining Logical Systems and RFC Destinations [Extern].

• For each backend system:

You have specified the logical system.

You have specified the RFC destination.

You have created a second RFC connection for the same backend system (for account assignment search help in the backend system, for example).

• You have defined how FI data is to be validated.

• You have replicated/created the product categories.

Procedure Defining a Backend System For additional information (for example, on authorization) refer to SAP Note 656633 Search help requires dialog users.

8. In the SAP SRM system, go to transaction SPRO and choose Supplier Relationship Management → SRM Server → Technical Basic Settings → Define Backend Systems.

a. Enter the logical system, destination and system type of the SRM system. Define your SRM system as local if the logical system is your local SAP Enterprise Buyer system and if purchase orders, confirmations and invoices are to be created there.

b. Enter the logical system, destination and system type of the backend system and select the RFC indicator if the logical system is RFC-compatible.

Defining a Backend System for a Product Category This step determines, depending on the product category, whether purchase orders and their follow-on documents (confirmations, goods receipts/service entry sheets and invoices) are to be created locally in SAP Enterprise Buyer or in the backend system. ...

1. To define the source and target system for each category, go to transaction SPRO and choose Supplier Relationship Management → SRM Server → Technical Basic Settings → Define Backend Systems → Define Backend System for Product Category.

2. For specific settings go to transaction SPRO and choose Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders).

08.12.2004


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

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

08.12.2004


Configuring SAP Catalog Content Management In this section you make settings to enable SAP Enterprise Buyer to call SAP Catalog Content Management.

To use SAP Catalog Authoring Tool in Enterprise Buyer, you must either assign the roles /CCM/CATALOG_MANAGER (Catalog Manager) and /CCM/CATALOG_APPROVER (Content Approver) directly to users, or include them in composite roles. You do this in Customizing for mySAP SRM by choosing SRM Server → Cross-Application Basic Settings → Roles → Define Roles.

08.12.2004


Mapping Catalog Characteristics to OCI Fields Use In the standard delivered version of SAP Catalog Content Management, the standard characteristics are already mapped to fields of the Open Catalog Interface (OCI). You can use this procedure to change these standard settings for each catalog individually, and to map non-standard characteristics to OCI fields.

The following table lists the predefined characteristics in SAP Catalog Content Management and their corresponding OCI fields:

SAP Catalog Content Management Characteristic

OCI Field

/CCM/AMOUNT NEW_ITEM-PRICE

/CCM/CURRENCY_CODE NEW_ITEM-CURRENCY

/CCM/CONTRACT_ID NEW_ITEM-CONTRACT

/CCM/CONTRACT_ITEM_ID NEW_ITEM-CONTRACT_ITEM

/CCM/IS_SERVICE NEW_ITEM-SERVICE

/CCM/LEAD_TIME NEW_ITEM-LEADTIME

/CCM/LONG_DESCRIPTION NEW_ITEM-LONGTEXT_N:132

/CCM/MNFCTR_ID NEW_ITEM-MANUFACTCODE

/CCM/MNFCTR_PART_NO NEW_ITEM-MANUFACTMAT

/CCM/ORDER_UNIT NEW_ITEM-UNIT

/CCM/PRODUCT_GROUP NEW_ITEM-MATGROUP

/CCM/PRODUCT_ID NEW_ITEM-MATNR

/CCM/SUPPLIER_ID NEW_ITEM-VENDOR

/CCM/SUPPLIER_PART_NO NEW_ITEM-VENDORMAT

For more information about the OCI and OCI field names, see sap.com/partners/icc/scenarios/srm/ → B2B-OCI → Open Catalog Interface.

Procedure ...

1. In SAP Catalog Content Management, open the catalog that you want to edit.

2. On the Schema tab page, select Edit Characteristics.

3. Choose a characteristic that you want to transfer using the OCI. The system displays the details relating to the characteristic that you chose. If the characteristic is already mapped to an OCI field, the field is displayed in the OCI Field field.

4. Enter a new value in the OCI Field field or make changes to the existing entry.

08.12.2004


You must enter the OCI field name without the square brackets and anything contained within them.

You want to map the catalog characteristic /CCM/ORDER_UNIT, which contains the unit of measurement to be used in orders. The OCI field for unit of measurement is NEW_ITEM-UNIT[n]. N represents the line number. You must enter NEW_ITEM-UNIT in the OCI Field field. SAP Catalog Content Management adds the information represented by [n] automatically.

The OCI field for long texts is an exception. To map to the long text field, you must enter NEW_ITEM-LONGTEXT_n:132. The ending _n:132 tells SAP Catalog Content Management that it must handle this field differently. Do not include the brackets when you enter this field in the OCI Field field in SAP Catalog Content Management.

SAP Catalog Content Management does not check whether you have used the same OCI field for more than one characteristic. This is because, in certain circumstances, it might make sense to map different characteristics in different catalog categories to the same OCI field. If more than one characteristic is mapped to the same OCI field and those characteristics contain values, the value that is transferred to the OCI field last overwrites any values that were previously transferred.

In the standard delivered version of SAP Catalog Content Management, the characteristic /CCM/SUPPLIER_ID is mapped to the OCI field NEW_ITEM-VENDOR. On schema level, you create the additional characteristic Vendor, map it to the same OCI field (NEW_ITEM_VENDOR), and publish the catalog. You transfer an item for which both characteristics are filled (the characteristic /CCM/SUPPLIER_ID with the value 1000, and the Vendor characteristic with the value 1050) to the shopping cart. The characteristic value that is transferred to the OCI field last, overwrites the characteristic value that was transferred first. The OCI field NEW_ITEM_VENDOR can therefore have the value 1000 or 1050, depending on which characteristic value was transferred last.

08.12.2004


Configuring Customer-Specific OCI Fields

Procedure The OCI provides several fields that are not used in the standard delivered version of SAP Catalog Content Management, for example NEW_ITEM-CUSTFIELD1. You can map characteristics to these fields in the same way as to other OCI fields.

For more information about the OCI and OCI field names, see sap.com/partners/icc/scenarios/srm/ → B2B-OCI → Open Catalog Interface.

08.12.2004


Defining the Integrated Call Structure in SAP Enterprise Buyer Use You use this procedure to define the integrated call structure in the SAP Enterprise Buyer system. This enables you to use SAP Catalog Search Engine in SAP Enterprise Buyer to search in catalogs that you created using SAP Catalog Content Management.

Prerequisites You have defined a locale for the catalogs that you want to access and have published those catalogs for those locales in SAP Catalog Content Management.

Procedure The following procedure describes the specific steps you must complete to define the integrated call structure for catalogs that you created in SAP Catalog Content Management. You must carry out these steps for every catalog that you want to use in SAP Catalog Search Engine. For a more detailed description of the steps, see the documentation for the IMG activity. ...

1. In Customizing for mySAP SRM, choose SRM Server → Master Data → Define External Web Services.

2. Create a new entry for a catalog that you created using SAP Catalog Content Management.

...

a. If you want to assign the catalog to a particular purchasing organization, enter the organization in the Purch. Organization field.

b. Set the indicators for the OCI features as appropriate:

To use the DETAIL feature, set the Display Product Data Again in Catalog indicator.

To use the VALIDATE feature, set the Validate Product Data from SAP Enterprise Buyer indicator.

To use the BACKGROUND SEARCH feature, set the Cross-Catalog Search indicator.

The system always displays the detail view (displaying item details for a particular item from within Enterprise Buyer) in a separate window. You cannot change this setting from within SAP Catalog Content Management.

c. Ensure that the indicator Use HTTP GET to Call Web Service is not set.

SAP Catalog Content Management supports both the GET call method and the POST call method, but we recommend that you always use the POST method.

3. Choose Integrated Call Structure:

08.12.2004


It is possible to define a standard call structure for catalogs that you create using SAP Catalog Content Management, however we do not recommend this, as these catalogs are intended to be displayed as integrated catalogs.

4. Make the following entries:

Mandatory Parameters

Name Value Type

http://<HTTP server>:<port>/sap/bc/bsp/ccm/srm_cse/main.do

URL

CATALOGID <ID of catalog as in SAP Catalog Content Management>

Fixed value

SAP-CLIENT <client in which SAP Catalog Search Engine> runs

Fixed value

SAP-LANGUAGE SY-LANGU SAP Field

locale <locale in which you published the catalog> Fixed value

5. If you want to use the OCI call to provide user names and passwords, also make the entries shown in the table below. If you want users to logon directly or using Single Sign-On, you can ignore this step.

Optional Parameters

Name Value Type

ccm-user <user-ID> Fixed value

ccm-password <password for user> Fixed value

If you use the OCI call to provide user names and passwords, these also determine the views of the catalog that the users can see.

If you use the OCI call to provide user names and passwords, you must enter a service user in the Internet Communication Framework (ICF) for SAP Catalog Search Engine, using transaction SICF. You must do this in the system in which you are running SAP Catalog Search Engine:

i. Create a user with the type Service and assign the role /CCM/CATALOG_SEARCH to that user.

ii. In transaction SICF, choose default_host → sap → bc → bsp → ccm and enter the user in service srm_cse

Enterprise Buyer uses the service user as the logon user when it calls a session of SAP Catalog Search Engine. As a result, the system checks the user and password that you entered in Define External Web Services and determines the correct view for the user.

For security reasons, we recommend that you use named users in SAP Catalog Search Engine and logon using Single Sign-On.

08.12.2004


6. If you want to activate the accessibility features provided by the BSP/HTMLB environment, create the parameter sap-accessibility with the value X and the type Fixed Value.

08.12.2004


Assigning Call Structure IDs to Users and Organizations Use You use this procedure to assign the integrated call structure IDs of catalogs that you have created in SAP Catalog Content Management to users or organizations in SAP Enterprise Buyer.

Prerequisites You have defined call structures, as described in the section Defining the Integrated Call Structure in SAP Enterprise Buyer.

Procedure In transaction PPOMA_BBP, use input help to assign the call structure IDs of the catalogs that you want to use, to organizations or users.

For more information about transaction PPOMA_BBP, see the section Maintaining the User Attributes in this configuration guide.

08.12.2004


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


08.12.2004


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 51], Downloading Business Objects [page 53], and SAP Note 309734.

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

1. Defining the RFC Destination [Extern]

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

3. Setting the Middleware Parameters [page 49]

4. Downloading Customizing Objects [page 51]

5. Downloading Business Objects [page 53]

Result The replication of the materials is complete.

For more information, see:

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

08.12.2004


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 read and implemented:

• Defining the RFC Destination and Logical System [Extern]

• SAP Note 720819

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 in mySAP.com Systems (CRM, EBP, APO, BW, SEM…)

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

2.

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.

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.

08.12.2004


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 roles you have been assigned authorize you to use transaction SMOEAC.

• You have completed the following:

Defining the RFC Destination [Extern]

Customizing Material Replication in Enterprise Buyer [page 48]

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.

See also SAP Note 720819, Middleware consumer entry for SRM 4.0 in the OLTP.

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. See also SAP Note 720819.

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

08.12.2004


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 519794 , EBP: Replication of Materials exclusively for Purchasing.

08.12.2004


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.

Prerequisites You have completed the following steps:

• Defining the RFC Destination [Extern]

• Customizing Material Replication in Enterprise Buyer [page 48]

• Setting the Middleware Parameters [page 49]

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.

08.12.2004


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.

08.12.2004


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.


• Defining the RFC Destination [Extern]

• Customizing Material Replication in Enterprise Buyer [page 48]

• Setting the Middleware Parameters [page 49]

• Downloading Customizing Objects [page 51]

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.

08.12.2004


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).

08.12.2004


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, e.g.:

• Organizational Unit Customizing

• Master Data Customizing

• Process Customizing


08.12.2004


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.

08.12.2004


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.


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 Change.

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 All Roles

3. Enter SAP_EC_BBP*

4. Choose

08.12.2004


Creating the Organizational Plan

Prerequisites You must first make settings for External Locations (see Making Settings for Locations and External Business Partners [page 67]).

Procedure

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. For information about the recommended profile for this user, see SAP note 642202, EBP user admin: RFC user profile in back end/plug-in.

2. Assign this user the administrator role SAP_BBP_STAL_ADMINISTRATOR.

3. 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!

4. Using the Web application, transaction Manage User Data, 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.

08.12.2004


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.

After the managers have been created via the web application, check PPOMA_BBP to make sure that all the users have been attached to the appropriate organizational units. Make sure that the indicator is set for the Head of Own Organizational unit check box for each manager.

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

6. 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 → Match Up Organizational Units and Persons with Business Partners

You first have to set up the integration with organizational management.

See menu path in the SAP Implementation Guide:

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Organizational Management → Integration Business Partner – Organizational Management → Set Up Integration with Organizational Management

If errors occur for any of the organizational root nodes, select the node in the Object Overview screen (on the right side), and click on Start Resynchronization.

Procedure button . You first need to consider the error messages and correct them in PPOMA_BBP, for example, then you can execute the resynchronization.

We recommend that you define the attributes VENDOR_ACS (Accounting system for the vendor) and VENDOR_SYS (System alias for vendor) at a high level in the organizational plan.

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

7. 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.

08.12.2004


Examples 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:

Classic Scenario

Root organizational unit

Vendor (root node)

Backend purchasinggroup 1

Backend purchasingorganization



Administrator

Manager

ManagerManager

Company

Department 1 Purchasing department 1

Department 2

Employee w ith purchasing activities

‚is Purchaser of ‘

Professional Purchaser with sourcing activities

Extended Classic Scenario

08.12.2004



Vendor (root node)

Purchasinggroup 1

Backend purchasingorganization


Administrator

Manager

Manager

Manager

Manager

Company

Department 1 Purchasing department

Local purchasingorganization

Purchasinggroup 2

Purchaser


Enhancing the Organizational Plan To make the connection between purchasing organizations and purchasing groups more flexible, you can lessen the hierarchical restrictions of the organizational model by activating the BAdI Display of Input Helps, Search Helps, and Favorites and by deactivating the checks in the method layer using the IMG activity Influence Message Control. In this case, the hierarchical restrictions only have default character.

Menu path in the SAP Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Business-Add-Ins (BAdIs) → Interface Configuration → Input Helps and Search Helps → Display of Input Helps, Search Helps and Favorites

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Message Control → Influence Message Control

Employees that are assigned to the line organization of the HR organizational model and simultaneously work as purchasers in an SRM purchasing organization can be assigned to the new relationship type “Is Purchaser of…”.

In the Purchasing View of transaction PPOMA_BBP you have several possibilities to assign the purchaser to a purchasing group:

• Via drag and drop within the hierarchy

• Via drag and drop from the selection area into the hierarchy

• Using the Assign button and the search help to find the object to be assigned to the selected unit in the hierarchy.

08.12.2004



Purchasing organization

Purchasinggroup 1

Company

Department 1 Purchasing departmentPurchasinggroup 2

Purchaser

‚is Purchaser of‘

08.12.2004


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

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.)

08.12.2004


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 category: 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.

The attribute RESP_PRCAT is on the tab card Responsibility

The other purchasing org. related attributes mentioned above are on the tab card Function.

• Currency: CUR

• Plant: WRK (on the tab card Extended Attributes → Locations)

• 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 the Enterprise Buyer documentation at http://help.sap.com.

See also:

Maintaining User Attributes in the SAP Enterprise Buyer documentation.

08.12.2004


Shopping on Behalf of Other Users Use Purchasing assistants and purchasers can buy products on behalf of other users, for example, their managers. This can be of advantage to managers as it saves them time that they could use for more strategic tasks. It can also be advantageous when employees are absent, or have not yet started in the company, but still need certain products such as PC configuration, for example. It allows more flexibility in the procurement process.

Procedure The users for whom other users can shop must be specified as values for the attribute REQUESTER in the organizational structure.

For more information, see the documentation in the Implementation Guide (IMG) for Supplier Relationship Management: SRM Server → Cross-Application Basic Settings → Organizational Management → Change Organizational Plan

You can only shop on behalf of another colleague using the extended form [Extern].

See also For more information please refer to the online help (SAP library) chapter mySAP Supplier Relationship Management → Operational Procurement → Self-Service Procurement → Shop → Shopping on Behalf of Other Users

08.12.2004


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

08.12.2004


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


• 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 SAP Web Application Server → Web Application Server → 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

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.

08.12.2004


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.

For further information refer to SAP Note 563180, Locations for EBP 4.0 – plant replication

External Business Partners

Prerequisites ...

1. 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 58]

2. You must first create Business Number Ranges and Groupings. See section Business Partner Number Ranges in Defining Number Ranges [page 79]

The Internal Business Number Range should NOT conflict with the External Number Range for Vendors.

Procedure ...

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 Managing External Business Partners at http://help.sap.com.

2. 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 (IMG) under Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Organizational Management → Integration Business Partner – Organizational Management → Schedule Periodic Comparison.

08.12.2004


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

08.12.2004


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

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

You need to execute the following transactions:

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

• Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → SAP Business Workflow → Activate Standard Tasks

If the workflow is not working as expected, refer to SAP Note 322526, Analysis for workflow problems.

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 58].

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 57].

Procedure ...

You activate the specific workflows by activating the event linkage.

Activate the event linkage of those workflows that you want to use in your scenario. See Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → SAP Business Workflow → Perform Task-Specific Customizing

a. Expand the SRM folder

b. Expand the SRM-EBP folder

c. Go to folder SRM-EBP-WFL

d. Click on the link Activate event linking associated with this folder.

Workflows with delivered Start Conditions: Event Linkages and delivered Start Conditions per Workflow listed according to Business Objects (by Delivery)

Business Object

Triggering Event(s) Workflows belonging to Business Object

Event Linkage (by Default) Activated

Start Conditions (by Default)Activated 1)

2)

BUS2121 (Shopping Cart)

SAVED WS10000060 (auto approval)

No No

WS10000129 (one-step approval)

No No

WS10000031 No No

08.12.2004


Business Object




2) (two-step approval)

WS10000276 (spending limit approval)

No No

WS14000044 (completion by purchaser)

No No

BUS2201 (Purchase Order)

SAVED/ CHANGEVERSIONSAVED

WS14000075 (auto approval)

Yes No


No No

BUS2209 (Purchase Order Response)


Yes Yes

WS14500019 (transfer by purchaser)

Yes Yes

WS14500007 (mail if POR differs from PO)

No No

BUS2203 (Confirmation)

SAVED WS10400002 (one-step approval)

Yes Yes

WS10400009 (two-step approval)

Yes Yes


Yes Yes

WS10400020 (administrator approval)

Yes Yes

BUS2205 (Invoice)


Yes Yes


Yes Yes

WS10400018 (two-step approval)

Yes Yes

WS10400021 (administrator approval)

Yes Yes

08.12.2004


Business Object




2)

BUS2000113 (Contract)

SAVED/ CHANGEVERSIONSAVED


Yes No


No No

BUS2202 (Vendor Bid)

TOBEACCEPTED WS79000010 (auto approval)

Yes No


No No

1) start condition activation is required, if several workflows are assigned to the same business object and triggering event 2) if you activate a start condition, the event linkage of the related workflow is activated automatically

If an event linkage is activated and the corresponding start condition is not activated, the workflow is started every time the event occurs (and the start condition rules are not followed).

Workflows without delivered Start Conditions: You can use the following workflows too (optional):

Business Object (BO)

Triggering Event(s) Workflow Template

Event Linkages (by Default) Activated?

Start ConditionsRequired? 3)

BUS2121 (Shopping Cart)

SAVED WS14000109 (n-step spending limit approval)

No Yes 3)

WS14500015 (line-item approval)

No Yes 3)

WS14000045 (delete SC item after application error)

No No

WS10000202 (transfer PM requisition)

No No

WS10000215 (resubmit SC item by administrator)

No No

08.12.2004


BUS2201 (Purchase Order)

SAVED/ CHANGEVERSIONSAVED WS14000145 (n-step approval)

No Yes 3)

BUS2209 (Purchase Order Response)

SUBMITTED WS14500017 (alert POR expected)

No No

BUS2205 (Invoice)

ERRORINVOICETOBEPROCESSED WS14500020 (error correction)

Yes No

BUS2000113 (Contract)

ALERTBUSINESSWAREHOUSE WS10400022 (contract alert)

No No

BUS2200 (Bid Invitation)

EXTERNALAUCTIONSTARTED WS14000091 (alert WFL)

No No

BUS1006200 (Business Partner)

COMPLETED WS14000043 (auto approval)

Yes No


Yes No

WS14500021 (BP locked)

Yes No

BBP_PCARD (Procurement Card)

APPROVECHARGES1 WS10000093 (one-step approval)

No No

APPROVECHARGES2 WS10000100 (two-step approval)

No No

BUS4101 (User)

SAVED WS10000192 (approve new user) Depends on IMG setting Set Approval Indicator!

No No

NEWPASSWORD WS10000223 (approve new password) Depends on IMG setting Set Approval Indicator!

No No

BUS2203 (Confirmation)

RETURN WS10001048 (notify vendor at good return)

No No

BUS22101 (Request for Bidder Registration)

CREATED WS10000209 (approve vendor or bidder)

No No

08.12.2004


3) create and activate start conditions, if several workflows are assigned to the same business object and triggering event

You must define start conditions for some of the workflows before you can execute them.

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. 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

The delivered or changed start conditions must be activated I order that the workflow runs!

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 (auto 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.

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.

Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → SAP Business Workflow → Perform Task-Specific Customizing

e. Expand the SRM folder

f. Expand the SRM-EBP folder

08.12.2004


g. Go to folder SRM-EBP-WFL

h. Click on the link Assign Agents associated with this folder.

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

You have to assign a processor to the following tasks:

Task (Description)

Used/ Usable in Workflow

Processor (Type of task Agent Assignment)

TS10007947 (approve charges of P-Card)

WS10000093 General task

TS10008024 (approve new user)

WS10000192 Manager role or Administrator

TS10008054 (approve new password)

WS10000223 Manager role or general task

TS10008061 (ask whether requester accepts rejection of SC)


TS10008069 (1st approval task in two-step approval of SC)


TS10008109 (approve vendor or bidder)

WS10000209 Administrator or purchaser

TS10008125 (approve new user)


TS10008126 (approval task in one-step approval of SC)

WS10000129

WS10000276

Manager role or general task

TS10008127 (2nd approval task in two-step approval of SC)


TS10008212 (check SC by reviewer)


TS10008214 (approval task to insert in approval of SC)


TS10107914 (present changes in SC to requestor)

WS10000031

WS10000060

General task

TS10407914 (approval task in one-step approval of GR)


TS10407915 (1st approval task in two-step approval of GR)


TS10407916 WS10400011 Manager role or general task

08.12.2004


(check GR by reviewer)

TS10407917 (approval task to insert in approval of GR)


TS10407918 (approval task to insert in approval of INV)


TS10407919 (check INV by reviewer)


TS10407920 (approval task in one-step approval of INV)


TS10407921 (1st approval task in two-step approval of INV)


TS10407922 (2nd approval task in two-step approval of GR)


TS10407923 (2nd approval task in two-step approval of INV)


TS10407924 (administrator approval task for GR)

WS10400020 Administrator

TS10407925 (administrator approval task for INV)

WS10400021 Administrator

TS10407926 (check CTR in alert workflow)


TS10407972 (change rejected SC)

WS10000031

WS10000060

General task

TS14007938 (present changes to creator of SC)

WS10000060

WS10000129

WS10000031

WS10000276

WS14000044

WS14000109

WS14500015

General task

TS14007942 (approve creation of vendor)


TS14007947 (completion task of SC)


TS14007969 (approval task in one-step approval of CTR)


TS14007970 (approval task in one-step


08.12.2004


approval of PO)

TS14008026 (approval task to insert in approval of PO)


TS14008027 (check PO by approver)


TS14008028 (send PO back to purchaser)


TS14508055 (transfer POR data to PO)


TS14508056 (correct erroneous invoice)


TS79007914 (approval task in one-step approval of bid)

WS79000002 Manager role

SC: Shopping Cart, PO: Purchase Order, POR: Purchase Order Response, GR: Goods Receipt (Confirmation), CTR: Contract, INV: Invoice

Authorization to change/ insert 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 auto approval (shopping cart)

WS10000271 - Approval fragment for anchor

WS10400002 - One-step approval goods receipt

WS10400008 - Approval fragment to insert in approval of goods receipt

WS10400009 - Two-step approval goods receipt

WS10400010 - Workflow auto approval goods receipt

WS10400016 - Invoice auto approval

WS10400017 - One-step approval invoice

WS10400018 - Two-step approval invoice

WS10400020 - Approval goods receipt by administrator

WS10400021 - Approval invoice by administrator

WS14000075 – Auto approval PO

WS14000089 – One-step approval PO

WS14000145 – N-step approval PO

WS14000002 – Approval fragment to insert in approval of PO

WS14000154 – Reviewer workflow for PO

08.12.2004


For more information, see the Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → SAP Business Workflow → Perform Task-Specific Customizing

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

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.

08.12.2004


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

• Purchase contracts

• Purchase order responses

• Confirmations for goods and services

• Invoices

If you create materials management documents in the backend system, you also determine in Enterprise Buyer the internal number range for :

• Purchase requisitions

• Purchase orders

• Reservations

This is then used in the backend system as an external number range

You can define different number ranges for different backend systems.

The number range interval for a backend document, for example, a backend purchase order, must be the same as in the internal number range that you use for the local document in the SRM system. The number range in the backend system must use external number assignment.

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

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Number Ranges → SRM Server Number Ranges → Define Number Ranges for Shopping Carts and Follow-On Documents

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.

08.12.2004


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

08.12.2004


Defining Transaction Types Use In this section you can 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.

You do not have to create new transaction types for Self-Service Procurement. Use the default transaction type for the transaction object types Shopping Cart, Confirmation, and Invoice.

If corresponding settings have been made in the organizational plan for the particular user, these will overrule the settings you make here. To check these, go to transaction PPOMA_BBP and view the attributes there. For more information, see the section Maintaining the User Attributes.

Procedure ...

1. Go to the SAP Implementation Guide (IMG) for Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Define Transaction Types.

2. Choose the business transaction category for which you want to define a transaction type.

3. Double click on Transaction Type in the side menu.

4. Double click on a transaction type to display the fields for definition.

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

08.12.2004


Making Settings for Account Assignment Use In this section you make the relevant account assignment settings.

Prerequisites • The accounts needed have been defined.

• The account assignment categories have been defined.

Procedure ...

1. Select account assignment categories.

You can select the required account assignment categories from a preconfigured list. To do this, go to the Implementation Guide (IMG) for Supplier Relationship Management and choose SRM Server → Cross-Application Basic Settings → Account Assignment → Define Account Assignment Categories.

2. Map account assignment categories

You map R/3 account assignment categories to the SAP Enterprise Buyer categories. To do this, go to IMG for Supplier Relationship Management and choose SRM Server → Cross-Application Basic Settings → Account Assignment → Define Account Assignment Categories.

3. Change account assignment categories.

You can change account assignment categories using Business Add-Ins. To do this to go the IMG for Supplier Relationship Management and choose SRM Server → Business Add-Ins → Account Assignment. Then choose Change Account Assignment Category when Creating Backend Documents or Change Account Assignment Category when Importing Backend Documents.

4. Define 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 assignment category. To do this go to the IMG for Supplier Relationship Management and choose SRM Server → Cross-Application Basic Settings → Account Assignment → Define G/L Account for Product Category and Account Assignment Category.

Alternatively, you can define your own criteria for determining the G/L account using a Business Add-In. To do this, go to the IMG under SRM Server → Business Add-Ins → Account Assignment → Determine G/L Account.

08.12.2004


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 BBPV_PTERM_LOCAL for local terms of payment and tables BBP_PAYTERM and BBP_PAYTERM_TEXT for backend payment terms.

The input help will display only those terms of payment that have a description in table BBP_PAYTERM_TEXT (backend table T052U).

Path in the SAP 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.

Refer to the above-mentioned path in the IMG.

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.

We recommend 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.

08.12.2004


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

from R/3 Backend Systems [page 47].

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

08.12.2004


Making Settings for Confirmations

• 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.

• In the default delivery you cannot create return deliveries if the invoice has already been entered. If you want to implement this possibility, you can switch off the Customizable message BBP_PD 233 “Activity not possible. Follow-on documents exist.” . In this case, return deliveries can be created in spite of already entered invoices.

For more information see menu path in the SAP Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Message Control → Influence Message Control

• You need to define the number ranges for confirmations for goods receipts. The transaction type for confirmations is CONF.

For more information see menu path in the SAP Implementation Guide (IMG): Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Number Ranges → SRM Server Number Ranges

• If confirmations should be sent via XML, see the following BAdIs in the SAP Implementation Guide (IMG):

Supplier Relationship Management → SRM Server → Business Add-Ins (BAdIs) → Confirmation and Invoice Verification → Define Target System for Sending of Confirmation

And

Supplier Relationship Management → SRM Server → Business Add-Ins (BAdIs) → Confirmation and Invoice Verification → Send Confirmation via XML

08.12.2004


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 [Extern]

Defining number ranges Define the number ranges for local invoices.

Defining Number Ranges [page 79]

Defining the transaction type Define the transaction type for invoices or credit memos.

Defining Transaction Types [page 81]

Making settings for account assignment

Make the settings necessary for account assignment.

Making Settings for Account Assignment [Extern]

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 Schema for User Status

Workflow: Perform task-specific Customizing

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


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

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

08.12.2004


documentation SAP Enterprise Buyer.

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

You want to assign an account assignment

Menu path in the SAP

08.12.2004


backend documents category in the Enterprise Buyer system to multiple account assignment categories in different backend systems.

Implementation Guide (IMG):

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

You want to assign the 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.

08.12.2004


Procurement Card Use In the SAP Enterprise Buyer system, you can specify procurement cards as the payment method when you purchase items, provided you are using the SAP Materials Management functions in SAP Enterprise Buyer. In addition, you can manage settlements for purchases made using a procurement card. This means, you can transfer the settlement file that the bank or card company sends you to the SAP Enterprise Buyer system to check that the contents are correct and specify account assignments.

Prerequisites • You must be using the SAP Materials Management functions in the SAP Enterprise

Buyer component.

• In the backend system, Accounting should be set up and the card company should be created as a vendor.

Procedure ...

1. Enter your procurement card details using the Create User transaction

2. The settlement files are transferred to the SAP Enterprise Buyer System and invoices and transaction figures are transferred from the SAP Enterprise Buyer system to the backend system via the ALE interface.

You have set up the ALE distribution model in Customizing for the Enterprise Buyer System and the backend system in the Implementation Guide (IMG) for Supplier Relationship Management: SRM Server → Technical Basic Settings → ALE Settings (Logical System)

3. The procurement cards have to be set up so that the system can transfer the settlement information from the card company and carry out updates in Accounting in the backend system

You can use the information on the procurement cards to control the postings in Accounting and validate the procurement card numbers on the bank’s settlement file. This information also provides an overview of the cards issued, the assignment of cards to employees and an overview of information such as the transaction limit or overall limit of a card and the approval workflow. Go to the IMG for Supplier Relationship Management: SRM Server → Procurement Card

4. If you want to create commitments, you must specify this in Customizing in the IMG for Supplier Relationship Management: SRM Server → Procurement Card → Manage Commitments

See also For more information please refer to the online help (SAP library) chapter mySAP Supplier Relationship Management → Operational Procurement → Self-Service Procurement → Shop (Self-Service) → Procurement Card Process Flow and its subchapters.

08.12.2004


Navigation Interfaces of Shopping Cart Use In the Shop application, three navigation interfaces have been developed with different types of user (purchaser, employee, and so on) in mind. These three navigation interfaces are called:

• Wizard

• Extended Form

• Simplified Form

Purchasers or purchasing assistants can use the Extended Form navigation interface to fill shopping carts with products quickly and easily. Employees can order products simply using the Simplified Form navigation interface. The default navigation interface for the employee is the Wizard, though this setting can be changed in Customizing

Prerequisite • The backend system, catalogs and users are defined and set up accordingly.

• If you want to use procurement cards, the system requires additional settings.

These have to have been configured in the Implementation Guide (IMG) for

Supplier Relationship Management → SRM Server → Procurement Card

Purchase orders have to be created locally in the SAP Enterprise Buyer system

The vendor must accept these procurement cards (see Business Partner [Extern])

The procurement card data must exist for the user that places the orders. This data can be entered when requesting a user master record or at a later date using the Settings function.

Procedure ...

1. To change interface settings go to the IMG for Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Roles → Define Roles

2. To override standard settings, you can use the Business Add-In (BAdI) Change Display in Shopping Cart. To tailor the interface to fit your individual requirements, go to the IMG for Supplier Relationship Management → SRM Server → Business Add-Ins (BAdIs) → Shopping Cart and requirement Items → Change Display in Shopping Cart

See also

For more information see the online help (SAP library) chapter mySAP Supplier Relationship Management → Operational Procurement → Self-Service Procurement → Shop (Self-Service) → Shopping Cart (Wizard)

See also mySAP Supplier Relationship Management → Operational Procurement → Self-Service Procurement → Shop (Self-Service) → Shopping Cart (Simplified and Extended Form)

For more information about procurement cards see the online help (SAP library) chapter mySAP Supplier Relationship Management → Operational Procurement → Self-Service

08.12.2004


Procurement → Shop (Self-Service) → Procurement Card Process Flow or Procurement Card [page 89] in this document.

08.12.2004



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.

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

08.12.2004


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

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.

Activation of SAP BW Links in Application Context

In order to activate the links, you first have to maintain the connection to the BW system in the SAP Enterprise Buyer system. Then you have to assign the different reports to the links in the Implementation Guide (IMG) for mySAP SRM under SRM Server → Cross-Application Basic Settings → Define Logical Systems and Template Names for BW reports

For information on the BW reports Comparison of Bidders by Product Category, Vendor Evaluation in SRM, Simple Price Comparison and Bid Comparison of Attributes see chapter Activation of SAP BW Links in Application Context in the Configuration Guide Reporting for SAP Bidding Engine at SAP Service Marketplace\srm → mySAP SRM in Detail → SRM 3.0 → Components in Detail → Business Information Warehouse → Implementation Information

Settings in BW

08.12.2004



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_ACT_PURREP, and then activating In data flow

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

08.12.2004


before, and after.

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 must also activate the end user role SAP_BW_SRM_OPER_PURCHASER with Only necessary objects.

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.

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

08.12.2004


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.