Beruflich Dokumente
Kultur Dokumente
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.
Content
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3.1
3.2
3.3
3.4
3.5
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
30
31
10
11
12
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
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
34
14
Configure Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
Configure Branding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
16
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
41
43
Introduction
This guide describes the deployment of SAP Sourcing OnDemand Wave 10 on LJS.
[protocol]
[port]
[context]
[login type]
fsbuyer.
[login path]
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
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
Note
Some system properties can be overridden at the enterprise level. To do so, log in as the enterprise user.
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,
system.avscanner.ty
pe
system,
system.avscanner.ho
stname
system,
system.avscanner.po
licy
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
Property
Description
system,
system.avscanner.po
Note
rt
You must also configure the protocol (ICAP) and port (1344) in the Symantec Management
console.
system,
system.avscanner.re
adWriteTime
VSI Properties
Table 4
Property
Description
system,
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
i_config_file
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
Copyright 2014 SAP AG.
All rights reserved.
Table 5
Pattern
Description
*.name.com
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
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.
Property
Description
system, system.cookies.enable_http_only
system, system.cookies.enable_secured
https protocol.
system,
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
Property
Description
nonexistent directory entry (username). When False, both
failures result in the same error message.
system,
performance.
system,
system.security.separate_pswd_and_name
system, system.allow.embed.in.iframe
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
Context
Cluster
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
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
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
2.
Choose
Setup
System
3.
Choose New.
4.
Enterprise Contexts .
Display Name
External ID
5.
6.
Choose Done
2.
Choose
3.
Create a new cluster, replacing the parameters in the following example with values appropriate to your
needs:
Setup
System
Table 7
Field
Value Description
Display Name
ClusterExample
External ID
cluster.example
Context
Host Name
example.sap.com
Supply the IP address or fully qualified hostname.
Port
50000
Supply the appropriate port. The default is 50000.
4.
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.
2.
3.
4.
5.
Choose OK.
Choose Save
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
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.
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.
2.
Choose New.
3.
Changeable Passwords
Expired Passwords
New Accounts
Browsing
Properties Tab
12
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
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.
2.
Choose New.
3.
Changeable Passwords
Expired Passwords
New Accounts
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
13
Browsing
Properties Tab
Local ID:EMAIL
2.
3.
Choose and edit the inactive cluster configuration you created above.
4.
5.
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
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
Copyright 2014 SAP AG.
All rights reserved.
Procedure
1.
2.
Choose New
3.
3.3
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
NetWeaver UME Directory Configuration
1.
2.
Choose New
3.
Properties
Attributes Mapping
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
15
Example
MSAD LDAP Directory Configuration
1.
2.
Choose New
3.
LDAP Configuration
3.4
Host: msad.ldap.com
Port: 636
Attributes Mapping
Mapped ID: sn
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
Copyright 2014 SAP AG.
All rights reserved.
Procedure
Example
NetWeaver UME Directory Configuration
1.
2.
Choose New.
3.
Properties
Attributes Mapping
Example
MSAD LDAP Directory Configuration
1.
2.
Choose New
3.
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
17
LDAP Configuration
3.5
Host: msad.ldap.com
Port: 636
Attributes Mapping
Mapped ID: sn
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.
2.
Choose New
3.
18
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
Using Templates
No Templates
Cluster (checked)
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
19
Master Data
Purchaser organizational data: Locations, Companies, Business Units, Groups, and Users
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
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
Configurable
enterprise-level objects
an RFP might follow the format: RFPnnnn, where nnnn increments for each
new rfp created.
objects
Configurable
referenced in an extension
Configurable
Configurable
20
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
Contents
Data Classification
Description
Units of Measure
Configurable
Currencies
Configurable
Currency Conversions
Configurable
Configurable
Configurable
Scheduled Tasks
Configurable
Metrics
Configurable
Contract Terms
Configurable
Contract Types
Configurable
Project Types
Configurable
RFx Types
Configurable
Auction Types
Configurable
DA Types
Configurable
Security Profiles
Configurable
Configurable
Time Periods
Configurable
Reporting Calendars
Configurable
Collaborator Roles
Configurable
Configurable
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
21
Contents
Data Classification
Description
Shared Discussions
Configurable
Workbench Channels
Configurable
Workbench IFrames
Configurable
Configurable
Workbench Pages
Configurable
Configurable
Configuration Properties
Configurable
Enterprise Extensions
Custom
Directory Configurations
Custom
Geographies
Custom
Locations
Custom
Payment Terms
Custom
External Categories
Custom
Internal Categories
Custom
Vendors
Custom
Custom
Companies
Custom
Registration Categories
Custom
22
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
Contents
Data Classification
Description
Organizational Units
Custom
Groups
Custom
Contacts
Custom
Accounts
Custom
Terms Templates
Custom
Purchasing Organization
Custom
Purchasing Group
Custom
Custom
Business System
Custom
Text Id
Custom
Transaction Type
Custom
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
Configurable
Configurable
Configurable
Configurable
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
23
Contents
Data Classification
Description
Configurable
Company extensions
Custom
masterdata.Activity
Custom
Cost Centers
Custom
Custom
Entities
Custom
GL Accounts
Custom
Plants
Custom
Plants or facilities
Materials
Custom
Category Managers
Custom
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
Procedure
1.
2.
3.
Log on as a purchaser user with administrative rights to configure company master data.
24
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
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
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 Data
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.
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
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
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
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
Workbooks
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
Copyright 2014 SAP AG.
All rights reserved.
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.
5.
6.
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
Procedure
1.
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
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.
4.
5.
6.
28
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
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
System Administration
Internal Accounts
1.
2.
3.
2.
Setup
Purchaser: 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:
Setup
System Administration
Setup
Processed Messages .
System Administration
Queued Messages .
3.
To test the new account, log on as a purchaser user, using the credentials sent in the e-mail.
4.
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
29
Procedure
Create a supplier user to test the supplier portal. A supplier user is a contact on a supplier record.
1.
Choose
2.
3.
4.
5.
6.
Log on as a supplier user, using the credentials provided in the test user e-mail.
7.
30
Supplier Management
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
Create Supplier .
Procedure
Note
We do not recommend installing an image larger than 200 x 29.
1.
2.
3.
1.
Choose
Setup
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.
2.
Choose Setup.
3.
On the Master Data tab, find the Organization and Accounting section and choose Companies.
4.
5.
Choose Edit.
6.
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
31
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.
3.
Change the value in the Internal Address field to an internal IP address or host name.
4.
32
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
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.
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
33
Procedure
You must install a license key before the SAP Sourcing system can be used in production mode.
1.
Choose
Setup
System Administration
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.
5.
Use the import tool to import the licenses you received from Support, as follows:
1.
Setup
System Administration
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
System Administration
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
System Management
System Information .
11
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.
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
35
12
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.
3.
Make sure the value isFALSE. If not, set the value to FALSE.
36
Setup
System Properties .
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
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
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.
2.
Choose
3.
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
-Dhttp.proxyHost=proxy
-Dhttp.proxyPort=8080
-Dhttps.proxyHost=proxy
-Dhttps.proxyPort=8080
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
37
2.
3.
4.
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.
2.
3.
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.
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
Copyright 2014 SAP AG.
All rights reserved.
In Setup, choose
2.
3.
Choose the Security tab. Then choose Contract e-Signature, or Contract e-Signature Admin.
System Administration
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
4.
Choose Done.
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.
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
39
2.
Choose Setup.
3.
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
Copyright 2014 SAP AG.
All rights reserved.
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.
Workbench Page
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
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 Business Partner logo image for the supplier login page
Procedure
Change the Branding after Installation
1.
Choose
Setup
System Properties .
2.
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.
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.
42
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
16
By default supplier workflow management feature is disabled in SAP Sourcing. To enable this feature you need to
perform following general steps:
1.
2.
3.
4.
5.
6.
7.
Click Setup in the toolbar at the top of the page and select Platform.
2.
3.
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.
7.
Click Setup in the toolbar at the top of the page and select Platform.
2.
In the Suppliers section of Document Setup, click on Supplier Configurable Phase Definition.
3.
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.
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.
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
43
9.
Click Setup in the toolbar at the top of the page, and select Platform.
2.
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.
Click Setup in the toolbar at the top of the page and select Platform.
2.
In the Suppliers section of Document Setup, select Supplier Field Access Definition.
3.
4.
On the UI page fill in necessary fields. For details, see the Field Help for Supplier Field Access Definition
page.
5.
6.
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.
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
Copyright 2014 SAP AG.
All rights reserved.
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.
2.
Press Edit.
3.
4.
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.
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
Copyright 2014 SAP AG.
All rights reserved.
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
Example
Words or characters that you enter in the system exactly as they appear in the
documentation
www.sap.com
/example
Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web
123456
Example
Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
Example
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
Copyright 2014 SAP AG.
All rights reserved.
PUBLIC
Copyright 2014 SAP AG.
All rights reserved.
47
www.sap.com