CUSTOMER

Document Version: DRAFT – 2016-12

Setting Up SAP Ariba Supplier Lifecycle and

Performance
Content

Getting started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
What is SAP Ariba Supplier Lifecycle and Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
The supplier request process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
The supplier registration process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
The supplier qualification process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
The preferred supplier management process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Key assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
SAP Ariba Supplier Lifecycle and Performance setup checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Understanding supplier management templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Commodity, region, and user combinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Documents: forms, questionnaires, and internal surveys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Tasks: form and questionnaire approvals and internal survey to do tasks. . . . . . . . . . . . . . . . . . . . . 15
Team: automatic assignment by commodity and region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
SAP Ariba Supplier Lifecycle and Performance default template configurations. . . . . . . . . . . . . . . . . . . 16
Best practices for fitting SAP Ariba Supplier Lifecycle and Performance projects into SAP Ariba
Supplier Lifecycle and Performance workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
General best practices for supplier management templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Best practices for supplier request templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Best practices for supplier registration templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Best practices for supplier qualification templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Best practices for preferred supplier management templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Where to find more information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Setting up Supplier Lifecycle and Performance users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
SAP Ariba Supplier Lifecycle and Performance user groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
How to add users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
How to edit users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Setting up supplier data integration with SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

About supplier data integration with SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Integration workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
MDG business functions for supplier data integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
How to define a replication model for supplier data integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
How to import the supplier management transports into SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
How to maintain table entries for SAP Ariba supplier management solutions. . . . . . . . . . . . . . . . . . . . . 34

Setting Up SAP Ariba Supplier Lifecycle and Performance

2 CUSTOMER Content
 How to set up SAP ERP credentials in Ariba. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Configuring the Direct Connectivity integration method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
How to configure SOAMANAGER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
How to install the SSL client certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Configuring the Mediated Connectivity integration method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Requirements for Mediated Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
How to configure the Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
How to configure SSL Certificate for Mediated Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
How to configure shared secret authentication for Mediated Connectivity. . . . . . . . . . . . . . . . . . . . 43
How to configure the proxy on SAP ERP systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
How to configure the proxy for single stack (Java only) instances for SAP Process Integration 7.3
and higher. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
How to create a configuration scenario on a single stack system. . . . . . . . . . . . . . . . . . . . . . . . . . . 45
How to create a configuration scenario on a dual stack system. . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
How to replicate Business Partner master data from SAP Ariba supplier management solutions . . . . . . .48
Customizing supplier master data integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
ABAP example code for processing incoming GenericCustomField data. . . . . . . . . . . . . . . . . . . . . . 51
How to create custom message mappings in SAP Process Integration. . . . . . . . . . . . . . . . . . . . . . . 52
Setting default supplier field values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Default_properties.csv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
How to set up supplier data synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
How to monitor errors in SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Monitoring integration errors in SAP Ariba supplier management solutions. . . . . . . . . . . . . . . . . . . . . . 56

Importing SAP Ariba Supplier Lifecycle and Performance data. . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Importing site master data for SAP Ariba Supplier Lifecycle and Performance. . . . . . . . . . . . . . . . . . . . 57
Assigning users to supplier processes by commodity and region. . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Defining preferred supplier levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
How to import your data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
How to import your translation data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Language values for defining translations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Importing SAP Ariba Supplier Lifecycle and Performance supplier data. . . . . . . . . . . . . . . . . . . . . . . . . 63
How to obtain existing Ariba supplier data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
How to import supplier data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
[Link]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
[Link]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
[Link]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
[Link]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
[Link]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
[Link]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
[Link]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
[Link]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Setting Up SAP Ariba Supplier Lifecycle and Performance

Content CUSTOMER 3
 Editing and publishing supplier project templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
How to create a new version of a template and enabling editing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Using the template Overview tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
How to publish project templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
How to update supplier-related projects to a new template version. . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Creating supplier forms, questionnaires, and internal surveys. . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

How to create a supplier form or simple questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
How to set up a targeted supplier questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
How to create a targeted supplier questionnaire segment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
How to create a supplier-related internal survey. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Adding content to a supplier form, questionnaire segment, or internal survey. . . . . . . . . . . . . . . . . . . . 89
How to add a section to a supplier form, questionnaire segment, or internal survey. . . . . . . . . . . . . . 89
How to add a question to a supplier form, questionnaire, or internal survey. . . . . . . . . . . . . . . . . . . 90
How to add a requirement to a supplier form, questionnaire segment, or internal survey. . . . . . . . . . 92
How to add an attachment to a supplier form, questionnaire segment, or internal survey. . . . . . . . . . 93
Supplier form, questionnaire, and internal survey question answer types. . . . . . . . . . . . . . . . . . . . . 94
Using visibility conditions to show or hide content based on answers. . . . . . . . . . . . . . . . . . . . . . . . . . 95
How to create a basic visibility condition in a form or questionnaire segment. . . . . . . . . . . . . . . . . . 96
How to create an advanced visibility in a form or questionnaire segment. . . . . . . . . . . . . . . . . . . . . 97
Expressions for advanced visibility conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Content examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
How to create a dropdown menu with predefined values on a supplier form or questionnaire. . . . . . . 99
How to automatically reject answers that don't fall within a limited range on supplier forms. . . . . . . 100
How to ask for a supplier certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
How to ask for a supplier's address and map the answer to the supplier database: method 1. . . . . . .102
How to ask for a supplier's address and map the answer to the supplier database: method 2. . . . . . 103
How to create a question that is only visible suppliers with green certifications. . . . . . . . . . . . . . . . 104
How to ask about preferred supplier levels using master data values. . . . . . . . . . . . . . . . . . . . . . . 105
How to add translations for form and questionnaire content names. . . . . . . . . . . . . . . . . . . . . . . . . . .106
Mapping form or questionnaire content to supplier database fields. . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Common supplier database field names for mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Adding project groups and team members to project templates. . . . . . . . . . . . . . . . . . . . . . . . . . 113

Adding project groups and team members to project templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Buyer category assignments versus team member rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Using buyer category assignments to add team members to project groups. . . . . . . . . . . . . . . . . . . . . 115
How to use buyer category assignments to add team members to project groups. . . . . . . . . . . . . . 115
Using team member rules to add project groups and team members. . . . . . . . . . . . . . . . . . . . . . . . . . 116
About team member rules files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Team member rules file templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Rule matching in projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Setting Up SAP Ariba Supplier Lifecycle and Performance

4 CUSTOMER Content
 How to create team member rules files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Hierarchical region example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
How to add team member rules to a template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
How to validate team member rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Setting up supplier form and questionnaire approvals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

About approval rules in project templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
About serial and parallel approvers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
About groups in approval flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Removing and adding approvers in task rounds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Using commodity and region assignments or team member rules for form and questionnaire
approvals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Example: how to create a conditional approval flow using commodity and region assignments
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
How to create or edit approval rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Limitations when Specifying Approvers in the Approvers or Reviewers Field. . . . . . . . . . . . . . . . . . 129
About the approval rules editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
How to create a simple approval rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
How to edit approval flows with the approval process diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Using approval rule conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
References to a condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Subconditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
How to define approval rule conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
How to add approvers in the approval rule editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
How to add approvers from approver lookup tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Types of approvers in approver lookup tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Approver lookup table field values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Approver lookup table examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Customizing SAP Ariba Supplier Lifecycle and Performance notifications. . . . . . . . . . . . . . . . . . 144

About customizing SAP Ariba Supplier Lifecycle and Performance notification templates. . . . . . . . . . . 144
How to customize email templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
How to add email template tokens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
How to add translated text to email notification templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
How to delete customized email templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
SAP Ariba Supplier Lifecycle and Performance notification reference. . . . . . . . . . . . . . . . . . . . . . . . . 149
Notifications related to supplier requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Notifications related to supplier registrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Notifications related to supplier qualifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Notifications related to preferred supplier status changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Issuing mass registration invitations to suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

How to issue a mass registration invitation to suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Setting Up SAP Ariba Supplier Lifecycle and Performance

Content CUSTOMER 5
 [Link]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Site configuration options for setting up SAP Ariba Supplier Lifecycle and Performance. . . . . . .154
Site configuration options for supplier contacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Setting Up SAP Ariba Supplier Lifecycle and Performance

6 CUSTOMER Content
Getting started

What is SAP Ariba Supplier Lifecycle and Performance [page 7]

Key assumptions [page 11]

SAP Ariba Supplier Lifecycle and Performance setup checklist [page 12]

Understanding supplier management templates [page 13]

SAP Ariba Supplier Lifecycle and Performance default template configurations [page 16]

Best practices for fitting SAP Ariba Supplier Lifecycle and Performance projects into SAP Ariba Supplier
Lifecycle and Performance workflows [page 18]

Where to find more information [page 22]

What is SAP Ariba Supplier Lifecycle and

Performance
SAP Ariba Supplier Lifecycle and Performance is a set of linked processes for managing suppliers from onboarding
to qualification to preferred supplier management. Category and supplier managers use 365° views of each
supplier to manage these processes and monitor suppliers in one place.

SAP Ariba Supplier Lifecycle and Performance offers:

● Defined, template-based processes for managing suppliers that scales easily to bring large numbers of
suppliers under management.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Getting started CUSTOMER 7
● A centralized supplier database with a complete vendor model, and native integration to SAP ERP.
● Built-in alignment with SAP Ariba procurement solutions, and Ariba Strategic Sourcing and Contract
Management Solutions to leverage supplier qualifications and preferred status in procurement and sourcing
activities.
● Supplier self-service through Ariba Network
● "Matrix"-based supplier management based on combinations of commodity categories and regions.
● A complete 360° supplier views for each supplier, where both data bout the supplier and all related supplier
management activities is centralized.

The supplier request process

Users in your company who want to work with new suppliers, such as procurement agents and people running
sourcing events, request the new supplier by filling out and submitting a supplier request.

The supplier request template determines:

● What information users add to the request.

● Which category or supplier managers approve the request.
● Whether other stakeholders at your company must also approve the request.
● Whether a denied request can be resubmitted.

Users create supplier requests from the Create menu on the dashboard. The category or supplier managers
assigned to the supplier review the request, approve or deny it, and monitor the approval flow and status in the
supplier's 360° profile on the Supplier Management tab of the dashboard.

Notifications let the approver know that the request requires approval, let the requesting user know when the
request has been approved or denied, and show the final approver so that requesting users can have further
discussions about denied request.

When a supplier request is approved, the supplier is added to the Ariba supplier database. Integration settings
determine when the supplier is added to your ERP vendor master list, at which point your company's users can
begin creating requisitions for the supplier, adding them to sourcing events, and so forth; one of the options is
after the request has been approved.

The supplier registration process

After the request for a supplier has been approved, a category or supplier manager assigned to the supplier invites
the supplier contact to register and sends them a registration questionnaire, reviews the supplier's answers, and
approves or denies the registration.

The registration process typically solicits basic profile information from the supplier; for example, what
commodities they supply, the regions in which they operate, whether they have certifications in broad categories
such as diversity, whether they will agree to a code of conduct, and so forth. It can also include internal questions
that allow supplier or category managers to add internal information to the supplier's profile.

The supplier registration template determines:

● What questionnaire segments the category or supplier manager can select to assemble the questionnaire, and
which segments are required.

Setting Up SAP Ariba Supplier Lifecycle and Performance

8 CUSTOMER Getting started
 ● The content of the questionnaire segments.
● Which category or supplier managers approve the registration.
● Whether other stakeholders at your company must also approve the registration.
● Whether a denied registration can be resubmitted.
● Whether internal surveys or other tasks are part of the registration process.

The category or supplier managers assigned to the supplier invite the supplier to register, assemble and send the
questionnaire, review the supplier's answers, fill out internal surveys, complete to do tasks, approve or deny the
registration, and monitor the approval flow and status in the Registration tile on the supplier's 365° profile on the
Supplier Management tab of the dashboard. The supplier answers the registration questionnaire in their Ariba
Network for Suppliers profile; they must register with Ariba Network if they have not already. The supplier's profile
is automatically shared between Ariba Network and your Ariba supplier management solution.

Notifications let supplier know that they have been invited to register and provide a link to the questionnaire; let
the user who created the original supplier request know that registration has started; let approvers know that they
need to approve a supplier registration; let internal stakeholders know if they need to complete other tasks; and let
the supplier know that the registration has been approved, denied, or requires more information.

Integration settings determine when the supplier is added to your ERP vendor master list, at which point your
company's users can begin creating requisitions for the supplier, adding them to sourcing events, and so forth;
options include after the request has been approved, when the supplier is in the registration process, and after the
registration has been approved.

In solutions that include Ariba Sourcing, event templates can specify that suppliers must be registered in order to
either participate in or be awarded events.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Getting started CUSTOMER 9
The following diagram shows a registration workflow where integration is set to synchronize the supplier
automatically with the ERP vendor master after registration is approved:

The supplier qualification process

After a supplier is registered, a category or supplier manager qualifies the supplier for specific commodities and
regions by sending a qualification questionnaire, reviews the supplier's answers, and approves or denies the
qualification.

The qualification process typically solicits detailed information from the supplier that is specific to the
qualification's regions and commodities; for example, their sourcing and sustainability processes; shipping,
delivery, and return policies; commodity-specific certifications; methods of compliance with regional laws; and so
forth. Qualifications are always based on commodities and regions; they do not have to be for the commodities
and regions for which the supplier registered.

The supplier qualification template determines:

● What questionnaire segments the category or supplier manager can select to assemble the questionnaire, and
which segments are required.
● Which category or supplier managers approve the qualification.
● The content of the questionnaire segments.
● Whether other stakeholders at your company must also approve the qualification.
● Whether a denied qualification can be resubmitted.
● Whether internal questionnaires or other tasks or documents are part of the qualification process.

The category or supplier managers assigned to the supplier start the qualification, assemble and send the
questionnaire, review the supplier's answers, approve or deny the qualification, and monitor the approval flow and

Setting Up SAP Ariba Supplier Lifecycle and Performance

10 CUSTOMER Getting started
status in the Qualification tile on the supplier's 365° profile on the Supplier Management tab of the dashboard.
The supplier answers the qualification questionnaire in their Ariba Network for Suppliers profile. The supplier's
profile information is automatically shared between Ariba Network and your Ariba supplier management solution.

Notifications let supplier know that they have been invited toqualify for specific commodities and regions and
provide a link to the questionnaire; let approvers know that they need to approve a supplier qualification; and let
the supplier know that the qualification has been approved, denied, or requires more information.

At any point after the supplier qualification has been approved, category or supplier managers can:

● Start new qualifications for additional commodities and regions.

● Evaluate the supplier for a preferred status level (if your company uses preferred supplier levels).

In solutions that include Ariba Sourcing, event templates can specify that suppliers must be qualified in the event's
commodities and regions in order to either participate in or be awarded events.

The preferred supplier management process

After the supplier is qualified for a specific commodity and region combination, a category or supplier manager can
designate them as a preferred supplier for that commodity and region. Preferred suppliers show first in supplier
search results and can be automatically invited to sourcing events for their commodities and regions.

The preferred supplier management template determines:

● What information users add to the form

● Whether the preferred status designation requires approval, and if so, which category or supplier managers
approve it
● Whether other stakeholders at your company must also approve the status change.
● Whether a denied status designation can be resubmitted.

Users specify that they want to designate a supplier as preferred for a commodity and region in the supplier's 365°
profile on the Supplier Management tab of the dashboard.

If the process includes an approval flow, notifications let the approver know that the request requires approval, let
the requesting user know when the request has been approved or denied, and show the final approver so that
requesting users can have further discussions about denied request.

In solutions that include Ariba Sourcing, event templates can automatically invite the suppliers that are preferred
for the event's commodities and regions..

Key assumptions

The topics about setting up SAP Ariba Supplier Lifecycle and Performance assume the following:

● Your site has all non-SAP Ariba Supplier Lifecycle and Performance-specific master data (commodities,
regions, users, departments, and so forth) loaded.
● If your site also uses master data services, those services have already been configured, and their integration
has been set up. Master data service integration and SAP Ariba Supplier Lifecycle and Performance supplier
data integration are separate configurations.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Getting started CUSTOMER 11
SAP Ariba Supplier Lifecycle and Performance setup
checklist

Assign users in your site to the relevant SAP Ariba Supplier

 Lifecycle and Performance user groups [page 23], making
sure that:

● The users who will set up integration are in the SM ERP

Admin group.
● The users who will import data are in the Customer
Administrator and SM Ops Admin groups.
● The users who will set up project templates are in the SM
ERP Admin, SM Ops Admin, or Template Creator group.

If your company uses SAP ERP,

 set up integration [page 28].

Set up and publish the supplier request template. Make sure

 that the supplier request form includes required questions for
supplier name and supplier contact information [page 19].

Set up and publish the supplier registration template.


Set up and publish the supplier qualification template.

(Optional) Set up preferred supplier management by:
 ● Defining your preferred supplier levels [page 59].
● Setting up and publishing the preferred supplier manage­
ment template.

Customize supplier request, registration, and qualification no­

 tifications. [page 144]

(Optional) Contact your designated support contact to set up

 the way supplier contacts are synchronized from Ariba Net­
work supplier accounts [page 154].

Assign your company's category or supplier managers to the

 commodities and regions [page 57] for which they are re­
sponsible.

Import all of your supplier data. [page 63]


(Optional) Start onboarding suppliers in bulk by issuing a
 mass registration invitation [page 152].

Setting Up SAP Ariba Supplier Lifecycle and Performance

12 CUSTOMER Getting started
 (Optional) If your solution includes Ariba Sourcing, edit your
 event templates to:

● Use registration or qualification status as a criterion for

participating in or being awarded events.
● Automatically invite preferred suppliers to evens that
match their categories and regions.

See the Event Management Guide for details.

Understanding supplier management templates

SAP Ariba Supplier Management solutions use project templates with some special characteristics to define
supplier management processes.

The following templates are designed to work as parts of the supplier management workflow:

● Supplier Request Project Template

● Supplier Registration Project Template
● Supplier Qualification Project Template (SAP Ariba Supplier Lifecycle and Performance solutions only)
● Preferred Supplier Management Project Template (SAP Ariba Supplier Lifecycle and Performance solutions
only)

There is only one template for each of these project types in a site. When you update one of these templates, you
push those updates to all of the projects created by the template.

Supplier management project templates function in much the same way as other project templates: they have
documents, tasks, project teams, and so forth. However, the way users experience projects created from these
templates is very different.

The category or supplier managers who manage these projects do not work in the classic project interface, with its
tabs for documents and tasks and team. Instead, they work in the 360° profiles of individual suppliers. A supplier's
360° profile includes all supplier management projects for the supplier. The category or supplier manager
assigned to the supplier creates and manages projects from this profile: starting registration, qualification, and
other processes, sending and approving forms and questionnaires, monitoring approval flows, and so forth.

These supplier management project templates are designed to support these special workflows and user
experiences.

Note
Ariba Supplier Information and Performance Management solutions also use SPM project templates for
supplier performance management. Users manage these projects outside of supplier 360° profiles, in the
classic project interface. Therefore, SPM project templates do not share any of the special characteristics
discussed in these topics. For information on setting up SPM project templates, see Configuring Supplier
Performance Management Reviews.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Getting started CUSTOMER 13
Commodity, region, and user combinations
Supplier management templates use a combination of commodities and regions to route supplier management
processes to the appropriate supplier or category managers and other internal stakeholders.

These templates have therefore built commodity and region information into their processes in the following ways:

● Targeting forms and questionnaires: Template creators create different questionnaire segments with
questions pertaining to specific commodities or regions (or both). When a supplier or category manager sends
a questionnaire to a supplier, they assemble that questionnaire from all of the segments that apply to the
supplier's commodities and regions.
● Assigning the appropriate project owners, approvers, and other team members: If user assignments to
commodities, regions, and project groups are imported into a site, and the project templates use those
assignments to determine project group membership, supplier management templates automatically add
those users to the teams of the appropriate projects. These team members have access to the project,
approve or deny forms and questionnaires, and can be assigned to perform other tasks as well.

Documents: forms, questionnaires, and internal surveys

Supplier management project templates use survey and content documents to create forms, simple,
questionnaires, dynamic questionnaires targeted to suppliers based on region and commodity, and internal
surveys.

Supplier management processes center around a form or questionnaire, which solicits information about a
supplier. Therefore, each supplier management project template includes a default survey document, which forms
the basis of that form or questionnaire. Projects can use additional internal surveys to supplement the form or
questionnaire information.

● Forms: for projects that need a basic set of information from a limited number of questions, you use the
default survey document in the project, without any additional content or other documents, to create the form.
For example, a supplier request is an initial process and might involve having one of your company's sourcing
agents or buyers provide the name, contact information, commodities, regions, and other basic information
for the requested supplier. In this case, you create the supplier request by editing the default template survey
to set its type to Form and add all of the form content.
● Simple questionnaires: for projects that need a larger set of general information that is not for the most part
commodity- and region-specific, you use the default survey document in the project, without any additional
content documents, to create the simple questionnaire.
For example, if your solution includes supplier qualification projects, you might want to reserve targeted
commodity- and region-specific questions for the qualification phase and ask general questions in the
registration questionnaire. In this case, you create the supplier questionnaire by editing the default template
survey to set its type to Questionnaire and add all of the questionnaire content.
● Targeted questionnaires: for projects that need a dynamic questionnaire with targeted questions based on
the supplier's commodities and regions, you use the default survey document in the project as an empty
container to generate the dynamic questionnaire. You then add a content document for each targeted
questionnaire segment.
For example, if your solution does not include supplier qualification projects, you might want to ask your
suppliers both general and commodity- and region-specific questions during registration. In this case, you set
the survey up as a framework by setting its type to Questionnaire and leaving it empty. You then create a
content document with questions for all suppliers, another content document with questions for suppliers in

Setting Up SAP Ariba Supplier Lifecycle and Performance

14 CUSTOMER Getting started
 Brazil, a third content document with questions for suppliers in France, and so forth. The category or supplier
manager assigned to the project assembles a questionnaire for each supplier based on the segments that
apply to the supplier's region and commodities. The template survey document simply functions as a
framework for pulling all of those questionnaire segments together and automatically generating a single
questionnaire for the supplier.
The following diagram illustrates the relationship between survey documents and content documents in SAP
Ariba supplier management projects:

● Internal surveys: supplier management projects support additional survey documents to allow category or
supplier managers to supplement the information gathered in the project's form or questionnaire.
For example, suppliers fill out registration questionnaires, but your company's registration process might
include having a category or supplier manager rate the supplier on a set of specific metrics. In this case, you
create an additional survey document in the project, set its content type to Form, and specify that it is internal.
You then add questions to it.

Note
When you create approval or to do tasks for a form or questionnaire, those tasks must always be on the survey
document, not the individual questionnaire segments (content documents).

Tasks: form and questionnaire approvals and internal

survey to do tasks
Supplier management projects use approval tasks and approval flows to define approval processes for forms and
questionnaires.

Supplier management projects are designed to use an approval task on the template's survey document to route
approvals for various supplier management processes. The approval flow is defined in the approval task.

Although there are a number of task types available in SAP Ariba projects, the most important task for a supplier
management project is the approval task on the project's form or questionnaire.

Approval flows in approval tasks are often constructed using site-wide user groups (such as Supplier
Qualification Manager or Legal) and project groups (such as Project Owner). If you are using either buyer

Setting Up SAP Ariba Supplier Lifecycle and Performance

Getting started CUSTOMER 15
category assignments or team member rules to determine project group membership, you can create approval
flows and assign other tasks based on project groups, and the tasks are automatically assigned to the users who
are responsible for managing suppliers in specific categories and regions.

Supplier management projects also support to do tasks; for example, a to do task that requires a category or
supplier manager to complete the project's internal survey.

Users complete these approvals and to do tasks in the supplier's 360° view. Users must complete any other
project tasks outside of the supplier's 360° view by clicking Manage My Tasks on the dashboard.

Team: automatic assignment by commodity and region

SAP Ariba Supplier Management solution projects use teams to define who can work with and approve supplier
management processes for specific suppliers.

In other SAP Ariba projects, the user who creates the project is automatically a member of the Project Owner
group. However, supplier management project templates are designed to dynamically add users to project groups
on the Team tab, including Project Owner, based on their assignments to categories, regions, and project groups.

If you are not using category and region assignments, you can also create team member rules in order to make
those assignments. User assignments to category and region are site-wide and automatically apply to project
groups in all supplier management projects except for SPM projects, while you must set up team member rules
separately in each project template.

SAP Ariba Supplier Lifecycle and Performance

default template configurations
The initial deployment of SAP Ariba Supplier Lifecycle and Performance adds all of the templates in a default
configuration. You then edit the templates to define your supplier management processes.

Template Default Configuration

Supplier Request Template ● Version 1, status Active

● Documents: Supplier request form (an empty survey
document with the form questionnaire type) in Draft sta­
tus
● Tasks: Approval for supplier request (an approval task for
the supplier request form document, with members of the
Project Owner group as approvers)
● Team: the system user aribasystem and the Template
Creator user group are members of the Project Owner
project group. By default, membership in Project Owner
group is not assigned by commodity and region.

Setting Up SAP Ariba Supplier Lifecycle and Performance

16 CUSTOMER Getting started
 Template Default Configuration

Supplier Registration Template ● Version 1, status Active

● Documents: Supplier registration questionnaire (an
empty survey document with the questionnaire type) in
Draft
● Tasks: Approval for supplier registration questionnaire
(an approval task for the supplier registration question­
naire document, with members of the Project Owner
group as approvers)
● Team: the system user aribasystem and the Template
Creator user group are members of the Project Owner
project group. By default, membership in Project Owner
group is not assigned by commodity and region.

Supplier Qualification Template ● Version 1, status Active

● Documents: Supplier qualification questionnaire (an
empty survey document with the questionnaire type) in
Draft status
● Tasks: Approval for supplier qualification questionnaire
(an approval task for the supplier qualification question­
naire document, with members of the Project Owner
group as approvers)
● Team: the system user aribasystem and the Template
Creator user group are members of the Project Owner
project group. By default, membership in Project Owner
group is not assigned by commodity and region.

Preferred Supplier Management Template ● Version 1, status Active

● Documents: Category status (an empty survey document
with no questionnaire type set)
● Tasks: Approval for category status change (an approval
task for the supplier request form, with members of the
Project Owner group as approvers)
● Team: the system user aribasystem and the Template
Creator user group are members of the Project Owner
project group. By default, membership in Project Owner
group is not assigned by commodity and region.

The default team configuration in all of the templates means that:

● The forms and questionnaires are not yet visible in the site, since they are in Draft status.
● Members of the Template Creator group can edit the templates. However, they do not become owners of any
of the projects created from the templates.
● The users who create projects from these templates are automatically the project owners, since the system
user aribasystem is the Project Owner group.
● The users who create projects from these templates are also the approvers for the approval tasks.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Getting started CUSTOMER 17
 Note
All supplier management processes are designed to work with the default template properties. By default, all
supplier management templates have a default rank of 10 and no access control or conditions. Since there is
only one template per project type per site, and users do not explicitly create projects from these templates,
rank is irrelevant, and you should not set access control or conditions at the template level. You can use the
Allowed Commodity Levels settings to specify the range of commodity levels (from 1, highest level, to 4, lowest
level) that can be specified for the template content documents that define targeted questionnaire segments;
by default, no levels are set.

Best practices for fitting SAP Ariba Supplier

Lifecycle and Performance projects into SAP Ariba
Supplier Lifecycle and Performance workflows
Unlike other Ariba projects, which exist independently from each other, SAP Ariba Supplier Lifecycle and
Performance projects are designed to fit together into a specific workflow in supplier 360° profiles on the Supplier
Management tab.

The SAP Ariba Supplier Lifecycle and Performance workflow activates projects in this order:

1. Supplier request
2. Registration
3. Qualification (in at least one category/region)
4. (Optional) Preferred supplier designation (in at least one category/region)

Category or supplier managers cannot invite a supplier to register until the request has been approved, start a
qualification until the registration has been approved, or designate a supplier as preferred for a category/region
combination until a qualification in that category/region has been approved. This flow is automatic and is not
configurable in the templates or elsewhere.

Because of this automatic flow, and since category or supplier managers interact with these projects through the
specialized workflows on the supplier 360° view, best practices help to ensure that SAP Ariba Supplier Lifecycle
and Performance project templates fit into those processes and workflows.

General best practices for supplier management templates

The following are best practices for all supplier management templates:

● In other Ariba projects, template creators use project conditions to display specific documents based on the
project's commodities and regions. Supplier management templates automatically show only the
questionnaire segments that apply to a supplier's commodities and regions to the category or supplier
manager who assembles the questionnaire to send to the supplier. Therefore, it is unnecessary to apply
project conditions to the content documents that define questionnaire segments.
● Supplier management questionnaires consist of one empty survey document, which serves as a container,
and a number of questionnaire segments (content documents). Each content document is tied to specific

Setting Up SAP Ariba Supplier Lifecycle and Performance

18 CUSTOMER Getting started
 commodites and regions. You can apply visibility conditions [page 95] to show and hide additional
questionnaire content based on answers in a questionnaire segment, but be careful to make sure that the
conditions work with the commodities and regions to which the segment is targeted.
● Supplier management workflows are designed to use only the survey and content documents that define the
project's form or questionnaire and optionally an additional internal survey. Users can view and work with
those documents in the supplier 360° profile. Any other document types added to the project do not show in
the supplier 360° profile. Avoid adding other types of documents to these projects.
● Users fill out internal surveys and (in solutions that include SAP Ariba Supplier Lifecycle and Performance)
forms for preferred supplier status change on tiles in the supplier 360° view. The survey names show as
section headings on the tiles. Make sure that the names work in this context.
● Supplier management project workflows are designed to use one approval task and optionally one or two
additional to do tasks. All supplier management projects must have an approval task for the project's default
survey document, which leads to approval for the project's form or questionnaire. They also support to do
tasks. Task owners complete those tasks alongside the project's form or questionnaire; for example, they
approve a registration or complete a registration-related to do task on the Registration tile of the supplier
360° profile. (There is an exception for tasks in preferred supplier management projects, which users must
complete outside of the supplier 360° profile.) Avoid adding approvals for additional documents and all other
types of tasks in these projects.

Best practices for supplier request templates

Users at your company request to add suppliers to the vendor master by using the Create menu on the
dashboard, or by creating the request while adding participants to a sourcing event. Supplier requests are
automatically internal-only, regardless of whether you set Is questionnaire internal only? to Yes or No.

The following are best practices for supplier requests:

● You can either set up a supplier request form or a questionnaire. However, since the request process is the
initial stage of your relationship with the supplier and is designed to solicit only basic information, a form is
recommended. [page 83] If you do want to use a questionnaire, set the survey document's questionnaire
type to Questionnaire, but create the content directly in the survey document. Do not use content documents
to create questionnaire segments. There is no mechanism for assembling a questionnaire from segments
based on the supplier's commodities and regions in request projects, and in any case you have no information
on the supplier's regions and commodities before the form is submitted, so using content documents to
create a questionnaire in a supplier request project does not make sense.
● Make sure to make the question about the supplier's name required and map it [page 107] to the
[Link].name1 field in the supplier database. The supplier name and mapping is required in
order to create the supplier in the database.
● Since the person requesting the supplier is likely to have the best initial information about supplier contacts,
add questions for the contact's first name, last name, and email address and map them to the
[Link], [Link], and [Link] fields in the supplier database. Supplier
contact information and mapping are also required for supplier requests.
● Adding a question for the supplier contact's phone number and mapping it to [Link] to the
supplier request is recommended.
● Asking for the supplier contact's locale based on the locale information in your site is also recommended. This
locale information allows SAP Ariba to send the notifications and questionnaire content that match the
supplier contact's language. To do this, ask for the contact's locale using master data as the acceptable
answer value, select Locale as the master data type, and map the question to [Link].

Setting Up SAP Ariba Supplier Lifecycle and Performance

Getting started CUSTOMER 19
● When asking about the supplier's commodities and regions, use the Commodity and Region answer types and
map them to the [Link] and [Link] fields in the supplier database. These answer
types and mappings are required for assigning project ownership and displaying questionnaire segments
based on the supplier's commodities and regions.

Best practices for supplier registration templates

External suppliers fill out and submit registration questionnaires. They are automatically internal-only, regardless
of whether you set Is questionnaire internal only? to Yes or No for the default survey document.

The following are best practices for supplier registrations:

● Depending on your company's processes, you can set up your registration questionnaire either to ask general
or commodity- and region-specific questions:
○ If your solution includes supplier qualification projects, and you want to reserve commodity- and region-
specific questions for the qualification phase, set up the template's default survey document as a
questionnaire [page 83] and add content to it.
○ If you want to ask sets of questions targeted to specific commodities and regions during registration, set
up the template's default survey document as a questionnaire [page 85] but do not add content to it.
Then add questionnaire segments as separate content documents [page 86]. You can add general
questionnaire segments as well as questionnaire segments based on specific categories or regions. Make
sure that the supplier request includes questions about the supplier's commodities and regions so that
you can target the registration questionnaire segments correctly.
● Plan a consistent strategy for organizing each questionnaire segment's contents using sections [page 89]. If
you do not use sections in any questionnaire segments, all of the content is displayed as a continuous
numbered list when the segments are assembled in the final questionnaire. If you use a top-level section in
each segment, and nest all of the segment's content inside it, each segment is its own numbered section in the
final questionnaire, with the segment content as numbered sub-items under it. However, if you use a top-level
section in one questionnaire segment and no top-level section in the segment that comes after it, the content
in the second segment is added to the previous segment's section, and uses the previous section's numbering,
in the final questionnaire.
● Make sure that any internal-facing documents or other content you add to questionnaire segments is not
visible to participants.
● Use additional internal surveys to allow category or supplier managers to add internal information that needs
to be displayed prominently displayed in supplier profiles.. In registration projects only, internal surveys are
displayed as sections of the Summary tab on the Overview tile in the supplier 360° profile, alongside other
basic information about the supplier.

Caution
If you add a survey document to the template in addition to the default survey document, make sure to set Is
questionnaire internal only? to Yes. Any survey other than the default survey must be interal-facing in supplier
registration projects.

Setting Up SAP Ariba Supplier Lifecycle and Performance

20 CUSTOMER Getting started
Best practices for supplier qualification templates

External suppliers fill out and submit qualification questionnaires. They are automatically internal-only, regardless
of whether you set Is questionnaire internal only? to Yes or No for the default survey document.

The following are best practices for supplier qualifications:

● Set up the template's default survey document as a questionnaire, but do not add content to it. [page 85]
● Add separate questionnaire segments (content documents) based on questions for specific category/region
combinations. [page 86] Supplier qualifications are always based on specific commodity/region
combinations.
● Unlike registration, which is a one-time process, the qualification process is designed so that category or
supplier managers can run multiple separate qualifications on the same supplier for different commodities or
regions. A supplier contact will potentially answer multiple qualification questionnaires from you. Therefore,
it's a good idea to choose the levels of the commodity and region hierarchies at which you want to qualify
suppliers and use them consistently to target questionnaire segments so that you avoid asking the same
questions over and over. For example, you can create a questionnaire segment that is required for all suppliers
in the US. However, if your company qualifies suppliers by individual state, every new qualification
questionnaire for a new state will include that required segment for the US. If you need to gather information
about a supplier that is broadly applicable across multiple commodities or regions, consider either doing so
during registration or making sure that the questionnaire segment is not required so that category or supplier
managers can omit it from successive qualifications.
● Plan a consistent strategy for organizing each questionnaire segment's contents using sections [page 89]. If
you do not use sections in any questionnaire segments, all of the content is displayed as a continuous
numbered list when the segments are assembled in the final questionnaire. If you use a top-level section in
each segment, and nest all of the segment's content inside it, each segment is its own numbered section in the
final questionnaire, with the segment content as numbered sub-items under it. However, if you use a top-level
section in one questionnaire segment and no top-level section in the segment that comes after it, the content
in the second segment is added to the previous segment's section, and uses the previous section's numbering,
in the final questionnaire.
● Make sure that any internal-facing documents you add are not visible to participants.

Caution
If you add a survey document to the template in addition to the default survey document, make sure to set Is
questionnaire internal only? to Yes. Any survey other than the default survey must be interal-facing in supplier
qualification projects.

Best practices for preferred supplier management

templates

Users at your company designate qualified suppliers as preferred on the Summary tab of the Overview tile in
supplier 360° profiles. Preferred supplier management forms are automatically internal-only, regardless of
whether you set Is questionnaire internal only? to Yes or No.

The following are best practices for preferred supplier management templates:

Setting Up SAP Ariba Supplier Lifecycle and Performance

Getting started CUSTOMER 21
● You can either set up a preferred supplier request as a form or a questionnaire. However, since the form is
filled out in the supplier 360° profile and the preferred supplier management process is designed to be simple,
a form is recommended. [page 83] If you do want to use a questionnaire, set the survey document's
questionnaire type to Questionnaire, but create the content directly in the survey document. Do not use
content documents to create questionnaire segments. Preferred supplier requests are always based on
successful qualifications, so they are already specific to the commodities and regions for which the supplier is
qualified.
● For the question asking which preferred supplier level to use for the supplier, use your site's preferred supplier
level master data [page 105] for acceptable answers and map the question to [Link] in the supplier
database.
● Task owners for preferred supplier management tasks cannot complete those tasks in the supplier 360°
profile. They must click a link in a notification email or click Manage My Tasks on the dashboard and
complete the task using the classic project task interface. If your company's policies do not require approval
for preferred supplier designation, you can set the approval task on the template's default survey to
automatical approval.

Where to find more information

To find more information about... See...

Importing master data (including users, regions, commodities, Common Data Import and Administration Guide
and so forth) into your site
Note
The information about importing supplier data and manag­
ing suppliers and supplier users in this guide does not apply
to SAP Ariba Supplier Lifecycle and Performance.

SAP Ariba project templates in general, including documents, Project Template Guide
task, teams, versioning, and publication

To do tasks and access control in projects Managing Projects, Teams, Documents, and Tasks

Managing enterprise users in your site Common Data Import and Administration Guide

Setting up sourcing event templates to use qualified and pre­ Event Management Guide
ferred suppliers

Setting Up SAP Ariba Supplier Lifecycle and Performance

22 CUSTOMER Getting started
Setting up Supplier Lifecycle and Performance
users

Setting up Supplier Lifecycle and Performance users involves making sure that those users have the appropriate
permissions through user group membership and assigning the users who are responsible for suppliers by
commodity and region.

Prerequisites [page 23]

SAP Ariba Supplier Lifecycle and Performance user groups [page 23]

How to add users [page 25]

How to edit users [page 26]

Prerequisites

Before you set up Supplier Lifecycle and Performance users, they must be created in your site.

Typically, enterprise users are imported as master data as part of Ariba's deployment of your site, and might be
updated by periodic imports from an integrated ERP system. You can also manually create enterprise users [page
25].

SAP Ariba Supplier Lifecycle and Performance user

groups

The following table describes the user groups are pertinent to SAP Ariba Supplier Lifecycle and Performance:

Members of this group... Can...

Template Creator Manage all SAP Ariba Supplier Lifecycle and Performance
templates, including creating questionnaires and request
forms. In the default configuration, the Template Creator
group is a member of the project team for all of the SAP Ariba
Supplier Lifecycle and Performance templates.

Translator Provide translations for questionnaire and form content (for

users that are also members of the Template Creator group)
and custom notifications (for users that are also members of
the Project Email Template Administrator group).

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up Supplier Lifecycle and Performance users CUSTOMER 23
Members of this group... Can...

Project Email Templates Administrator Customize the content of all SAP Ariba Supplier Lifecycle and
Performance notifications.

Customer Administrator Import and export data in Ariba Administrator and SM Admin,
create new users, and add groups to existing users.

Customer User Admin Create new users and add groups to existing users.

Supplier Request Manager Manage supplier requests.

Supplier Registration Manager Initiate and manage supplier registrations.

Supplier Qualification Manager Initiate and manage supplier qualifications.

Preferred Supplier Manager Initiate and manage processes to designate preferred suppli­
ers.

SM Ops Admin Import and export data in SM Admin area and manage all SAP
Ariba Supplier Lifecycle and Performance templates, including
creating questionnaires and request forms.

SM ERP Admin Configure integration with an external ERP system in SM

Admin area and manage all SAP Ariba Supplier Lifecycle and
Performance templates, including creating questionnaires and
request forms.

Legal Approve forms and questionnaires, if they are part of the ap­
proval process defined in the template. This group does not
confer many functional privileges, but is useful for defining ap­
proval processes that require participation by your organiza­
tion's legal department.

Finance Approve forms and questionnaires, if they are part of the ap­
proval process defined in the template. This group does not
confer many functional privileges, but is useful for defining ap­
proval processes that require participation by your organiza­
tion's legal department.

To set up your SAP Ariba Supplier Lifecycle and Performance users, either create new users [page 25] or edit
existing users [page 26], adding the relevant groups to them.

Setting Up SAP Ariba Supplier Lifecycle and Performance

24 CUSTOMER Setting up Supplier Lifecycle and Performance users
How to add users
You can add individual users from Ariba Administrator as necessary.

Prerequisites

You must be a member of the Customer Administrator or Customer User Admin group in order to add users to a
site.

Context

If you need to add many users, it is more efficient to run data import tasks.

Procedure

1. On the dashboard, click Mange Administration .

2. In Ariba Administrator, click User Manager, and then click Users.
3. On the Users page, click Create New User.
4. On the General tab, enter:

○ Type: This field can be set to Enterprise User, Third Party Enterprise User (Ariba), or Supplier User.
○ User ID: A unique internal identifier for the user. For security reasons, this field cannot contain an
apostrophe.
○ Name: The display name for the user.
○ Organization: Do not modify the value in this field.
○ Business Email Address: The user’s business email address.
User email addresses are checked for validity. Valid email addresses be entered, even in test
environments. Invalid email addresses trigger an error message and must be corrected. By default, an
email address must include a valid, existing domain. (The domain name is the part of the email address
that appears after the @ sign.) Ariba Customer Support can set a parameter to turn off the domain portion
of the validity check, in which case only syntax is checked. The name of the parameter is
[Link].

Note
If Ariba Customer Support configured a set of valid email address domain names specifically for your
site, any domain you use in the Business Email Address field must match a domain in that set, unless
you select the Allow External Email Domain option (see the next item).

○ Allow External Email Domain - Click this check box to allow an unapproved email address domain for this
user.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up Supplier Lifecycle and Performance users CUSTOMER 25
 ○ Business Phone Number - The user’s business phone number.
○ Business Fax Number - The user’s business fax number.
○ Locale - The user’s default locale.
○ Default Currency - The user’s default currency. You must use a currency code defined on the
Reference - System Level Codes worksheet.
○ Timezone - The user’s time zone.
○ Supervisor - The user’s supervisor.
5. On the Invitation tab set your preference for user password generation and login invitation:

○ Click the check box if you want Ariba Administrator to generate a temporary password and send a login
invitation message to the user immediately after you click Save.
○ Clear the check box (the default) if you want to manually generate a temporary password before Ariba
Administrator sends a login invitation message..
6. On the Ship To Addresses tab, click Add/Remove to display the available shipping addresses and enter the
user’s ship-to address.
7. On the Billing Addresses tab, click Add/Remove to display the available billing addresses and enter the user’s
billing address.
8. On the Groups tab, click Add/Remove to display the available groups. Select one or more groups to assign to
the new user and click Done.
9. Click Save to save your changes, or click Cancel to return to the previous page without saving your changes.

Results

If you allowed Ariba to generate a temporary password for the user, the user receives the system-generated email
invitation containing a temporary password and instructions for logging in to Ariba. When the user clicks the URL
in the invitation, the user is prompted to create a new password.

How to edit users

You can modify existing users from Ariba Administrator.

Prerequisites

You must be a member of the Customer Administrator or Customer User Admin group in order to edit users.

Context

If you need to edit many users at once, it is more efficient to run data import tasks.

Setting Up SAP Ariba Supplier Lifecycle and Performance

26 CUSTOMER Setting up Supplier Lifecycle and Performance users
Procedure

1. On the dashboard, click Mange Administration .

2. In Ariba Administrator, click User Manager, and then click Users.
3. Search for and select the user you want to edit.
4. Choose Edit from the Actions pull-down menu.
5. On the General tab, edit the user’s name, email address, phone number, fax number, locale, default currency,
supervisor, and department. Do not edit the default values in the Type and Organization fields.
6. On the Ship To Addresses tab, click Add/Remove to display the available shipping addresses and edit the
user’s ship-to address.
7. On the Billing Addresses tab, click Add/Remove to display the available billing addresses and edit the user’s
billing address.
8. On the Groups tab, click Add/Remove to display the available groups and edit the groups to which the user
belongs.
9. Click Save to save your changes, or click Cancel to return to the previous page without saving the changes.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up Supplier Lifecycle and Performance users CUSTOMER 27
Setting up supplier data integration with SAP
ERP

About supplier data integration with SAP ERP [page 28]

Prerequisites [page 30]

Integration workflow [page 30]

MDG business functions for supplier data integration [page 31]

How to define a replication model for supplier data integration [page 32]

How to import the supplier management transports into SAP ERP [page 33]

How to maintain table entries for SAP Ariba supplier management solutions [page 34]

How to set up SAP ERP credentials in Ariba [page 35]

Configuring the Direct Connectivity integration method [page 36]

Configuring the Mediated Connectivity integration method [page 39]

How to replicate Business Partner master data from SAP Ariba supplier management solutions [page 48]

Customizing supplier master data integration [page 49]

Setting default supplier field values [page 53]

How to set up supplier data synchronization [page 54]

How to monitor errors in SAP ERP [page 55]

Monitoring integration errors in SAP Ariba supplier management solutions [page 56]

About supplier data integration with SAP ERP

SAP Ariba supplier management solutions (SAP Ariba Supplier Lifecycle and Performance, SAP Ariba Supplier
Risk, and Ariba Supplier Information and Performance Management extended funtionality) are designed for native
integration with SAP ERP.

The integration between Ariba supplier management solutions and SAP ERP and MDG is bidirectional and enables
you to replicate supplier master data as business partners in SAP ERP and SAP Ariba.

Note
If your Ariba solution includes existing Ariba Sourcing, Ariba Contract Management, or Ariba Supplier
Information and Performance Management (classic functionality) solutions, and you have an existing
integration with SAP ERP for supplier data, this integration method replaces the previous one.

The outbound integration from SAP ERP to SAP Ariba supplier management solutions is achieved through
business partner interfaces provided by MDG and standard SAP programs such as Data Replication Framework

Setting Up SAP Ariba Supplier Lifecycle and Performance

28 CUSTOMER Setting up supplier data integration with SAP ERP
(DRF) programs. You can use the DRFOUT transaction code for initial replication of business partners from SAP
ERP to SAP Ariba supplier management solutions.

Note
SAP Ariba Supplier Risk consumes outbound supplier data from SAP ERP, but does not send any data back
inbound. Therefore, if your solution does not include any SAP Ariba supplier management solutions except for
SAP Ariba Supplier Risk, you only need to configure outbound integration.

The inbound integration from SAP Ariba supplier management solutions with SAP ERP and MDG is achieved
through a polling client, /ARBA/SM_BUSINESS_PARTNER_PULL, that runs on SAP ERP. You can specify the polling
frequency and configure the polling client to poll SAP Ariba supplier management solutions at regular intervals for
business partner master data or confirmation messages for the business partners exported from SAP ERP.

Alternatively, you can manually trigger the poll by executing the /ARBA/SM_BUSINESS_PARTNER_PULL program
from the SAP ERP user interface. When you execute this program, you can choose one or more of the following
options:

● Business Partner Bulk Replicate Request

● Business Partner Bulk Replicate Confirmation
● Business Partner Relationship Bulk Replicate Request
● Business Partner Relationship Bulk Replicate Confirmation

Note
SAP Ariba supplier management solutions do not currently support Business Partner Relationship
Bulk Replicate Request and Business Partner Relationship Bulk Replicate
Confirmation.

Tip
Create a scheduled job to run the polling client and data replication at regular intervals. You can use the
sm36 transaction code to schedule the program to run at regular intervals.

For every successful poll, SAP Ariba supplier management solutions include the sequence number of the message
in the response. The polling client updates the sequence number in the /ARBA/SM_SEQNUM table when a poll is
successfully completed. In case of an error, an error log is created in SLG1. For subsequent polls, the polling client
includes the sequence number of the last successful poll, which is stored in /ARBA/SM_SEQNUM.

When a polling request goes without a sequence number, SAP Ariba supplier management solutions identify it as a
first time request and sends the business partner records starting from the first record. The number of records
that SAP Ariba supplier management solutions send in response to a poll request depends on the configuration in
SAP Ariba for the maximum number of records to include in a response. Currently, this is set to 10 records.

If there are more than the configured number of records to replicate, SAP Ariba supplier management solutions
send the remaining records as responses to subsequent polls until there are no new records to replicate. SAP ERP
continues to use the same sequence number in the polls until SAP Ariba supplier management solutions send a
new record and updates the sequence number.

SAP ERP and MDG integration with SAP Ariba supplier management solutions uses SOAP messages for
requesting and receiving data from SAP Ariba. SAP Ariba supplier management solutions use MDG business
partner interface structure to store supplier master data. However, SAP Ariba supplier management solutions
integration with SAP ERP supports extension of the business partner data structure to enable you to use custom

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 29
fields to address your specific requirements. For more information about extensions and customizations, see
Customizing supplier master data integration [page 49].

You can use the Direct Connectivity or Mediated Connectivity integration method to integrate SAP Ariba supplier
management solutions with SAP ERP.

Prerequisites

The following items are prerequisites for integrating SAP Ariba supplier management solutions with SAP ERP:

Ariba Cloud Integration release version: 8.0 or higher

SAP ERP system landscape: ● SAP ERP 6.0 EHP 7 SP11

SAP S/4HANA On-Premise Edition 1503/1511
● SAP Business Services Foundation 747

SAP ERP configuration: Digital Certificates and Keys -Yes

Authorizations - Yes

Logical Path -Yes/No

Partner Profile -Yes/No

IDOC -Yes/No BAPI -Yes/No

BAdI -Yes/No

Custom Exits - No

Implicit Enhancements- No

Integration workflow

The following high-level steps describe the workflow for setting up integration between SAP Ariba supplier
management solutions and SAP ERP:

1. If you have not done so already, configure MDG or DRF integration for suppliers. For more information, see the
Configuring Master Data Governance for Suppliers on the SAP Help portal. For outbound integration, complete
the following tasks:
○ Enable the business functions listed in MDG business functions for supplier data integration [page 31].
○ Set up the Customer-Vendor integration, define a replication model [page 32], and a assign a target
system or replication model or outbound implementation.
(SAP ERP)
2. Import the latest SAP Ariba supplier management transports into SAP ERP [page 33]. (SAP ERP)
3. Maintain table entries for SAP Ariba supplier management in the /ARBA/SM_SEQNUM table [page 34]. (SAP
ERP)

Setting Up SAP Ariba Supplier Lifecycle and Performance

30 CUSTOMER Setting up supplier data integration with SAP ERP
 4. Set up the SAP ERP system credentials in the SAP Ariba supplier management solution [page 35]. (SAP
Ariba supplier management solutions).
5. Configure the Direct Connectivity [page 36] or Mediated Connectivity [page 39] integration method. (SAP
ERP)
6. Replicate Business Partner master data from SAP Ariba supplier management solutions [page 48]. (SAP
ERP)
7. Set any default values for supplier fields that you want to send to SAP ERP during supplier synchronization
[page 53]. [Link] is automatically set to 2 so that SAP ERP recognizes
the data sent from SAP Ariba supplier management solutions as supplier data. You must set default values for
any required fields that aren't included in, and mapped from, required questions on forms and questionnaires,
so that those fields will include data during initial synchronization. (SAP Ariba supplier management solutions)
8. Specify how and when suppliers created in SAP Ariba supplier management solutions [page 54] are first
synchronized to SAP ERP.

MDG business functions for supplier data

integration

For the outbound integration between SAP ERP and SAP Ariba supplier management solutions, you must activate
the following business functions:

Note
You do not require MDG license to activate these business functions.

● CA_BP_SOA
● CA_SUPPLIER
● DRF_FOUNDATION

Note
DRF_FOUNDATION is activated only in SAP_BS_FOUNDATION 748 and later. If you are running a lower
version of SAP_BS_FOUNDATION, you can use the transaction code SFW2 to define a custom business
function named Z_DRF_FOUNDATION with the following switches:
○ MDG_BS_CA_MDGAF_UI_SFWS_06
○ MDG_BS_CA_UI_SFWS_06
○ MDG_DATALOAD_SFWS_01
○ MDG_DRF_MAIN_05
○ MDG_DRF_MAIN_UI_05
○ MDG_DRF_SFWS_06
○ MDG_DRF_SFWS_07
○ MDG_DRF_UI_SFWS_06
○ MDG_KEY_MAPPING_05
○ MDG_KEY_MAPPING_UI_05
○ MDG_VALUE_MAPPING_05

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 31
 ○ MDG_VALUE_MAPPING_UI_05

If you have an MDG license and have the CA_BP_SOA, CA_SUPPLIER_SOA, and MDG_FOUNDATION business
functions activated, ensure that you also define and activate the DRF_FOUNDATION business function, which
contains the following additional switches that MDG_FOUNDATION does not contain:

● MDG_BS_CA_MDGAF_UI_SFWS_06
● MDG_BS_CA_UI_SFWS_06
● MDG_DRF_SFWS_06
● MDG_DRF_SFWS_07
● MDG_DRF_UI_SFWS_06

How to define a replication model for supplier data

integration
Context

For the outbound integration between SAP ERP and Ariba supplier management solutions to work, you must
configure the data replication settings.

Procedure

1. Run the transaction code DRFIMG from the SAP ERP user interface.
The Display IMG window appears.

2. Click Data Replication Define Custom Settings for Data Replication Define Technical Settings
Define Technical Settings for Business Systems .
The Change View "Define Business Systems": Overview window appears.
3. To define a new business system and to maintain the logical system for the receiving systems, click New
Entries.
4. In the New Entries: Overview of Added Entries window, specify a business system, for example ABC_123,
and a logical system, ABCCLIENT123.
5. Click Save and go back to the Display IMG window.

6. To define a replication model, click Data Replication Define Custom Settings for Data Replication
Define Replication Models .
The Change View "Define Replication Model": Overview window appears.
7. Click New Entries to enter a name for the replication model and add a description.
8. Select the line that contains the newly-added replication model and click Assign Outbound Implementation.
Create a new entry and enter the following values using the input help:

○ Outbound Implementation: 986_3 Outbound Impl. for BP/REL via Services

Setting Up SAP Ariba Supplier Lifecycle and Performance

32 CUSTOMER Setting up supplier data integration with SAP ERP
 ○ Communication Channel: Replication via Services
○ Filter time: Filter After Change Analysis
9. Mark the line and choose Assign Target Systems for Repl. Model /[Link]. Create a new entry and enter
the business system name for the receiving system that you created.
10. Click Assign Outbound Parameter. Create a new entry, enter the following values, and save.

○ Outb. Parameter: PACK_SIZE_BULK

○ Outb. Parameter value: For example, 100
11. Go back to the Define Replication Model view. Optionally, you can also add an expiration time for the log.
12. Save the replication model.
13. Select the newly-created replication model, and click Activate.

For more information, click the IMG activity documentation icon on the left side of Data Replication
Define Custom Settings for Data Replication Define Replication Models in the Display IMG window.

How to import the supplier management transports

into SAP ERP
Context

You must download the latest version of the Ariba supplier management transports to implement the integration
between SAP Ariba supplier management solutions and SAP ERP. To implement Mediated Connectivity, you must
download the latest .TPZ files.

Procedure

1. On the Home tab of [Link] , go to Product Summary On-Demand and click Ariba Cloud
Integration.

The Ariba Cloud Integration page appears.

2. Click the Integration tools for Ariba Supplier Management link.
3. On the Resources tab, click ABAP Transports for SAP ERP. If the list does not contain this entry, contact your
Ariba account executive.

The Sourcing SAP Transports page appears.

4. Click Download and save the Ariba_Supplier_Management_V_CI_8.zip package.
5. Extract the contents of the ZIP file and import the transports to SAP ERP.
6. If you want to implement the feature over Mediated Connectivity, go back to the Integration Tools for Ariba
Supplier Management page and click SAP NetWeaver PI Mapping from the Resources tab.
The Ariba Supplier Management SAP NetWeaver PI Mapping page appears.
7. Click Download and save the Ariba_Supplier _Management_SAP_Netweaver_Repositor_CI8.zip
package.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 33
8. Extract and import the relevant TPZ files into the SAP Process Integration.

How to maintain table entries for SAP Ariba supplier

management solutions

Context

You can use the sm30 transaction code to access tables. To maintain a table, enter the name of the table in the
Table/View field of the Maintain Table Views: Initial Screen, and click Maintain.

Procedure

● Maintain the following entries in the /ARBA/SM_SEQNUM table:

Parameter Description and Example Values

Service Name Name of the SAP Ariba supplier management solutions im­
port service.

Example values:
○ BP_REPLICATE_CONFIRM
○ BP_REPLICATE_REQUEST
○ BP_RELATNSHP_CONFIRM
○ BP_RELATNSHP_REQUEST

Note
SAP Ariba supplier management solutions currently do
not support BP_RELATNSHP_CONFIRM and
BP_RELATNSHP_REQUEST services.

Logical Port The logical port that you configure in SOAMANAGER.

Example value: Polling_Client

Note
If you are using Mediated Connectivity integration
method, leave this parameter blank.

Setting Up SAP Ariba Supplier Lifecycle and Performance

34 CUSTOMER Setting up supplier data integration with SAP ERP
 Parameter Description and Example Values

Sequence Number The sequence number for the last successful import for the
given service.

You can leave this blank. When this parameter is left blank,
SAP Ariba supplier management solutions identify the re­
quest as a first time request and sends records starting with
the first record to the maximum number of records as con­
figured to send in one batch.

The sequence number received from SAP Ariba supplier

management solutions replaces the value for this parame­
ter and is included in the next request.

If the request contains a sequence number, SAP Ariba sup­

plier management solutions send the records since the last
record as indicated by the sequence number.

How to set up SAP ERP credentials in Ariba

Prerequisites

You must be a member of the SM ERP Admin group in order to manage ERP integration settings in the SM Admin
area.

Context

Integration configurations in SM Admin only support shared secret authentication for integration. It does not
support certificate authentication. The shared secret you use here does not have to be the same password you use
for other SAP Ariba integration configurations.

Procedure

1. On the dashboard, click Manage SM Admin .

2. Click ERP Integration.
3. In the Enter ERP Credentials area, enter the following information:

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 35
 ○ The business or ERP system ID of the SAP ERP system, which is the ID the ERP system uses to identify
itself in all messages.
○ The shared secret password you want to use for this integration setup.
4. Click Save.

Configuring the Direct Connectivity integration

method

Direct Connectivity is one of the two integration methods you can use to integrate Ariba supplier management
solutions with SAP ERP. The other method is Mediated Connectivity [page 39].

You use the SOAMANAGER transaction to configure Direct Connectivity.

Note
Before you configure Direct Connectivity, you must configure the Web Services Runtime for SAP ERP on Client
000 and the actual business system clint. For more information, see Configuring the Web Service Runtime on
the SAP Help portal.

How to configure SOAMANAGER

Context

You can use the SOAMANAGER configuration to set up Direct Connectivity for integrating SAP Ariba supplier
management solutions with SAP ERP. This topic explains the SOAMANAGER configuration for the polling client.

To set up SOAMANAGER configuration for the outbound services, repeat these steps with the proxy name and URL
access path that correspond to the DRFOUT and confirmation out services.

Procedure

1. Go to transaction code SOAMANAGER.

2. In the Service Administration tab, click Web Service Configuration.
3. Specify the following Search Criteria:

○ In the Search By pull-down list, select Consumer Proxy.

○ Select Contains from the options.
○ Enter the first few characters of the proxy name that you want to search for and click Search.

The name of the proxy for the inbound integration is /ARBA/CO_POLLING_CLIENT_REQRES.

The list of proxies that match the specified criteria appears.

Setting Up SAP Ariba Supplier Lifecycle and Performance

36 CUSTOMER Setting up supplier data integration with SAP ERP
 4. From the list of proxies, click /ARBA/CO_POLLING_CLIENT_REQRES.

The Details of Consumer Proxy:<proxy name> page appears.

5. From the Configuration tab, click Create Logical Port. and select Manual Configuration.
6. Under General Configuration, specify the following:

○ Logical Port name.

○ Description
○ Check the Logical Port is Default check box.
7. Click Next.
The New Manual Configuration of Logical Port for Consumer Proxy <proxy name> page appears.
8. From the Authentication Settings, select Shared Secret-based authentication, select User ID/Password,
and enter the User ID and the Password in the corresponding fields that appear.

Note
User ID is the name of the sourcing realm and the password is the shared secret that you configured in the
Ariba application.

9. Click Next.

The Transport Bindings page appears.

10. In the Transport Bindings page, specify the following:

○ URL Access Path:

○ /SM/soap/PollingService for the polling client (inbound integration).
○ Computer Name of Access URL: Specify the path to your Ariba application.
For example, [Link].
○ Port Number of Access URL: 443
○ URL Protocol Information: HTTPS
11. Click Next.
The Reliable Messaging (Asynchr.) page appears.
12. In the Reliable Messaging (Asynchr.) page, specify the following:

○ RM Protocol to SAP RM.

Note
Ariba Supplier Management integration with SAP ERP does not support WS-RM .

○ Message ID Protocol to Suppress ID Transfer.

13. Click Finish to save the changes.

Note
When you do a Web Service Ping, you might receive a “Web service ping failed (RC=403). Service Ping
ERROR: Forbidden.” This is expected behavior and does not indicate any error in the SOAMANAGER
configuration.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 37
Next Steps

Repeat the SOAMANAGER configuration for the following proxies:

● CO_MDG_BP_RPLCTRQ for outbound integrations from SAP ERP.

● CO_MDG_BP_RPLCTCO for outbound confirmations from SAP ERP.

Except for the URL access path, the configuration remains the same as that for /ARBA/
CO_POLLING_CLIENT_REQRES.

● For CO_MDG_BP_RPLCTRQ, the URL access path is /SM/soap/BPIntegrationServiceIn.

● For CO_MDG_BP_RPLCTCO, the URL access path is /SM/soap/BPIntegrationServiceInConf.

How to install the SSL client certificate

Context

To enable HTTPS connection between SAP Ariba and SAP ERP, install SSL client certificate.

Procedure

1. Open your browser in Internet Explorer or Google Chrome and download the client certificate for the URL that
you have configured in SOAMANAGER.
2. Click the Secure Lock indicator on the address bar and then click the Connection tab.
3. Click the Certificate information link to download the certificates.
The Certificate dialog box appears.
4. Click the Details tab and then click Copy to File.
The Certificate Export Wizard appears.
5. Follow the steps in the Certificate Export Wizard. Ensure that you select the DER encoded binary X.509
(.CER) option. This option is selected by default.
6. Specify the path where you want to store the certificates. Click Finish.
7. On your ERP system, go to STRUST and click SSL Client SSL Client(Anonymous).
8. Click the Import Certificates button and then choose the path where you exported the certificates.
9. Click Allow and then Continue to download the certificates.
10. Click Add to Certificate List.

You will see a message that you have added the certificates successfully.

Note
Ensure that you save the newly added certificates. This notifies the ICM about the new certificates you have
just imported.

Setting Up SAP Ariba Supplier Lifecycle and Performance

38 CUSTOMER Setting up supplier data integration with SAP ERP
 11. After you have saved the entries in the STRUST, go to the Tcode SMICM.
12. On the Administration menu, click ICM > Exit Soft and then Global.
13. In the Internet Communication Manager dialog box, Do you really want to restart all ICM processes in the
system?, click Yes.
14. On the Administration menu, click ICM > Exit Hard and then Global. Restart the services for the Exit Global.
15. In the Internet Communication Manager dialog box, Do you really want to restart all ICM processes in the
system?, click Yes.
16. Test your connection using SOAMANAGER.
17. On the Search tab, select Consumer Proxy in the Search By pull-down list.
18. Enter first few characters of the proxy name in the Search Pattern text box and select Both Names in the
Field pull-down list.
19. From the list of results, select one or more of the following proxies:
○ /ARBA/CO_POLLING_CLIENT_REQRES for the polling client.
○ CO_MDG_BP_RPLCTRQ for DRFOUT.
○ CO_MDG_BP_RPLCTCO for confirmation out.
[Link] the Configurations tab, click Ping Web Service.

○ In case you see an ICM_HTTP_SSL_ERROR, verify that the SSL certificate is valid and the configuration is
correct.
○ If the connection is successful, you see a message saying the connection is successful.

Configuring the Mediated Connectivity integration

method

Mediated Connectivity is one of the two integration methods you can use to integrate SAP Ariba supplier
management solutions with SAP ERP. The other method is Direct Connectivity [page 36].

Note
SAP Ariba does not provide an out-of-the-box integration option for outbound integration or confirmation out.
The Mediated Connectivity configuration explained in this section is specific to the inbound integration between
SAP Ariba and SAP ERP. For the outbound integration and confirmation out services, you can create custom
configuration scenarios on a dual stack [page 46] or single stack [page 45] system.

Requirements for Mediated Connectivity

The following tasks are prerequisites for configuring Mediated Connectivity:

● Complete the following configuration in the System Landscape Directory (SLD):

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 39
 ○ Ensure that the software component ARIBA_SUPPLIER_MANAGEMENT 2.0 of [Link] is available in
the System Landscape Directory (SLD). You need to import the CIM file from
[Link].
○ (For SAP EPR) Download and configure the SAP_BS_FOUNDATION version that corresponds to the SAP BS
Foundation version that you run as a dependent component of
ARIBA_SUPPLIER_MANAGEMENT 2.0 of [Link].
(For S/4HANA) Download and configure S4CORE as a dependent component of
ARIBA_SUPPLIER_MANAGEMENT 2.0 of [Link].
You can use the Define Prerequisite Software Component Versions button on the Dependencies tab of
the ARIBA_SUPPLIER_MANAGEMENT 2.0 of [Link] page to specify the dependent component.
For more information, see About Configuring the System Landscape Directory in the Ariba Procurement
Solutions Integration Guide for SAP ERP .
● If you have configured a logical port for the proxy, delete or deactivate the logical port in SOAMANAGER and
remove the logical port information from the table [page 34].

How to configure the Integration Scenario

Context

Note
The integration scenario configuration explained in this topic is specific to the inbound integration between SAP
Ariba supplier management solutions and SAP ERP. Ariba does not provide an out-of-the-box integration option
for outbound integration or confirmation out. You might want to create your own custom dual stack [page 46]
or single stack [page 45] configuration scenario for the outbound integration and confirmation out.

Procedure

1. From the SAP NetWeaver Process Integration main page, select Integration Directory > Integration Builder,
and then log in to the Configuration: Integration Builder application.
2. In the Integration Builder page, select Tools > Apply Model from ES Repository.
3. In the first screen of the Transfer Model from ES Repository wizard > Select ES Repository Model and then
click Process Integration Scenario.
4. Click the Name field and then click the Display Input Help pull-down menu and then click Input Help.
5. Select AR_Supplier_Management from the Select Process Integration Scenario from Enterprise Services
Repository screen.
6. Click Apply. The Transfer Model from ES Repository wizard appears. The Namespace and the Software
Component Version is available in the wizard.
7. Click Continue and then click Close. Based on the value you set in the Select Process Integration Scenario
from Enterprise Services Repository field, this completes the export or import configuration scenario .
8. In the Model Configurator, click the Assign Component button.

Setting Up SAP Ariba Supplier Lifecycle and Performance

40 CUSTOMER Setting up supplier data integration with SAP ERP
 9. In the Select Component View for Configuration page, select the Business System Components for A2A
tab to assign components for your SAP ERP.
10. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is present.
11. Click the row under the Communication Component column, then click the Value List drop down and select
Value List ..F4. Select the communication component name, SAP ERP, from the selection list and click Apply.
12. Click the Next Application Component button (the right arrow) to go to the next screen in the window.
13. In the Model Configurator page, choose the Business System Components for A2A tab to assign the
communication component for your Ariba Sourcing solution.
14. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is present.
15. Click the row under the Communication Component column, then click the Value List dropdown and choose
Value List ..F4. Choose the communication component name for the business system from the selection list
and click Apply.
16. Click the Save Settings button to save the changes.
17. In the Model Configurator page, click the Configure Connections button. You must assign a Communication
Channel to set up the connections.
18. In the Connections from Component Assignment tab, click the empty Communication Channel cell
corresponding to the to the business system component value.
19. Click the Value List dropdown and select Value List ..F4. Choose the communication component and click
Apply.
[Link] the Proxy Sender communication channel from the selection list and click Apply.

Note
You require the Proxy Sender communication channel only for a single stack Java machine. If you are using
a dual stack Java machine, the Communication Channel cell must be left blank.

21. Click the New Communication Channel button (the icon at the top left) on the Communication Channels
page to start the Create Communication Channel wizard.
22. Click Continue and in the next page click the Name field, then click the Display Input Help dropdown list and
select Input Help. Select the following Communication Channel Template:
CCT_PollingClient_SOAP_Receiver
23. Click Finish. The Model Configurator window appears.
[Link] the Model Configurator, click the Create Configuration Object button.
25. In the Create Configuration Object window, do the following:

○ Click Generation in the General section.

○ Select the Receiver Determination, and Interface Determination check boxes in the Scope of
Generation section.
[Link] Create New in the Change List for Generated Objects section. The text box already contains an object
name that you can use or modify.
27. Click Start to begin generating objects.
[Link] the object generation is complete, click Apply to save the new configuration settings. Close the log that is
created without saving. You can save it, if required.
[Link] the communication channel you created and specify the following settings:
○ Target URL:[Link]

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 41
 ○ User name and Password for shared secret authentication [page 43]. User name is name of the
sourcing realm.
[Link] the changes and activate the configuration scenario along with its associated objects.

How to configure SSL Certificate for Mediated Connectivity

Context

The SSL client certificate enables the SAP Process Integration to successfully establish an SSL connection with
Ariba Sourcing. To enable HTTPS connection over Mediated Connectivity, configure SSL certificate.

Procedure

1. To download the SSL client certificate from the Ariba Sourcing URL, follow these steps.
1. Open your browser in Internet Explorer or Google Chrome, and download the SSL client certificate for the
URL that you configured in the SOAP communication channel.
2. Click the Secure Lock indicator on the address bar and then, click the Connection tab.
3. Click the Certificate information link to download the certificates. The Certificate dialog box appears.
4. Click the Details tab and then click Copy to File. The Certificate Export Wizard appears.
5. Follow the steps in the Certificate Export Wizard. Ensure that you select the DER encoded binary X.509
(.CER) option. This option is selected by default.
6. Specify the path where you want to store the certificates and click Finish.
2. The SSL client certificates that SOAP Adapter uses to connect to Ariba Sourcing must be stored in the SAP
Process Integration keystore.

3. Go to the SAP Process Integration main page and click NetWeaver Administration Configuration
Management .
4. Click Certificate and Keys.
5. Search for the default keystore TrustedCAs and Click Import Entry button.

Note
Alternatively, you can add the SSL client certificate to the keystore you created for client certificate-based
authentication.

6. Select X.509 Certificate option from the Select Entry Type drop-down list in the Entry Import window.
7. Select file and import.

Setting Up SAP Ariba Supplier Lifecycle and Performance

42 CUSTOMER Setting up supplier data integration with SAP ERP
How to configure shared secret authentication for
Mediated Connectivity

Procedure

1. Open the Configuration Integration Builder from the main SAP Process Integration page.
2. In the Objects tab of the Integration Builder, click Communication Channel.
3. Click Edit button that corresponds to the Communication Channel, and click Configure User Authentication.
4. In the Target URL field, specify the URL of the Supplier Management system. For Example:
○ [Link] management system URL>/SM/soap/PollingService for inbound
integration.
○ [Link] management system URL>/SM/soap/BPIntegrationServiceIn for outbound
integration.
○ [Link] management system URL>/SM/soap/BPIntegrationServiceInConf for
confirmation out.
5. In the User text box, enter the name of the Sourcing realm..
6. In the Password text box, enter the same shared secret that you specified on the Integration Toolkit Security
page of the Ariba application.
7. Save and activate the communication channel.

How to configure the proxy on SAP ERP systems

Procedure

1. Start Transaction SM59 and check if following configurations exist:

○ SAP_PROXY_ESR under HTTP Connections to External Server

○ XI_INTEGRATIONSERVER_<SID> (SID - system identifier) under HTTP Connections to ABAP
System (H Type RFC)
○ LCRSAPRFC under TCP/IP Connections. Specify the program ID similar to the one created under Jco
RFC destinations (LCRSAPRFC_<SID>, where SID - system identifier)
○ SAPSLDAPI under TCP/IP Connections. Specify the program ID similar to the one created under Jco RFC
destinations (SAPSLDAPI_<SID>, where SID - system identifier)
2. Start transaction SLDAPICUST.
3. Enter SAP XI hostname, port, XI user ID, and password.
4. Start transaction SXMB_ADM.
5. Expand Integration Engine> Configuration.
6. Click Integration Engine Configuration to edit global configuration data.
7. In the Global Configuration Data section, enter the following:

○ Role of Business System: Application System

○ Corresponding Integ. Server: dest://<XI_INTEGRATIONSERVER_PPI>

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 43
 This is the same H Type RFC destination mentioned in Step 1.
8. Run SLDCHECK command in SAP ERP.

The PI server appears and the Summary section indicates that the connection to XI is successful.

How to configure the proxy for single stack (Java only)

instances for SAP Process Integration 7.3 and higher

Procedure

1. Start Transaction SM59 and create RFC destination SAP_PROXY_ESR (Type G) under HTTP Connections to
External Server.

1. Under the Technical Settings tab, add AEX (PI Java Stack) server host name and port.
2. In the Path Prefix field, enter /rep.
3. Under the Logon & Security tab, you must ensure that the user is assigned to the role
SAP_XI_REP_SERV_USER.
2. Create an HTTP destination to AEX of Type G (example: PI_AEX) as follows:

1. Under the Technical Settings tab, add AEX (PI Java Stack) server host name and port.
2. In the Path Prefix field, enter /XISOAPAdapter/MessageServlet?ximessage=true.
3. Under the Logon & Security tab, user must be assigned to role SAP_XI_REP_SERV_USER.
3. Start transaction SXMB_ADM.
4. Expand Integration Engine > Configuration.
5. Click Integration Engine Configuration to edit global configuration data.
6. Under Global Configuration Data, enter:

○ Role of Business System: Application System

○ Corresponding Integ. Server: dest://<PI_AEX>
This is the same G Type RFC destination mentioned in step 2.
7. Click Specific Configuration and enter the following:

○ Category: Runtime
○ Parameter: IS_URL
○ Current Value: dest://<PI_AEX>
This is the same G Type RFC destination mentioned in step 2.
8. Start transaction SLDAPICUST.
9. Enter SAP XI hostname, port, XI user ID, and password.
10. Run SLDCHECK command in SAP ERP.

Setting Up SAP Ariba Supplier Lifecycle and Performance

44 CUSTOMER Setting up supplier data integration with SAP ERP
How to create a configuration scenario on a single stack
system

Context

For outbound integration and the confirmation out service from SAP ERP to SAP Ariba supplier management
solutions, you must set up configuration scenarios. This topic contains the steps for creating a configuration
scenario on a single stack system.

Procedure

1. From the SAP Process Integration main page, log in to Integration Directory Integration Builder .
2. Right click the object type Configuration Scenario in the left pane, and click Create from the popup menu.

The Create object page appears.

3. Specify a name for the configuration scenario and click Create.
For example, you may name the configuration scenario for outbound integration as
AR_Supplier_Outbound_DRF, and the one for the confirmation out service as
AR_Supplier_Outbound_Confirmation.

The Edit Configuration Scenario page appears.

4. Go to the the Object tab and add a business system each for SAP ERP and Ariba Supplier Management.
5. Create a communication channel for the sender and specify the following settings.

○ Specify a name for the communication channel. For example, CC_SOAP_Sender.

○ Set the Adapter Type to SOAP.
○ Set the Message Protocol to XI 3.0.
○ Add the communication channel to the Configuration Scenario.
6. Create a communication channel for the receiver and specify the following settings:

○ Specify a name for the communication channel. For example, you may name the receiver communication
channel for outbound integration as CC_DRF_SOAP_Receiver, and the communication channel for
confirmation out as CC_Con_SOAP_Receiver.
○ Set the Adapter Type to SOAP.
○ Set the Message Protocol to SOAP 1.1.
○ Set one of the following values for Target URL:

For outbound integration: [Link] name>/SM/soap/BPIntegrationServiceIn.

For confirmation out: [Link] name>/SM/soap/BPIntegrationServiceInConf.
○ Add the communication channel to the Configuration Scenario.
7. Define Integrated Configuration and configure the following settings.
○ Set the Communication Component to the SAP ERP business system.
○ Set one of the following values for the sender interface:

For outbound integration: BusinessPartnerSUITEBulkReplicateRequest_Out

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 45
 For confirmation out: BusinessPartnerSUITEBulkReplicateConfirmation_Out
○ On the Inbound Processing tab, set the Sender Communication Channel to CC_SOAP_Sender.
○ On the Receiver tab, specify a local rule and set the Ariba Supplier Management business system as the
communication component for the rule.
Set the following values for Receiver Interface:

Integration Type Name Namespace

Outbound integration BusinessPartnerSUITEBulk [Link] name>/SM/ soap/

ReplicateRequest_In BPIntegrationServiceIn

Confirmation out BusinessPartnerSUITEBulk [Link] soap/

ReplicateConfirmation_In BPIntegrationServiceInConf

Note
Interface Operation Mapping is not required.

○ On the Outbound Processing tab, specify the communication channels for receiver.
For example, you may name the receiver communication channel for the outbound integration as
CC_DRF_SOAP_Receiver, and the one for the confirmation out service as CC_Con_SOAP_Receiver.
○ If the Integrated Configuration is not part of the Configuration Scenario, add the Integrated Configuration
to the configuration scenario.

8. Save the objects and the configuration scenario.

9. Click Configuration Scenario on the menu bar and select Activate. The Activate Change list popup appears.
Select the newly created or modified objects and click Activate.

Repeat the steps to create configuration scenarios for both outbound integration and the confirmation out
service.

How to create a configuration scenario on a dual stack

system

Context

For outbound integration and the confirmation out service from SAP ERP to SAP Ariba supplier management
solutions, you must set up configuration scenarios. This topic contains the steps for creating a configuration
scenario on a dual stack system.

Procedure

1. From the SAP Process Integration main page, log in to Integration Directory Integration Builder .

Setting Up SAP Ariba Supplier Lifecycle and Performance

46 CUSTOMER Setting up supplier data integration with SAP ERP
 2. Right click the object type Configuration Scenario in the left pane, and click Create from the popup menu.

The Create object page appears.

3. Specify a name for the configuration scenario and click Create.
For example, you may name the configuration scenario for outbound integration as
AR_Supplier_Outbound_DRF, and the one for the confirmation out service as
AR_Supplier_Outbound_Confirmation.

The Edit Configuration Scenario page appears.

4. Go to the the Object tab and add a business system each for SAP ERP and Ariba Supplier Management.
5. Create a communication channel for the receiver and specify the following settings:

○ Specify a name for the communication channel. For example, you may name the receiver communication
channel for outbound integration as CC_DRF_SOAP_Receiver, and the communication channel for
confirmation out as CC_Con_SOAP_Receiver.
○ Set the Adapter Type to SOAP.
○ Set the Message Protocol to SOAP 1.1.
○ Set one of the following values for Target URL:

For outbound integration: [Link] name>/SM/soap/BPIntegrationServiceIn.

For confirmation out: [Link] name>/SM/soap/BPIntegrationServiceInConf.
○ Add the communication channel to the Configuration Scenario.
6. Create Receiver Determination and configure the following settings:

○ Specify the SAP ERP business system as the communication component for Receiver Determination.
○ For Receiver Determination for the outbound integration, set Sender interface to
BusinessPartnerSUITEBulkReplicateRequest_Out.
○ For Receiver Determination for the confirmation out service, set Sender interface to
BusinessPartnerSUITEBulkReplicateConfirmation_Out.
○ Add a local rule to Receiver Determination and set the Ariba Supplier Management business system as the
communication component for the rule.
○ If the newly-created Receiver Determination is not added to the configuration scenario, add Receiver
Determination to the configuration scenario.
7. Create Interface Determination and configure the following settings:

○ Specify the SAP ERP business system as the communication component.

○ Set the Sender Interface for the outbound integration to
BusinessPartnerSUITEBulkReplicateRequest_Out.
○ Set the Sender Interface for the confirmation out service to
BusinessPartnerSUITEBulkReplicateConfirmation_Out.
○ Set Receiver Communication Component to the Ariba Supplier Management business system.
○ Set the following values for Receiver Interface:

Integration Type Name Namespace

Outbound integration BusinessPartnerSUITEBulk [Link] soap/

ReplicateRequest_In BPIntegrationServiceIn

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 47
 Integration Type Name Namespace

Confirmation out BusinessPartnerSUITEBulk [Link] soap/

ReplicateConfirmation_In BPIntegrationServiceInConf

Note
Interface Operation Mapping is not required.

8. Define Receiver Agreement and configure the following settings: After you create the Receiver Agreement,
specify the Receiver Communication channel CC_DRF_SOAP_Receiver.

○ Set the Sender Communication Component to the SAP ERP business system.
○ Set the Receiver Communication Component to the Ariba Supplier Management business system.
○ Set one of the following values for the Receiver Interface:

BusinessPartnerSUITEBulkReplicateRequest_In for outbound integration.

BusinessPartnerSUITEBulkReplicateConfirmation_In for the confirmation out service.
○ After you define Receiver Agreement, specify the Receiver Communication channel.
For example, you may set the Receiver Communication channel for outbound integration as
CC_DRF_SOAP_Receiver, and Receiver Communication channel for the confirmation out service as
CC_Con_SOAP_Receiver.
9. Save the objects and the configuration scenario.
10. Click Configuration Scenario on the menu bar and select Activate. The Activate Change list popup appears.
Select the newly created or modified objects and click Activate.

Repeat the steps to create configuration scenarios for both outbound integration and the confirmation out
service.

How to replicate Business Partner master data from

SAP Ariba supplier management solutions

Prerequisites

● Maintain values in the /ARBA/SM_SEQNUM table as explained in How to maintain table entries for SAP Ariba
supplier management solutions [page 34].
● Set up Direct Connectivity [page 36] or Mediated Connectivity [page 39] integration method between SAP
Ariba supplier management solutions and SAP ERP.

Setting Up SAP Ariba Supplier Lifecycle and Performance

48 CUSTOMER Setting up supplier data integration with SAP ERP
Context

You can replicate Business Partner master data from SAP Ariba supplier management solutions in SAP ERP and
Master Data Governance.

Tip
Always schedule this program to run at regular intervals. You can use the sm36transaction code to schedule the
program to run in the background at regular intervals.

Procedure

1. From SAP ERP, execute the /ARBA/SM_BUSINESS_PARTNER_PULL program.

The Ariba Supplier Management Business Partner Pull Interface window appears.
2. Choose one or more of the following options:
○ Business Partner Bulk Replicate Request. To import the supplier master data.
○ Business Partner Bulk Replicate Confirmation. To receive confirmation for the supplier master data
import.
3. Click Execute.

Customizing supplier master data integration

SAP Ariba supplier management solutions use MDG business partner interface structure to store supplier master
data. However, SAP Ariba supplier management solutions integration with SAP ERP supports extension of the
business partner data structure to enable you to use custom fields to address your specific requirements.

The following structures have been modified to include the GenericCustomField element and the
genericCustomFieldListCompleteTransmissionIndicator attribute:

● BPSUITERplctReqBkDets for bank details.

● BPSUITERplctReqAcctgInfo for accounting information.
● BPSUITERplctReqBP for business partner information.
● BPSUITERplctReqSuplr for supplier information.

The GenericCustomField element contains the following attributes:

Attribute Name Attribute Type Description

Name GenericCustomFieldName Name of the field. This is both the default

display name and also the identifier for
the field.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 49
Attribute Name Attribute Type Description

Type GenericCustomFieldType General type of the field, selected from

the GenericCustomerFieldType
enumerated values. If it is not specified
or not recognized, the type defaults to
Text.

Title GenericCustomFieldTitle Display title of the field.

Description GenericCustomFieldDescription Description of the field.

Language Code LanguageCode SAP Language code for the title and de­
scription of the field. If no value is speci­
fied, it defaults to en.

Table GenericCustomFieldMappingName Sender's table name where the value of

the mapped field is stored.

Field GenericCustomFieldMappingName Sender's field name in the table where

the value of the mapped field is stored.

Check Table GenericCustomFieldMappingName Sender's name of the check table used

to validate the code values.

Receiver Table GenericCustomFieldMappingName Receiver's table name, if any, where the

value of the mapped field is stored. recei­
verTable and receiverField should ap­
pear together, or not at all.

Receiver Field GenericCustomFieldMappingName Receiver's field name in the table where

the value of this mapped field is stored.
receiverTable and receiverField should
appear together, or not at all.

Receiver Check Table GenericCustomFieldMappingName Receiver's name of the check table used
to validate the code values.

Maximum Length GenericCustomFieldMappingName Maximum length of the value string in

characters, for input validation, if
type="Text".

Minimum Length NumberValue Minimum length of the value string in

characters, for input validation, if
type="Text".

Pattern NumberValue Pattern A regular expression that must match

valid input, if type="Text".

Total Digits NumberValue Maximum total digits, for input valida­

tion, if type="Decimal".

Setting Up SAP Ariba Supplier Lifecycle and Performance

50 CUSTOMER Setting up supplier data integration with SAP ERP
 Attribute Name Attribute Type Description

Fraction Digits NumberValue Maximum digits in the fractional part, for

input validation, if type="Decimal".

Maximum Inclusive Inclusive Maximum decimal value, for input valida­

tion, if type="Decimal".

Minimum Inclusive Inclusive Minimum decimal value, for input valida­

tion, if type="Decimal".

Display Restrictions GenericCustomFieldRestrictions A comma separated list of display con­

texts in which this field should be dis­
played.

Edit Restrictions GenericCustomFieldRestrictions A comma separated list of display con­

texts in which this field should be edita­
ble.

If you need to extend your business partner data to include these custom fields, you can implement the following
BAdIs of the enhancement spot MDG_SE_SPOT_BPBUPA:

● MDG_SE_BP_BULK_REPLRQ_IN to extend the business partner data while creating the record in ERP.
● MDG_SE_BP_BULK_REPLRQ_OUT to extend the business partner data in ERP while sending to Ariba Supplier
Management.

Customizations using the MDG_SE_SPOT_BPBUPA enhancement spot are specific to the Business Partner tables in
SAP ERP.

You can implement the BAdI CVI_CUSTOM_MAPPER to replicate these extensions in the vendor master data tables.
The CVI_CUSTOM_MAPPER BAdI enables you to map customizations in business partner tables to vendor master
data tables.

Related Information

ABAP example code for processing incoming GenericCustomField data [page 51]

ABAP example code for processing incoming

GenericCustomField data

The following example contains a sample ABAP code for processing incoming GenericCustomField data.

METHOD if_mdg_se_bp_bulk_replrq_in~inbound_processing.
***Implementation for customer data
***Local Declaration for Internal table
DATA: lt_ariba_generic_data TYPE /arba/generic_custom_fiel_tab1.
***Local Declaration for Work Area

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 51
 DATA: ls_ariba_generic_data TYPE /arba/generic_custom_field.
***Local Declaration for variable for generic fields
DATA: lv_sup_creator TYPE string,
lv_sup_sponsor TYPE string.
***Field symbol declaration
FIELD-SYMBOLS:<fs_org_data> TYPE bus_ei_bupa_central_data,
<fs_org_datax> TYPE bus_ei_bupa_central_data_xflag.
***Assigment of genereic field
lt_ariba_generic_data = in-business_partner-supplier-/arba/generic_custom_field.
***Assign the field symbol
ASSIGN out-partner-central_data-common-data TO <fs_org_data>.
ASSIGN out-partner-central_data-common-datax TO <fs_org_datax>.
***Loop at internal table for custom field.
LOOP AT lt_ariba_generic_data INTO ls_ariba_generic_data.
IF ls_ariba_generic_data-name EQ 'SupplierCreator'.
lv_sup_creator = ls_ariba_generic_data-content.
ENDIF.
IF ls_ariba_generic_data-name EQ 'SupplierSourcingSponsor'.
lv_sup_sponsor = ls_ariba_generic_data-content.
ENDIF.
ENDLOOP.
***Updating the value into the MDG_BS_BP_S_EXTERN
IF lv_sup_creator IS NOT INITIAL OR lv_sup_sponsor IS NOT INITIAL.
IF <fs_org_data> IS ASSIGNED.
<fs_org_data>-zsup_creator = lv_sup_creator.
<fs_org_data>-zsup_sponsor = lv_sup_sponsor.
ENDIF.
IF <fs_org_datax> IS ASSIGNED.
IF <fs_org_data>-zsup_creator IS NOT INITIAL.
<fs_org_datax>-zsup_creator = abap_true.
ENDIF.
IF <fs_org_data>-zsup_sponsor IS NOT INITIAL.
<fs_org_datax>-zsup_sponsor = abap_true.
ENDIF.
ENDIF.
ENDIF.
ENDMETHOD.

The LOOP AT lt_ariba_generic_data INTO ls_ariba_generic_data code creates a loop for the list of
GenericCustomField data in the structure generated from the SOAP WSDL. You could add your processing at
this point in the code to check for GenericCustomField records with specific names and process each of the
custom fields appropriately.

You can choose which of the custom fields you need to implement and at which extension [page 49] point. You can
specify the name of the field and also specify to which fields in your SAP Ariba supplier management solution the
custom fields you add map to.

To create custom fields to SAP Ariba supplier management solutions, you can implement the
BAdIMDG_SE_BP_BULK_REPLRQ_OUT, which extends the master data when SAP ERP sends the data to the SAP
Ariba supplier management solution.

How to create custom message mappings in SAP Process

Integration

Context

To extend the business partner data, you can create custom message mappings in the SAP Process Integration.

Setting Up SAP Ariba Supplier Lifecycle and Performance

52 CUSTOMER Setting up supplier data integration with SAP ERP
Procedure

1. From the SAP Process Integration main page, click Enterprise Service Repository.
2. Select the Software Component Version ARIBA_SUPPLIER_MANAGEMENT 2.0 of [Link].
3. Select the customization namespace [Link]
4. Right click and create new mapping and operation mapping for customization.
5. Customize the mapping to suit your requirements, create new message mapping by assigning the request and
source message type.
6. Save the changes and activate the mapping.
7. Assign the message mapping in Operation Mapping.
8. Save and activate the Operation mapping.
9. Go to the Integration Directory and click Integration Builder.
10. Click the Configuration Scenario for Supplier Management.
11. Select Interface Determination and click the Edit icon.
12. Assign the operation mapping as per the customization in Interface Determination.
13. Save the changes and activate Interface Determination.

Setting default supplier field values

Default field values allow you to specify initial values for fields when a supplier created in an SAP Ariba supplier
managmenet solution is first sent to SAP ERP.

These default settings are useful for making sure that required fields are populated with initial values and for
setting values for fields that aren't mapped from forms and questionnaires. For example, you might want to set a
default general ledger account number for the supplier because it is a requirement in the ERP and, since the
category or supplier managers who approve supplier creation do not have access to that information, it is not a
question on the supplier request. Users in SAP ERP can update these default values as necessary after the initial
supplier synchronization.

Note
SAP ERP uses a category code of 2 for business partner objects that are suppliers; SAP Ariba supplier
management solutions automatically set this default value.

The Defaults area of SM Admin provides samples and allows you to download your current default settings and
upload new default settings.

There are two sample files available:

● A sample file, Default_properties_sample.csv, with the names of all of the fields for which you can set
defaults in the name column. The file also has a value column, and you can use the sample to construct your
Default_properties.csv file. The file includes a name/value pair setting
[Link] to 2.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 53
● A sample file, Default_properties_special_names.csv, with the valid variables you can use to set
default field values. For example, if you set a field default to ${[Link]}, when the supplier data is sent
to SAP ERP, the field value is set to the current date.

Default_properties.csv

Default field values specify the initial values set for supplier fields. You import data defining default field values in
the Defaults area of SM Admin using Default_properties.csv.

Field Description

name The name of the field. To obtain a list of valid field names, ex­
port the sample file from the Defaults area of SM Admin.

value The default value to set for the field. This can be a concrete
value or a valid variable. To obtain a list of valid variables, ex­
port the sample file from the Defaults area of SM Admin.

The following example shows lines of the Default_properties.csv file:

name,value
[Link],2
[Link],33001
[Link],${[Link]}

How to set up supplier data synchronization

Setting up supplier data synchronization involves choosing manual or automatic synchronization and specifying
the supplier status at which synchronization occurs.

Prerequisites

You must be a member of the SM ERP Admin group in order to set up supplier synchronization.

Context

Automatic synchronization occurs automatically when the supplier reaches the specified status and is designed to
synchronize all suppliers of that status in the SAP Ariba supplier management solution database with the ERP.

Setting Up SAP Ariba Supplier Lifecycle and Performance

54 CUSTOMER Setting up supplier data integration with SAP ERP
With manual synchronization, when the supplier reaches the specified status, an ERP synchronization link appears
in the upper right corner of the supplier 360° view. A category or supplier manager clicks the link when they are
ready to transact with the supplier. Otherwise, suppliers of that status are not synchronized with the ERP.

Procedure

1. On the dashboard, click Manage SM Admin .

2. Click ERP integration.
3. In the Initial supplier synchronization, choose either Automatic synchronization or Manual
synchronization.
4. Choose one of the following statuses for initial synchronization:

Status Description

Not Invited The supplier request has been approved and the supplier is
created in the SAP Ariba supplier management solution da­
tabase, but the supplier has not been invited to register yet.

Invited The supplier has been invited to register. (Manual synchro­

nization only.)

In Registration The supplier has submitted the registration questionnaire.

(Manual synchronization only.)

Pending Approval The approval flow for the registration has started and there
is one final approval pending. (Manual synchronization
only.)

Registered The supplier registration has been finally approved.

5. Click Save.

How to monitor errors in SAP ERP

You can use one of the following transaction codes to monitor errors that might occur in the SAP Ariba supplier
management solution integration with SAP ERP:

● SLG1 [page 56]

● SRT_TOOLS [page 56]
● SXMB_MONI [page 56]

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier data integration with SAP ERP CUSTOMER 55
SLG1

1. Go to transaction code SLG1.

The Analyse Application Log screen appears.
2. In the Object field, enter /ARIBA/SM.
3. In the Subobject field, enter /ARIBA/SUB_SM.
4. Specify the filters.
5. Click the Execute icon.
The Display Logs screen lists the logs associated with the Ariba Supplier Management integration with SAP
ERP.

SRT_TOOLS

1. Go to transaction code SRT_TOOL.

The SOA Runtime Tools window appears.
2. Click SOA Runtime Tools Monitoring Web Service Utilities: Message Monitor .
The Web Service Utilities: Message Monitor window appears.
3. Specify the filters and click the Execute icon.
The Web Service Utilities: Message Monitor page lists the errors, if any.

SXMB_MONI

You can use the SXMB_MONI transaction code to view errors occurred on SAP Process Integration when you use
the Mediated Connectivity integration method.

Monitoring integration errors in SAP Ariba supplier

management solutions
The ERP integration status area of SM Admin shows detailed status information for inbound and outbound
integration messages with SAP ERP.

You can filter the status list by message direction, time range, status, and message type.

To reprocess a failed message, click Reprocess.

Setting Up SAP Ariba Supplier Lifecycle and Performance

56 CUSTOMER Setting up supplier data integration with SAP ERP
Importing SAP Ariba Supplier Lifecycle and
Performance data

There are two different types of SAP Ariba Supplier Lifecycle and Performance data: site master data, imported in
Ariba Administrator, and supplier-specific data, imported in the SM Manager.

Importing site master data for SAP Ariba Supplier Lifecycle and Performance [page 57]

Importing SAP Ariba Supplier Lifecycle and Performance supplier data [page 63]

Importing site master data for SAP Ariba Supplier

Lifecycle and Performance
You import site master data for SAP Ariba Supplier Lifecycle and Performance using the Ariba Administrator Site
Manager workspace.

This section discusses only the master data that is specific to SAP Ariba Supplier Lifecycle and Performance. The
Ariba Common Data Import and Administration Guide describes all other site master data, as well as site
administration, in detail.

Note
The information on importing supplier data in the Ariba Common Data Import and Administration Guide, and the
data import tasks in Ariba Administrator for supporting supplier organizations and profiles, apply only to sites
that do not use SAP Ariba Supplier Lifecycle and Performance. In sites with SAP Ariba Supplier Lifecycle and
Performance, there is a separate process for importing supplier data [page 63].

Assigning users to supplier processes by commodity and region [page 57]

Defining preferred supplier levels [page 59]

How to import your data [page 60]

How to import your translation data [page 62]

Language values for defining translations [page 62]

Assigning users to supplier processes by commodity and

region
Assigning users to supplier processes involves importing a CSV file that defines user assignments to commodities,
regions, and project groups.

For example, you can assign John Smith to computer equipment in North America as a project owner. He is a
member of Supplier Request Manager user group, and the approval flow for the supplier request form makes

Setting Up SAP Ariba Supplier Lifecycle and Performance

Importing SAP Ariba Supplier Lifecycle and Performance data CUSTOMER 57
project owners into approvers. When someone in your company submits a request to use a new supplier for
computer equipment in North America, John Smith automatically becomes an approver for that request.

You an assign a user to a combination of commodities, regions, and project groups. You can also assign a user to
only a region (by specifying the region and using All for region) or to only a commodity (by specifying the
commodity and using All for commodity).

Note
● When you assign a user to a commodity or region in one level of the hierarchy, that user is also assigned to
all commodities and regions below it. For example, if you assign John Smith to North America, he is
assigned all three countries in North America and to all cities and states in those countries.
● When you assign a user to a project group, that group must also exist in the appropriate template.

You use the Import Enterprise user category region data import task to specify user assignments to categories
and regions. The task reads from the [Link] file, which contains the following fields:

Field Description

ProjectGroup The name of the project group to which the user is assigned.

[Link] The code for the commodity to which the user is assigned.

[Link] The domain of the commodity code; for example, unspsc.

[Link] The region to which the user is assigned

[Link] The user's username.

[Link] The user's password adapter, usually

PasswordAdapter1.

The following example shows lines of the [Link] file, as well as the mandatory header:

UTF-8
ProjectGroup,[Link],[Link],[Link],[Link]
Name,[Link]
Legal,All,unspsc,North America,tjones,PasswordAdapter1
Project Owner,4213,unspsc,All,ljenkins,PasswordAdapter1
Project Owner,All,unspsc,Los Angeles,grooney,PasswordAdapter1
Project Owner,All,unspsc,San Diego,grooney,PasswordAdapter1

To assign a single user to multiple commodities or regions, you must create separate rows, one for each
assignment. This example uses two rows to assign the same user, George Rooney, as project owner for all
commodities in Los Angeles and San Diego.

After you have defined assignments in [Link], you import it into your site [page
60].

Setting Up SAP Ariba Supplier Lifecycle and Performance

58 CUSTOMER Importing SAP Ariba Supplier Lifecycle and Performance data
Defining preferred supplier levels

Preferred supplier levels indicate the degree to which your organization prefers one supplier over another for a
given category or region.

Examples of preferred supplier levels include number ranges (such as 1-5) or text labels (High, Medium, Low).

If your organization designates preferred suppliers, you must define their levels. If your preferred levels are text
labels, you must also define translations for each language you use in your site.

Defining the preferred supplier levels

You use the Import Preferred Supplier Level data import task to define preferred supplier levels. The task reads
from the [Link] file, which includes the following fields:

Field Description

Name The name of the preferred supplier level.

UniqueName A unique identifier for the preferred supplier level.

Note
If you plan to set up sourcing event templates, to automati­
cally invite preferred suppliers to sourcing events that
match their categories and regions, you must make sure
that your preferred level uses a UniqueName of 1. Only
suppliers with a preferred level that maps to 1 are automati­
cally invited to sourcing events.

The following example shows lines of the [Link] file, as well as the mandatory header:

UTF-8
Name,UniqueName
Gold,1
Silver,2
Bronze,3

After you have defined preferred supplier levels in [Link], you import it into your site
[page 60].

Defining translations for the preferred supplier levels

You use the Import Translations for Preferred Supplier Level data import task to define preferred supplier levels.
The task reads from the [Link] file, which includes the following fields:

Setting Up SAP Ariba Supplier Lifecycle and Performance

Importing SAP Ariba Supplier Lifecycle and Performance data CUSTOMER 59
Field Description

Name The name of the preferred supplier level.

UniqueName A unique identifier for the preferred supplier level.

Language The language of the name.

The following example shows lines of the [Link] file for supplier level translation, as
well as the mandatory header:

UTF-8
Name,UniqueName
Oro,1,Spanish
Or,1,French
Ouro,1,BrazilianPortuguese

After you have defined preferred supplier level translations in [Link], you import it
into your site [page 62].

Related Information

Language values for defining translations [page 62]

How to import your data

After you enter your data in the CSV files, you can import it using the data import tasks available from Site
Manager in Ariba Administrator.

Prerequisites

You must be a member of the Customer Administrator group to import data into a site.

Context

These steps are for importing data that does not require translation.

Setting Up SAP Ariba Supplier Lifecycle and Performance

60 CUSTOMER Importing SAP Ariba Supplier Lifecycle and Performance data
Procedure

1. Log in to your site using your administrator username and password.

2. On the dashboard, click Manage Administrator .

3. In Ariba Administrator, click Site Manager, and then click Data Import/Export.
4. Select the type of data import operation you want to perform. The data import operation you choose
determines exactly how the data is imported.

The maximum number of objects that can be removed from the database at one time is 160,000. This number
is controlled by a system parameter. If this number is exceeded, a warning message appears.

The following table describes import operations. If a data import task does not support a particular data
import operation, that operation is not available.

Import Operation Description

Load Creates and modifies objects in the database using values in the data file. If an object in the data
file does not already exist in the database, it is created. If an object in the data file already exists in
the database, it is modified using the value in the data file.

Create Creates new objects in the database using values in the data file. If an object in the data file al­
ready exists in the database, it is not modified.

Update Only Modifies existing objects only in the database using values in the data file. If an object in the data
file does not already exist in the database, it is not created. If you do not want to modify a particu­
lar object, do not include it in the data file.

Deactivate Deactivates objects in the database based on objects in the data file. If you do not want to deacti­
vate a particular object, do not include it in the data file.

5. Enter the location of the relevant file, or click Browse to find and select the file.
6. Click OK to import your data, or click Cancel to exit without importing your data.
7. Click Refresh Status on the Data Import/Export page to view the current status of the data import.

Next Steps

For detailed status information, click the link in the Status column.

Related Information

How to import your translation data [page 62]

Setting Up SAP Ariba Supplier Lifecycle and Performance

Importing SAP Ariba Supplier Lifecycle and Performance data CUSTOMER 61
How to import your translation data
After you enter your translation data in the appropriate CSV files, you can import it using the data import tasks
available from Site Manager in Ariba Administrator.

Prerequisites

You must be a member of the Customer Administrator group to import translation data.

Procedure

1. Log in to your site using your administrator username and password.

2. On the dashboard, click Manage Administrator .

3. In Ariba Administrator, choose Site Manager Data Import/Export .

4. Click Import next to the data import task you want to run.
5. Choose the language you want to import from the dropdown menu. Choose All to import translations for all
the languages defined in the CSV.
6. Enter the location of your supplemental workbook or CSV file, or click Browse to find and select your CSV file.
7. Click OK to import your translations, or click Cancel to exit without importing your translations.
8. Click Refresh Status on the Data Import/Export page to view the current status of the data import.

Next Steps

For detailed status information, click the link in the Status column.

Language values for defining translations

The following are valid values for the Language field in CSV files that define translations for preferred supplier
levels:

● SimplifiedChinese
● TraditionalChinese
● English
● French
● German
● Italian
● Japanese

Setting Up SAP Ariba Supplier Lifecycle and Performance

62 CUSTOMER Importing SAP Ariba Supplier Lifecycle and Performance data
● BrazilianPortuguese
● Swedish
● Korean
● Russian
● Spanish
● Danish
● Norwegian
● Turkish
● Polish
● Hungarian
● Greek
● Romanian

Importing SAP Ariba Supplier Lifecycle and

Performance supplier data
You import SAP Ariba Supplier Lifecycle and Performance supplier data in SM Admin.

You can download samples of all SAP Ariba Supplier Lifecycle and Performance data files from the Imports/
Exports area of SM Admin. On the dashboard, click Manage SM Admin to access this area.

How to obtain existing Ariba supplier data

If you already have an Ariba solution, you need to add your existing suppliers to the database. Obtaining existing
Ariba supplier data involves using the Data Import/Export task in Ariba Administrator.

Prerequisites

You must be a member of the Customer Administrator or Supplier/Customer Manager group to export supplier
data in Ariba Administrator.

Context

Existing Ariba supplier data is exported in a [Link] file. That file contains two CSV
files: SupplierOrganization_Export.csv, which contains data on the suppliers, and
SupplierOrganizationOrganizationIdPart_Export.csv, which maps supplier domain IDs. For details on
the fields in these files, click Download Data Dictionary in the Ariba Administrator Site Manager Data
Import/Export task.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Importing SAP Ariba Supplier Lifecycle and Performance data CUSTOMER 63
Procedure

1. Perform one of the following actions:

○ If your site includes Ariba procurement solutions, on the dashboard, click Manage Core
Administration .
○ If your site does not include Ariba procurement solutions, n the dashboard, click Manage
Administration .

2. Choose Site Manager Data Import/Export .

3. Click the Export tab.
4. Locate the Export Supplier Organizations (CSV) data export task and click Export.
5. Save the exported ZIP file to the location of your choice.

Next Steps

After exporting the existing Ariba suppliers from your site, you import them into the supplier database [page 64].

How to import supplier data

Importing supplier-related data makes it available for supplier management, risk, and procurement activities.

Prerequisites

You must be a member of the SM ERP Admin, SM Ops Admin, Supplier Risk Manager, or Customer
Administrator group to import supplier data in SM Admin.

To import existing Ariba suppliers, you must first obtain the data using a data export task in your site [page 63].

The suppliers referenced by supplier data files, such as supplier contacts, preferred supplier lists, and supplier
factory data, must already exist in the database before you import the files, either as a result of importing suppliers
first or because they were created manually in the user interface. The exception to this rule is for supplier
qualification data, which offers an option to create the suppliers referenced in the file if they do not already exist.

Procedure

1. On the dashboard, click Manage SM Admin .

2. Click Imports/Exports.

Setting Up SAP Ariba Supplier Lifecycle and Performance

64 CUSTOMER Importing SAP Ariba Supplier Lifecycle and Performance data
3. Select the type of data you want to import on the dropdown menu. Depending on your solution, you might or
might not use some of these data types:

This data type... Imports...

Suppliers Suppliers from outside SAP Ariba using [Link].

Supplier from Sourcing Suppliers exported from SAP Ariba solutions using
[Link].

Supplier Contacts Supplier contacts using [Link].

Supplier qualification data A list of supplier qualifications by commodity and code and
region using [Link].

Preferred Supplier list data A list of preferred suppliers by commodity code and region
using [Link].

Supplier factory data Information about supplier factories using

[Link].I

Purchasing org data The purchasing organizations associated with the supplier,
including defaults, using
[Link].

Custom display names Custom labels for registration and qualification statuses us­
ing [Link].

Primary Supplier Manager The names of primary and alternative internal contacts for
suppliers using [Link].

4. (Optional) For supplier qualification data, check Create supplier if required to add any suppliers in the data
that don't already exist to the database.
5. On the Upload tab, click Browse and navigate to the file you want to import.
6. Click Upload.

Next Steps

Click the Upload Summary tab to view the status of your data import.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Importing SAP Ariba Supplier Lifecycle and Performance data CUSTOMER 65
[Link]
You import supplier data using the Suppliers file type and [Link].

Field Description Required?

erpVendorId The ID of the supplier in the integrated Yes

ERP system.

masterVendorId The ID of the supplier in the vendor mas­ No

ter record.

sourceSystem The system in which the supplier was No

created; for example, SM for Ariba or
SAP for SAP ERP.

name1 The primary name of the supplier. Yes

name2 An alternate name for the supplier. No

name3 A second alternate name for the sup­ No

plier.

name4 A third alternate name for the supplier. No

phone The supplier phone number. No

fax The supplier fax number. No

line1 The first line of the supplier address. At least one of the following fields is re­
quired: line1, line2, line3, city,
state, postalCode, or
countryCode

line2 The second line of the supplier address. At least one of the following fields is re­
quired: line1, line2, line3, city,
state, postalCode, or
countryCode

line3 The third line of the supplier address. At least one of the following fields is re­
quired: line1, line2, line3, city,
state, postalCode, or
countryCode

postalCode The postal code of the supplier address. At least one of the following fields is re­
quired: line1, line2, line3, city,
state, postalCode, or
countryCode

Setting Up SAP Ariba Supplier Lifecycle and Performance

66 CUSTOMER Importing SAP Ariba Supplier Lifecycle and Performance data
 Field Description Required?

poBox The post office box number of the sup­ No

plier address.

city The city of the supplier address. At least one of the following fields is re­
quired: line1, line2, line3, city,
state, postalCode, or
countryCode

state The state or province of the supplier ad­ At least one of the following fields is re­
dress. quired: line1, line2, line3, city,
state, postalCode, or
countryCode

countryCode The two-character ISO country code of At least one of the following fields is re­
the country for the supplier address. quired: line1, line2, line3, city,
state, postalCode, or
countryCode.

Either partyTaxID or countryCode

is required.

taxIdentificationNumberType A code that identifies the type of the tax No

Code identification number.

partyTaxID The supplier party tax ID. Either partyTaxID or countryCode

is required

longPartyTaxID The long format of the supplier party tax No

ID.

dunsId The supplier Dun & Bradstreet D-U-N-S No

number.

[Link]

You import supplier contact (supplier user) data using the Supplier Contacts data type and
[Link]. To specify the same supplier as preferred for multiple categories or regions, add a
unique row for each combination of category, region, and supplier

Field Description Required?

erpVendorId The ID of the supplier in the integrated Yes

ERP system.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Importing SAP Ariba Supplier Lifecycle and Performance data CUSTOMER 67
Field Description Required?

sourceSystem The system in which the supplier was Yes

created; for example, SM for Ariba or
SAP for SAP ERP.

firstName The first name of the supplier contact. No

lastName The last name of the supplier contact. No

telephone The supplier contact's telephone num­ No

ber.

email The supplier contact's email address, Yes

which is also the supplier contact's user­
name.

type The type of the supplier contact, which No

must match one of the types defined for
your site.

title The supplier contact's title. No

categories The commodities for which the supplier No

contact is responsible.

regions The regions for which the supplier con­ No

tact is responsible.

isPrimary A Boolean value that specifies whether Yes

or not the supplier contact is the primary
contact for the supplier. Valid values are
TRUE and FALSE.

[Link]
Supplier qualification data is used to designate supplier qualification status in the guided buying feature for Ariba
Procure-to-Pay, and for suppliers that were created outside of SAP Ariba Supplier Lifecycle and Performance. You
import data about suppliers' qualification status using the Supplier qualification data file type and
[Link]. To specify the same supplier as qualified for multiple categories or regions, add
a unique row for each combination of category, region, and supplier.

Setting Up SAP Ariba Supplier Lifecycle and Performance

68 CUSTOMER Importing SAP Ariba Supplier Lifecycle and Performance data
 Field Description Required?

sourceSystem For existing Ariba suppliers, if the Yes for existing suppliers.
SupplierOrganizationOrganiz
For suppliers that do not already exist in
ationIdPart_Export.csv file con­
the database, if you check the Create
tains a Domain and Value entry for the supplier if required option during data
supplier, use the Domain in this field. If import, you can leave this field blank.
not, use SM. The supplier is added with the default SM
source system.
For suppliers imported from outside
Ariba, use the sourceSystem speci­
fied in [Link].

vendorId For existing Ariba suppliers, if the Yes

SupplierOrganizationOrganiz
ationIdPart_Export.csv file con­
tains a Domain and Value entry for the
supplier, use the Value in this field. If
not, use the [Link].

For suppliers imported from outside

Ariba, use the erpVendorId specified
in [Link].

category The commodity code of the commodity No

for which qualification status applies.
This code must match the commodity
master data loaded in your site.

region The code for the region in which the No

qualification status applies. This code
must match the region master data
loaded in your site.

status The supplier's qualification status. The Yes

following are valid status values:

● NotQualified
● QualificationStarted
● InQualification
● PendingQualificationAppr
oval
● PendingResubmit
● QualificationRestricted
● QualificationRejected
● Disqualified
● Qualified
● Expired

Setting Up SAP Ariba Supplier Lifecycle and Performance

Importing SAP Ariba Supplier Lifecycle and Performance data CUSTOMER 69
Field Description Required?

startDate The date from which the supplier qualifi­ No

cation status is valid for the specified
commodity and region.

endDate The date to which the supplier qualifica­ No

tion status is valid for the specified com­
modity and region.

[Link]

Preferred supplier data is used to designate preferred suppliers in the guided buying feature for Ariba Procure-to-
Pay and Ariba Procure-to-Order solutions and in SAP Ariba Supplier Risk, and for suppliers that were created
outside of Ariba in SAP Ariba Supplier Lifecycle and Performance. You import data about your list of preferred
suppliers using the Preferred Supplier list data file type and [Link]. To specify the same
supplier as preferred for multiple categories, add a unique row for each combination of category and supplier.

Field Description Required?

sourceSystem For existing Ariba suppliers, if the Yes

SupplierOrganizationOrganiz
ationIdPart_Export.csv file con­
tains a Domain and Value entry for the
supplier, use the Domain in this field. If
not, use SM.

For suppliers imported from outside

Ariba, use the sourceSystem speci­
fied in [Link].

vendorId For existing Ariba suppliers, if the Yes

SupplierOrganizationOrganiz
ationIdPart_Export.csv file con­
tains a Domain and Value entry for the
supplier, use the Value in this field. If
not, use the [Link].

For suppliers imported from outside

Ariba, use the erpVendorId specified
in [Link].

category The commodity code of the commodity No

for which the supplier is preferred. This
code must match the commodity master
data loaded in your site.

Setting Up SAP Ariba Supplier Lifecycle and Performance

70 CUSTOMER Importing SAP Ariba Supplier Lifecycle and Performance data
 Field Description Required?

region The code for the region in which the sup­ No

plier is preferred. This code must match
the region master data loaded in your
site.

status The supplier's preferred status level. Yes

If your solution includes SAP Ariba Sup­

plier Lifecycle and Performance, this sta­
tus level must be one of the
UniqueName values in the master data
used to define preferred supplier levels
in your site.

startDate The date from which the supplier is pre­ No

ferred for the specified commodity and
region.

endDate The date to which the supplier is prefer­ No

red for the specified commodity and re­
gion.

Related Information

Defining preferred supplier levels [page 59]

Setting Up SAP Ariba Supplier Lifecycle and Performance

Importing SAP Ariba Supplier Lifecycle and Performance data CUSTOMER 71
[Link]
Supplier factory data is used in direct material sourcing. You import supplier factory data using the Supplier
factory data file type and [Link].

Field Description Required?

vendorId For existing Ariba suppliers, if the Yes

SupplierOrganizationOrganiz
ationIdPart_Export.csv file con­
tains a Domain and Value entry for the
supplier, use the Value in this field. If
not, use the [Link].

For suppliers imported from outside

Ariba, use the erpVendorId specified
in [Link].

sourceSystem For existing Ariba suppliers, if the Yes

SupplierOrganizationOrganiz
ationIdPart_Export.csv file con­
tains a Domain and Value entry for the
supplier, use the Domain in this field. If
not, use SM.

For suppliers imported from outside

Ariba, use the sourceSystem speci­
fied in [Link].

factoryName The name of the factory. No

factoryId A unique identifier for the factory. Yes

factoryType The factory type. No

factoryClassification The classification category for the fac­ No

tory.

businessImpact The factory business impact. No

factoryMainContact The name of the main contact at the fac­ No

tory.

factoryMainContactEmail The email address of the main contact at No

the factory.

factoryMainContactPhone The phone number of the main contact No

at the factory.

Setting Up SAP Ariba Supplier Lifecycle and Performance

72 CUSTOMER Importing SAP Ariba Supplier Lifecycle and Performance data
 Field Description Required?

factoryContact2 The name of a secondary contact at the No

factory.

factoryContact2Email The email address of a secondary con­ No

tact at the factory.

factoryContact2Phone The phone number of a secondary con­ No

tact at the factory.

addressName The name assigned to the factory ad­ No

dress specified in this file (for example,
Headquarters).

phone1 The main phone number of the factory. No

phone2 A secondary phone number for the fac­ No

tory.

fax The fax number for the factory. No

line1 The first line of the factory address. No

line2 The second line of the factory address. No

line3 The third line of the factory address. No

city The factory address city. No

state The factory address state. No

postalCode The factory address postal code. No

poBox The factory address post office box. No

countryCode The country code for the factory address No

country.

region The factory address region. No

province The factory address province. No

district The factory address district. No

languageCode The ISO language code for the factory No

address.

purchasingOrgCode The ID of the purchasing organization as­ No

sociated with the factory.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Importing SAP Ariba Supplier Lifecycle and Performance data CUSTOMER 73
Field Description Required?

url The factory website URL. No

categoryCode The commodity code for the commdity No

supplied by the factory.

materialId The material master ID for the commod­ No

ity supplied by the factory.

materialDescription The material master description for the No

commodity supplied by the factory.

internalMainContact The name of the main contact at your No

company who is responsible for the fac­
tory.

internalMainContactEmail The email address of the main contact at No

your company who is responsible for the
factory.

internalQualityManager The name of the quality manager at your No

company who is responsible for the fac­
tory.

internalQualityManagerEmail The email address of the quality man­ No

ager at your company who is responsible
for the factory.

internalTechnicalContact The name of the technical contact at No

your company who is responsible for the
factory.

internalTechnicalContactEma The email address of the technical con­ No

il tact at your company who is responsible
for the factory.

additionalInternalContact The name of a secondary contact at your No

company who is responsible for the fac­
tory.

additionalInternalContactEm The email address of a secondary con­ No

ail tact at your company who is responsible
for the supplier.

qualityAuditStatus The factory quality audit status. No

qualityAuditNumber The factory quality audit number. No

qualityAuditor The name of the factory quality auditor. No

Setting Up SAP Ariba Supplier Lifecycle and Performance

74 CUSTOMER Importing SAP Ariba Supplier Lifecycle and Performance data
 Field Description Required?

qualityAuditValidityStartDa The date from which the quality audit No

te status is valid.

qualityAuditValidityEndDate The date to which the quality audit status No

is valid.

qualityAuditComments Any comments from the quality audit. No

complianceAuditStatus The factory compliance audit status. No

complianceAuditNumber The factory compliance audit number. No

complianceAuditor The name of the factory compliance au­ No

ditor.

complianceAuditValidityStar The date from which the compliance au­ No

tDate dit status is valid.

complianceAuditValidityEndD The date to which the compliance audit No

ate status is valid.

complianceAuditComments Any comments from the compliance au­ No

dit.

otherAuditStatus The factory status from an other audit. No

otherAuditNumber The other audit number for the factory. No

otherAuditor The name of the auditor. No

otherAuditValidityStartDate The date from which the other audit sta­ No

tus is valid.

otherAuditValidityEndDate The date to which the other audit status No

is valid.

otherAuditComments Any comments from the other audit. No

attribute1 Custom field. Regardless of the data in No

this field, the column header must be
attribute1.

attribute2 Custom field. Regardless of the data in No

this field, the column header must be
attribute2.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Importing SAP Ariba Supplier Lifecycle and Performance data CUSTOMER 75
[Link]
Purchasing organization data is required for solutions using the guided buying feature in Ariba Procure-to-Pay or
Ariba Procure-to-Order and is used for catalog searches. You import data about the purchasing organizations
associated with your suppliers using the Purchasing org data file type and [Link].

Field Description Required?

erpVendorId For existing Ariba suppliers, if the Yes

SupplierOrganizationOrganiz
ationIdPart_Export.csv file con­
tains a Domain and Value entry for the
supplier, use the Value in this field. If
not, use the [Link].

For suppliers imported from outside

Ariba, use the erpVendorId specified
in [Link].

sourceSystem For existing Ariba suppliers, if the Yes

SupplierOrganizationOrganiz
ationIdPart_Export.csv file con­
tains a Domain and Value entry for the
supplier, use the Domain in this field. If
not, use SM.

For suppliers imported from outside

Ariba, use the sourceSystem speci­
fied in [Link].

purchasingOrganisationId The ID of the purchasing organization. Yes

partyRoleCode The ID of the related partner function. Yes

partyInternalID The internal ERP ID of the related part­ No

ner function.

defaultIndicator A Boolean value that indicates whether No

or not the purchasing organization is to
be used as the default.

Setting Up SAP Ariba Supplier Lifecycle and Performance

76 CUSTOMER Importing SAP Ariba Supplier Lifecycle and Performance data
[Link]
You import custom display names for registration and qualification statuses using the Custom display names file
type and [Link].

Field Description Required?

fieldName The name of the registration of qualifica­ Yes

tion status field, in dot notation. Valid
values are:

● [Link]
● [Link]
● [Link]
● [Link]
ion
● [Link]
oval
● [Link]
bmit
● [Link]
● [Link]
nDenied
● [Link]
ed
● [Link]
ionStarted
● [Link]
ation
● [Link]
lificationApproval
● [Link]
ubmit
● [Link]
ionRestricted
● [Link]
ed
● [Link]
● [Link]
ionRejected
● [Link]

locale The ISO code for the language used for Yes
the displayName.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Importing SAP Ariba Supplier Lifecycle and Performance data CUSTOMER 77
Field Description Required?

displayName The custom label to use for the registra­ Yes

tion or qualification status.

[Link]
Primary supplier manager data is used to specify a primary and optional alternate contact within your company
who either interfaces with the supplier or can answer questions about it. Primary and alternate supplier managers
do not have any role in supplier projects; they are for information only unless you issue mass registration
invititations, in which case they are required. You import data about primary supplier managers using the Primary
Supplier Manager file type and [Link].

Field Description Required?

erpVendorId For existing Ariba suppliers, if the Yes

SupplierOrganizationOrganiz
ationIdPart_Export.csv file con­
tains a Domain and Value entry for the
supplier, use the Value in this field. If
not, use the [Link].

For suppliers imported from outside

Ariba, use the erpVendorId specified
in [Link].

sourceSystem For existing Ariba suppliers, if the Yes

SupplierOrganizationOrganiz
ationIdPart_Export.csv file con­
tains a Domain and Value entry for the
supplier, use the Domain in this field. If
not, use SM.

For suppliers imported from outside

Ariba, use the sourceSystem speci­
fied in [Link].

primarySupplrManager The username of the buyer user who is Yes

the primary internal contact for the sup­
plier.

altSupplrManager The username of the buyer user who is No

the alternate internal contact for the
supplier.

Setting Up SAP Ariba Supplier Lifecycle and Performance

78 CUSTOMER Importing SAP Ariba Supplier Lifecycle and Performance data
Editing and publishing supplier project
templates

When a solution is initially deployed, supplier project templates such as the Supplier Request Template or the
Supplier Registration Template are in Active status. Setting the templates up involves creating new versions,
editing them, and publishing the updates.

After the initial setup, once projects have been created from the templates, the upgrade will affect those projects.

Note
It is not necessary to publish the surveys and content documents in a template before you publish the template
itself.

How to create a new version of a template and

enabling editing
Procedure

1. On the dashboard, click Manage Templates .

2. Locate the template you want to edit. Click the template name and select Open.
3. Navigate to the Overview tab of the template.

4. In the Properties pane, select Actions Template New Version .

Using the template Overview tab

The following table lists the tasks you can perform on a template from the Overview tab. The available tasks can
vary depending on the project type and the state of the template.

To do this... Choose...

View template details Actions Template View Details to view the name, description, version, sta­
tus, base language, rank, owner, access control, conditions, tasks, and Documents tab.

View the template’s history Actions Template View History to view and search the past actions per­
formed on the template, including the type of action and the user who performed the
action.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Editing and publishing supplier project templates CUSTOMER 79
To do this... Choose...

Edit the template properties attrib­ Actions Template Edit Properties to edit the template name, description,
utes owner, process status, rank, access controls, and conditions.

Make the template available to use to Actions Template Publish .

create projects

Revert to the original version of a Actions Template Revert .

template

Export the template to a ZIP file Actions Template Export Template to export various template components
to XML files in a ZIP file.

Create a new version of the template Actions Template New Version .

To deactivate a template so new Actions Template Inactivate . You can later Reactivate the template.
projects cannot be created from it

Display all tabs in a project Actions Display Full View . The newly-created template displays in compact
view. The view you use when publishing the template determines the initial view users
see in projects created from the template. Choose Actions Display Compact
View to return to the compact view.

Note
Templates for Ariba Sourcing quick projects only use compact view.

How to publish project templates

Context

You must publish a project template to make it available to users who are creating projects.

If the template contains team member rules file documents, those files are validated during publication, and an
error message tells you which team member rules files contain errors. You need to fix any validation errors in team
member rules files before you can successfully publish a template.

When you publish a template, any previous active version of that template changes to archive status. You can
create a new version from an archived version as a way to recover a previous version as the current draft.

Note
Documents do not have versions within a particular version of a template. However, if you make changes to a
document in a subsequent version of a template, the original version of the document is retained in the previous
template version.

Setting Up SAP Ariba Supplier Lifecycle and Performance

80 CUSTOMER Editing and publishing supplier project templates
Procedure

Choose Actions Publish on the Overview tab.

Note
If you cannot publish a supplier-related template because of errors in the team member rules file, you publish
the file to see exact error messages.

Next Steps

After you have completed work on a template, you can export it to a ZIP file and import it for later use.

How to update supplier-related projects to a new

template version
Procedure

1. On the dashboard, click Manage Templates .

2. Navigate to the supplier-related template you want to modify and choose Actions Template New
Version on the Overview tab.
3. Edit the template.
4. Navigate to the Advanced Options tab.
5. In the Upgrade Template Settings area, select Yes.

6. On the Overview tab, choose Actions Template Publish .

Results

After you have published a new version of the template, the Upgrade Template Task Status area on the
Advanced Options tab shows how many projects have been the template upgrade scheduled task has upgraded
to the new template version, and how many it has yet to upgrade. Projects that are upgraded when users open
them do not count toward either of these numbers, because it only counts those projects that are touched by the
scheduled task. If a project is upgraded when a user opens it while the scheduled task is running, the total number
to be upgraded decreases by 1.

Individual project History tabs show when they were upgraded to the new template version and display all of the
changes to project groups, tasks, phases, and documents that occur during a template upgrade. For example, a
template upgrade adds a document to a project. The History tab for the project contains two entries with the same

Setting Up SAP Ariba Supplier Lifecycle and Performance

Editing and publishing supplier project templates CUSTOMER 81
(or nearly the same) time stamp. The first entry is for the workspace change, with Details text similar to the
following:

Upgraded to a new version of template

The second entry is for the added document with Details text similar to the following:

Created from template

To view information about the current template version, click the link in the Details column for the workspace
change.

Setting Up SAP Ariba Supplier Lifecycle and Performance

82 CUSTOMER Editing and publishing supplier project templates
Creating supplier forms, questionnaires, and
internal surveys

Supplier management processes such as supplier requests and registrations uses template survey and content
documents to create forms and dynamic questionnaires targeted to suppliers based on region and commodity.
They can also use survey documents to solicit information from internal stakeholders. Content in these
documents can be mapped to specific fields in your supplier database.

How to create a supplier form or simple questionnaire [page 83]

How to set up a targeted supplier questionnaire [page 85]

How to create a targeted supplier questionnaire segment [page 86]

How to create a supplier-related internal survey [page 87]

Adding content to a supplier form, questionnaire segment, or internal survey [page 89]

Using visibility conditions to show or hide content based on answers [page 95]

Content examples [page 99]

How to add translations for form and questionnaire content names [page 106]

Mapping form or questionnaire content to supplier database fields [page 107]

How to create a supplier form or simple

questionnaire
Forms are useful if you have a relatively small set of content that applies to all projects, such as with a supplier
request. Simple questionnaires are useful if you do not have lots of questions targeted to specific regions or
commodities. Creating a form or simple questionnaire involves editing the template's default survey document to
add content.

Prerequisites

You must be working with a new version of the template, so that the template itself is open for editing, in order to
edit its survey document. See Editing and publishing supplier project templates [page 79] for more information.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 83
Context

Note
Template survey documents contain a number of settings (supplier eligibility criteria, timing rules, definitions,
participants, and so forth) that are not relevant to supplier management processes. These settings are ignored
in supplier management projects. Only the supplier management settings on the survey's Overview page and
the content on its Content page are used in supplier management projects.

Procedure

1. On the dashboard, click Manage Templates .

2. On the Documents tab of the Templates page, expand the folder for the template you want to work with to see
its contents.`
3. Click the template and choose Open.
4. Click the Documents tab of the template project.
5. Click the template's survey document and choose Edit Attributes.
6. On the Create Event page, in the Supplier Management area, perform the following actions:

○ For Specify questionnaire format, choose Form to create a form or Questionnaire to create a simple
questionnaire.
○ For Is questionnaire internal only?, choose Yes if only your organization's employees will be filling the
form our, or No if external people such as supplier contacts will be filling it out.
○ For Is questionnaire required?, choose Yes.
7. Click Content.
8. Add content to the form or questionnaire. [page 89]
9. Click Summary.
10. Perform one of the following actions:

○ To save the form or questionnaire and work on it later, click Exit, then click Save and then exit
○ To publish the form or questionnaire, click Publish.

Results

Once you publish the form or questionnaire and upgrade and publish the project's template [page 81], the it is
available to all users who have permission to use it.

Setting Up SAP Ariba Supplier Lifecycle and Performance

84 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
How to set up a targeted supplier questionnaire
Setting up a supplier questionnaire with segments targeted to specific commodities and regions is a one-time
operation that involves making sure that the project's empty survey document, which forms the questionnaire
framework, has the right settings.

Prerequisites

You must be working with a new version of the template, so that the template itself is open for editing, in order to
edit its survey document. See Editing and publishing supplier project templates [page 79] for more information.

Context

When you are setting up the targeted questionnaire by editing the survey, do not add any content to it directly. You
add questionnaire content in separate content documents.

Note
Template survey documents contain a number of settings (supplier eligibility criteria, timing rules, definitions,
participants, and so forth) that are not relevant to supplier management processes. These settings are ignored
in supplier management projects. Only the supplier management settings on the survey's Overview page and
the content on its Content page are used in supplier management projects.

Procedure

1. On the dashboard, click Manage Templates .

2. On the Documents tab of the Templates page, expand the folder for the template you want to work with to see
its contents.`
3. Click the template and choose Open.
4. Click the Documents tab of the template project.
5. Click the template's survey document and choose Edit.
6. On the Rules page, in the Supplier Management area, perform the following actions:

○ For Specify questionnaire format, choose Questionnaire.

○ For Is questionnaire internal only?, choose Yes if only your organization's employees will be filling out the
questionnaire, or No if external people such as supplier contacts will be filling it out.

Note
Always choose No for registration and qualification questionnaires, which are designed for suppliers to
fill out.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 85
 ○ For Is questionnaire required?, choose Yes.
7. Click Summary.
8. Click Publish.

Results

The questionnaire framework is now ready. The next step is to add content to it by creating questionnaire
segments [page 86].

How to create a targeted supplier questionnaire

segment
Questionnaire segments are targeted at specific commodities and regions, and are dynamically added to
questionnaires based on the supplier's regions and commodities.

Prerequisites

You must be working with a new version of the template, so that the template itself is open for editing, in order to
create questionnaire segments. See Editing and publishing supplier project templates [page 79] for more
information.

Context

Selecting at least one commodity and one region for each questionnaire segments is required, because it is how
you make sure that they are sent to suppliers for those commodities and regions. If you select a commodity or
region at a high level of the hierarchy, the questionnaire segment is sent to all suppliers who are associated with all
of the commodities or regions under it. To make the questionnaire segment general to all suppliers, choose All for
both commodity and region.

Procedure

1. On the dashboard, click Manage Templates .

2. On the Documents tab of the Templates page, expand the folder for the template you want to work with to see
its contents.`
3. Click the template and choose Open.

Setting Up SAP Ariba Supplier Lifecycle and Performance

86 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
 4. Click the Documents tab of the template project.

5. Choose Actions Create Content Document .

6. In the Title field, enter a descriptive title for the questionnaire segment. Category or supplier managers see
this title when they are selecting questionnaire segments to include in a questionnaire.
7. (Optional) In the Description field, enter descriptive information about the questionnaire. This information is
only visible in the template.
8. Choose at least one commodity from the Commodities dropdown menu and at least one region from the
Regions dropdown menu.

If the commodity or region you want to specify does not appear on the menu, click select more, select the
commodity or region, and click Done. If you want to send the questionnaire segment to all suppliers, choose
All
9. (Optional) To add more commodities or regions, click add more to the right of the Commodity and Region
dropdown menus and repeat the previous step.
10. Click Create.
11. Add content to the questionnaire segment. [page 89]
12. Click Done.

How to create a supplier-related internal survey

Internal surveys in supplier projects allow internal stakeholders to add information that supplements the project's
form or questionnaire. Creating an internal survey involves adding a survey document to the template.

Prerequisites

You must be working with a new version of the template, so that the template itself is open for editing, in order to
edit its survey document. See Editing and publishing supplier project templates [page 79] for more information.

Context

In most cases, internal surveys are displayed the supplier 360° tile related to the project. For example, in solutions
that include SAP Ariba Supplier Lifecycle and Performance, internal surveys are displayed on the Qualification tile.
The exception to this rule is for supplier registration projects, where internal surveys are displayed on the
Overview tile; this design allows you to use an internal survey as a way to allow category or supplier managers to
supplement supplier registration information and display it as part of the supplier profile.

Note
Template survey documents contain a number of settings (supplier eligibility criteria, timing rules, definitions,
participants, and so forth) that are not relevant to supplier management processes. These settings are ignored

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 87
 in supplier management projects. Only the supplier management settings on the survey's Overview page and
the content on its Content page are used in supplier management projects.

Procedure

1. On the dashboard, click Manage Templates .

2. On the Documents tab of the Templates page, expand the folder for the template you want to work with to see
its contents.`
3. Click the template and choose Open.
4. Click the Documents tab of the template project.

5. Choose Actions Create Survey .

6. In the Title field, enter a descriptive title for the questionnaire segment. Category or supplier managers see
this title when they are selecting questionnaire segments to include in a questionnaire.
7. (Optional) In the Description field, enter descriptive information about the questionnaire. This information is
only visible in the template.
8. (Optional) Choose at least one commodity from the Commodities dropdown menu and at least one region
from the Regions dropdown menu.

If the commodity or region you want to specify does not appear on the menu, click select more, select the
commodity or region, and click Done. If you want to send the questionnaire segment to all suppliers, choose
All
9. (Optional) To add more commodities or regions, click add more to the right of the Commodity and Region
dropdown menus and repeat the previous step.
10. Click Create.
11. On the Rules page, in the Supplier Management area, perform the following actions:

○ For Specify questionnaire format, choose Form.

○ For Is questionnaire internal only?, choose Yes.
○ To make the survey required, for Is questionnaire required?, choose Yes.
12. Click Content.
13. Add content to the survey. [page 89]
14. Click Summary.
15. Perform one of the following actions:

○ To save the survey and work on it later, click Exit, then click Save and then exit
○ To publish the survey, click Publish.

Results

Once you publish the survey and upgrade and publish the project's template [page 81], the survey is available to all
users who have permission to use it.

Setting Up SAP Ariba Supplier Lifecycle and Performance

88 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
Adding content to a supplier form, questionnaire
segment, or internal survey
You add content to a form or questionnaire segment as sections, questions, requirements, or attachments.

Note
On the content table, you can drag and drop pieces of content to place them in the order in which you want
them to appear.

How to add a section to a supplier form, questionnaire

segment, or internal survey
A section is a container in which you organize other content, such as questions, requirements, or attachment. You
can nest sections within other sections.

Context

Sections are automatically numbered in their order of appearance, and the content inside them is numbered
based on the parent section number. For example, a section in a questionnaire segment might be numbered 1, and
the three questions inside it numbered 1.1, 1.2. and 1.3.

Top-level sections in questionnaire segments are useful for organizing content in the final questionnaire, which is
assembled from multiple segments. If you nest all of the content of a questionnaire segment inside a section, it is
displayed and numbered together in the final assembled questionnaire. If you do not, but the content of a previous
questionnaire segment is nested in a top-level section, the content of the current segment is added to and
numbered with the previous segment's content in the final questionnaire.

If you apply a condition to a section, that condition applies to all of the content in the section. Sections are
therefore useful if you have a series of questions that you want to show or hide based on the answers to other
questions.

Procedure

1. (Optional) To nest a section inside another section, select it.

2. Select Add Section .

3. (Optional) If you are creating a nested section, select Add Inside.
4. Enter a name and description for the section.
5. Select whether or not suppliers can see the question from the Visible to Participants pull-down menu.
Selecting No creates a requirement that is only visible to internal users.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 89
6. (Optional) Click none and select an existing visibility condition, or select Create Condition to create a new
condition. See Using visibility conditions to show or hide content based on answers [page 95] for details.
7. Click OK.

How to add a question to a supplier form, questionnaire, or

internal survey

Context

Note
The Add Question pages for both surveys and content documents include a number of settings (include in cost,
access control, participant-specific initial values, and so forth) that are not relevant to supplier management.
These settings are ignored in supplier management projects. Only the settings discussed in the following steps
are used in supplier management projects.

Procedure

1. Perform one of the following actions:

○ Select Add Question at the bottom of the content table to add the question to the end of the form
or questionnaire.
○ Select the section to which you want to add the question and select Add Question at the bottom of
the content table.
○ Click a section to add the question inside or after it and select Add Question from the pull-down
menu.
2. If you selected a location for the new question, select Add Inside to add the new question nested inside
section, or Add After to add it after the selected section on the same level.
3. Choose an answer type from the Answer Type dropdown menu. The answer type you choose determines the
other settings you can specify for the question.
4. Enter the text for your question in the Name field.
5. (Optional) For answer types that allow acceptable values, on the Acceptable Values dropdown menu, perform
one of the following actions:

○ To allow respondents to enter any value in the answer field, choose Any Value.
○ To force respondents to choose a value from the master data loaded in your site, choose Master Data
Value. At the bottom of the Add Question page, choose a master data type from the Master data types
to use for value dropdown menu.

Setting Up SAP Ariba Supplier Lifecycle and Performance

90 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
 ○ To force respondents to choose from a set of answers you pre-define, select List of Choices. The default
list of choices is a dropdown menu where respondents select one value from the list. At the bottom of the
Add Question page, specify the following properties for your list of choices:

Property Description and Options

Allow participants to specify other value? Options are:

○ Yes: respondents can select Other on your list of choices and
enter a value that is not on your list in an Other field.
○ No: respondents must choose from the values on your list.

Allow participants to select multiple values? If you select Yes, the list of choices is a set of check boxes instead
of a pull-down menu, and respondents can select multiple values
to answer the question. If you allow multiple answers to a question,
you cannot add it to reports.

List of Choices Specifies the value on the list of choices.

Enter values and click Add to add choices to the list. Select a value
from the list and click Set Default to make it the default choice.

○ For answer types that allow number ranges, to limit answers to a specific range of numbers, select
Limited Range. At the bottom of the Add Question page, add from and to values to define the range. For
date questions, select a relative range such as Last Week or This Year from the Range menu, or select
Custom and specify a fixed from and to date to define the range.

6. For decimal number, money, or percentage answer types, enter the number of decimal places; the default
number is 2.
7. Specify the following settings for the question; available settings depend on the answer type you selected:

Setting Description and Options

Response Required? Specifies whether or not you want to require various respondents to answer the
question. Options are:
○ Not Required
○ Yes, Participant Required: suppliers must answer the question.
○ Yes, Owner Required: creates an internal-only question. Only use this op­
tion in internal forms (such as the supplier request form) and surveys.
For projects where the supplier answers the questionnaire, there is no way
for an internal user to edit the questionnaire to add owner-required an­
swers.

Reference documents Click Attach a file to attach a reference file to the question; you can either up­
load the file from your local computer or select it from your site’s library content.
You can only attach library content to which you have access.

Visible to Participants Specifies whether or not suppliers can see the question. Selecting No creates a
question that is only visible to internal users. Note that for projects where the
supplier answers the questionnaire, internal users can see the question but can­
not answer it.

Participants can add additional Specifies whether or not respondents can add additional attachments and com­
comments and attachments ments to the question using an icon that opens an extra comment field and at­
tachment link.

SM Field Mapping If you want to map the question to a supplier database field [page 107], enter
the field name.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 91
 Setting Description and Options

Visibility Conditions Specifies the conditions under which suppliers and internal users at your com­
pany see the question. Click none and select an existing condition, or select
Create Condition to create a new condition. For details, see Using visibility con­
ditions to show or hide content based on answers [page 95].

8. (Optional) Provide an initial value as an example, in order to communicate your expectations of how
respondents should answer by performing one of the following actions:

○ For yes/no questions, select Yes or No as a default value, or select Unspecified if you do not want to
provide a default value.
○ For attachment questions, click Attach a file and either upload the file from your local computer or select
it from your site’s library to provide an attachment that respondents can use as a template or form for
providing their responses
○ For certificate questions, select Yes or No as a default value, or select Unspecified if you do not want to
provide a default value. If you select Yes, you can click Details and provide default certificate information
such as issuer to communicate your expectations for how respondents will answer the question.
○ For quantity questions, the default unit of measure for the initial value is each. To change it, click each and
select from the list of units of measure used in your site.
○ For all other answer types, enter an initial value in the Initial Value field.
9. Click Done.

Related Information

Supplier form, questionnaire, and internal survey question answer types [page 94]

How to add a requirement to a supplier form, questionnaire

segment, or internal survey
A requirement is a statement that communicates your expectations or other information to suppliers and internal
stakeholders.

Procedure

1. Perform one of the following actions:

○ Select Add Requirement at the bottom of the content to add a new requirement to the end of the
questionnaire.
○ Select the section before or inside of which you want to add the requirement and select Add
Requirement at the bottom of the content table.
○ Click a section to add the requirement inside or after it and select Add Requirement from the pull-
down menu.

Setting Up SAP Ariba Supplier Lifecycle and Performance

92 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
 2. If you selected a section for the new requirement, select Add Inside to add the new requirement nested inside
the section, or Add After to add it after the section on the same level.
3. Add a descriptive name for the requirement in the Requirement field.
4. Click Attach a file to attach a reference file to the requirement; you can either upload the file from your local
computer or select it from your site’s library content. You can only attach library content to which you have
access.
5. Select whether or not suppliers can see the question from the Visible to Participants pull-down menu.
If you use a requirement for internal text, make sure to specify that it is not visible to participants so that external
suppliers can’t see it. Selecting No creates a requirement that is only visible to internal users.
6. (Optional) Click none and select an existing visibility condition, or select Create Condition to create a new
condition. See Using visibility conditions to show or hide content based on answers [page 95] for details.
7. Click OK.

How to add an attachment to a supplier form,

questionnaire segment, or internal survey
An attachment in a form or questionnaire a document file that provides additional information to respondents. It is
an independent content item to which you can apply visibility conditions.

Context

When you add an attachment to the profile questionnaire, use its description to communicate the format of the
attached file and your expectations for its use by respondents.

You can add document files either from your local computer or from the Sourcing Library to supplier profile
questionnaire attachments.

You cannot set visibility conditions on attachments initially when you add them as standalone attachments.
However, when you edit any attachment you added this way, you can set visibility conditions on them and add
reference documents at that time.

Note
In addition to standalone attachments, you can also attach files to questions, requirements, and other pieces of
content.

Procedure

1. Perform one of the following actions:

○ Select Add Attachments from Desktop at the bottom of the content table. Click Browse, navigate
to the file you want to attach on your local computer, and click Open. Click Add More to add up to 10 files
as attachments at the same time.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 93
 ○ Select Add Attachments from Library at the bottom of the content table. Search for the project or
library content you want to attach, select the files, and click OK. You can only attach library content to
which you have access.
2. Enter a description for each file.
3. (Optional) Click Show Details and perform one of the following actions for each file:

○ Select whether or not suppliers can see each attachment from the Visible to Participants pull-down
menu. Selecting No creates an attachment that is only visible to internal users.
○ Limit access control to the file to specific sets of users.
4. Click Done.

Supplier form, questionnaire, and internal survey question

answer types
For each question you add to a form, questionnaire, or internal survey, you specify an answer type that defines the
type of data you want in that field.

Answer Type Description

Text (single line limited) The answer field accepts a single line of text (numerical and al­
phabetic characters) with no character returns and a maxi­
mum of 255 characters.

This answer type is the only one for which you can set master
data values as an acceptable answer.

Text (single line) The answer field accepts a single line of text (numerical and al­
phabetic characters) with no character returns and a maxi­
mum of 4000 characters.

Text (multiple lines) The answer field displays six lines of text initially and can be
expanded indefinitely with a vertical scroll bar and no charac­
ter limit.

Whole Number A whole number; for example, 20.

Decimal Number A decimal number; for example, 19.5. The default number of
decimal places is 2

Date A formatted date; for example, Fri., 12 Aug., 2009.

Money A decimal number plus currency symbol. The default number

of decimal places is 2.

Yes/No The input field is a dropdown menu with Yes and No menu
items.

Setting Up SAP Ariba Supplier Lifecycle and Performance

94 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
 Answer Type Description

Attachment Requires the respondent to answer the question by uploading

a file attachment. You can provide a default file attachment as
an initial value, which the respondent can then download, edit,
and upload to answer the question.

Note
Use the separate Certificate answer type to ask for small
business, diversity, green, and other certifications.

Certificate The answer field is a pull-down menu with Yes and No menu
items. Selecting Yes displays a Details link that allows re­
spondents to enter certificate information such as issuer,
number, location, type, and effective and expiration dates, and
to upload a certificate file as an attachment.

Address The answer is a complete set of address fields: Street, City,

State/Province/Region, and Country, which uses a drop­
down menu to allow users to select from a list available coun­
tries.

Percentage A percentage value; for example, 25%. The default number of

decimal places is 2.

Quantity A number value plus a unit of measurement selected from a

list. The default unit of measurement is each.

Commodity The answer field is a dropdown menu that allows respondents

to select from the commodities used in your site.

Region The answer field is a dropdown menu that allows respondents

to select from the regions used in your site.

Using visibility conditions to show or hide content

based on answers
The content to which you have applied a visibility condition is hidden from respondents unless they supply an
answer that fulfils the condition. At that point, the page refreshes and the conditional content appears. If a
participant changes an answer so that the condition is no longer fulfilled, the content disappears and any existing
answers are not retained.

If you add a question to your document from the Sourcing Library (as library content), you have the option of
copying its conditions as well so that they operate in your document.

You can create two types of visibility conditions: basic and advanced.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 95
● Basic visibility conditions [page 96] are based on the answer to one question.
● Advanced visibility conditions [page 97] allow you to combine the answers to multiple questions to create
conditional expressions based on logical operators (AND, OR, and NOT).You can stack and nest expressions,
but take care that the logic in an advanced condition doesn’t contain contradictions.

When you create either type of condition, keep in mind the following considerations:

● If the project uses a form, all respondents see the single form, and visibility conditions based on commodity
and region can be useful for displaying content dynamically based on answers. But questionnaires are
assembled from content document segments that are targeted to specific commodities and regions. It is
therefore important be aware of all of your existing segments and the commodity and region settings you have
applied to each segment, and only apply visibility conditions based on commodity or region in segments where
it makes sense. For example:
○ If you have a questionnaire segment that applies to all commodities, but another questionnaire segment
that applies only to IT and computer equipment, it doesn't make sense to use visibility conditions to add a
question to the general questionnaire that is only shown to suppliers of IT and computer equipment. Add
the question (without conditions) to the IT and computer equipment questionnaire segment instead, and
it will automatically only show to those suppliers.
○ If you have a questionnaire segment that applies to all regions, and other region-specific questionnaire
segments that only target regions down to the country level, you can use visibility conditions for specific
states, regions, or cities to show content based on more granular region values. Add conditional questions
that only applies to Parisian suppliers to the questionnaire segment targeted at France.
● You cannot create conditions based on questions of answer type Text (multiple lines). You can create
conditions based on questions of any other answer type.
● If you set a visibility condition for content that suppliers will see in registration or other questionnaires, make
sure that the question that triggers the condition is visible to participants.

How to create a basic visibility condition in a form or

questionnaire segment

Basic visibility conditions are based on answers to a single question.

Prerequisites

You must create the question on which the condition is based before you can create the condition.

Context

Setting Up SAP Ariba Supplier Lifecycle and Performance

96 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
Procedure

1. Use an existing question or create a new question on which to base the condition.
2. On the content table, perform one of the following actions:

○ Choose Edit Conditions .

○ Click the question and choose Edit, then choose Add Conditions .
3. On the Edit Conditions page, click Add.
4. In the Create Condition window, enter a short name and description for the condition. The name appears on a
menu of available conditions that you can apply to content, so it should be descriptive.
5. For the expression, click Undefined and select the question or formula on which you want to base the
condition.

6. Perform one of the following actions to set the condition content match:

○ For questions with numerical answer types (including date and money), enter a From and To value to
create a range of values.
○ For questions with text answer types, enter a string of text which must match participant answers exactly
to satisfy the condition.
○ For questions with Yes/No answer types, select either Yes, No, or Either.
○ For questions with a defined list of answer values that are specific to the question, select the answer from
the dropdown menu.
○ For questions with answers that must be selected from a list of site-wide values (such as commodity),
click select and select the values that participants’ answers must match in order to satisfy the condition.
7. Click OK.

Next Steps

Now you can apply the condition to form or questionnaire segment content. When you are creating or editing a
section, question, requirement, or attachment, for Visibility Condition, click none and choose from the list of
available conditions.

How to create an advanced visibility in a form or

questionnaire segment

Advanced visibility conditions are based on the answers to multiple questions.

Prerequisites

You must create the questions on which the condition is based before you can create the condition.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 97
Procedure

1. Use an existing question or create a new question on which to base the condition.
2. Perform one of the following actions:

○ Choose Edit Conditions .

○ Click the question and choose Edit, then choose Add Conditions .
3. On the Edit Conditions page, click Add.
4. In the Create Condition window, enter a short name and description name for the condition. The name
appears on a menu of available conditions that you can apply to content, so it should be descriptive.
5. For the expression, click Undefined and select an expression (All of, Any of, or None of). For descriptions of
available expressions, see Expressions for Advanced Visibility Conditions in Events, Surveys, and the Supplier
Profile Questionnaire [page 99]
6. Perform any of the following steps. The order in which you add expressions and questions determines the
nested structure of your condition.

○ Click Undefined and select the question on which you want to base the condition from the list of options,
then specify the content match that fulfills the condition.
○ To enclose an expression within an expression, click the expression and select it. The new expression is
added to its left.
○ To add a condition in parallel to another condition, click the expression to its left, then select the question
or formula from the list of options and specify the content match that fulfills the condition.
○ To nest a set of conditions with an expression inside another expression, add a condition to the first
expression, then select Content Match for the condition and select the expression. The new expression is
added to the left of the condition, but within the first expression.
7. Continue adding nested conditions and expressions as needed.
8. Click OK.

Next Steps

Now you can apply the condition to form or questionnaire segment content. When you are creating or editing a
section, question, requirement, or attachment, for Visibility Condition, click none and choose from the list of
available conditions.

Setting Up SAP Ariba Supplier Lifecycle and Performance

98 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
Expressions for advanced visibility conditions
You can use expressions to create advanced visibility conditions.

Expression Definition

All of An advanced expression that can include multiple expressions used for conditions that require all
expressions to match (AND). You can use the All of expression to make a condition true under spe­
cific, layered circumstances.

For example, you can create an All of expression with two content matches: Are you Woman Owned
Enterprise Certified? = Yes and Are you Small Business Certified? = No. This condition is true for any
supplier that is Woman Owned Enterprise Certified but is not Small Business Certified. You can use
this condition to display specific content for suppliers with that combination of certifications.

Any of An expression that is true if one or more of the expressions defined in it are true (OR).

For example, if you define an Any of condition with four questions in it, that condition is true if the
participant’s answer matches the answers you define as content matches for at least one, or as
many as all four, of those four questions.

None of An expression that is true only if none of the expressions defined in it are true (NOT).

For example, you can create a None of expression with content matches to four different regions
where you have manufacturing plants for questions that ask participants if they have shipping cen­
ters close to those regions. You can use this condition to display content to suppliers who answered
No to all of those questions, and therefore might not be able to fulfill your shipping requirements.

Content examples

How to create a dropdown menu with predefined values on

a supplier form or questionnaire
When you add a question and provide a list of choices for the answer, the form or questionnaire displays those
choices in a dropdown menu. The person who fills out the form must choose one of the values on the list.

Prerequisites

Lists of choices are only available for questions with one of the following answer types:

● Text (single line)

● Text (single line limited)
● Whole Number

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 99
● Decimal Number
● Date
● Money
● Percentage

Procedure

1. In the content area of the form or questionnaire, click Add Question .

2. Choose one of the answer types that support lists of choices.
3. On the Acceptable Values dropdown menu, choose List of Choices.

The List of Choices editor appears at the bottom of the page.

4. Perform the following actions to add choices to the list:
a. Enter the first choice in the text box.
b. Click Add and enter additional choices.
c. To make one of the choices the default choice, which appears at the top of the dropdown menu, select it
and click Set Default. To specify no default choice, make sure that none of the choices are selected and
click Set Default.
5. Specify other settings for the question and click Done.

How to automatically reject answers that don't fall within a

limited range on supplier forms

When you add a question with a limited range answer to a form or questionnaire segment, any values entered in
the field that do not fall within that range are rejected, and the person filling out the form or questionnaire must
provide an answer within the defined range in order to submit it successfully..

Prerequisites

Limited ranges are only available for questions with one of the following answer types:

● Whole Number
● Decimal Number
● Date
● Money
● Percentage
● Quantity

Setting Up SAP Ariba Supplier Lifecycle and Performance

100 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
Context

For questions with answer type Date, you can limit answers relative to the current date or specify a fixed (custom)
date range. For example, you can require that the respondant's answer be in the current year, current month,
previous fiscal quarter, and so forth.

Procedure

1. In the content area of the form or questionnaire, click Add Question .

2. Choose one of the answer types that support limited ranges.
3. On the Acceptable Values dropdown menu, choose Limited Range.

The limited range fields appear at the bottom of the page.

4. Perform the following actions to define your range:

○ For number ranges, enter numerical values in the From and To fields.
○ For date ranges, choose a value from the Range dropdown menu, or choose Custom and specify a fixed
date range.
5. Specify other settings for the question and click Done.

How to ask for a supplier certificate

The Certificate question answer type includes fields that allow respondents to provide effective and expiration
dates, issuers, and other details. You can map the question to the supplier database.

Procedure

1. In the content area of the form or questionnaire, click Add Question .

2. On the Answer Type dropdown menu, select Certificate.
3. Enter a name for the question, such as Please provide your green certificate.
4. For Visible to Participant, choose Yes.
5. In the SM Field Mapping field, enter certificate.
6. Specify other settings for the question and click Done.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 101
Results

When the supplier chooses Yes to provide a certificate and clicks the Details link, a window opens up. The supplier
can enter issuer, effective and expiration dates, certificate numbers, and other details, as well as uploading the
certificate as an attachment.

How to ask for a supplier's address and map the answer to

the supplier database: method 1
Commodity, Region, and Address are all special answer types, and in most cases you will want to map the
answers to the supplier database so that the answers are the supplier's official records for those fields.

Context

You can use one of two methods to ask for a supplier's address: by using the Address answer type, as
demonstrated in this example, or by creating separate questions for each address field [page 103]. The method
shown here is useful if you do not want to allow multiple lines in a supplier's street address, since the Address
answer type only supports one street address line. With the Address answer type, respondents select from a list of
countries on a dropdown menu.

You can follow these steps for questions with the Commodity and Region answer types, mapping them to the
[Link] and [Link] database fields respectively.

Procedure

1. In the content area of the form or questionnaire, click Add Question .

2. Enter a title for the question, such as Address:.
3. Choose the Address answer type.
4. For Response Required, choose Yes, Participant Required.
5. For Visible to Participant, choose Yes.
6. In the SM Field Mapping field, enter Address :: address.
7. Click Done.

Results

The form or questionnaire shows a predefined set of address fields: Street, City, State/Province/Region, and
Country, which uses a dropdown menu to allow users to select from a list available countries. These fields are all
mapped to the supplier database.

Setting Up SAP Ariba Supplier Lifecycle and Performance

102 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
How to ask for a supplier's address and map the answer to
the supplier database: method 2

Context

You can use one of two methods to ask for a supplier's address: by using the Address answer type [page 102], or
by creating separate questions for each address field, as shown here. Since the Address answer type supports a
fixed number of address fields, including only one street address line, the method shown here is useful if you want
to ask for supplier addresses with multiple lines for street address. You can only map the first address line to the
supplier database, but you can still acquire all of the lines in the supplier's street address.

The question you create for the country portion of the address has a text answer type, so respondents enter a text
value instead of choosing from a dropdown menu of available countries unless you use master data as the
acceptable answer values and choose Region as the master data type for the answer.

Procedure

1. Create a section to hold the address questions:

a. In the content area of the form or questionnaire, click Add Section .

b. Enter a name for the section, such as Address.
c. On the Visible to Participant dropdown menu, choose Yes.
d. Click OK.
2. Create a question for the second address line:

a. Click the address section and choose Add Question .

b. For Location, choose Add Inside.
c. Enter a name for the question, such as Address Line 2:.
d. On the Answer Type dropdown menu, choose Text (single line limited).
e. On the Visible to Participant dropdown menu, choose Yes.
f. Click Done.
3. Create a question for the city:

a. Click the address section and choose Add Question .

b. For Location, choose Add Inside.
c. Enter a name for the question, such as City:.
d. On the Answer Type dropdown menu, choose Text (single line limited).
e. On the Visible to Participant dropdown menu, choose Yes.
f. In the SM Field Mapping field, enter [Link]
g. Click Done.
4. Repeat the procedure to create questions in the address section for state, region, or province (mapped to
[Link]), postal code (mapped to ([Link]), and country (mapped to
[Link]).

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 103
How to create a question that is only visible suppliers with
green certifications
Visibility conditions allow you to create a question that is only visible to suppliers who are certified green.

Procedure

1. Create a certificate question that asks for green certification:

a. Below the content table for the form or questionnaire segment, choose Add Question .
b. Enter a name for the question, such as Are you certified green?.
c. On the Answer Type dropdown menu, choose Certificate.
d. For Visible to Participant, choose Yes.
e. In the SM Field Mapping field, enter certificate.
f. Specify other settings for the question and click Done.
2. Create a condition based on a yes answer to the green certificate question:

a. Below the content table for the form or questionnaire segment, choose Edit Conditions .
b. On the Edit Conditions page, click Add.
c. In the Create Condition window, enter a name for the condition, such as Show for green certified.
d. For the expression, click Undefined and select your green certification question.
e. Select Yes for the content match.
f. Click OK, then click Done.
3. Create a question that will only show when a supplier Yes to your certification question:

a. Below the content table for the form or questionnaire segment, choose Add Question .
b. Enter a name for the question, such as Please provide your company's sustainability
policy. You can add it as an attachment..
c. On the Answer Type dropdown menu, select Text (multiple line).
d. For Visible to Participant, choose Yes.
e. For Participant can add additional comments and attachments, choose Yes.
a. For Visibility Conditions, click none and select your green certified condition.
b. Click Done.

Setting Up SAP Ariba Supplier Lifecycle and Performance

104 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
How to ask about preferred supplier levels using master
data values
If you company uses preferred supplier levels, they are loaded into your site as master data, and you can use that
master data to specify how respondents answer questions.

Context

This question is useful in category status forms in preferred supplier management projects, where internal users
can request changes to the preferred status of the suppliers they work with.

Procedure

1. In the content area of the form or questionnaire, click Add Question .

2. On the Answer Type dropdown menu, choose Text (single line limited).
3. Enter a name for the question, such as Requested preferred status level:.
4. On the Acceptable Values dropdown menu, choose Master Data Value
5. For Visible to Participant, choose Yes.
6. In the SM Field Mapping field, enter [Link].
7. On the Master data type to use for values dropdown menu, choose Supplier Preferred Level.
8. Specify other settings for the question and click Done.

Results

Users answering this question select from among the supplier preferred levels defined in your site's master data
on a dropdown menu.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 105
How to add translations for form and questionnaire
content names
When you provide translations of form or questionnaire content names in a language, users with that locale set in
their profiles automatically see those translations. If you do not provide translations, users in all locales see the
content names in the originally language in which you created them (the base language).

Prerequisites

You must be a member of the Template Creator group in order to edit project templates. You must also belong to
the Translator group in order to add translations of form or questionnaire content names in the template.

Context

You can provide translations for each of the languages that are enabled in your site. The translation fields include
the same formatting controls as the original content name fields, so you can also duplicate the formatting.

Note
These translations apply only to the text in the Name field of form and questionnaire content. There is no way to
translate answers that involve lists of choices, and attached files are always in the language of the file. If you
need to add content with attachments or lists of choices that are also translated into multiple languages, you
must:

● Create a piece of content in each language, rather than creating a single piece of content in the base
language and providing translations. For each piece of language-specific content, the choices in the list of
choices and the attached documents must be in that language.
● Use either visibility conditions based on region or region-specific questionnaire segments to make sure that
the content for each language only displays for the region corresponding to that language.

Note that this way of providing translated content is less precise, because it is not based on individual user
locale settings; for example, if you add French content that is visible to suppliers in Switzerland, it is shown to
Swiss users who specify either French or German as their language.

Procedure

1. Above the content table for the survey or content document, choose Actions Translate .
The Content Translation page opens. It displays the Base Language on the left in read-only fields and the
Translation Language on the right in editable fields. You cannot modify the base language data from this
page.

Setting Up SAP Ariba Supplier Lifecycle and Performance

106 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
 2. Select a language from the Translation Language dropdown menu.
3. Enter a translation for each piece of content in the corresponding translation field. If you have already entered
translations, they are displayed and you can edit them.
4. Select a new language from the Translation Langauge dropdown menu and continue adding translations, or
click Done.

Mapping form or questionnaire content to supplier

database fields
Mapping specific pieces of content in template forms and questionnaires to specific supplier database fields
makes them the source of data for those fields.

For example, a supplier request form needs to ask for the supplier's name. You create this field by adding a
question, titled something like Supplier Name:, to the form. If you do not map the question to a supplier
database field, the answer is simply stored in the database as value associated with the question. However, if you
map the question to the [Link].name1 field, the answer is stored in the database as the supplier's
name.

Mapped fields are synchronized with your ERP system's vendor master data. When a value is updated in the ERP
system, that update is synchronized to the mapped field in Ariba.

Most questionnaire content does not have to be mapped. However, any other form of questionnaire content that
you want to synchronize with the ERP system must be mapped to a supplier database field. For supplier projects,
these fields typically include basic supplier information (name, contact, address, bank acount, and other important
information). This reference [page 107] provides a list of common supplier database field names for basic
information.

Users in the SM Integration Administrator group can download a complete list of available supplier database field
names by clicking Manage SM Administrator on the dashboard, navigating to the Defaults area, and
downloading the Default_properties_sample.csv file.

Common supplier database field names for mapping

The following list of common supplier database field names is useful for mapping between a piece of form or
questionnaire content and a supplier database field that will be synchronized with the integrated ERP system.

Supplier name and ID fields

The information in these fields is used to determine possible matches to existing suppliers in the database.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 107
Field Name Description

[Link].name1 The name of the supplier.

Note
This field is required in supplier request forms.

[Link].name2 An alternate name for the supplier, or the name of a supplier's

parent company.

[Link].name3 A second alternate name for the supplier, or the name of a

supplier's parent company.

[Link] The ID of the supplier in your organization's ERP vendor mas­

ter.

A supplier created in Ariba will not have an ERP vendor ID until

it is synchronized with the ERP system. That synchronization
can be manual or automatic, and can occur at different points
in the lifecycle, depending on your organization's integration
configuration.

[Link] The supplier's Dun & Bradstreet DUNS number.

[Link] Any certificates that the supplier provides, such as diversity or

green certifications. Map questions with the Certificate an­
swer type to this field.

Supplier contact fields

Field name Description

[Link] The first name of the supplier contact, the person to whom the
registration questionnaire invitation is sent by default.

Note
This field is required in supplier request forms.

[Link] The last name of the supplier contact, the person to whom the
registration questionnaire invitation is sent by default.

Note
This field is required in supplier request forms.

Setting Up SAP Ariba Supplier Lifecycle and Performance

108 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
 Field name Description

[Link] The email address of the supplier contact.

Note
This field is required in supplier request forms.

[Link] The phone number of the supplier contact.

Note
This field is recommended in supplier request forms.

[Link] The locale of the supplier contact. Map a question that uses
master data of type Locale as the acceptable answer value to
this field.

Note
This field is recommended in supplier request forms.

Supplier address fields

The information in these fields is used to determine possible matches to existing suppliers in the database.

Field Name Description

Address :: address A predefined set of address fields: Street, City, State/

Province/Region, and Country.

Map questions with the Address answer type to this field.

address.line1 The first line of the supplier's street address. The information
in address fields is used to determine possible matches to ex­
isting suppliers in the database.

[Link] The city of the supplier's street address. The information in

address fields is used to determine possible matches to exist­
ing suppliers in the database.

[Link] The state or province of the supplier's street address. The in­
formation in address fields is used to determine possible
matches to existing suppliers in the database.

[Link] The postal code of the supplier's street address. The informa­
tion in address fields is used to determine possible matches to
existing suppliers in the database.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 109
 Field Name Description

[Link] The country of the supplier's street address. The information

in address fields is used to determine possible matches to ex­
isting suppliers in the database.

[Link] The ISO language code for the language of the supplier's ad­
dress.

Supplier tax fields

The information in these fields is used to determine possible matches to existing suppliers in the database.

Field Name Description

[Link] An identifier for the tax authority to which the supplier reports.

taxInfo.taxNumber1 A set of unique identifiers for the taxes to which the supplier is
subject, as defined by the tax authority.
taxInfo.taxNumber2

taxInfo.taxNumber3

taxInfo.taxNumber4

taxInfo.taxNumber5

[Link] XX What is this?

[Link] An indicator for whether or not the tax is split.

[Link] The type of the tax, such as withholding.

[Link] The VAT number assigned to the supplier.

[Link] XX What is this?

[Link] An identifier for the base percentage subject to tax.

[Link] An indicator for whether or not the supplier is subject to sales

tax.

[Link] An indicator for whether or not the supplier is subject to VAT.

Setting Up SAP Ariba Supplier Lifecycle and Performance

110 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
Supplier bank account fields

Field Name Description

[Link] A name for the supplier's bank account.

[Link] The supplier's bank account number.

[Link] All of the information about a supplier's bank account. This

field can include the account number, routing number, bank
name, bank key, and other information.

[Link] The type of the supplier bank account; for example, checking.

[Link] The control key for the bank. XX what is this?

[Link] The country in which the supplier's bank operates.

[Link] A unique identified, which is usually assigned to the bank by

the country in which it operates.

[Link] The date from which the supplier bank information is valid.

[Link] The date to which the supplier bank information is valid.

Commodity, region, and project field names

These fields are for Ariba use only and are not synchronized with an ERP system.

Field Name Description

[Link] The commodities associated with the supplier.

Map questions with answer type Commodity to this field.

[Link] The regions associated with the supplier.

Map questions with answer type Region to this field.

[Link] The preferred supplier status level for the supplier.

In forms that allow internal users to request preferred status

changes for a supplier, map questions about the requested
level to this field.

[Link] An approval level from the legal department.

[Link] An approval level from the finance department.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Creating supplier forms, questionnaires, and internal surveys CUSTOMER 111
 Field Name Description

[Link] An approval level from quality auditors.

[Link] An approval level from green auditors.

[Link] An approval level from the procurement department.

[Link] An approval level from the line of business.

[Link] A manually entered risk score.

Setting Up SAP Ariba Supplier Lifecycle and Performance

112 CUSTOMER Creating supplier forms, questionnaires, and internal surveys
Adding project groups and team members to
project templates

Adding project groups and team members to project templates [page 113]

Buyer category assignments versus team member rules [page 114]

Using buyer category assignments to add team members to project groups [page 115]

Using team member rules to add project groups and team members [page 116]

Adding project groups and team members to project

templates
You add project groups to project template teams in one of two ways:

● By manually adding project groups on the template’s Team tab. The groups you add in a template are added
to every project created from the template. You add project groups on a template’s Team tab as you would
add groups to a project. You can also specify if project owners can edit a project group in projects created
from the template (Can owner edit this Project Group). You can also add individual users or entire user
groups to project groups. For supplier request, registration, qualification, and preferred supplier management
project groups, if your site includes user assignments to project groups, commodities, and regions, you can
specify that members of a project group are added dynamically based on assignment (Apply buyer category
assignment matrix).
● By creating team member rules. Team member rules dynamically add groups or individual users to a project
based on the values supplied during project creation.

Note
In projects, use either the buyer category assignment matrix or team member rules to assign users to groups in
a supplier project template. Do not use both. Buyer category assignments apply to all project groups to which
they are applied in all supplier templates. Team member rules must be added to each project template's team
separately.

Adding Project Owners to Project Teams

To specify members of the Project Owner group that are inherited by projects created from a template, you must
use either buyer category assignments or team member rules.

Members manually added to a Project Owner group from a template’s Team tab are not inherited by any projects
created from that template. Manually adding members to the Project Owner group for a template grants those
users Project Owner rights for that template only.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Adding project groups and team members to project templates CUSTOMER 113
Buyer category assignments versus team member
rules
In supplier project templates for supplier requests, registration, qualification, and peferred status management,
you can dynamically add users to project groups using one of two methods: buyer category assignments or team
member rules.

It is important to understand the advantages and disadvantages of each method before you choose which
approach you want to use.

Buyer category assignments Team member rules

Purpose: Designed to add category or supplier Designed to add team members to a

managers to all of the related supplier specific type of project based on project
projects for suppliers of specific com­ attributes.
modities in specific regions, so that they
manage the same suppliers through
their lifecycles.

Implementation: Imported as site master data and auto­ Created and uploaded in each individual
matically apply to all supplier projects. project template. Updates must be made
Updates to the master data update all in indiviudal templates as well.
projects automatically.

Template project group creation: Template creators must manually add Project groups specified in team mem­
the project groups specified in the cate­ ber rules files in the project template are
gory assignment data to the supplier automatically added to projects when
templates. they are created from the template.

Criteria for project group membership: Use only commodity and region to as­ Use commodity, region, department, and
sign users to project groups. permission groups such as Classified
Access to assign users to project
groups.

Note
Buyer category assignments are not available in SPM projects. You must use team member rules for them.

Related Information

Using buyer category assignments to add team members to project groups [page 115]
Using team member rules to add project groups and team members [page 116]

Setting Up SAP Ariba Supplier Lifecycle and Performance

114 CUSTOMER Adding project groups and team members to project templates
Using buyer category assignments to add team
members to project groups
In order to use buyer category assignments to add team members to project groups, you must apply the buyer
category assignment matrix to them.

By default, project groups (including Project Owner) do not use buyer category assignment.

How to use buyer category assignments to add team

members to project groups

Prerequisites

You can only apply buyer category assignments to project groups in supplier request, registration, qualification,
and preferred supplier management templates.

Buyer category assignment data must be imported into your site in order for users to be added to project groups
based on those assignments.

In order to make supplier or category managers the owners of those supplier projects based on commodity and
region assignments, you must edit the Project Owner group to apply the category assignment matrix to it and
make sure that the system user aribasystem is a member of the group.

Procedure

1. Open a supplier template for editing. If the template status is not Draft, create a new version so that you can
edit it [page 79].

2. On the Team tab, choose Actions Team Members Edit .

3. Perform one of the following actions:

○ To edit an existing project group, click its name.

○ To add a new group, click Add Group and enter a name for the group.
4. For Apply buyer category assignment matrix, choose Yes.
5. Click OK.
6. (Optional) Use the dropdown menu in the Members column to manually add individual users or user groups to
the group.
7. Click OK.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Adding project groups and team members to project templates CUSTOMER 115
Using team member rules to add project groups and
team members

About team member rules files

You can use team member rules files to automatically add project team members when a project is created. To
pre-populate the Project Owner group from a template, you must use a team member rules file. (If you add users
to the Project Owner group in a template from the Team tab, those users will be members of the Project Owner
group for that template project only; they are not inherited by any projects created using that template.)

Note
In supplier request, registration, qualification, and preferred supplier management project templates, you can
use buyer category assignments to populate the Project Owner groups from the template instead. However,
buyer category assignments are not available in other project template types, including SPM project templates.

Team member rules files are a specific type of template document. They are always Microsoft XLS workbooks.
Unlike other project documents, you can upload team member rules files on the template’s Team or Documents
tab. However, once you have uploaded a team member rules file, you manage it as you would any other template
document on the Documents tab.

Team member rules files help you standardize your template creation process. Your company can create different
rules files for different kinds of projects, such as projects in different regions, or projects that are associated with
different commodity categories. For example, you can create team member rules files to route ownership of
projects to the people at your company who are responsible for a particular region or commodity category. When a
user creates a project with the appropriate region or commodity categories, the project uses the team member
rules to populate the team with the correct members for that region or commodity category. Whenever someone
edits a project, the team rules are re-processed to update team membership based on the changes.

You create team member rules using the following general steps:

1. Download a team member rules file template that contains the project template’s current project groups and
field names; see Creating Team Member Rules Files [page 118].
2. Create team member rules in the file; see Creating Team Member Rules Files [page 118].
3. Upload the team member rules file to the project template; see Adding Team Member Rules to a Template
[page 121].

Related Information

Using buyer category assignments to add team members to project groups [page 115]

Setting Up SAP Ariba Supplier Lifecycle and Performance

116 CUSTOMER Adding project groups and team members to project templates
Team member rules file templates

The team member rules file template contains the following tabs:

● Instructions: A set of instructions for using the team member rules file.
● Team Member Rules: A worksheet where you create team member rules by entering values in columns.
● Field Names: A list of the full names of all of the template’s current fields in dot notation.
● Project Groups: A list of all of the template’s current project groups.

You use the information on the Field Names and Project Groups tabs to create team member rules on the Team
Member Rules tab.

The Field Names and Project Groups tabs are populated with all of the current fields and project groups in the
template at the time you download the team member rules file template. If you add project groups or fields to the
template, you can download the file again to see those additional values on the Field Names and Project Groups
tabs.

If your site uses the supplier profile questionnaire to gather information about suppliers, you can also create team
member rules based on published supplier profile questionnaire content that is available for reporting. The content
must have a single response; you cannot create rules based on questionnaire content that has multiple responses,
such as multiple choice questions. If you add reportable content to the profile questionnaire, you must re-publish it
and then download the file again in order to see those additional values on the Field Names tab. For more
information on supplier profile questionnaire content, see Managing the Supplier Profile Questionnaire. If your site
uses supplier request and registration projects and registration questionnaires to gather information about
suppliers, the content of those questionnaires is not available in team member rules templates.

Rule matching in projects

Each row on the Team Member Rules tab creates a rule. Ariba Spend Management reads the rules file and, if all of
the Field_Name values in a row match in the project created from the template, it does the following in the new
project:

● Assigns the users in the User or Group columns to the project specified in the ProjectGroup column.
● Makes any user specified in the OwnerId column the default project owner.

When Ariba Spend Management matches values to add team members, it uses the following criteria for each row
in the rules file:

● All values in field name columns must match the template project’s values for those fields or the row is not
considered a match and is ignored. For example, if the rules file uses [Link]
and [Link] field name columns, the values in both of those columns must match the
project template’s values. If only the [Link] value matches, the row is ignored
and the users or groups are not added to the project group or made the default project owner.
If a rule (row) does not match and is ignored, processing continues to the next rule (rule evaluation does not
stop).
● Wildcards (*) and empty column values always match. For example, if the rules file uses
[Link] and [Link] field name columns, and the
[Link] value matches while [Link] is a wildcard, the
row matches and the users or groups are added to the project group or made the default project owner.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Adding project groups and team members to project templates CUSTOMER 117
● Hierarchical field matches can be matched by child field values. For example, if you use a Commodity as a field
name column and specify a top-level commodity value in the rules file, any project value that is a child of the
top-level commodity will match. If the field in the template project uses any of the child commodities under
that parent, the row matches and the users or groups are added to the project group or as the default project
owner.
Child field matches can be used for the Commodity, Regions, Departments, and Product hierarchical fields.

How to create team member rules files

Procedure

1. Create or open a project template.

2. Download a team member rules template that contains the project template’s current project groups and field
names. On the template’s Team tab, choose Actions Team Member Rules Download Template .
3. Save the team member rules file template XLS file to the location of your choice.
4. Edit the team member rules file template to create team member rules. Enter values in columns on the Team
Member rules sheet according to the following table.

If you want the rule to apply to all of the possible values for a column, enter a wildcard (*) in the column or
leave it blank.

If you want the rule to apply to a range of values for a column, use the tilde character (~). Range expressions
are inclusive on the lower boundary but not on the upper boundary. For example, to create a rule that applies
to every value of 1000 and over, enter 1000~; to create a rule that applies to every value from 0 to 3, enter
0~4; to create a rule that applies to every value below 1000 (but not 1000 itself), enter ~1000. You can only
use range expressions in rules for numeric fields.

Setting Up SAP Ariba Supplier Lifecycle and Performance

118 CUSTOMER Adding project groups and team members to project templates
 Column Description

Field_Name The Field_Name columns represent the names of different Ariba Spend Management fields. If
the Field_Name value you specify in this column matches values in a project created from the
template, the template adds the users or groups in the row to the project group, or makes the
specified user the default project owner. For the Supplier field in supplier workspace profiles,
you must include the full field name using dot notation; for example, the full name of the
Country field is [Link]. The Field Names tab in a
team member rules file template lists the full names for all current fields in the project tem­
plate from which it was downloaded.

You must always supply either a specific value or a wildcard for Field_Name columns. You
cannot enter multiple values in a Field_Name column. However, you can include multiple
Field_Name columns in a rule file; the values in all Field_Name columns in a row must match
in order for the template to add the users or group to the project group, or to make the speci­
fied user the default project owner.

Some data field values must match specific values in the system, such as values for regions or
commodity codes. For these field types, you can use an export task to find out what the spe­
cific values should be. If you cannot access the necessary export events, contact the Cus­
tomer Administrator in your organization.

If you are using date fields or data fields with numeric values that are mapped to an element in
a vector, such as commodity codes, you must force Microsoft Excel to store the value as text.
To do this, either change the format of the column to type Text in Microsoft Excel or prefix the
value with an apostrophe (‘); for example, for a value of 500, enter ‘500.

Note
Values for countries must be 2-letter ISO country codes.

For more information about how the system matches values in Field_Name columns with val­
ues in projects, see Understanding Rule Matching in Template Projects [page 117].

ProjectGroup The name of the project group to which you want to add users or groups; for example, Project
Owner. You must supply a value for this column. The Project Groups tab in a team member
rules file template lists all of the current project groups in the project template from which it
was downloaded.

User The user names of the users you want to assign to a project group; for example, bobsmith.
You do not have to supply a value for this column; you should only use it if you want to assign
individual users to the project group.

You can enter one user name, or multiple user names separated by colons (:); for example,
bobsmith:tomjones:anndavis.

PasswordAdapter The password adapter associated with the user name or user names. Ariba Spend Manage­
ment uses password adapters to distinguish between users that have the same user names.
The default password adapter values are PasswordAdapter1 (for internal users at your
company, the buyer organization) and SourcingSupplierUser (for external supplier and
customer organization users). Use this column only if you have also entered one or more val­
ues in the User column.

You can only enter one value per row in this column, so if you want to create rules for both
buyer and supplier users, you must create two separate rules, one for each
PasswordAdapter value.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Adding project groups and team members to project templates CUSTOMER 119
 Column Description

Group The name of the global user group that you want to assign to the project group; for example,
Supplier/Customer Manager or Supplier Registration Manager

You do not have to supply a value for this column. If you do supply a value, and you also supply
a value in the User column on the same row, both values are added to the project group. You
can enter one group, or multiple groups separated by colons (:).

OwnerID The user name of the default project owner for all projects created from the template; for ex­
ample, bobsmith.

You do not have to supply a value for this column; you should only use it if you want to make a
specific user or users the default project owner for all projects created from the template. If
there is no value specified in this column, the new project is owned by the user who created
the project and the members of the Project Owner group.

In the supplier workspace, request, registration, qualification, and preferred supplier manage­
ment templates, the project owner is the account owner or category manager for the supplier.
You can assign specific users as owners for specific projects created from the template, or
specify aribasystem as the default, unassigned owner. Specifying aribasystem in the
template means that the person who creates the project is not the project owner by default, so
that ownership of the supplier project can be assigned to the correct owner at a later time.

Note
You should exercise caution when making a single user a default project owner in the tem­
plate. When a user creates a project that matches the template’s rules for default project
ownership, the user who created the project is not the project owner and cannot manage
the project; only the default project owner can. There are specific cases where default
project ownership is useful. For example, whenever different users in solutions that include
Ariba Supplier Information Management or Ariba Supplier Information and Performance
Management create unapproved supplier organizations, they automatically create associ­
ated supplier workspaces that they are not intended to manage; your supplier workspace
template should route default ownership of those supplier workspace projects to the spe­
cific Supplier/Customer Manager users who manage specific sets of suppliers. However,
it is usually important for the user who created a contract workspace, Ariba Sourcing event,
or SPM project to own and manage the project, instead of using the template to assign a
default owner.

OwnerPasswordAdapter The password adapter associated with the owner’s username. The default password adapter
values are the same as those for the PasswordAdapter column. Use this column only if you
have also entered one or more values in the OwnerId column.

Hierarchical region example

The following example shows a team member rules file with a rule that specifies a parent region (APAC):

Region,ProjectGroup,Group,User,PasswordAdapter,OwnerId,OwnerPasswordAdapter

APAC,My Project Group,My Group,xleo:hlei,PasswordAdapter1,hlei,PasswordAdapter1

Setting Up SAP Ariba Supplier Lifecycle and Performance

120 CUSTOMER Adding project groups and team members to project templates
The region APAC is a parent region that contains China as a child. If a project created from the template has China
as its Region field value, the following additions are made to the project:

● every user in the global My Group group is assigned to the My Project Group project group
● the users xleo and hlei are assigned to the My Project Group project group
● the user hlei becomes the default project owner

How to add team member rules to a template

Context

You add team rules to a template by uploading team member rules files on the Documents or Team tab. You
cannot create tasks for team member rules file documents or set conditions on them.

There is no limit to the number of team member rules files you can add to a template. Each team member rules file
that you upload to a template adds to the total set of team member rules the template uses. To modify a
template’s existing team rules, you must make edits to the appropriate team member rules file on your local
computer and upload the file as a replacement document.

Procedure

1. Create or open a project template. If the status is not Draft, create a new version as described in Creating a
New Version of a Template and Enabling Editing [page 79].

2. On the Team tab, choose Actions Team Member Rules Upload Rules File .
3. Click Browse and navigate to the team rules file.
4. Add an optional description. Ariba recommends that you describe the type of rules the file creates, so that
users who edit the template can see them at a glance.
5. Set other properties for the rules file, such as base language and keywords.
6. Click Create.

Results

The uploaded team member rules file now appears on the template’s Documents tab.

How to validate team member rules

Context

Setting Up SAP Ariba Supplier Lifecycle and Performance

Adding project groups and team members to project templates CUSTOMER 121
Procedure

1. On the Documents tab, click the team rules file you want to validate and choose Publish.

If the team member rules file does not contain any syntax or data errors, the document publishes. If it does
contain errors, a validation error message displays at the top of the page, and the team member rules file
document is not published. You cannot publish a template that contains team member rules files with
validation errors.
2. If you see a validation, correct the problems in the team member rules file and publish it again. Validation error
messages are displayed at the top of the Ariba page.

Setting Up SAP Ariba Supplier Lifecycle and Performance

122 CUSTOMER Adding project groups and team members to project templates
Setting up supplier form and questionnaire
approvals

Each supplier template includes a defalt approval task for template's form or questionnaire. You use that task to
define the form or questionnaire's approval process.

About approval rules in project templates [page 123]

Using commodity and region assignments or team member rules for form and questionnaire approvals [page
125]

How to create or edit approval rules [page 129]

About the approval rules editor [page 130]

How to create a simple approval rule [page 132]

How to edit approval flows with the approval process diagram [page 133]

Using approval rule conditions [page 135]

How to add approvers in the approval rule editor [page 137]

How to add approvers from approver lookup tables [page 139]

About approval rules in project templates

Template authors can use the approval rule editor to create or edit sets of custom approval rules that can include
both parallel and serial approvers, conditions for approvers, or approval rule lookup tables.

Template authors can also specify a simple set of parallel or serial approvers directly in the Approvers or
Reviewers field. This method provides a simple way to specify approvers but does not include all the functionality
provided by the approval rule editor.

About serial and parallel approvers

Approvers (or reviewers) can be serial or parallel approvers.

Serial approvers are assigned consecutively in the order they appear in the approval flow diagram (from left to
right). Ariba Spend Management does not activate a node in a flow (assign a task to the approver in the node) until
the preceding approvers (approvers to the left in the approval flow) have submitted approvals or reviews. In the
following approval flow, Ariba first assigns the task to user AAA. After AAA submits his or her approval, Ariba
assigns the task to user BBB.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier form and questionnaire approvals CUSTOMER 123
Parallel approvers are assigned simultaneously. Ariba Spend Management assigns the task to the approvers at the
same time. In the following approval flow, Ariba assigns the task to users AAA and BBB at the same time.

An approval flow can contain a combination of both parallel and serial approvers.

About groups in approval flows

When you add a group to an approval (or review) flow, Ariba Spend Management can either:

● Expand the group (and any subgroups) and insert each user as a parallel approver (or reviewer) in the
approval flow. Each user receives notification about the task. All users in the group are needed to approve (or
review) the document. After all users in the group approves (or reviews) the document, the approval flow
moves to successive approvers.
● Insert the group as a single unit in the approval flow. All users in the group receive notification about the task.
Any one user in the group is sufficient to approve the task (or move to the next approver in a serial flow).

The behavior when you add a group to an approval flow is determined by the method you use to add the approver.

● If you add a group using the graphical approval flow editor, the pane for adding an approver contains the
option All approvers need to approve? If you select No, Ariba Spend Management inserts the group as a
single unit in the approval flow. If you select Yes, Ariba Spend Management expands the group and inserts
each user as a parallel approver. The default value is No.
● If you add a group as an approver directly in an editable Approvers or Reviewers field in a task window for a
serial or parallel approval flow, Ariba Spend Management does not expand the group.
● If the group was inherited from an approver lookup table file in the template, Ariba Spend Management does
not expand the group.

Setting Up SAP Ariba Supplier Lifecycle and Performance

124 CUSTOMER Setting up supplier form and questionnaire approvals
Removing and adding approvers in task rounds

Approvers added to a task before the task is submitted cannot be removed after the task is submitted for that
round. However, these approvers can be removed in any subsequent rounds (if the approvers were not specified in
the project template).

Approvers added after a task is submitted are retained only for the current round. If a new review or approval
round is created, the new round does not include any approvers added after the task was submitted.

If you click the Properties tab for a task, you see only the reviewers or approvers in the flow that were present
when the task was submitted. Ariba Spend Management does not show reviewers or approvers added after the
task was submitted. To view reviewers or approvers that were added after the task was submitted, you must click
View Task Details and then click the Review Flow, Negotiation Flow, or Approval Flow tab.

Using commodity and region assignments or team

member rules for form and questionnaire approvals
After adding members to supplier project teams using either user commodity and region assignments or team
member rules, you can use that dynamic team membership to construct approval flows for supplier forms and
questionnaires.

Example: how to create a conditional approval flow using

commodity and region assignments

This example uses conditions commodity and region assignments to add the appropriate category or supplier
managers and other stakeholders to the approval flow to a supplier request form.

Prerequisites

This example assumes that the following commodity, region, and project group assignment data is loaded in the
site:

Project Owner,801116,unspsc,USA,ljenkins,PasswordAdapter1
Human Resources,8011,unspsc,USA,tjones,PasswordAdapter1
Human Resources,8011,unspsc,Canada,ayang,PasswordAdapter1
Global Services,80,unspsc,All,rbarney,PasswordAdapter1

This data assigns:

● Larry Jenkins (ljenkins) to the Project Owner project group for all temporary personnel services (UNSPSC
code 801116) in the United States. He is a category manager for temporary labor and will manage all
temporary labor suppliers in the US.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier form and questionnaire approvals CUSTOMER 125
● Theresa Jones (tjones) to the Human Resources project group for all temporary labor services (UNSPSC code
8011) in the United States. Theresa Jones is in US Human Resources department and must approve all US
temporary labor suppliers.
● Alan Yang (ayang) to the Human Resources project group for all temporary labor services (UNSPSC code
8011) in Canada. Alan Yang is in the Canadian Human Resources department and must approve all Canadian
temporary labor suppliers.
● Regina Barney (rbarney) to the Global Services project group for management and business professionals and
administrative services UNSPSC code 80) for all regions. Regina Barney is the member of the global services
department who must approve all suppliers of services.

Context

Although this example uses commodity and region assignments, it applies equally as well to projects where team
membership is assigned based on team member rules. The only difference is that team member rules
automatically create the project groups specified in the rules, while with commodity and region assignments, you
must manually add the specified project groups to the project template.

In this example, a category manager must approve the supplier registration; if it is for a temporary labor supplier, a
human resources representative must approve the registration in parallel; after that, all registrations for services
are sent serially to the global services department for final approval.

Procedure

1. Open the Supplier Registration Template. If the status is not Draft, create a new version as described in
Creating a New Version of a Template and Enabling Editing [page 79].
2. Since Human Resources and Global Services are not default Ariba groups, create them by performing the
following steps:

a. On the Team tab, choose Actions Team Members Edit .

b. Click Add Group.
c. For Apply buyer category assignment matrix, choose Yes.
d. In the Title field, enter Human Resources.
e. Click OK.
f. Repeat these steps to add the Global Services project group.

The Project Owner group is always included in projects, so you do not have to add it manually. However, make
sure that the aribasystem system user is a member of the group; it is a requirement for adding users to the
Project Owner group dynamically.
3. Create conditions for the temporary labor and management and business professionals and administrative
services commodities by performing the following steps:
a. On the Conditions tab, click Add Condition.
b. Enter a name for the condition, such as Temporary Labor Services, and a description, such as
Applies when the commodity is temporary labor services.
c. Click the action triangle button () next to All Are True and choose Add Condition Field Match .

A new condition component for selecting the field appears.

Setting Up SAP Ariba Supplier Lifecycle and Performance

126 CUSTOMER Setting up supplier form and questionnaire approvals
 d. Click Select and choose Commodity.
e. Click the Select menu to the right of (No Value Selected) and choose Select Value.
f. In the commodity window, click select.
g. Expand Management and Business Professionals and Administrative Services and select Human
resource services, which is one level under it, then click Done.
h. Click OK.
i. Repeat the previous steps to add a condition named Management and Business Professionals
and Administrative Services, with that commodity selected for the expression.
4. On the Tasks tab, click the Approval for supplier request task and choose Edit Task.
5. For Approval Rule Flow Type, choose Custom.
6. Click Custom to open the approval flow editor.
7. In the task's default approval flow, the project owner is the approver. Add a parallel node for the US human
resources representative with a condition on the temporary labor commodity by performing the following
steps:
a. In the Approval Process Diagram area, click the action triangle button () to the left of the Project
Owner approval node and choose Add Parallel Rule.

A new, untitled approval node appears on the graph in parallel to the Project Owner node.
b. Click the new rule to select it.
c. In the Approval Rule Editor area, enter a name for the node, such as Human Resources, and a
description, such as Adds a member of the Human Resources department to the approval
flow for temporary labor suppliers.
d. In the Condition area, click the action triangle button () next to All Are True and choose Add
Condition Reference to Condition .
e. On the Reference to Condition dropdown menu, choose Search more, then click the Select button to the
right of the Temporary Labor Services condition.
f. Click OK.
g. In the Action area, for Type, choose Add Approvers and Groups.
h. From the Action dropdown menu, choose Add Project Group.
i. Make sure that All users in group have to approve is not selected. In this scenario, only the user in the
project group who is assigned to the specific supplier registration commodities and regions needs to
approve the registration.
j. Select Approval Required.
k. For ProjectGroup to be added to the flow?, on the dropdown menu, choose Search more. Click the
Select button next to Human Resources, then click Done.
l. For Reason for the specified approver(s) to be added to the flow , enter a reason such as A Human
Resources representative must approve requests related to temporary labor.
8. Next, add a serial node for the global services representative with a condition on the management and
business professionals and administrative services commodity by performing the following steps:
a. In the Approval Process Diagram area, click the action triangle button () to the right of the Project
Owner approval node and choose Add Parallel Rule.

A new, untitled approval node appears on the graph in parallel to the Project Owner node.
b. Click the new rule to select it.
c. In the Approval Rule Editor area, enter a name for the node, such as Global Services, and a
description, such as Adds a member of the Global Services department to the approval

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier form and questionnaire approvals CUSTOMER 127
 flow for management and business professionals and administrative services
suppliers.
d. In the Condition area, click the action triangle button () next to All Are True and choose Add
Condition Reference to Condition .
e. On the Reference to Condition dropdown menu, choose Search more, then click the Select button to the
right of the Management and Business Professionals and Administrative Services
condition.
f. Click OK.
g. In the Action area, for Type, choose Add Approvers and Groups.
h. From the Action dropdown menu, choose Add Project Group.
i. In this scenario, only the user in the project group who is assigned to the specific supplier request
commodities and regions needs to approve the request, so make sure that All users in group have to
approve is not selected.
j. Select Approval Required.
k. For ProjectGroup to be added to the flow?, on the dropdown menu, choose Search more. Click the
Select button next to Global Services, then click Done.
l. For Reason for the specified approver(s) to be added to the flow , enter a reason such as A Global
Services representative must approve requests related to management and business
professionals and administrative services.
9. Click Done.

Results

When you publish the template, and a supplier of temporary labor services in the United States submits a
registration questionnaire, the following actions occur in that supplier registration project:

● Category manager Larry Jenkins is added to the Project Owner group for the supplier registration and
becomes the project owner. He receives a notification that he needs to review the registration, then approves
or denies it.
● At the same time, human resources representative Theresa Jones is added to the Human Resources group
for the supplier registration. She receives a notification that she needs to review the registration, then
approves or denies it.
● Regina Barney is added to the Global Services group for the supplier request. After both Larry Jenkins and
Theresa Jones have approved the supplier registration, she receives a notification that it is her turn to approve
it. Her approval or denial is final.

Alan Yang is not added to the Human Resources group for the supplier registration, because he is assigned to
temporary labor services in Canada, and is therefore not a match for this supplier registration.

Setting Up SAP Ariba Supplier Lifecycle and Performance

128 CUSTOMER Setting up supplier form and questionnaire approvals
How to create or edit approval rules
Procedure

1. Create or open a project template. If the status is not Draft, create a new version as described in Creating a
New Version of a Template and Enabling Editing [page 79].

2. If the task does not already exist, select the appropriate document and click Create New Task Review ,
Approval, or Negotiation. The system opens a window to create the task.

If the task already exists, click the task name and click Action View Task Details . In the task area, click
Actions Task Edit .
3. Use one of the following methods to add approvers:

○ Specify a simple set of parallel or serial approvers directly in the Approvers or Reviewers field. Select
Parallel or Serial for the approval flow type, then use the pull-down menu in the Reviewers or Approvers
field to add approvers without using the approval rule editor. See Limitations when Specifying Approvers
in the Approvers or Reviewers Field [page 129] for limitations.
○ Open the approval rules editor. In the window for a new task or task without an approval flow, navigate to
the Approvers or Reviewers field, then click one of the following:

○ an approval flow icon (such as ).

○ a link for an approval flow type (Parallel, Serial, or Custom)
○ If you are working on an existing task with an approval flow, click View Task Details, then click the
Review Flow, Negotiation Flow, or Approval Flow tab.

Note
If you select Parallel or Serial for the approval flow type and use the approval rule editor to add
approvers, the system changes the approval flow type to Custom.

If you have a Custom approval flow and change the approval flow type to Parallel or Serial, the system
removes all customization data from the approval flow, including:
○ Any condition for each rule.
○ Any rule that uses an approver lookup table file.
○ The Required Approver or Watcher option. All approvers become required approvers.
○ The title, description, and reason for each approver.

Limitations when Specifying Approvers in the Approvers or

Reviewers Field

If the approval rule flow type is parallel or serial, template authors can specify a simple set of parallel or serial
approvers directly in the Approvers or Reviewers field, with the following limitations:

● The approval flow can contain either parallel or serial approvers, but not both parallel and serial approvers.
● You cannot add any watchers to the flow.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier form and questionnaire approvals CUSTOMER 129
● You cannot specify any conditions for the approvers.
● You cannot use approval rule lookup tables.
● You cannot move approvers in the flow.
● If you specify multiple serial approvers, you must add the approvers in order from last to first; the last reviewer
you specify will be the first approver in the approval flow.
● If you select a group as an approver, there is no option to expand the group and require all users in the group
to approve (or review) the document. Only one user in the group is needed to approve (or review) the
document. After one user in the group approves the document, the approval flow moves to successive
approvers. If you want to require all users in a group to approve a document, you must add the group using the
approval rule editor.
● You cannot use the Add Launch Approver or Add Contract Approver action to conditionally add the Sourcing
Approver or Contract Approver group to an approval flowSpecifying Actions to Add Approvers and Groups
[page 137].
● You cannot use the Add Supervisor action create a supervisor rule, which adds the supervisor of a user
project field to an approval flow by notification profiles.
● The system adds the following text as the reason for the approver: Action is required. By default, this text is
included in email notifications sent to approvers.

About the approval rules editor

As an alternative to specifying approvers directly in the Approvers or Reviewers field, you can use the approval
rule editor in a project template. The approval flow editor enables you to create a mix of parallel and serial
approvers and to specify conditional approvers. From top to bottom, the approval rule editor contains the
following sections:

● Approval Process Diagram. Add rules here or select a rule to see the condition and action.
● Approval Rule Editor. Specify or view the condition that triggers the action (add users or groups) for the rule
selected in the diagram. It contains the following sections:
○ Condition: Specify a condition for the action. If you always want the action to occur, use the default
condition (an empty All Are True condition).
○ Action. Specify or view the action taken when the condition is met. The action specifies if approvers are
added by selecting individual users or groups using a drop-down menu or by using an Approver Lookup
Table.
● Parameters. Specify parameters for the rule selected in the diagram. If you are not using an Approver Lookup
table, use the drop-down menu to select the users or groups to add to the approval flow.

Setting Up SAP Ariba Supplier Lifecycle and Performance

130 CUSTOMER Setting up supplier form and questionnaire approvals
For example:

The approval rules for a given task are shown in the Approval Process Diagram. Each approval rule consists of:

● A condition.
The condition in an approval rule contains one or more references to conditions defined for the template.
● An action.
The action adds specified approvers to the approval flow. If the condition is met, then the system performs the
action and adds the specified approvers to the approval flow.

Creating a condition is optional; if you do not create a condition, the default condition (an empty All Are True
condition) always evaluates to true and the action always occurs.

In this example, the approval process diagram has the rule Over $100M. The rule Over $100M is highlighted and
the editor shows the condition and action for this rule: if the template condition Contract Amount Over $100M
is true, the system takes the action to add the user Max Olson to the approval flow.

To configure approval rules, you:

1. Add one or more approval rules, which are shown in the approval process diagram. For information about
working with the approval process diagram, see How to edit approval flows with the approval process diagram
[page 133].

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier form and questionnaire approvals CUSTOMER 131
2. (Optional) Specify a condition for each approval rule. The condition contains references to template
conditions. The approval rule editor includes a feature that enables you to define a template condition if one
does not already exist. For information about working with conditions, see Working with Approval Rule
Conditions [page 135].
3. Specify an action for each approval rule to add approvers. For information about adding approvers, see How to
add approvers in the approval rule editor [page 137].

Related Information

How to create a simple approval rule [page 132]

How to create a simple approval rule

Context

Use the following procedure to create a simple approval rule without using an approval rules table. Each approval
rule adds one approver or group of approvers to the approval flow.

Procedure

1. Create a new task in a template or edit an existing template task from the View Task Details page.

2. Select the approval flow type and click the corresponding approval flow icon (such as ).
The approval rule editor opens.
3. In the approval process diagram, click Add Initial Rule.
4. Specify a a name in the Rule Title field and add text for the Rule Description.
5. Optional: If you always want the approvers in this rule to be added, leave the Condition area as it is
(containing only the All Are True statement). If you want to add the approvers based on a condition, see Using
approval rule conditions [page 135].
6. In the Action area, select Add Approvers and Groups if it is not already selected. From the Action pull-down
menu, choose the type of approver you want to add:

○ Add Approvers: adds one or more individual users, groups, or project groups.
○ Add Group: adds one global group.
○ Add Project Group: adds one project group.
○ Add Contract Approver: adds the Contract Approvers global group if the required conditions are met. For
more information, see Specifying Actions to Add Approvers and Groups [page 137].
○ Add Launch Approver: adds the Sourcing Approver global group if the required conditions are met. For
more information, see Specifying Actions to Add Approvers and Groups [page 137].
○ Add Supervisor. Adds the supervisor of a project user field (such as the Owner field) to the approval flow
using notification profiles. The rule can also be “chained” to repeatedly add supervisors.

Setting Up SAP Ariba Supplier Lifecycle and Performance

132 CUSTOMER Setting up supplier form and questionnaire approvals
 7. Specify the appropriate parameter values for the approvers as follows:

○ All users in group have to approve: This field is present only if you are adding a global group or project
group to the approval flow. If selected, the system expands the group and adds each user in the group as
an individual parallel node in the approval flow. Each user in the group must approve (or review) the
document.
○ If the All users in group have to approve option is not selected, the system adds the group as a single
entity in the flow and only one user in the group is needed to approve (or review) the document. After any
one user in the group approves the document, the approval flow moves to successive approvers.
○ Approval required: If selected, the approver must approve or review the document associated with the
task (this is the default value). If this option is not selected, the approver is added as a watcher. A watcher
cannot approve the task but can view the task and the approval flow.
○ Approving Group, Approver(s) to be added to the flow, or ProjectGroup to be added to the flow: Select
the group or users to be added.
○ Reason: Reason for adding the approvers. This field is optional. By default, the text you specify in this field
is included in email notifications sent to approvers.
8. To add additional approval rules to the flow, go back to the Approval Process Diagram and click the action
triangle button (  ) where you want to add the node in the flow.

The new node is highlighted in green to indicate that the contents of the Approval Rule Editor apply to this
node.
9. Click Done.

Related Information

About the approval rules editor [page 130]

How to edit approval flows with the approval process

diagram
Context

Each box, or node, in an approval flow represents an approval rule. Approval rules are processed in order from left
to right. When the system creates an approval flow from the approval rules, it evaluates the condition for each rule
and adds the approvers specified in the action for the rule.

Nodes in an approval flow have action triangle buttons () you can click to add or move nodes . To delete an
approval rule, click the “X” button ().

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier form and questionnaire approvals CUSTOMER 133
Procedure

1. Open the approval flow editor as described in Creating or Editing Approval Rules [page 129].
2. To add an approval rule:
a. Click the area in the approval flow where you want to add the approver (or reviewer).
○ If there are no approvers in the approval flow, click Add Initial Approver to add an approver. This
button is available only when there are no approvers.
○ If you are adding a serial approval rule to a flow with existing rules, click the action triangle button ()
where you want to add the approval rule.
○ If you are adding a parallel approval rule to a flow with existing rules, click the left-most action triangle
button () in the flow.
b. Choose Add Serial Node or Add Parallel Node.
c. To specify where the parallel rule or flow should connect back into the main approval process, click a blue
target (). (If there is only one position possible, the position is selected for you.)
d. In the approval rule editor below the diagram, enter a title and description for the new rule.
3. To move an approval rule:
a. Click the left or right triangle action button () beside the approval rule you want to move.
b. Choose Move Rule.

Blue targets ( ) indicate the possible positions for the rule.

c. Click one of the blue targets to move the rule to the corresponding position.

The updated diagram shows the new position of the moved rule.
4. To delete an approval rule:
a. Click the “X” button () on the approval rule you want to delete.
b. Click OK when prompted for confirmation.

Next Steps

● (Optional) Specify a condition for this rule (Using approval rule conditions [page 135]).
● Add approvers.

Related Information

How to add approvers in the approval rule editor [page 137]

How to add approvers from approver lookup tables [page 139]

Setting Up SAP Ariba Supplier Lifecycle and Performance

134 CUSTOMER Setting up supplier form and questionnaire approvals
Using approval rule conditions

Note
Specifying a condition for an approval rule is optional. If an approval rule has no condition defined, the system
always performs the action specified for that rule.

A condition for an approval rule consists of components. The components can be:

● References to a condition, which are references to a condition defined for the template. The approval rule
editor also enables you to create a template condition and add a reference to the new condition.
● Subconditions, which contain a set of condition components that are evaluated together with a series of logical
operators. Subconditions enable you to build conditions with multiple components.
● Document field matches, which evaluate to true or false depending on field values in document forms.

Note
You can also define conditions and actions based on an approver lookup table. For example, you could create a
lookup table that adds approvers based on commodity codes. For more information, see Adding Approvers
from Approver Lookup Tables [page 139].

A condition in an approval rule always contains at least one subcondition. In its simplest form, an approval rule
condition consists of a subcondition that contains a reference to a template condition. For example, you could
have the following condition expression:

All Are True Regions is equal to USA

This condition expression consists of the All Are True subcondition and the field match Regions is equal
to USA.

Note
All condition expressions start with a subcondition, even if the only additional component is a field match or a
reference to a condition.

References to a condition
When you choose to add a reference to a condition, the system opens a window with a chooser for conditions
already defined in the project template and a Create Condition link you can click to open the condition editor and
create a new condition for the template. For more information about the condition editor, see Defining Approval
Rule Conditions [page 136].

Subconditions
Subconditions enable you to group and evaluate a set of condition components as a whole.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier form and questionnaire approvals CUSTOMER 135
In the following figure, All Are True is the subcondition.

There are three subcondition types:

● All Are True. For this subcondition to be true, all the condition components that it contains must be true.
Conceptually, the All Are True subcondition places AND operators between the condition components in the
set.
● Any Are True. For this subcondition to be true, at least one of the condition components that it contains must
be true. Conceptually, the Any Are True subcondition places OR operators between the condition components
in the set.
● None Is True. For this subcondition to be true, all condition components that it contains must be false.
Conceptually, the None Is True subcondition uses NOT...AND NOT operators:
NOT condition component 1 AND NOT condition component 2 AND NOT condition component 3.

An approval condition can contain multiple subconditions (and components). You add condition components from
left to right in the condition builder. The components are evaluated in the opposite direction—from right to left.

How to define approval rule conditions

Context

Use the condition builder in the approval rule editor to define the condition for an approval rule.

Procedure

1. Open the approval flow editor as described in Creating or Editing Approval Rules [page 129].
2. In the approval process diagram, select the rule for which you want to build a condition.
3. Click the action triangle button () next to All Are True. All conditions must start with a subcondition even if
you plan to add only one other condition component. The default initial subcondition is All Are True. If you
want to change the subcondition type, scroll down to the Change To area and choose the new type. For more
information on subcondition types, see Subconditions [page 135].

To create a new template condition or to add a reference to a project template condition, click the action
triangle button next to All Are True, then click Reference to Condition.

The system opens a pane with a Reference to Condition field and a Create Condition link.

Setting Up SAP Ariba Supplier Lifecycle and Performance

136 CUSTOMER Setting up supplier form and questionnaire approvals
 To use an existing project template condition, click the arrow button next to the Reference to Condition field.
A chooser opens with the existing project template conditions.

To create a new project condition, click Create Condition. You can also use this link to define a document field
condition..
4. Enter a name for the condition, such as RegionIsEMEA.
5. Enter a description for the condition.
6. All conditions start with the subcondition All Are True. If you want to change the subcondition type, click the
action triangle button () next to All Are True, then select a type under Change To, such as None Is True.

7. To add a field match, click the triangle button next to All Are True, then click Add Condition Field
Match .

A field match builder opens. Click Select. A pull-down menu opens with project fields commonly used for field
matches.
8. Select a project field, such as Regions. If you want to use a field that is not listed or to use a subfield (such as
the country in the customer or supplier address), click more fields to open a complete list of project fields.
Click Select for the field you want to use and click Done.
9. Select an operator from the pull-down menu, such as is equal to.
10. Click Select to the right of the (No Value Selected) text to specify the value for the field match.

Depending on the data type for the field, the system displays a pull-down menu with acceptable values, a
selection pane, or data entry pane. Enter or choose the value, set of values, or range of values (as applicable)
that you want to match.

If a field can have multiple values, the system displays a selection pane. Clicking Select opens a chooser that
enables you to specify a set of multiple values for the field match. The condition will be true if any of the field
values in the set are matched. To create a condition that is true if all of the specified field values are matched,
you must create a condition expression with the All of operator and multiple field matches, where each field
match specifies a single value.
11. Continue adding condition components as necessary.
12. Click OK.

How to add approvers in the approval rule editor

Procedure

1. Open the approval rule editor as described in Creating or Editing Approval Rules [page 129].
2. In the Approval Process Diagram area, select the rule (node) for which you want to add approvers.
3. (Optional) Specify or create a condition for the action as described in Defining Approval Rule Conditions [page
136].
4. In the Action area, select one of the following options to add approvers.

○ Add Approvers and Groups: Specify a user, global group, or project group from the Action pull-down
menu.
You can also use this option to add the supervisor of a project user field (such as the Owner field) to the
approval flow. This action can also be “chained” to repeatedly add supervisors.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier form and questionnaire approvals CUSTOMER 137
 ○ Use Approver Lookup Table: Use an Microsoft Excel XLS lookup table to determine which approver to
add based on project field values. For example, you could have an approver lookup table that lists
commodity codes and specifies which approver to add for each code.
5. If you selected Add Approvers and Groups, navigate to the Action pull-down menu and select the type of
approver you want to add:

○ Add Approvers: adds one or more individual users.

○ Add Group: adds one global group.
○ Add Project Group: adds one or more project groups.
○ Add Launch Approver: adds the Sourcing Approver global group in Ariba Sourcing if the following
conditions are true:
-the task is an Approval for Publish task for a Sourcing event
-the user attempting to publish the event does not have PublishEvent permission
-the system parameter [Link] is set to no
○ Add Contract Approver: adds the Contract Approver global group in Ariba Contract Management if the
task is an approval task for an entire contract workspace or contract request.
○ Add Supervisor: adds the supervisor of a user in a selected user field using notification profiles.
6. Select the appropriate parameters and approvers. Complete the fields as follows:

○ All users in group have to approve

This field is present only if you are adding a global group or project group to the approval flow. If selected,
the system expands the group and adds each user in the group as an individual node in the approval flow.
Each user in the group must approve (or review) the document. If this option is not selected, only one user
in the group is required to approve (or review) the document. After one user in the group approves the
document, the approval flow moves to successive approvers.
○ Approval Required
If selected, the approver must approve or review the document associated with the task (this is the default
value). If this option is not selected, the approver is added as a watcher. A watcher cannot approve the
task but can view the task and the approval flow.
○ Approver(s) to be added to the flow
○
○ Group
Specifies the users, project group, or global group to be added to the approval flow. Click the pull-down
menu and then click Search for more to open a chooser.
○ Reason
Reason for adding the approvers.
7. Click Done.

Related Information

How to add approvers from approver lookup tables [page 139]

Setting Up SAP Ariba Supplier Lifecycle and Performance

138 CUSTOMER Setting up supplier form and questionnaire approvals
How to add approvers from approver lookup tables
Context

An approver lookup table maps field values to approvers. When project is created, the system compares project
field values with field values in the lookup table. If they match, the system adds the approvers specified in
matching entry.

When you define a new table, you define the field columns to include, the operation to use for evaluating the fields,
and the types of approvers to include. Then you export the column headers, fill in the data, and upload the file.

Procedure

1. Open the approval flow editor as described in Creating or Editing Approval Rules [page 129].
2. In the approval process diagram, select the rule for which you want to use an approver lookup tab.
3. (Optional) Specify or create a condition for the action as described in Defining Approval Rule Conditions [page
136].
4. In the Action section, select Use Approver Lookup Table.
5. Click Add Columns and add the project fields you want to evaluate to select approvers.
6. In the Operation pull-down menu, specify the operation to use when comparing the value specified in the
approver lookup table with project field values. The default is equal to.

The operator is applied to every field value in the selected column. To use different operators for the same
field, you must create additional approver rules and approver lookup table files.
7. Under Approver Type Fields, select one or more check boxes for the types of approvers you want to include in
the file. For information about types of approvers, see Types of Approvers in Approver Lookup Tables [page
140].
8. To create a Microsoft Excel file template containing the columns you specified, click Export Column Headers,
and save the file. The default file name is [Link], where SiteName is the name given
to your Ariba customer site. You can rename the file with a more descriptive name.
9. Open the file and enter field values.

For example:

Region User Tooltip Required

USA molson Add M. Olson for USA TRUE

APAC achang Add A. Chang for TRUE

APAC

EMEA bfox Add B. Fox for EMEA TRUE

For information about field values, see Approver Lookup Table Field Values [page 140].

10. To upload the edited approver lookup table file, verify that you have selected the appropriate rule and that Use
Approver Lookup Table is selected for the Action. Upload the file by clicking Upload File. A sample of the data
you entered appears in the table.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier form and questionnaire approvals CUSTOMER 139
Types of approvers in approver lookup tables
When you work with approver lookup tables, you select the types of approvers to include by clicking one or more
Approver Type Field check boxes. For each check box that you click, a column is included in the exported file.

● User lets you specify one ore more users by user ID. Separate multiple IDs with colons.
● Group lets you specify one or more groups. Separate multiple names with colons. To specify a global group,
enter the group name.
To specify a project group, enter the project group ID (PGnnnnn). If you do not know the project group ID, you
can display it by returning to the Action area, and selecting Add Approvers and Groups. Select Add Project
Group. In the ProjectGroup to be added to the flow pull-down menu, choose Search for more. The system
opens a chooser for project groups that includes an ID column for the project group ID.
○ If you copy a template, the project group IDs in the new template will be different than the IDs in the
original template. After you copy a template, determine the project group IDs in the new template and
update the approver lookup table with the new IDs.
○ If you import a template, the system replaces project group IDs in the imported template if the project
group IDs are already used by another template. After you import a template, verify that the project group
IDs in the approver lookup tables match the project group IDs in the template and update the approver
lookup tables if needed.
● ApproverList lets you specify multiple user IDs or unique group names. Separate the IDs with colons. Users in
a list are added to the approval flow as one single approver. Only one user in the list needs to approve.
● ApproverFieldPath lets you add an approver based on a field path relative to an object specified in a column of
the approver lookup table file. This type is useful if you have custom master data that includes a user or group
as a subfield. Contact Ariba Customer Support if you want to use approver field paths. All field paths used in
approval rules must be approved by Ariba Customer Support.

Approver lookup table field values

When you click Export Column Headers from the approver lookup table window, Ariba creates a Microsoft Excel
file with:

● one or more columns for project fields (field_name columns, where field_name is a project field name,
such as Amount or Commodity)
● one or more columns for approvers (approver_type columns, where approver_type is the type of
approver to add, such as Group or User)
● a Tooltip column
● a Required column

For example:

Amount User Tooltip Required

The field values for approver lookup tables are described in the sections that follow.

Setting Up SAP Ariba Supplier Lifecycle and Performance

140 CUSTOMER Setting up supplier form and questionnaire approvals
field_name

Each field_name column represents a project field. Enter a value in the cell that you want to compare with the
value for this field in projects created from this template. The system uses the operator specified in the Operation
field when comparing the values; the default operator is equal to. If the comparison is true, the system adds the
approvers specified in the approver_type field for this row.

If there are multiple field_name columns, the system only adds the approvers in the row if all field comparisons
are true in the row (the system uses the logical operator AND when evaluating multiple field comparisons).

If the operator is is between, specify two values separated by a dash (-). The is between operator matches values
greater than or equal to the first value and less than the second value. For example, 1000-1000000 matches the
following values: 1000, 1001, and 999999. It does not match the value 1000000.

Some data field values must match specific values in the system, such as values for regions or commodity codes.
For these field types, you can use an export task to find out what the specific values should be. If you cannot
access the necessary export events, contact the Customer Administrator in your organization.

If you are using data fields with numeric values that are mapped to an element in a vector, such as commodity
codes, you must force Microsoft Excel to save the value as text by prefacing the value with an apostrophe ( ' ).

To specify a wildcard match in a field, enter an asterisk ( * ) in the field.

Empty field values are treated as null strings.

approver_type

Each approver_type column represents the type of approvers to be added and will be one of the following
values: User, Group, ApproverList, or ApproverFieldPath.

For descriptions of the types and how to specify the values for these types, see Types of Approvers in Approver
Lookup Tables [page 140].

Tooltip

Contains text for the system to display when users mouse over the node in an approval flow.

Required

Specify TRUE to add the approvers in this row as required approvers; specify FALSE to add the approvers as
watchers.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier form and questionnaire approvals CUSTOMER 141
Approver lookup table examples

Approver lookup table file with commodity code

The following example adds the user Ann Alcott to the approval flow if the Commodity field for the project is 44,
which maps to office equipment for this customer. Note that the value for the Commodity field is prefaced with an
apostrophe ('44), which forces Microsoft Excel to store the data as text.

Commodity User Tooltip Required

'44 aalcott Add A. Alcott for TRUE

office products

Approver lookup table file with multiple field values

You can specify only one value in a field_name column. If you want to add the same approver for multiple field
values, you must add a row for each possible field value. For example:

Region User Tooltip Required

USA molson Add M. Olson for USA TRUE

APAC molson Add M. Olson for APAC TRUE

If an approver lookup table file contains multiple rows, the system reads the entries in order and selects the first
entry that evaluates to true when comparing all fields in the entry. If you have multiple rows, place more specific
entries before less specific entries. For example, you want to have one approver for the Region HI-USA and
another approver for all other regions in the USA. HI-USA is a child of the region USA. You can specify the
operation is child of for the Region field and create the approver lookup table as follows:

Region User Tooltip Required

HI-USA aalcott Add A. Alcott for USA TRUE

USA molson Add M. Olson for USA TRUE

Do not reverse the order of the rows. If you do so and use the operation is child of for the Region field, Ariba Spend
Management would select the entry for the region USA even when the region in a project is HI-USA.

Approver lookup table file with multiple numeric field values

The following example uses the operator is greater than or equal to for the Amount field. Note that the row with
the higher value (1000000) in the Amount field is listed first. If the row order was reversed, Ariba Spend
Management would select the 1000 entry for all amounts greater than or equal to 1000, even when the amount is
greater than 1000000.

Setting Up SAP Ariba Supplier Lifecycle and Performance

142 CUSTOMER Setting up supplier form and questionnaire approvals
 Amount User Tooltip Required

1000000 molson Add M. Olson if over 1 TRUE

mil.

1000 aalcott Add A. Alcott if >= 1000 TRUE

and < 1000000

Approver lookup table using the is between operator

The following example uses the operator is between for the Amount field. The ranges for the amounts are
separated by a dash (-).

Amount User Tooltip Required

1000000-10000000 molson Add M. Olson if >= 1 TRUE

00 mil. and <1 bil.

1000-1000000 aalcott Add A. Alcott if >= 1000 TRUE

and < 1000000

Approver lookup table file with multiple fields

If an approver lookup table file contains multiple field values, the system uses the AND operator for the field
values. For example, the user creates the following approver lookup table file with the Amount and Region fields:

Amount Region User Tooltip Required

1000000 EMEA aalcott Add A. Alcott if EMEA & > TRUE

1 mil.

1000000 * molson Add M. Olson if not EMEA TRUE

and > 1 mil.

The operator for the Amount field is greater than or equal to and the operator for the Region field is child of. The
system adds the user aalcott to projects with the amount greater than 1000000 (USD) and in the EMEA region.
For projects in all other regions with the amount greater than 1000000 (USD), the system adds the user molson.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Setting up supplier form and questionnaire approvals CUSTOMER 143
Customizing SAP Ariba Supplier Lifecycle and
Performance notifications

About customizing SAP Ariba Supplier Lifecycle and Performance notification templates [page 144]

How to customize email templates [page 145]

How to add email template tokens [page 146]

How to add translated text to email notification templates [page 148]

How to delete customized email templates [page 148]

SAP Ariba Supplier Lifecycle and Performance notification reference [page 149]

About customizing SAP Ariba Supplier Lifecycle and

Performance notification templates
SAP Ariba Supplier Lifecycle and Performance uses email notification templates to create notifications for various
activities in SAP Ariba Supplier Lifecycle and Performance projects. You can customize these notifications.

SAP Ariba Supplier Lifecycle and Performance provides a specific set of notification templates that are tailored to
SAP Ariba Supplier Lifecycle and Performance workflows. SAP Ariba also provides a standard, generic set of
notifications that you can apply to SAP Ariba Supplier Lifecycle and Performance projects.

Note
SAP Ariba provides a generic set of notifications for different actions related to approval tasks, but they are not
used for SAP Ariba Supplier Lifecycle and Performance questionnaire approval tasks. Instead, SAP Ariba
Supplier Lifecycle and Performance questionnaire approval tasks use the specific approval task notification
templates for each SAP Ariba Supplier Lifecycle and Performance project type.

You must be a member of one of the following groups to customize email templates:

● Customer Administrator
● Project Email Templates Administrator
● Contract Administrator
● Project Administrator

You can customize email notifications by:

● Modifing the subject and body of the email notification messages.

● Formatting text in the body of the message. The email template editor includes a rich-text editor that enables
you to add formatting effects, including:
○ Font changes
○ Bold, italic, and underlined text

Setting Up SAP Ariba Supplier Lifecycle and Performance

144 CUSTOMER Customizing SAP Ariba Supplier Lifecycle and Performance notifications
 ○ Bullet and numbered lists
○ Background and font color changes
● Creating different versions of email templates according to the project type. For example, you can create one
version of the email template for overdue tasks for supplier registrations and another version for supplier
qualifications.
The system is preconfigured with template versions that are applicable to all project types, labeled All
Applicable Types. You cannot delete these templates. If there is no template version defined for a given
project type, the system uses the All Applicable Types version of the template for an event.
● Adding email template tokens to the email subject or text. Email template tokens are references or
placeholders for information that is provided by the system when the email generated from the template is
sent. The information can come from project field values, information about a task or phase, or generated by
the system for the email message itself, such as the recipient’s email address.
● Providing translated text for the email subject or text.

Related Information

How to customize email templates [page 145]

How to add email template tokens [page 146]
How to add translated text to email notification templates [page 148]

How to customize email templates

You customize email templates using the Project Manager Project Email Templates task in Ariba
Administrator.

Prerequisites

You must be a member of one of the following groups to edit email templates:

● Customer Administrator
● Project Email Templates Administrator
● Contract Administrator
● Project Administrator

Procedure

1. Click Manage Administration .

2. Click the expand arrow for Project Manager, then click Project Email Templates:

Setting Up SAP Ariba Supplier Lifecycle and Performance

Customizing SAP Ariba Supplier Lifecycle and Performance notifications CUSTOMER 145
3. Click the radio button for the template you want to edit. Click the Edit button.
4. If you are editing a notification in the All Applicable Types section in order to create a notification for a specific
project type (such as a sourcing project), select the type from the Project Type dropdown menu.

Tip
○ If you are editing a notification that is already associated with a specific project type, this option is not
available.
○ Selecting a specific project type makes it easier to add email template tokens that are specific to that
project type. If you create or modify a template for All Applicable Types, the email token chooser
displays only the subset of email template tokens that apply to all project types.
○ If you select a project type and a template already exists for that type, the system asks if you want to
open and load the existing template for that project type.
○ If you click Cancel, the text from the current template remains loaded in the editor but the system
changes the project type to the type you selected. This operation enables you to copy a template for
one project type (the project type of the template you originally opened) for use with another project
type (the project type you selected after opening the template).
○ If you click OK, the system loads the existing template for the selected project type and discards any
changes you made in the current template.

5. Make changes or additions to the text and add formatting to meet your needs.
6. (Optional) Add or remove email template tokens. To remove email template tokens, delete the text and the
square brackets.
7. (Optional) Add any translations.
8. Click Save to save the edited template.
9. Click Done to exit the email template editor.

Related Information

Adding Email Template Tokens [page 146]

Adding Translated Text [page 148]

How to add email template tokens

Email template tokens are placeholders for information provided by the system when the email generated from
the template is sent. Information can come from project field values, information about a task or phase, or
generated by the system for the email message itself, such as the recipient’s email address.

Prerequisites

You must be a member of one of the following groups to edit email templates:

Setting Up SAP Ariba Supplier Lifecycle and Performance

146 CUSTOMER Customizing SAP Ariba Supplier Lifecycle and Performance notifications
● Customer Administrator
● Project Email Templates Administrator
● Contract Administrator
● Project Administrator

Context

Email template tokens are delimited by square brackets ([ ]). For example, the text [[Link]] is an
email template token that the system replaces with the workspace or project title (name) when it sends an email
message generated from the email template.

Procedure

1. Open the appropriate email template for editing.

2. (Optional) To add the email token to a specific location in the email contents or subject line, add an empty set
of square brackets ([ ]) to the appropriate location.

When you add an email template token in the next step, the system inserts the email template token in the first
set of empty square brackets. If there are no empty square brackets, the system places the email template
token at the end of the Content or Subject field; you can cut and paste the token to another area after it is
inserted.
3. Perform one of the following actions:

○ To add an email template token to the subject line, to the right of the Subject field, click Add Email
Template Token.
○ To add an email template token to the body of the email, below the Content field, click Add Email
Template Token.

The system opens a Choose Content Field or Choose a Subject Field window with folders that contain the
email template tokens available for the specific message and area (subject or content).
4. Perform the following actions:

○ Click the expand arrows next to a folder name to display the email template tokens.
○ Click the cue tip next to the email template token to display more information.
○ Click Select to add the selected email template token.
5. Click OK.

Related Information

Customizing Email Templates [page 145]

Setting Up SAP Ariba Supplier Lifecycle and Performance

Customizing SAP Ariba Supplier Lifecycle and Performance notifications CUSTOMER 147
How to add translated text to email notification
templates
The translated text added to email notification templates is linked to locales and the system substitutes the
translated text when sending email notifications to users in the given locale.

Prerequisites

You must be a member of the Translator or Customer Administrator groups to add translated text to email
templates.

Procedure

1. Open the appropriate email template for editing.

2. Perform one of the following actions:To provide translated text for the message contents, click Translations to
the right of the Content box. To provide translated text for the subject line, click Translations to the right of
the Subject box.

○ To provide translations of the email subject, below the Subject field, click Translations.
○ To brovide translations for the email body content, below the Content field, click Translations.

The system opens a page that contains translation fields for each locale available in SAP Ariba solutions.
3. Enter your translated text in the field that corresponds to its language..
4. Click OK.

Related Information

Customizing Email Templates [page 145]

How to delete customized email templates

Context

You can delete customized email templates for a specific project type. You cannot delete default email templates
for specific project types, or customized email templates used for all applicable project types. If you delete an
email template for a specific project type, the system immediately reverts to the email template used for all
applicable project types for that event.

Setting Up SAP Ariba Supplier Lifecycle and Performance

148 CUSTOMER Customizing SAP Ariba Supplier Lifecycle and Performance notifications
Procedure

1. Choose the template you want to delete.

2. Click Delete to open the Delete Email Template Confirmation window.
3. Click OK.

SAP Ariba Supplier Lifecycle and Performance

notification reference
SAP Ariba Supplier Lifecycle and Performance provides a specific set of notification templates that are tailored to
SAP Ariba Supplier Lifecycle and Performance workflows.

Notifications related to supplier requests

SAP Ariba sends notifications for the following events related to supplier requests:

● Submitted: Your request to add <supplier name> as a supplier

Sent to the user who submitted the supplier request.
● Action needed: Approve request to add <supplier name> as a supplier
Send to the users in the supplier request approval flow once it is their turn to approve the supplier request.
● Approved: Your request to add <supplier name>
Sent to the user who submitted the supplier request once the request is finally approved.
● Denied: Your request to add <supplier name>
Sent to the user who submitted the supplier request if the request is finally denied, and includes any
comments the approver made to explain the denial.

Notifications related to supplier registrations

SAP Ariba sends notifications for the following events related to supplier registrations:

● Invitation: Register to become a supplier with <buyer name>

Sent to the person specified as the supplier's business contact in the supplier request or the supplier self-
registration.
● Fyi: <supplier name> has started the registration process with <buyer name>
Sent to the user who submitted the request for the supplier who is now in registration.
● Fyi: <supplier name> has submitted registration info with <buyer name>
Sent to the registration project's team members.
● Action needed: Approve supplier registration with <buyer name>
Sent to the users in the registration questionnaire approval flow once it is their turn to approve the supplier
registration.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Customizing SAP Ariba Supplier Lifecycle and Performance notifications CUSTOMER 149
● Approved: Supplier registration with <buyer name>
Sent to the supplier who submitted the registration questionnaire.
● Declined: Supplier registration with <buyer name>
Sent to the supplier who submitted the registration questionnaire if the registration is finally denied, and
includes contact information for the user who submitted the supplier request.
● Action needed: Provide additional registration information to <buyer name>
Sent to the supplier who submitted the registration questionnaire if an approver has denied the questionnaire
but allowed the supplier to resubmit answers, and includes any comments the approver made to explain the
denial.

Notifications related to supplier qualifications

SAP Ariba sends notifications for the following events related to supplier qualifications:

● Action needed: Fill out qualification questionnaire to become a qualified supplier with <buyer name>
Sent to the supplier's main business contact once a category or supplier manager has launched a new
qualification.
● Fyi: <supplier name> has submitted qualification info with <buyer name>
Sent to the user who submitted the request for the supplier who is now in qualification.
● Fyi: <supplier name> has started a qualification process with <buyer name>
Sent to the qualification project's team members.
● Action needed: Review qualification for <supplier name>
Sent to the users in the qualification questionnaire approval flow once it is their turn to approve the supplier
qualification.
● Approved: Supplier qualification request with <buyer name>
Sent to the supplier who submitted the qualification questionnaire.
● Declined: Supplier qualification with <buyer name>
Sent to the supplier who submitted the qualification questionnaire if the qualification is finally denied.
● Action needed: Provide additional qualification information to <buyer name>
Sent to the supplier who submitted the qualification questionnaire if an approver has denied the questionnaire
but allowed the supplier to resubmit answers, and includes any comments the approver made to explain the
denial.
● Action needed: Review disqualification for <supplier name>
Sent to the users in the disqualification approval flow once it is their turn to approve the supplier
disqualification.
● Approved: The disqualification request for <supplier name> in <commodity category>
Sent to the user who submitted the request to disqualify the supplier once the disqualification is finally
approved in cases where the disqualification is immediate and does not include an intermediary restriction.
● Approved: the disqualificaton request for <supplier name> in <commodity category>
Sent to the user who submitted the request to disqualify the supplier once the disqualification restriction is
finally approved.
● Fyi: The status for <supplier name> in <commodity category> has changed to Disqualified
Sent to the user who submitted the request to disqualify the supplier in cases where the disqualification date
on the approved disqualification restriction has been reached and the supplier's status changes from
Restricted to Disqualified.

Setting Up SAP Ariba Supplier Lifecycle and Performance

150 CUSTOMER Customizing SAP Ariba Supplier Lifecycle and Performance notifications
Notifications related to preferred supplier status changes

SAP Ariba sends notifications for the following events related to preferred supplier status changes:

● Action needed: Approve new category status for <supplier name> in <category>
Sent to the users in the preferred supplier category status change request approval flow once it is their turn to
approve the status change.
● Approved: The status change made for <supplier name> in <category>
Sent to the internal user who requested the category status change.
● Denied: The status change made for <supplier name> in <category>
Sent to the internal user who requested the category status change, and includes the name of the approver
who denied the request.
● Fyi: The status of <supplier name> for <category> has changed to <status>
Sent to the category or supplier managers who manage the supplier.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Customizing SAP Ariba Supplier Lifecycle and Performance notifications CUSTOMER 151
Issuing mass registration invitations to
suppliers

Once you have imported supplier data and set up your supplier management projects, mass registration
invitations invite all specified suppliers to register with your company automatically..

How to issue a mass registration invitation to suppliers [page 152]

[Link] [page 153]

How to issue a mass registration invitation to

suppliers
Supplier mass registration invitations allow you to automatically send registration invitations to multiple suppliers
at once so that you can quickly get them registered and on board.

Prerequisites

You must be a member of the SM Ops Admin group to issue mass registration invitations.

You must have imported primary supplier manager data for the suppliers you want to invite. Suppliers that do not
have a primary manager are not included. You must also have imported supplier contact data for the suppliers you
want to invite.

You must have set up and published the supplier registration project template in your site.

To include a specific list of suppliers, you must add their ERP vendor IDs to a [Link] [page 153] file.

Context

When you import supplier data (either existing SAP Ariba suppliers or suppliers from outsite SAP Ariba), they are
created in the database with the Not Invited status.

For suppliers created individually through approved supplier requests, the category or supplier manager assigned
to the supplier will manually invite the supplier to register. However, when you are getting started with your SAP
Ariba supplier management solution, or whenever you create a large number of suppliers using data import,
manually initiating registration invitations is not practical. Moreover, if the supplier data does not include
categories or regions, the registration projects cannot assign project owners based on buyer category
assignments or team member rules. Supplier mass registration automatically sends invitations to all of the
suppliers you register and assigns them to their primary supplier contacts for initial processing.

Setting Up SAP Ariba Supplier Lifecycle and Performance

152 CUSTOMER Issuing mass registration invitations to suppliers
With mass invitation registrations, there is no option to select among registration questionnaires; all registration
questionnaire segments that apply to the supplier are included.

Procedure

1. On the dashboard, click Manage SM Admin .

2. Click Mass Invite.
3. Perform one of the following actions:

○ To invite every supplier in the database that has the status Not Invited and a primary supplier manager,
choose Mass Invite All.
○ To invite a specific list of suppliers, click Choose file, navigate to [Link] [page 153], and click
Upload.
4. Click Send Invite.

[Link]
[Link] defines the list of suppliers you want to automatically invite to register all at once. Only those
suppliers who have a primary supplier manager defined by importing [Link] are
included in the automatic invitation, so you must import that file before importing [Link].

Field Definition Required

erpVendorId For existing Ariba suppliers, if the Yes

SupplierOrganizationOrganiz
ationIdPart_Export.csv file con­
tains a Domain and Value entry for the
supplier, use the Value in this field. If
not, use the [Link].

For suppliers imported from outside

Ariba, use the erpVendorId specified
in [Link].

Related Information

[Link] [page 78]

Setting Up SAP Ariba Supplier Lifecycle and Performance

Issuing mass registration invitations to suppliers CUSTOMER 153
Site configuration options for setting up SAP
Ariba Supplier Lifecycle and Performance

Site configuration options for supplier contacts

Some of the functionality for supplier contacts is controlled by configuration options, which Ariba sets for you
[Link]
This parameter specifies whether or not new supplier users in supplier Ariba Network
accounts are automatically synchronized with existing suppliers in your site. If this
parameter is set to Yes, the new users are added to your site as new supplier contacts. The
default setting is Yes.

A separate parameter,
[Link], specifies whether
or not the supplier contacts are automatically approved when they are synchronized, or
whether they require manual approval.
[Link]
This parameter specifies whether or not new supplier contacts added to your site through
synchronization with the suppliers' Ariba Network account are automatically approved. If
this parameter is set to Yes, the new supplier contacts are automatically approved. If it is
set to No, the new supplier contacts must be approved or denied manually. The default
setting is No.

This parameter is only applicable if

[Link] is set to Yes.

Setting Up SAP Ariba Supplier Lifecycle and Performance

Site configuration options for setting up SAP Ariba Supplier Lifecycle and
154 CUSTOMER Performance
Important Disclaimers and Legal Information

Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.

Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see:
[Link]

Setting Up SAP Ariba Supplier Lifecycle and Performance

Important Disclaimers and Legal Information CUSTOMER 155
[Link]

Copyright © 2016 Ariba, Inc. All rights reserved.

This documentation, as well as the Ariba solutions, software and/or
services described in it, contain proprietary information. They are
provided under a license or other agreement containing restrictions
on use and disclosure and are also protected by copyright, patent
and/or other intellectual property laws. Except as permitted by such
agreement, no part of the document may be reproduced or
transmitted in any form by any means, electronic, mechanical or
otherwise, without the prior written permission of Ariba, Inc.
Ariba, Inc. assumes no responsibility or liability for any errors or
inaccuracies that may appear in the documentation. The
information contained in the documentation is subject to change
without notice.
Ariba and Ariba products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of
Ariba, Inc. in the United States and other countries. Please see
[Link] for additional trademark
information and notices.
Ariba Sourcing solutions (On Demand and software) are protected
by one or more of the following patents, including without limitation:
U.S. Patent Nos. 6,199,050; 6,216,114; 6,223,167; 6,230,146;
6,230,147; 6,285,989; 6,408,283; 6,499,018; 6,564,192; 6,871,191;
6,952,682; 7,010,511; 7,072,061; 7,130,815; 7,146,331;
7,152,043;7,225,152; 7,277,878; 7,249,085; 7,283,979; 7,283,980;
7,296,001; 7,346,574; 7,383,206; 7,395,238; 7,401,035; 7,407,035;
7,444,299; 7,483,852; 7,499,876; 7,536,362; 7,558,746; 7,558,752;
7,571,137; 7,599,878; 7,634,439; 7,657,461; 7,693,747; 8,364,577;
and 8,392,317. Patents pending.
Other Ariba product solutions are protected by one or more of the
following patents:
U.S. Patent Nos. 6,199,050, 6,216,114, 6,223,167, 6,230,146,
6,230,147, 6,285,989, 6,408,283, 6,499,018, 6,564,192, 6,584,451,
6,606,603, 6,714,939, 6,871,191, 6,952,682, 7,010,511, 7,047,318,
7,072,061, 7,084,998; 7,117,165; 7,225,145; 7,324,936; 7,536,362;
8,364,577; and 8,392,317. Patents pending.
Certain Ariba products may include third party software or other
intellectual property licensed from a third party. For information
regarding software or other intellectual property licensed from a
third party, go to [Link]