You are on page 1of 36

Configuration Guide SAP Sourcing 7.

0
Target Audience ■ System administrators ■ Consultants

PUBLIC Document version: 1.4 – 2012-05-12

Document History

The following table provides an overview of the most important document changes.
Version Date Description

1.0 1.1 1.2 1.3 1.4

2011-02-28 2011-11-11 2012-02-02 2012-03-09 2012-05-17

Initial version Enhanced Global Search information Managing the SSL Certificate Corrected workbook names. Added security system property.

2/36

PUBLIC

2012-05-12

Table of Contents

Chapter 1 1.1 1.2 1.2.1 1.2.2 1.2.3 1.2.4 1.2.5 1.3 1.3.1 1.3.2 1.3.3 1.3.4 1.3.4.1 1.3.4.2 1.3.4.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11 1.12 1.13 Chapter 2 2.1 2.1.1

Basic Settings for SAP Sourcing and CLM . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Define System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Context, Cluster, and Directory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 8 Create Cluster Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Create Internal Directory Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Create External Directory Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Managing the SSL Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Create Tenant Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Overview of Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Create Master Data Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Import Master Data Using CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Workbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Overview of Workbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Download and Customize Workbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Import Master Data Using Workbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Create and Verify Buy-Side User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Create and Verify Sell-Side User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Install Company Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Specify Internal Address of SAP Sourcing Server . . . . . . . . . . . . . . . . . . . . . . . 20 Update Master Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Install License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Change Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Enable Contract Authoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Configure Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Configure Branding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Basic Settings for Search in SAP Sourcing and CLM . . . . . . . . . . . . . . . . . 25 Search Via KM and Trex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Configuration of Knowledge Management Content Search and TREX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2012-05-12

PUBLIC

3/36

2.1.1.1 2.1.1.2 2.1.2 2.1.2.1 2.1.2.2 2.1.2.3 2.1.3 2.2 2.3

Configure TREX Server in KM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploy KM SCA File to KM Server Using SDM . . . . . . . . . . . . . . . . . . . . . . . . Authentication Between KM Server and SAP Sourcing Server . . . . . . . . . . . . . Overview of Authentication Between KM and TREX Server and SAP Sourcing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Basic Authentication for KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up KM HTTP Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up KM System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up Indexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshoot KM Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

25 26 26 26 26 27 28 30 31

4/36

PUBLIC

2012-05-12

1 1.1

Basic Settings for SAP Sourcing and CLM Define System Properties

1 Basic Settings for SAP Sourcing and CLM

This guide describes the deployment of SAP Sourcing 7.0 on SAP NetWeaver Composition Environment 7.1 including enhancement package 1.

1.1 Define System Properties
J2EE System Properties

The following are the default values:
NOTE

These J2EE system properties can also be defined automatically using a dbimport script. For more information, see Define J2EE System Properties in the installation guide for SAP Sourcing on SAP Service Marketplace at http://service.sap.com/eso SAP Sourcing .
Initial JNDI Context system, j2ee.jndi.java.naming.factory.initial=com.sap.engine.services.jndi.InitialContextFact oryImpl JNDI Naming Factory system, j2ee.jndi.java.naming.factory.url.pkgs=com.sap.tm.jndi.providers JNDI Provider system, j2ee.jndi.java.naming.provider.url=localhost:50004 NOTE

If you are deploying the Symantec Scan Engine to scan uploaded attachments for viruses, SAP Sourcing requires use of the native protocol, and certain properties should be set up. Log in as the System user and modify the properties listed in the table below as specified:
Property
system, system.avscanner.hos tname system, system.avscanner.por t

Instructions

Set to the host where the Symantec Scan Engine is installed.

Set to the port where you have the service listening (default is 7777).

2012-05-12

PUBLIC

5/36

1 1.1

Basic Settings for SAP Sourcing and CLM Define System Properties Property
system, system.avscanner.pol icy system, system.avscanner.ena bled

Instructions

Can be set to either SCAN_ONLY or SCAN_REPAIR.

Should be set to True.

NOTE

For multiple landscape use, all the configurations must have the same name. If not, migration will be affected.
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 systemlevel 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:
Pattern
* *.name.com

Description

Any referrer is trusted. Trusted referrer domains must end with the specified string.
EXAMPLE
*.mydomain.com

name.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. Trusted referrer domains must match the specified string exactly.

6/36

PUBLIC

2012-05-12

1 1.1 Pattern

Basic Settings for SAP Sourcing and CLM Define System Properties Description 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.
Property
system, system.cookies.enable_http_only

Description

system, system.cookies.enable_secured

system, system.security.directory.display_entry_does_not_exist_error

system, system.security.domain.validate_redirect_url

system, system.security.separate_pswd_and_name

system, system.allow.embed.in.iframe

When True, the browser denies Javascript access to cookies. When True, cookies can only be passed using the secure https protocol. When True, error messages for failed login attempts distinguish between invalid credentials (password) and nonexistent directory entry (username). When False, both failures result in the same error message. When True, this property forces the system to work only under a single domain. This can adversely affect performance. When True, creation or modification of a user account results in two separate email notifications: one with a username, one with a password. When True, SAP Sourcing can be embedded in an iframe.

2012-05-12

PUBLIC

7/36

1 1.2

Basic Settings for SAP Sourcing and CLM Context, Cluster, and Directory Configuration

1.2 Context, Cluster, and Directory Configuration
To establish a working environment, you must configure the following components: ■ Context ■ Cluster ■ Directory configurations (internal and external) All of these configurations are accessed using the System login. 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 X-Original-HTTPS to the request with a value of on. Sticky sessions must also be enabled by cookie or another method. For more information about Cluster Configuration, see the SAP Sourcing help, at help.sap.com Setup System Setup Configuration Cluster Configuration .

1.2.1 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 10].
Procedure

1. 2. 3.

Login as the System Manager and choose Cluster Templates Choose New Create a new cluster template with the following (example) parameters: ■ External ID: cluster.example ■ Display Name: Cluster Example ■ Host Name: example.sap.com

1.2.2 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 10]

8/36

PUBLIC

2012-05-12

1 1.2

Basic Settings for SAP Sourcing and CLM Context, Cluster, and Directory Configuration

Procedure

1. 2. 3.

Login as the System Manager and choose Directory Templates. Choose New Create a new directory template with the following (example) parameters: ■ External ID: directory.internal.example ■ Display Name: Internal Directory Example ■ Usage: Active Internal ■ Authentication Support: true ■ Case Sensitive Username: false ■ Driver: NetWeaver UME ■ Properties ● Property Name: bypass_error_block ● Property Value: true ■ Attributes Mapping ● Local ID: NAME ● Mapped ID: uniquename ● Edit Mode: Pull

1.2.3 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 10] .
Procedure

1. 2. 3.

Login as the System Manager and choose Directory Templates. Choose New. Create a new directory template with the following (example) parameters: ■ External ID: directory.external.example ■ Display Name: External Directory Example ■ Usage: Active External ■ Authentication Support: true ■ Case Sensitive Username: false ■ Driver: NetWeaver UME ■ Properties ● Property Name: bypass_error_block ● Property Value: true ■ Attributes Mapping

2012-05-12

PUBLIC

9/36

1 1.2

Basic Settings for SAP Sourcing and CLM Context, Cluster, and Directory Configuration

● Local ID: NAME ● Mapped ID: uniquename ● Edit Mode: Pull

1.2.4 Managing the SSL Certificate
In order to write to an Active Directory, Microsoft requires that communication to the LDAP is conducted over SSL.
Getting SSL Working

In order to enable SSL communication, you need to do the following: ■ Change the communication port in the Directory Configuration from 389 (the default setting) to 636. ■ Select the SSL checkbox in the Directory Configuration. ■ Verify that the Certificate Authority (CA) that issued the server certificate is in the Java Keystore. ■ When an intermediate CA is used to generate server certificates, the intermediate CA certificate will need to be imported manually. If any 'Issuer' CA certificates required to complete the server certificate chain are missing from the Java security repository on the application server, install them manually into that repository. Use the following command to install the certificate:
<JAVA_HOME>\bin\keytool -import -trustcacerts -keystore cacerts -file <Location_of_exported_Certificate xxx.crt> -alias <some_alias> <JAVA_HOME> is the location of the SAPJVM. For example /sapmnt/<SID>/exe/jvm/linuxx86_64/ sapjvm_5.1.064/sapjvm_5.

For this <JAVA_HOME>, the cacerts file would be located at /sapmnt/<SID>/exe/jvm/linuxx86_64/ sapjvm_5.1.064/sapjvm_5/jre/lib/security/. After performing these tasks, restart NetWeaver and test by creating a new user in SAP Sourcing.

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

10/36

PUBLIC

2012-05-12

1 1.3

Basic Settings for SAP Sourcing and CLM Master Data

Procedure

1. 2. 3. ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Login as the System Manager and choose Tenant Configuration # # Choose New Create a new tenant configuration with the following (example) parameters:

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 8] step ■ Internal Directory Configuration [page 8] step ■ External Directory Configuration [page 9] step

1.3 Master Data
Gathering Critical Information

For each deployment, gather critical information, including (but not limited to) the following: ■ Buy-side organizational data: Locations, Companies, Business Units, Groups, and Users ■ Sell-side 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.

2012-05-12

PUBLIC

11/36

1 1.3

Basic Settings for SAP Sourcing and CLM Master Data

1.3.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.
Contents Data Classification Description

Numbering table definitions for enterprise- Configurable level objects

Default list of extendible enterprise-level objects Default list of objects that can used referenced in an extension Value List Types Value List Values Units of Measure Currencies Currency Conversions Document Link Definitions Scheduled Task Types Scheduled Tasks Metrics Contract Terms Contract Types Project Types RFx Types Auction Types

Configurable Configurable

Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable

Defines the format of IDs. For example, an RFP might follow the format: RFP-nnnn, where nnnn increments for each new rfp created. Lists those enterprise-level objects which can be extended One type of extension allows a reference to another type of object. This list identifies the allowed kinds of references. Default value list types Default value list values, such as countries, time zones, and so on Standard units of measure used throughout the system A list of all currencies used by your organization Default values for any currency conversion rates Lists the allowable kinds of document links Used to define categories of scheduled tasks Lists scheduled or background tasks Used to define metrics for scorecards Used to define terms on contracts Types define what set of contract features are available Types define what set of Project features are available Types define what set of RFx features are available Types define what set of Auction features are available

12/36

PUBLIC

2012-05-12

1 1.3

Basic Settings for SAP Sourcing and CLM Master Data Data Classification Description

Contents

DA Types Security Profiles Rights on security profiles Time Periods Reporting Calendars Collaborator Roles

Configurable Configurable Configurable Configurable Configurable Configurable

Document Security Templates Shared Discussions

Configurable Configurable

Workbench Channels Workbench IFrames Workbench Channel Configurations Workbench Pages Workbench Page Configurations Configuration Properties Enterprise Extensions Directory Configurations Geographies Locations Payment Terms External Categories

Configurable Configurable Configurable Configurable Configurable Configurable Custom Custom Custom Custom Custom Custom

Internal Categories Vendors Vendor Extensions in List Form Companies

Custom Custom Custom Custom

Registration Categories

Custom

Types define what set of Demand features are available Identifies the security profiles installed with the system Defines the rights for each security profile Defines information about quarters, years, and so on Used for managing how data is reported with relation to the calendar Defines the role (rights and responsibilities) of a person/group on a specific document instance Sets up the default collaborators and security when new documents are created A list of discussion forums available as a channel and not relating to a specific document Channels available on a user's desktop Data to create iFrames Channel configuration parameters Pre-defined desktop pages Channel content and placement settings for predefined pages Various deployment settings, including mail Actual extensions on enterprise-level objects Used for the LDAP directory configuration Used to represent the Geographic regions Locations of plants, companies, and other organizational elements Terms of payment between the buyer and vendor Typically this data set consists of industry standard category codes, such as UN-SPSC or SIC codes, if used by your organization. All internal purchasing categories used by the buyer Used in all components for various purchasing actions Actual extensions on enterprise-level objects Used by all components of the system for purchasing actions such as Auctions and RFPs Defines mapping from arbitrary category names to actual internal or external

2012-05-12

PUBLIC

13/36

1 1.3

Basic Settings for SAP Sourcing and CLM Master Data Data Classification Description

Contents

Organizational Units

Custom

Groups Contacts Accounts Terms Templates

Custom Custom Custom Custom

categories. Used during vendor selfregistration. Further definition of the organizational hierarchy. Use to define departments, business units, and so on. Arbitrary groups of buy-side users Used for all vendors to distinguish the various contacts at each vendor Handles all user accounts for the system Standard terms and conditions phrases to which a vendor must agree before accessing an event

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.
Contents Data Classification Description

UFNs System Answered Sources

System Configurable

Company Extension Definitions Configurable Document Security Templates Configurable Contract Generation Phases Contract Generation Tags Company extensions masterdata.Activity Cost Centers Cost Center Groups Entities GL Accounts Plants Materials Category Managers
Master Data Security

Configurable Configurable Custom Custom Custom Custom Custom Custom Custom Custom Custom

Metadata for RFx utility functions Defines the available sources of system answered questions List of company-scoped objects which have extensions Sets up the default collaborators and security when new documents are created Used to define Phases for Contract Generation library documents Used to define Tags for Contract Generation List of extensions on individual object types Used for general accounting purposes Used for accounting purposes to assign cost on a center by center basis Used for accounting purposes for purchasing by division Used for general accounting purposes Plants or facilities Standard materials for use in line items Users who are responsible for certain categories

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

14/36

PUBLIC

2012-05-12

1 1.3

Basic Settings for SAP Sourcing and CLM Master Data

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

2.

If Supplier Administrators need to import Supplier records, then that can be enabled. 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.

1.3.2 Create Master Data Manually
Procedure

1. 2.

Log in as the enterprise administrator for enterprise master data. Create objects from within the Setup module. You must log in as a sourcing administrator (a real user) in order to configure company master data. 3. Log in as a sourcing administrator (a real user) to configure company master data. For more information, see SAP Library for SAP Sourcing on SAP Help Portal at http:// help.sap.com SAP Business Suite SAP Sourcing Setup System Setup Master Data .

1.3.3 Import Master Data Using CSV File
You can import master data files with CSV or XLS format in two ways: ■ Use the standard web user interface ■ Use a client application distributed with the system, which allows data to be imported outside of the web environment The following procedure describes how to import using the web-based UI.
Procedure

1. 2. 3. 4. 5. 6. 7.

Open a web browser and access your buy-side logon page. If application users have already been created, log into the enterprise as a user with administrative rights. If users have not been created, use the enterprise administrator built-in account. Choose Setup System Administration Import Export Tools Import Data and then choose OK. Choose Create. The import wizard opens. 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. Choose Upload Import File and select the CSV or Deployment Workgroup file to import. For CSV files, select the object type and choose Next.

2012-05-12

PUBLIC

15/36

1 1.3

Basic Settings for SAP Sourcing and CLM Master Data

8. 9.

Indicate whether you want to wait for the import to finish or perform the import in the background and then choose Next. Choose Finish to view the results.

1.3.4 Workbooks 1.3.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 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.

16/36

PUBLIC

2012-05-12

1 1.3

Basic Settings for SAP Sourcing and CLM Master Data

1.3.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:
System Workbooks

SAP Sourcing

■ Enterprise Deployment Workbook ■ Company Deployment Workbook

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. For details on customizable fields, see Master Data [page 11].
Procedure

1.

In SAP Sourcing, log on as the enterprise user and download the sample enterprise and company workbooks from the SAP Sourcing reference guide (RG).
NOTE

2.

3. 4. 5. 6.

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. 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. Find each sheet, review each sheet and the comments in the sheet, and update the data accordingly. Provide at least one internal category. Find the sheet labeled companies and edit it as necessary. 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

7.

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. Import the enterprise and company workbooks into SAP Sourcing by choosing Setup System Administration Import and Export Tools Import Data and then choose Create.

2012-05-12

PUBLIC

17/36

1 1.4

Basic Settings for SAP Sourcing and CLM Create and Verify Buy-Side User

1.3.4.3 Import Master Data Using Workbooks
Procedure

1. 2.

3.

4. 5. 6. 7.

Open a browser and go to the login page http://yourhost/fsbuyer/portal/login. Log into the new enterprise with the following: ■ For the Username, enter enterprise. ■ For the Password, enter the value you entered when you created the context. Choose Setup, then choose Import Data from the dropdown list under Import and Export Tools, and then choose OK. The Import Data page appears. Choose Create to start a new import job. Choose Upload to the Server and then choose Next. Select the modified workbook and choose Next. Wait for the import to finish and choose Next. Typically, running the enterprise workbook can take several minutes.

1.4 Create and Verify Buy-Side User
Procedure

For the SAP NetWeaver UME driver, users should be created in SAP Sourcing and the SAP NetWeaver UME with the same username. For LDAP drivers, depending on how the LDAP was set up, you must perform one of the following: ■ Create the user in SAP Sourcing and supply the information FROM the LDAP. ■ If you have access, create the account and supply the information TO the LDAP. In either case, an e-mail is generated, giving the user a path to the application and his or her user name. If the account is created, 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 Setup User Account List and create a buy-side user as follows: 1. On the Account Properties tab, enter required information. 2. On the Account Management tab, enter information as follows: ■ 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 3. On the Security tab, enter information as follows: ■ Buyer: Select ■ Buyer Manager: Select

18/36

PUBLIC

2012-05-12

1 1.5

Basic Settings for SAP Sourcing and CLM Create and Verify Sell-Side User

2.

3. 4.

■ 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 Setup System Administration Processed Messages . ■ To check for stuck or failed messages, choose Setup System Administration Queued Messages . To test the new account, log in using the credentials sent in the e-mail. Reset your password and choose OK. If you can successfully log into the new buy-side account, the context cluster and directory are properly configured and the SMTP server is processing e-mail.

1.5 Create and Verify Sell-Side User
Procedure

Create a sell-side user to test the sell-side portal. A sell -side user is a contact on a supplier record. 1. Choose Supplier Management Create Supplier . 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 in using the credentials provided in the test user e-mail and the sell-side URL: http:// [hostname:port]/fsvendor/portal/login. 7. Reset the password as prompted and accept the usage terms.

1.6 Install Company Logo
Procedure
NOTE

We do not recommend installing an image larger than 200 x 29. 1. 2. Access the Login page: http://<yourhost>/fsbuyer/portal/login Log into the new enterprise as follows: 1. For the Username, enter enterprise. 2. For the Password, enter the value you entered when you created the context. 3. Choose Login. Attach the logo as follows:

3.

2012-05-12

PUBLIC

19/36

1 1.7

Basic Settings for SAP Sourcing and CLM Specify Internal Address of SAP Sourcing Server

4.

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. 1. Choose Setup Configuration System Properties . 2. If there is an entry in the property list for buylogoimage, select it and choose Edit. Otherwise, choose Create. 3. Set the Property Set to userinterface. 4. Set the Property Value to custom/companylogo/.

Resize Company Logo

If you have uploaded a company logo in your source release, you must resize the image to 200x29. 1. Log on to SAP Sourcing as a 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.

1.7 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 Sourcing’s notification ports, this will result in failure to deliver notifications for some events. To avoid this, do the following: 1. Log in as a system administrator. 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.

20/36

PUBLIC

2012-05-12

1 1.8

Basic Settings for SAP Sourcing and CLM Update Master Time Zone

1.8 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. Log into SAP Sourcing as a system administrator. 2. Choose Setup Configuration System Properties . 3. Check to confirm that the alternate values of the valueless value(s) is filled in. Refer to that object as the source of the correct time zone entry.
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 to SAP Sourcing 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”.

1.9 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 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. 4. Log on as the enterprise user and choose Setup System Administration Import and Export Tools Import Data . 5. Use the import tool to import the licenses you received from Support, as follows: 1. 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 Setup System Administration System Management System Information . 7. Choose the Components tab and verify that the appropriate licenses are checked under SRM Module Licenses.

2012-05-12

PUBLIC

21/36

1 1.10

Basic Settings for SAP Sourcing and CLM Change Session Timeout

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

1.10 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 on SAP Service Marketplace at http://service.sap.com/ eso SAP Sourcing .
NOTE

Both internal property in SAP Sourcing and configuration tool in NetWeaver should be set to the same value.

1.11 Enable Contract Authoring
Contracts, amendments, and clauses use the Word service. This service must be referenced. For more information, see Create OfficeAutomationUser Account in the installation guide for SAP Sourcing on SAP Service Marketplace at http://service.sap.com/eso SAP Sourcing .
Procedure

Configure a path to the Word service in SAP Sourcing, as follows: 1. Choose Setup System Properties.

22/36

PUBLIC

2012-05-12

1 1.12

Basic Settings for SAP Sourcing and CLM Configure Workbench

2. 3.

From the Name dropdown list, choose contractgen.serviceurl. Set the value to <protocol>://<hostname>/<virtual directory>/wordservice.asmx.

1.12 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 Workbench Page All Workbench Pages . Edit the Contract Management page and add collaborators.

1.13 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 buyer 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. 2.

Choose Setup System Properties . Change the value of system.brand_name to (for example) SAP CLM.
NOTE

Themes

The following two steps require editing of themes, see SAP Library for SAP Sourcing on SAP Help Portal at http://help.sap.com Setup Themes. .

2012-05-12

PUBLIC

23/36

1 1.13

Basic Settings for SAP Sourcing and CLM Configure Branding

1. 2. 3. 4.

Open the current enterprise’s theme Branding area and choose Buyer Login Banner link, then Image link. Delete the original path in Image Path field, and paste /images/logos/logo_sapXCLM.gif. Choose Delete on Background Image field. Choose the Supplier Login Banner link, then Image link. Delete the original path in Image Path field, and paste /images/logos/logo_sapXCLMBusinessPartner.gif. Choose Delete on Background Image field.

More Information

For more information about branding your login page, splash screen, and portal page, see SAP Library for SAP Sourcing on SAP Help Portal at http://help.sap.com Setup Themes .

24/36

PUBLIC

2012-05-12

2 2.1

Basic Settings for Search in SAP Sourcing and CLM Search Via KM and Trex

2 Basic Settings for Search in SAP Sourcing and CLM

2.1 Search Via KM and Trex 2.1.1 Configuration of Knowledge Management Content Search and TREX
NOTE

Instead of KM content search, we recommend using global search to carry out free-text content search on documents and attachments. This simplifies your landscape because global search does not require a TREX server. For information about global search, see SAP Library for SAP Sourcing on SAP Help Portal at http://help.sap.com SAP Business Suite SAP Sourcing Getting Started General Functions Global Search . If your database is Oracle 10.2.0.4, note that global search supports Microsoft Office Word 2007 documents only on Oracle 11.2.0.1 and higher. Knowledge Management (KM) content search and Search and Classification (TREX) are optional features that enable you to carry out free-text content search on contract documents, attachments, and clauses. The content search capability is provided by the KM server and TREX server. The TREX server indexes the documents and provides the functionality to perform content search on the indexed documents. The KM server is used as a channel to index the documents in order to use the TREX client API that is available on the KM server. Each installation of the KM and TREX server can serve multiple SAP Sourcing application servers.
Prerequisites

KM content search and TREX are installed. For more information, see Install Knowledge Management Content Search and TREX in the installation guide for SAP Sourcing on SAP Service Marketplace at http://service.sap.com/eso SAP Sourcing .

2.1.1.1 Configure TREX Server in KM Server
Procedure

To configure the TREX server in the KM server, see the following links: ■ Configuration of the TREX Services in the SAP J2EE Engine: http://help.sap.com/
erp2005_ehp_03/helpdata/EN/26/eeb73975a4e94b85c70de1c020b2f1/frameset.htm

2012-05-12

PUBLIC

25/36

2 2.1

Basic Settings for Search in SAP Sourcing and CLM Search Via KM and Trex

■ Specifying the Address of the TREX Name Server: http://help.sap.com/erp2005_ehp_03/ helpdata/EN/c7/e0d13f7fb44c21e10000000a1550b0/content.htm. In addition, you must perform the following additional configuration steps: 1. Open the TREXqueueServer.ini file in the TREX server and do the following: 1. In the preprocessor section, check the pool size and ensure that it is not greater than 1. 2. After changing the configuration, restart the TREX server. 2. Increase the value of the Timeout parameter for the Crawler, as follows: 1. Navigate to System Administration System Configuration Knowledge Management Content Management Global Services Crawlers Parameters Index Management Crawler standard Document Retrieval Timeout . 2. Set the value to 200.

2.1.1.2 Deploy KM SCA File to KM Server Using SDM
In this step, you: ■ Deploy the custom repository manager portal application to the KM server. This repository manager makes the SAP Sourcing documents accessible to the KM. The name of the component is srm/xclm/kmc/rms. ■ Deploy and configure the SAP Sourcing data provider proxy. The name of the component is srm/ xclm/kmc/services/wsproxy.
Procedure

To deploy the KM SCA file (SRMKMXCLMJAVA00_0.sca), see the following: ■ Deployment: http://help.sap.com/erp2005_ehp_03/helpdata/EN/92/ fb673ba8ecf22fe10000000a11402f/content.htm. ■ Deploying Components: http://help.sap.com/erp2005_ehp_03/helpdata/EN/ 43/2ae0ec69742182e10000000a114cbd/content.htm.

2.1.2 Authentication Between KM Server and SAP Sourcing Server 2.1.2.1 Overview of Authentication Between KM and TREX Server and SAP Sourcing Server
You can configure authentication between the KM server and the SAP Sourcing server using basic authentication.

2.1.2.2 Configure Basic Authentication for KM
There are two steps to configure authentication between the KM server and the SAP Sourcing server:

26/36

PUBLIC

2012-05-12

2 2.1

Basic Settings for Search in SAP Sourcing and CLM Search Via KM and Trex

1. 2.

Configure the Repository Manager Configure Repository Managers for multiple SAP Sourcing sections

Procedure

Configure the Repository Manager To configure the SAP Sourcing repository manager, navigate to the following location in the Enterprise Portal: System Administration System Configuration Knowledge Management Content Management Repository Managers SAP Sourcing Repository Manager . By default, a single instance of a repository manager is available with the deployment. Configure this default instance for the first SAP Sourcing server, as follows: 1. Enter the SAP Sourcing server URL as: http://<host name>:<port number>/<context>/
services/KMDocumentHierarchyHomeService

2.

Create an SAP Sourcing user with KM Administrator security profile. The user should be created only when using Basic Authentication. For information about creating a new user, see SAP Library for SAP Sourcing on SAP Help Portal at http://help.sap.com SAP Business Suite SAP Sourcing . 3. For Basic Authentication, enter the User Name and Password of the user you just created. 4. Leave the remaining fields unedited. Configure Repository Managers for Multiple SAP Sourcing Servers
NOTE

Perform this step only when the KM server is shared by multiple SAP Sourcing applications. In this case, the Repository Manager name must be unique. To connect multiple SAP Sourcing servers to the same KM server, create corresponding instances of Repository Manager. To create additional instances of the repository manager, do the following: 1. Click the Duplicate button under the SAP Sourcing repository manager list. 2. Follow the above steps for Configure the Repository Manager.

2.1.2.3 Set Up KM HTTP Destination
KM accesses the SAP Sourcing system to download document content. This connection should be configured by creating the HTTP destination on the KM side.
Procedure

1. 2. 3.

Open the Visual Administrator of the SAP NetWeaver Java Application Server on which the Java application is running. Under Cluster, choose <your_server> Services Destinations . Create an HTTP destination called DOWNLOAD_ESRC_DOC_CONTENT.

2012-05-12

PUBLIC

27/36

2 2.1

Basic Settings for Search in SAP Sourcing and CLM Search Via KM and Trex

4. 5. 6.

To activate basic authentication, select NONE as the authentication method and leave the Login Password and URL fields blank. Save your entries. If you changed an already operational destination, restart the Java application server.

2.1.3 Set Up KM System Properties
These configuration properties can be set at the system or the enterprise level. When set at the system level, the property applies to the complete system. When set at the enterprise level, the property applies to the specific enterprise. The enterprise-level settings will overwrite the system-level settings.
Procedure

1. 2. 3.

4.

Log on to SAP Sourcing using the relevant system or enterprise user name and password. Choose Setup. Do one of the following: ■ For a system user, choose System System Properties . ■ For an enterprise user, choose System Setup Configuration System Properties . Edit the following property to change the value from FALSE to TRUE.
Set Name/Property Value Description

contractgen

contractgen.km_search.enabled

TRUE

Enable KM search

5.

If the default number of search results obtained from KM needs to be changed, edit the following system property. The default value for the property is 100.
Set Name/Property Value Description

contractgen contractgen.km_search_webservice.max_results 1000

Maximum number of search results
Description

6.

Create the following system properties:
Set Name/Property Value

system

system.webservices.enabled

TRUE

contractgen contractgen.km_search_webservice. username

<User name for KM server>

Enables Web Services framework. If enabled, KM and other WS consumers can call SAP Sourcing/ SAP CLM Web Services methods KM server user name

28/36

PUBLIC

2012-05-12

2 2.1

Basic Settings for Search in SAP Sourcing and CLM Search Via KM and Trex Set Name/Property Value Description

contractgen contractgen.km_search_webservice. password <Password for KM server> KM server password contractgen contractgen.km_search_webservice.url <protocol>:// This property <hostname>:/ sets a ESourcingKmcServicesWS/ reference to ESourcingKm the KM web cServicesConfig? service style=document contractgen contractgen.km_search.not_supported_types List of file extensions used A commathat are not supported by separated list of file extensions unsupported by TREX used in SAP Sourcing/ SAP CLM for generating/ uploading contract documents / attachments/ clauses. Use file extensions only, without periods (for example, TIF, TIFF, and so on.) For a complete list of supported file formats, see File Formats supported by TREX. Customers should determine whether TREX supports indexing for the formats used for their contract documents and

2012-05-12

PUBLIC

29/36

2 2.2

Basic Settings for Search in SAP Sourcing and CLM Set Up Indexing Set Name/Property Value Description

contractgen contractgen.km_search.repository_prefix

TREX <file ext1, file ext2>. attachments. For example, tif, gif, jpg. The system property should be set accordingly. <KM Repository Name> The repository manager in the KM server to which the current SAP Sourcing instance is pointing

2.2 Set Up Indexing
The TREX index server indexes and classifies documents and answers search queries. An index is a TREX data structure that allows you to find document text efficiently. For additional details, see the following link:
Procedure

1.

2.

Create three indexes for the root context as follows: ■ Master Agreement (Contract Documents and Attachments) ■ Subageement (Contract Documents and Attachments) ■ Clause Documents Assign the data source to the index. Each index object should be assigned to the corresponding SAP Sourcing repository manager document folders as a data source. root EsourcingEnterprise Context ID Enterprise Sub Context ID Class ID
Company Class ID Value Indices
CONTEXT_MA_INDEX CONTEXT_SA_INDEX CONTEXT_CLAUSES_INDEX

Master Agreement Subagreement Clauses
NOTE

1004 1003 1818

3. 4.

When creating an index for the root context, the Enterprise Context ID and Enterprise Subcontext ID are the same. If you have multiple contexts, repeat steps 1 and 2 for each context. Schedule the time when the indexes are to be executed. Schedule the time when the indexing process should start on the TREX server. Each index should be assigned a different time slot to reduce the load on the TREX server.

30/36

PUBLIC

2012-05-12

2 2.3

Basic Settings for Search in SAP Sourcing and CLM Troubleshoot KM Installation RECOMMENDATION

We recommend that you schedule the indexing at around midnight when usage of the application is minimal. The suggested value for the time interval for each index is 15 minutes.
NOTE

The content search is available only for documents that are already indexed. Users cannot search on document changes until those documents are indexed. If a user searches for a word that has recently been added to the document, the search results may not include the modified document. Indexing time is dependent on the web service update time and the indexing schedule routine. The TREX queue parameters can be configured as in the following help link to change the response time for indexing the documents.
Monitoring the Indexing Status of Documents

At any point, you can monitor the indexing status the SAP Sourcing documents using the Indexing Monitor in the Enterprise Portal. To do this, navigate to the following location in the Enterprise Portal: System Administration System Configuration Knowledge Management Index Administration Indexing Monitor . This page displays the status of each created index, along with the numbers of documents that have been indexed or are in process, and those for which indexing failed.
More Information

■ Creating an Index and Assigning Data Sources: http://help.sap.com Knowledge Management Administration Guide System Administration System Configuration Index Administration iView Creating an Index and Assigning Data Sources. ■ Optimizing Performance: http://help.sap.com Knowledge Management Technical Operations in Detail TREX Admin Tools TREX Admin Tool (Stand-Alone) Queue Area Queue Parameters Start Condition Optimizing Performance ■ Start Condition: http://help.sap.com Knowledge Management Technical Operations in Detail TREX Admin Tools TREX Admin Tool (Stand-Alone) Queue Area Queue Parameters Start Condition .

2.3 Troubleshoot KM Installation
This topic includes the following areas: ■ Troubleshooting Indexing ■ Adding KM Workbench Channels
Procedure
Troubleshooting Indexing

If indexing fails for some documents, check the KM and TREX server configuration, as follows: 1. Open the TREXqueueServer.ini file in the TREX server.

2012-05-12

PUBLIC

31/36

2 2.3

Basic Settings for Search in SAP Sourcing and CLM Troubleshoot KM Installation

2. 3. 4.

In the preprocessor section, check the pool size and ensure that it is not greater than 1. After changing the configuration, restart the TREX server. Trigger reindexing for the failed documents. Increase the value of the Timeout parameter for the Crawler. This parameter can be changed in System Administration System Configuration Knowledge Management Content Management Global Services Crawlers Parameters Index Management Crawler Standard Document Retrieval Timeout . Set the value to 200. After changing the value, trigger reindexing for the failed documents.

Adding KM Workbench Channels

If the KM Search channels (Contract Content Search and Clause Content Search) are not visible on the Workbench, add them. For information about adding workbench channels, see SAP Library for SAP Sourcing on SAP Help Portal at http://help.sap.com.

32/36

PUBLIC

2012-05-12

Typographic Conventions

Example
<Example>

Description

Example Example Example
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>”. Arrows separating the parts of a navigation path, for example, menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web 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. ■ 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 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 Keys on the keyboard

http://www.sap.com /example

123456 Example

Example

EXAMPLE

EXAMPLE

2012-05-12

PUBLIC

33/36

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

© Copyright 2012 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/ OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

34/36

PUBLIC

2012-05-12

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
Disclaimer

Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

2012-05-12

PUBLIC

35/36

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

© Copyright 2012 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.