SAP ESourcing Wave 10

Configuration Guide
Document version:1.1 2014-09-24
SAP Sourcing OnDemand Wave 10
PUBLIC
Document History
The following table provides an overview of the most important document changes.
Table 1
Version
Date
Description
1.0
2014-05-16
Initial Release
1.1
2014-09-24
Updated Symantec.
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.

Document History
Content
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3
3.1
3.2
3.3
3.4
3.5
Context, Cluster, and Directory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Manual Context, Cluster, and Directory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Cluster Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Internal Directory Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create External Directory Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Tenant Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
10
14
15
16
18
4
4.1
4.2
4.3
4.4
Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Master Data Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Import Master Data Using CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Workbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of Workbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Download and Customize Workbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Import Master Data Using Workbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
20
24
25
25
25
26
27
Create and Verify Purchaser User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Create and Verify Supplier User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
Install Company Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
Specify Internal Address of SAP Sourcing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Update Master Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
10
Install License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
Change Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
12
Enable Contract Authoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36
13
13.1
13.2
13.3
13.4
13.5
e-Signature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Up EchoSign Account and System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Check EchoSign Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Up User Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resolve e-Signature Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Up Scheduled Task to Retrieve e-Signature Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37
37
38
39
39
40

Content
PUBLIC
34
14
Configure Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
Configure Branding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
16
Configuring Supplier Workflow Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PUBLIC
41
43

Content
Introduction
This guide describes the deployment of SAP Sourcing OnDemand Wave 10 on LJS.
How to Construct an SAP Sourcing Login URL

At various points, this guide will instruct you to log in as a certain user. You can log in as a purchaser user, a
supplier user, the enterprise user, or the system user. You must connect to the system using a different URL
depending on which user the instructions call for. This section explains how to construct the correct login URL for
the specified user.
SAP Sourcing login URLs can be constructed as follows:
[protocol]://[hostname]:[port]/[context]/[login type]/[login path]
Table 2
[protocol]
http or https. Typically https for customer productive

systems.
[port]
The [port] element is optional.
[context]
This is the context you defined during installation.
[login type]
Use one of the following, depending what user is called for in

the instructions:
If the instructions call for a purchaser user, use
fsbuyer.
[login path]
For a supplier user, use fsvendor.
For the system user, use fssystem.
For the enterprise user, use fsenterprise .
For fsbuyer, fsenterprise, and fssystem, this is
portal/login.
For fsvendor, this is vendordesktop/login.
Example
https://www.mycompany.com/mycontext/fsenterprise/portal/login
https://www.mycompany.com/mycontext/fsvendor/vendordesktop/login
https://www.mycompany.com/mycontext/fssystem/portal/login
Note
After the initial login, the system prompts you to change your password

Introduction
PUBLIC
Define System Properties
Note
Some system properties can be overridden at the enterprise level. To do so, log in as the enterprise user.
Virus Scanner Properties

You have two options for virus scanning:
Symantec Protection Engine for Cloud Services
VSI
To enable virus scanning using either method, you must log in as the system user and set the system,
system.avscanner.enabled system property to true.
If you use Symantec Protection Engine for Cloud Services, log in as the system user and configure the properties
in the Symantec Properties table.
If you use VSI, log in as the system user and configure the properties in the VSI Properties table.
Symantec Properties
Note
If you are deploying the Symantec Protection Engine for Cloud Services to scan uploaded attachments for
viruses, you will use the Remote Access API
Table 3
Property
Description
system,system.avsca
Set to TRUE.
nner.enabled
system,
Determines the type of scan mechanism . Set to SYMANTEC_AV.
system.avscanner.ty
pe
system,
Set to the Symantec engine IP address.
system.avscanner.ho
stname
system,
Set either to SCAN_ONLY or SCAN_REPAIR.
system.avscanner.po
licy
PUBLIC

Property
Description
system,
Set to the Symantec ICAP port. The default value is 1344.
system.avscanner.po
Note
rt
You must also configure the protocol (ICAP) and port (1344) in the Symantec Management
console.
system,
Socket timeout. The default value is 30 seconds.
system.avscanner.re
adWriteTime
VSI Properties
Table 4
Property
Description
system,
Determines the type of scan mechanism . Set to VSI_AV.
system.avscanner.ty
pe
system.avscanner.vs
Enter the name of the configured Sourcing-specific AV profile. For example: Z_MCAFEE
i_profile
system.avscanner.vs
Enter the absolute path to the VSI properties file.
i_config_file
Security System Properties

system, system.security.csrf.trusted_referrer_domains
You can specify patterns to identify authorized URLs from which users may submit requests.
A request is trusted under the following circumstances:
If the referrer (the URL from which the request originates) is absent, it is trusted.
If the referrer's domain name is exactly the same as the application's domain, it is trusted.
If the referrer's domain name matches any of the patterns in the system,
system.security.csrf.trusted_referrer_domains system property, it is trusted.
To protect the enterprise itself, set this property as the enterprise user. To provide protection for system-level
tasks, you must also set this property as the system user.
Example
If you set this property only as the enterprise user, any URL can refer requests for system user functionality,
but requests for supplier functionality must come from URLs that match one or more patterns in this system
property. If you set this property as the system user also, then even requests for system user functionality
must come from a trusted URL.
Set the value of the system property system, system.security.csrf.trusted_referrer_domains by
adding one or more of the following patterns, separated by semi-colons:

PUBLIC
Table 5
Pattern
Description
Any referrer is trusted.
*.name.com
Trusted referrer domains must end with the specified string.
Example
*.mydomain.com
Requests from www.mydomain.com and
mobile.mydomain.com and
cloud.mydomain.com, etc, would all be trusted.
Requests from www.mydomain.org would not be
trusted.
name.com
Trusted referrer domains must match the specified string

exactly.
Example
www.mydomain.com
Only requests from www.mydomain.com would be
trusted.
If you add more than one pattern to the property, requests that match any of the included patterns will be trusted.
Example
www.yourdomain.com; *.mydomain.com
Requests from any domain ending in .mydomain.com would be trusted, along with requests from the
www.yourdomain.com domain.
Note
By default this system property is empty, so the only trusted domain is the application's own domain.
Other Security System Properties

This table lists the other security system properties in SAP Sourcing.
Table 6
Property
Description
system, system.cookies.enable_http_only
When True, the browser denies Javascript access to

cookies.
system, system.cookies.enable_secured
When True, cookies can only be passed using the secure
https protocol.
system,
When True, error messages for failed login attempts
system.security.directory.display_entry_do distinguish between invalid credentials (password) and

es_not_exist_error
PUBLIC

Property
Description
nonexistent directory entry (username). When False, both
failures result in the same error message.
system,
When True, this property forces the system to work only
system.security.domain.validate_redirect_u under a single domain. This can adversely affect

rl
performance.
system,
When True, creation or modification of a user account
system.security.separate_pswd_and_name
results in two separate email notifications: one with a

username, one with a password.
system, system.allow.embed.in.iframe

When True, SAP Sourcing can be embedded in an iframe.
PUBLIC
Context, Cluster, and Directory

Configuration
To establish a working environment, you must configure the following components:
Context
Cluster
Directory configurations (internal and external)
Log on as the system user to access all of these configurations. These can be individually created and manually
associated, or they can be configured using the Tenant Configuration utility. When using the utility, the individual
cluster and directory components are created as templates. The Tenant Configuration utility will then create the
context and associate the context, cluster, and directories automatically.
For the purposes of clarity, the association between the three components is as follows:
Context: None
Cluster: Context
Directory configuration: Context and cluster
If SSL Termination is occurring in the load balancer prior to arrival at SAP Sourcing, add the HTTP header XOriginal-HTTPS to the request with a value of on. Sticky sessions must also be enabled by cookie or another
method.
For information related to using SAML 2.0 for the authentication mechanism, see Single Sign-On User
Authentication in the SAP Sourcing 10.0 Security Guide, located at service.sap.com/eso SAP Sourcing
OnDemand SAP Sourcing OnDemand Wave 10 .
For more information about Cluster Configuration, see the SAP Sourcing help, at help.sap.com/sourcing-od
SAP Sourcing OnDemand Wave 10 Help for Purchasers [choose a language] Setup System Setup
Configuration Cluster Configuration .
3.1
Manual Context, Cluster, and Directory Configuration

Note
The manual procedures described in this section can be used instead of using templates for context, cluster,
and directory configuration. If you choose to use templates, do not execute these procedures; you can skip this
section. In general, if you need to make several configurations using the templates can save you time and
effort. If you only have to make one, or a small number, you might prefer to make them manually.
Procedure
Create the Enterprise Context
1.
10
Log on as the system user.

PUBLIC

Context, Cluster, and Directory Configuration
2.
Choose
Setup
System
3.
Choose New.
4.
Fill in the following fields:
Enterprise Contexts .
Display Name
External ID
Sys Admin Password
Sys Admin Password (again)
5.
Choose Save. This will take several minutes to complete.
6.
Choose Done
Create a Cluster Configuration

A cluster configuration is the setup object in SAP Sourcing that provides the means to assign the host name, port,
and selected protocol for the system. In addition, this is where the services that will be available to this cluster are
assigned.
1.
2.
Choose
3.
Create a new cluster, replacing the parameters in the following example with values appropriate to your
needs:
Setup
System
Cluster Configuration , then choose New.
Table 7
Field
Value Description
Display Name
ClusterExample
External ID
cluster.example
Context
Select the context you created in the previous procedure.
Host Name
example.sap.com
Supply the IP address or fully qualified hostname.
Port
50000
Supply the appropriate port. The default is 50000.
4.
In the Settings area:
Choose either HTTP or HTTPS.
Note
We suggest starting with HTTP and enabling HTTPS later.
5.
6.
Leave Automatically add new services and Enable Load Balancing on this cluster unchecked.
Add the service or services to the cluster by executing the following steps for each service you want to add:
1.
In the Cluster Members collection, choose Add.
2.
In the Host Name field, supply the host name.
3.
Using the picker, add a service.
4.
Select the Active checkbox.
5.
Choose OK.
Choose Save

PUBLIC
11
Note
The cluster will display the following message:
This cluster is inactive and cannot be used until it is assigned to both a user directory and enterprise context.
Furthermore, the Inactive Cluster checkbox will be grayed out. This is expected, and will be dealt with later in
the manual configuration process.
Create an Internal Directory Configuration

The internal directory configuration is the setup object that allows the configuration of the authentication method
to be used by internal (supplier-side) users. It can be NetWeaver UME or one of the supported LDAPs. The
example below uses UME.
Note
It is necessary that the users in the UME or LDAP have the same usernames as the users in SAP Sourcing. You
can achieve this by pushing the user accounts from SAP Sourcing to the UME or LDAP, or by pulling them from
the UME or LDAP to SAP Sourcing. Select Push or Pull in the Edit Mode field on Attributes Mapping tab, as
appropriate.
Example
NetWeaver UME Directory Configuration
1.
Log on as the system user and choose Directory Configuration.
2.
Choose New.
3.
Create the directory configuration, replacing the (example) parameters:
External ID: directory.internal.example
Display Name: Internal Directory Example
Context: using the dropdown, choose the context created above.
Default: Select (checked)
Usage: Active Internal
Authentication Support: true
External Role: Assigned UME Sourcing Role
Case Sensitive Username: false
Driver: NetWeaver UME
Cluster: using the picker, choose the cluster created above.
Features: Select (check) the following:
Changeable Passwords
Expired Passwords
New Accounts
Browsing
Properties Tab
Property Name: bypass_error_block
Property Value: true
Attributes Mapping Tab
12
Local ID: NAME
PUBLIC

Mapped ID: uniquename
Edit Mode: Pull
Local ID: EMAIL
Mapped ID: email
Edit Mode: Pull
Local ID: FIRST_NAME
Mapped ID: firstname
Edit Mode: Pull
Local ID: LAST_NAME
Mapped ID: lastname
Edit Mode: Pull
Create an External Directory Configuration

The external directory configuration is the setup object that allows the configuration of the authentication method
to be used by external (supplier-side) users. It can be NetWeaver UME or one of the supported LDAPs. The
example below uses UME.
Note
It is necessary that the users in the UME or LDAP have the same usernames as the users in SAP Sourcing. You
can achieve this by pushing the user accounts from SAP Sourcing to the UME or LDAP, or by pulling them from
the UME or LDAP to SAP Sourcing. Select Push or Pull in the Edit Mode field on Attributes Mapping tab, as
appropriate.
Example
1.
Log on as the system user and choose Directory Configuration.
2.
Choose New.
3.
Create the directory configuration, replacing the (example) parameters:
External ID: directory.external.example
Display Name: External Directory Example
Context: using the dropdown, choose the context created above.
Default: Select (checked)
Usage: Active External
Cluster: using the picker, choose the cluster created above.
Features: Select (check) the following:
Changeable Passwords
Expired Passwords
New Accounts

PUBLIC
13
Browsing
Properties Tab
Attributes Mapping Tab
Local ID: NAME
Edit Mode: Pull
Local ID:EMAIL
Mapped ID: email
Edit Mode: Pull
Edit Mode: Pull
Local ID: LAST_NAME
Mapped ID: lastname
Edit Mode: Pull
Finish and Test the New Context / Cluster / Directory Configuration

In order to complete the configuration, the new cluster must be made active, as follows:
1.
2.
Choose Cluster Configuration.
3.
Choose and edit the inactive cluster configuration you created above.
4.
Uncheck the Inactive checkbox.
5.
Save the cluster.
Test the new enterprise login as follows:

1.
Log out as the system user and log on as the enterprise user, as follows:
<hostname>:<port>/<context>/fsenterprise/portal/login?cid=<cluster-id>
Note
<cluster-id> is the external ID of the new cluster.
3.2
Create Cluster Template
Cluster Templates can be created to make the tenant configuration process faster, but it is not necessary to
create them. The cluster information can also be entered manually in the Create Tenant Configuration [page 18].
14
PUBLIC

Procedure
1.
Log on as the system user and choose Cluster Templates
2.
Choose New
3.
Create a new cluster template with the following (example) parameters:
External ID: cluster.example
Display Name: Cluster Example
Host Name: example.sap.com
3.3
Create Internal Directory Template
Directory Templates can be created to make the tenant configuration process faster, but it is not necessary to
create them. The directory information can also be entered manually in Create Tenant Configuration [page 18]
Procedure
Example
1.
Log on as the system user and choose Directory Templates.
2.
Choose New
3.
Create a new directory template with the following (example) parameters:
Properties
Attributes Mapping
Local ID: NAME
Edit Mode: Pull
Local ID: EMAIL
Mapped ID: email
Edit Mode: Pull

PUBLIC
15
Edit Mode: Pull
Local ID: LAST_NAME
Mapped ID: lastname
Edit Mode: Pull
Example
MSAD LDAP Directory Configuration
1.
2.
Choose New
3.
Driver: LDAP Microsoft Active Directory
LDAP Configuration
3.4
Host: msad.ldap.com
Port: 636
User ID Attribute: samaccountname
Attributes Mapping
Local ID: NAME
Mapped ID: sAMAccountName
Edit Mode: Pull
Local ID: EMAIL
Mapped ID: mail
Edit Mode: Pull
Mapped ID: givenName
Edit Mode: Pull
Local ID: LAST_NAME
Mapped ID: sn
Edit Mode: Pull
Create External Directory Template
Directory Templates can be created to make the tenant configuration process faster, but it is not necessary to
create them. The directory information can also be entered manually in Create Tenant Configuration [page 18] .
16
PUBLIC

Procedure
Example
1.
2.
Choose New.
3.
Properties
Attributes Mapping
Local ID: NAME
Edit Mode: Pull
Local ID: EMAIL
Mapped ID: email
Edit Mode: Pull
Edit Mode: Pull
Local ID: LAST_NAME
Mapped ID: lastname
Edit Mode: Pull
Example
MSAD LDAP Directory Configuration
1.
2.
Choose New
3.

PUBLIC
17
Driver: LDAP Microsoft Active Directory
LDAP Configuration
3.5
Host: msad.ldap.com
Port: 636
User ID Attribute: samaccountname
Attributes Mapping
Local ID: NAME
Mapped ID: sAMAccountName
Edit Mode: Pull
Local ID: EMAIL
Mapped ID: mail
Edit Mode: Pull
Mapped ID: givenName
Edit Mode: Pull
Local ID: LAST_NAME
Mapped ID: sn
Edit Mode: Pull
Create Tenant Configuration
The creation of a tenant configuration will also create:
a context
a cluster
an internal directory
an external directory
The information necessary can be retrieved from cluster and directory templates or entered manually.
Note
For multiple landscape use, all the configurations must have the same name. If not, migration will be affected.
Procedure
1.
Log on as the system user and choose Tenant Configuration
2.
Choose New
3.
Create a new tenant configuration with the following (example) parameters:
18
PUBLIC

Using Templates
External ID: tenant.example
Display Name: Tenant Example
Sys Admin Password:
Sys Admin Password (again):
Cluster: Cluster Example
Directory Internal Site: Internal Directory Example
Directory External Site: External Directory Example
No Templates
External ID: tenant.example
Display Name: Tenant Example
Sys Admin Password:
Sys Admin Password (again):
Overwrite Templates Configurations:
Cluster (checked)
Directory Internal Site (checked)
Directory External Site (checked)
Cluster Configuration [page 14] step
Internal Directory Configuration [page 15] step
External Directory Configuration [page 16] step

PUBLIC
19
Master Data
Gathering Critical Information

For each deployment, gather critical information, including (but not limited to) the following:
Purchaser organizational data: Locations, Companies, Business Units, Groups, and Users
Supplier organizational data: Suppliers and Contacts
Commodity Information: Internal and External Categories
The current implementation methodology recommends defining these attributes before going live to maximize
efficiency. Data attributes may be modified or added throughout the life of the implementation using the Setup
module.
4.1
Overview of Master Data
SAP Sourcing provides the following means to install master data:
Manual entry from Setup
Import from CSV file
Import from deployment workbook
Define the components of master data that exist within each context after contexts and clusters have been
defined. The following table lists the master data object types requiring definition for the enterprise. The data
classification Configurable indicates that default data is provided but can be customized for deployment. The data
classification Custom indicates that no default data is provided and the deployment must provide the data.
Table 8
Contents
Data Classification
Description
Numbering table definitions for
Configurable
Defines the format of IDs. For example,
enterprise-level objects
an RFP might follow the format: RFPnnnn, where nnnn increments for each
new rfp created.
Default list of extendible enterprise-level Configurable
Lists those enterprise-level objects
objects
which can be extended
Default list of objects that can used
Configurable
referenced in an extension
One type of extension allows a reference

to another type of object. This list
identifies the allowed kinds of
references.
Value List Types
Configurable
Default value list types
Value List Values
Configurable
Default value list values, such as

countries, time zones, and so on
20
PUBLIC

Master Data
Contents
Data Classification
Description
Units of Measure
Configurable
Standard units of measure used

throughout the system
Currencies
Configurable
A list of all currencies used by your

organization
Currency Conversions
Configurable
Default values for any currency

conversion rates
Document Link Definitions
Configurable
Lists the allowable kinds of document

links
Scheduled Task Types
Configurable
Used to define categories of scheduled

tasks
Scheduled Tasks
Configurable
Lists scheduled or background tasks
Metrics
Configurable
Used to define metrics for scorecards
Contract Terms
Configurable
Used to define terms on contracts
Contract Types
Configurable
Types define what set of contract

features are available
Project Types
Configurable
Types define what set of Project

RFx Types
Configurable
Types define what set of RFx features

are available
Auction Types
Configurable
Types define what set of Auction

DA Types
Configurable
Types define what set of Demand

Security Profiles
Configurable
Identifies the security profiles installed

with the system
Rights on security profiles
Configurable
Defines the rights for each security

profile
Time Periods
Configurable
Defines information about quarters,

years, and so on
Reporting Calendars
Configurable
Used for managing how data is reported

with relation to the calendar
Collaborator Roles
Configurable
Defines the role (rights and

responsibilities) of a person/group on a
specific document instance
Document Security Templates
Configurable
Sets up the default collaborators and

security when new documents are
created

Master Data
PUBLIC
21
Contents
Data Classification
Description
Shared Discussions
Configurable
A list of discussion forums available as a

channel and not relating to a specific
document
Workbench Channels
Configurable
Channels available on a user's desktop
Workbench IFrames
Configurable
Data to create iFrames
Workbench Channel Configurations
Configurable
Channel configuration parameters
Workbench Pages
Configurable
Pre-defined desktop pages
Workbench Page Configurations
Configurable
Channel content and placement

settings for predefined pages
Configuration Properties
Configurable
Various deployment settings, including

mail
Enterprise Extensions
Custom
Actual extensions on enterprise-level

objects
Directory Configurations
Custom
Used for the LDAP directory

configuration
Geographies
Custom
Used to represent the Geographic

regions
Locations
Custom
Locations of plants, companies, and

other organizational elements
Payment Terms
Custom
Terms of payment between the

purchaser and supplier
External Categories
Custom
Typically this data set consists of

industry standard category codes, such
as UN-SPSC or SIC codes, if used by
your organization.
Internal Categories
Custom
All internal purchasing categories used

by the purchaser
Vendors
Custom
Used in all components for various

purchasing actions
Vendor Extensions in List Form
Custom
Actual extensions on enterprise-level

objects
Companies
Custom
Used by all components of the system

for purchasing actions such as Auctions
and RFPs
Registration Categories
Custom
Defines mapping from arbitrary

category names to actual internal or
external categories. Used during
supplier self-registration.
22
PUBLIC

Master Data
Contents
Data Classification
Description
Organizational Units
Custom
Further definition of the organizational

hierarchy. Use to define departments,
business units, and so on.
Groups
Custom
Arbitrary groups of purchaser users
Contacts
Custom
Used for all suppliers to distinguish the

various contacts at each supplier
Accounts
Custom
Handles all user accounts for the

system
Terms Templates
Custom
Standard terms and conditions phrases

to which a supplier must agree before
accessing an event
Purchasing Organization
Custom
An organizational unit in SAP ERP,

subdividing an enterprise according to
the requirements of purchasing
Purchasing Group
Custom
A key for a purchaser or group of

purchasers in SAP ERP.
Vendor Account Group
Custom
A classifying feature of supplier master

records in SAP ERP
Business System
Custom
Represents a system in the landscape,

for example SAP Sourcing or SAP ERP
Text Id
Custom
Represents SAP ERP header and item

texts
Transaction Type
Custom
Represents SAP ERP transation types
After configuring the enterprise master data, you must next configure the company master data. This data must
be created once for each sub-context. This example only uses a single context, so this data must only be created
once.
Table 9
Contents
Data Classification
Description
UFNs
System
Metadata for RFx utility functions
System Answered Sources
Configurable
Defines the available sources of system

answered questions
Company Extension Definitions
Configurable
List of company-scoped objects which

have extensions
Document Security Templates
Configurable
Sets up the default collaborators and

security when new documents are
created
Contract Generation Phases
Configurable
Used to define Phases for Contract

Generation library documents

Master Data
PUBLIC
23
Contents
Data Classification
Description
Contract Generation Tags
Configurable
Used to define Tags for Contract

Generation
Company extensions
Custom
List of extensions on individual object

types
masterdata.Activity
Custom
Used for general accounting purposes
Cost Centers
Custom
Used for accounting purposes to assign

cost on a center by center basis
Cost Center Groups
Custom
Entities
Custom
Used for accounting purposes for

purchasing by division
GL Accounts
Custom
Used for general accounting purposes
Plants
Custom
Plants or facilities
Materials
Custom
Standard materials for use in line items
Category Managers
Custom
Users who are responsible for certain

categories
Master Data Security

When configuring and importing Master Data there are some things to remember about security:
1.
Each piece of importable master data has an Import right as part of its ACL list. By default, this right is only
added for the System Administrator security profile, and therefore, only those users can import master data
out of the box. As always, an admin can add Import rights to other security profiles, on and object-by-object
basis.
Example
If Supplier Administrators need to import Supplier records, then that can be enabled.
2.
When importing Master Data, be it via CSV, XLS, XML, etc., the user running the imports must have Import
right allowed for all objects in question. The Enterprise user is considered trusted and can import any of these
objects.
4.2
Create Master Data Manually
Procedure
1.
Log on as the enterprise user.
2.
Create objects from within the Setup module.
3.
Log on as a purchaser user with administrative rights to configure company master data.
24
PUBLIC

Master Data
For more information, see the SAP Sourcing help at help.sap.com/sourcing-od . To access the help system,
scroll to SAP Sourcing Wave 10 Help for Purchasers and choose a language. In the help, choose Setup
System Setup Master Data .
4.3
Import Master Data Using CSV File

Note
The user account being used to import the following must have Allow Import rights on these specific objects. If
you do not have Allow Import on these objects, it must be added or the import will fail.
Use the standard web user interface to import data files with CSV, XLS, or XLSX format.
The following procedure describes how to import using the web-based UI.
Procedure
1.
If application users have already been created, log on as a purchaser user with administrative rights. If users
have not been created, log on as the enterprise user.
2.
Choose
3.
Choose Create.
Setup
System Administration
Import Export Tools
Import Data
and then choose OK.
The import wizard opens.

4.
Specify whether you want to upload the file to the server or whether the file is already located on the
application server and choose Next.
5.
Choose Upload Import File and select the CSV or Deployment Workgroup file to import.
6.
For CSV files, select the object type and choose Next.
7.
Indicate whether you want to wait for the import to finish or perform the import in the background and then
choose Next.
8.
Choose Finish to view the results.
4.4
Workbooks
4.4.1
Overview of Workbooks
Note
There are many sheets in the workbooks that have the prefix eso. While these sheets may appear as duplicates
of other sheets, the data in them is in fact different. These sheets should be imported by default. You may also
add data to these sheets if you would like to augment the data provided in the sample workbooks.
We recommend using the deployment workbook for initial deployment of the system to ensure that all required
data is imported into the system

Master Data
PUBLIC
25
To facilitate the import of data, SAP Sourcing provides an alternative to CSV files for import. SAP Sourcing
provides the ability to import Microsoft Excel files containing one or more master data imports. The system
processes these Excel files directly without the user having to export the data to a raw CSV file. The Enterprise
Deployment Workbook and Company Deployment Workbook are two sample deployment workbooks delivered
with SAP Sourcing.
Anyone with system administrator access rights can download the deployment workbooks from the web user
interface. The deployment workbooks are included in the online Reference Guide (RG).
When starting a new deployment project, preserve the original workbook templates by making a copy of them and
saving them with a new name. Import data using your modified templates only. By doing so, you assure continuity
if future, additional deployments are required.
Note
Keep the following in mind when using deployment workbooks:
The Configuration Sheet controls the import process. Refer to the Help Sheet for input specifications of
Configuration Sheet columns.
The system can import the workbooks directly, but there are limitations to what Excel constructs are
supported. The Help Sheet describes the rules that must be observed.
The same importing process supports both CSV files and Excel workbooks.
There is a one to one relationship with the workbook configuration file and the worksheet tabs.
4.4.2
Download and Customize Workbooks
The sample enterprise and company workbooks that you download from SAP Sourcing are designed for you to
configure a base system using a sample enterprise context. We recommend modifying the default deployment
workbooks. Choose the appropriate workbooks from this table:
Table 10
System
SAP Sourcing
SAP CLM
SAP Sourcing and SAP CLM
SAP Supplier Management
Workbooks
Sourcing Enterprise Deployment Workbook
Sourcing Company Deployment Workbook
CLM Enterprise Deployment Workbook
CLM Company Deployment Workbook
Sourcing and CLM Enterprise Deployment Workbook
Sourcing and CLM Company Deployment Workbook
Supplier Management Enterprise Deployment

Workbook
Supplier Management Company Deployment Workbook
Note
By default, these workbooks are based on the premium offering. To implement the standard offering, first
install one of these workbooks, and then use the Enterprise Make Standard Workbook. This applies to all
packages except SAP Supplier Management.
26
PUBLIC

Master Data
Users setting up a base system should adjust the various settings in these workbooks prior to running them in the
system. For example, the company data should be updated to reflect specifics about the company that is
installing the system. Similarly, you should review other tabs to ensure that the configurations are consistent with
the desired implementation.
Note
If you want to use SAP Sourcing on an iPad open the Configurations tab in the workbook, and ensure that
Workbench Page and Channel Configuration are marked Yes in the Enabled column. These configurations
enable structures required for iPad use.
For details on customizable fields, see Master Data [page 20].
Procedure
1.
Log on as the enterprise user and choose Reference Guide. Download the sample enterprise and company
workbooks appropriate for your system.
Note
The enterprise workbook should be run as the enterprise user. The company workbook should be run as a
system administrator associated with the company object intended to be configured.
2.
From the Enterprise Deployment workbook, open the file and find the sheet labeled locations and edit this
sheet as necessary.
Only one location is required.
3.
Find each sheet, review each sheet and the comments in the sheet, and update the data accordingly.
4.
Provide at least one internal category.
5.
Find the sheet labeled companies and edit it as necessary.
6.
Repeat for org_units, groups, accounts, and so on.

Your are establishing a hierarchy. To configure the hierarchy correctly, you must ensure that the child
references the parent correctly. For example, the PARENT column in the business_units page should include
a valid EXTERNAL_ID from the companies sheet.
Note
To build all custom data in the user interface, simply deactivate the import of the above data types in the
deployment workbook. See the Help page for instructions on how to skip a specific worksheet.
7.
Import the enterprise and company workbooks into SAP Sourcing by choosing Setup
Administration Import and Export Tools Import Data and then choose Create.
4.4.3
System
Import Master Data Using Workbooks
Procedure
1.
Log on as the user specified in this table, and choose Setup.

Master Data
PUBLIC
27
Table 11
Workbook
Login User
Enterprise
Enterprise user
workbook
Company workbook
2.
Purchaser user
From the Import and Export Tools dropdown, chooseImport Data, and then choose OK.
The Import Data page appears.
3.
Choose Create to start a new import job.
4.
Choose Upload to the Server and then choose Next.
5.
Select the modified workbook and choose Next.
6.
Wait for the import to finish and choose Next.

Typically, running the enterprise workbook can take several minutes.
28
PUBLIC

Master Data
Create and Verify Purchaser User
Procedure
If the user is pulled from the UME or LDAP to SAP Sourcing, an e-mail is generated, giving the user a path to the
application and his or her user name. If the account is pushed from SAP Sourcing to the UME or LDAP, a
temporary password is also mailed. A system property determines whether this information is delivered in the
same e-mail or separate e-mails.
1.
Choose
Internal Accounts
and create a purchaser user as follows:
1.
On the Account Properties tab, enter required information.
2.
On the Account Management tab, enter information as follows:
3.
2.
Setup
Enable User to Login: Select
Directory: Select as needed
User ID: Type userid
Create Directory Account: Select
Generate a New Password: Select
Send Notification: Select
On the Security tab, enter information as follows:
Purchaser: Select
Purchaser Manager: Select
System Administrator: Select
Supplier Administrator: Select
Make sure this first user is given Administrator privileges to import the Company Workbook.
Wait for the e-mail to be sent and received. If you do not receive it, check the following:
To verify the mail was sent, choose
To check for stuck or failed messages, choose
Setup
Setup
Processed Messages .
Queued Messages .
3.
To test the new account, log on as a purchaser user, using the credentials sent in the e-mail.
4.
Reset your password and choose OK.

If you can successfully log into the new purchaser account, the context cluster and directory are properly
configured and the SMTP server is processing e-mail.

Create and Verify Purchaser User
PUBLIC
29
Create and Verify Supplier User
Procedure
Create a supplier user to test the supplier portal. A supplier user is a contact on a supplier record.
1.
Choose
2.
Enter and save the required information.
3.
Choose the Contacts tab.
4.
Under Supplier Contacts, choose Add.
5.
Enter and save the required information.
6.
Log on as a supplier user, using the credentials provided in the test user e-mail.
7.
Reset the password as prompted and accept the usage terms.
30
Supplier Management
PUBLIC
Create Supplier .

Create and Verify Supplier User
Install Company Logo
Procedure
Note
We do not recommend installing an image larger than 200 x 29.
1.
2.
Attach the logo as follows:
3.
1.
Choose
Setup
Organization and Accounting Information
Companies .
2.
Select the enterprise company from the list and choose Edit Document.
3.
Attach your logo image to the company using the Logo Attachment field.
Save your entries.
Resize Company Logo

If you have uploaded a company logo in your source release, you must resize the image to 200x29.
1.
Log on as a purchaser user with system administrator rights.
2.
Choose Setup.
3.
On the Master Data tab, find the Organization and Accounting section and choose Companies.
4.
Choose the company.
5.
Choose Edit.
6.
In the Logo field, upload the resized image.

Install Company Logo
PUBLIC
31
Specify Internal Address of SAP Sourcing

Server
Procedure
When SAP Sourcing is first installed or whenever a new server is added to an application cluster, the Internet
address that is used for internal communications within SAP Sourcing is initially set to the external host name of
the server. In many cases, this will result in unexpected or delayed behavior in the application.
If the application landscape includes a network firewall, accessing the server through this name requires exiting
the firewall and re-entering. If the firewall blocks incoming traffic on SAP Sourcings notification ports, this will
result in failure to deliver notifications for some events. To avoid this, do the following:
1.
2.
Open the System Information record for editing.
3.
Change the value in the Internal Address field to an internal IP address or host name.
4.
Save your changes.
32
PUBLIC

Specify Internal Address of SAP Sourcing Server
Update Master Time Zone
Procedure
This procedure is required to enable SAP Sourcing to normalize all dates and times that are used in sourcing
events. Normalizing allows time fields to be presented differently for each user, according to his or her preferred
time zone, while maintaining a consistent reference to the same point in time.
1.
2.
Choose
3.
Edit the system.master_timezone property in the system set. This property value should be set to the Java
time zone identifier that corresponds to the current database server time zone.
Setup
Configuration
System Properties .
Note
The SAP Sourcing Time Zone Value List Type provides a relatively comprehensive list of java time zone
identifiers. To view this list, log on as a purchaser user and navigate to Setup Master Data Value List
Types and Values Time Zone. . The Alternate Name column of this list contains the java time zone identifier
for the corresponding time zone.
Example
America/New_York is the alternate name of the SAP Sourcing Timezone ValueListValue for (GMT-5:00)
Eastern Standard Time.

Update Master Time Zone
PUBLIC
33
10 Install License Key
Procedure
You must install a license key before the SAP Sourcing system can be used in production mode.
1.
Choose
Setup
System Management
System Information .
2.
Note the installation ID from the Installation ID field on the Service Registration tab.
3.
Create OSS ticket this ID and a list of the requested modules to license (include the optimizer) to SAP
Customer Support. You will receive a .csv file including all the license keys.
Note
Requesting the optimizer key without installing an optimizer server will result in a high volume of irrelevant
optimizer-related messages in your log files. If you do not intend to install an optimizer server, do not
request an optimizer key.
4.
Log on as the enterprise user and choose

Import Data .
5.
Use the import tool to import the licenses you received from Support, as follows:
1.
Setup
Import and Export Tools
On the Import Wizard: Select a File screen, type a description such as License Keys and choose Upload
Import File to upload the .csv file. Choose Next.
2.
On the Import Wizard: CSV Contents screen, select Module License as the Object Type, choose Next, and
follow any additional prompts to finish the process. The successful file import is displayed on the File
Import tab.
6.
Choose
7.
Choose the Components tab and verify that the appropriate licenses are checked under SRM Module
Licenses.
8.
If you are installing the optimizer, verify that a new Optimizer tab appears and displays an appropriate Status
Queue value and JVM information. (If the optimizer is not installed, the Status Queue value is OFFLINE and
the JVM Information is set to unknown.)
34
Setup
PUBLIC
System Management
System Information .

Install License Key
11
Change Session Timeout
Procedure
Note
This is optional.
The deployment descriptor for the SAP Sourcing application defaults to a 30-minute session timeout or to the
value that was set during installation.
Note
The above property should be set longer than the below two properties.
To change this setting:
1.
Log on as the system user and set the following system property in SAP Sourcing:
upp.metering.login_inactivity_timeout and set to the timeout that was chosen when running the
configure utility.
2.
Property upp.metering.cleanup_interval defines the time between runs of the daemon, which
removes inactive sessions. It is recommended that this value be set to a value that is slightly larger than the
upp.metering.login_inactivity_timeout setting is set to.
3.
Set the time-out using the configure tool. For information about the configure tool, see the Installation Guide
for SAP Sourcing 10.0 on the SAP Service Marketplace at service.sap.com/eso SAP Sourcing OnPremise SAP Sourcing 10.0 .
Note
Both internal property in SAP Sourcing and configuration tool in NetWeaver should be set to the same value.

Change Session Timeout
PUBLIC
35
12
Enable Contract Authoring
Contracts, amendments, and clauses use the contract generation service to generate contract documents.
Procedure
To use the DOCX Contract Generation Service, follow these steps:
1.
Choose
2.
From the Name dropdown list, choose contractgen.wordservice.enabled.
3.
Make sure the value isFALSE. If not, set the value to FALSE.
36
Setup
System Properties .
PUBLIC

Enable Contract Authoring
13
e-Signature
To enable e-Signature functionality, users first get user accounts from EchoSign. EchoSign adds the users to the
EchoSign SAP channel. System administrators define the integrated system configuration, and set up the
management of customer and user accounts. System administrators can schedule automated checks of contract
document signature statuses. System users can check the availability of e-Signature components,
Note
e-Signature is available only with SAP Sourcing OnDemand Wave 10 premium package, in both public and
private editions.
13.1
Set Up EchoSign Account and System Configuration
Procedure
Set Up EchoSign Account
Before a system administrator enables e-Signature features for a customer, EchoSign adds the customer to the
EchoSign SAP channel. The customer gives the account key provided by EchoSign to the system administrator.
The system administrator then configures e-Signature to work with EchoSign.
Set Up Integrated System Configuration

Adding an EchoSign account to SAP Sourcing configuration enables e-Signature functionality in SAP Sourcing. To
set up an EchoSign account for use with e-Signature, a system administrator creates an integrated system
configuration object for EchoSign integration.
1.
2.
Choose
3.
On the subsequent screen, choose New.
4.
On the subsequent screen, select EchoSign for System Type, and select Continue.
5.
Under EchoSign Properties, the customer enters the EchoSign account key provided the customer by
EchoSign, and choose Done.
Setup
Integrated System Configuration .
Set Up Proxy Settings

To connect with the EchoSign servers in OnDemand installations running on Lean Java Server where there is a
proxy server in the landscape, a system administrator sets JVM parameters as follows:
In <LJS installation folder>\props.ini, add the following properties:
-Dhttp.proxyHost=proxy
-Dhttp.proxyPort=8080
-Dhttps.proxyHost=proxy
-Dhttps.proxyPort=8080

e-Signature
PUBLIC
37
In <LJS installation folder>\configuration\config.ini, add the following configuration:
http.nonProxyHosts=<non proxy hosts>
Change EchoSign service URL

SAP Sourcing ships with the current EchoSign service URL. Change the service URL value in System Properties
only when EchoSign changes the service URL. To change this value, do the following:
1.
2.
On the System Setup tab, choose System Properties.
3.
Open contractgen.esignature_url from the Properties list.
4.
Enter the new EchoSign service URL provided by EchoSign.
Note
Set the URL property only if the EchoSign domain has changed. The current url is secure.echosign.com/
services/EchoSignDocumentService9. Note that the API version should be set to 9.
Change the length of the EchoSign timeout

By default, SAP Sourcing sets the length of the EchoSign timeout to 300,000 milliseconds, or five minutes.
Change the length of the EchoSign timeout only if the default timeout causes issues when you send documents to
EchoSign.
1.
2.
On the System Setup tab, choose System Properties.
3.
Choose contractgen.esignature_timeout from the Name dropdown menu.
4.
Enter a numeral specifying the desired length, in milliseconds, for the EchoSign timeout in the Value field. The
Value field requires no minimum, nor maximum, value, nor number formatting.
13.2 Check EchoSign Configuration Status

Procedure
1.
2.
Choose System Information. Then, on the subsequent screen, choose the Audits tab.
3.
Choose the correct context for the customer's location from the Context dropdown menu.
4.
In the Availability pane, OK appears in the Status column next to EchoSign Availability if you configured SAP
Sourcing correctly for EchoSign.
38
PUBLIC

e-Signature
13.3 Set Up User Rights

Procedure
Assign Right to Send Contract Documents for Signatures, or to Resolve Errors
To enable a user to send contract documents for signatures, a customer system administrator adds Contract eSignature to the user's security profiles.
To assign the right to send contract documents out for signatures to a user, a system administrator does the
following:
1.
In Setup, choose
2.
Select the desired user account.
3.
Choose the Security tab. Then choose Contract e-Signature, or Contract e-Signature Admin.
Internal User Accounts .
A system administrator can assign either of the following e-Signature rights to a user.
Table 12
Right
Description
ESO_CONTRACT_ESIGNATURE
Users with this right can send contract documents out for
signatures using the e-Signature feature.
ESO_CONTRACT_ESIGNATURE_ADMIN
This right allows designated users to resolve errors. Users

with this right can change a contract document while it is
out for signatures. Users with this right can change the
signature status of a contract document to Error, and can
thus allow the contract document author to unlock a
frozen document. System administrators assign this right
only to other administrators, not to standard users.
4.
Choose Done.
13.4 Resolve e-Signature Errors

Procedure
Unexpected errors, such as network or system errors, can freeze the status of a contract document to Sending
for e-Signature, or Out for Signature. A user with the right ESO_CONTRACT_ESIGNATURE_ADMIN can unfreeze
the status of the contract document so that the contract author can cancel the e-Signature process. A system
administrator can assign the right ESO_CONTRACT_ESIGNATURE_ADMIN to a user.
1.
The contract author adds a user with the ESO_CONTRACT_ESIGNATURE_ADMIN right to the affected
Master Agreement as a collaborator.
2.
The user with the ESO_CONTRACT_ESIGNATURE_ADMIN right manually changes the status of the frozen
contract document to ERROR.
3.
The contract author logs in to EchoSign, and manually cancels the e-Signature process for the contract
document.

e-Signature
PUBLIC
39
13.5 Set Up Scheduled Task to Retrieve e-Signature Status

Procedure
You can set SAP Sourcing to retrieve the e-Signature statuses of all contract documents, at a frequency you
specify, automatically. However, an end user need not wait for these automated retrievals to see the current eSignature status of a contract document. End users can get instant updates of the e-Signature status manually
through the contract document user interface.
1.
2.
Choose Setup.
3.
On the System Setup tab, choose Scheduled Tasks.
4.
On the subsequent page, choose New, then select the e-Signature Status radio button, then choose Continue.
5.
Enter the display name, and start date. Set the frequency and end date, as desired.
Note
SAP recommends automatically retrieving e-Signature statuses daily, and setting the retrievals to run at
night.
6.
40
Choose Save.
PUBLIC

e-Signature
14 Configure Workbench
The CLM system is delivered with a base workbench page that is available to all internal users. Additionally, the
system is configured with a workbench page intended to be used by CLM contract managers.
The workbench page is established in the system, but requires additional configuration to make it available to the
desired users. This configuration is done by adding collaborators to the Contract Management Workbench page.
Prerequisites
You must be logged on as the enterprise user.
Procedure
Configure the Contract Management Workbench page with the individual users or user groups that should also
have access to the page.
To do this, go to Setup System Setup Workbench
Contract Management page and add collaborators.

Configure Workbench
Workbench Page
All Workbench Pages . Edit the
PUBLIC
41
15
Configure Branding
The following procedures enable you to change the branding from the default SAP Sourcing to SAP CLM. Four
branding items are affected:
Branding text in the title bar of the browser (for example, SAP Sourcing)
SAP CLM logo image for the purchaser login page
SAP CLM Business Partner logo image for the supplier login page
Images on the login page
Images on the splash screen
Procedure
Change the Branding after Installation
1.
Choose
Setup
System Properties .
2.
Change the value of system.brand_name to (for example) SAP CLM.
Themes
Note
The following two steps require editing of themes. For further information about themes, see the SAP Sourcing
help at help.sap.com/sourcing-od . To access the help system, scroll to SAP Sourcing Wave 10 Help for
Purchasers and choose a language. In the help, choose Setup Themes .
1.
Open the current enterprises theme Branding area and choose Purchaser Login Banner link, then Image link.
Delete the original path in Image Path field, and paste /images/logos/logo_sapXCLM.gif.
2.
Choose Delete on Background Image field.
3.
Choose the Supplier Login Banner link, then Image link. Delete the original path in Image Path field, and
paste /images/logos/logo_sapXCLMBusinessPartner.gif.
4.
Choose Delete on Background Image field.
42
PUBLIC

Configure Branding
16
Configuring Supplier Workflow

Management
By default supplier workflow management feature is disabled in SAP Sourcing. To enable this feature you need to
perform following general steps:
1.
Create Workflow Definitions
2.
Create Supplier Configurable Phase Definition
3.
Create/Modify Supplier Type
4.
Create Supplier Field Access Definition (optional)
5.
Configure Security Templates
6.
Assign Supplier Types to Suppliers
7.
Configure Supplier UI Mapping
The following subsections provide details for each of these steps.
Create Workflow Definitions

1.
Click Setup in the toolbar at the top of the page and select Platform.
2.
In the Workflow section of System Setup, click on Workflow Definitions.
3.
On the Workflow Definitions List page, click New.
4.
On the Workflow Definition Summary page, fill in the fields with workflow information. For details, see the
Field Help for Workflow Definition Summary page.
5.
Click the Add New Version button to add a process template to the workflow definition. For details, see the
Field Help for Process Template Dialog Box page.
6.
Click the Save button in the toolbar.
7.
Create another Workflow Definition if necessary.
Create Supplier Configurable Phase Definition

Supplier phases determine the actions that can be performed on supplier registration and modification requests.
To create a supplier configurable phase definition:
1.
2.
In the Suppliers section of Document Setup, click on Supplier Configurable Phase Definition.
3.
On the Supplier Configurable Phase Definition List page, click New.
4.
On the Header page, fill in the fields with phase information. For details, see the Field help for Supplier
Configurable Phase Definition Header page.
5.
Click Add to add phases to the definition.
6.
In the dialog box that appears, select each phase to include in the phase definition and click OK.
7.
(optional) Click the Edit icon for each phase to edit phase information, including the sequence of phases in
the workflow. On this page you can assign workflow definition and supplier field access definition. For details,
see the Field help for Supplier Configurable Phase Header page.
8.

Configuring Supplier Workflow Management
PUBLIC
43
9.
Create another Supplier Configurable Phase Definition if necessary.
Create/Modify Supplier Type

Supplier types can be used to determine whioch workflow phase definition to enable in a supplier registration or
modification requests. The Configurable Phase Definition field of Supplier Type is responsible for defining
whether registration/modification requests will use workflow and which phases will have these requests. If
Configurable Phase Definition is empty then supplier registration and modification requests will not have
configured phases and any supplier administrator will be able to approve or deny request of such type as it was in
previous versions of SAP Sourcing. To enable supplier workflow management some supplier-configurable phase
definition must be assigned to supplier types.
SAP Sourcing provides one default supplier type. You can modify this type and create new ones.
1.
Click Setup in the toolbar at the top of the page, and select Platform.
2.
In the Suppliers section of Document Setup, select Supplier Type.
3.
On the Supplier Type List page, click New for creating new type or select existing from the list for editing.
4.
On the Type page, fill in necessary fields. On this page you can assign Supplier Configurable Phase Definition
to Supplier Type. For details, see the Field Help for Supplier Type page.
Create Supplier Field Access Definition

This step is optional.
Supplier Field Access Definition allows you to configure access rules foe approver on specific phase.
To create a supplier field access definition:
1.
2.
In the Suppliers section of Document Setup, select Supplier Field Access Definition.
3.
On the Supplier Field Access Definition List page, click New.
4.
On the UI page fill in necessary fields. For details, see the Field Help for Supplier Field Access Definition
page.
5.
6.
Open existing Supplier Configurable Phase Definition.
7.
Click Edit.
8.
Click the Edit icon for the phase where you want to configure access rights for approvers. This should be the
approval phase.
9.
Click the Lookup icon to select a supplier field access definition to associate with this phase.
10. Save the Supplier Configurable Phase Definition.
Configure Security Templates

This is a very important configuration step. In the case of supplier registrations/modifications without configured
workflows, requests can be viewed and approved by any Supplier Administrator. But in the case of new
functionality collaborator, security is used to define access rights. A document security template is a set of rules
governing the way an SAP Sourcing document assigns collaborator roles. You should configure collaborators,
defined by role and user type, that are automatically added to a registration and modification requests.
You must configure two security templates: first for Workflow Supplier Registration and second for Workflow
Supplier Modification. The following must be configured in these templates:
44
The document owner must be any specified buy-side user. Otherwise automatic phase transitions will not
work for sell-side and the phase will need to be changed manually by any buy-side user.
PUBLIC

Document creator (current user) must be added to collaborator list with a role that allows viewing, editing,
and changing phases (e.g. Collaborator).
Supplier administrators should be included to collaborator list to be able view and manually complete
registration/modification requests, in case automatic completion should fail for some reason.
Assign Supplier Type to Supplier

After the upgrade procedure, one default supplier type is created and assigned to all suppliers. It will be used to
recognize phases for supplier modifications via workflow. The supplier type can be changed for any supplier, as
follows:
1.
Open the supplier whose supplier type you want to reassign.
2.
Press Edit.
3.
Click the Lookup icon under the Document Type field.
4.
Select a new supplier type.
5.
Click Ok.
6.
Click Save
Note
When the supplier is created via workflow, the supplier type used for creation is assigned to created supplier.
Configure Supplier UI Mapping

The supplier type can be mapped to any supplier-side self-registration form. The Supplier Type UI includes a
collection of Supplier registration UI Mappings. This allows you to configure the mapping between supplier type
and self-registration forms:
1.
Open any Supplier Type
2.
Click Edit.
3.
Click Add under Sell-Side Supplier Registration UI Mapping to add the UI page that will be mapped to this
type.
4.
Click Save.
Note
The self-registration form can be assigned to only one supplier type. If no form is assigned to a supplier type,
the default supplier type will be used for registration.

PUBLIC
45
Typographic Conventions
Table 13
Example
Description
<Example>
Angle brackets indicate that you replace these words or characters with appropriate entries
to make entries in the system, for example, Enter your <User Name>.
Example
Example
Arrows separating the parts of a navigation path, for example, menu options
Example
Emphasized words or expressions
Example
Words or characters that you enter in the system exactly as they appear in the
documentation
www.sap.com
Textual cross-references to an internet address
/example
Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web
123456
Example
Hyperlink to an SAP Note, for example, SAP Note 123456
Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
Example
Cross-references to other documentation or published works
Output on the screen following a user action, for example, messages
Source code or syntax quoted directly from a program
File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE
Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE
46
PUBLIC
Keys on the keyboard

Typographic Conventions
PUBLIC
47
www.sap.com
Copyright 2014 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. National product specifications may vary.
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.
SAP 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 other countries.
Please see www.sap.com/corporate-en/legal/copyright/
index.epx#trademark for additional trademark information and
notices.
Please see www.sap.com/corporate-en/legal/copyright/index.epx
for disclaimer information and notices.

SAP ESourcing Wave 10

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP ESourcing Wave 10

Uploaded by

Copyright:

Available Formats

Configuration Guide

Document version:1.1 2014-09-24

SAP Sourcing OnDemand Wave 10

SAP Sourcing OnDemand Wave 10

Define System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Context, Cluster, and Directory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create and Verify Purchaser User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Create and Verify Supplier User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Install Company Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Specify Internal Address of SAP Sourcing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Update Master Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Install License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Change Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Enable Contract Authoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SAP Sourcing OnDemand Wave 10

Configuring Supplier Workflow Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SAP Sourcing OnDemand Wave 10

How to Construct an SAP Sourcing Login URL

http or https. Typically https for customer productive

The [port] element is optional.

This is the context you defined during installation.

Use one of the following, depending what user is called for in

If the instructions call for a purchaser user, use

For a supplier user, use fsvendor.

For the system user, use fssystem.

For the enterprise user, use fsenterprise .

For fsbuyer, fsenterprise, and fssystem, this is

SAP Sourcing OnDemand Wave 10

Define System Properties

Virus Scanner Properties

Symantec Protection Engine for Cloud Services

Determines the type of scan mechanism . Set to SYMANTEC_AV.

Set to the Symantec engine IP address.

Set either to SCAN_ONLY or SCAN_REPAIR.

SAP Sourcing OnDemand Wave 10

Set to the Symantec ICAP port. The default value is 1344.

Socket timeout. The default value is 30 seconds.

Determines the type of scan mechanism . Set to VSI_AV.

Enter the absolute path to the VSI properties file.

Security System Properties

SAP Sourcing OnDemand Wave 10

Any referrer is trusted.

Trusted referrer domains must end with the specified string.

Trusted referrer domains must match the specified string

Other Security System Properties

When True, the browser denies Javascript access to

When True, cookies can only be passed using the secure

When True, error messages for failed login attempts

system.security.directory.display_entry_do distinguish between invalid credentials (password) and

SAP Sourcing OnDemand Wave 10

When True, this property forces the system to work only

system.security.domain.validate_redirect_u under a single domain. This can adversely affect

When True, creation or modification of a user account

results in two separate email notifications: one with a

SAP Sourcing OnDemand Wave 10

When True, SAP Sourcing can be embedded in an iframe.

Context, Cluster, and Directory

To establish a working environment, you must configure the following components:

Directory configurations (internal and external)

Directory configuration: Context and cluster

Manual Context, Cluster, and Directory Configuration

Log on as the system user.

SAP Sourcing OnDemand Wave 10

Fill in the following fields: