Sunteți pe pagina 1din 68

Service Procurement:

Configuration Guide

ADDON.SRM_SSSCONGUIDE

Release SRM 4.0


SAP Online Help 21.04.2005

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.

Service Procurement: Configuration Guide 2005 2


SAP Online Help 21.04.2005

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.

Service Procurement: Configuration Guide 2005 3


SAP Online Help 21.04.2005

Service Procurement: Configuration Guide............................................................................... 6


mySAP.com Solution and Business Scenario Documentation Landscape ......................... 11
SAP Notes............................................................................................................................ 13
General Settings .................................................................................................................. 14
Aligning Units of Measurement, Currencies, and Exchange Rates ................................. 15
Scheduling Reports .......................................................................................................... 16
Setting Up Services for SAP Supplier Self-Services........................................................ 18
Setting Up Attachments.................................................................................................... 21
Configuring SUS User Management................................................................................ 22
System Connections ............................................................................................................ 25
Defining Logical Systems and RFC Destinations............................................................. 26
Defining XI Settings.......................................................................................................... 28
Configuring the System Landscape Directory (SLD).................................................... 30
Configuring Communication and Security .................................................................... 32
Importing Business Scenarios ...................................................................................... 33
Checking XI Settings .................................................................................................... 35
Business Customizing.......................................................................................................... 37
Organization Configuration............................................................................................... 38
Regenerating Role Profiles........................................................................................... 38
Creating the Organizational Plan.................................................................................. 39
Defining Organizational Plans for Suppliers ................................................................. 41
Making Settings for Creating Internal Users................................................................. 43
Maintaining User Attributes........................................................................................... 44
Process Configuration ...................................................................................................... 45
Defining Number Ranges ............................................................................................. 45
Defining Transaction Types .......................................................................................... 46
Making Settings for Account Assignment ..................................................................... 47
Defining Technical Settings for E-Mail.......................................................................... 48
Configuring SAP Supplier Self-Services .......................................................................... 49
Making Settings for Business Partners......................................................................... 51
Defining Backend Systems........................................................................................... 52
Defining Customer Settings .......................................................................................... 54
Defining Tax Calculation............................................................................................... 55
Defining Analytics Settings for SAP SUS ..................................................................... 56
Configuring SAP Enterprise Buyer................................................................................... 57
Defining Master Data in SAP Enterprise Buyer and SUS ............................................ 58
Creating Payment Conditions ....................................................................................... 60
Defining Message Control for Limit POs ...................................................................... 61
Setting Up SAP Business Workflow ............................................................................. 62

Service Procurement: Configuration Guide 2005 4


SAP Online Help 21.04.2005

Configuring Link to Service Agent List in EBP.............................................................. 63


Making Settings for Confirmations and Invoices .......................................................... 64
Making Settings for Evaluated Receipt Settlement (ERS) ........................................... 65
Making Settings for Replication of Vendor Master Records......................................... 66
Making Settings for Requests for External Staff........................................................... 67

Service Procurement: Configuration Guide 2005 5


SAP Online Help 21.04.2005

Service Procurement: Configuration Guide


Business Scenario
This business scenario configuration guide applies to the business scenario Service
Procurement with the corresponding releases of its mySAP.com application components.

Business Scenario and mySAP.com application components

Business Scenario mySAP.com application component with


minimum release
Service Procurement SAP SRM Server 5.0
SAP Exchange Infrastructure 3.0

Service Procurement Component View

Process Request for External Staff

Service Procurement: Configuration Guide 2005 6


SAP Online Help 21.04.2005

Process Requirements

Order Management (1/3)

Service Procurement: Configuration Guide 2005 7


SAP Online Help 21.04.2005

Order Management (2/3)

Service Procurement: Configuration Guide 2005 8


SAP Online Help 21.04.2005

Order Management (3/3)

To be able to configure the Service Procurement business scenario, you must


first
configure the Self-Service Procurement business scenario.

Please note that the Service Procurement business scenario is a standalone


scenario that
must be connected to a FI backend system. As a result, the following sections in
the
Business Scenario Configuration Guide for Self-Service Procurement are not
applicable.
ƒ Configuring SAP Catalog Content Management (including subsections)
ƒ Data replication (including subsections)
For the Business Scenario Configuration Guide for Self-Service Procurement,
see the SAP Service Marketplace at service.sap.com/ibc-srm → Self-
Service Procurement → Business Scenario Configuration Guide

Service Procurement: Configuration Guide 2005 9


SAP Online Help 21.04.2005

Contents
The business scenario configuration guide contains all steps required to implement the
Service Procurement business scenario. The guide specifies the sequence of the
configuration activities, and their dependencies.
It includes information about the following topics:
• General Settings
• System Connections
• Business Customizing
For further information about the Service Procurement business scenario, see the SAP
Service Marketplace at service.sap.com/ibc → mySAP SRM.

Target group
• Technical consultants
• Application consultants
• Project team members during the implementation of an SAP solution
• SAP customer IT department
The System Connections section is aimed at technical consultants in particular, while the
Business Customizing section is aimed at application consultants. The remaining sections are
of equal interest to both groups of consultants. The importance of sections to the other target
groups depends on their responsibilities.

It is a prerequisite that consultants have completed all relevant training courses


before starting to work with this guide.

Integration
Documentation Landscape for SAP Solutions and Business Scenarios
The system landscape has already been created using the Master Guide and other
documentation. For more information about other relevant documentation, see
Documentation Landscape for SAP Solutions and Business Scenarios.

Business Scenario Configuration Guide Feedback


Your feedback can help us to continually improve the business scenario configuration guide.
If you find errors in the configuration guide, please send a message in the SAP Service
Marketplace under service.sap.com/message.

Service Procurement: Configuration Guide 2005 10


SAP Online Help 21.04.2005

mySAP.com Solution and Business Scenario


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

All quicklinks are listed in SAP Service Marketplace at


service.sap.com/quicklinks.
Current documents
Document Quick Link to the SAP Service
Marketplace (service.sap.com)
Master Guide, Installation and Upgrade installation → Installation and Upgrade
Guides Guides
ibc
Business Scenario Description ibc
Business Scenario Configuration Guide ibc
Implementation Guide (IMG) Note: in the SAP system, not in SAP Service
Marketplace
SAP Library helpportal with all releases of a
mySAP.com component
Note: available in the SAP system under Help
→ SAP Library
The following information supplements the individual documents:

Current supplementary information

Information Quick Link to the SAP Service


Marketplace (service.sap.com)
SAP notes notes to the note search
instguides listed by installation and
upgrade guide
Technical infrastructure (for example ti
hardware sizing, platforms, network security)

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

Master Guide, Installation and Upgrade Guides


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

Service Procurement: Configuration Guide 2005 11


SAP Online Help 21.04.2005

Business Scenario Description


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

Business Scenario Configuration Guide


This document describes the settings you use to configure the 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. Configuration activities can be
IMG activities, SAP system transactions, organizational activities, etc.

Implementation Guide (IMG)


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

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

Service Procurement: Configuration Guide 2005 12


SAP Online Help 21.04.2005

SAP Notes
Use
Before you start to configure this business scenario, consult the following SAP notes. This
summary only contains central SAP notes, to give you an initial overview.

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

Central SAP Notes for the Business Scenario

Note Number Title


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
769901 (RIN) SRM 4.0 SP stack 10/2004: Release and information note
790376 (RIN) SRM 4.0 SR01
705541 XI 3.0 (SP01 and following): Importing XI content
455140 Configuration E-mail, fax, paging/SMS via SMTP
707701 SRM-SUS: Upgrade from SUS 1.0 or SUS 2.0

Service Procurement: Configuration Guide 2005 13


SAP Online Help 21.04.2005

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

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.

Service Procurement: Configuration Guide 2005 14


SAP Online Help 21.04.2005

Aligning Units of Measurement, Currencies, and


Exchange Rates
Use
The units of measurement (UOMs), currencies, and exchange rates in the SAP Enterprise
Buyer system must be identical with the UOMs, currencies, and exchange rates in the
backend system.

Procedure
Perform the following steps in the SAP Enterprise Buyer system and in the SAP Supplier Self-
Services system:

Checking Units of Measurement


Transaction code SPRO
IMG path SAP Web Application Server → General
Settings → Check Units of Measurement.
Make sure that the contents in the IMG activity Check Units of Measurement are identical in
SAP Enterprise Buyer and in the backend system.

Adjusting currencies and exchange rates


Only if an SAP FI backend system is used, run the following reports:
• BBP_GET_CURRENCY
• BBP_GET_EXRATE
These reports adjust the currencies and exchange rates in the backend system with those in
the SAP Enterprise Buyer system, whenever currencies and exchange rates are updated in
the backend system.

Assigning ISO codes


Transaction code SPRO
IMG path SAP Web Application Server → General
settings → Check Units of Measurement
Assign the relevant ISO codes, especially if you have connected catalogs.

Service Procurement: Configuration Guide 2005 15


SAP Online Help 21.04.2005

Scheduling Reports
To ensure that the documents have the proper status and are available in the respective
systems we recommend that you schedule various reports periodically.
Scheduling Reports
Report Name Description Required/
optional
CLEAN_REQREQ_UP (and Updating of documents Required
START_CLEANER) (purchase requisitions,
purchase orders,
reservations) is
executed
asynchronously in the
backend system. You
cannot process the
shopping cart in the
SAP Enterprise Buyer
system until the update
has been carried out.
Use transaction SA38
to schedule report
CLEAN_REQREQ_UP
to run periodically (for
example every 2
minutes). Create a
variant with only a
logical system name,
and schedule this job
with this variant.
If you previously used
the report
START_CLEANER,
you can also use
transaction SA38 to
schedule this report.
BBP_GET_STATUS_2 This report updates Required
shopping carts.
To ensure that
information on the
status of purchase
requisitions, purchase
orders, and
reservations is up to
date, use transaction
SA38 to schedule this
report to run
periodically (for
example every 2
minutes) in the SAP
Enterprise Buyer
system. Create a
variant, and schedule
this job with the
variant.

Service Procurement: Configuration Guide 2005 16


SAP Online Help 21.04.2005

RSPPFPROCESS If the purchase orders Optional


are to be transferred to
the vendors, schedule
this report to run at
regular intervals.

Do not schedule this


report if you have
selected Processing
when saving document
for the Action Profile in
the IMG activity Define
Actions for Purchase
Order Output. You
make this setting in the
Time of Processing
field of the Action
Definition box on the
Action Settings tab
page.
BBPERS If you use Evaluated Required if
Receipt Settlement ERS is used
(ERS) for local
purchase orders for
which confirmations
exist, you have to start
BBPERS.
BBP_DELETE_LOCAL_ACCOUNT This report updates Optional
account assignment
tables and deletes
those account
assignment objects
that are no longer
valid, that is when the
expiration date has
passed.

Service Procurement: Configuration Guide 2005 17


SAP Online Help 21.04.2005

Setting Up Services for SAP Supplier Self-Services


Use
You need to make the following settings to use Business Server Pages (BSP) as user
interface and start self-registration directly. You define a user called sus_service, which is
to be used for anonymous login for the self-registration.
For more information about Activation of SICF services, see SAP Service Marketplace at
service.sap.com/instguides → SAP NetWeaver → Release 04 → Installation →
Configuration Guide – SAP XI 3.0, section 6.

Procedure
Perform the following steps in the SAP Supplier Self-Services (SAP SUS) system:

Creating and Assigning User


Transaction code SU01
...

1. Enter a user name, for example sus_service.


2. Choose Create.
3. Choose the Logon data tab page and set the Service indicator in the User Type screen
area.
4. Choose the Roles tab page and assign the following roles:
{ SAP_BC_BASIS_MONITORING
{ SAP_EC_SUS_ADMIN_VENDOR
5. Save your entries.

Activating SICF Services


Transaction code SICF
...

For more information about inactive services in the Internet Communication, see
SAP Note 517484.
Activate the following SICF services for SAP SUS by choosing Activate Service in the
context menu <name_of_virtual_host>:
{ → sap → bc → bsp → sap → system: System Services Business
Server Pages
{ → sap → bc → bsp → sap→ public → bc: Basis Mime Objects
{ → sap → public → bsp → sap → public → bc: Basis Mime Objects
{ → sap → public → bsp → sap → system: System Services Business
Server Pages
{ → sap → public → bsp → sap → htmlb: HTMLB Public Handler
{ → sap → public → bc
{ → sap → public → bc → ur
{ → sap → bc → bsp → sap → srmsus: SUS Supplier Self-Services
{ → sap → bc → bsp → sap → srmsus_selfreg

Service Procurement: Configuration Guide 2005 18


SAP Online Help 21.04.2005

{ → sap → bc → bsp → sap → bbp_sus_sagent (only relevant for Service


Procurement)

Creating Aliases
Transaction code SICF
...

Creating an alias for supplier self-registration


...

1. Choose External Aliases.


2. Right-click the according virtual host and choose Create External Aliases.
The Maintain external aliases dialog box appears.
3. Enter an appropriate name in the External Alias field, for example /sus_selfreg.
4. On the Service data tab page, enter the name of the user you created before (see
“Creating and Assigning User”), for example sus_service.
5. Enter a password.
6. Choose the Trg Element tab page and enter the service target by choosing a node in
the Virt. Host / Services selection tree as follows:
<name of virtual host> → sap → bc → bsp → sap → srmsus_selfreg
7. Save your entries.
8. Test the SICF service, for example by calling
http://<hostname>:<port>/sap/bc/bsp/sap/srmsus_selfreg. Make sure
that the URL in the e-mail takes you to the supplier registration page.

Creating an alias for service agent

Perform the following steps only for the Service Procurement business scenario.
...

1. Choose External Aliases.


2. Right-click the according virtual host and choose Create External Aliases.
The Maintain external aliases dialog box appears.
3. Enter an appropriate name in the External Alias field, for example /serv_agent.
4. On the Service Data tab page, set the Alternative Logon Order indicator.
The Logon Order tab page is added to the Maintain external aliases dialog box.
5. Choose the Logon Order tab page and change the sequence number of Service
Authentication to 0.
6. Choose the Service Data tab page and enter the name of the user you created before
(see “Creating and Assigning User”).
7. Enter a password.
8. Choose the Trg Element tab page and enter the service target by choosing a node in
the Virt. Host / Services selection tree as follows:
<name of virtual host> → sap → bc → bsp → sap → bbp_sus_sagent
9. Save your entries.
10. Test the SICF service.

Adjusting URLs
Transaction code SPRO

Service Procurement: Configuration Guide 2005 19


SAP Online Help 21.04.2005

SAP Reference IMG → Supplier Relationship


Management → Supplier Self-Services →
Master Data → Making Settings for Business
Partners
...
...
...

To adjust the URL for self-registration, change the URL in the URL for UM field.

Enter the same path that you used as the external alias in “Creating an alias for
supplier self-registration”, in this case:
http://<hostname.domain>:<port>/sus_selfreg.
This URL is sent by e-mail to the corresponding user and will enable the user to start
the self-registration process.

Result
The SICF services for SAP SUS are activated.
The URL for suppliers is maintained so that the self-registration can be started directly.

Service Procurement: Configuration Guide 2005 20


SAP Online Help 21.04.2005

Setting Up Attachments
Use
To use attachments in conjunction with your purchasing documents, you first have to make
the following settings:

Procedure
...
For each client which should use the attachment service, create in the client a user in transaction SU01, for instance SERVICExxx, where xxx = Client number
In Address enter a name into last name field, content does not matter
Under Logon Data enter a password into the password and password-repeat fields
Under Logon Data set the User type to be a communication user
Save your user
To display attachments in your internet browser, make the relevant setting in the internet communication framework in transaction SICF
In transaction SICF hit the button ‚External Aliases’ to maintain aliases
For each client a new external alias has to be created do this as follows:

1. Create a user (in transaction SU01) for each client that is to use the attachment service,
for example SERVICExxx, where xxx = client number.
2. In the Address area, enter a name in the Last Name field.
3. In the Logon Data area, enter a password in the Initial password and Repeat password
fields.
4. As User Type choose communication user.
5. Save your entries.

To display attachments in the Web browser, you first have to make the following settings in
the Internet communication framework in transaction SICF:
1. Select the External Aliases pushbutton.
2. In the Virtual Hosts/Services field, choose your <virtual host>.
3. Right-click on the <virtual host> and select Create External Alias from the dialog box.
4. Enter a name for the external alias, for example /attach_<clientno.>.
5. Enter a description, for example Attachment display.
6. In the Logon Data area, enter the client number in the corresponding field.
7. Enter username and password for the respective client, as created in steps 1 to 5.
8. Save your entries.
9. Repeat steps 1 to 8 for each client.

Service Procurement: Configuration Guide 2005 21


SAP Online Help 21.04.2005

Configuring SUS User Management


Use
When administrating user data of suppliers in addition to the administration in SAP Supplier
Self-Services (SAP SUS), you can replicate the supplier user data to other components, for
example, SAP Business Information Warehouse (SAP BW) and SAP Bidding Engine.
You replicate the user data of suppliers in Supplier Relationship Management (SRM) for
Bidding or in SAP BW for Reporting (Analytics).
In this procedure, you do the following:
• Define the settings for business partners to replicate the business partner and to create
users through User Management
• Make the relevant settings for the https protocol, if required
• Adjust the roles for SUS User Management in the SUS backend, if required
• Make an upgrade from SUS 2.0 to SUS 3.0, if required

Procedure
• Perform the following steps in the SAP SUS system:

Performing SRM Administrator Setup


Go to transaction SU01, create a dialog user (for example, srm_admin), and assign the role
SAP_EC_SUS_ADMIN_PURCHASER to it.

Make sure that a valid e-mail address, first name, and last name are assigned to
this user.
The user name allows you to log in to SAP SUS, which you access via
http://<hostname>:<port>/sap/bc/bsp/sap/srmsus. Additionally, this user can act
as an SRM administrator.

The role SAP_EC_SUS_ADMIN_PURCHASER gives the user a wide range of


authorizations. So it should be handled carefully.
...

Defining Settings for the Secure Sockets Layer Protocol


For encrypting data from browser to system, you can make settings for the HTTPS protocol, if
required.
To do so, see the SAP Service Marketplace at service.sap.com/helpportal → SAP
Netweaver → Web Application Server 6.40 → mySAP Web Application Server → SAP Web
Application Server → Security → SAP Web Application Server Security → Using the Secure
Sockets Layer Protocol.

Defining Roles
IMG Path SAP Reference IMG → Supplier Relationship Management
→ Supplier Self-Services → Define roles
...

1. Choose in the IMG activity Define roles via input help one of the following roles:
• SAP_EC_SUS_ADMIN_PURCHASER

Service Procurement: Configuration Guide 2005 22


SAP Online Help 21.04.2005

• SAP_EC_SUS_ADMIN_VENDOR
• SAP_EC_SUS_DISPATCHER
• SAP_EC_SUS_INVOICER
• SAP_EC_SUS_ORDER_PROCESSOR
• SAP_EC_SUS_SERVICE_AGENT
• SAP_EC_SUS_MANAGER (Reporting)
• SAP_EC_SUS_BIDDER (Bidding)

If you want to change attributes of a role, copy the corresponding role in


transaction PFCG to a new role in the customer name space and correct this
one.
Examples for changing attributes: Authorizations or menu entries

For all roles maintained in transaction PFCG, an attribute set for SUS specific
settings exist. For maintaining this set, select the corresponding role in
transaction PFCG.
2. Choose Change role.
3. Choose the Personalization tab page.

The personalization is valid for all roles. Users can create their own roles, for
example as copy of the delivered SAP roles. Users can adjust created roles by
changing the SUS-specific role attributes.
4. Select the entry BBP_SUS_ROLES_ATTRIBUTES (SUS specific role
attributes) and choose Change values.
The system displays the Maintaining SUS specific roles dialog box.
5. Perform the following steps if necessary:
Selecting Means that
Display role in SUS UM Only these roles are displayed in the SUS
User Management. By this the supplier
administrator can assign these roles to the
respective user.
Service agent The user can be displayed as service agent
by the buyer.
SRM Administrator The user is defined as SRM Administrator. In
this role the user is authorized to maintain
any supplier user data.
SUS Administrator This role is automatically assigned to the user
while the SUS Administrator is registering
himself.
6. Choose Save.

Performing a Mass Generation of Profiles


If you have changed roles, start the mass generation of profiles.
For more information, see Regenerating Role Profiles [Extern].

Service Procurement: Configuration Guide 2005 23


SAP Online Help 21.04.2005

Upgrading User Data

You must perform the following steps before you run the user data
upgrade. After the upgrade, the previous data is no longer available.

For more information about upgrading the data in SUS User Management, see
SAP Note 729355.
If you want to change from Do the following:
UME 3.O to UME 4.0 No steps are necessary
UME 3.0 to SUS UM in SUS 2.0 Run the migration report
BBP_SUS_BP_UM_JUM2SUM
UME 3.0 to SUS UM in SUS 3.0 Run the migration reports
BBP_SUS_BP_UM_JUM2SUM and
BBP_SUS_BP_UM_SUS20_TO_SUS3OT.
SUS UM in SUS 2.0 to SUS UM in SUS 3.0 Run the report
BBP_SUS_BP_UM_SUS20_TO_SUS3OT.

Service Procurement: Configuration Guide 2005 24


SAP Online Help 21.04.2005

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

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

Service Procurement: Configuration Guide 2005 25


SAP Online Help 21.04.2005

Defining Logical Systems and RFC Destinations


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 SAP Supplier Self-Services, you have
defined SAP Supplier Self-Services as a unique logical system.

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 SAP Supplier Self-Services using RFC calls for
functions such as user synchronization only. 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.
Since the user’s logon language from SAP Enterprise Buyer is used, you do not have to enter
a logon language for SAP Supplier Self-Services.

In general, you do not need an RFC destination for this scenario. It is only
required for functions such as user synchronization.
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 both in SAP Enterprise Buyer and SAP Supplier Self-Services. If
you have several SAP Supplier Self-Services systems, you have to define a user in
each of these systems.

The user must be a system or dialog user.


2. Log on to SAP Enterprise Buyer.
3. Using transaction SM59, define an RFC destination for SAP Supplier Self-Services. If
you have more than one SAP Supplier Self-Services system, define an RFC
destination for each of these systems.
4. Log on to your SAP Supplier Self-Services system. (If you have several SAP Supplier
Self-Services systems, you have to log on to each of them in turn.)
5. Using transaction SM59, define an RFC destination for SAP Enterprise Buyer. If you
have several SAP Supplier Self-Services systems, we recommend that you give the
RFC destination for SAP Enterprise Buyer the same name in all of your SAP Supplier
Self-Services systems.

Service Procurement: Configuration Guide 2005 26


SAP Online Help 21.04.2005

Testing an RFC connection


...

1. Log on to SAP Enterprise Buyer.


2. Call transaction SM59.
3. Select RFC destinations → R/3 connections, and double-click on the entry for your
SAP Supplier Self-Services system.
4. Choose Test connection.
5. If the test was not successful, start by checking the entries under on the Technical
Settings tab page.
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 the remote logon was successful, you are now logged on to the R/3 system. In this
system, call SM59. Select RFC destinations → R/3 connections, and double-click 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
causes:
• The entry for the system on the Technical settings tab page (transaction SM59) is
incorrect
• The user or password was not entered correctly
• The specified user does not have the required level of authorization

Service Procurement: Configuration Guide 2005 27


SAP Online Help 21.04.2005

Defining XI Settings
Purpose
In this section, you define settings in SAP Exchange Infrastructure 3.0. These settings allow
the SRM application components to communicate with each other using the Integration
Server.

Prerequisites
Required Documentation

Step Documentation Where to find


...

You have installed an 1. Installation Guide: 1. SAP Service Marketplace at


Integration Server. SAP Exchange service.sap.com/instg
Infrastructure 3.0 uides → SAP NetWeaver
→ Release 04 → Installation
→ Installation Guide - SAP
2. Installation Guide: XI 3.0.
SAP Web AS 6.40
Unicode on 2. SAP Service Marketplace at
<Operating System> service.sap.com/instg
uides → SAP NetWeaver
→ Release 04 → Installation
→ SAP Web AS 6.40
Unicode on <Operating
System>
You have installed the Master Guide Supplier SAP Service Marketplace at
SAP components that are Relationship Management service.sap.com/instguides
relevant to the business - Supplier Collaboration → mySAP SRM → Using SAP
scenarios using supplier Engine → Supplier Self- EBP 5.0 → Master Guide
integration Services Overview and
Implementation
You have installed and Master Guide Supplier SAP Service Marketplace at
imported Interface and Relationship Management service.sap.com/instguides
Mapping Repository - Supplier Collaboration → mySAP SRM → Using SAP
content Engine → of the Interface EBP 5.0 → Master Guide
and Mapping Repository
Content for mySAP SRM
on SAP Exchange
Infrastructure
You have imported the SRM Master Guide SAP Service Marketplace at
Exchange Infrastructure service.sap.com/instguides
(XI) content for the → Installation & Upgrade Guides
following components, → mySAP SRM → Using SAP
after you have installed SRM Server 5.0
SAP Exchange
Infrastructure:
• SAP SRM Server
5.0
• SAP RosettaNet
1.0 (optional)
• SAP BI Content
3.5.2 (optional)

Service Procurement: Configuration Guide 2005 28


SAP Online Help 21.04.2005

• SAP R/3 4.6c, 4.7,


or 5.0

Enable the SAP Exchange Infrastructure


Transaction code SPRO
IMG path SRM Server → Cross-Application Basic
Settings → Enable Use of Exchange
Infrastructure

Select the Use Application Exchange


Infrastructure checkbox.

Service Procurement: Configuration Guide 2005 29


SAP Online Help 21.04.2005

Configuring the System Landscape Directory


(SLD)
Use
In this section you define the system landscape in the SLD.
The graphic below shows the possible system landscape for the Service Procurement business
scenario:

http Web Ser ver

HTTP S / OC I

Firewall
BSP ITS BSP

BI BW R/3 3.1i – 4.7


Catalog Content SRMSERVER 5.0 IPC SRMSERVER 5.0
CONT 3.5
Management 4.0 FI / CO
3.5. 2
1.0 EBP SUS
R/3 Plug_I n R/3 Plug_I n

XI Proxy XI Int. RFC XI Proxy XI Int. XI Proxy XI Int.


Framew. Engine Framew. Engine Separate IPC for SUS
Framew. Engine
not needed, when
IPC
TREX 6.0 RFC
SUS and EBP are RFC

implemented in the 4.0


same SAP system

HTTP(S)
XML XML

XIXII ntegration
Integration
Engine
Engine XI 3.0

The areas you need to configure for the Service Procurement scenario are
enclosed within a dotted line.

Procedure
Configure the technical and business system landscape for the following installed
components:

• SAP SRM Server 5.0 EBP (Type: SAP business system)


• SAP SRM Server 5.0 SUS (Type: SAP business system)
• Integration Server (Type: SAP business System)

For information about configuring the technical and business system landscape, see the next
two documents in SAP Solution Manager

Result
You have now defined business systems for each of the above products. In the remainder of
the documentation on configuring SAP Exchange Infrastructure, we refer to these business
systems as follows:

Service Procurement: Configuration Guide 2005 30


SAP Online Help 21.04.2005

• <EBP_BS> - represents the SAP business system for SAP SRM Server 5.0 EBP
• <SUS_BS> - represents the SAP business system for SAP SRM Server 5.0 SUS
• <Integration-Server_BS> - represents SAP business system for the Integration
Server

Ensure that you name the business systems consistently. This is especially
important if you are configuring multiple SRM scenarios.

Service Procurement: Configuration Guide 2005 31


SAP Online Help 21.04.2005

Configuring Communication and Security


Use
In this section, the configuration procedure for the different protocols and components
involved in a communication between SAP Enterprise Buyer (SAP EBP) and the integration
server and SAP Supplier Self-Services (SAP SUS) and the integration server is described.

Procedure
...

1. Define HTTP destinations on both your EBP system and your SUS system that point to
the associated Integration Server.

To do so, you need to enter on the Technical Settings tab the correct Target
Host as well as the Path Prefix. Start transaction sicf in the XI system →
Goto → Port Information. For more information, see the next document in SAP
Solution Manager (Connecting to the Integration Server).
Configuring the destination includes selection of the transport protocol and the
authentication method. Instruct the local Integration Engine of your EBP system and of
your SUS system to use this destination for outgoing XML messages.
2. On the associated Integration Server, create the user-defined destination and assign a
user with the role SAP_XI_APPL_SERV_USER to it. For both sending systems (EBP
and SUS), one associated service user should be created on the Integration Server.
When using SSL, make sure that SSL is enabled on the Integration Server.

Further information

Documentation Where to find


SAP Security Guide for SAP Web AS 6.40 SAP Service Marketplace at
service.sap.com/securityguide
Document HTTP and SSL in SAP Solution See the document after next in SAP Solution
Manager Manager

Service Procurement: Configuration Guide 2005 32


SAP Online Help 21.04.2005

Importing Business Scenarios


Use
In this section you transfer the Service Procurement business scenario from the SAP
Integration Repository, generate it, and finally activate it.

Prerequisites
The business system for SAP Enterprise Buyer (EBP) and the business system for SAP
Supplier Self-Services (SUS) have been defined.
The XI content for mySAP SRM has been imported into SAP Integration Repository.

For more information on how to import XI content, see SAP Note 705541
Importing XI content (XI 3.0 SP01 and higher).

Procedure
1. Using transaction SXMB_IFR, choose Integration Builder: Configuration (Integration
Directory) in the SAP XI system.
2. Choose Tools → Transfer Business Scenario from Integration Repository.
3. Choose tab page Objects → SAPSRM SERVER.
The system opens a wizard window Transfer Business Scenario from the Integration
Repository.
4. Choose Repository Business Scenario.
5. Using input help, choose in the Name field
SERVICE_PROCUREMENT_SUPPLIER_ENABLEMENT (with namespace
http://sap.com/xi/SRM/Basis/Global and component SAP SRM SERVER
5.0).
6. Click OK and Continue.
7. Continue with the next step Create Scenario. Enter the Scenario Name Service
Procurement.
8. Click Finish and confirm by clicking Close.
The Business Scenario Configurator automatically opens.
9. Select Component View.
Window 1. Select Component View opens.
10. Confirm by clicking Apply.
Window 2.Assign Services to Roles opens.
11. Choose the Service Assignment tab page and choose Insert line.
12. For assigning a Business System to the Materials Management System, choose via
input help.
13. Choose for each role .
14. Confirm with Assign.
The system opens the Configure Connection window.

Service Procurement: Configuration Guide 2005 33


SAP Online Help 21.04.2005

If the systems are applied from the SAP If the systems are not applied from the
Landscape Directory (SLD), SAP Landscape Directory (SLD),
the Integration Builder automatically creates you create communication channels
the communication channels. manually.
For it you choose an existing service and
then Communication Channel. Choose via
context menu New.
15. Confirm.
Generate window opens.
16. Select Generation, Simulation and mark all in the list Scope of Generation.
17. Choose Start.
You get a result list.
18. If the result list has 0 errors, select Generation and choose Start.
19. Confirm the dialog box Transfer changes by clicking Apply.
You get the result.
20. Choose tab page Change Lists.
21. Choose the context menu of the entry change list and choose Activate.

Configuring Communication Channels for SAP SUS


...

1. Choose tab page Objects and open Service Without Party → Business System →
Business System for SUS → Communication Channel
2. Double click on GeneratedReceiverChannel_XI
3. Click on the Change icon.
4. Verify all settings and enter data for Target Host and Service Number. To do so, start
transaction sicf in the SUS system and open Goto → Port Information; the default
path reads as follows: /sap/xi/engine/?type=receiver
5. Choose Activate.

Result
The Business Scenario Service Procurement is configured concerning receivers, senders and
the communication channels.
The Service Procurement business scenario is activated.

Service Procurement: Configuration Guide 2005 34


SAP Online Help 21.04.2005

Checking XI Settings
Procedure
Check for all Business Systems, if the following steps are carried out:
Activity in
You have defined a logical system in the SAP Enterprise Buyer and SAP Supplier
transaction SALE. See in Customizing for Self-Services (SUS) for Service
SAP NetWeaver → SAP Web Application Procurement Business Scenario
Server → Basic Settings → Application Link SAP MM and SAP SUS for Plan-Driven
Enabling (ALE) → Logical Systems → Define Procurement with Supplier Integration
Logical System. Business Scenario
You have assigned the client to the logical
system SAP NetWeaver → SAP Web
Application Server → Basic Settings →
Application Link Enabling (ALE) → Logical
Systems → Assign Client to Logical System.
You have defined the XIAPPLUSER. SAP Enterprise Buyer and SAP SUS for
Service Procurement Business Scenario
SAP MM and SAP SUS for Plan-Driven
Procurement with Supplier Integration
Business Scenario
You have defined the http destination to XI in SAP Enterprise Buyer and SAP SUS for
transaction SM59. Service Procurement Business Scenario
SAP SUS for Plan-Driven Procurement with
Supplier Integration Business Scenario
You have activated the relevant service for XI SAP Enterprise Buyer and SAP SUS for
in transaction SICF, as described in unit 6.1 of Service Procurement Business Scenario
the XI Configuration Guide, see SAP Service
SAP SUS for Plan-Driven Procurement with
Marketplace at
Supplier Integration Business Scenario
service.sap.com/instguides → SAP
NetWeaver → Release 04 → Installation →
Configuration Guide – SAP XI 3.0.
You have configured the Integration Engine in SAP Enterprise Buyer and SAP SUS for
transaction SXMB_ADM, as described in unit Service Procurement Business Scenario
6.0 of the XI Configuration Guide, see SAP
SAP SUS for Plan-Driven Procurement with
Service Marketplace at
Supplier Integration Business Scenario
service.sap.com/instguides → SAP
NetWeaver → Release 04 → Installation →
Configuration Guide – SAP XI 3.0
You have registered the queues in transaction SAP Enterprise Buyer and SAP SUS for
SXMB_ADM, as described in unit 6.2 of the XI Service Procurement Business Scenario
Configuration Guide, see SAP Service
SAP SUS for Plan-Driven Procurement with
Marketplace at
Supplier Integration Business Scenario
service.sap.com/instguides → SAP
NetWeaver → Release 04 → Installation →
Configuration Guide – SAP XI 3.0

Service Procurement: Configuration Guide 2005 35


SAP Online Help 21.04.2005

You have defined the SLD access data in SAP Enterprise Buyer and SAP SUS for
transaction SLDAPICUST, as described in Service Procurement Business Scenario
unit 6.3 of the XI Configuration Guide, see
SAP SUS for Plan-Driven Procurement with
SAP Service Marketplace at
Supplier Integration Business Scenario
service.sap.com/instguides → SAP
NetWeaver → Release 04 → Installation →
Configuration Guide – SAP XI 3.0
You have maintained the RFC destinations SAP Enterprise Buyer and SAP SUS for
LCRSAPRFC and SAPSLDAPI in transaction Service Procurement Business Scenario
SM59, as described in unit 6.3.1 of the XI
SAP SUS for Plan-Driven Procurement with
Configuration Guide, see SAP Service
Supplier Integration Business Scenario
Marketplace at
service.sap.com/instguides → SAP
NetWeaver → Release 04 → Installation →
Configuration Guide – SAP XI 3.0
You have maintained the SAP J2EE SAP Exchange Infrastructure
Connection Parameters for LCRSAPRFC, as
described in unit 6.3.1 of the XI Configuration
Guide, see SAP Service Marketplace at
service.sap.com/instguides → SAP
NetWeaver → Release 04 → Installation →
Configuration Guide – SAP XI 3.0
You have defined a technical name, for SLD
example QWA.
You have defined a Business System Name, SLD
for example QWA_100.
You have tested the connection between a SAP Enterprise Buyer and SAP SUS) for
Business System and the SLD in transaction Service Procurement Business Scenario
sldcheck, as described in unit 6.3.2 of the XI
SAP SUS for Plan-Driven Procurement with
Configuration Guide, see SAP Service
Supplier Integration Business Scenario
Marketplace at
service.sap.com/instguides → SAP
NetWeaver → Release 04 → Installation →
Configuration Guide – SAP XI 3.0
You have defined a backend system, see SAP Enterprise Buyer and SAP SUS for
Defining Backend Systems [Extern]. Service Procurement Business Scenario
SAP SUS for Plan-Driven Procurement with
Supplier Integration Business Scenario

Service Procurement: Configuration Guide 2005 36


SAP Online Help 21.04.2005

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

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

Service Procurement: Configuration Guide 2005 37


SAP Online Help 21.04.2005

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

Regenerating Role Profiles


Use
You have to regenerate the authorizations for each role that you intend to use. This ensures
that the profiles belonging to these roles are assigned all the required authorizations. In
Customizing for Supplier Relationship Management, choose 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. In Customizing for Supplier Relationship Management,
choose SRM Server → Cross-Application Basic Settings → Roles → Maintain
Attribute Access Rights by Role.
For more information, see SAP Note 644124.
...
...

1. Choose Utilities → Mass generation.


2. Select All Roles.
3. Enter SAP_EC_BBP*.

4. Choose .

Service Procurement: Configuration Guide 2005 38


SAP Online Help 21.04.2005

Creating the Organizational Plan


Procedure

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

1. Use transaction SU01 to create an R/3 user with the profile described in SAP Note
642202. Assign this user the administrator role SAP_BBP_STAL_ADMINISTRATOR.
2. As this administrator, create your organizational plan.
At the very least, you must create a root node for the organizational plan. The
remaining organizational units can be created by the employees and managers
themselves using the self-service Web application. We recommend 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 the Web application Manage Users:
a. Create the root organizational unit. Remember to enter an address for the
organizational unit.
Go to Customizing for Supplier Relationship Management and choose SRM
Server → Cross-Application Basic Settings → Organizational Management →
Create Organizational Plan

You start to create the organizational plan in the IMG activity Create
Organizational Plan (transaction PPOCA_BBP). After leaving this activity, you
make changes to the organizational plan in the IMG 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 Function tab page.

You must enter an address for each organizational unit. If you fail to do so, the
self-service Web transaction for creating users will not work!
3. Using the Web application, 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.
• 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.
4. In the same way, create an organizational root node for your vendors.

Service Procurement: Configuration Guide 2005 39


SAP Online Help 21.04.2005

5. After creating your organizational plan, you can run a report to check that a business
partner has been defined for each node in the organizational structure.
Go to Customizing for Supplier Relationship Management and choose SRM Server →
 ross-Application Basic Settings → Organizational Management → Integration
C
Business Partner – Organizational Management → Match Up Organizational Units and
Persons with Business Partners

You first have to set up the integration with Organizational Management.


Go to Customizing for Supplier Relationship Management and choose 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 choose Start Resynchronization.
You first need to consider the error messages and correct them in
PPOMA_BBP, for example, then you can execute the resynchronization.
6. After creating your organizational plan, you can run a report to check that the attributes
have been defined correctly for the individual applications allowed for the users:
Transaction BBP_ATTR_CHECK or report BBP_CHECK_CONSISTENCY.

Service Procurement: Configuration Guide 2005 40


SAP Online Help 21.04.2005

Defining Organizational Plans for Suppliers


Use
In this procedure you define the organizational data in the SAP Supplier Self-Services (SUS)
system.
You define only one root node (Central Org.Unit for Vend.) and then you assign the supplier
organizational plan to this root node.
This graphic shows that you define the central organizational unit for vendors to assign the
respective currency to the corresponding supplier.

Transaction
PPOMA_BBP

Buyer 1 Buyer 2

Accounting system Accounting system


(ACS) 1 (ACS) 2

Company code (BUK) 1 Company code (BUK) 2

Central Org.Unit for Vend.

Vendor 1 Vendor 2 Vendor n

Currency of Currency of Currency of


vendor 1 vendor 2 vendor n

Default of
purchasing organization (Purch.Org.)

Procedure
Perform the following steps in the SAP SUS system:

Creating an Organizational Plan


Transaction code SPRO
SAP Reference IMG → Supplier Relationship Management → SRM
Server→ Cross-Application Basic Settings → Organizational
Management → Create Organizational Plan
...

1. Enter a technical name and description for the organizational plan.


2. Choose the Function tab page and set the indicator Purch. Organization.
This is the default value for the purchasing organization (Default Pur.Org.) in the IMG
activity Making Settings for Business Partners.
3. Save your entries.
4. Enter a technical name and description for a second organizational plan without setting
the indicator Purch. Organization.
This is the default value for the central organizational unit for vendors (Central Org.Unit
for Vend.) in the IMG activity Making Settings for Business Partners.

Service Procurement: Configuration Guide 2005 41


SAP Online Help 21.04.2005

5. Save your entries.


Transaction code SPRO
SAP Reference IMG → Supplier Relationship Management → SRM
Server→ Cross-Application Basic Settings → Organizational
Management → Change Organizational Plan.
Perform the IMG activity as decribed in the IMG documentation.

Making Settings for Business Partners


Transaction code SPRO
SAP Reference IMG → Supplier Relationship Management →
Supplier Self-Services → Master Data → Make Settings for Business
Partners.
Maintain the following fields in the IMG activity Make Settings for Business Partners as
described in the IMG documentation:
• Central Org.Unit for Vend.
• Purch. Organization

Result
You have defined a purchasing organization for all suppliers and a central organizational unit
for suppliers in SAP SUS.

Service Procurement: Configuration Guide 2005 42


SAP Online Help 21.04.2005

Making Settings for Creating Internal Users


Prerequisites
You have defined the root organizational unit of the organizational plan. See Creating the
Organizational Plan [Extern].

Procedure
If the user’s superior is to approve the user master record, activate the approval
process in Customizing for Supplier Relationship Management, by choosing 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.)

Service Procurement: Configuration Guide 2005 43


SAP Online Help 21.04.2005

Maintaining User Attributes


Prerequisites
• You must have created the root node of the organizational plan.
• Before managers can approve the creation of new user master records, they must have
been assigned the manager role SAP_BBP_STAL_MANAGER.
• To enable the Web application Change Attributes, you have assigned a change
authorization to the role responsible for changing the user attributes.
Go to Customizing for Supplier Relationship Management and choose SRM Server →
Cross-Application Roles → Maintain Attribute Access Rights by Role.

Procedure
1. Use transaction PPOMA_BBP, Attributes tab page, to specify values for the main user
attributes. For the most attributes, use the Web application Change Attributes to do
this. Important attributes include:
{ Product categories: The product responsibilities have to be specified on the
Extended Attributes tab page (attribute PRCAT).
{ Systems: ACS, SYS
{ Document types: BSA
{ Role: ROLE
{ Direct material transaction type: DP_PROC_TY
{ Contract transaction type: CT_PROC_TY
{ 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 the earlier SAP Enterprise Buyer releases)
{ Procurement attributes have to be specified on the Function and Responsibility
tab pages
{ Currency: CUR
{ Ship-to address: ADDR_SHIPT
{ ITS Destination for bids: EXT_ITS and ITS_DEST
{ Transaction type for bid invitations created from Sourcing: TEND_TYPE
2. To make sure all attributes that are necessary for your business scenario have been
specified, you can start transaction BBP_ATTR_CHECK.
a. Mark the User Attributes for Application check type.
b. Execute the report for the relevant applications.

See also:

Maintaining User Attributes [Extern]


Modeling the Purchasing Organization in the Organizational Plan [Extern]

Service Procurement: Configuration Guide 2005 44


SAP Online Help 21.04.2005

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

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
Additionally, you have to define number ranges for documents that are to be created in
backend systems.

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

Procedure
In Customizing for SRM, define number ranges by choosing SRM Server → Cross-
Application Basic Settings → Number Ranges.
The interval number must be the value of Int.No. that you have defined for the transaction
type. For more information, see the Implementation Guide (IMG) for SRM: SRM Server →
Cross-Application Basic Settings → Define Transaction Types.

Business Partner Number Ranges


In Customizing for SRM, define number ranges (for internal and external number assignment)
in central business partner maintenance, by choosing Cross-Application Components → SAP
Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings
→ Define Number Ranges.

When vendors are replicated from multiple backend systems, the number range
for which the standard indicator has been set is used for external number
assignment. Therefore, we recommend that the number range is large enough
to cover all number ranges specified in the individual backend systems.
For more information, see the IMG for SRM: Cross-Application Components →
SAP Business Partner → Business Partner → Basic Settings → Number
Ranges and Groupings → Define Groupings and Assign Number Ranges.

Service Procurement: Configuration Guide 2005 45


SAP Online Help 21.04.2005

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 from
which the document numbers are determined, 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.

Procedure
...

1. In Customizing for Supplier Relationship Management, choose 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 Transaction Type in the side menu.
4. Double click 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.

Service Procurement: Configuration Guide 2005 46


SAP Online Help 21.04.2005

Making Settings for Account Assignment


Use
You must make the relevant account assignment settings.

Prerequisites
• The necessary accounts have been defined.
• The account assignment categories have been defined.

Procedure
...
...

1. Select account assignment categories.


In Customizing for Supplier Relationship Management (SRM), select the required
account assignment categories from a preconfigured list by choosing SRM Server →
Cross-Application Basic Settings → Account Assignment → Define Account
Assignment Categories.
2. Map account assignment categories.
In Customizing for SRM, map R/3 account assignment categories to the SAP
Enterprise Buyer categories by choosing SRM Server → Cross-Application Basic
Settings → Account Assignment → Define Account Assignment Categories.
3. Change account assignment categories.
To change account assignment categories using Business Add-Ins, go to Customizing
for SRM 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. In Customizing for SRM,
choose SRM Server → Cross-Application Basic Settings → Account Assignment →
Define G/L Account for Product Category and Account Assignment Category.
Alternatively, you can use a Business Add-In to define your own criteria for determining
the G/L account. In Customizing for SRM, choose SRM Server → Business Add-Ins →
Account Assignment → Determine G/L Account.
5. Maintain local accounting data.
You enter account assignment information and define an account assignment object for
local validation. In Customizing for SRM, choose SRM Server → Cross-Application
Basic Settings → Account Assignment → Maintain Local Accounting Data.

Service Procurement: Configuration Guide 2005 47


SAP Online Help 21.04.2005

Defining Technical Settings for E-Mail


Use
This setting enables communication between the buyer and suppliers, for example, sending
notification to the supplier when a new order is created, or an existing order is changed.

Prerequisites
The user SAPconnect has to be activated in transaction SICF (service SAPconnect).

Procedure
Creating the Mail Service in SAPconnect
Transaction code SCOT
Menu path SAP Menu → Basis Tools → Business Communication →
Communication → SAPconnect
...
...

Another way for setting up mail via SMTP is described in SAP Note 455140.

Creating a Job for the Mail Service in SAPconnect


Transaction code SCOT
Menu Path SAP Menu → Basis Tools → Business
Communication → Communication
→ SAPconnect
...

1. Choose View → Jobs.


2. Choose Create.
3. Enter a name for the job and choose Enter.
4. Select the variant INT.
5. Choose Schedule Job.
6. Select Schedule Periodically. You can then enter the duration time between the jobs.
7. Enter the duration time and choose Create.

Service Procurement: Configuration Guide 2005 48


SAP Online Help 21.04.2005

Configuring SAP Supplier Self-Services


Use
In this section, you configure settings in the Supplier Relationship Management (SRM)
system for SAP Supplier Self-Services (SAP SUS).

ƒ For upgrading SAP SUS, see SAP Note 707701.


ƒ For migrating documents and business partner data in SAP SUS, see
SAP Service Marketplace at service.sap.com/instguides →
mySAP Business Suite Solution → mySAP SRM → Using SAP EBP 5.0
→ Component Upgrade Guide – SRM Server 5.0 :<platform> in section
SAP SRM Server: Post-Upgrade Activities, subsections Migrating
Documents and Migrating Business Partner Data.
...

Procedure
1. Technical Basic Settings
Define Configuration Data for Publishing Attachments
If you want to send document attachments to SAP Enterprise Buyer, define the
settings in this activity. You need to define the Web server that is used for sending and
receiving attachments in the SAP Enterprise Buyer environment.
If you want to send document attachments from SAP Enterprise Buyer to SAP
Supplier Self-Services, define the settings in Customizing for Supplier Relationship
Management, by choosing SRM Server → Cross-Application Basic Settings → Transfer
Attachments.
2. Application-Specific Basic Settings
Perform the following IMG activities in Customizing for SRM, by choosing Supplier Self-
Services →
a. Master Data → Make Settings for the Business Partners
For more information, see Defining Settings for Business Partners [page 51].

If you want to use supplier registration, see Making Settings for Supplier
Registration [Extern]. Perform these steps once you have defined the backend
systems.
b. Settings for the User Interface → Customer Settings
For more information, see Defining Customer Settings [page 54].
c. Cross-Application Basic Settings → Settings for Documents → Number Ranges
Perform as described in the IMG documentation.
d. Cross-Application Basic Settings → Define Transaction Types
For more information, see Defining Transaction Types [Extern].
e. Cross-Application Basic Settings → Tax Calculation
For more information, see Defining Tax Calculation [page 55].
3. BAdI Settings

Service Procurement: Configuration Guide 2005 49


SAP Online Help 21.04.2005

In Customizing for SRM, choose Supplier Self-Services → Business Add-Ins (BADIs)


→ Download Documents.
For information about using own forms, see the IMG documentation.
4. Defining External Web Services
If you use catalogs in SAP SUS, define external Web services in Customizing for SRM,
by choosing SRM Server → Master Data → Define External Web Services (Catalogs,
Vendor Lists etc.).

Service Procurement: Configuration Guide 2005 50


SAP Online Help 21.04.2005

Making Settings for Business Partners


Prerequisites
• You have defined organizational plans for suppliers, see Defining Organizational Plans
for Suppliers [page 41].
• You have defined a URL for User Management Registration, see Setting up Services
for SAP Supplier Self-Services [page 18].

Procedure
IMG Path Supplier Relationship Management → Supplier Self-
Services → Cross-Application Basic Settings →
Make Settings for Business Partners
...

1. Replace the given URL (www.xyz-supplier-portal.com) in accordance with this naming


convention: http://<vendor-specific UM
server.domain>:<port>/sap/bc/bsp/sap/srmsus_selfreg/userselfreg.
htm?
2. Enter data as described in the IMG activity.
3. Save your entries.

Service Procurement: Configuration Guide 2005 51


SAP Online Help 21.04.2005

Defining Backend Systems


Use
You define all systems of the purchaser, including business system, logical system and
system type of the backend system.

Backend systems must be defined for both EBP and SUS.

Procedure
Transaction Code SPRO
IMG Path SAP Reference IMG → Supplier Relationship
Management→ Supplier Self-Services →
Cross-Application Basic Settings → Define
Backend Systems
...
...

1. Create a new entry.


2. Select a logical system.
3. Specify the logical systems:
Logical System Required Data
SUS Logical System name
SLD Name in description
RFC: indicator not set
CI Connect: indicator not set
SLD name: <SUS_BS>
MM (only relevant for Business Scenario Logical System name
Plan-Driven Procurement with Supplier
SLD Name in description
Integration)
System Type R/3 System Version
Local: indicator not set
CI Connect: indicator not set
SLD name: <MM_BS>
EBP (only relevant for the Service Logical System name
Procurement business scenario)
SLD Name in description
System Type SRM System Version
Local: indicator not set
CI Connect: indicator not set
SLD name: <SRM_BS>

4. Enter proper system type:


For EBP system: Connected EBP system
For SUS system: Local B2B system
For R/3 system: R/3 system – version x.y

Service Procurement: Configuration Guide 2005 52


SAP Online Help 21.04.2005

If you want to use SAP SUS and SAP Enterprise Buyer in the same client, make
sure that you have selected OneClient EBP and SUS as system type.
For more information, see the documentation of IMG activity Defining backend
systems.
5. Enter the SLD name, for example QW8_250.

The SLD name is case sensitive.


6. Save your entries.
7. Perform step 1 to 5 for all logical systems.

Service Procurement: Configuration Guide 2005 53


SAP Online Help 21.04.2005

Defining Customer Settings


Use
In this section you can define
• The location of your SAP Bidding Engine and SAP Business Information Warehouse
(SAP BW) systems, if you want to link directly to them from your application.
• List entries per page
• Item list entries per page
• The menu folder status
• To show the payment status of invoices
• To show and hide elements of the user interface: Scenario, header line, breadcrumb,
menu width, and information area
• To force users to change the password on initial login

Prerequisites
For the location of your SAP Bidding Engine and SAP BW, you have connected SAP Bidding
Engine and SAP BW to your SAP Supplier Self-Services (SAP SUS) system.

Procedure
IMG Path Supplier Relationship Management → Settings
for the User Interface → Customer Settings
...

1. For the key BIDDING_SERVICE, enter the URL destination for your SAP Bidding
Engine system under Parameter value.
2. For the key BW_SERVER, enter the URL destination for your SAP BW under Parameter
value.

If SAP BW and SAP SUS run in the same system, but on different clients,
extend the URL to &SAP-CLIENT=<client number> with no space.

ƒ URL before changing:


http:://<hostname.domain:port>/SAP/BW/BEX?CMD=LDOC&TEM
PLATE_ID=0TPL_BBP_C01_SUS_00
ƒ URL after changing:
http:://<hostname.domain:port>/SAP/BW/BEX?CMD=LDOC&TEM
PLATE_ID=0TPL_BBP_C01_SUS_00&SAP-CLIENT=300
3. If you have entered the key FORCE_INITITIAL_PASSWORD_CHANGE with value
TRUE, new SAP SUS users have to change the password with the first login.
4. For the keys LIST_ENTRIES_PER_PAGE, ITEM_LIST_ENTRIES_PER_PAGE,
MENU_FOLDER_STATUS, SHOW_INVOICE_PAY_STATUS, NO_TOP_LOGO,
SHOW_ELEMENT_MENU, SHOW_ELEMENT_BREADCRUMB, MENU_WIDTH and
SHOW_ELEMENT_INFO, see the documentation of the IMG activity Customer Settings.

Service Procurement: Configuration Guide 2005 54


SAP Online Help 21.04.2005

Defining Tax Calculation


Procedure
IMG Path Supplier Relationship Management → SRM
Server → Supplier Self-Service → Cross-
Application Basic Settings → Defining Tax
Calculation
Follow the link and perform the IMG activities for tax calculation:
...

1. Determine System for Tax Calculation


If the tax is calculated in R/3, specify this option. In this case, step 2 is mandatory.
If no tax calculation is selected, you can ignore the other steps.
If TTE is specified, make sure that the TTE is configured.
2. Enter Tax Code
Enter R/3 tax codes. If the tax rate is 0 %, then specify No tax.
3. Determine Tax Code for Country/Product Category
For more information, see the IMG documentation.
4. Assign Enterprise Buyer Tax Code to FI System
For more information, see the IMG documentation.
5. Define Tax Calculation for Freight Costs
For more information, see the IMG documentation.

Tax Calculation with R/3 System


...

If you have chosen the option R/3 system in the IMG activity Determine System for Tax
Calculation, you have to assign two attributes to the business partner buyer.
Perform the following steps:
Transaction Code PPOMA_BBP
...

1. Choose Organizational Unit → Companies.


2. Double-click the relevant purchasing organization.
3. Choose attributes tab page.
4. Go to the row with the system alias.
5. Select the relevant value for the accounting system (ACS).
6. Select the relevant company code for BUK.
7. Save your entries.

Required Information

Documentation Where To Find


IPC 4.0 Configuration Support SAP Service Marketplace at
service.sap.com/ibc → for mySAP SRM

Service Procurement: Configuration Guide 2005 55


SAP Online Help 21.04.2005

Defining Analytics Settings for SAP SUS


Use
Before you can use the Analytics functions in SAP Supplier Self-Services, you must activate a
Business Add-in (BAdI) in the Analytics system.
This BAdI ensures that the Analytics user created in SAP Supplier Self-Services can log on to
the Analytics system.

Procedure
Transaction code SE19
...
...

1. In the Implementation name field, enter BAdI RSSBR_SMUM_CRM_SUS.


2. Choose Activate Business Add-In implementation.

Service Procurement: Configuration Guide 2005 56


SAP Online Help 21.04.2005

Configuring SAP Enterprise Buyer


In this section, you configure settings relevant to SAP Enterprise Buyer.

Service Procurement: Configuration Guide 2005 57


SAP Online Help 21.04.2005

Defining Master Data in SAP Enterprise Buyer and


SUS
Use
In this step, you define business partners in SAP Enterprise Buyer for the use with SAP
Supplier Self-Services (SAP SUS). You create the SUS supplier as a business partner
(vendor) in Enterprise Buyer and then replicate the vendor data from Enterprise Buyer to
SUS.

Database table T006 is shipped with identical entries for Enterprise Buyer and
Supplier Self-Services. If, for any reason, you make changes to entries in the
table, you must make these changes in both tables so that the table entries in
the two systems remain identical.

Make sure that you have created the organizational data in the SAP SUS
system. See Defining Organizational Data [page 41].

Procedure
Specifying SUS business partners in SAP Enterprise Buyer (Browser)
Enterprise Buyer Browser Business Partner→ Manage Business Partners
...

1. Enter the business partner under Business partner data and choose Create.
2. Under Contact for Business Partner, maintain the following:
a. In the Standard communication protocol field, choose XI infrastructure
b. Select Portal vendor.

If you don´t select Portal vendor, you can´t maintain vendor data from SAP
Enterprise Buyer in SAP Supplier Self-Services.
3. Save your entries.

This step is only necessary if you want to change an existing EBP vendor to a
portal vendor. If you selected Portal Vendor when you originally created the
business partner, you do not need to do this step. This transaction automatically
replicates business partners to SUS.

Replicating Company Data in SAP Enterprise Buyer


Transaction code BBP_SP_COMP_INI
...

1. Select the companies that are to become SUS buyers and the employees that are to
become SUS contacts.
2. Choose Replication.

Any changes made to business partners are automatically replicated. You only
need to perform this step for new business partners.

Service Procurement: Configuration Guide 2005 58


SAP Online Help 21.04.2005

Replicating Suppliers for SUS in SAP Enterprise Buyer


Transaction code BBP_SP_SUPP_INI
...

1. Enter the number of the Enterprise Buyer vendor to become a SUS supplier in the
SUPPLIER field
2. Save your entries.

Result
The supplier receives an e-mail with a registration ID for SAP Supplier Self-Services.
Suppliers can then create an administration user and individual users.

Further Information

Documenation Where to find


Section 12.2 Supplier-Self-Service Self- SAP Service Marketplace
Registration Process,
Choose service.sap.com/srm → mySAP SRM
Configuration Guide SAP User Management in Detail → Components in Detail →User
Engine 3.0 Management Engine →Implementation
Information →Configuration Guide User
Management Engine 3.0.

Service Procurement: Configuration Guide 2005 59


SAP Online Help 21.04.2005

Creating Payment Conditions


Procedure
Activity Description For more information, see:
Creating payment conditions You can use this setting to Path in the Implementation
define rules used by SAP Guide (IMG) for Supplier
Enterprise Buyer to determine Relationship Management:
payment conditions. When SRM Server → Cross-
processing business Application Basic Settings →
documents, you want to Create Payment Conditions
select payment conditions via
an input help, this step is
mandatory. The input help
comes from 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).
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 instead. When you use this report,
not only the day/percentage values but the complete range (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.

Service Procurement: Configuration Guide 2005 60


SAP Online Help 21.04.2005

Defining Message Control for Limit POs


Use
If you want to use limit purchase orders in SAP Supplier Self-Services, you must adjust XML
message control settings in Customizing for SAP Enterprise Buyer.
This Customizing activity ensures that the product category field appears in SAP Enterprise
Buyer when you send a confirmation for a limit PO to SAP Enterprise Buyer. If you do not
define this setting, the confirmation is not created in Enterprise Buyer and is automatically set
to Rejected in SAP Supplier Self-Services.

Procedure
SPRO SAP Implementation Guide → Supplier Relationship
Management → SRM Server → Cross-Application Basic
Settings → Message Control → Influence XML Message
Control
...
...
...

1. Select Confirmations Goods/Services EC (BUS2203).


2. Double-click on XML Message Control.
3. Select Enter a Product Category.
4. Select Ignore.
5. Save your changes.

Service Procurement: Configuration Guide 2005 61


SAP Online Help 21.04.2005

Setting Up SAP Business Workflow


Use
Before purchasers can approve or reject goods receipt confirmations and invoices from the
SUS system in the Enterprise Buyer system, all four start conditions supplied have to be
activated for the Confirmation Goods/Services EC (BUS2203) and Incoming Invoice EC
(BUS2205) business object.
Only then can you use the confirmation approval workflows
• WS10400002 One-Step Approval
• WS10400009 Two-Step Approval
• WS10400010 Workflow Without Approval
• WS10400020 Approval by Admin
and the invoice approval workflows
• WS10400016 Workflow Without Approval
• WS10400017 One-Step Approval
• WS10400018 Two-Step Approval
• WS10400021 Approval by Admin.

All relevant start conditions are shipped as active by default.

Procedure
You activate the start conditions in the Implementation Guide (IMG) for Supplier Relationship
Management → SRM Server → Cross-Application Basic Settings → SAP Business Workflow
→ Define Conditions for Starting Workflows.

Service Procurement: Configuration Guide 2005 62


SAP Online Help 21.04.2005

Configuring Link to Service Agent List in EBP


Use
In the SAP Enterprise Buyer system you need to perform the following configuration steps to
enable the link to the service agent list in SAP Supplier Self-Services (SAP SUS).

Procedure
...

In Customizing for Supplier Relationship Management, create the service agent list by
choosing SRM Server → Master Data → Define External Web Services.
In the Service Procurement business scenario you need to be able to choose a service agent
from a list in the SAP SUS system.
...

1. Enter the URL of the service agent catalog as a parameter with type URL.
2. Maintain the catalog as an attribute for the user using transaction PPOMA_BBP.

For information on how to define the service agent list, see the IMG
documentation.

Service Procurement: Configuration Guide 2005 63


SAP Online Help 21.04.2005

Making Settings for Confirmations and Invoices


Use
Use the following IMG activities to configure all necessary settings for time recording in SAP
Enterprise Buyer.

Prerequisites
To process confirmations that contain limit items with catalog connection, you have
maintained the IMG activity Define External Web Services.

Procedure

All of the following settings are optional.

Activity Description For more information, see:


Define Defaults for Time Creates a version for time Menu path in the SAP
Recording recording that is used as the Implementation Guide (IMG):
standard version in SAP
Supplier Relationship
Enterprise Buyer if you add a
workday or a work week. Management → SRM Server
→ Confirmation and Invoice
Verification → Define
Defaults for Time Recording
Control Default Values for Overrides the standard Menu path in the IMG:
Time Recording version that you have defined
Supplier Relationship
in the IMG activity Define
Defaults for Time Recording. Management → SRM Server
→ Business Add-Ins for
Enterprise Buyer (BadIs) →
Confirmation and Invoice
Verification → Control
Default Values for Time
Recording
Define Default Setting for Defines defaults for Menu path in the IMG:
Limit Items unplanned items that are
Supplier Relationship
added to limit items.
Management → SRM Server
→ Confirmation and Invoice
Verification → Define Default
Setting for Limit Items
Control Entry Options for Controls the addition of Menu path in the IMG:
Unplanned Items unplanned items.
Supplier Relationship
Management → SRM Server
→ Business Add-Ins for
Enterprise Buyer (BadIs) →
Confirmation and Invoice
Verification → Control Entry
Options for Unplanned Items

Service Procurement: Configuration Guide 2005 64


SAP Online Help 21.04.2005

Making Settings for Evaluated Receipt Settlement


(ERS)
Use
The ERS process and its necessary settings differ between the local and extended classic
scenarios.
In the local scenario the ERS run is performed in SAP Enterprise Buyer and settles the local
purchase order. After that the postings are sent to the FI backend system.
In the extended classic scenario the ERS run is started in the backend system where the FI
postings take place as well.

Prerequisites
• The number range(s) for these documents are set up.
• The transaction type is set up.

Procedure
1. Set up the preferred output medium (print, e-mail, fax).
2. Set the indicator for Evaluated Receipt Settlement in the vendor’s business partner
master record.

A confirmation is expected for the purchase order.


A goods-receipt-related invoice verification is required.
To use ERS you should schedule report BBPERS as a periodical (batch) job.

Service Procurement: Configuration Guide 2005 65


SAP Online Help 21.04.2005

Making Settings for Replication of Vendor Master


Records
Use
Depending on your system landscape, you can replicate vendor master records in two ways:
• You have an FI backend system and no MM backend system:
In this case, the vendor is created in the SAP Enterprise Buyer system and a
corresponding creditor is created in the FI backend system. This must be mapped to
the vendor master in SAP Enterprise Buyer using the application Manage Business
Partners. For more information, see Managing External Business Partners in the SAP
Enterprise Buyer documentation at http://help.sap.com.

• You have both an FI backend system and an MM backend system:


The vendor master records have to be replicated from the MM backend system.
For more information, see Making Settings for External Locations and Business
Partners in the Business Scenario Configuration Guide for Self-Service Procurement at
http://service.sap.com/ibc.

Service Procurement: Configuration Guide 2005 66


SAP Online Help 21.04.2005

Making Settings for Requests for External Staff


Use
To be able to request external staff or services prior to ordering them, you can make several
settings.

Procedure

All of the following settings are optional.

Settings

Activity Description For more information, see:


Adding links to You can add additional links to the wizard, Implementation Guide (IMG) for
shopping cart. simplified, or extended form of the shopping Supplier Relationship Management:
cart in order to request or order external SRM Server → Business Add-Ins
staff or services. (BAdIs) → Shopping Carts and
Requirement Items → Change Display
in Shopping Cart
Defining Once you have created a request for IMG: SRM Server → Business Add-Ins
transaction type external staff or other services, the system (BAdIs) → Bid Invitation → Determine
for requests for creates a bid invitation, to which bidders can Bid Invitation Transaction Type
external staff. submit a quotation, for example, they
respond to your request. You can customize
the transaction type for this kind of bid
invitation to change the default
implementation.
Customizing text To customize the default text message that Transaction smartforms →
message in e- the bidder (supplier) receives by e-mail BBP_BIDINV_BID → folder
mail notification informing him about a new request for FO_PUBLISHING
for bidder external staff, you choose smart form
(supplier). BBP_BIDINV_BID.

It is a prerequisite that the administrator has


entered the bidder’s e-mail address. See
SAP Enterprise Buyer → Manage Business
Partners
Customizing text To customize the default text message that Transaction smartforms →
message in e- the requester receives by e-mail informing BBP_BID_NOTIFICATION
mail notification him about the bidder’s response to his
for requester. request for external staff, you choose smart
form BBP_BID_NOTIFICATION.

It is a prerequisite that the administrator has


entered the requester’s e-mail address. See
SAP Enterprise Buyer → Edit Internal
Addresses

Service Procurement: Configuration Guide 2005 67


SAP Online Help 21.04.2005

Defining start You can perform some standard IMG: SRM Server → Cross-Application
conditions for Customizing for SAP Business Workflow. Basic Settings → SAP Business
workflows Workflow → Perform Task-Specific
(concerning Customizing
requests for
external staff). You need to activate the event linkage for IMG: SRM Server → Cross-Application
the following workflows: Basic Settings → SAP Business
Workflow → Define Conditions for
• WS10000276 Starting Workflows
• WS10000031 (Two-step approval of
shopping cart)
• WS10000129 (One-step approval of
shopping cart)
• WS14000109
• WS10000060 (Shopping cart without
approval)
• WS14000141
• WS14500015
• WS10400047
• WS14000133
Defining start You can perform some standard IMG: SRM Server → Cross-Application
conditions for Customizing for SAP Business Workflow. Basic Settings → SAP Business
workflows Workflow → Perform Task-Specific
(concerning Customizing
quotations).

You need to activate the event linkage for IMG: SRM Server → Cross-Application
the following workflows: Settings → SAP Business Workflow →
Define Conditions for Starting
• WS79000002 Workflows
• WS79000010
Creating skill You can customize the default PDF form for IMG: SRM Server → Business Add-Ins
profiles. skill profiles that you use to describe skills (BAdIs) → Skill Profiles (BBP_SKILLS)
for requested service agents.

Service Procurement: Configuration Guide 2005 68