supplier evoluation

SAP Enhancement Package 2 for SAP SRM 7.0: Supplier EvaluationBased on SAP Solution Manager Content

Target Audience ■ System Administrators ■ Consultants

PUBLICDocument version: 1.0 – 2011-11-08

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of SAP Solution

Manager content. For more information on the SAP Solution Manager content, see SAP Note

1461039.

The following table provides an overview of the most important document changes:

Version Date Description

1.0 2011-11-08 Initial Version

2/64 PUBLIC 2011-11-08

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1461039&_NLANG=en&_NVERS=0

Table of Contents

Chapter 1 Important Information About This Document . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2 Basic Settings for Supplier Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1 Basic Settings for Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.2 Supplier Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.3 SAP Notes and BAdIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.3.1 Business Add-In – Flexible Adaptation of Specific Requirements . . . . . . . . . . . . 8

2.3.2 More Information About SAP Notes and BAdIs . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.4 Preparation of Evaluation in SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.4.1 Configuration in SAP Supplier Relationship Management (SAP

SRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.4.2 Customizing for Ad-Hoc Surveys (Supplier Survey Cockpit) . . . . . . . . . . . . . . 10

2.4.3 Sending and Receiving Questionnaires via E-Mail . . . . . . . . . . . . . . . . . . . . . . 10

2.4.4 Creating New Parameters for a Questionnaire . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.5 Preparation of Evaluation in SAP NetWeaver BI . . . . . . . . . . . . . . . . . . . . . . . . 12

2.5.1 Preparation of SAP NetWeaver BI for Supplier Evaluation . . . . . . . . . . . . . . . . 12

2.5.2 Adding Parameters to a Questionnaire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.5.3 Loading Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.5.4 Defining Evaluation Roles and Attaching them to User IDs . . . . . . . . . . . . . . . 18

2.5.5 Setting Up Supplier Evaluation for Non-Standard DataStore

Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.5.6 Loading Transaction Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.5.7 More Information About the Preparation of Evaluation in SAP NetWeaver

BI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.6 Preparation of Evaluation in SAP ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.6.1 Customizing in ERP Vendor Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.7 Preparation of SAP NetWeaver BI for Analysis . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.7.1 Maintaining the ERP Vendor Evaluation Enhancement . . . . . . . . . . . . . . . . . 22

2.7.2 Maintaining Common Interface for External Evaluation Systems . . . . . . . . . . 23

2.7.3 Configuration of Supplier Evaluation for Analysis . . . . . . . . . . . . . . . . . . . . . . 25

2.7.4 Loading Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2011-11-08 PUBLIC 3/64

2.7.5 Load of Transaction Data from SAP SRM, SAP ERP, and SAP NetWeaver

BI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.7.6 Update of Supplier Evaluation InfoCube . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.7.7 Settings in Content Queries in SAP NetWeaver BI . . . . . . . . . . . . . . . . . . . . . . 30

2.7.8 Change of Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 3 Supplier Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.1 Evaluating and Monitoring of Supplier Performance . . . . . . . . . . . . . . . . . . . . 37

3.1.1 Supplier Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.1.2 More Information About Evaluating and Monitoring of Supplier

Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.1.3 Defining Questionnaires with Web Survey Cockpit . . . . . . . . . . . . . . . . . . . . . 39

3.1.4 Content of SAP SRM Questionnaires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.1.5 Definition of Parameters and Valuation Levels . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.1.6 Defining Questionnaires with Web Survey Cockpit in SAP NetWeaver

BI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.1.7 Defining Questionnaire Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.1.8 Execution of Evaluations in SAP NetWeaver BI . . . . . . . . . . . . . . . . . . . . . . . . 53

3.1.9 Definition of Groupings in SAP NetWeaver BI . . . . . . . . . . . . . . . . . . . . . . . . . 56

3.1.10 Definition of Weightings in SAP NetWeaver BI . . . . . . . . . . . . . . . . . . . . . . . . . 58

3.1.11 Supplier Evaluation: Available Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

4/64 PUBLIC 2011-11-08

1 Important Information About This Document

The configuration documentation for SAP Supplier Relationship Management (SAP SRM) is delivered

with the SAP Solution Manager content. To implement and configure SAP SRM, you must use SAP

Solution Manager, which contains the complete configuration documentation including links to

Customizing, SAP Notes, and SAP ERP documentation.

This guide contains only the SAP SRM configuration documentation and references to other

documentation. It provides you with a quick overview of the required SAP SRM configuration settings.

CAUTION

This guide is a supplement to the SAP Solution Manager content and does not replace it. The

complete configuration content and tool support is only available in SAP Solution Manager.

For more information on the SAP Solution Manager content, see SAP Note 1461039 and the SAP SRM

master guide at http://service.sap.com/instguides under Installation & Upgrade Guides SAP Business

Suite Applications SAP SRM SAP SRM Server 7.01 .

Business Functions

SAP enhancement package 1 for SAP Supplier Relationship Management 7.0 (SAP SRM 7.0) includes

the following business functions:

■ SRM, Strategic Sourcing Innovations

■ SRM, Catalog Innovations

■ SRM, Approval Process

■ SRM, Continuous Innovations

■ SRM, Implementation Simplification

■ SRM, Service Procurement Innovations

■ SRM, PI-Independent Enterprise Services

■ SRM, Supplier Collaboration

■ SRM, Self-Service Procurement

■ SRM, Analytics

For more information about these business functions, see SAP Help Portal at http://help.sap.com

SAP Supplier Relationship Management Business Functions and Customizing Switches .

1 Important Information About This Document

2011-11-08 PUBLIC 5/64


http://service.sap.com/instguides

http://help.sap.com

This page is left blank for documents that are printed on both sides.

2 Basic Settings for Supplier Evaluation

2.1 Basic Settings for Analytics

Ensure that you have completed the configuration steps described in SAP Solution Manager under

<project name> Configuration SAP SRM <release> Basic Settings for SAP SRM Basic Settings for

Analytics before configuring the Spend Analysis or Supplier Evaluation business scenarios.

2.2 Supplier Evaluation

In recent years, the importance of a generic evaluation tool within collaborative scenarios has increased

as a result of the need for customers to reduce procurement costs, enhance and optimize collaboration,

and globalize procurement activities. This is possible with Supplier Evaluation, which can help you,

for example, to optimize your supply base and improve the relationships with your suppliers.

Process

1. Creating Questionnaires

The Supplier Evaluation process starts with creating questionnaires. For this, a tool called the Web

Survey Cockpit, which allows the customer to define and maintain Web-enabled questionnaires, is

available in the application basis. In the Web Survey Cockpit, users can select the criteria they want to

evaluate (for example, delivery reliability and quality). They can define different types of questions (for

example, single choice, multiple choice, or free-text answers). They can also determine when the

evaluation is to occur.

The Web Survey tool can be accessed from both SAP SRM and SAP NetWeaver Business Intelligence

(SAP NetWeaver BI). The questionnaire data, as well as the responses, are updated in the delta structures

and extracted into SAP NetWeaver BI.

SAP supports two main methodologies for Supplier Evaluation:

■ Event-driven evaluation, triggered from confirmation, invoice, and advanced supplier list

■ Ad-hoc surveys using the Supplier Survey Cockpit

2. Event-Driven Evaluation

The questionnaires are included in the SAP SRM processes, and can be filled out when a document

(confirmation, invoice) is processed. For this purpose, a new browser window opens up.

3. Ad-Hoc Surveys Using the Supplier Survey Cockpit

Supplier Survey Cockpit is a new function in SRM 2007 SP03.The user can create ad-hoc surveys by

using the Supplier Survey Cockpit. Suppliers and questionnaires are assigned to a survey, which is


2.1 Basic Settings for Analytics

2011-11-08 PUBLIC 7/64

distributed via e-mail to selected participants. The Supplier Survey Cockpit is available in SAP SRM

only.

NOTE

You can also perform ad-hoc evaluation using the Web Survey tool through SAP NetWeaver BI.

Here, you can rate confirmations and invoices, and the overall performance of your suppliers on

product or product category level. The benefit is that purchasing documents from multiple

systems can be accessed and rated. This rating is, however, done offline and requires the extraction

of data from the source systems to SAP NetWeaver BI. The evaluation is done using reports

specifically prepared for supplier evaluation

4. Grouping and Weighting

In SAP NetWeaver BI, it is possible to assign the questions to different groups, allowing the user to

analyze different performance areas such as delivery, and quality, for example. The groups can also be

assigned a weight, dependent on their importance.

5. Consolidating and Analyzing Data

When the data has been extracted from SAP NetWeaver BI delta structures into SAP NetWeaver BI, and

updated with grouping and weighting, this information is available for analysis in SAP NetWeaver BI.

The survey data from the Supplier Survey Cockpit on the one hand and from the event-driven surveys

on the other hand are extracted to different DataStore Objects and InfoCubes.

Many reports are available directly from the SAP SRM application, and the user does not need to log

on to SAP NetWeaver BI (though a user for the SAP NetWeaver BI system is required). Supplier

performance results can be accessed also from various processes, for example, a user can view evaluation

scores when determining which bidders to invite for an RFx. The reports available depend on the role

the user has in the SAP SRM context.

2.3 SAP Notes and BAdIs

2.3.1 Business Add-In – Flexible Adaptation of Specific Requirements

The Business Add-In (BAdI) BBP_VE_QSTN_DET_BADI allows you to modify the standard supplier

evaluation to meet your specific requirements. You can use the following methods to do so:

■ DETERMINE_QSTN

If you implement this method, the system overrides the result of the standard questionnaire finding

■ CHECK_USER_ON_CHANGE

If you implement this method, you can activate or deactivate the user check when you change

questionnaires.

■ CHECK_SEND_MAIL_ON_ABORT


2.3 SAP Notes and BAdIs

8/64 PUBLIC 2011-11-08

If you implement this method, you can activate or deactivate the e-mail notification function for

users in cases when the questionnaire response is terminated.

For more information, see Customizing for Supplier Relationship Management under SRM Server Business

Add-Ins Define Questionnaire for Supplier Evaluation in SRM .

2.3.2 More Information About SAP Notes and BAdIs

The following SAP Note applies:

■ 774898

2.4 Preparation of Evaluation in SAP SRM

2.4.1 Configuration in SAP Supplier Relationship Management (SAP SRM)

Procedure

The evaluation of suppliers for invoice, confirmation, and advanced supplier list in SAP SRM can

occur in the following ways:

■ Automatically when a business transaction is saved

■ On an individual basis for selected business transactions

■ On the basis of previously defined stochastic probability

You can define when the evaluation is to occur and under which circumstances in Customizing for

SAP SRM under Integration with Other SAP Components Data Transfer to the SAP NetWeaver Business Intelligence

Settings for Application-Specific DataSources (SRM) Define Events for Supplier Evaluation in SRM.

For more information, see:

■ Definition of Parameters and Valuation Levels [page 44]

■ Business Add-In - Flexible Adaptation of Specific Requirements [page 8]

■ Sending and Receiving Questionnaires via E-Mail [page 10]

The evaluation of suppliers using ad-hoc surveys is executed using the Supplier Survey Cockpit. The

following Customizing is necessary

■ Evaluation Category

■ Evaluation Area

■ Number ranges for Survey - a unique id that is automatically generated by the system

■ Number ranges for Survey Package - a unique id that is automatically generated by the system

For more information, see:

■ Customizing for ad-hoc surveys (the Suppler Survey Cockpit) [page 10]

■ Sending and Receiving Questionnaires via E-Mail [page 10]



2011-11-08 PUBLIC 9/64

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=774898%20&_NLANG=en&_NVERS=0

2.4.2 Customizing for Ad-Hoc Surveys (Supplier Survey Cockpit)

Procedure

Number Range of Survey ID

Every Survey is assigned a unique ID number. The ID number is automatically generated by the system.

The number range needs to be configured.

In Customizing for SAP Supplier Relationship Management, define the number range by choosing

SRM Server Cross-Application Basic Settings Number Ranges SRM Server Number Ranges Define Number

Ranges for Survey .

Number Range of Survey Package ID

All Surveys are assigned to a Survey Package. The Survey Package is a mandatory field. Every Survey

Package is assigned a unique ID number. The ID number is automatically generated by the system. The

number range needs to be configured.

In Customizing for SAP Supplier Relationship Management, define the number range by choosing

SRM Server Cross-Application Basic Settings Number Ranges SRM Server Number Ranges Define Number

Ranges for Survey Package .

Numeric and alphanumeric number ranges are possible. You have to configure the number range “01”.

Evaluation Area

With evaluation areas, surveys can be classified according to, for example, which part of the organization

is evaluated. Examples of evaluation areas could be “Marketing” , “Production”, and “Finance”. This is

later used for analysis.

In Customizing for SAP Supplier Relationship Management, define the evaluation area by choosing

SRM Server Supplier Evaluation Evaluation Area .

Evaluation Category

Each survey is assigned an evaluation category. This refers to the questionnaire and the target group

(the participants) of the specific survey. Examples of evaluation categories could be “Quality” and

“Delivery”.

In Customizing for SAP Supplier Relationship Management, define the evaluation category by choosing

SRM Server Supplier Evaluation Evaluation Category .

2.4.3 Sending and Receiving Questionnaires via E-Mail

To make use of the e-mail integration offered by Supplier Evaluation in SAP Supplier Relationship

Management (SAP SRM), you have to perform some additional configuration steps. You have to enable

the system to do the following:

■ Send the questionnaires via e-mail to the specified recipient



10/64 PUBLIC 2011-11-08

■ Receive the incoming questionnaires and ensure that they are properly processed

Procedure

1. Create a suitable mail user in transaction SU01

NOTE

Note that this mail user must have:

■ A valid e-mail address

■ User type SERVICE

■ Authorization profile S_A.SCON

For more information, see SAP Note 455140.

2. Set up internet mail gateway

3. Maintain e-mail address for the SAP SRM server

4. Create profile parameters in transaction RZ10

Add corresponding port for receiving inbound e-mail from the SMTP mail gateway after it has

been registered.

5. Maintain mail user in transaction SICF

Add the mail user's ID to node SAPconnect and activate it. Enter 1 | CL_SMTP_EXT_SAPCONNECT

in tab strip Handler List.

6. Define inbound exit rules using transaction SO50

Create an e-mail address under Recipient Address, for example anyname@system and assign

CL_UWS_FORM_RUNTIME_MAIL as the Exit Name to pass the mails to the survey framework.

NOTE

We recommend using mailto:survey@system. This name is used as the return address in the

questionnaire, which means that all mails for recipient “anyname” are sent to the survey

framework.

2.4.4 Creating New Parameters for a Questionnaire

Procedure

You can enhance the list of potential questionnaire parameters (see section Adding Parameters to a

Questionnaire [page 13]) according to your needs. You can add all InfoObjects that are included in the

DataStore objects for transactional document data. To do so, run transaction se11 to edit the append

structure CI_BBP_VE_ATTR of structure SRM_VE_SEVENT_ATTR.

If you want the parameters to be available for analysis of supplier scores later on, you have to add the

respective InfoObject to the extract structure SRM_VE_GUID_ATTR_STRUC.

NOTE

■ If you want to add standard SAP InfoObjects to the structures, drop the leading ‘0’. If you

want to add your self-defined InfoObjects, name the parameters exactly the same way as the



2011-11-08 PUBLIC 11/64

mailto:survey@system

InfoObjects. If you do so, the Supplier Evaluation front end automatically matches parameters

and InfoObjects.

■ Remember that parameters are only filled if the respective InfoObject is contained in the

DataStore object which holds the transactional document data for the particular scenario.

For example, if you want to add a parameter for confirmation questionnaires, the

corresponding InfoObject must be contained in the confirmation DataStore object.

2.5 Preparation of Evaluation in SAP NetWeaver BI

2.5.1 Preparation of SAP NetWeaver BI for Supplier Evaluation

To analyze data from operative systems and applications in SAP NetWeaver Business Intelligence (SAP

NetWeaver BI), the following tools and objects are necessary:

■ Data Extractors in the source systems, which work as interfaces to upload transactional and master

data to SAP NetWeaver BI

■ Data Structures like DataStore Objects and InfoCubes that store the transactional data in the SAP

NetWeaver BI system

■ Reporting Tools that allow you to view and analyze the transactional data in the SAP NetWeaver

BI system

BI Content includes extractors, data structures, and reports for the Supplier Evaluation scenario. BI

Content exists both in SAP NetWeaver BI and the ERP operational systems. Since customers can extend,

modify or just use the delivered structures as they stand, BI Content has to be actively installed.

PrerequisitesYou have configured SAP NetWeaver BI.

ProcessTo prepare the system for Supplier Evaluation, the following steps have to be performed:

1. Activate DataSources in the operational system

2. Activate DataSources in the SAP NetWeaver BI system

3. Install BI Content

4. Transfer BI roles for Supplier Evaluation to the operational system

5. Activate BSP application for Supplier Evaluation.

6. Optional: Set up Broadcasting for Reports

For more information about steps 1–3 and 6, see SAP Solution Manager under <project name>

Configuration SAP SRM <release> Basic Settings for SAP SRM Basic Settings for Analytics .

For more information about step 4, see the following paragraph. For more information about step 5,

see SAP Help Portal at http://help.sap.com under SAP NetWeaver <release> Library SAP Library

SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP



12/64 PUBLIC 2011-11-08

http://help.sap.com

Technology ABAP Workbench ABAP Workbench Tools Web Application Builder for BSPs Basic Functions

Activating BSP Application .

Transferring BI Roles for Supplier Evaluation to the Operational System

To analyze suppliers in the SAP NetWeaver BI system, users do not have to access the Supplier Evaluation

roles in the SAP NetWeaver BI system directly. It is also possible to include the Web templates for

evaluation in the SAP NetWeaver Portal, and you can import the relevant SAP NetWeaver BI roles into

your ERP or SAP SRM system and assign them to the users.

To do so, run transaction PFCG, and choose Role Read from other system via RFC . Select your SAP

NetWeaver BI system and the following BI roles:

■ SAP_BWC_SRM_STRAT_PURCHASER (Strategic Purchaser): Contains Web templates for the

strategic purchaser

■ SAP_BWC_SRM_MANAGER (Manager): Contains Web templates for the manager

■ SAP_BW_SRM_VENDOR_EVAL (Supplier Evaluation): Contains all Web templates of Supplier

Evaluation

You have to determine the Web templates which a certain user has in his menu. If you import the roles

into SAP SRM, we recommend the following matching between SAP NetWeaver BI and SAP SRM roles:

SAP NetWeaver BI Role SAP SRM Role

SAP_BWC_SRM_STRAT_PURCHASER (Strategic Purchaser)

/SAPSRM/ST_PURCHASER (SRM Strategic Purchaser)

SAP_BWC_SRM_MANAGER (Manager) /SAPSRM/MANAGER (SRM Manager)

SAP_BW_SRM_VENDOR_EVAL (Supplier Evaluation) /SAPSRM/OP_PURCHASER (SRM Operational Purchaser)

2.5.2 Adding Parameters to a Questionnaire

You can add parameters to the questionnaire to provide the user with the business context in which

he or she evaluates.

The following tables show all parameters that can be added to a questionnaire as context data. This

data is filled at runtime by the Supplier Evaluation front end. The data is read by DataStore Objects

which contain the transaction data for the documents. In the standard BI Content, these are the objects

0SRPO_D1, 0SRCF_D2, or 0SRIV_D3, depending on the valuation scenario involved. The technical

names of the parameters match the names of the InfoObjects (without the leading '0'), which are

contained in these DataStore objects and from which the data is read at runtime.

The list at the same time shows all context data belonging to an evaluation. The context data is

automatically extracted to SAP NetWeaver BI for later evaluation whenever a questionnaire is filled.

Be aware that the extraction of context data is independent of the number of parameters you added to

the questionnaire



2011-11-08 PUBLIC 13/64

You can find more information on adding parameters to a questionnaire on SAP Help Portal at

http://help.sap.com SAP NetWeaver <release> Library SAP Library SAP NetWeaver Library SAP

NetWeaver by Key Capability Application Platform by Key Capability Business Services Web Survey . You can

also view sample questionnaires on the SAP Service Marketplace at service.sap.com/ibc-srm Spend Analysis

and Reporting in SRM .

Procedure

Parameters for Invoice, Confirmation and Advanced Supplier List (0SRPO_D1, 0SRCF_D2 or

0SRIV_D3):

Description Technical Name

Logical Procurement System LOGSYS_PUR

Logical procurement system for which the evaluation is performed (equals parameter LOGSYS_PUR)

SR_EVALSYS

Business Transaction Category (Supplier Evaluation event) SR_EVENT

Document Number SR_DOCIDVE

Item Number in Document BBP_ITEM

Document GUID BBP_DOGUID

Document Item GUID BBP_ITGUID

Document Description BBP_DESCR

Document Posting Date CALDAY

Purchase Order Number BBP_PO_ID

Item Number in Purchase Order BBP_POITEM

Purchase Order GUID BBP_POGUID

Item GUID BBP_POITGU

Purchasing Organization ID (ERP or SRM) ORG_IDX

Purchasing Organization Name (read from master data) ORG_NAME

SRM Purchasing Organization ID (only filled if document is from SRM) BBP_PURORG

ERP Purchasing Organization ID (only filled if document is from ERP) PURCH_ORG

Product Category / Material Group ID (ERP or SRM) CAT_PUR_IDX

Product Category Name (read from master data) CAT_PUR_NAME

Product Category ID (SRM) PRCA_ID

Product Category GUID (SRM) PROD_CATEG

Material Group (ERP) MATL_GROUP

Product Category generic GUID (ERP or SRM) GN_CAT_PUR

Product / Material ID (ERP or SRM) PRODUCT_IDX

Product Name (read from master data) PRODUCT_NAME

Product ID (SRM) PROD_ID

Product GUID (SRM) BBP_PROD

Material (ERP) MATERIAL

Source System of Product BBP_SYS_PR



14/64 PUBLIC 2011-11-08

http://help.sap.com

Product generic GUID (ERP or SRM) PRODUCT

Supplier ID (ERP or SRM) VENDOR_IDX

Supplier Name (read from master data) VENDOR_NAME

Supplier ID (SRM) BBP_VENDOR

Supplier ID (ERP) VENDOR

Supplier generic GUID (ERP or SRM) GN_VENDOR

Service Agent ID (ERP or SRM) SR_SVP_LID

Service Agent Name (ERP or SRM) SRVPROV_NAME

Service Agent generic GUID (ERP or SRM) GN_SRVPROV

Plant (ERP) PLANT

Location (SRM) SR_LOCATIO

Parameters for Ad-Hoc Surveys Using Supplier Survey Cockpit

The following data is filled at runtime by the Supplier Survey Cockpit front end. The data is read from

the master data Object 0SR_SECGUID in standard BI Content.


Survey ID 0SR_CSURYID

Survey Name 0SR_CSRNAME

Survey Package ID 0SR_CSRGPID

Survey Package Name 0SR_SRPGNM

Questionnaire name 0SR_CQSNRNM

Questionnaire id 0SR_CQSNRID

Supplier SUPPLIER_ID

DUNS number

Evaluation Area ID 0SR_CEVAREA

Evaluation Area description 0SR_CEVARDS

Evaluation Category ID 0SR_CEVCATE

Evaluation Category description 0SR_CEVCTDS

Evaluation Period 0SR_CEVPERD

Participant e-mail address 0SR_CPCPMID

Participant last name 0SR_CEVLTNM

Participant first name 0SR_CEVFTNM

Plant ID (of participant) 0SR_CPLANT

Plant text (of participant) 0SR_CPLTTXT

In addition, the DataStore Object 0SR_VE_CP contains the following objects:


Free text indicator 0SR_CLNGTXT

Answers with zero (poor performance) 0SR_CASN0

Number of not answered questions 0SR_CNRANS



2011-11-08 PUBLIC 15/64

NOTE

When uploading data into 0SR_VE_CP, note the following:

After creating an info package on the DataSelection tab, enter SUSUCO as application, to retrieve

transactional data only from Supplier Survey Cockpit.

To obtain a complete upload including all Supplier Evaluation records, also the event-driven,

leave the data selection blank.

2.5.3 Loading Master Data

The master data contains the texts and attributes of characteristics for display.

It is mandatory to load the master data and texts from the OLTP system before performing the Supplier

Evaluation Customizing for questionnaire finding and before loading the transaction data. In

Customizing, you can only enter products, materials, supplier, and so on, for which master data exists.

Prerequisites

■ You have installed Business Content for Supplier Evaluation

■ System IDs have been maintained.

Procedure

Schedule the data load process as described below for at least the following InfoObjects. You can upload

more InfoSources, but those mentioned here are the ones necessary for this scenario: InfoObjects to

load master data for invoice, confirmation, approved supplier list and Supplier Survey Cockpit:

Application Component Info Object Comment

0CA_SUR-IO 0WS_ANSWER Optional; not yet integrated into reporting

0WS_APPL SRM_EV; The last two characters mirror the two-character logical system ID for which the questionnaire was defined. When loading data from SAP SRM, the last two letters ‘AL’ of the updated value ‘SRM_EVAL’ are overwritten with the two-character logical system ID. This is because the uploading system is not integrated with the Web Survey master data

0WS_QUEST -

0WS_QSTNNR -

0WS_SURVEY -

0WS_STATUS 0WS_STATUS Optional

0SRM_VE-IO 0SR_EVENT -

0GN 0GN_VENDOR InfoSources to load for ERP: ■ 0VENDOR_ATTR ■ 0VENDOR_TEXTInfoSources to load for SRM: ■ 0BPARTNER_ATTR ■ 0BPARTNER_TEXT ■ BBP_PARTNER_FLAG_VENDOR ■ 0BP_DEF_ADDRESS_ATTR



16/64 PUBLIC 2011-11-08


(these InfoSources do not update 0GN_VENDOR directly, but via DataStore object 0GN_BP)

0GN_CAT_PUR InfoSources to load for ERP: ■ 0MATL_GROUP_TEXTInfoSources to load for SRM: ■ 0PROD_CATEG_ATTR ■ 0PROD_CATEG_TEXT

0PRODUCT InfoSources to load for ERP: ■ 0MATERIAL_ATTR ■ 0MATERIAL_TEXTInfoSources to load for SRM: ■ 0BBP_PRODUCT_ATTR ■ 0PRODUCT_TEXT

0GN_LOCATIO InfoSources to load for ERP: ■ 0PLANT_ATTRInfoSources to load for SRM: ■ 0BBP_PLANT_ATTR ■ 0BBP_PARTNER_FLAG_LOCATION(the InfoObject is also updated by DataStore object 0GN_BP)

1. Choose InfoSources in the Data Warehousing Workbench (transaction RSA1)

2. Position the cursor on the top node in the tree on the right side.

3. To find the InfoSource you want to load, choose Find.

4. To assign a DataSource, click the right-hand mouse button on the InfoSource and select your

source system.

5. Click the right-hand mouse button on your source system. Choose Create InfoPackage.

6. Enter a description and choose Enter.

7. On the following screen, select Full Update on tab page Update Parameters.

8. On tab page Processing, select PSA and then into DataTargets.

9. On tab page Schedule, click on Batch. Then click on Start. The data is transferred into the master data

table of your InfoObject.

NOTE

IF you have not connected SAP Supplier Relationship Management (SAP SRM), but only ERP

systems to SAP NetWeaver BI, you have to maintain values for the InfoObject 0SR_EVENT

manually. We recommend that you maintain at least the following values:

■ BUS2203: Invoice

■ BUS2205: Goods Receipt

■ BUS2206: Approved Supplier List



2011-11-08 PUBLIC 17/64

2.5.4 Defining Evaluation Roles and Attaching them to User IDs

A role authorization concept determines which documents or suppliers a user can evaluate. Evaluation

worklists are filtered by the rules a user is assigned to. Therefore you have to define roles in SAP

NetWeaver Business Intelligence (SAP NetWeaver BI) for the different groups of employees entitled to

evaluate. Different groups may see different questionnaires for a document, or, for example, a group

may only be allowed to perform evaluations for certain product categories or suppliers.

Procedure

1. Define the roles you need for Supplier Evaluation using transaction PFCG.

2. Distribute the roles to the users that are supposed to evaluate.

2.5.5 Setting Up Supplier Evaluation for Non-Standard DataStore Objects

If you do not want to use the standard DataStore Objects 0SRPO_D1, 0SRCF_D2, or 0SRIV_D3 for

Supplier Evaluation, you have to integrate the DataStore Objects you want to use instead into Supplier

Evaluation.

Procedure

1. Change the InfoSets 0SRVE_IS1, 0SRVE_IS2 and 0SRVE_IS3 to run on the new DataStore Objects.

2. Copy the Supplier Evaluation queries from the standard InfoSets to your alternative ones.

3. Create update rules from the new DataStore Objects into the administrative DataStore Objects

0SRVE_O3 or 0SRVE_O4, respectively.

4. You have to implement Business Add-In (BAdI) RS_BCT_SRM_VE_APP, so that the Supplier

Evaluation front end can access the new DataStore Objects during the evaluation process.

BAdI RS_BCT_SRM_VE_APP

The BAdI enables you to modify the standard Supplier Evaluation process to meet your specific

requirements.

Method SET_ODS_OBJECTS

If you implement this method, the system overrides the result of the standard DataStore Object

determination. Using the method, you can make sure that the Supplier Evaluation front end still finds all

necessary objects, even after you copied or modified the DataStore Objects delivered with SAP BI

Content.

Importing

IV_SR_EVENT

Transaction Type



18/64 PUBLIC 2011-11-08

■ BUS2203: Confirmation


■ BUS2206: Supplier List

Changing

■ CV_SOURCE_ODS

DataStore Object that holds document data from the OLTP system for the business transaction

category

■ CV_ADMIN_ODS

DataStore Object that holds administrative data for Supplier Evaluation (that is, information about

the questionnaire that has to be called for a certain document or supplier, if an evaluation is

mandatory or not, and who is supposed to evaluate)

■ CV_EVAL_ODS

Transactional DataStore Object that holds information about the evaluation status (that is, who

evaluated the document or supplier, and the evaluation time)

■ CV_SOURCE_DOCGUID

InfoObject in the DataStore Object CV_SOURCE_ODS, which holds the document GUID of a

document (this information is necessary to match SOURCE_ODS and ADMIN_ODS)

■ CV_SOURCE_ITMGUID

InfoObject in the DataStore Object V_SOURCE_ODS, which holds the item GUID of a document

(this information is necessary to match SOURCE_ODS and ADMIN_ODS)

2.5.6 Loading Transaction Data

The transaction data contains all the information that the user wants to report on. It also contains all

relevant information about confirmations, invoices, and suppliers that are necessary to perform an

offline Supplier Evaluation in SAP NetWeaver Business Intelligence (SAP NetWeaver BI).

Prerequisites

■ You have installed Business Content for Supplier Evaluation.

■ You have assigned a source system ID to every source system in the Data Warehousing Workbench under

Tools Assign source system to source system ID.

■ You have loaded the master data.

■ You have defined the Customizing for Supplier Evaluation to be able to load the administrative

DataStore Objects.



2011-11-08 PUBLIC 19/64

Procedure1. Perform a delta initialization for your transaction data from the OLTP systems into the DataStore

Objects. The following figure illustrates where the upload of transaction data into DataStore object

is situated within the whole Supplier Evaluation process. The table below describes the data flow.

Figure 1:

Application Component Info Source Comments

MM_PUR 2LIS_02_HDR Updates document headers from SAP ERP in 0SRPO_D1

2LIS_02_ITM Updates document items from SAP ERP in 0SRPO_D1

2LIS_02_SCL Updates document schedule lines from SAP ERP in 0SRPO_D1

MM_LIV 2LIS_06_INV Updates documents and items from SAP SRM in 0SRIV_D3

0BBP_PROC_50 0SRM_TD_PO Updates documents and items from SAP SRM in 0SRPO_D1

0SRM_TD_IV Updates documents and items from SAP SRM in 0SRIV_D3

0SRM_TD_CF Updates documents and items from SAP SRM in 0SRCF_D2

2. Update the transaction data from the DataStore Objects all the way into InfoCube 0SR_C01 and

to the administrative DataStore Objects for Supplier Evaluation (see figure below).

The administrative DataStore Objects are designed as follows:

■ 0SRVE_O3: Administrative Supplier Evaluation for documents (on item level)

■ 0SRVE_O4: Administrative Supplier Evaluation for suppliers (by product category or by

product, depending on the level of detail of questionnaire determination Customizing)

3. For each supplier or document that has been loaded into the DataStore Objects for transactional

document data, the administrative DataStore Objects hold information about which

questionnaires have to be filled in, by which role, and who is responsible for the evaluation. It also

carries information on whether this evaluation is obligatory or optional.

4. The update rules of the administrative DataStore Objects determine this information by reading

the questionnaire determination Customizing. If you want to override the standard questionnaire

determination, you can change the update rules.

NOTE

■ In this process, special Customizing counts more than general Customizing – an entry

for product 100 of product category 4711 is preferred to an entry for all products of

category 4711. See also the examples in Defining Questionnaire Determination [page 49].

■ If you created equal Customizing entries for different roles (for example, to allow

different roles to evaluate a document or a supplier from differing points of view), the

update rules store the record in the administrative DataStore Objects several times, once

for each role.

■ The administrative DataStore Objects are also updated with evaluations that have been

performed in SAP Supplier Relationship Management (SAP SRM). This ensures you



20/64 PUBLIC 2011-11-08

cannot only monitor the evaluation process in SAP NetWeaver BI, but also in SAP SRM.

The standard BI Content, though, has several queries for monitoring.

Figure 2:

5. Use the delta method for loading transactional data after a successful delta initialization.

2.5.7 More Information About the Preparation of Evaluation in SAP NetWeaver BI

Run the following system transactions in SAP NetWeaver BI:

■ Modeling - DW Workbench (RSA1)

■ RFC Destinations (Display/Maintain) (SM59)

■ BIW in IMG for OLTP (SBIW)

■ Authorizations for Reporting(RSSM)

■ Role Maintenance (PFCG)

2.6 Preparation of Evaluation in SAP ERP

2.6.1 Customizing in ERP Vendor Evaluation

For information on the purpose of the required settings, see the documentation for SAP ERP Central

Component on the SAP Help Portal at http://help.sap.com SAP Library SAP ERP Central

Component Logistics Materials Management (MM) Information System (MM-IS) MM Vendor Evaluation

and Customizing of your ERP system under Materials Management Purchasing Vendor Evaluation

Logistics Invoice verification.

ProcedureYou can define the points scores and common parameters for the automatic criteria per purchasing

organization. You do so in Customizing of your ERP system under Materials Management Purchasing

Evaluation and Statistics Vendor Evaluation Maintain Purchasing Organization Data.

You can also define the point scores and common parameters for the automatic criteria per company

code. You do so and activate the evaluation for invoices in Customizing of your ERP system under

Materials Management Purchasing Evaluation and Statistics Vendor Evaluation Logistics Invoice

verification.

The points scores can be customized only for the automatic criteria quantity reliability (scoring method

2), on-time delivery (scoring method 3), shipping notification reliability (scoring method A), quantity variance for

invoices (scoring method F), and price variance for invoices (scoring method E). These scores are dependent

on which Best Score is defined under the common parameters.


2.6 Preparation of Evaluation in SAP ERP

2011-11-08 PUBLIC 21/64

http://help.sap.com

You can define the parameters Standardizing value for delivery time variance and Minimum delivery quantity

(percentage) for the criterion on-time delivery performance. You do so under the common parameters. These

two parameters can also be defined directly by the material master. See the Customizing under

Materials Management Purchasing Material Master Define Purchasing Value Keys.

The points scores of the criterion shipping instructions (scoring method 6) are defined in Customizing under

Materials Management Purchasing Material Master Define Shipping Instructions.

The points scores of the criterion quality rating of service (scoring method C) and timeliness rating of service

(scoring method D) are filled directly in the service entry sheet.

You must have defined the criteria quality rating of service and timeliness rating of service in Customizing under

Materials Management Purchasing Vendor Evaluation Define Criteria.

All other criteria, common parameters, and customizing settings are not relevant to extract

the scores on item level with DataSource 2LIS_02_ITM and SR_VE_INT_IV.

2.7 Preparation of SAP NetWeaver BI for Analysis

2.7.1 Maintaining the ERP Vendor Evaluation Enhancement

To be able to use the automatic scores of the standard ERP Vendor Evaluation, you have to maintain

master data manually in the SAP NetWeaver Business Intelligence (SAP NetWeaver BI) system. This

enables you to use the criteria in the Customizing of grouping and weighting.

Procedure

Maintain the master data in the Data Warehousing Workbench (transaction RSA1) for the following Web

Survey info objects:

1. 0WS_QUEST Question

NOTE

For the application, maintain SRM_EVXX. "XX"' is the two-character system ID of your ERP

system.

For the questionnaire, maintain R3VE.

For the question, maintain the scoring method ID of your automatic criteria and the

description of your criteria. The following automatic criteria are available:

■ 2 - quantity reliability

■ 3 - on-time delivery

■ 6 - shipping instructions

■ A - notification reliability

■ C - quality rating of service

■ D - timeliness rating of service

2. 0WS_QSTNNR Questionnaire



22/64 PUBLIC 2011-11-08

NOTE

For the application, maintain SRM_EVXX. "XX"' is the two-character system ID of your ERP

system.

For the questionnaire, maintain R3VE.

2.7.2 Maintaining Common Interface for External Evaluation Systems

To be able to use evaluation scores of other supplier evaluation systems, you have to maintain master

data manually in the SAP NetWeaver Business Intelligence (SAP NetWeaver BI) system. This way, you

can also use the criteria in the Customizing of grouping and weighting. Additionally, you have to

maintain the common interface, performing a mapping between DataSource and InfoSource.

Procedure

Maintain the master data in the Data Warehousing Workbench (transaction RSA1) for the following Web

Survey info objects:

1. 0WS_QUEST Question

NOTE

For the application, maintain SRM_EVXX. "XX" is the two-character system ID of your

evaluation system.

For the questionnaire, maintain a grouping text for your criteria.

For the question, maintain the IDs of your criteria and the descriptions.

2. 0WS_QSTNNR Questionnaire

NOTE

For the application, maintain SRM_EVXX. "XX" is the two-character system ID of your

evaluation system.

For the questionnaire, maintain a grouping text for your criteria.

Maintain the mapping between the InfoSource 0SR_VE_INT (General Evaluation Interface) and your self-

defined DataSource. The following table lists the info objects are available:

0SR_VEGUID Assessment GUID

0BBP_ITEM Document Line Number

0BBP_POITEM Item No.in Order Doc

0BBP_PO_ID Purchase Order No.

0BBP_PROD Product

0BBP_PURORG Purch. Organization

0BBP_SYS_BP Log. Procurem.System

0BBP_SYS_PR Source Product

0BBP_VENDOR Vendor

0CALDAY Calendar Day



2011-11-08 PUBLIC 23/64

0LOGSYS_PUR Log. Proc. System

0PRCA_ID Product Category ID

0PROD_CATEG Product Category

0PROD_ID Product ID

0SR_DOC_DT Document Date

0SR_EVENT Valuation Event

0USERNAME User Name

0SR_DOCIDVE Document ID

0SR_LOCATIO Bus.Partner Location

0MATERIAL Material

0MATL_GROUP Material group

0PURCH_ORG Purchasing org.

0PLANT Plant

0VENDOR Vendor

0SR_SVP_LID Local ID Serv.Provid

0SR_VE_CRIT Criterion

0SR_SUBCRIT Subcriterion

0WS_APPL Application

0WS_QSTNNR Questionnaire

0WS_VALUE Value of Answer

0WS_SURVEY Survey

0SR_VE_VAL Criteria Valuation

0WS_STATUS Questionnaire Status

0WS_COUNT Number

0WS_KFIGTYP Key Figure Type

0RECORDMODE Update Mode

0SR_ROLE Role in Vendor Evaln

0SR_EVALSYS Evaluation System

The following list shows the most important fields and their explanations:

■ 0SR_VEGUID ( unique key for each evaluation)

■ 0SR_VE_CRIT ( criterion ID like ONTDEL for on-time delivery)

■ 0WS_APPL (application like SRM_EVAL)

■ 0WS_QSTNNR (grouping element for criteria)

■ 0WS_VALUE (scores)

■ 0WS_SURVEY (second grouping element for 0WS_QSTNNR)

■ 0SR_VE_VAL (1 means this record should update the evaluation DataStore object)

■ 0WS_STATUS (status of the evaluation)

■ 0WS_COUNT (count = 1)

■ 0WS_KFIGTYP (type of criterion like automatic calculation)



24/64 PUBLIC 2011-11-08

For ad-hoc surveys using the Supplier Survey Cockpit the following fields are required in addition to

above listed fields:

■ 0SR_CLNGTXT (free text indicator)

■ 0SR_CASN0 (answers with zero; bad performance)

■ 0SR_CNRANS (number of not answered questions)

2.7.3 Configuration of Supplier Evaluation for Analysis

Before you can upload the data of filled questionnaires from SAP Supplier Relationship Management

(SAP SRM) to SAP NetWeaver Business Intelligence (SAP NetWeaver BI), and perform a supplier

evaluation, you have to customize how this evaluation is to be performed. You have to customize the

grouping of questionnaire criteria, and afterwards specify how the grouped criteria are weighted to

calculate the total score of a supplier. You do this in SAP NetWeaver BI.

Prerequisites

You have configured the SAP NetWeaver BI system and prepared it for Supplier Evaluation as explained

in the preceding sections.

Process

To configure Supplier Evaluation, the following steps have to be performed:

1. Load and maintain master data

2. Define Grouping

3. Define Weighting

2.7.4 Loading Master Data

The master data contains the texts and attributes of characteristics for display.

It is mandatory to load the master data and texts from the OLTP system before performing the Supplier

Evaluation Customizing for questionnaire finding and before loading the transaction data. In

Customizing, you can only enter products, materials, supplier, and so on, for which master data exists.

Prerequisites

■ You have installed Business Content for Supplier Evaluation

■ System IDs have been maintained.

Procedure

Schedule the data load process as described below for at least the following InfoObjects. You can upload

more InfoSources, but those mentioned here are the ones necessary for this scenario: InfoObjects to

load master data for invoice, confirmation, approved supplier list and Supplier Survey Cockpit:



2011-11-08 PUBLIC 25/64


0CA_SUR-IO 0WS_ANSWER Optional; not yet integrated into reporting

0WS_APPL SRM_EV; The last two characters mirror the two-character logical system ID for which the questionnaire was defined. When loading data from SAP SRM, the last two letters ‘AL’ of the updated value ‘SRM_EVAL’ are overwritten with the two-character logical system ID. This is because the uploading system is not integrated with the Web Survey master data

0WS_QUEST -

0WS_QSTNNR -

0WS_SURVEY -

0WS_STATUS 0WS_STATUS Optional

0SRM_VE-IO 0SR_EVENT -

0GN 0GN_VENDOR InfoSources to load for ERP: ■ 0VENDOR_ATTR ■ 0VENDOR_TEXTInfoSources to load for SRM: ■ 0BPARTNER_ATTR ■ 0BPARTNER_TEXT ■ BBP_PARTNER_FLAG_VENDOR ■ 0BP_DEF_ADDRESS_ATTR(these InfoSources do not update 0GN_VENDOR directly, but via DataStore object 0GN_BP)

0GN_CAT_PUR InfoSources to load for ERP: ■ 0MATL_GROUP_TEXTInfoSources to load for SRM: ■ 0PROD_CATEG_ATTR ■ 0PROD_CATEG_TEXT

0PRODUCT InfoSources to load for ERP: ■ 0MATERIAL_ATTR ■ 0MATERIAL_TEXTInfoSources to load for SRM: ■ 0BBP_PRODUCT_ATTR ■ 0PRODUCT_TEXT

0GN_LOCATIO InfoSources to load for ERP: ■ 0PLANT_ATTRInfoSources to load for SRM: ■ 0BBP_PLANT_ATTR ■ 0BBP_PARTNER_FLAG_LOCATION(the InfoObject is also updated by DataStore object 0GN_BP)

1. Choose InfoSources in the Data Warehousing Workbench (transaction RSA1)

2. Position the cursor on the top node in the tree on the right side.

3. To find the InfoSource you want to load, choose Find.

4. To assign a DataSource, click the right-hand mouse button on the InfoSource and select your

source system.



26/64 PUBLIC 2011-11-08

5. Click the right-hand mouse button on your source system. Choose Create InfoPackage.

6. Enter a description and choose Enter.

7. On the following screen, select Full Update on tab page Update Parameters.

8. On tab page Processing, select PSA and then into DataTargets.

9. On tab page Schedule, click on Batch. Then click on Start. The data is transferred into the master data

table of your InfoObject.

NOTE

IF you have not connected SAP Supplier Relationship Management (SAP SRM), but only ERP

systems to SAP NetWeaver BI, you have to maintain values for the InfoObject 0SR_EVENT

manually. We recommend that you maintain at least the following values:


■ BUS2205: Goods Receipt

■ BUS2206: Approved Supplier List

2.7.5 Load of Transaction Data from SAP SRM, SAP ERP, and SAP NetWeaver BI

The transaction data contains all the information that the user wants to report on.

Prerequisites

■ You have installed BI Content for Supplier Evaluation.

■ You have assigned a source system ID to every source system in the Administrator Workbench under

Tools Assign source system to source system ID .

■ You have loaded the master data.

■ You have defined the Customizing for Supplier Evaluation to load the InfoCube.

Process

1. The figure below illustrates the upload process of transactional evaluation data for confirmation,

invoice, and approved supplier list.

Figure 3:

1. Load your transaction data from the SAP SRM and/or SAP NetWeaver BI system using the

following DataSources:

CAUTION

Always load InfoSource 0SR_VEGUID before InfoSource 0WS_DATA_1.

■ 0SRM_VE-IO: 0SR_VEGUID



2011-11-08 PUBLIC 27/64

■ 0CA_SUR: 0WS_DATA_1

2. Load your transaction data from the ERP vendor evaluation using the following DataSource:

0MM_PUR: 2LIS_02_ITM

3. Update the Supplier Evaluation InfoCube (0SR_VE_C1). For more information, see Update of

Supplier Evaluation InfoCube [page 28].

4. Use the delta method for loading transaction data after a successful delta initialization.

2. The principle for load of transactional data for ad-hoc surveys is the same, but it uses different

DataStore Objects and InfoCubes:

Figure 4:

1. Load your transaction data from the SAP SRM and/or SAP NetWeaver BI system using the

following DataSources:

CAUTION

Always load DataSource 0SR_VEGUID before DataSource 0WS_DATA_1.

■ 0SRM_VE: 0SR_SECGUID

■ 0CA_SUR: 0WS_DATA_1_C

2. Update the Weighted Evaluation from Cockpit InfoCube (0SR_VE_C2).

3. Use the delta method for loading transaction data after a successful delta initialization.

2.7.6 Update of Supplier Evaluation InfoCube

Procedure

The weighted scores of suppliers are calculated during the InfoCube update on the basis of the

Customizing tables with the grouping definitions and weighting definitions.

Determination of Grouping of Criteria

The update routine reads the grouping definitions for every row of the DataStore Object to determine

the groupings to which criteria are assigned. Since Supplier Evaluation supports both, system-specific

evaluations, and global evaluations, you can assign criteria that are defined in a specific system to both,

to the system-specific grouping, and to the global grouping. In this case, the update routine duplicates

the data record from the DataStore Object to create a system-specific and a global data record in the

InfoCube.

If you have only defined a global weighting, the system field is overwritten with (*). This shows that

criteria have been weighted globally. The System-Wide indicator (0SR_SYSFLAG), which is used in the

queries, is also set. If criteria have not been assigned to a grouping, they are not transferred to the

InfoCube.



28/64 PUBLIC 2011-11-08

Instead, a warning message is displayed in the monitor informing you that you have defined criteria in

a questionnaire and that these criteria cannot be used in reporting. To ensure that your grouping model

is correct, you should always check the monitor after you have uploaded data to the InfoCube. If, on

the other hand, you have defined a grouping, but you have not defined a suitable weighting, the update

is terminated. During the upload, the groups to which the criterion is assigned at every level are saved

to the relevant InfoObjects (0SR_VE_GID1, 0SR_VE_GID2, and 0SR_VE_GID3). The data in the

DataStore Object is enriched by calculating the numerators and denominators for each level.

Example

Calculation of Scores

Figure 5:

In this example, the groups Procurement Criteria, Quality, and Quality of Goods are saved at levels 3 through 1

for the criterion State of Goods.

The diagram below shows how the individual numerators and denominators are determined:

Figure 6:

The update routine saves the numerators and denominators for each level and criterion in separate

InfoObjects (The numerators are stored in 0SR_VE_EGW1, 0SR_VE_EGW2, 0SR_VE_EGW3, and

0SR_VE_EGWO; the denominators in 0SR_VE_DGW1, 0SR_VE_DGW2, 0SR_VE_DGW3, and

0SR_VE_DGWO.). For example, the fraction 1/6 is stored at level 1 by writing 1 to InfoObject

0SR_VE_EGW1 and 6 to InfoObject 0SR_VE_DGW1.

At the same time, the update routine calculates the extent to which the criterion counts toward the

weighted score at each level. (The results are stored in the InfoObjects 0SR_VE_VAL1, 0SR_VE_VAL2,

0SR_VE_VAL3, and 0SR_VE_VALO.) The following diagram shows our example with actual scores:

Figure 7:

Processing Several Weightings

As mentioned in the Definition of Weightings in SAP NetWeaver BI [page 58] section, it is possible to define

several weightings for the same source system. You can define a general weighting and specific

weightings for some product categories and products.

For example, you might define a global weighting that applies to the vast majority of your products.

On-time delivery is not, however, a critical issue for a specific product category (office supplies, for



2011-11-08 PUBLIC 29/64

example). Consequently, you can give a lower weighting to the criterion for on-time delivery. The

price, on the other hand, is important, and so you give this criterion a higher weighting. The reliability

of the quantity delivered is not so important for the product pencils, which means that you can define

a specific weighting for this as well.

How does the update rule deal with several weightings at different levels of specialization? During the

update, the level with the highest degree of specialization is read first. If it does not find a weighting

there, the rule continues looking at the next level up until it finds a weighting.

In our example, the following weightings are used:

■ For a product of the product category Chemicals: general weighting

■ For the product Computer: weighting for product category Office Supplies

■ For the product Pencil: product-specific weighting for Pencil.

The table below shows the consecutive levels at which the update routine searches for weightings. The

routine reads the source system for every data record, and checks the groupings and weightings that

have been defined in Customizing for SAP NetWeaver BI.

Read Step Product Product Category Purchasing Organization Location

(01) 4711 10 1000 10

(02) 4711 10 1000 *

(03) 4711 10 * *

(04) * 10 1000 10

(05) * 10 1000 *

(06) * 10 * *

(07) * * 1000 10

(08) * * 1000 *

(09) * * * 10

(10) * * * *

2.7.7 Settings in Content Queries in SAP NetWeaver BI

Procedure

The Business content for Supplier Evaluation comprises queries and Web templates that you may have

to adapt to your business scenario. Therefore, you require an idea of the variables and key figures used

specifically in Supplier Evaluation.

Variables in Web Templates

All the queries of Supplier Evaluation used in Web templates have at last two variables for manual entry:

■ Cross-system evaluation

■ E-Procurement system

(Exception: Query for supplier portfolio 0SR_VE_M1_Q001)



30/64 PUBLIC 2011-11-08

You only maintain one of the two variables. To report on the data and grouping – independently of

the source system of evaluation data – enter X in the variable cross-system evaluation. Leave the other

variable empty.

To report on the data and grouping belonging to one single source system of evaluation data, leave the

variable cross-system evaluation empty. Use the input help to maintain the specific logical procurement

system in the E-Procurement System.

If you have only one source system, or if you always want to evaluate suppliers independently of the

source system, you can delete the variable E-Procurement System in the query definition. In this case,

also delete the variable cross-system evaluation and set X as a fixed filter value for the characteristic

System-Wide (0SR_SYSFLAG) in the query definition. As a result, the query only reports on the defined

(*)-grouping (see Definition of Groupings in SAP NetWeaver BI [page 56]).

NOTE

Be sure that in the described case, you also delete the mapping of the logical procurement system

to the SAP NetWeaver BI variable for every Web template. See Customizing for SAP Supplier

Relationship Management under SRM Server Cross-Application Basic Settings Define Logical Systems

and Template Names for BW Reports .

Maintain Filter Values

In the section entitled Examples and Recommendations for Modeling in Definition of Groupings in SAP NetWeaver

BI [page 56], we looked at cases where it might not be possible to compare the total scores of different

suppliers. If you cannot define questionnaires and the evaluation process properly to solve the

mentioned problem, you can use filter values in the query definition.

RECOMMENDATION

We recommend that you build specific queries for the suppliers that require specific weightings.

In most cases, these suppliers belong to one specific product category. The specific query should

show only the data from the scoring levels on which suppliers are comparable. Preselect the special

suppliers as fixed filter values of the InfoObject 0BBP_SUPPLIER (in case of one connected

procurement system) or 0GN_SUPPLIER (in case of multiple connected procurement systems)

in the query definition. Furthermore, preselect the criteria and groupings that are evaluated for

the displayed suppliers.

Calculation of Supplier Scores in Queries

If you want to build your own query for Supplier Evaluation or to adapt the key figure definition, you

have to understand the calculation process.

For each criterion of an evaluation document (invoice, confirmation), the InfoCube 0SR_VE_C01

provides the value of the criterion, as well as the four weighted scores of the different grouping levels

(see Update of Supplier Evaluation InfoCube [page 28]). Note that the weighted score of the different grouping



2011-11-08 PUBLIC 31/64

levels in the InfoCube is – strictly speaking – only the contribution of the criterion’s valuation to the

weighted score of the group or total score.

Selection of InfoObjects in the InfoCube 0SR_VE_C01

Evaluation GUID

Criterion (0SR_VE_CRIT)

Criteria Valuation (0SR_VE_VAL)

Contribution of Weighted Score Level1 (0SR_VE_VAL1)



Contribution of Weighted Overall Score (0SR_VE_VAL0)

000001 Condition of Goods

100 16.667 5.556 3.178 0.987

Furthermore, the following InfoObjects are relevant for the calculation in the query:

■ Weighting key (0SR_VE_WKEY)

■ Grouping 1 (0SR_GID1)



The calculation of the score is dependent on the level that is analyzed.

Calculation of Criterion Value

The calculation of the value per criterion is simple. Criteria Valuation (0SR_VE_VAL) has to be

aggregated for each single criterion as an arithmetic average.

Calculation of Weighted Score on Each Grouping Level

The calculation of the weighted score is performed in three calculation steps, because the calculation

is dependent on the objects criterion, weighting key, and grouping.

1. At first, for each criterion and each weighting key of one group, the average must be calculated.

Result: average of contribution of weighted score per criterion and weighting key of analyzed level.

Correspondence as calculated key figure:

Group score per criterion and weighting (Grouping Level 1) 0SR_VE_C1_CK021



Overall score per criterion and weighting (Grouping Level 4) 0SR_VE_C1_CK024

Calculation Step 1: Average per Criterion and Weighting Key

Figure 8:

2. Aggregate the criterion averages of contribution per weighting key for each grouping of the

grouping level.

Result: The weighted score of each group of the grouping level depends on the weighting key.


Group score per weighting (Grouping level 1) 0SR_VE_C1_CK011



32/64 PUBLIC 2011-11-08



Overall score per weighting (Grouping level 4) 0SR_VE_C1_CK014

Calculation Step 2: Weighted Score of Each Group (here group Service Quality) per

weighting key

Figure 9:

3. Aggregate the individual weighted score per weighting key as average.

Result: Weighted score of each group


Group Score (Grouping Level 1) 0SR_VE_C1_CK001



Overall Score (Grouping Level 4) 0SR_VE_C1_CK004

Calculation Step 3: Weighted Score for Each Group (here group Service Quality)

Figure 10:

2.7.8 Change of Settings

Procedure

The change of Customizing settings always affects the evaluation results. Therefore, you must perform

certain follow-up activities to ensure the evaluation scores are based on the new settings. These follow-

up activities are described here for each category of change.

Change of Questionnaires / Definition of New Questionnaires

You can change existing questionnaires for event-driven surveys or define new ones using transaction

BBP_EVAL_SURVEY. For ad-hoc surveys using the Supplier Survey Cockpit, click on Create

questionnaire or Change questionnaire in your portal landscape. An SAPGUI session opens with the transaction

for questionnaire creation.

Changing questionnaires has a strong impact on SAP NetWeaver BI evaluation data and you need to

perform several follow-up activities if you carry out any changes:

New Questions/Questionnaires

■ Include the new questionnaire in the event-handling of Supplier Evaluation using the view

BBPV_VE_EVENTS per SM30, or, alternatively, in Customizing under Integration with Other SAP



2011-11-08 PUBLIC 33/64

Components Data Transfer to the SAP NetWeaver Business Intelligence Settings for Application-Specific

DataSources (SRM) Define Events for Supplier Evaluation in SRM .

■ Upload master data of survey, questionnaires, and questions into SAP NetWeaver BI with the help

of InfoSources 0WS_*.

■ Include the new objects into grouping and weighting Customizing using the transactions

SRM_VE_GROUPING and SRM_VE_WEIGHTING.

If existing grouping or weightings have changed:

■ Delete data of InfoCube Weighted Scores (0SR_VE_C1 for event-driven surveys and 0SR_VE_C2 for

ad-hoc surveys with the Supplier Survey Cockpit)) with transaction RSA1. Click the right-hand

mouse button on the InfoCube, choose Delete Data. Delete Fact Table and Dimensions.

■ Reload evaluation data of InfoCube 0SR_VE_C1 from ODS object 0SR_VE for event-driven

surveys. Reload evaluation data of InfoCube 0SR_VE_C2 from DataStore object 0SR_VE_CP for

ad-hoc surveys.

Change to Questions in an Existing Questionnaire

RECOMMENDATION

We recommend that you do not change the question-ID of an existing question. If you do have

to change it, you must complete the following:

■ Upload master data of questions into SAP NetWeaver BI with the help of InfoSource 0WS_QUEST.

■ Include of the new (changed) question into grouping and weighting Customizing using

transactions SRM_VE_GROUPING and SRM_VE_WEIGHTING and delete the old question.

■ Delete data of InfoCube Weighted Scores (0SR_VE_C1 for event-driven surveys and 0SR_VE_C2 for

ad-hoc surveys with the Supplier Survey Cockpit) with transaction RSA1. Click the right-hand

mouse button on the InfoCube, choose Delete Data. Delete Fact Table and Dimensions.

■ For event driven surveys: Delete data of DataStore Object 0SR_VE.

■ Reload evaluation data of InfoCube 0SR_VE_C1 from DataStore Object 0SR_VE for event-driven

surveys.

■ For ad-hoc surveys: Delete data of DataStore Object 0SR_VE_CP

■ Reload evaluation data of InfoCube 0SR_VE_C2 from DataStore Object 0SR_VE_CP for ad-hoc

surveys.

You can change the Reporting text field in the definition of a question, but afterwards you must upload

the master data of the question with InfoSource 0WS_QUEST.

If you change the valuation of answer options belonging to a question, you must upload the master

data of the question into SAP NetWeaver BI with the help of InfoSource 0WS_QUEST. A change of

valuation should only be made with regard to the definition of the valuation scale.



34/64 PUBLIC 2011-11-08

RECOMMENDATION

We recommended that you only use one scale definition for all Supplier Evaluation questionnaires

(application SRM_VENDOR_EVALUATION). After changing answer options, you must upload

object Answer Option (InfoSource 0WS_ANSWER).

Deletion of Questions in an Existing Questionnaire

You must complete the following:

■ Delete the old question in grouping and weighting Customizing using transactions

SRM_VE_GROUPING and SRM_VE_WEIGHTING.

■ (Recommended:) Upload master data of questions into SAP NetWeaver BI with the help of

InfoSource 0WS_QUEST.

■ Delete data of InfoCube Weighted Scores (0SR_VE_C1 for ad-hoc surveys and SR_VE_C2 For event

driven surveys) with transaction RSA1. Click the right-hand mouse button on the InfoCube,

choose Delete Data. Delete Fact Table and Dimensions.

■ For event-driven surveys:

● Delete data of DataStore Object 0SR_VE.

● Reload evaluation data of InfoCube 0SR_VE_C1 from DataStore Object 0SR_VE

■ For ad-hoc surveys:

● Delete data of DataStore Object 0SR_VE_CP

● Reload evaluation data of InfoCube 0SR_VE_C2 from DataStore Object 0SR_VE_CP

Changes to Parameters and Valuation Levels for Supplier Evaluation in SRM

You can change the parameters and valuation levels for Supplier Evaluation in SRM in Customizing

for SAP SRM under Integration with Other mySAP.com Components Data Transfer to the SAP Business Information

Warehouse Settings for Application-Specific DataSources (SRM) Define Events for Vendor Evaluation in SRM .

Changes to these objects affect future evaluations. Follow-up activities are not necessary if these

definitions are changed.

Change of Grouping/Weighting

If you make changes to weighting, you must always complete the following:

■ Delete the data of InfoCube Weighted Scores (0SR_VE_C1) with transaction RSA1. Click the right-

hand mouse button on the InfoCube, choose Delete Data. Delete Fact Table and Dimensions.





If you make changes to grouping definition, you must always complete the following:

■ Change weighting definitions accordingly




2011-11-08 PUBLIC 35/64

● Delete data of the InfoCube Weighted Scores (0SR_VE_C1) with transaction RSA1. Click the

right-hand mouse button on the InfoCube, choose Delete Data. Delete Fact Table and Dimensions.



● Delete data of the InfoCube Weighted Scores (0SR_VE_C2) with transaction RSA1. Click the

right-hand mouse button on the InfoCube, choose Delete Data. Delete Fact Table and Dimensions.




36/64 PUBLIC 2011-11-08

3 Supplier Evaluation

3.1 Evaluating and Monitoring of Supplier Performance

The process Evaluating and Monitoring of Supplier Performance consists of the following process steps:

■ Create questionnaires

■ Define evaluation

■ Capture and consolidate internal data

■ Capture evaluation data from external sources

■ Analyze supplier performance

You can find a process description in SAP Solution Manager under <project name> Scenarios Supplier

Evaluation Business Processes Evaluation and Monitoring of Supplier Performance . Select the Documentation tab.

3.1.1 Supplier Evaluation

In recent years, the importance of a generic evaluation tool within collaborative scenarios has increased

as a result of the need for customers to reduce procurement costs, enhance and optimize collaboration,

and globalize procurement activities. This is possible with Supplier Evaluation, which can help you,

for example, to optimize your supply base and improve the relationships with your suppliers.

Process

1. Creating Questionnaires

The Supplier Evaluation process starts with creating questionnaires. For this, a tool called the Web

Survey Cockpit, which allows the customer to define and maintain Web-enabled questionnaires, is

available in the application basis. In the Web Survey Cockpit, users can select the criteria they want to

evaluate (for example, delivery reliability and quality). They can define different types of questions (for

example, single choice, multiple choice, or free-text answers). They can also determine when the

evaluation is to occur.

The Web Survey tool can be accessed from both SAP SRM and SAP NetWeaver Business Intelligence

(SAP NetWeaver BI). The questionnaire data, as well as the responses, are updated in the delta structures

and extracted into SAP NetWeaver BI.

SAP supports two main methodologies for Supplier Evaluation:

■ Event-driven evaluation, triggered from confirmation, invoice, and advanced supplier list




2011-11-08 PUBLIC 37/64

2. Event-Driven Evaluation

The questionnaires are included in the SAP SRM processes, and can be filled out when a document

(confirmation, invoice) is processed. For this purpose, a new browser window opens up.

3. Ad-Hoc Surveys Using the Supplier Survey Cockpit

Supplier Survey Cockpit is a new function in SRM 2007 SP03.The user can create ad-hoc surveys by

using the Supplier Survey Cockpit. Suppliers and questionnaires are assigned to a survey, which is

distributed via e-mail to selected participants. The Supplier Survey Cockpit is available in SAP SRM

only.

NOTE

You can also perform ad-hoc evaluation using the Web Survey tool through SAP NetWeaver BI.

Here, you can rate confirmations and invoices, and the overall performance of your suppliers on

product or product category level. The benefit is that purchasing documents from multiple

systems can be accessed and rated. This rating is, however, done offline and requires the extraction

of data from the source systems to SAP NetWeaver BI. The evaluation is done using reports

specifically prepared for supplier evaluation

4. Grouping and Weighting

In SAP NetWeaver BI, it is possible to assign the questions to different groups, allowing the user to

analyze different performance areas such as delivery, and quality, for example. The groups can also be

assigned a weight, dependent on their importance.

5. Consolidating and Analyzing Data

When the data has been extracted from SAP NetWeaver BI delta structures into SAP NetWeaver BI, and

updated with grouping and weighting, this information is available for analysis in SAP NetWeaver BI.

The survey data from the Supplier Survey Cockpit on the one hand and from the event-driven surveys

on the other hand are extracted to different DataStore Objects and InfoCubes.

Many reports are available directly from the SAP SRM application, and the user does not need to log

on to SAP NetWeaver BI (though a user for the SAP NetWeaver BI system is required). Supplier

performance results can be accessed also from various processes, for example, a user can view evaluation

scores when determining which bidders to invite for an RFx. The reports available depend on the role

the user has in the SAP SRM context.

3.1.2 More Information About Evaluating and Monitoring of Supplier Performance

For more information, see SAP Help Portal at http://help.sap.com under:

■ SAP Supplier Relationship Management Functions Analytics Supplier Evaluation Event-Driven

Evaluation



38/64 PUBLIC 2011-11-08

http://help.sap.com

■ SAP Supplier Relationship Management Functions Analytics Supplier Evaluation Ad-Hoc Evaluation:

Supplier Survey Cockpit

3.1.3 Defining Questionnaires with Web Survey Cockpit

You use SAP Web Survey Cockpit to create questionnaires for Supplier Evaluation. One questionnaire

can be reused, and used in parallel for different surveys. There is one constraint. Questionnaires designed

for ad-hoc surveys (Supplier Survey Cockpit) cannot be used for the other types of evaluation

(confirmation, invoice and approved supplier list), and the other way around. The reason is that ad-

hoc survey uses different parameters than the other processes.

Three surveys and four questionnaires (in English and German) are shipped with Supplier Evaluation.

They can be deployed for the processes confirmation / invoice / approved supplier list:

■ Survey for supplier list with questionnaire for supplier list

■ Survey for confirmation with one questionnaire for goods receipt confirmation and another for

service entry

■ Survey for invoice with questionnaire for invoice

You can customize these predefined surveys and questionnaires to meet your needs, and you can also

create surveys and questionnaires of your own. There are no templates delivered for the ad-hoc surveys,

using the Supplier Survey Cockpit.

For more information on how to add more parameters to a questionnaire, see SAP Help Portal under

http://help.sap.com SAP NetWeaver <release> Library SAP Library SAP NetWeaver Library SAP

NetWeaver by Key Capability Application Platform by Key Capability Business Services Web Survey .

See also the documentation on the Supplier Survey Cockpit on SAP Help Portal under http://

help.sap.com SAP Supplier Relationship Management Functions Supplier Evaluation Ad-Hoc Evaluation:

Supplier Survey Cockpit.

The Web Survey Cockpit is part of the Basis SAP_ABA 6.20 SP1 and available with functions for Supplier

Evaluation only on SP18 and higher. It is required to have SAP GUI installed.

Procedure

Event-Driven Surveys

1. The transaction for the creation of event-driven questionnaires is accessed from Customizing using

SAP GUI whereas ad-hoc surveys, using the Supplier Survey Cockpit, are accessed from a link in

the portal.

To create surveys and questionnaires, make the necessary settings in Customizing for Supplier

Relationship Management (SRM) under SRM Server Integration with Other mySAP Components Data

Transfer to the SAP Business Information Warehouse Settings for Application-Specific DataSources (SRM) Web

Survey Cockpit for SRM Supplier Evaluation .



2011-11-08 PUBLIC 39/64

http://help.sap.com

http://help.sap.com

http://help.sap.com

NOTE

You can also use transaction code BBP_EVAL_SURVEY to access the Web Survey Cockpit.

2. To create a Web survey, choose Survey Create from the menu. The name and the identifier can

be chosen freely. The survey credentials are not used for calling up the questionnaire later on, but

are helpful for categorizing the different questionnaires.

3. After having saved a survey for the first time, you can add a new target group for mass data to its

target group hierarchy. No additional user information (e-mail, user) is needed here, because user

information is added to the questionnaire at runtime.

4. To create a questionnaire, choose the Questionnaire pushbutton.

NOTE

When saving the questionnaire for the first time, you can also define a name and an identifier.

The identifier is used when the questionnaire is called with the URL in SAP SRM.

The dependencies between the different elements in SAP Web Survey tool are as follows:

■ One survey CAN CONTAIN multiple questionnaires

■ One questionnaire CAN BELONG TO multiple surveys

■ One survey CAN HAVE multiple recipients

This reflects the possibilities given by the Web Survey Tool.

However, for usage in SAP SRM, we recommend the following setup:

■ 1 survey REFLECTS 1 scenario (invoice, confirmation (goods receipt), and so on)

■ 1 survey CONTAINS 1 questionnaire or multiple questionnaires (different versions for different

categories of one scenario)

■ 1 survey HAS 1 recipient (target group for mass data)

Ad-Hoc Surveys Using the Supplier Survey Cockpit

To create questionnaires for ad-hoc surveys using the Supplier Survey Cockpit, select Create

questionnaire from your portal landscape. An SAP GUI session opens with the transaction for questionnaire

creation.

There is a slight difference in how to create the questionnaire for event-driven surveys compared to

ad-hoc surveys. For event-driven surveys, the complete functions of SAP Web Survey must be used,

and it is necessary to create a survey to “wrap” the questionnaire. For ad-hoc survey, the user only

creates the questionnaire, without the survey functions delivered with SAP Web Survey tool.

Event-Driven and Ad-Hoc Surveys

CAUTION

■ Each question (criterion) must have a different question ID, regardless of which questionnaire

it belongs to. If you use supplier evaluations in a multi-system landscape, you must make

sure that the question IDs are unique across all of these systems. This ensures that each

question is unique and can be identified in the SAP NetWeaver BI reports.



40/64 PUBLIC 2011-11-08

■ Do not forget to change the Reporting Text when you create a new question. Otherwise you

only see the default descriptions like Question 1 when you analyze suppliers.

■ The scale of valuations has to be similar across all questionnaires, for example, 0 to 100.

■ You define the possible valuations of each question (option) in the option definition. Click

the right-hand mouse button on Option and choose Change Attributes.

■ Input fields, dropdown boxes, and radio buttons are possible options for the supplier

evaluation. Checkboxes and free-text-entries can not be reported on in SAP NetWeaver BI.

■ The Web Survey Cockpit offers the possibility to define weightings in the option definition.

In the scenario described in this configuration documentation, however, you define

weightings and groupings exclusively in SAP NetWeaver BI.

3.1.4 Content of SAP SRM Questionnaires

There are two main SAP SRM processes:


■ Event-driven surveys:

● Invoice

● Confirmation

● Approved supplier list

Invoice, confirmation, and approved supplier list are reflected in the three SAP SRM standard

questionnaires. They are examples that you can modify or use as a basis for creating your own. The

parameters available in the questionnaires are fixed and cannot be modified.

For ad-hoc surveys, the parameters are derived from information from the survey created in the

Supplier Survey Cockpit. They are partly different from the parameters of the event-driven

questionnaires. SAP has defined the following parameters to be used according to your needs in the

questionnaires.

Handling of "No Response"

There might be questions, which the survey participant is not able to answer. Therefore we recommend

that you give the option "no response" or "do not know" as an answer. In order for SAP NetWeaver BI

to handle these answers correctly in the calculation of scores, this option must be assigned a rate of -1.

If the option is assigned any other weight, such as 0, the calculation in SAP NetWeaver BI might, under

certain circumstances, be incorrect.

Supplier Survey Cockpit (Ad-Hoc) Questionnaire

You can add parameters to the questionnaire to provide the user with the business context in which

he or she evaluates. These parameters are later visible on the header when for example previewing the

questionnaire.

The following tables show the parameters that can be added to a questionnaire as context data:



2011-11-08 PUBLIC 41/64

Survey Field Technical Name Visible

Survey ID SURVEY_ID Yes

Survey Name SURVEY_NAME Yes

Supplier ID SUPPLIER_ID Yes

Supplier Name SUPPLIER_NAME Yes

Evaluation Period EVAL_PERIOD Yes

Invoice Questionnaire

To maintain the Invoice questionnaire, update an invoice in SAP Supplier Relationship Management

(SAP SRM). The questionnaire should contain the following context data in the form of parameters:

Description Tech. Name Visible

PO number PO_NUMBER yes

PO Item number PO_ITEM_NO yes

Document type OBJECT_TYPE yes

Invoice number OBJECT_ID yes

Invoice GUID OBJECT_GUID no

Invoice description OBJECT_NAME yes

Invoice item number ITEM_NUMBER no

Invoice item GUID ITEM_GUID no

Invoice date POSTING_DATE yes

Supplier ID VENDOR_ID yes

Supplier name VENDOR_NAME yes

Purchasing Organization ID PROC_ORG_ID yes

User ID UNAME no

Logical EBP system ID BBP_LOG_SYSTEM no

Category ID CATEGORY_ID yes

Category GUID CATEGORY_GUID no

Category text CATEGORY_NAME yes

Product source system ID PROD_SRC_SYS no

Product ID PRODUCT_ID yes

Product GUID PRODUCT_GUID no

Product text PRODCUCT_NAME yes

Location ID LOCATION_ID no

User Full Name UFULLNAME no

Confirmation Questionnaire

To maintain the Confirmation questionnaire, update a confirmation in SAP SRM. The questionnaire

should contain the following context data in the form of parameters:


PO number PO_NUMBER yes



42/64 PUBLIC 2011-11-08

PO Item number PO_ITEM_NO yes

PO name PO_NAME yes

Document type OBJECT_TYPE no

Confirmation number OBJECT_ID yes

Confirmation GUID OBJECT_GUID no

Confirmation description OBJECT_NAME yes

Confirmation item number ITEM_NUMBER no

Confirmation item GUID ITEM_GUID no

Confirmation date POSTING_DATE yes



Service provider ID SRVPROV_ID yes

Service provider name SRVPROV_NAME yes


User ID UNAME no





Product source system ID PROD_SRC_SYS no



Product text PRODUCT_NAME yes

Location ID LOCATION_ID no


Approved Supplier List Questionnaire

To maintain the approved supplier list questionnaire, update a supplier list in SAP SRM. The questionnaire

should contain the following context data in the form of parameters:


Document type OBJECT_TYPE no

Supplier list number OBJET_ID yes

Supplier list GUID OBJECT_GUID no

Supplier list description OBJECT_NAME yes




User ID UNAME no





2011-11-08 PUBLIC 43/64






Product text PRODUCT_NAME yes

Questionnaire URL

As soon as a questionnaire is saved in the Web Survey Cockpit, the URL is accessible by clicking a button

in the survey application.

Multilingual Capability

When creating questionnaires, you can define a language code for each recipient. To ensure that the

questionnaires are sent in the correct language, you must first save the newly created questionnaire.

You can then translate the texts in transaction SE63. The object names of all questionnaires start

with ?SURVEY?. You can use the wildcard (*) to find them.

CAUTION

Do not translate a questionnaire that is still subject to change. The translation is deleted when

the questionnaire is changed and saved another time.

If you have not created any translated texts, the system will use the language in which the questionnaire

was created, independently of the receiver's defined language code.

Also note that the fields filled in by a recipient will not be translated.

3.1.5 Definition of Parameters and Valuation Levels

NOTE

This section is not valid for ad-hoc surveys using the Supplier Survey Cockpit.

To perform a supplier evaluation in SAP Supplier Relationship Management (SAP SRM), you must

enter certain parameters. You do this in Customizing under Integration with Other SAP Components Data

Transfer to SAP NetWeaver Business Intelligence Settings for Application-Specific DataSources (SRM) Define Events

for Supplier Evaluation .

You have to enter the following parameters:

■ Where? This determines where you want the Web Survey and questionnaires to appear, in other

words, the SAP SRM transaction category you want to evaluate: confirmation, invoice, or approved

supplier list.



44/64 PUBLIC 2011-11-08

NOTE

You can evaluate your suppliers based on operational SAP SRM confirmation and invoice

documents, or on a more global level from the supplier list, or using ad-hoc surveys.

■ What? What parameters do you want to evaluate? You can choose from: supplier, purchasing

organization, product category, source system, and product. You can enter specific values or

generic patterns. For the selection of specific values, use the input help. (Parameters for ad-hoc

surveys are maintained differently. They are directly derived from the specific survey.) Any

parameter that has no input is not transferred to SAP NetWeaver Business Intelligence (SAP

NetWeaver BI).

NOTE

The source system is only required when there are multiple back-end systems with

unconsolidated master data. Otherwise, the source system is automatically filled by category

or product assignment. This is not applicable for ad-hoc surveys.

■ How? With which method and, where applicable, with which probability do you want to evaluate?

The following parameters control when and how often the evaluation is to occur:

● Individual: the evaluator needs to click on a button to access and answer a questionnaire

● Always – when saving: the questionnaire pops up automatically when the document is saved

● Random – when saving: the questionnaire stochastically pops up automatically when the

document is saved

If you select Random – when saving, you must assign a probability, too (for example, in only 50% of

cases, or every other time data is saved).

■ Which? Which Web Survey and which questionnaire are to be called under the defined

circumstances? The Web Survey can be determined automatically from the questionnaire you have

chosen; but a questionnaire can occur in multiple Web Surveys. In some cases, you might have to

assign the Web Survey manually.

NOTE

There are two aspects to bear in mind during the maintenance of supplier evaluation parameters:

■ Control – defining the parameters, you set up conditions that control the appearance

(where, what, how and which) of questionnaires.

■ Valuation – defining the parameters, you also set up the level of analysis in SAP NetWeaver

BI. If you leave a parameter empty, it is not available in SAP NetWeaver BI, even if it has a

value in the SAP SRM document.

PrerequisitesYou have defined your own Web Survey and questionnaires (see Defining Questionnaires with Web Survey

Cockpit [page 39]).

ExampleThe following examples illustrate how questionnaire determination works.



2011-11-08 PUBLIC 45/64

Example: Questionnaire Determination I (Example for Confirmation)

Figure 11:

NOTE

For questionnaire determination control, it is irrelevant, whether a parameter is empty or filled

with ‘*’. The distinction between empty and ‘*’ is only relevant for the valuation level of analysis

in SAP NetWeaver BI.

In this example, questionnaire SRM_CONF_1 appears independently of the supplier, purchasing

organization, category, source system, and product ID because of the ‘*’. If a confirmation contains

several product IDs, then questionnaire SRM_CONF_1 appears only once for each product ID. If

you process a confirmation with two different product IDs, this means that you have to fill out

the questionnaire twice.

Example: Questionnaire Determination II (Example for Confirmation)

Figure 12:

NOTE

In this example, you cannot perform the SAP NetWeaver BI analysis based on the product category

or on the product itself (see the note above).

As you can see, if you do not make any entry for a certain parameter at all, it makes a large difference

to entering the star symbol: Even with different product IDs in a confirmation you have to fill in

questionnaire SRM_CONF_1 only once. The product ID – as well as the category and source

system in example Questionnaire Determination 2 - are not even transferred to SAP NetWeaver

BI.

NOTE

In questionnaire determination, the SAP SRM document parameter (for example, the identifier

of category or product) is matched with the customizing parameter pattern. The comparison is

not case-sensitive. The customizing pattern can contain ordinary characters and wildcards. ‘*’

stands for any character string and ‘+’ denotes any character. The character ‘#’ serves as a control

character and indicates that the very next character should be compared exactly.

This facilitates a search for:

■ Characters in upper or lower case, for example ‘#A#b*’

■ The wildcard characters ‘*’, ‘+’ themselves, for example ‘*#**’ or ‘*#+*’



46/64 PUBLIC 2011-11-08

■ The escape symbol itself, for example ‘*##*’

■ Blanks at the end, for example ‘*# ‘

3.1.6 Defining Questionnaires with Web Survey Cockpit in SAP NetWeaver BI

Supplier Evaluation uses the Web Survey Cockpit to perform manual evaluations within SAP

NetWeaver BI. Users can evaluate supplier performance related to individual SAP SRM confirmations

and invoices, as well as SAP ERP goods receipts. They can also give an overall rating for a supplier.

In SAP NetWeaver BI, you can define surveys for the individual events that trigger questionnaires

(approved supplier list, invoice, confirmation / goods receipt) and, within such a survey, one or multiple

questionnaires (for example, different questionnaires for different types of invoices, and so on).

For more information about the Web Survey Cockpit, see SAP Help Portal at http://help.sap.com

under SAP NetWeaver <release> Library SAP Library SAP NetWeaver Library SAP NetWeaver by Key

Capability Application Platform by Key Capability Business Services Web Survey .

NOTE

Ad-hoc surveys using the Supplier Survey Cockpit CANNOT be created in SAP NetWeaver

Business Intelligence (SAP NetWeaver BI). They are only applicable for SAP SRM. The grouping,

weighting, and the analysis of ad-hoc surveys still takes place in SAP NetWeaver BI.

Prerequisites

The Web Survey Cockpit is part of the Basis SAP_ABA 6.20 SP1 and available with functions for Supplier

Evaluation only on SP18 and higher.

Procedure

The dependencies between the different elements in a survey are as follows:

■ One survey CAN CONTAIN multiple questionnaires.

■ One questionnaire CAN BELONG TO multiple surveys.

■ One survey CAN HAVE multiple recipients.

RECOMMENDATION

We recommend that you create a survey for each Supplier Evaluation event (approved supplier

list, invoice, confirmation / goods receipt) you want to implement. However, these surveys are

only used for structuring your questionnaires; they are not available for use in later evaluations.

NOTE

SAP delivers four exemplary questionnaires (Supplier Evaluation, Service Evaluation, Goods

Evaluation, and Invoice Evaluation) in XML format. Each questionnaire is also available for

Unicode-based systems. You can load these questionnaires into Web Survey Cockpit and use them



2011-11-08 PUBLIC 47/64

http://help.sap.com

as they are, or modify them. You find the questionnaires on the SAP Service Marketplace at

service.sap.com/ibc-srm under Spend Analysis and Reporting in SRM.

Of course, you can also define your own questionnaires.

Creating Surveys and Questionnaires

1. In Customizing for SAP NetWeaver Business Intelligence (SAP NetWeaver BI), choose SAP Net

Weaver Business Intelligence Settings for Business Content Supplier Relationship Management Supplier

Evaluation – Define Questionnaires .

NOTE

You can also use transaction code SRM_VE_SURVEY to access the Web Survey Cockpit for

Supplier Evaluation.

2. Entering the Web Survey Cockpit for Supplier Evaluation, you first have to specify the OLTP system,

for which the questionnaire is used. Choose ‘*’ if you want questionnaires to appear independent

of the OLTP system a supplier or document was created in and uploaded from into SAP NetWeaver

BI.

3. To create a Web Survey, choose Survey Create from the menu. The name and the identifier

can be chosen freely. The survey credentials are not used for calling up the questionnaire later on,

but are helpful for categorizing the different questionnaires.

4. After having saved a survey for the first time, you have to add a new target group for mass data to

its target group hierarchy. The target group has to be defined to be able to open the questionnaire

for evaluation later on. No additional user information (e-mail, user) is needed here, because user

information is added to the questionnaire at runtime.

5. Next, you can start to add questionnaires to the survey. For example, you can provide a

confirmation survey with one questionnaire for goods confirmation and one questionnaire for

service confirmation. If you want different questions to be answered for different products, services

or suppliers, you can also define different questionnaires for them.

NOTE

Be aware that Supplier Evaluation can only report on simple questions. Question tables are

not reported on properly!

■ Supported question types: Input fields, dropdown boxes, and radio buttons are possible

options for the supplier evaluation. Checkboxes and free-text-entries can not be reported

on in SAP NetWeaver BI.

■ Specifying criteria: Every question (criterion) must have a different question ID,

regardless of which questionnaire it belongs to. If you use supplier evaluations in a multi-

system landscape, you must make sure that the question IDs are unique across all of

these systems. This ensures that each question is unique and can be identified in the SAP

NetWeaver BI reports.



48/64 PUBLIC 2011-11-08

■ Reporting Text: Do not forget to change the “Reporting Text” when you create a new

question. Otherwise you only see the default descriptions like “question 1” when you

analyze suppliers.

■ Valuations: In the standard, Supplier Evaluation uses a scale of scores from 1 to 100,

where 1 is the lowest score and 100 the highest. A score of 0 stands for “no answer” and

does not affect the supplier’s score. Creating a new questionnaire you can create a

different scale of valuations according to your preference (for example, 1 to 6). However,

the scale of valuations has to be defined similarly across all questionnaires. You define

the possible valuations of each question (option) in the option definition. Click the right-

hand mouse button on Option and choose Change Attributes.

■ Weightings: The Web Survey Cockpit offers the possibility to define weightings in the

option definition. In the scenario described in this documentation, however, you define

weightings and groupings exclusively in SAP NetWeaver BI.

■ Parameters: You can add parameters to the questionnaire to provide the user with the

business context in which he or she evaluates. For more information about parameters,

see below.

■ Multilingual support: See section Content of SAP SRM Questionnaires [page 41].

■ When saving the questionnaire for the first time, you can define a name and an identifier.

The latter is used when calling the questionnaire via URL in the evaluation process.

Loading Predefined Questionnaires

1. Perform steps 1-4 from the procedure described above.

2. Click on the icon with quick info Create New Questionnaire.

3. Position your cursor on the top node of the questionnaire.

4. Click the right-hand mouse button on the top node and choose Favorites Management Import

Favorites .

5. Navigate to the folder where you have saved the exemplary questionnaires and select the

questionnaire you want to upload.

6. The questionnaire is now available in Web Survey Cockpit. To include it into your web survey,

choose Insert from Favorites.

3.1.7 Defining Questionnaire Determination

To perform a supplier evaluation in SAP Supplier Relationship Management (SAP SRM), you must

define in which business context (that is, for which scenario, for which products or categories, and so

on) and by whom a certain questionnaire shall be filled out.



2011-11-08 PUBLIC 49/64

NOTE

Ad-hoc surveys using the Supplier Survey Cockpit CANNOT be performed in SAP NetWeaver

Business Intelligence (SAP NetWeaver BI). Therefore, it is not relevant to create questionnaires in

SAP NetWeaver BI for those types of surveys. They are only applicable for SAP SRM. The grouping,

weighting, and the analysis of ad-hoc surveys still take place in SAP NetWeaver BI.

Prerequisites

■ You have defined your own Web Survey and questionnaires (see Defining Questionnaires with Web Survey

Cockpit [page 39]).

■ You have loaded the master data. In the Customizing transaction, input help of all fields accesses

the SAP NetWeaver BI master data of the corresponding InfoObject.

Procedure

You define the questionnaire determination in Customizing for SAP NetWeaver Business Intelligence

(SAP NetWeaver BI) under SAP Net Weaver Business Intelligence Settings for BI Content Supplier Relationship

Management Supplier Evaluation – Determine Questionnaires .

You have to enter the following parameters:

■ What? What do you want to evaluate? You can choose from: supplier, purchasing organization,

product category, and product. You can either enter a specific value or make the entry applicable

for all values by leaving the field empty or entering a ‘*’. We recommend that you use the input

help for the selection of specific values.

NOTE

There is an important difference between no input and ‘*’, even though they seem to mean

the same at first sight. The settings directly affect the number of questionnaires displayed for

evaluation of a document or supplier, as well as the possibilities of the analysis of supplier

scores later on. See examples below for more information.

■ Obligatory or optional? Should the evaluation be optional or obligatory?

You can choose between Always obligatory or Determined by stochastic methods.

If you choose the latter, you must assign a probability, too. For example, if you enter a probability

of 50%, only every second document that is uploaded into SAP NetWeaver BI is marked as obligatory

for evaluation. See examples below for more information.

■ Which business transaction? This determines for which business transaction category the

current entry is defined: confirmation, invoice, or approved supplier list.

■ Which system? For which OLTP system should the entry apply? Similarly, you have already defined

different questionnaires for different OLTP systems in Web Survey Cockpit, or you have defined

questionnaires for a ‘*’ system.

■ Which questionnaire? Which Web Survey and which questionnaire are to be called under the

defined circumstances? Using input help you can access all questionnaires that are defined in the

system, no matter what OLTP system or survey (scenario) they were defined for.



50/64 PUBLIC 2011-11-08

NOTE

It is important that you only add questionnaires, which were defined for the system that you

chose for the Customizing entry. For example, if you created a survey and questionnaire for

system EB, you should only assign it to a Customizing entry that applies for system EB. If you

created questionnaires for the ‘*’system, you should only assign them to Customizing entries

for the ‘*’system. Otherwise, you face problems during the analysis of scores later on.

■ By whom? Which role in your company is supposed to fill out the questionnaire under the defined

circumstances?

NOTE

If you want different roles (for example purchasing and quality management) in your

company to evaluate a supplier or document, you can define several customizing entries that

only differ in the entry for the role.

The use of evaluation roles also allows you to mix the offline evaluation scenario (in SAP

NetWeaver BI) with the online evaluation scenario (in SAP SRM). For example, you can enable

accountants or recipients to evaluate online when they enter an invoice or confirmation in

SAP SRM. At the same time, you can enable quality management and purchasers to answer

other important questions offline at the end of the week.

■ Default user? Here you can enter the user (assigned to the role entered above) who evaluates.

This information can be used later to inform this user, for example by e-mail, about new evaluations

he or she is responsible for. He or she is also able to control how many evaluations he or she still

has to perform. You can also enter a manager here, who is responsible for dispatching and

controlling the evaluation process.

Examples

The following examples illustrate how questionnaire determination works. In all examples, you want

to evaluate the following confirmation 1234:

Item Supplier Purch.Org. Prod.Categ. Product …

10 1000 O 5016 4711 100 …

20 1000 O 5016 4711 200 ...

30 1000 O 5016 4711 300 ...

40 1000 O 5016 4712 400 ...

Customizing Example 1

Transaction Type Supplier Purch. Org. Prod. Categ. Product Probability Questionnaire

Confirmation * * * * 100% SRM_CONF

This setting means that you want to evaluate all confirmations with the same questionnaire,

independent of the information about supplier, purchasing organization, product category, and

product on item level.



2011-11-08 PUBLIC 51/64

For confirmation 1234, you have to fill in the following questionnaires:

Questionnaire Supplier Purch. Org. Prod. Categ. Product

SRM_CONF 1000 O 5016 4711 100

SRM_CONF 1000 O 5016 4711 200

SRM_CONF 1000 O 5016 4711 300

SRM_CONF 1000 O 5016 4712 400

NOTE

The meaning of ‘*’: The entry is used for all values. But evaluations have to be performed

individually, that is, the questionnaire has to be filled in again for each value. Advantage: In

analysis of scores later on, you can report on the individual values and access all evaluations in

detail. Disadvantage: When evaluating, for example, confirmations that contain many different

products, the user has to spend a long time filling-out questionnaires.

Customizing Example 2:

Transaction Type Supplier Purch. Org. Prod. Categ. Product Probab. Quest.

Confirmation * * * (no input) 100% SRM_CONF

This setting means the same as the example above: You want to evaluate all confirmations with the

same questionnaire, independent of the information about supplier, purchasing organization, product

category, and product on item-level.

But this time, you have to fill only two questionnaires for confirmation 1234:

Questionnaire Supplier Purch. Org. Prod. Categ. Product

SRM_CONF 1000 O 5016 4711 -

SRM_CONF 1000 O 5016 4712 -

NOTE

The meaning of no input: The entry is used for all values. But evaluations have to be performed

only once, that means, for equal values only one questionnaire is displayed. Advantage: Fast fill-

in process. Disadvantage: In our example you are not able to report on product level because

only one evaluation with empty product is transferred to SAP NetWeaver BI. You do not have

information on which and how many products have been evaluated in the process.

The same goes for suppliers, purchasing organizations and product categories if no input has been

made.

Customizing Example 3:


Confirmation * * 4712 * 100% SRM_CONF2



52/64 PUBLIC 2011-11-08


Confirmation * * 4711 - 50% SRM_CONF1

Confirmation * * 4711 100 100% SRM_CONF1

This setting means that you want to evaluate confirmations with product category 4712 with

questionnaire SRM_CONF2.

Confirmations with product category 4711 on the other hand are evaluated with questionnaire

SRM_CONF1. Since the probability setting is 50%, only every second confirmation with product

category 4711 is indicated for obligatory evaluation, the others are marked as optional.

However, the special setting for product 100 of this product category causes all confirmations with this

product to be marked for obligatory evaluation.

NOTE

In standard Supplier Evaluation, you always evaluate entire documents. Depending on what is

specified at item level for the product and product category, it is possible to determine several

questionnaires for filling out. For this reason, the administrative data for the supplier evaluation

is stored at item level.

For confirmation 1234, you have to fill out the following questionnaires:

Questionnaire Supplier Purch. Org. Prod. Categ. Product Obligatory

SRM_CONF 1000 O 5016 4711 100 X

SRM_CONF 1000 O 5016 4711 - -

SRM_CONF 1000 O 5016 4712 400 X

NOTE

If you want to override the result of the standard questionnaire finding, you can modify the update

rules from the source DataStore objects to the administrative DataStore objects of Supplier

Evaluation (see Loading Transaction Data [page 19]).

3.1.8 Execution of Evaluations in SAP NetWeaver BI

This section explains the evaluation process for Supplier Evaluation for offline evaluations using SAP

NetWeaver Business Intelligence (SAP NetWeaver BI).

Prerequisites

You have prepared the SAP NetWeaver BI system for evaluations.

Procedure

In SAP NetWeaver BI, you can evaluate suppliers (in general, by product category, or by product) as

well as confirmations, goods receipts, and invoices (on document-level). You perform these evaluations



2011-11-08 PUBLIC 53/64

offline after they have been entered in the OLTP system and uploaded to the SAP NetWeaver BI system.

The users who are to evaluate a supplier or document receive a worklist with all obligatory evaluations

in a given time frame. This worklist can be accessed via the ERP role menu, a URL, or can be directly

sent to a user via e-mail.

The worklists are provided as SAP NetWeaver BI Web templates. These templates via InfoSets join the

DataStore Objects that hold the transaction data (purchase orders, confirmations / goods receipts,

invoices), the administrative DataStore Objects for Supplier Evaluation (information about

questionnaires that are to be called for the document) and the transactional DataStore Objects for

Supplier Evaluation (data about already evaluated documents or suppliers). All this information is

processed to provide the user with worklists that display the documents he or she must / can evaluate,

or has already evaluated, respectively. Additionally, information like the purchase volume is displayed.

NOTE

■ On the selection screen, it is always possible to restrict the worklists using certain criteria like

document number, supplier, purchasing organization, product category, and so on.

■ A user can only ever display and evaluate documents / suppliers that can be evaluated by the

role which he or she is assigned (see Defining Evaluation Roles and Attaching them to User IDs [page

18]).

■ It is possible that more than one user with the same role evaluates the same document or

supplier. In this case, each evaluation by another user is counted as a new evaluation for this

role.

■ If a user selects a document that they have already evaluated, they can only change their

prior evaluation. In contrast to that, if a user selects a supplier they have already evaluated,

they can decide whether they want to change an old evaluation, or if they want to create a

new one. In this way, users can perform a quarterly or yearly strategic evaluation of the

suppliers, for example.

The data flow from DataStore Objects to queries and to the Supplier Evaluation front-end is illustrated

in the figure below.

Figure 13:

The user is able to switch between several views of a worklist. When he or she evaluates suppliers, he

or she can switch between Evaluate suppliers by product category and a more detailed evaluation level, Evaluate

suppliers by product category and product.

In the section Defining Questionnaire Determination [page 49], you specified which suppliers shall be evaluated.

The evaluation of these suppliers is always obligatory.



54/64 PUBLIC 2011-11-08

For evaluation of documents, on the other hand, you can request the system to mark them as obligatory

or optional following stochastic methods. When a user evaluates confirmations or invoices, he or she

is therefore able to switch between obligatory or optional evaluations via the dropdown-box on top of

the screen. This function is especially useful if he or she wants to evaluate a certain confirmation or

invoice for a reason, even though the system marked it as optional.

The user can evaluate a document or supplier by clicking on the evaluation icon at the end of a work

item. This calls the Supplier Evaluation front end via URL. This front end is used for performing

evaluations.

When you evaluate documents, the worklist on the left of the screen shows all questionnaires that

must be evaluated for the previously selected document. Since one document can carry different

product categories and products, multiple questionnaires may be displayed in the worklist. How many

questionnaires are displayed depends on the settings you defined, see section Defining Questionnaire

Determination [page 49].

The traffic lights next to the questionnaires inform you about its evaluation status:

■ Red: Obligatory evaluation – not evaluated

■ Yellow: Optional evaluation – not evaluated

■ Green: Already evaluated

NOTE

Having selected an obligatory document for evaluation, you might see some obligatory and some

optional questionnaires in the worklist. This is because Supplier Evaluation decides individually

for each product and product category of a document, which questionnaire shall be filled in and

if the evaluation is obligatory or not.

A document is included in the worklist for obligatory evaluations as soon as at least one of its

products and product categories are marked for obligatory evaluation.

When you submit a questionnaire, your evaluation is stored on the database. From now on, the

questionnaire is displayed with a green light next to it. However, the document you evaluated remains

in the worklist for obligatory evaluations until all obligatory questionnaires (red light) are filled in

(green light).

Information about an evaluation is stored twice in the SAP NetWeaver BI system. First, the evaluation

and its parameters (the business context) are stored in the Web Survey database and can be extracted

into SAP NetWeaver BI itself later on for analysis of scores. Simultaneously, the transactional DataStore

Objects for Supplier Evaluation are updated with information that the questionnaire was filled out for

the selected document. This information also includes the user and the evaluation time. Two

transactional DataStore Objects exist for Supplier Evaluation:

■ 0SRVE_O1: Evaluation data for documents (transactional DataStore object)

■ 0SRVE_O2: Evaluation data for suppliers (transactional DataStore object)



2011-11-08 PUBLIC 55/64

3.1.9 Definition of Groupings in SAP NetWeaver BI

In the grouping transaction Supplier Evaluation — Grouping (SRM_VE_GROUPING) in SAP

NetWeaver BI, you can customize how evaluation criteria are grouped. Evaluation criteria can

correspond to questions in a questionnaire that was created in the source system, for example, SAP

Supplier Relationship Management (SAP SRM) or SAP NetWeaver Business Intelligence (SAP

NetWeaver BI). (These questions have subsequently been imported into SAP NetWeaver BI using

InfoObject 0WS_QSTN.) You can also group automatic criteria, if you have a connection to SAP ERP

Vendor Evaluation, or if you use the interface for integrating evaluations from external systems.

For more information, seeMaintaining the ERP Vendor Evaluation Enhancement [page 22] and Maintaining Common

Interface for External Evaluation System [page 23]. You can define up to four levels, three of which can be used

for defining groups. The fourth one is reserved for the ungrouped criteria (grouping level zero).

NOTE

The group levels are numbered from three on the highest level – which directly affects the total

score – down to one on the most detailed level.

Prerequisites

You have loaded the master data. For more information, see Loading Master Data [page 16].

Procedure

Grouping Levels

You can define how many levels to use for grouping. However, the definition of the grouping has a

direct effect on the display in the queries that are designed for using all four grouping levels. If you do

not use all levels, the queries contain groups marked with Not assigned.

RECOMMENDATION

We recommend that you either use all three grouping levels for your grouping definition, or

change the queries and omit the respective grouping levels in the query definition.

System-Specific Grouping

Supplier Evaluation supports scenarios with multiple OLTP systems. Therefore, you can group the

criteria in two ways, either globally for all systems, or system-specific for particular systems. On the

upper part of the screen, you have to enter a source system. You have the following options:

■ ‘*’ for the global definition

In this case, all questionnaires and assigned criteria are displayed.

■ The two-character name of the questionnaire/criteria source system

In this case, only questionnaires and assigned criteria that have been defined in the particular system

are displayed.

To prevent mistakes during grouping, criteria can be assigned to a distinct group within a grouping.



56/64 PUBLIC 2011-11-08

NOTE

All criteria must be assigned to at least one grouping. If ungrouped criteria exist, a warning is

displayed in Monitoring after the Supplier Evaluation InfoCube is updated.

RECOMMENDATION

If you connect Supplier Evaluation to just one OLTP system, we recommend that you define a

global grouping instead of a system-specific grouping. In this way, you can be sure that all Supplier

Evaluation queries can be used properly. For example, the Supplier Portfolio only allows a global

analysis that includes all OLTP systems.

If you use Supplier Evaluation with multiple OLTP systems, you should also define a global

grouping, and, if the need arises, additional groupings for single systems.

For further recommendations, see the Example section below.

Example

You can choose how many groups you define and how you define the path, on which criteria values

are aggregated on the single levels and finally into the total score. As mentioned above, the only

restriction is that you use four levels.

The example shows how a grouping could be defined:

In the example, you can see several specific uses for groups:

Figure 14:

■ Combine groups or criteria for generalization:

In our example, the groups Quality and Handling are combined into the more general group Procurement

Criteria. This is the normal use of grouping.

■ Combine similar criteria from different questionnaires:

In our example, the criteria Condition of Goods is defined in two questionnaires – once in the

questionnaire for goods receipts and once in the questionnaire for supplier lists. In this case, a group

called Quality of Goods is used to combine both these criteria. For this reason, there is a simulated

criterion at level 1. (Even though the criteria appear to be the same, in SAP NetWeaver BI they are

dissimilar, because they originate from two different questionnaires.) A criterion is unique only if

application (SRM_EVAL for Supplier Evaluation), questionnaire and criterion are provided.

A similar situation arises if you have defined special questionnaires for different products in the

source system. Normally, you find a question concerning the condition of the goods in every

questionnaire.

■ Dummy group on level:



2011-11-08 PUBLIC 57/64

In our example, the group Price is defined once at level 2 and once at level 1. No generalization

occurs between the two groups. The only reason there is a Price group on level 1 is that all provided

levels are filled out so that a score is visible on level 2 and 1 in the queries.

RECOMMENDATION

We recommend that you fully describe and validate your grouping model before you define it in

SAP NetWeaver BI and upload the Supplier Evaluation data. Subsequent changes in your model,

even minor ones, require great effort. For more information, see Change of Settings [page 33].

3.1.10 Definition of Weightings in SAP NetWeaver BI

In the weighting transaction, you define the weightings for the groupings that you identified during

the customizing of the groups.

PrerequisitesYou have defined groupings, see Definition of Groupings in SAP NetWeaver BI [page 56].

Procedure

Specific Weighting

You can define specific groups for individual OLTP systems. By defining weightings, however, you can

achieve even more specialization. In addition to the source system of the criteria, you have the choice

to specialize the weighting on special products, product categories, purchasing organizations, or

locations. This way you can weight criteria differently for individual product categories, for example.

The resulting “weighting views” are stored with special weighting keys.

RECOMMENDATION

We recommend that you define at least a general weighting (‘*’ in every field) for every grouping

that you defined in the first step. After that, you can define more special weightings, for example

for a particular product category, to which your general weightings do not apply. As an example,

for most of your products, timeliness could be important, but not crucial. For one special product

category, however, it is crucial, so you define a special higher weighting for timeliness. If your

purchasing organizations or locations have differing requirements for a supplier evaluation, you

can also define special weightings for them.

About Weights

There are no restrictions concerning weights (despite that they have to be numbers). Be aware that

you assign a relative weight. You do not have to specify percentages, or ensure that the sum of the

weightings is 100. The extent to which a criterion counts toward its superordinate group is determined

by the InfoCube update (see Update of Supplier Evaluation InfoCube [page 28]). Weights that you define for a

criterion or group specify only the rate with which it flows into the direct superordinate group. The

rate with which it flows into the total score is the product of all weights on the path to the total score.



58/64 PUBLIC 2011-11-08

If you have left out a grouping level in your model - for example, you have not defined a group on level

1 - be aware that criteria values flow into the next superordinate group on level 2.

NOTE

In our example of a grouping (see Definition of Groupings in SAP NetWeaver BI [page 56]), we could have

omitted the group Price at Level 1. The values for Terms of Payment would then have been included

in the Price group at Level 2 with a weighting of 1.

A zero weighting (see Procurement Criteria in the graphic) means the group or criterion and all

subordinate groups and criteria do not flow into the superordinate group.

Example Weighting

Figure 15:

Weighting Views

As mentioned above, “weighting views” on a system-specific grouping are created to weight global

criteria differently for individual product categories or products, for example. It can also be necessary

to create individual questionnaires for certain product categories or products that include special

criteria, which only make sense in this particular case. To be able to analyze these criteria, you have to

include all general and special criteria in one system-specific grouping.

Business Object-Specific Questionnaires

In Customizing, you can define questionnaires to appear for particular business objects, such as product

or product category. One purpose of this is to restrict the supplier evaluation process to just a few

important business objects. You always obtain proper supplier scores, if these business objects are

assigned to the same general questionnaire (because they can be answered for all your products and

product categories).

If you have defined separate questionnaires for goods and services, once again, you also have to model

this in SAP NetWeaver Business Intelligence (SAP NetWeaver BI).

Since there is no direct categorization for goods and services, we recommend the following method:

■ Use product categories to differentiate between goods and services.

■ Define different weightings for good and service product categories in SAP NetWeaver BI. If you

have more product categories for goods than for services, define the global weighting for goods,

and special weightings services. Proceed the other way around if you have more service product

categories.

You can also define special weightings for certain goods or services.



2011-11-08 PUBLIC 59/64

3.1.11 Supplier Evaluation: Available Queries

This document lists the predefined queries for Supplier Evaluation, delivered by SAP.

Prerequisites

■ You have performed all the steps necessary for general SAP NetWeaver BI configuration. See SAP

Solution Manager under <project name> Configuration SAP SRM <release> Basic Settings for SAP

SRM Basic Settings for Analytics .

■ All the business content for this scenario is installed and activated. For more information, see SAP

Solution Manager under <project name> Configuration SAP SRM <release> Basic Settings for SAP

SRM Basic Settings for Analytics Lists of Content Objects and Transactions .

Features

Query List


Alerting Vendor Evaluation 0SR_VE_C1_Q025

Analysis Report Score Calculation Step 2 0SR_VE_C1_Q014

Analysis Report Score Calculation Step 3 0SR_VE_C1_Q015

Analysis Report Score Calculation Step 3 (Flexible) 0SR_VE_C1_Q016

Analysis Report Score Calculation Step 3 Group 2 0SR_VE_C1_Q017

Analysis Report: Vendor Evaluation 0SR_VE_C1_Q013

Cobweb Diagram Vendor Scores 0SR_VE_C1_Q010

Compare Total Scores per Vendor 0SR_VE_C1_Q002

Compare suppliers and performance trends over the years 0SR_VE_C2_Q002

Comparison of Total Scores (SUS) 0SR_VE_C1_SUS_Q002

Evaluation Data on Document Level 0SR_VE_Q001

Evaluation of Vendor by Product Category 0SR_VE_M2_Q001

Evaluation of Vendor by Product Category and Product 0SR_VE_M2_Q002

Evaluation of the Criteria by Vendor (global) 0SR_VE_C1_Q020

Group Scores Level 1 0SR_VE_C1_Q011

Group Scores Level 2 0SR_VE_C1_Q012

Mandatory Evalns for Goods Receipts/Service Confirmations 0SRVE_IS2_Q001

Mandatory Evaluations for Invoices 0SRVE_IS1_Q001

Open Evaluations (Goods/Service Confirmations) 0SRVE_IS2_Q003

Open Evaluations (Invoices) 0SRVE_IS1_Q003

Optional Evalns for Goods Receipts/Service Confirmations 0SRVE_IS2_Q002

Optional Evaluations for Invoices 0SRVE_IS1_Q002

Outlier List Valuation Records 0SR_VE_C1_Q006

SUS: Cobweb Diagram Vendor Scores 0SR_VE_C1_Q021

SUS: Evaluation Data on Document Level 0SR_VE_SUS_Q001

SUS: Evaluation of Service Providers 0SR_VE_C1_SUS_Q005



60/64 PUBLIC 2011-11-08

Submitted Evaluations (Vendors) 0SR_VE_M2_Q003

Supplier Survey Cockpit: Evaluation 0SR_VE_C2_Q001

Trend Comparison of Vendors (Criteria Selection) 0SR_VE_C1_Q004

Total Eval. / Purch. Order Value of Vendor over Time 0SR_VE_M1_Q002

Trend Vendor (Total Score) 0SR_VE_C1_Q008

Trend Vendor to Average (Criteria Selection) 0SR_VE_C1_Q007

Valuation of Criteria (SUS) 0SR_VE_C1_SUS_Q001

Valuation of Criteria (with Result / SUS) 0SR_VE_C1_SUS_Q009

Valuation of Criteria per Vendor 0SR_VE_C1_Q001

Valuation of Criteria per Vendor (with Event) 0SR_VE_C1_Q009

Valuation of Service Provider 0SR_VE_C1_Q005

Vendor Evaluation Data with Category and Product 0SR_VE_Q002

Vendor Portfolio with PO Value and Overall Score 0SR_VE_M1_Q001

Vendor Valuation: Criteria Selection 0SR_VE_C1_Q003



2011-11-08 PUBLIC 61/64

Typographic Conventions

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

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ 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

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

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

EXAMPLE Keys on the keyboard

62/64 PUBLIC 2011-11-08

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2011 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, and PowerPoint 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, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle and Java are registered trademarks of Oracle.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.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 companySybase 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.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.

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

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/srm-inst

2011-11-08 PUBLIC 63/64

http://service.sap.com/srm-inst

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

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

supplier evoluation

Documents

sap erp

sap notes

sap netweaver bi302

sap enhancement package

preparation of evaluation

supplier evaluationbased

supplier evaluation73

supplier evaluation72