SlpSetup English PDF

PUBLIC
2020-08
Supplier management setup and administration

guide
SAP Ariba Supplier Lifecycle and Performance
© 2020 SAP SE or an SAP affiliate company. All rights reserved.
SAP Ariba Supplier Information and Performance Management (new

architecture)
THE BEST RUN

Content
Supplier management setup and administration guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Topics about getting started with SAP Ariba Supplier Management solutions. . . . . . . . . . . . . . . . 10
What is supplier management in SAP Ariba Supplier Management solutions?. . . . . . . . . . . . . . . . . . . . .10
About internal supplier requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
About external supplier requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
About new supplier registrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
About supplier registration updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
About supplier qualification and requalification using supplier qualification projects. . . . . . . . . . . . . .18
About setting preferred category statuses for suppliers using preferred supplier management
projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Supplier disqualifications using supplier disqualification projects. . . . . . . . . . . . . . . . . . . . . . . . . . . 20
About supplier performance evaluations using SPM projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Key assumptions for setting up SAP Ariba Supplier Management solutions . . . . . . . . . . . . . . . . . . . . . . 22
Supplier management setup checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
APIs for SAP Ariba Supplier Management solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Integration options for SAP Ariba Supplier Management solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Transitioning from supplier organizations to supplier requests and registrations. . . . . . . . . . . . . . . . . . . 27
Where to find more information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Topics about setting up supplier management users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Supplier management user groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
How to add users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
How to edit users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
User groups in supplier management buyer category assignments (the user matrix). . . . . . . . . . . . . . . 36
Topics about importing supplier management data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Topics about importing site master data for supplier management. . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
About importing site master data for supplier management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Defining preferred supplier levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Defining modular supplier management questionnaire types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Defining supplier certificate types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Defining questionnaire scoring band categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Defining questionnaire scoring bands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Defining country-specific tax ID fields in Tax questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Defining country-specific bank ID prefixes for Bank Account questions. . . . . . . . . . . . . . . . . . . . . . . 52
Topics about defining country-specific validations for supplier bank account information. . . . . . . . . . 54
Defining country-specific ERP region code mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Supplier management setup and administration guide

2 PUBLIC Content
Defining country-specific postal code validation for supplier addresses. . . . . . . . . . . . . . . . . . . . . . . 61
Defining mappings between guided buying ship-to addresses and preferred and qualified supplier
regions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
How to import your data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
How to import your translation data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Language values for defining translations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Topics about importing supplier-related data in SM Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . 67
About importing supplier-related data for supplier management. . . . . . . . . . . . . . . . . . . . . . . . . . . 68
How to obtain existing SAP Ariba supplier data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
How to import supplier data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Supplier data file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Supplier contact data file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Supplier qualification data file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Preferred supplier data file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
Supplier factory data file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Purchasing organization data file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Custom display name data file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Primary supplier manager data file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
User matrix (buyer category assignment) data file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Internal supplier registration data file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
How to import custom SAP region codes for supplier extended addresses. . . . . . . . . . . . . . . . . . . . . . 104
Importing business partner IDs for ERP suppliers added through SAP Ariba Procurement solutions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Topics about setting up optional features for supplier and supplier contact names. . . . . . . . . . . 107
Showing supplier names longer than 35 characters in SAP Ariba solutions. . . . . . . . . . . . . . . . . . . . . . 107
How to set up your site to show contact names with family name first. . . . . . . . . . . . . . . . . . . . . . . . . 109
Topics about supplier management project template basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Understanding supplier management project templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Commodity, region, department, and user combinations in supplier management projects. . . . . . . . 112
Documents in supplier management projects: forms and questionnaires. . . . . . . . . . . . . . . . . . . . . 113
Tasks in supplier management projects: To Do's and form and questionnaire approvals. . . . . . . . . . . 114
Team in supplier management projects: automatic assignment by commodity, region, and
department. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Using SPM project templates in SAP Ariba Supplier Management solutions that use the unified vendor
model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Exporting and importing supplier management project templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Topics about editing and publishing project templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
How to edit a project template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
How to set validation rules for publishing new template versions. . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Using the project template Overview tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
How to publish supplier management project templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121

Content PUBLIC 3
How to revert a project template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Topics about upgrading supplier management projects to the latest template version. . . . . . . . . . . . . . 123
About supplier management project template upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Which supplier management projects are eligible for template upgrade?. . . . . . . . . . . . . . . . . . . . . 125
How template upgrade affects supplier management projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
How to upgrade supplier management projects to the latest template version. . . . . . . . . . . . . . . . . 132
Topics about setting up supplier requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

About the internal supplier request project template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Restrictions, requirements, and helpful hints for setting up the internal supplier request project
template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
About the external supplier request project template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Restrictions, requirements, and helpful hints for setting up the external supplier request project
template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Setting up external supplier request by business unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Default supplier request duplicate checks and setting up custom duplicate checks. . . . . . . . . . . . . . . . 144
How duplicate checks work in submitted supplier requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Topics about setting up supplier registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

About the supplier registration project template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148
Restrictions, requirements, and helpful hints for setting up the supplier registration project template
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Configuration considerations for supporting both internal and external registrations . . . . . . . . . . . . . . 155
How to set up reminders for suppliers to complete a new registration. . . . . . . . . . . . . . . . . . . . . . . . . .156
How to set up periodic reminders for suppliers to update a registration questionnaire. . . . . . . . . . . . . . 158
How to specify a custom sender name for registration invitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
How to set up different workflows for new registrations and registration updates. . . . . . . . . . . . . . . . . .162
Using registration and registration update status in visibility and editability conditions. . . . . . . . . . . . . .165
How to prevent suppliers from updating some registration questionnaire answers using editability
conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Using conditions to set up alternate workflows for manual and mass invited registrations. . . . . . . . . . . 167
How to streamline the registration questionnaire for legacy suppliers using editability conditions. . . . . . 168
Enabling users to set and maintain associated sets of ERP profile data by mapping question values to
other questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
Setting up supplier blocking and unblocking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
Enabling users to inactivate suppliers by flagging them for deletion in questionnaire answers. . . . . . . . . 174
Topics about setting up supplier qualifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

About the supplier qualification project template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Restrictions, requirements, and helpful hints for setting up the supplier qualification project template
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Setting up the prequalification questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
How to set up the prequalification questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
How to remove an existing internal qualification survey. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

4 PUBLIC Content
Topics about setting up supplier disqualifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
About the supplier disqualification project template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Restrictions, requirements, and helpful hints for setting up the supplier disqualification project
template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Topics about setting up preferred supplier management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187

About the preferred supplier management project template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Restrictions, requirements, and helpful hints for setting up the preferred supplier management
template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Topics about setting up modular supplier management questionnaires. . . . . . . . . . . . . . . . . . . . 190

About modular supplier management questionnaire project templates. . . . . . . . . . . . . . . . . . . . . . . . 190
Restrictions, requirements, and helpful hints for modular supplier management questionnaire project
templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
How to create a modular supplier management questionnaire project template. . . . . . . . . . . . . . . . . . 194
How to set up a modular supplier management questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
How to set up separate workflows for new and updated modular supplier management questionnaires
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Setting up supplier certificate management using modular questionnaires. . . . . . . . . . . . . . . . . . . . . . 201
Adding scoring and score bands to modular supplier management questionnaires. . . . . . . . . . . . . . . . 203
About scoring points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
About pre-grading supplier questionnaires. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Structural considerations for scoring supplier questionnaire content. . . . . . . . . . . . . . . . . . . . . . . . 211
How to set up scoring bands for a modular supplier management questionnaire. . . . . . . . . . . . . . . 213
How to set up scoring bands for individual questionnaire sections. . . . . . . . . . . . . . . . . . . . . . . . . .215
How to add scoring to a modular supplier management questionnaire. . . . . . . . . . . . . . . . . . . . . . .217
Topics about creating supplier forms and questionnaires. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220

About creating supplier forms and questionnaires. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Supplier form or questionnaire closing, reopening, and due dates. . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
How to create a supplier form or questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
How to set up a targeted supplier qualification questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
How to create a targeted supplier qualification questionnaire segment. . . . . . . . . . . . . . . . . . . . . . . . 228
How to create a supplier-related internal questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Topics about adding content to a supplier form or questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
How to add a section to a supplier form or questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
How to add a repeatable section to a supplier form or questionnaire. . . . . . . . . . . . . . . . . . . . . . . . 232
Topics about adding questions to supplier forms and questionnaires. . . . . . . . . . . . . . . . . . . . . . . 235
How to add a requirement to a supplier form or questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
How to add translations for some form and questionnaire content fields. . . . . . . . . . . . . . . . . . . . . 295
How to add an attachment to a supplier form or questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Masking sensitive data in supplier forms and questionnaires. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Topics about using visibility conditions to show or hide questionnaire content based on answers. . . . . . 299

Content PUBLIC 5
Using visibility conditions to show or hide content based on answers. . . . . . . . . . . . . . . . . . . . . . . 299
How to create a basic visibility condition in a form or questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . 301
How to create an advanced visibility condition in a form or questionnaire. . . . . . . . . . . . . . . . . . . . 302
Expressions for advanced visibility conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Using editability conditions to control the editability of answers in a form or questionnaire. . . . . . . . . . 304
Topics with supplier management questionnaire content examples. . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Example: how to create a dropdown menu with predefined values on a supplier form or
questionnaire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Example: how to automatically reject answers that don't fall within a limited range on supplier
forms and questionnaires. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306
Example: how to ask for a supplier certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Example: how to ask for a supplier's address and map the answer to the supplier database. . . . . . . 308
Example: how to create a question that is only to visible suppliers with green certifications. . . . . . . .309
Example: how to ask about preferred supplier levels using master data values. . . . . . . . . . . . . . . . . 310
Topics about adding project groups and team members to project templates. . . . . . . . . . . . . . . . 311
Adding project groups and team members to project templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Understanding buyer category assignments (the user matrix). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
How to use buyer category assignments to add team members to project groups. . . . . . . . . . . . . . . . . 314
Topics about setting up supplier form and questionnaire approvals. . . . . . . . . . . . . . . . . . . . . . . 316

Topics about creating approval flows in the approval rules editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
About approval rules in project templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
How to create or edit approval rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
About the approval rules editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
How to create a simple approval rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
How to edit approval flows with the approval process diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Using approval rule conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
How to add approvers in the approval rule editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328
Using commodity, region, and department assignments for form and questionnaire approvals. . . . . . . .329
Example: how to create a conditional approval flow using commodity and region assignments. . . . . 330
Creating conditional approval flows based on form and questionnaire answers. . . . . . . . . . . . . . . . . . . 333
Example: How to add the legal department to an approval flow when a supplier won't agree to your
code of conduct. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334
Setting up external approval of SAP Ariba project approval tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Topics about setting default values for vendor database fields. . . . . . . . . . . . . . . . . . . . . . . . . . .339
Setting default values for vendor database fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Default_properties.csv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Defining lookup key field-based default values for company code, purchasing organization, and other
array fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342
Defining default values based on condition fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Topics about customizing supplier management notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . 345

6 PUBLIC Content
About customizing supplier management notification templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . .345
Topics about customizing project-level supplier management notifications. . . . . . . . . . . . . . . . . . . . . 346
How to customize project-level email templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
How to delete customized project-level email templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Notifications related to supplier requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Notifications related to supplier registration projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Notifications related to supplier qualification projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Notifications related to preferred supplier status changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Notifications related to supplier disqualification projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Notifications related to modular supplier management questionnaires. . . . . . . . . . . . . . . . . . . . . . 354
Notifications related to certificate questions in modular supplier management questionnaires. . . . . 355
Notifications related to supplier management project template upgrades. . . . . . . . . . . . . . . . . . . . 355
Supplier management-specific notifications related to tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Other supplier management notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .357
How to customize the questionnaire invitations sent to suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . .357
How to add email template tokens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
How to add translated text to email notification templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Topics about issuing mass registration invitations to suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . 362

Issuing mass registration invitations to suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
How to issue a mass registration invitation to suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
How to monitor the progress of mass registration invitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Mass registration invitation data import file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Topics about performing administrative tasks for supplier management. . . . . . . . . . . . . . . . . . . 367

How to download the vendor onboarding report to track supplier registration and qualification
progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Topics about inactivating and reactivating suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Inactivating and reactivating suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
How to view and manually reactivate inactive suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
How to cancel a qualification project that is in progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
How to manage access to the advanced view of supplier management projects. . . . . . . . . . . . . . . . . . 372
Topics about managing ERP integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

How to manage schema validation errors in outbound integration messages. . . . . . . . . . . . . . . . . . . . 374
How to enable email notifications with daily summaries of integration failures. . . . . . . . . . . . . . . . . . . 376
When updates from the ERP system are pushed to external supplier management questionnaires
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Topics about setting up Dun & Bradstreet integration with SAP Ariba Supplier Lifecycle and
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Integrating SAP Ariba Supplier Lifecycle and Performance with Dun & Bradstreet. . . . . . . . . . . . . . . . . 383
Workflow for Dun & Bradstreet integration with SAP Ariba Supplier Lifecycle and Performance. . . . . . . 384

Content PUBLIC 7
Prerequisites for integrating Dun & Bradstreet with SAP Ariba Supplier Lifecycle and Performance
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
How to configure Dun & Bradstreet integration in your site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Setting up the internal supplier request for Dun & Bradstreeet integration. . . . . . . . . . . . . . . . . . . . . . 388
Setting up supplier registration questionnaires for Dun & Bradstreet integration. . . . . . . . . . . . . . . . . .390
Field mappings for Dun & Bradstreet questions in the internal supplier request and registration
questionnaires. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Deleting Dun & Bradstreet data from your site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Field reference for Dun & Bradstreet integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Quick reference to optional supplier management features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Supplier management features and functions that require the new supplier 360° profile. . . . . . . . . . . . 407
Topics about default master data for supplier management. . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

Default bank control keys in Bank Account questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Default syntax for IBAN numbers in Bank Account questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Default syntax validation for account holder names, account numbers, and bank keys in Bank
Account questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Default country-specific ERP region code mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .423
Default syntax validation for postal codes in supplier addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Topics about site configuration parameters for supplier management. . . . . . . . . . . . . . . . . . . . . 516

Site configuration parameters for supplier management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Self-service site configuration parameters for supplier management. . . . . . . . . . . . . . . . . . . . . . . . . . 517
Automatically start supplier registrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Enable configurable default sender for supplier invitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Define the length of supplier bank IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Require only attachment and expiration date for supplier certificates. . . . . . . . . . . . . . . . . . . . . 519
Set minimum registration status for event participation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Use custom logo and footer for emails sent to suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521

8 PUBLIC Content
Supplier management setup and administration
guide
This guide is for SAP Ariba buyer template creators and administrators seeking information about how to maintain
supplier data and set up processes for managing supplier lifecycles.
Buyers use supplier lifecycle processes to add new suppliers, gather and maintain supplier profile information, and
decide which suppliers are qualified or preferred in specific domains.
This guide applies to:
● SAP Ariba Supplier Lifecycle and Performance

● SAP Ariba Supplier Information and Performance Management (new architecture)
Related guides
Quick reference to SAP Ariba Supplier Management solutions features
Managing suppliers and supplier lifecycles
Supplier Data API with Pagination
Common data import and administration guide for SAP Ariba Strategic Sourcing and Supplier Management
solutions
Strategic sourcing and supplier management group descriptions
Migrating suppliers to the unified vendor model
Configuring supplier performance management reviews
Running supplier performance management reviews
Managing project email notifications
Project template guide
Managing projects, teams, documents, and tasks

Supplier management setup and administration guide PUBLIC 9
Topics about getting started with SAP Ariba
Supplier Management solutions
What is supplier management in SAP Ariba Supplier Management solutions? [page 10]
Key assumptions for setting up SAP Ariba Supplier Management solutions [page 22]
Supplier management setup checklist [page 24]
APIs for SAP Ariba Supplier Management solutions [page 26]
Integration options for SAP Ariba Supplier Management solutions [page 26]
Transitioning from supplier organizations to supplier requests and registrations [page 27]
Where to find more information [page 29]
What is supplier management in SAP Ariba Supplier

Management solutions?
SAP Ariba Supplier Management solutions provide a set of linked processes for managing suppliers. Category and
supplier managers use 360° views of each supplier to manage these processes and monitor suppliers in one place.
The following diagram illustrates the complete set of processes in an SAP Ariba supplier lifecycle:
SAP Ariba Supplier Management solutions include SAP Ariba Supplier Lifecycle and Performance and SAP Ariba
Supplier Information and Performance Management (new architecture). Both solutions offer:
● Defined, template-based processes for managing suppliers that scales easily to bring large numbers of
suppliers under management. These processes include:
○ Internal and external requests for adding new suppliers to your vendor database.
○ Supplier registrations for collecting and managing detailed profile information.
○ (Optional) Supplier performance management (SPM) projects for evaluating the performance of the
suppliers with which you do business.
● A centralized supplier database with a complete, unified vendor model, and native integration to SAP ERP and
SAP S/4HANA.
● A complete 360° supplier view for each supplier that presents supplier information across all SAP Ariba
solutions available in a site. The supplier 360° profile also provides guided navigation for actions that users are
assigned to for the supplier.

10 PUBLIC Topics about getting started with SAP Ariba Supplier Management solutions
● Supplier self-service through Ariba Network
SAP Ariba Supplier Lifecycle and Performance also includes:
● "Matrix"-based supplier qualification, preferred status, and disqualification lifecycle processes based on
combinations of commodity categories, regions, and (optionally) departments.
● Built-in alignment with SAP Ariba Buying solutions and SAP Ariba Sourcing to leverage supplier qualifications
and preferred status in procurement and sourcing activities.
Related Information
About internal supplier requests [page 11]

About external supplier requests [page 12]
About new supplier registrations [page 13]
About supplier qualification and requalification using supplier qualification projects [page 18]
About setting preferred category statuses for suppliers using preferred supplier management projects [page 19]
Supplier disqualifications using supplier disqualification projects [page 20]
About supplier performance evaluations using SPM projects [page 22]
Supplier management setup checklist [page 24]
About internal supplier requests

Internal supplier request projects allow internal users to request to work with new suppliers. When a supplier
request is approved, the supplier is created in your site.
Users in your company who want to work with new suppliers, such as procurement agents, functional buyers, and
people running sourcing events, request a new supplier by filling out and submitting an internal supplier request
form. Note that there is a separate project for suppliers to create an external supplier request [page 12].
The internal supplier request template determines:
● What information users need to provide when submitting the request.

● Whether the request is automatically approved on submission or must be manually approved.
● If the request requires manual approval, which category or supplier managers approve the request, and
whether other stakeholders at your company must also approve the request.
Users create internal supplier requests from the Create menu on the dashboard and monitor their progress in the
My Activities area of the Supplier Management dashboard. When a user submits an internal supplier request, it is
checked against the existing suppliers in the database and the user is presented with any potential matches; they
then have the option of canceling the request (if they believe it is a duplicate) or continuing to submit it. If your site
is integrated with Dun & Bradstreet (D&B), the supplier request workflow also includes a step that looks up the
supplier in the Dun & Bradstreet database and, if the supplier isn't found, might include an exception process for
requesting a non-D&B supplier.
Notifications let the approver know that the request requires approval; they can also see outstanding requests
using Manage My Tasks on the dashboard. Notifications also let the requesting user know when the request
has been approved or denied, and show the final approver so that requesting user can have further discussions

Topics about getting started with SAP Ariba Supplier Management solutions PUBLIC 11
about denied requests. Approvers also see a list of potential duplicate suppliers so that they can deny duplicate
requests and approve only requests for genuinely new suppliers.
When a supplier request is approved, either automatically or manually, the supplier is created in your site's supplier
database. The information in the approved supplier request displays in the Origin of the Supplier area of the
Overview tab in the new supplier's 360° profile. If your site is integrated with Dun & Bradstreet, the new supplier
profile includes data from D&B.
Depending on your site's configuration, the supplier might be automatically invited to register at this point, or a
category or supplier manager might need to manually issue a registration invitation. If your site is integrated with
SAP ERP, SAP S/4HANA, SAP S/4HANA Cloud, or SAP MDG-S, your site's integration settings determine whether
the new supplier is automatically or manually synchronized with integrated system's vendor master list either at
this point or during supplier registration.
Related Information

About external supplier requests

External supplier request projects allow suppliers who want to do business with your organization to introduce
themselves. When an external request is approved, the supplier is created in your site.
External supplier request projects are not available by default and are only available in sites where the feature is
enabled. As part of external supplier request enablement, SAP Ariba Support provides your organization with an
external supplier request URL that is specific to your site. Your organization might provide this URL to potential new
suppliers through specific outreach programs, by publishing it on a corporate website, or through other means.
Suppliers can introduce themselves to your organization by clicking the URL and filling out and submitting the
external supplier request form. Note that there is a separate type of request project for internal users at your
company to request a new supplier [page 11]. External supplier requests are sometimes called self-registration, but
the form submitted is a request, the first step in working with a supplier. Supplier registration [page 13], the next
step, is a separate type of project.
The external supplier request project template determines:
● What information suppliers need to provide when submitting the request.

● Which category or supplier managers approve the request and whether other stakeholders at your company
must also approve the request.
Notifications let the approver know that the external supplier request requires approval; they can also see
outstanding external requests using Manage My Tasks on the dashboard. Approvers see a list of existing
suppliers in the database that match information in the external request so that they can deny duplicate requests
and approve only requests for genuinely new suppliers.

When an external supplier request is approved, the supplier is created in your site's supplier database. The
information in the approved external supplier request displays in the Origin of the Supplier area of the Overview
tab in the new supplier's 360° profile.
Depending on your site's configuration, the supplier might be automatically invited to register at this point, or a
category or supplier manager might need to manually issue a registration invitation. If your site is integrated with
SAP ERP, SAP S/4HANA, SAP S/4HANA Cloud, or SAP MDG-S, your site's integration settings determine whether
the new supplier is automatically or manually synchronized with the integrated system's vendor master list either
at this point or during supplier registration.
Related Information

About new supplier registrations
The new supplier registration process uses a registration project with questionnaires to gather detailed profile
information about a supplier.
After a new supplier is created, a registration manager starts a supplier registration by sending one or more
external registration questionnaires to recipients. Registration projects can also include internal questionnaires,
and starting the registration makes them available for editing. Approvers review the submitted questionnaires and
approve or deny them. The registration project then supports ongoing updates to both external and internal
questionnaires.
There are two types of supplier registration:
Registration type Description
External Invites a supplier contact to create an account or log into an

existing account on Ariba Network to fill out and submit exter
nal registration questionnaires. Suppliers participate in exter
nal registrations, and you collect registration information di
rectly from them.
After a supplier completes an external registration, you can es

tablish a fulfillment relationship with them.

Registration type Description
Internal Invites people in your organization to fill out and submit exter
nal registration questionnaires on behalf of the supplier. Sup
pliers do not participate in internal registrations, and you col
lect registration information about them from other people in
your organization, who might have collected it from the sup
plier through other means. A registration manager can later in
vite the supplier to participate in an internal registration, con
verting it to an external registration.
After a supplier completes an internal registration, you cannot

establish a fulfillment relationship with them.
Both registration types use the same registration project and have the same registration statuses.
Depending on your site's configuration and the particular supplier, registrations might start one the following ways:
Registration method Registration type
Automatically whenever a supplier request is approved. External
Manually by a registration manager. External or internal
Through a mass invitation wave, which a customer administra External
tor can create to onboard a specific set of suppliers at one

time.
(In sites that include SAP Ariba Sourcing) Automatically when External
ever an uninvited supplier is invited to a sourcing event that re

quires that the supplier have registration status of at least
Invited, if not higher, to participate in the event.
(In sites that include SAP Ariba Sourcing) Automatically when External
a previously uninvited supplier attempts to participate in a

sourcing event if your site requires a minimum status of
Registered to participate in sourcing events.
The registration process typically solicits detailed profile information about the supplier; for example, what
commodities they supply, the regions in which they operate, what standards they adhere to or agree with, bank and
tax details, and so forth. Depending on the way registration is set up in your site, it can include one or more external
registration questionnaires to gather this information.
Supplier registration projects can also include internal questionnaires that allow internal stakeholders to answer
questions about the supplier based on your organization's internal processes and to add internally-important
information such as company codes, purchasing organizations, payment terms, and so on to the supplier's profile.
The supplier registration project template determines:
● The number of external registration questionnaires and the number of internal questionnaires (if any), and
their content.
● Registration approvers, and whether or not there are different approval flows and other tasks for new
registrations versus questionnaire updates.

● Whether other tasks are part of the registration workflow.
● Whether or not denial of an internal questionnaire affects the supplier's registration status.
● How long external questionnaires remain open so that suppliers can submit their answers.
Users with the appropriate permissions start the registration, send one or more external questionnaires to
recipients, fill out any internal questionnaires, review the questionnaire responses, request more information,
complete To Do tasks, approve or deny the registration, and monitor its progress and status in the Registration
area of the supplier's 360° profile.
In external registrations, the supplier submits external registration questionnaires in their Ariba Network profile. To
do so, they must register with Ariba Network if they have not already. The supplier's profile is automatically shared
between Ariba Network and SAP Ariba Supplier Management solutions. Once registration is complete, the supplier
is public, meaning that they have a linked Ariba Network account in your site.
In internal registrations, internal recipients in your organization submit external registration questionnaires in your
site and the supplier does not participate at all. Internal registrations do not establish communications with the
supplier through Ariba Network. Unless you have interacted with the supplier through Ariba Network for another
activity, such as a sourcing event or an external modular questionnaire, they remain private, meaning that they do
not have a linked Ariba Network account in your site.
Notifications let questionnaire recipients know that they have been invited to register and provide a link to the
questionnaire; let the requester for the supplier know that registration has started; let approvers know that they
need to approve a new or updated supplier registration; let internal stakeholders know if they need to complete
other tasks; and (in external registrations) let the supplier know that the registration has been approved, denied, or
requires more information. If a registration invitation includes multiple questionnaires, questionnaire recipients
receives a separate notification for each questionnaire.
As your organization's registration process evolves over time, an administrator in your organization can upgrade
existing registration projects to the latest version of the template. An upgrade can include changes to internal or
external questionnaires, tasks, and approval flows. The administrator can opt to sent notifications about the
upgrade to supplier contacts so that they can update affected questionnaires. Internal users do not receive
upgrade notifications.
If your site is integrated with SAP ERP, SAP S/4HANA, SAP S/4HANA Cloud, or SAP MDG, your site's integration
settings determine whether a new supplier is automatically or manually synchronized with your ERP vendor master
list. Options include after the request has been approved, when the supplier registration is in progress, or after the
new registration has been approved. If the synchronization occurs while the registration is in progress, by default,
answers in internal registration questionnaires are synchronized to the integrated system immediately when the
internal questionnaires are submitted, even for questionnaires with approval flows. An optional feature requires
approval of internal registration questionnaires before they are synchronized with the integrated. External
registration questionnaires must always be approved before synchronization to the integrated system, even in
internal registrations.
For suppliers with external registrations, additional settings allow users with the appropriate permissions to
establish a fulfillment relationship with the supplier as they register for any event, at the same time the sourcing
relationship is established.
In solutions that include SAP Ariba Sourcing, event templates can specify that suppliers must be registered in order
to either participate in or be awarded events. There is also a configuration option for requiring a minimum
registration status for participation in sourcing events.

The following diagram shows the workflow for a new external registration where integration is set to synchronize
the supplier automatically with the ERP vendor master after registration is approved:
Related Information

About supplier registration updates [page 16]
About supplier registration updates

After a supplier is registered, external questionnaire recipients and people in your organization can update
questionnaires to profile information for the supplier current.
Supplier registration projects can be set up to supports different approval flows for new registrations and for
updates to individual questionnaires.
When a new registration starts, external registration questionnaires are open for the amount of time defined in the
template questionnaire's timing rules. Once the recipient submits the questionnaire the first time, it closes

automatically. After all of the tasks in a new registration are completed and the supplier has Registered status,
previously-closed external questionnaires automatically reopen for an amount of time defined by your site's
configuration and configurations in individual questionnaires. The default amount of time a questionnaire remains
open is 365 days from the approval. The recipient assigned to the external questionnaires in a registration can
navigate to them can submit updates at any time when they are not in approval. External questionnaires can be set
up to generate periodic reminders asking suppliers for updates.
Internal registration questionnaires are also always open for update when they are not in approval.
In a new registration, once the recipient invited to the registration opens at least one questionnaire, only they can
access the external questionnaires in the registration. In internal registrations, the registration project owner can
also access external questionnaires. After the new registration is approved, you can reassign external
questionnaires to a different recipient at any time when no external questionnaire updates are in approval. Only the
assigned recipient or, in internal registrations, the registration project owner, can update the external
questionnaires.
If a registration starts as an internal registration, meaning that people in your organization submit questionnaires
on behalf of the supplier, internal recipients can continue to update those questionnaires. A registration manager
can invite the supplier to an internal registration, transferring ownership of external questionnaires to a supplier
contact. When a supplier contact submits external questionnaires from a registration that was previously internal
for the first time, that initial submission is also treated as an updated.
As your organization's registration process evolves over time, an administrator in your organization can upgrade
existing registration projects to the latest version of the template. An upgrade can include changes to internal or
external questionnaires, tasks, and approval flows. The administrator can opt to sent notifications about the
upgrade to supplier contacts so that they can update affected questionnaires. Internal users do not receive
upgrade notifications. Suppliers or internal recipients can also choose to update registrations for other reasons.
When a recipient submits an update to an external registration questionnaire, the supplier remains in Registered
registration status, but has a separate Pending Approval registration update status.
The new registration workflow includes all of the tasks associated with all of the questionnaires in a new
registration. If your site uses the new supplier 360° profile and your registration projects include one or more
registration update phases to define tasks for registration updates, each questionnaire update is handled
individually. When a respondent submits an update to an external or internal registration questionnaire, only the
tasks associated with that questionnaire start, and task owners or approvers can complete the tasks related to the
questionnaire being updated. If your site does not use the new supplier 360° profile and your registration projects
include tasks in one or more registration update phases, the update workflow also includes all of the update tasks
associated with all of the questionnaires in the registration. When there are no remaining tasks in progress for the
questionnaire that is being approved and no tasks in progress for the other questionnaires in the update phase, the
update status is Approved.
If the registration update is not set to auto-approve, approvers approve or request more information for registration
updates. If the updates are approved, they are added to the supplier profile. The supplier remains in Registered
registration status, but will have Approved registration update status. The registration update status is always
based on the entire workflow defined by all of the tasks in registration update phases.
The registration status reflects the supplier's progress through the full initial registration process where your
organization collects important profile information from them. Registration update status is useful mainly for
tracking individual updates, which typically involve small changes to that profile information, and can be used to
create conditions in the registration project. Registration update status does not show in the supplier's 360° profile.
However, you can search for registration projects using the search bar on the Home dashboard and filter the results
by registration update status, and if you have permission to access the advanced view of a registration project, you
can see its registration update status on the Overview tab. To see the advanced of a registration project, the

Advanced View link for that project type must be enabled in your site and you must have the appropriate
permissions.
 Note
Questionnaire updates submitted using questionnaire data import or the Supplier Data API with Pagination do
not trigger registration update tasks.
Related Information

Supplier registration status flow
About supplier qualification and requalification using

supplier qualification projects
After a supplier is registered, a qualification manager can start qualifying the supplier for one or more specific
combinations of commodities, regions, and (optionally) departments by starting qualification projects and sending
qualification questionnaires. Approvers review the supplier's answers and approve or deny the qualifications.
Although a customer administrator can set qualification statuses for suppliers using a data import operation in
both SAP Ariba Supplier Management solutions, supplier qualification projects are only available in solutions that
include SAP Ariba Supplier Lifecycle and Performance.
Supplier qualification questionnaires typically solicit detailed information from the supplier that is specific to the
qualification's commodities and regions. For example, qualification questionnaires might ask suppliers about their
sourcing and sustainability processes; shipping, delivery, and return policies; commodity-specific certifications;
compliance with policies; and so forth. New qualifications are always based on commodities and regions that a
qualification manager selects; they do not have to be for the commodities and regions for which the supplier
registered. Qualifications and requalifications are also based on departments if the business unit matrix
enhancement is enabled in your site.
When a supplier either has been disqualified or had a qualification expire, they are eligible for requalification.
Qualifications and requalifications use the same workflow; however, a requalification is always based on the same
commodities, regions, and departments as the previous disqualification or expired qualification.
The supplier qualification project template determines:
● The questionnaire segments for various commodity, region, and department combinations, and which
segments are required.
● The approvers for the qualification or requalification. In sites that use buyer category assignments, approvers
are automatically assigned based on the commodities, regions, and departments of the qualification or
requalification.
● The content of the questionnaire segments.
● Whether other stakeholders in your organization must also approve the qualification or requalification.
● Whether internal questionnaires or other tasks or documents are part of the qualification or requalification w.

● Whether the qualification expires after a specific date, and if so, whether there is a waiting period before the
supplier can be requalified.
The category or supplier managers assigned to the supplier start a new qualification or a requalification, send the
questionnaire, review the supplier's answers, request more information, approve or deny the qualification or
requalification, and monitor the approval flow and status in the Qualification area of the supplier's 360° 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
SAP Ariba Supplier Management solutions.
Notifications let supplier know that they have been invited to qualify for specific commodities, regions, and
departments and provide a link to the questionnaire; let approvers know that they need to approve a supplier
qualification or requalification; let supplier or category managers know when one of their qualifications has expired
or is eligible for requalification; and let the supplier know that the qualification or requalification has been approved,
denied, or requires more information.
At any point after the supplier qualification or requalification has been approved, category or supplier managers
can:
● Start new qualifications for additional combinations commodities, regions, and departments.
● Evaluate the supplier for a preferred category status (if your company uses preferred supplier management
projects).
● Disqualify the supplier for commodities, regions, and departments for which it was previously qualified.
In solutions that include SAP Ariba Sourcing, event templates can specify that suppliers must have specific
qualification statuses for the event's commodities and regions to either participate in or be awarded events.
Departments are not considered for event eligibility.
Related Information

About setting preferred category statuses for suppliers

using preferred supplier management projects
After the supplier is qualified for a specific commodity, region, and (optionally) department combination, a
category or supplier manager can designate them as a preferred supplier for that combination.
Although a customer administrator can set preferred statuses for suppliers using a data import operation in both
SAP Ariba Supplier Management solutions, preferred supplier management projects are only available in solutions
that include SAP Ariba Supplier Lifecycle and Performance.

Supplier preferred category status is always based on a combination of commodity and region. It can also based on
departments if the business unit matrix enhancement is enabled in your site.
The preferred supplier management project template determines:
● What information users add to the preferred category status request form.
● Whether the preferred category status request requires approval, and if so, who the approvers are.
● Whether other stakeholders in your organization must also approve the status change.
Users request a preferred category status for a new commodity, region, and department combination, or a change
to an existing status, in the Preferred area of the supplier's 360° profile on the Supplier Management dashboard.
Up to five status levels are supported, including the preferred level. They also remove preferred status levels there.
 Note
You cannot combine multiple qualified combinations in the same preferred status request. For example, if a
supplier has separate qualifications for Electronic reference material and Printed media in the Canada region,
you must create individual preferred category status requests for each category.
If the preferred supplier management workflow includes an approval flow, notifications let the approver know that
the preferred status change request requires approval, let the requesting user know when the preferred status
request has been approved or denied, and show the final approver so that requesting users can have further
discussions about denied preferred status requests.
In solutions that include SAP Ariba Sourcing, event templates can be set up to automatically invite the suppliers
that are preferred for the event's commodities and regions. Department is not considered for automatic event
invitation.
Related Information

Supplier disqualifications using supplier disqualification

projects
After a supplier is qualified or preferred, a qualification manager can disqualify the supplier for previously qualified
specific commodities, regions, and (optionally) departments by submitting a disqualification form.
Although a customer administrator can set qualification statuses for suppliers using a data import operation in
both SAP Ariba Supplier Management solutions, supplier qualification and disqualification projects are only
available in solutions that include SAP Ariba Supplier Lifecycle and Performance.

Disqualifications are always based on a previous qualification. However, the disqualified commodities and regions
do not have to match exactly, and the disqualification always applies to all commodity or region levels below the
ones approved for disqualification. For example, a supplier can be qualified for Europe and subsequently
disqualified only in France; that disqualification applies to all departments and cities in France. Disqualifications are
also based on departments if the business unit matrix enhancement is enabled in your site.
The disqualification project template determines:
● What information qualification managers add to the form.

● Whether the disqualification requires approval, and if so, who the approvers are.
● Whether other stakeholders in your organization must also approve the disqualification.
● Whether the disqualification is immediate upon approval, takes effect on a specified date without phase-out, or
takes effect automatically after a phase-out period during which the supplier has Restricted status.
Category or supplier managers start the disqualification, approve or deny it, and monitor the approval flow and
status in the Qualification area of the supplier's 360° profile on the Supplier Management tab of the dashboard.
If a disqualification includes an approval flow, notifications let the approver know that the disqualification requires
approval, let the requesting user know when the disqualification has been approved or denied, and show the final
approver so that requesting users can have further discussions about denied disqualifications.
Once a disqualification is approved, any preferred supplier status for the disqualified commodities, regions, and
departments (including any preferred commodities, regions, or departments above or below the disqualified
commodities, regions, and departments in the same branch of the hierarchy) is automatically removed. For
example, if a supplier is preferred for shoes and later disqualified for apparel, the preferred status for shoes is
automatically removed. Likewise, if a supplier is preferred for apparel and later disqualified for shoes, the preferred
status for apparel is automatically removed. In solutions that include SAP Ariba Sourcing, if event templates are
restricted to qualified participants, or automatically invite preferred suppliers, disqualified suppliers are not event
participants. However, disqualification is otherwise just a status and there is no mechanism for preventing users
from inviting disqualified suppliers to unrestricted sourcing events and so forth.
Qualification managers can requalify disqualifications. If a qualification I restricted, a qualification manager can
only do so after the restricted period has passed and the supplier is disqualified. If a disqualification has a minimum
disqualification period set, they can only do so after that date has passed. They can also start new qualifications for
categories, regions, and departments other than the ones for which the supplier was disqualified.
Related Information


About supplier performance evaluations using SPM
projects
After your company has started buying from a supplier, category or supplier managers can use Supplier
Performance Management (SPM) projects to evaluate their performance on an ongoing basis.
SPM projects periodically solicit feedback from internal stakeholders based on a standardized set of criteria that is
applied to all suppliers.
The SPM project template typically uses:
● surveys, which collect input from stakeholders in your organization

● scorecards, which provide an overall score for suppliers
● recurring task phases for periodic review cycles, which include tasks to invite users to participate in surveys
and to review and publish scorecards
The category or supplier managers assigned to the project manage review cycles and use the information gathered
in them to evaluate and act on supplier performance by, for example, collaborating with suppliers on
improvements, designating them as preferred suppliers, or initiating disqualifications.
SPM projects use the classic SAP Ariba project interface, meaning that they are not visible in supplier 360° profiles
on the Supplier Management tab or linked to other supplier management projects. Supplier or category managers
create them by clicking Create SPM Project on the dashboard, and view them by searching for projects on
the Home dashboard.
Details on using SPM projects are covered separately in the Running supplier performance management reviews
topics.
Key assumptions for setting up SAP Ariba Supplier

Management solutions
The topics about setting up and managing SAP Ariba Supplier Lifecycle and Performance and SAP Ariba Supplier
Information and Performance Management (new architecture) assume the following:
● Your site has all common master data that is not specific to suppliers (commodities, regions, users,
departments, and so forth) loaded.
● The commodity, region, and (optionally) department data used in supplier management projects uses a
hierarchical structure with an "All" root node at the top of the hierarchy and, to the degree possible, multiple
levels of groupings. In some supplier management projects such as qualifications, disqualifications, and
preferred supplier management projects, the commodity/region/department combination for the project is an
important part of its functionality. If your master data uses a flat structure with a large number of low-level
values, users must add large numbers of low-level commodities, regions, or departments to those projects if
they want to include broad categories, regions, or departments, resulting in potential performance issues for
project-related queries. Structuring your commodity, region, and department data so that they can add the
most appropriate grouping at a higher level avoids this problem. Supplier management project performance is
likely to be poor if the project includes more than 50 commodity, region, and department values. In addition, if
you use the user matrix (buyer category assignments) to populate project groups based on the project
commodity, region, and department, a well-defined hierarchy with groupings at multiple levels can provide
better user matrix coverage.

For example, if a category or supplier manager wants to qualify a supplier for shoes, but your commodity
master data only includes level 4 entries for mules, kitten heels, pumps, hiking boots, running shoes, and so
forth, the category or supplier manager must add each of those individual commodities to the qualification
project, and all queries related to that qualification must include all of those individual commodity values. On
the other hand, if your commodity hierarchy includes a level 3 value for shoes, with all of those level 4 values
located under it, the category or supplier manager can simply qualify the supplier for shoes, resulting in more
efficient qualification queries using the single commodity value.
In some cases, only one or two of the three "matrix" elements (commodity, region, and department) is
important in the project. For example, a commodity or supplier manager might want to qualify a supplier
globally for a specific commodity, or qualify a supplier for a commodity in Europe regardless of department.
Including a top-level value for "All" at the top of your commodity, region, and department hierarchies allows the
category or supplier manager to explicitly select one value of "All" rather than having to select multiple values
that combine to achieve "All," and the single-value selection avoids performance problems in queries. Note that
"All" is used here as an example, not a literal value.
● 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 supplier data integration with SAP Ariba Supplier
Management solutions are separate configurations.
Related Information
What is supplier management in SAP Ariba Supplier Management solutions? [page 10]
Where to find more information [page 29]
Integration options for SAP Ariba Supplier Management solutions [page 26]

Supplier management setup checklist
A checklist helps you identify the tasks that are essential to setting up SAP Ariba Supplier Lifecycle and
Performance or SAP Ariba Supplier Information and Performance Management (new architecture).
Assign users in your site to the relevant Supplier management

 user groups [page 31], making sure that:
● The users who will set up integration are in the SM ERP

Administrator group.
● The users who will import data are in the Customer
Administrator and SM Ops Administrator groups.
● The users who will perform other supplier management-
specific administrative tasks are in the SM Ops
● The users who will set up project templates are in the
Template Creator group and, for modular supplier man
agement questionnaire project templates, also in the SM
Modular Questionnaire Manager group.
Review the list of optional features [page 399] that are not ena
 bled by default and the available configuration options [page
516] and enable the ones you want to use.
If your company uses SAP ERP, SAP S/4HANA, or SAP MDG,

 set up the supplier data integration. See the Configuration
guide for sourcing, contracts, and supplier data integration with
SAP ERP and SAP S/4HANA for details.
Set up and publish theinternal supplier request project tem

 plate [page 135]. Make sure that the internal supplier request
form includes the required questions for supplier name and
contact first name, last name, and email address.
If you plan to use external supplier requests, set up and publish

the external supplier request [page 135] in this step as well. It
has the same requirements for questions about supplier name
and contact first name, last name, and email address.
Set up and publish the supplier registration project template

 [page 148].
Set up and publish the supplier qualification project template

 [page 176] (SAP Ariba Supplier Lifecycle and Performance
only).

(Optional) Set up preferred supplier management by:
 ● Defining your preferred supplier levels [page 39].
● Setting up and publishing the preferred supplier manage
ment project template [page 187].
(SAP Ariba Supplier Lifecycle and Performance only)
Set up and publish the supplier disqualification project tem

 plate [page 184] (SAP Ariba Supplier Lifecycle and Perform
ance only).
(Optional) If you plan to use modular supplier management

 questionnaires either as standalone questionnaires or for cer
tificate management, set them up by:
● Importing questionnaire type data [page 40].

● For certificate management, importing certificate types
[page 44].
● Creating and publishing modular supplier management
questionnaire project templates [page 190].
(Optional) Customize notifications for all supplier manage

 ment projects.. [page 345]
(Optional) Contact your designated support contact to set up

 the way supplier contacts are synchronized from Ariba Net
work supplier accounts [page 516].
Assign your company's category or supplier managers to the

 commodities and regions [page 98] for which they are re
sponsible.
Import all of your supplier data. [page 67]


(Optional) Start onboarding suppliers in bulk by issuing a mass
 registration invitation [page 362].
(Optional) If your solution includes SAP 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 events that
match their categories and regions.
See the Event Rules Reference for details.

APIs for SAP Ariba Supplier Management solutions
The SAP Ariba developer portal includes APIs that allow you to write applications that interact with SAP Ariba
Supplier Management solutions.
To use these APIs, you must complete the onboarding process on the SAP Ariba developer portal (https://
developer.ariba.com/api/ ). For instructions on how to do so, see the documentation there.
Supplier Data API with Pagination
The Supplier Data API with Pagination includes endpoints that allow you to extract basic supplier details, project
IDs, questionnaires, and questionnaire content, including information on certificate questions. It uses pagination
tokens to paginate results, and includes query and filter parameters that let you filter results.
External approval API
The external approval API allows you to process supplier management approval tasks in an external system,
including the addition of comments. Note that in addition to creating a client application with the API, you must
configure the approval tasks in your supplier management projects [page 337] to allow external approval.
Integration options for SAP Ariba Supplier

SAP Ariba offers several options for integrating SAP Ariba Supplier Management solutions with ERP systems.
SAP Ariba Supplier Management solutions integration with SAP ERP and SAP S/4HANA
SAP Ariba Supplier Management solutions offer integration with SAP ERP and SAP S/4HANA On Premise Edition,
with or without SAP Master Data Governance for Suppliers (MDG-S), and SAP S/4 HANA Cloud Edition release
2002 and higher without MDG-S. This integration method includes bi-directional synchronization of supplier data
between SAP Ariba Supplier Management solutions and the ERP system. Integration with custom fields is not
currently supported for SAP S/4 HANA Cloud Edition, since SAP Ariba Cloud Integration Gateway integration with
SAP S/4 HANA Cloud Edition does not currently include SAP Ariba Cloud Integration Gateway add-ons.
In configurations that include MDG-S, integration options enable validation of supplier requests in MDG-S before
the supplier record is created in the SAP Ariba supplier database and external approval of updates to supplier data
in registration questionnaires.

For details, see the Configuration guide for sourcing, contracts, and supplier data integration with SAP ERP and SAP
S/4HANA and the SAP Ariba Cloud Integration Gateway documentation set.
SAP Ariba integration toolkit
The SAP Ariba integration toolkit supports automated import of a limited set of supplier data from an ERP system
to SAP Ariba Supplier Management solutions. It does not support export of data from SAP Ariba Supplier
Management solutions to the ERP system, and does not support import of supplier contact data. You can only use
it to import extended supplier profile data if you previously migrated from SAP Ariba Supplier Information and
Performance Management (classic architecture) to the unified vendor model and defined mappings between your
previous supplier profile questionnaire and content in registration questionnaires while in migration mode.
For details, see the SAP Ariba integration toolkit guide.
SOAP web service API integration
SAP Ariba SOAP web service APIs support import of a limited set of supplier and supplier contact data from an ERP
system to SAP Ariba Supplier Management solutions. They do not support export of data from SAP Ariba Supplier
Management solutions to the ERP system. You can only use SOAP web service APIs to import extended supplier
profile data if you previously migrated from SAP Ariba Supplier Information and Performance Management (classic
architecture) to the unified vendor model and defined mappings between your previous supplier profile
questionnaire and content in registration questionnaires while in migration mode.
For details, see the SOAP web service API integration guide.
Transitioning from supplier organizations to supplier

requests and registrations
If you have an existing SAP Ariba solution that includes SAP Ariba Sourcing, SAP Ariba Contracts, or SAP Ariba
Supplier Information and Performance Management (classic architecture) and you are adding SAP Ariba Supplier
Lifecycle and Performance or SAP Ariba Supplier Information and Performance Management (new architecture),
your site is transitioning from a supplier data model that uses supplier organizations and the supplier profile
questionnaire a new, unified supplier data model that uses supplier requests and registrations.
The unified vendor model offers more flexible tools for gathering profile data, and in SAP Ariba Supplier Lifecycle
and Performance it includes additional methods for information-gathering and supplier management through
qualifications, preferred supplier management, and disqualifications.
SAP Ariba offers tools for migrating supplier organization, supplier user, and supplier profile questionnaire data to
the unified vendor model and supplier registration questionnaires. For information on these tools, see Migrating
suppliers to the unified vendor model.
The unified vendor model includes the following benefits:

● Rich supplier 360° views with all supplier information and management functionality in one place.
● Unified vendor master data management, with a complete vendor model in a new supplier database and native
integration with SAP ERP.
 Note
If your site uses Supplier Performance Management (SPM) projects, they continue to be standalone projects
and cannot be accessed from the supplier 360° profile.
In sites that have transitioned from supplier organizations to the unified vendor model, users can no longer
explicitly create new suppliers. The new supplier request and registration processes replace both supplier creation
(workspace projects) and the supplier profile questionnaire. Existing suppliers that are imported into the new data
model no longer have a Profile tab or supplier profile questionnaire data; instead, they have supplier 360° views
and have not yet been invited to register.
This means that template creators no longer update your site's supplier workspace template and supplier profile
questionnaire. Instead, they set up request and registration project templates. Category and supplier managers
work with supplier data on the Supplier Management dashboard, and manage registration in each supplier's 360°
view instead of on the Profile tab.
The following table summarizes the differences between supplier organizations with the supplier profile
questionnaire and the new request and registration workflow for gathering supplier profile information:
Feature Classic functionality New extended functionality
Supplier creation Users in different supplier management Users such as sourcing agents and func
groups click Create Supplier on tional buyers click Create Supplier

the dashboard to create a new supplier Request on the dashboard to create a
workspace project. The supplier is cre new supplier request project. Users in the
ated at this point. A user in the Supplier/ request approval flow approve the sup
Customer Manager group who is on the plier request. The supplier is only created
supplier workspace project team appro after the request is approved.
ves new suppliers.
Supplier profiles A supplier organization's Profile tab A supplier's 360° view on the Supplier
shows common profile fields and the Management tab shows request and reg
supplier's answers to the supplier profile istration information, information from
questionnaire. the ERP system, and information from
Ariba Network.
Questionnaires Users collect information about suppliers Users collect information about suppliers
using the supplier profile questionnaires. using separate internal and external reg
istration questionnaires.
Supplier search Users search for suppliers from any Users search for suppliers based on
dashboard tab based on values in profile name, ID, or contact name from any
fields. They cannot filter search results. dashboard tab, and results are shown on
the Supplier Management tab. They can
filter search results based on commodity,
region, status, an other criteria.

Feature Classic functionality New extended functionality
Synchronization of new suppliers to the In integrated sites, all new suppliers are The stage of the request or registration
integrated SAP ERP system initially synchronized to the ERP system process at which new suppliers are ini
after they are created. tially synchronized to the SAP ERP sys
tem is configurable.
One of the options is manual synchroni

zation, which allows customer adminis
trators to decide if and when to syn
chronize new suppliers.
Where to find more information

In addition to this set of topics, there are a number of additional resources that contain useful information for
setting up and managing SAP Ariba Supplier Management solutions.
To find more information about... See...
Importing master data other than suppliers (including users, Common data import and administration guide for SAP Ariba
regions, commodities, and so forth) into your site Strategic Sourcing and Supplier Management solutions
 Note
The information about importing supplier data and man
aging suppliers and supplier users in this guide does not
apply to your solution.
SAP Ariba project templates in general, including documents, Project Template Guide
task, teams, versioning, and publication
 Note
The information in this guide is general; supplier manage
ment project templates have a number of specific restric
tions and requirements, and do not support a number of
general project template features.
SAP Ariba projects in general, including details about approval Managing Projects, Teams, Documents, and Tasks
and To Do tasks
 Note
Since users interact with supplier management projects in
a specialized workflow, for details about how users interact
with supplier management projects, see the Managing
suppliers and supplier lifecycles.
Managing enterprise users in your site Common data import and administration guide for SAP Ariba
Strategic Sourcing and Supplier Management solutions

To find more information about... See...
Understanding what permissions each supplier management Strategic Sourcing and supplier management group descrip
user group has in detail tions
Setting up sourcing event templates to use qualified and pre Event Management Guide and Event Rules Reference
ferred suppliers
General templates for email notification templates generated Managing project email notifications
by SAP Ariba projects and their tasks
Setting up Supplier Performance Management (SPM) projects Configuring supplier performance management
Running SPM projects Running supplier performance management reviews
Setting up integration with SAP ERP Configuration guide for sourcing, contracts, and supplier data
integration with SAP ERP and SAP S/4HANA
Using the SAP Ariba integration toolkit with SAP Ariba Supplier SAP Ariba integration toolkit guide
Using SOAP web service APIs for integration with SAP Ariba SOAP web service API integration guide
Supplier Management solutions
Using supplier management-related SAP Ariba APIs on the ● The SAP Ariba developer portal
SAP Ariba developer portal ● SAP Ariba Supplier Data API
● External Approval API for Sourcing and Supplier Manage
ment

Topics about setting up supplier management
users
Supplier management user groups [page 31]
How to add users [page 33]
How to edit users [page 35]
User groups in supplier management buyer category assignments (the user matrix) [page 36]
Supplier management user groups

SAP Ariba Supplier Management solutions use membership in global user groups to grant users permissions to
work with specific supplier management features.
 Note
Before you set up supplier management users, they must be created in your site. Typically, enterprise users are
imported as master data as part of SAP Ariba's deployment of your site. You can also manually create
enterprise users [page 33]. For details, see the Common Data Import and Administration Guide.
The following table provides a brief description of the user groups are pertinent to supplier management. For
complete details, see the SAP Ariba Strategic Sourcing and Supplier Management solutions group descriptions:
Members of this group... Can...
Template Creator Manage all supplier templates, including creating question

naires and request forms. In the default configuration, the
Template Creator group is a member of the project team for
all of the supplier management project templates.
Members of the Template Creator group must also belong to

the SM Modular Questionnaire Manager group to create and
manage modular supplier management questionnaire tem
plates.
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).
Project Email Templates Administrator Customize the content of all project-related notifications.

Topics about setting up supplier management users PUBLIC 31
Customer Administrator Import and export data in Ariba Administrator and SM

Administration, create new users, and add groups to existing
users.
Customer User Admin Create new users and add groups to existing users.
Supplier Request Manager Create supplier requests.
Supplier Registration Manager Initiate and manage supplier registrations.
Supplier Qualification Manager Initiate and manage supplier qualifications and disqualifica-
tions.
Preferred Supplier Manager Initiate and manage processes to designate preferred suppli
ers.
SM Modular Questionnaire Manager Create and manage modular supplier management question
naires. Users who are also members of the Template Creator
group can also create and manage modular supplier manage
ment project templates.
Supplier Internal Questionnaire Editor Edit the internal registration questionnaire.
SPM Agent Create and manage SPM projects.
Sensitive Data Access View masked answers and attachments [page 297] in supplier
management questionnaires.
SM Manual ERP Sync Manually synchronize new suppliers with an integrated SAP
ERP system.
 Note
To preserve backward compatibility, all members of the
Supplier Registration Manager group as of the time of the
SAP Ariba May 2018 release were automatically added to
the SM Manual ERP Sync group so that they did not lose
an existing permission. If you want to remove the permis
sion from any of those users, you can do so in Ariba Ad
ministrator either manually or using the Import Group/
User Relationships data import task.
Users added to the Supplier Registration Manager group

after the SAP Ariba May 2018 release do not have the
manual ERP synchronization permission unless you also
add them to the SM Manual ERP Sync group.

32 PUBLIC Topics about setting up supplier management users
SM Ops Admin Import and export data and perform other administrative ac
tions in SM Administration area, as well as access the
Advanced View of supplier management projects when the
Control access by group option is disabled.
SM ERP Admin Configure integration with an external ERP system in SM

Administration area and manually synchronize new suppliers
with an integrated SAP ERP system.
SM Advanced View Access Access the Advanced View of supplier management projects
when the Control access by group option is enabled.
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 supplier management users, either create new users [page 33] or edit existing users [page 35], adding
the relevant groups to them.
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 Manage 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 (SAP 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.)SAP 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
Application.Base.EnforceEmailDomainCheck (set by SAP Ariba Support).
 Note
If SAP 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 - Check this checkbox to allow an unapproved email address domain for this
user.
○ 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. Specify one of the currency codes defined in your SAP
Ariba solution.
○ 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:
○ Check the checkbox 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 SAP 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 SAP Ariba. When the user clicks
the URL in the invitation, the user is prompted to create a new password.
Related Information
User data import and export tasks

How to generate or reset user passwords
Topics about user group management
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.
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.
Related Information
User data import and export tasks

Topics about user group management
User groups in supplier management buyer category

assignments (the user matrix)
You can assign either custom or default user groups to supplier management project teams using a buyer category
assignment (user matrix) CSV data file import.
The data import adds each specified user or group to a specific project group in supplier management projects
that match the assigned commodities, regions, and (in sites with the business unit matrix enhancement feature
enabled) department. Those project groups are then used in the project's approval flow. Buyer category
assignments therefore dynamically add users (either explicitly or through user group membership) to individual
project approval flows based on the project's commodities, regions, and departments. For details on buyer
category assignment data, see User matrix (buyer category assignment) data file format [page 98]. For details
and an example of using buyer category assignments to create a dynamic approval flow, see Using commodity,
region, and department assignments for form and questionnaire approvals [page 329].
There are advantages to making buyer category assignments by user group. If you assign individual users, when
those users leave the company or change roles, you must update and re-import the user matrix data. If you assign
groups, any member in the group can approve or deny the task, and you can add or remove users from groups as
needed rather than updating individual assignments. Having a larger pool of potential approvers means that there
is less risk that individual projects will have approval nodes with no assigned approvers. Whether you define buyer
category assignments by group or user depends on how detailed you want to make the assignments and how you
want to manage user groups in general in your site.
You can use SAP Ariba's default system groups or custom groups that you create when defining buyer category
assignments. For example, you can use the default Category Manager group, which includes a number of sourcing
permissions; or you can create a custom IT Category Manager group and add only a subset of your category
managers to it.
For details on user groups and how to create custom groups, see the Common data import and administration
guide topics.

Topics about importing supplier management
data
Topics about importing site master data for supplier management [page 37]
Topics about importing supplier-related data in SM Administration [page 67]
How to import custom SAP region codes for supplier extended addresses [page 104]
Importing business partner IDs for ERP suppliers added through SAP Ariba Procurement solutions [page 106]
Topics about importing site master data for supplier

management
About importing site master data for supplier management [page 38]
Defining preferred supplier levels [page 39]
Defining modular supplier management questionnaire types [page 40]
Defining supplier certificate types [page 44]
Defining questionnaire scoring band categories [page 45]
Defining questionnaire scoring bands [page 47]
Defining country-specific tax ID fields in Tax questions [page 50]
Defining country-specific bank ID prefixes for Bank Account questions [page 52]
Topics about defining country-specific validations for supplier bank account information [page 54]
Defining country-specific ERP region code mappings [page 60]
Defining country-specific postal code validation for supplier addresses [page 61]
Defining mappings between guided buying ship-to addresses and preferred and qualified supplier regions
[page 64]
How to import your data [page 65]
How to import your translation data [page 66]
Language values for defining translations [page 67]

Topics about importing supplier management data PUBLIC 37
About importing site master data for supplier management
Site master data for supplier management projects is typically used to define types or levels in projects. You import
site master data for supplier management using the Ariba Administrator Site Manager workspace.
Depending on your solution and the features enabled in your site, supplier management processes can use the
following types of site master data:
This master data... Is used for defining...
Preferred supplier levels [page 39] The names of the five preferred supplier management statuses
in your site (SAP Ariba Supplier Lifecycle and Performance
only).
Modular questionnaire types [page 40] Types for the modular supplier management questionnaires in
your site.
Supplier certificate types [page 44] The types of certificate questions that you use to collect sup
plier certificate information in your site.
Questionnaire scoring bands [page 47] The groupings or bands into which you divide different ranges
of modular supplier management questionnaire scores.
Questionnaire scoring band categories [page 45] The different types of scoring bands you use for scoring modu
lar supplier management questionnaires.
Country-specific tax ID fields [page 50] The country-specific tax ID fields, including supplier field map
pings and validation patterns, that are used in answers to Tax
questions in supplier management questionnaires.
Country-specific bank ID prefixes [page 52] The optional country-specific prefixes used in automatically
generated bank IDs for Bank Account questions in supplier
Country-specific bank control keys [page 54] The country-specific bank control key values available in the
Control Key field of Bank Account questions.
Country-specific IBAN number syntax [page 56] The country-specific syntax against which IBAN number an
swers in Bank Account questions is validated.
Country-specific syntax validation for bank account holder The country-specific syntax validation for bank account holder
name, account number, and bank key or ABA routing number name, account number, and bank key or ABA routing number
[page 58] answers in Bank Account questions.
Country-specific ERP region code mappings [page 60] The country-specific mappings between the custom SAP re
gion codes in Extended Address questions and the state co
des in supplier profile addresses on Ariba Network.
Country-specific postal code validation for supplier addresses The country-specific syntax validation for postal codes in
[page 61] Address and Extended Address questions.
Mappings between guided buying ship-to addresses and pre Mappings between the 2-character ISO country codes used in
ferred and qualified supplier regions [page 64] guided buying and the region codes your site uses to identify
preferred and qualified suppliers.
These are the types of site master data that are specific to supplier management. The Ariba Common Data Import
and Administration Guide describes all other site master data, as well as site administration, in detail. You can also

38 PUBLIC Topics about importing supplier management data
import custom SAP region fields [page 104] for use in Extended Address questions if your site is integrated with
an SAP ERP, SAP S/4HANA, SAP S/4HANA Cloud, or SAP MDG-S system that includes custom region fields.
 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 importing and exporting supplier organizations and profiles,
apply only to sites that do not use the unified vendor model. Sites that include SAP Ariba Supplier Lifecycle and
Performance or SAP Ariba Supplier Information and Performance Management (new architecture) use the
unified vendor model. In sites that use the unified vendor model, there is a separate process for importing
supplier data [page 67].
Defining preferred supplier levels
Preferred supplier levels indicate the degree to which your organization prefers one supplier over another for a
given category, region, department, or any combination of those three groups.
Examples of preferred supplier levels include number ranges (such as 1-5) or text labels (such as 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 PreferredSupplierLevels.csv 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, ensure that your pre
ferred level uses a UniqueName of 1. Only suppliers with
a preferred level that maps to 1 are automatically invited to
sourcing events.
The following example shows lines of the PreferredSupplierLevels.csv file, as well as the mandatory header:
UTF-8
Name,UniqueName
Bronze,1

Silver,2
Gold,3
After you have defined preferred supplier levels in PreferredSupplierLevels.csv, you import it into your site.
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 PreferredSupplierLevels.csv 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.
Language The language of the name.
The following example shows lines of the PreferredSupplierLevels.csv file for supplier level translation, as
well as the mandatory header:
UTF-8
Name,UniqueName
Oro,3,Spanish
Or,3,French
Ouro,3,BrazilianPortuguese
After you have defined preferred supplier level translations in PreferredSupplierLevels.csv, you import it
into your site.
Related Information
How to import your data [page 65]

Language values for defining translations [page 67]
Defining modular supplier management questionnaire

types
Questionnaire types specify the different categories or areas into which your company's modular supplier
management questionnaires are divided, usually based on their purpose. Each modular supplier management
questionnaire template has a type that determines its use.
For example, your company might define questionnaire types such as Compliance, Finance, Quality,
Certifications, and so on. Based on your site's modular supplier management template configurations, users

working with supplier management processes can send different modular questionnaires based on their
questionnaire type as well as the commodities, regions, and departments applicable to the process.
If your company uses modular supplier management questionnaires, you must define their types. If the types you
use are text labels, you must also define translations for each language you use in your site.
Defining the questionnaire types
You use the Import Questionnaire Types data import task to define questionnaire types. The task reads from the
SMQuestionnaireType.csv file, which includes the following fields:
Field Description Required?
Description A description of the questionnaire type. No

EvaluationType Specifies whether or not the modular No

questionnaire uses scoring using one of
the following values:
● Graded, meaning that the ques

tionnaire is evaluated based on
scores and scoring band ranges con
figured in the modular questionnaire
project template, which generate a
score and a band indicator for each
questionnaire based on respondent
answers. In the modular supplier
management questionnaire project
template, if a template creator choo
ses a questionnaire type with the
Graded evaluation type, they see
Band Score Range settings where
they can configure the range of
scores associated with each scoring
band in the questionnaire.
● NonGraded, meaning that the
questionnaire is evaluated based on
subjective judgment of respondent
answers. In modular supplier man
agement questionnaire project tem
plates, if a template creator chooses
a questionnaire type with the
NonGraded evaluation type, they
cannot configure band score ranges.
Blank values are considered

NonGraded.
Note that the value you specify in this

field simply determines whether or not
questionnaires of a given type use grad
ing for evaluation. For each individual
modular supplier management question
naire project template with a Graded
evaluation type, the actual scoring, the
type of scoring bands, and the range val
ues for those bands are defined in the in
dividual template.
Name The name of the questionnaire type. This Yes

name appears in the Questionnaire Type
dropdown menu in modular supplier
management questionnaire templates.

UniqueName The unique ID of the questionnaire type. Yes
If your site includes SAP Ariba Supplier

Risk control-based engagement risk as
sessment projects and you plan to use an
engagement risk assessment process
with only internal assessments for en
gagements with no specified supplier,
you must define a questionnaire type
with a UniqueName of SR
Engagement Questionnaire
Type, using this exact text. This require
ment is only applicable if the ability to
submit an engagement request with no
supplier selected is enabled in your site.
The following example shows lines of the SMQuestionnaireType.csv file, as well as the mandatory header:
UTF-8
Description,EvaluationType,Name,UniqueName
Health and safety requirements,Graded,Occupational Health and Safety
Requirements,OHSR
Certifications,NonGraded,Certifications,CERT
Defining translations for questionnaire types
You use theImport Translations for Questionnaire Types data import task to define translations for the
questionnaire types you defined in SMQuestionnaireType.csv. The task reads from a CSV file that includes the
following fields:
Name The translation for the name of the ques Yes

tionnaire type.
UniqueName The unique ID of the questionnaire type Yes

as defined in
SMQuestionnaireType.csv.
Language A valid value for the translation language. Yes
The following example shows lines from a CSV file for questionnaire type translations, as well as the mandatory
header:
UTF-8
Name,UniqueName,Language
Requisitos de Salud y Seguridad Ocupacional,OHSR,Spanish

Arbeitsschutzanforderungen,OSHR,German
Defining supplier certificate types
Certificate types specify the different categories into which your company's certificates are divided, usually based
on their purpose.
For example, your company might define certificate types such as Small Business, Women Owned, Green,
various ISO standards, and so on.
If your company uses certificate management, you must define certificate types. If the types you use are text
labels, you must also define translations for each language you use in your site.
 Tip
When defining your certificate types, keep in mind that the names of certificate types (which you define in the
Name field) and their translations display in the following places:
● A dropdown menu that template creators use when creating certificate questions [page 245] in modular
supplier management questionnaires.
● Certificate information in suppliers' 360° profiles.
● As search filters in supplier search on the Supplier Management dashboard.
● The subject lines of email notifications [page 355] sent to suppliers and internal users to inform them of
certificate expirations.
● In your suppliers' Ariba Network for Suppliers accounts, next to the certificate questions they have
answered for you.
Defining the questionnaire types
You use the Import Certificate Types data import task to define questionnaire types. The task reads from the
CertificateType.csv file, which includes the following fields:
Description A description of the certificate type. No
Name The name of the certificate type. Yes
UniqueName The unique ID of the certificate type. Yes
The following example shows lines of the Certificate.csv file, as well as the mandatory header:
UTF-8
Description,Name,UniqueName
Green Certified,Green,GRN
ISO 9001,ISO 9001,ISO9001

Defining translations for questionnaire types
You use theImport Translations for Certificate Types data import task to define translations for the certificate
types you defined in CertificateType.csv. The task reads from a CSV file that includes the following fields:
Name The translated for the name of the certifi- Yes

cate type.
UniqueName The unique ID of the certificate type as Yes

defined in CertificateType.csv.
Language A valid value for the translation language. Yes
The following example shows lines from a CSV file for certificate type translations, as well as the mandatory
header:
UTF-8
Verde,GRN,Spanish
Grün,GRN,German
Defining questionnaire scoring band categories
Scoring band categories define the different types of scoring bands your organization can use in questionnaire
scoring, usually based on the type of questionnaire data being scored. Each scoring band type includes a set of
individual bands.
For example, you might create a scoring band category called Compliance to use in modular supplier
management questionnaires that assess a supplier's compliance with different standards and procedures. You
define the bands for the Compliance band type in a separate scoring band data file [page 47].
If your organization uses scoring and banding in modular supplier management questionnaires, you must define
scoring band categories. There is no limit to the number of band categories you can define. If the categories you
use are text labels, you must also define translations for each language you use in your site.
Defining scoring band categories
You use the Import Scoring Band Categories data import task to define scoring band categories. The task reads
from the SMBandCategory.csv file, which includes the following fields:
Description A description of the scoring band cate No

gory

Name The name of the scoring band category. Yes

This name shows in the Band Category
dropdown menu in modular supplier
management questionnaire project tem
plates.
UniqueName The unique ID of the scoring band cate Yes

gory, which you specify in the
BandCategory.UniqueName field
when defining the individual bands for
each band category [page 45].
The following example shows lines of the SMBandCategory.csv file, as well as the mandatory header:
Description,Name,UniqueName
Scoring band category for compliance-related questionnaires,Compliance,Compliance
Scoring band category for audit-related questionnaires,Audit,Audit
Defining translations for scoring band categories
You use the Import Scoring Band Category Translations data import task to define translations for the scoring
band types you defined in SMBandCategory.csv. The task reads from a CSV file that includes the following fields:
UniqueName The unique ID of the scoring band cate Yes

gory as defined
inSMBandCategory.csv.
Name The translation for the name of the scor Yes

ing band category.
Description The translation for the description of the No

scoring band category.
Language A valid value for the translation language Yes
The following example shows a line from a CSV file for scoring band category translations, as well as the mandatory
header
UniqueName,Name,Description,Language
Compliance,Conformidad,Tipo de banda de puntuación para cuestionarios relacionados
con la conformidad,Spanish
Related Information

Adding scoring and score bands to modular supplier management questionnaires [page 203]

Defining questionnaire scoring bands
Scoring band data defines groupings for individual questionnaire scores. The band into which a score falls
determines the color of its color-coded indicator and label in the user interface, which provide guidance for
approvers and other stakeholders who need to make decisions about a questionnaire's responses.
Each band category [page 45] can include one or more bands. There is no technical limitation on the number of
bands per band category, but you can only assign them 16 pre-defined HTML colors , and in practice it's a good
idea to create no more than five bands per category to keep guidelines clear and prevent approvers and other
stakeholders from having to make subjective judgments on the differences between very narrow bands. Keep in
mind also that the template creator must use all of the bands defined for the selected band category in a
questionnaire. They cannot pick and choose which bands to use.
You define the bands themselves, their labels, and their associated colors in scoring band data. For example, for the
Compliance band category, you can define bands of Noncompliant (red), Marginally Compliant (yellow),
Substantially Compliant (green), and Fully Compliant (lime green). You do not define the range of scores
for each band. Each modular supplier management questionnaire project template defines the score ranges that
apply to each band so that template creators can calibrate the bands to the questionnaire's content.
If your organization uses scoring and banding in modular supplier management questionnaires, you must define
scoring bands. If the band names you use are text labels, you must also define translations for each language you
use in your site.
Defining scoring bands
You use the Import Scoring Bands data import task to define scoring bands. The task reads from the SMBand.csv
file, which includes the following fields:
BandCategory.UniqueName The unique identifier of the category for Yes

the scoring band as defined in the
UniqueName field of the band category
data import file [page 45].

Color The color to display in the band indicator, Yes

which is a colored dot that shows to the
right of each numerical questionnaire
score. You can specify the name of any of
the following 16 pre-defined HTML colors
in this field:
● Aqua
● Black
● Blue
● Fuchsia
● Gray
● Green
● Lime
● Maroon
● Navy
● Olive
● Purple
● Red
● Silver
● Teal
● White
● Yellow
The color visually differentiates scores
that fall within different bands. It's a good
idea to use a different color for each band
in a single band category; otherwise, ap
provers and other stakeholders must
know how to interpret the numerical dif
ferences between scores that fall within
different bands.
Description The description for the band. No
Name The name of the band. This name dis Yes

plays as a label when a user mouses over
a color-coded band indicator.
UniqueName A unique ID for the scoring band.

The following image shows a scoring band indicator for a score in a band with a Name of Average and a Color of
Yellow in the user interface:
The numerical range to the right of the Name in the hover text is the band range defined in the modular supplier
management questionnaire project template.
The following example shows lines of the SMBand.csv file, as well as the mandatory header:
BandCategory.UniqueName,Color,Description,Name,UniqueName
Compliance,Red,Band for noncompliant scores,Noncompliant,Compliance0
Compliance,Green,Band for fully compliant scores,Fully Compliant,Compliance3
Defining translations for scoring bands
You use the Import Scoring Band Translations data import task to define translations for the scoring band
categories you defined in SMBand.csv. The task reads from a CSV file that includes the following fields:
UniqueName The unique ID of the scoring band as de Yes

fined inSMBand.csv.
Name The translation for the name of the scor Yes

ing band.
Description The translation for the description of the No

scoring band.
Language A valid value for the translation language Yes
The following example shows a line from a CSV file for scoring band category translations, as well as the mandatory
header
UniqueName,Name,Description,Language
Conformidad,Completamente en conformidad,Banda para puntajes completamente en
conformidad,Spanish
Related Information


Defining country-specific tax ID fields in Tax questions
You can define the country-specific tax ID fields that respondents see in Tax questions, including validation
patterns and the vendor database fields to which they map, using data import tasks in Ariba Administrator.
Tax questions in supplier management questionnaires present respondents with an initial Country dropdown
menu; once the respondent chooses a country, the tax ID fields that you have defined for that country show. All tax
ID fields for the chosen country are required by default. To allow respondents to submit a blank answer for a tax
field, you can define a validation pattern of (^$) in your tax metadata CSV. To both allow blank answers and ensure
that if the supplier does answer the question, their answer must have a valid format, you can place the (^$)
pattern at the beginning or end of an existing validation pattern, separated by a pipe character (|). For example,
either of the following patterns allows the supplier to submit either a blank answer or an answer with a length of 10:
(^$)|(^\d{10}$) or (^\d{10}$)|(^$).
Defining the country-specific tax fields
You use the Import SAP Tax Metadata data import task to define preferred supplier levels. The task reads from the
SapTaxMetadata.csv file, which includes the following fields:
Field Description
UniqueName A unique identifier for the country-specific tax ID field.
CountryCode The country code to which the tax ID applies. The country code
you specify must match the country code master data loaded
for your site.
IsOrganization A boolean field that specifies the tax category. Specify TRUE
for Organization or FALSE for Personal. Tax questions cur
rently do not support the collection of personal tax data, and
rows with IsOrganization set to FALSE are ignored dur
ing tax data import.
TaxCode A number between 0 and 5 that determines the vendor data

base field to which the country-specific tax ID field is mapped
as follows:
● A TaxCode value of 0 maps to

vendor.taxExt.vatRegistrationNumber.
● TaxCode values of 1-5 map to
vendor.taxExt.taxNumber1 -
vendor.taxExt.taxNumber5, respectively.
TaxName The name of the tax. This name is used as the label for the tax
ID field in the question in your site's default locale. You can pro
vide translations for this name in a separate translation data
import file.

Field Description
RegexPattern A regular expression that defines the validation pattern for the
tax ID.
SampleFormat An example of a valid value for the tax ID. This example is used
in the automatic validation error message that respondents
see when they provide an answer that does not match the vali
dation pattern defined in RegexPattern.
Unlike other types of questions, you cannot specify validation patterns and validation error messages directly when
creating questions of answer type Tax. Instead, you specify the pattern and sample format for each country-
specific field in the SapTaxMetadata.csv file. The value a respondent provides for that field is automatically
validated against the pattern specified in the RegexPattern field, and the error message uses the example value
specified in the SampleFormat field.
The following example shows lines of the SapTaxMetadata.csv file, as well as the mandatory header:
UTF-8
UniqueName,CountryCode,IsOrganization,TaxCode,TaxName,RegexPattern,SampleFormat
DE0,DE,TRUE,0,Germany: VAT Registration Number,^DE\d{9}$|ÊU,DE123456789:EU
DE1,DE,TRUE,1,Germany: Income Tax Number,^DE\d{9}$|ÊU,DE123456789:EU
DE2,DE,TRUE,2,Germany: VAT Number,^DE\d{9}$|ÊU,DE123456789:EU
DE3,DE,TRUE,3,Germany: Elster Tax Number,^DE\d{9}$|ÊU,DE123456789:EU
DE4,DE,TRUE,4,Germany: Tax Number,^DE\d{9}$|ÊU,DE123456789:EU
Defining translations for country-specific tax fields
You use the Import SAP Tax Metadata Translations data import task to define preferred supplier levels. The task
reads from a CSV file that includes the following fields:
Field Description
Name The translated name of the tax field that you want to display.
UniqueName The unique identifier for the country-specific tax field, which
must be one of the values you defined in
SapTaxMetadata.csv.
The following example shows lines of the country-specific tax field translation file, as well as the mandatory header:
UTF-8
DE0,Umsatzsteuer-Identifikationsnummer,German
FR0,Numéro d'Enregistrement de la TVA,French

Related Information
Automatically validating question answers [page 258]

Collecting supplier tax information using Tax questions [page 254]
Defining country-specific bank ID prefixes for Bank Account

questions
You can define the country-specific bank ID prefixes used in automatically generated bank IDs for the banks
suppliers add as answers to Bank Account questions using a data import task in Ariba Administrator.
If SM-9657 is enabled in your site, SAP Ariba automatically generates unique, sequential IDs for each of a supplier's
banks. These IDs are unique per supplier but not across suppliers. Bank Account questions include a Country
dropdown menu that allows suppliers to specify the country in which the bank is located. Automatically generated
bank IDs consist of sequential numerical values and, optionally, a country-specific prefix. Defining country-specific
prefixes allows you to create bank IDs that are unique per bank and per country or per currency using the same ID
format as the integrated ERP system. For example, you can define a prefix of EUR for all European Union countries.
Country-specific bank prefixes are optional. If you do not define them in your site, SAP Ariba generates sequential
numerical bank IDs with a maximum length defined by the site configuration parameter
Application.SM.BankIdSize. For example, if the maximum length is 4 and you do not define country-specific
prefixes, SAP Ariba generates sequential, numerical bank IDs starting at 0000 up to a maximum of 9999.
You use the Import Country-Specific Bank ID Prefix data import task to define country-specific bank ID prefixes.
This task reads from the BankIdMetadata.csv file, which includes the following fields:
Field Description
CountryCode The country code to which the tax ID applies. The country code
you specify must match the country code master data loaded
for your site.

Field Description
Prefix The country-specific prefix.
The length of the values you specify in this field depends on the
maximum length for bank IDs specified in your site using the
configuration parameter Define the length of supplier bank
IDs (Application.SM.BankIdSize). The maximum
value of this parameter is 4 characters, but your site might use
a smaller maximum. All of the prefixes you define must be at
least one character shorter than the maximum bank ID
length defined in your site so that bank IDs include at least
one number. Use the same character length for all of the pre
fixes you define to produce standard bank IDs.
SAP Ariba generates bank IDs by prepending the country-spe

cific prefix to a number determined by the number of charac
ters in the prefix and the maximum bank ID size, starting with a
number from 0 to 0001 and ending with 9 to 0009. Where pre
vious bank IDs exist for the supplier and country or countries,
the automatically generated bank ID uses the next number in
sequence.
For example, if your maximum bank ID size is 4 characters and

you use 3-character prefixes, and you define a prefix of EUR,
the first bank that a supplier adds for a country that uses that
prefix receives an ID of EUR0, the second bank receives an ID
of EUR1, and so on.
 Note
● You can define the same prefix for multiple countries. For
example, if multiple countries use the same currency, and
your bank ID prefixes are based on currency, you can de
fine the same currency prefix for all of the countries that
use it. For example, if your maximum bank ID size is 4 and
you assign all of the countries in the European Union a
prefix of EUR, SAP Ariba can generate 10 bank IDs for all
supplier banks in the European Union using the EUR prefix
(EURO - EUR9).
● Once a supplier has reached the maximum number of
unique bank IDs that SAP Ariba can generate for a prefix,
based on prefix length and maximum bank ID length, sub
sequent IDs default to numbers only. These strictly-nu
merical IDs are unique per supplier but not per country.
For example, if your maximum bank ID size is 4, your pre
fixes are 3 characters, and you assign all of the countries
in the European Union a prefix of EUR, but a supplier has
more than 10 banks in the European Union, SAP Ariba as
signs the 11th bank the next sequential 4-number ID in

Field Description
stead. For example, if all of the supplier's other bank IDs

use country-specific prefixes until they add the 11th Euro
pean Union bank, SAP Ariba assigns that bank an ID of
0001. If the supplier then adds an 11th bank in the United
States (prefix USD), SAP Ariba assigns that bank an ID of
0002, and so on.
The following example shows lines of the BankIdMetadata.csv file, as well as the mandatory header:
UTF-8
CountryCode,Prefix
US,USD
DE,EUR
JP,JPY
Related Information
Define the length of supplier bank IDs [page 519]

Collecting supplier bank information using Bank Account questions [page 251]
Topics about defining country-specific validations for

supplier bank account information
Defining country-specific bank control keys in Bank Account questions [page 54]
Defining country-specific syntax for supplier bank account IBAN numbers [page 56]
Defining country-specific syntax validation for supplier bank account holder name, account number, and bank
key or ABA routing number [page 58]
Defining country-specific bank control keys in Bank Account

questions
You can define custom, country-specific bank control keys that respondents see in the Bank Control Key
dropdown menu in Bank Account questions using a data import task in Ariba Administrator. By default, the
dropdown menu includes values defined by default master data.
A bank control key specifies the type of the supplier bank account, such as savings or checking. Different countries
can have different bank control keys. In sites where the bank account syntax validation feature (SM-9656) is
enabled, a Bank Control Key field replaces the previous Bank Account Type field in Bank Account questions.
Bank Account questions in supplier management questionnaires also include a Country field for the bank address.
Once a respondent has chosen a country, the Bank Control Key dropdown menu shows the bank control keys

defined in your site's master data in the format ControlKeyDesc [ControlKeyCode]. In sites that are integrated
with an SAP ERP system, integration errors can occur when a supplier synchronized to the ERP system has an
invalid bank control key. Importing the bank control key values used by the ERP system in SAP Ariba helps avoid
this issue.
Bank control key data import tasks are only available in sites where the bank account syntax validation feature
(SM-9656) is enabled. This feature includes default bank control key master data [page 409], but no default
translation data. The functionality associated with this feature also requires the bank component feature
(SM-5590).
Defining country-specific bank control keys
You use the Import Country-Specific Bank Control Key data import task to define custom bank control keys. The
task reads from the BankControlKeyMetadata.csv file, which includes the following fields:
ControlKeyCode The code associated with the bank con Yes

trol key.
ControlKeyDesc Descriptive text for the bank control key. Yes

You can define translations for these de
scriptions in a separate translation mas
ter data file.
CountryCode The country code to which the bank con Yes

trol key applies. The country code you
specify must match the country code
master data loaded for your site.
UniqueName A unique identifier for the bank control Yes

key.
The following example shows lines of the BankControlKeyMetadata.csv file, as well as the mandatory header:
UTF-8
ControlKeyCode,ControlKeyDesc,CountryCode,UniqueName
Savings,savings account,US,USSavings
Checking,checking account,US,USChecking
Defining translations for country-specific bank control keys
You use the Import Country-Specific Bank Control Key Translations data import task to define translations for
bank control keys. The task reads from a CSV file that includes the following fields:
Field Description
Name The translated name of the bank control key.

Field Description
UniqueName The unique identifier for the country-specific bank control key,
which must be one of the values you defined in
BankControlKeyMetadata.csv.
The following example shows lines of the country-specific bank control key translation file, as well as the
mandatory header:
UTF-8
Cuenta de Cheques,USChecking,Spanish
Cuenta de Ahorros,USSavings,Spanish
Related Information
Syntax validation for supplier bank account information [page 253]

Defining country-specific syntax validation for supplier bank account holder name, account number, and bank key
or ABA routing number [page 58]
Default bank control keys in Bank Account questions [page 409]
Defining country-specific syntax for supplier bank account IBAN

numbers
You can define custom, country-specific syntax for the IBAN answers that respondents provide to Bank Account
questions in supplier management questionnaires using a data import task in Ariba Administrator. Validation
checks prevent respondents from entering answers that do not use the required syntax.
The International Bank Account Number (IBAN) is a system for identifying bank accounts across national borders.
This system uses a specific syntax that includes a country code, check digits, and other bank information. In sites
that are integrated with an SAP ERP system, integration errors can occur when a supplier synchronized to the ERP
system has an IBAN number that does not use the required syntax.
Bank Account questions in supplier management questionnaires include a Country field for the bank address. If
you have defined IBAN syntax, once a respondent has chosen a bank country, SAP Ariba validates the answer in the
IBAN Number field and shows the appropriate error message for invalid answers.
The data import task for IBAN syntax is only available in sites where the bank account syntax validation feature
(SM-9656) is enabled. This feature includes default IBAN syntax master data [page 410]. The functionality
associated with this feature also requires the bank component feature (SM-2936).
You use the Import Country-Specific Bank IBAN fields data import task to define custom IBAN syntax. The task
reads from the BankIBANMetadata.csv file, which includes the following fields:

CountryCode The country code to which the syntax Yes

definition applies. The country code you
IBANFormat The IBAN structure for the country, using Yes

in the following representational conven
tions:
● n to represent numeric characters

(0-9)
● a to represent upper-case alpha
betic characters (A-Z)
● c to represent upper- and lower-
case alphaneumeric characters (a-z,
A-Z, 0-9)
● e to represent blank spaces
● <nn>! to indicate fixed length
● <nn> to indicate maximum length
For example, the following value de

scribes valid IBAN structure for Brazil:
BR2!n8!n5!n10!n1!a1!c. An ex
ample of an IBAN that uses this structure
is
BR9700360305000010009795493
P1.
The IBAN registry document maintained

by ISO describes valid ISO IBAN struc
tures for each country.
IBANLength A numerical value defining the exact Yes

length of the IBAN.
IBANRegex A regular expression that defines the vali Yes

dation pattern for the IBAN structure
specified in the IBANFormat field.
For example, BR\d{25}[A-Z]{1}

[A-Z0-9]{1} specifies that the value
must start with the letters BR, followed
by 25 digits between 1 and 9, followed by
1 upper case letter A-Z, followed by 1 up
per- or lower-case alphaneumeric char
acter a-z, A-Z, or 0-9
The following example shows lines of the BankIBANMetadata.csv file file, as well as the mandatory header:
UTF-8
CountryCode,IBANFormat,IBANLength,IBANRegex

BR,BR2!n8!n5!n10!n1!a1!c,25,BR\d{25}[A-Z]{1}[A-Z0-9]{1}
Related Information

Default syntax for IBAN numbers in Bank Account questions [page 410]
Defining country-specific syntax validation for supplier bank

account holder name, account number, and bank key or ABA routing
number
You can define custom, country-specific syntax validation for the supplier bank account holder name, account
number, and bank key or routing number answers that respondents provide to Bank Account questions in supplier
management questionnaires using a data import task in Ariba Administrator..
Bank Account questions in supplier management questionnaires include a Country field for the bank address.
Once a respondent has chosen a bank country, SAP Ariba validates the answer in the Account Holder Name,
Account Number, and Bank Key/ABA Routing Number fields, and those fields and shows the appropriate error
message if the respondent attempts to submit a questionnaire with invalid values.
The data import task for bank account field validation is only available in sites where the bank account syntax
validation feature (SM-9656) is enabled. The feature includes default syntax master data [page 414] for these
fields. The functionality associated with this feature also requires the bank component feature (SM-2936).
 Note
Default syntax data does not include any validation patterns, only field sizes and, in some cases, check rules. If
syntax validation data includes field sizes and check rules, the system automatically generates validation
patterns from them. In sites integrated with SAP systems, specify field sizes and check rules. In sites that are
not integrated with SAP systems, specify regular expressions for validation patterns instead.
Bank account field validation definitions include fields where you specify which check rule to use during syntax
validation using a number between 1 and 8. These numbers correspond to the following check rules:
● 1: Maximum length, without gaps

● 2: Maximum length, numerical values only, without gaps
● 3: Exact length, without gaps
● 4: Exact length, numerical values only, without gaps
● 5: Maximum length
● 6: Maximum length, numerical
● 7: Exact length

● 8: Exact length, numerical
You use the Import Country-Specific Bank validation fields data import task to define custom, country-specific
syntax validation for supplier bank account holder names, account numbers, and bank key or ABA routing
numbers. The task reads from the BankMetadata.csv file, which includes the following fields:
AccountHolderNameCheckRule A number between 1 and 8 that specifies Yes

which check rule to use for the account
holder name validation..
AccountHolderNameRegex A regular expression that defines the vali Yes

dation pattern for the account holder
name.
AccountHolderNameSize The maximum length allowed for the ac Yes

count holder name value.
AccountNumberCheckRule A number between 1 and 8 that specifies Either AccountNumberCheckRule

which check rule to use for the account and AccountNumberSize or
number validation. AccountNumberRegex are required.
AccountNumberRegex A regular expression that defines the vali Either AccountNumberCheckRule

dation pattern for the account number. and AccountNumberSize or
AccountNumberRegex are required.
If AccountNumberCheckRule and
AccountNumberSize are specified,
the system automatically generates a
regular expression based on those values
and any values in the
AccountNumberRegex field are ig
nored.
AccountNumberSize The maximum length allowed for the ac Either AccountNumberCheckRule
count holder name value. and AccountNumberSize or
AccountNumberRegex are required.
BankKeyCheckRule A number between 1 and 8 that specifies Either BankKeyCheckRule and

which check rule to use for the bank key BankKeySize or BankKeyRegex are
or ABA routing number validation. required.
BankKeyRegex A regular expression that defines the vali Either BankKeyCheckRule and
dation pattern for the bank key or ABA BankKeySize or BankKeyRegex are
routing number. required. If BankKeyCheckRule and
BankKeySize are specified, the sys
tem automatically generates a regular ex
pression based on those values and any
values in the BankKeyRegex field are
ignored.
BankKeySize The maximum length allowed for the ac Either BankKeyCheckRule and
count holder name value, which can be a BankKeySize or BankKeyRegex are
number from 1 to 18. required.


The following example shows lines of the BankValidationMetadata.csv file file, as well as the mandatory
header:
UTF-8
AccountHolderNameCheckRule,AccountHolderNameRegex,AccountHolderNameSize,AccountNumbe
rCheckRule,AccountNumberRegex,AccountNumberSize,BankKeyCheckRule,BankKeyRegex,BankKe
ySize,CountryCode
4,^[0-9]{20}$,20,6,^[0-9\s]{0,20}$,20,1,^[a-zA-Z0-9]{0,30}$,30,DE
3,^[a-zA-Z0-9]{20}$,20,7,^[a-zA-Z0-9\s]{20}$,20,4,^[0-9]{20}$,20,US
Related Information

Defining country-specific ERP region code mappings
You can define custom, country-specific mappings between the custom SAP region codes in Extended Address
questions and the state codes in supplier profile addresses on Ariba Network using a data import task in Ariba
Administrator.
When a supplier is public, meaning that they have an Ariba Network account linked to their site, updates they make
to their Ariba Network profile synchronize to your site. Ariba Network uses in supplier profile addresses. The default
region codes in Extended Address questions are automatically mapped to Ariba Network ISO 3166-2 state codes.
If you import custom SAP region codes from T005S and T005U tables to populate the region field in Extended
Address, you can import country-specific ERP region code mapping master data to maintain mappings between
your custom SAP region codes and Ariba Network state codes and ensure that supplier address information
synchronizes correctly between the integrated ERP system, your SAP Ariba Supplier Management solutions site,
and supplier profiles on Ariba Network. You can also use the master data to add, edit, or remove mappings as your
ERP region data changes.
 Note
Whenever you update SAP region codes in your site, you must use this data import to update their mappings as
well.
SAP Ariba provides a set of default country-specific ERP region code mappings [page 423].
You use the Import Country-Specific ERP Region Code Mappings data import task to define custom country-
specific ERP region code mappings. The task reads from the StateCodeRegionMapping.csv file, which includes
the following fields:
UniqueName A unique identifier for the mapping. Yes


ANStateCode The ISO 3166-2 state code used in Ariba Yes

Network.
ERPRegionCode The ERP region code. Yes
PrevANStateCode The previous state code used for the cur Yes if you are updating a mapping for an
rent mapping, if any. Note that since existing Ariba Network state code. Other
Ariba Network has moved from using wise no.
two- or three-character state codes to
using ISO-3166-2 state codes, the default
mapping data already includes
PrevANStateCode data so that the
state codes associated with suppliers at
the time of that change are mapped to
the correct region code.
PrevERPRegionCode The previous ERP region code used for Yes if you are updating a mapping for an
the current mapping, if any. The data in existing region code. Otherwise no.
this column enables mappings for suppli
ers that were created with the previous
region code.
The following example shows lines of the StateCodeRegionMapping.csv file, as well as the mandatory header:
UTF-8
UniqueName,CountryCode,ANStateCode,ERPRegionCode,PrevANStateCode,PrevERPRegionCode
"anrm_00000077","AU","AU-QLD","QLD","QLD"
"anrm_00000078","BE","BE_WNA","07","WNA"
Related Information
Default country-specific ERP region code mappings [page 423]
Defining country-specific postal code validation for supplier

addresses
You can define custom, country-specific syntax for the postal codes that respondents provide in Address and
Extended Address questions in supplier management questionnaires using a data import task in Ariba
Administrator. Validation checks prevent respondents from entering answers that do not use the required syntax.
Address and Extended Address questions in supplier management questionnaires include a Country field. Once a
respondent has chosen a bank country, SAP Ariba validates the answer in the address postal code field and shows
the appropriate error message for invalid answers.

 Note
● Postal code validation based on configurable master data is only available in sites that use the new supplier
360° profile (SM-14322) and the enhanced supplier request (SM-15774). Sites that do not meet these
prerequisites use static, SAP Ariba-defined postal code validation.
● There might be a short delay between when you import postal code validation data and when those
validations take effect in supplier management questionnaires.
You use theImport Country-Specific Postal Code Validations data import task to define postal code validations.
The task reads from a ZipCodeValidationMetaData.csv file, which includes the following fields:
Country The name of the country to which the Yes

syntax definition applies.

ISO The two-digit ISO country code to which Yes

the syntax definition applies.
Note An optional note or explanatory informa No

tion about the syntax definition.
Regex One or more regular expressions that de No

fine the validation patterns for the postal
code structure specified in the
ZipFormat field. To define multiple val
idation patterns, separate the regular ex
pression for each pattern with a pipe
character (|).
For example, the following regular ex

pressions specify that the value must in
clude either 5 digits between 1 and 9, or 5
digits between 1 and 9, followed by a
dash, followed by 4 digits between 1 and
9: ^(^\d{5})$|^(\d{5}-\d{4}$)
$.

ZipFormat For countries that have a single postal No
code, the value of that postal code. For

countries that have multiple postal co
des, one or more postal code structures
for the country, using in the following rep
resentational conventions:
● N to represent numeric characters

(0-9)
A to represent upper-case alpha
betic characters (A-Z)
C to represent upper- and lower-
case alphanumeric characters (a-z,
A-Z, 0-9)
● (!value1|value2) to indicate
required value 1 or required value 2
● [value] to indicate optional val
ues
● [value1/value2] to indicate
optional value 2 or optional value 2
To define multiple postal code structures,

separate each structure with a comma (,)
and a space and enclose the entire value
with quotation marks.
For example, the following values de

scribe the valid postal code structures for
the United Status: "NNNNN, NNNNN-
NNNN". The following values describe
the valid postal code structure for Great
Britain: A[A]N[A/N] NAA. The follow
ing value is the postal code used for all
addresses in Anguilla: AI-2640.
e following example shows lines of the ZipCodeValidationMetaData.csv file, as well as the mandatory header:
UTF-8
Country,CountryCode,ISO,Note,Regex,ZipFormat
United States,US,US,,^(^\d{5})$|^(\d{5}-\d{4}$)$,NNNNN, NNNNN-NNNN
U.S. Virgin Islands,VI,VI,U.S. ZIP codes. Range 00801 - 00851.,^(^\d{5})$|^(\d{5}-
\d{4}$)$,NNNNN, NNNNN-NNNN
Saudi Arabia,SA,SA,NNNNN for PO Boxes. NNNNN-NNNN for home delivery.,^(^\d{5}-\d{4})
$|^(\d{5}$)$,NNNNN-NNNN, NNNNN
Related Information
Default syntax validation for postal codes in supplier addresses [page 504]

Defining mappings between guided buying ship-to
addresses and preferred and qualified supplier regions
The guided buying capability in SAP Ariba Buying solutions uses the standard 2-character ISO country codes in
ship-to addresses, but suppliers are preferred or qualified based on region code master data in your site. Mapping
between these codes allows guided buying searches locate the correct preferred and qualified suppliers.
When a user in the guided buying capability in SAP Ariba Buying solutions searches for goods or services, the
search uses the standard 2-character ISO country codes in their ship-to addresses to identify and filter search
results based on qualified and preferred suppliers. However, suppliers are preferred or qualified based on the region
codes defined by the Import Region Codes data import task in Manage Administration Site Manager
Data Import Export .
If the configurable mapping feature (SM-20598) is enabled in your site, you use a separate Import Country Code
to Sourcing Region Code Mapping data import task to define mappings between the 2-character ISO country
codes used in guided buying and the region codes your site uses to identify preferred and qualified suppliers. If the
configurable mapping feature is not enabled, SAP Ariba maps guided buying country codes to a standard list of ISO
3-chacter region codes. The configurable mapping feature (SM-20598) is suitable for sites that do not use
standard ISO 3-charcter region codes, and that therefore need to define mappings between guided buying country
codes and their own region code master data.
 Note
To use this mapping master data in guided buying searches, you must also enable the parameter
ENABLE_SM_INTEGRATION_ON_COUNTRYCODE in Admin Parameters Manage parameters .
You use the Import Country Code to Sourcing Region Code Mapping data import task to define mappings
between the 2-character ISO country codes used in guided buying supplier locations and the region code master
data used for preferred and qualified suppliers. The task reads from the
CountryToSourcingRegionMapping.csv file, which includes the following fields:
CountryCode One of the 2-character ISO country co Yes

des you use for supplier locations in
guided buying.
SourcingRegionCode The region code to which you want to Yes

map the country code. The value in this
field must be a valid value in the Region
field of the region master data loaded in
your SAP Ariba Strategic Sourcing solu
tions site.
The following example shows lines of the CountryToSourcingRegionMapping.csv file, as well as the
mandatory header:
UTF-8
CountryCode,SourcingRegionCode
US,USA
JP,Japan
GB,UK

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

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 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 supplier management
master data:
● BrazilianPortuguese
● Bulgarian
● Croatian
● Czech
● Danish
● Dutch
● English
● Finnish
● French
● German
● Greek
● Hungarian
● Italian
● Japanese
● Korean
● Norwegian
● Polish
● Romanian
● Russian
● SimplifiedChinese
● Spanish
● Swedish
● Thai
● TraditionalChinese
● Turkish
Topics about importing supplier-related data in SM

Administration
About importing supplier-related data for supplier management [page 68]
How to obtain existing SAP Ariba supplier data [page 70]
How to import supplier data [page 71]
Supplier data file format [page 74]
Supplier contact data file format [page 79]
Supplier qualification data file format [page 82]

Preferred supplier data file format [page 86]
Supplier factory data file format [page 89]
Purchasing organization data file format [page 93]
Custom display name data file format [page 94]
Primary supplier manager data file format [page 96]
User matrix (buyer category assignment) data file format [page 98]
Internal supplier registration data file format [page 102]
About importing supplier-related data for supplier

management
Supplier-related data defines the suppliers and supplier contacts in your site as well as their characteristics, such
as qualified or preferred status. You import supplier-related data using the Data import or export task in SM
Administration.
In sites that include SAP Ariba Supplier Lifecycle and Performance or SAP Ariba Supplier Information and
Performance Management (new architecture), you always import supplier-related data in SM Administration.
SAP Ariba Supplier Lifecycle and Performance and SAP Ariba Supplier Information and Performance Management
(new architecture) use the following types of supplier data:
This supplier data... Defines...
Supplier data [page 74] The suppliers in your site.
Supplier contact data [page 79] The contacts for your suppliers. Any supplier management ac
tivity that involves an external (supplier-facing) questionnaire
requires that the supplier have at least one contact defined for
it either through this data import or manually in the supplier
360° profile.
Supplier qualification data [page 82] Qualification and disqualification statuses for your suppliers.
In sites that include SAP Ariba Supplier Lifecycle and Perform

ance, category or supplier managers can manage supplier
qualifications and disqualifications using projects that include
questionnaires and approvals. They can disqualify qualifica-
tions defined by this data import, requalify disqualifications de
fined by this import, and so forth.
In sites that include SAP Ariba Supplier Information and Per

formance Management (new architecture), customer adminis
trators can set qualification and disqualification status through
data import, but qualification and disqualification projects are
not available.

This supplier data... Defines...
Preferred supplier data [page 86] Preferred supplier levels (category preferred status) for your
suppliers.
In sites that include SAP Ariba Supplier Lifecycle and Perform

ance, category or supplier managers can manage supplier pre
ferred levels using preferred supplier management projects
that include questionnaires and approvals. They edit the pre
ferred supplier levels defined by this data import using those
projects.
In sites that include SAP Ariba Supplier Information and Per

formance Management (new architecture), customer adminis
trators can set preferred levels through data import, but prefer
red supplier management projects are not available.
Supplier purchasing organization data [page 93] The purchasing organizations associated with your suppliers.
This data is used only in the guided buying capability in SAP

Ariba Buying solutions. For details, see Guided buying adminis
tration.
Custom display name data [page 94] The custom labels you specify for registration and qualification
statuses. Only buyer user can view the custom display labels.
Primary supplier manager data [page 96] The primary supplier managers for your suppliers. Primary
supplier managers are internal users who are familiar with or
responsible for particular suppliers. In sites that use modular
supplier management questionnaires, primary supplier man
agers might receive notifications related to questionnaire expi
rations.
User matrix (buyer category assignment) data [page 98] Assignments of internal users or global system groups to spe
cific project groups in supplier management projects for spe
cific combinations of commodity, region, and department.
Internal supplier registration data [page 102] Unregistered suppliers that you want to designate as internally
registered.
You can download samples of all supplier-related data files from the Imports/Exports area of SM Administration.
On the dashboard, click Manage SM Administration to access this area.
 Note
The sample files you download include a column for supplier name, which is included in exported data for
reference only. Do not include it in the data files you import. The exceptions to this rule are the name1 through
name4 columns in the file you import using the Suppliers data import task. Those columns must be included in
the imported file.

How to obtain existing SAP Ariba supplier data
If you already have an SAP Ariba solution, you need to add your existing suppliers to the supplier database.
Obtaining existing SAP 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 SAP Ariba supplier data is exported in a SupplierOrganizationExport.zip 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.
 Caution
If you are migrating your existing supplier organizations and supplier profile questionnaires to the unified
vendor model and supplier registration questionnaires, see Migrating supplier organizations to the unified
vendor model before you attempt to import existing SAP Ariba supplier data in SM Administration. That guide
contains important information about how to migrate suppliers with the correct ERP vendor IDs and address
state information, as well as detailed information about how migration works and the order in which you should
perform migration steps.
Procedure
1. Perform one of the following actions:
○ If your site includes SAP Ariba Procurement solutions, on the dashboard, click Manage Core
Administration .
○ If your site does not include SAP Ariba Procurement solutions, on 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 SAP Ariba suppliers from your site, you import them into the supplier database [page
71].
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 Administration.
 Note
For customers who use guided buying, you must belong to both the Supplier/Customer Manager and SM Ops
Admin groups.
If you are not importing suppliers for guided buying and your site includes existing SAP Ariba solutions with
supplier data, you must first obtain that data before importing it.
The suppliers referenced by supplier data files, such as supplier contacts 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 and preferred
supplier list data, which offer an option to create the suppliers referenced in the file if they do not already exist.
However, if you are importing supplier data in SAP Ariba Supplier Management solutions, the data in those files is
very limited and importing supplier data first is strongly recommended.
Context
You must import all supplier data for suppliers exported from SAP Ariba cloud solutions in CSV files. There is no
restriction on file naming. Supplier data import supports the following encoding types for CSV files:
● UTF-8
● US ASCII
● ISO-8859-1
● IUTF-16BE
● UTF-16LE
● UTF-16
Unless otherwise specified, all supplier data imports add new records and update existing records. For example, if
you import supplier data with a new ERP vendor ID, the import operation adds the new supplier record to the
database. If you import supplier data with an existing ERP vendor ID and source system, but with a change to some

other data such as a different address, the import operation updates the existing supplier record with the new
address. If a data file contains an existing record with no changes, the import operation ignores that record.
Procedure
1. From the dashboard, navigate to SM Administration. Available paths depend on the groups to which your user
belongs.
○ In sites that include SM Administration, members of the SM Ops Administrator, SM ERP Admin, or
Customer Administrator group can select Manage SM Administration .
○ Members of the Supplier Risk Manager group can access SM Administration from the SAP Ariba
Supplier Risk dashboard: click the settings icon (), then choose Import data Link to SM admin .
2. Click Data import or export.
3. On the Import tab, choose the type of data you want to import from the File type 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 in a CSV file.
Supplier from Sourcing Suppliers exported from SAP Ariba cloud solutions in
SupplierOrganizationExport.zip. Only import
the SupplierOrganizationExport.zip file using
this task. Do not import the CSV files it contains individually.
 Caution
Only use this data import task to migrate existing sup
plier organizations from another SAP Ariba solution.
There is important information that you must be aware
of about how to migrate suppliers with the correct ERP
vendor IDs and address state information before you
use this task. If you are:
○ Adding suppliers from an existing SAP Ariba solu
tion to SAP Ariba Supplier Risk without SAP Ariba
Supplier Lifecycle and Performance or SAP Ariba
Supplier Information and Performance Manage
ment (new architecture), see the topics on migrat
ing supplier organizations to the unified vendor
model in the setup guide.
○ Migrating suppliers and supplier profiles from an
existing SAP Ariba solution to SAP Ariba Supplier
Lifecycle and Performance or SAP Ariba Supplier
Information and Performance Management (new
architecture), see Migrating suppliers to the unified
vendor model. That guide also contains important
information about the order in which to perform

This data type... Imports...
various migration steps, including this data import,

as well as other migration requirements.
Supplier contacts Supplier contacts in a CSV file.
Supplier qualification data A list of supplier qualifications by commodity and code and
region in a CSV file.
Preferred supplier list data A list of preferred suppliers by commodity code and region in
a CSV file.
Supplier factory data Information about supplier factories in a CSV file.
Purchasing organization data The purchasing organizations associated with the supplier,
including defaults, in a CSV file.
Custom display names Custom labels for registration and qualification statuses in a
CSV file.
Primary supplier manager The names of primary internal contacts for suppliers in a
CSV file.
User Matrix User assignments to commodities, regions, and supplier

management project groups in a CSV file.
Supplier Risk Data Risk data for suppliers in SAP Ariba Supplier Risk.
4. (Optional) For supplier qualification data or preferred supplier list data, check Create supplier if required to
add any suppliers in the data that don't already exist to the database.
If you use this option, the preferred of qualified suppliers are created in the database with SM IDs but no
names. To display them correctly in the user interface, you must import complete data for them using the
Suppliers or Suppliers from sourcing data import option, specifying those SM IDs in the supplier data files.
Importing the suppliers first, rather than creating them from the preferred or qualified supplier data, is
recommended.
5. Click Choose File and navigate to the file you want to import.
6. Choose the encoding that the data file you want to import uses from the Encoding Type dropdown menu.
7. Click Import.
Next Steps
Click the Import summary tab to view the status of your data import. If your import contains any errors, click the
View link to the right of the number of errors in the import to see or download error messages.
 Tip
If you are using Microsoft Internet Explorer and you do not see any information in the Status column of the
Import Summary tab, adjust the document mode compatibility setting of your browser. To do so, right click

anywhere in the browser window and choose Inspect element to display the inspection pane at the bottom of
the browser window. Click the Emulation tab, choose 10 from the Document Mode dropdown menu, and close
the inspection pane.
Related Information
How to obtain existing SAP Ariba supplier data [page 70]

Supplier data file format [page 74]
Supplier contact data file format [page 79]
Preferred supplier data file format [page 86]
Supplier factory data file format [page 89]
Purchasing organization data file format [page 93]
Supplier risk data import file format
Topics about configuring risk exposure
How to manually migrate supplier organization data
Supplier data file format

Importing supplier data creates suppliers in the database.
You use the Suppliers data import task to import suppliers into your site. The task reads from a CSV file that
contains the following fields:
Field Description Required? Maximum field length
erpVendorId The ID of the supplier in the in Yes 50

tegrated ERP system.
(SAP ERP maximum field
length is 10)

smVendorId The ID that SAP Ariba assigns Yes, to update the

to the supplier. The value in erpVendorId. Otherwise
this field must be an existing no.
SM vendor ID.
If you import a supplier record

with an existing
smVendorId but a new
erpVendorId value, the da
tabase updates the existing
supplier record with the new
erpVendorId. The new
erpVendorId must be
unique; it cannot match an ex
isting supplier record. You can
only update ERP vendor IDs
for suppliers that are in Not
Integrated or In Process inte
gration status or whose initial
integration is in an error state.
masterVendorId Not currently used. No 255
sourceSystem The system in which the sup Yes 255

plier was created; for example,
SM for SAP Ariba or SAP for
SAP ERP.
name1 The primary name of the sup Yes 125

plier.
length is 35)
name2 An alternate name for the sup No 125

plier.
length is 35)
name3 A second alternate name for No 125

the supplier.
length is 35)
name4 A third alternate name for the No 125

supplier.
length is 35)
phone The supplier phone number. No 40
fax The supplier fax number. No 40

line1 The first line of the supplier At least one of the following 255
address. fields is required: line1,
line2, line3, city,
state, postalCode, or
countryCode
line2 The second line of the supplier At least one of the following 255
line2, line3, city,
countryCode
line3 The third line of the supplier At least one of the following 255
line2, line3, city,
countryCode
postalCode The postal code of the sup At least one of the following 10
plier address. fields is required: line1,
line2, line3, city,
countryCode
poBox The post office box number of No 10

the supplier address.
city The city of the supplier ad At least one of the following 40
dress. fields is required: line1,
line2, line3, city,
countryCode
state The state or province of the At least one of the following 6

supplier address. fields is required: line1,
line2, line3, city,
countryCode

stateName The state of the migrated sup No. This field is ignored in sup
plier organization from the or plier data imports.
ganization stateName field.
This field is included in sup

plier data exports for informa
tional purposes, and is there
fore also included in the sup
plier data sample file. How
ever, it only includes data from
migrated supplier organiza
tions if the Suppliers from
sourcing data import task
uses the Consider State as
State Nameoption. For details
on this option, see Migrating
supplier organizations to the
unified vendor model.
This field's presence in sup

plier data imports is not re
quired. If you re-import a pre
viously exported file, do not
edit or delete the values in
this column.
countryCode The two-character ISO coun At least one of the following 3 (minimum is 2)
try code of the country for the fields is required: line1,
supplier address. line2, line3, city,
countryCode.
Either
taxIdentificationNum
berTypeCode or
countryCode is required.
countryCode is required
for country enrichment in SAP
Ariba Supplier Risk solutions.

taxIdentificationNum A code that identifies the type Either 2

berTypeCode of the tax identification num taxIdentificationNum
ber. berTypeCode or
countryCode is required. If
you specify partyTaxID,
taxIdentificationNum
berTypeCode is also re
quired.
partyTaxID The supplier party tax ID. No 20
longPartyTaxID The long format of the sup No 60

plier party tax ID.
dunsId The supplier Dun & Bradstreet No 11

D-U-N-S number.
active Whether the supplier descri No

bed by the current row is ac
tive (TRUE) or inactive
(FALSE). If this field is empty,
the row is flagged as active.
s4OrgSystemId Used internally only. Migrated No

suppliers always include an
s4OrgSystemId.
This field is included in sup

plier data exports for informa
tional purposes, and is there
fore also included in the sup
plier data sample file. How
ever, it is only used internally
by SAP Ariba. This field's pres
ence in supplier data imports
is not required. If you re-im
port a previously exported
file, do not edit or delete the
values in this column.
Unless otherwise indicated, the minimum length of required fields is 1. In sites integrated with SAP ERP, data sent
to SAP ERP is truncated based on the SAP ERP maximum field length.
The following example shows lines of a supplier CSV file, as well as the mandatory header:
erpVendorId,masterVendorId,sourceSystem,name1,name2,name3,name4,phone,fax,line1,line
2,line3,postalCode,poBox,city,state,stateName,countryCode,taxIdentificationNumberTyp
eCode,partyTaxID,longPartyTaxID,dunsId,active,s4OrgSystemId

VDR100001,,SAP,ABC Company,,,,555-555-5555,555-555-5556,1234 Main Street,,,
12345,,Anytown,CA,,USA,02,AB1234,ABCD12345678910,987654321,TRUE,,
Related Information
How imported supplier data affects risk corporate enrichment
Supplier contact data file format

Supplier contacts are the supplier employees with whom your company interacts, and the primary contact receives
questionnaires by default.
To specify multiple contacts for the same supplier, add a unique row for each contact.
You use the Supplier Contacts data import task to add supplier contacts to suppliers. It reads from a CSV file that
erpVendorId The ID of the supplier in the integrated Yes

ERP system.
supplierName The name of the supplier. Supplier con No

tact data exports include this field for in
formational purposes, and it is therefore
also included in the supplier contact
sample data file. This field's presence in
supplier contact data imports is not re
quired. In imports, erpVendorId asso
ciates a contact with a supplier and
supplierName is ignored.
sourceSystem The system in which the supplier was Yes

created; for example, SM for SAP Ariba or
SAP for SAP ERP.
firstName The first name of the supplier contact. No
middleName The middle name of the supplier contact. No
lastName The last name of the supplier contact. No

countryCode The country code of the supplier con No

tact's land line telephone number. SAP
Ariba Supplier Management solutions
automatically insert a plus sign (+) be
fore the country code in user interface
display.
telephone The supplier contact's land line tele No

phone number.
mobileCountryCode The country code of the supplier con No

tact's mobile telephone number. SAP
Ariba Supplier Management solutions
automatically insert a plus sign (+) be
fore of the country code in user interface
display
mobilePhone The supplier contact's mobile telephone No

number.
email The supplier contact's email address, Yes

which is the default username for sup
plier contacts created via data import
(the supplier contact can edit their user
name on Ariba Network). The email ad
dress must be unique; two different sup
plier contacts cannot have the same
email address.
type The type of the supplier contact, which No

must match one of the types defined for
your site.
locale The ISO code for the supplier contact's No

language.
title The supplier contact's title. No
categories The commodities for which the supplier No

contact is responsible.
 Note
This code must match the commod
ity master data loaded in your SAP
Ariba Strategic Sourcing solutions
site.

regions The regions for which the supplier con No

tact is responsible.
 Note
This code must match the region
master data loaded in your SAP
site.
active A Boolean value that specifies whether No

the assignment described by the current
row is active (TRUE) or deactivated
(FALSE). If this field is empty, the row is
flagged as active. Deactivated contacts
are removed from the supplier.
timeZoneID The ID of the timezone where the sup No

plier contact is located. To obtain a list of
valid timezone IDs, in the Data import or
export area of SM Administration,
choose Supplier contacts from the File
type dropdown menu, then click Export
available time zones.
isPrimary A Boolean value that specifies whether or Yes

not the supplier contact is the primary
contact for the supplier. Valid values are
TRUE and FALSE.
If none of a supplier's contacts are desig

nated the primary contact, the first con
tact for the supplier in the file becomes
the primary contact.
If more than one of a supplier's contacts

is designated the primary contact, the
last contact for the supplier that is desig
nated as primary in the file becomes the
primary contact.
The following example shows lines of a supplier contact CSV file, as well as the mandatory header:
erpVendorId,firstName,middleName,lastName,countryCode,telephone,mobileCountryCode,mo
bilePhone,email,type,locale,title,categories,region,active,timeZoneID,isPrimary
VND123456,Francine,Marie,Peugot,33,555-555-5555,,,[email protected],,fr,,
4213,FRA,TRUE,Europe/Paris,TRUE

Supplier qualification data file format
Supplier qualification data is used to designate the suppliers qualified for specific categories and regions in the
guided buying feature for SAP Ariba Buying and Invoicing, and for supplier qualifications that were achieved
outside of SAP Ariba Supplier Lifecycle and Performance.
You use the Supplier qualification data data import task to designate qualified suppliers. The task reads from a
CSV file that contains the following fields:
sourceSystem For existing SAP 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. The
not, use SM. supplier is added with the default SM
source system.
For suppliers imported from outside SAP
Ariba, use the sourceSystem speci
fied in Supplier.csv.
vendorId For existing SAP Ariba suppliers, if the Yes

tains a Domain and Value entry for the
supplier, use the Value in this field. If
not, use the Parent.SystemID.

Ariba, use the erpVendorId specified
in Supplier.csv.
category The commodity code ID for which qualifi- Yes

cation status applies.
 Note
site.

region The code for the region in which the qual Yes
ification status applies. This code must
match the region master data loaded in
your site.
 Note
If your organization uses guided buy
ing, SAP Ariba maps country codes
in guided buying user ship-to ad
dresses to a standard list of ISO 3-
chacter region codes used for quali
fied and preferred supplier statuses.
If you use other region codes, you
must define custom mappings [page
64] between guided buying country
codes and preferred and qualified
supplier region codes.
 Tip
If you are a guided buying customer,
make sure that users have a match
ing ship-to country in the user files in
SAP Ariba Procurement solutions.
businessUnit The department ID for which the qualifi- Yes

cation status applies.
 Note
This code must match the depart
ment master data loaded in your
SAP Ariba Strategic Sourcing solu
tions site.
This field is only used if the business unit

matrix enhancement feature is enabled
in your site. If it is not, leave it blank.

status The supplier's qualification status. The Yes

following are valid status values:
● NotQualified
● QualificationStarted
● InQualification
● PendingQualificationAppr
oval
● PendingResubmit
● QualificationRestricted
● QualificationRejected
● Disqualified
● Qualified
● Expired
● Cancelled
If you use display mappings to customize

what statuses are called in your site, you
must still use these values to import sup
plier qualification data.
 Note
A status of Cancelled deactivates
the qualification and removes it from
the supplier's 360° profile and from
search results. You can use this sta
tus to remove any qualification that
was created using a data import. You
cannot use it to remove qualifica-
tions with associated qualification
projects. To cancel a project-based
qualification, see How to cancel a
qualification project that is in prog
ress [page 370].
startDate The date from which the supplier qualifi- No

cation status is valid for the specified
commodity and region, in the format
YYYY-MM-DD. This date is for informa
tional purposes only and does not trigger
an automatic change of qualification sta
tus

endDate The date to which the supplier qualifica- No

tion status is valid for the specified com
modity and region, in the format YYYY-
MM-DD. This date is for informational
purposes only and does not trigger an
automatic change of qualification status
name1 The name of the supplier. Yes if you use the Create supplier if
required option during data import to
create suppliers based on the data in this
file. Otherwise No.
requalificationEligibleDate The date from which a supplier with a No

disqualification or expired qualification is
eligible for requalification for the speci
fied commodity and region, in the format
YYYY-MM-DD. This date is for informa
tional purposes only and does not trigger
an automatic change of qualification sta
tus.
To specify the same supplier as qualified for multiple categories or regions, add a unique row for each combination
of category, region, and supplier.
The following example shows lines of a supplier qualification CSV file, as well as the mandatory header:
sourceSystem,vendorId,category,region,businessUnit,status,startDate,endDate,name1,re
qualificationEligibleDate
SAP,VDR1000001,1412,USA,IT,Qualified,2017-02-01,2018-01-31,ABC Company,
SAP,VDR1000002,14,USA,HR,Disqualified,2017-02-01,2017-12-31,XYZ Company,2018-01-01
 Note
In sites that include SAP Ariba Supplier Lifecycle and Performance, you can set qualification statuses for a
supplier using either qualification data import or qualification and disqualification projects. SAP Ariba Supplier
Lifecycle and Performance is designed to maintain qualifications over the long term using projects. Imported
qualifications do not have associated qualification or disqualification projects. Keep in mind the following
behavior for imported qualifications:
● If a qualification status was set using an approved qualification or disqualification project, you cannot use
data import to update it. If a supplier was qualified using a qualification project, you must disqualify them
using a disqualification project. If a supplier was disqualified using a disqualification project, you must
requalify them using a qualification project. If a supplier was qualified using a qualification project with an
expiration date and that qualification has expired, you must requalify them using a qualification project.
● If a qualification status was set using data import, you can use a qualification or disqualification project to
update it. In this case, a category or supplier manager can start a disqualification or requalification in the
supplier 360° profile. SAP Ariba Supplier Lifecycle and Performance then creates the appropriate
qualification or disqualification project based on the imported qualification commodities, regions, and
departments. Once that project is created, you continue managing the qualification status using projects..

● The qualification end (expiration) and requalification eligibility dates in qualification data import are for
information only and do not trigger updates to qualification status. For example, if you use data import to
define qualified status with an end date of 1/31/2019, the qualification status does not change to expired
on 2/1/2019. Since there was no underlying qualification project to set the status, you cannot start a
project-based requalification for a qualification that you defined using data import and that has since
passed the expiration date. The qualification retains the original qualified status unless you update it using
another data import.
Related Information

Defining mappings between guided buying ship-to addresses and preferred and qualified supplier regions [page
64]
Preferred supplier data file format

Preferred supplier data is used to designate preferred suppliers in the guided buying feature for SAP Ariba Buying
and SAP Ariba Buying and Invoicing and in SAP Ariba Supplier Risk, and for suppliers that were created outside of
SAP Ariba in SAP Ariba Supplier Lifecycle and Performance.
To specify the same supplier as preferred for multiple categories, add a unique row for each combination of
category and supplier.
You import data about your list of preferred suppliers using the Preferred Supplier list data file type and a CSV file
that contains the following fields:
sourceSystem For existing SAP Ariba suppliers, if the Yes

supplier, use the Domain in this field. If
not, use SM.




in Supplier.csv.
category The commodity code ID for which the Yes

supplier is preferred.
 Note
site.
region The code for the region in which the sup Yes
plier is preferred. This code must match
the region master data loaded in your
site.
 Note
If your organization uses guided buy
ing, SAP Ariba maps country codes
in guided buying user ship-to ad
dresses to a standard list of ISO 3-
chacter region codes used for quali
fied and preferred supplier statuses.
If you use other region codes, you
must define custom mappings [page
64] between guided buying country
codes and preferred and qualified
supplier region codes.
 Tip
If you are a guided buying customer,
make sure that users have a match
ing ship-to country in the user files in
SAP Ariba Procurement solutions.

businessUnit The department ID for which the prefer Yes

red status applies.
 Note
This code must match the depart
ment master data loaded in your
SAP Ariba Strategic Sourcing solu
tions site.
This field is only used if the business unit

matrix enhancement feature is enabled
in your site. If it is not, leave it blank.
startDate The date from which the supplier is pre No

ferred for the specified commodity and
region, in the format YYYY-MM-DD.
endDate The date to which the supplier is prefer No

red for the specified commodity and re
gion, in the format YYYY-MM-DD.
level The supplier's preferred status level. Yes
This status level must be one of the

UniqueName values in the master data
used to define preferred supplier levels in
your site.
active A Boolean value that specifies whether

the preferred supplier level described by
the current row is active (TRUE) or deac
tivated (FALSE). If this field is empty, the
row is flagged as active.
The following example shows one line of a preferred supplier CSV file, as well as the mandatory header:
sourceSystem,vendorId,category,region,startDate,endDate,level,active
SM,VDR100001,4212,North America,,,1,TRUE
If your company decides to make a different supplier preferred for that category and region instead, an
administrator can make that change by importing a preferred supplier CSV file with the following lines:
sourceSystem,vendorId,category,region,startDate,endDate,level,active
SM,VDR100001,4212,North America,,,1,FALSE
SM,VDR100002,4212,North America,,,1,TRUE

Related Information
Defining preferred supplier levels [page 39]

Defining mappings between guided buying ship-to addresses and preferred and qualified supplier regions [page
64]
Supplier factory data file format
Supplier factory data is used in direct material sourcing.
You import data about your list of preferred suppliers using the Supplier factory data file type and a CSV file that


in Supplier.csv.

not, use SM.

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

tory.
internalQualityManagerEmail The email address of the quality manager No

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

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
qualityAuditValidityStartDa The date from which the quality audit No

te status is valid, in the format YYYY-MM-
DD.
qualityAuditValidityEndDate The date to which the quality audit status No

is valid, in the format YYYY-MM-DD.
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, in the format YYYY-
MM-DD.
complianceAuditValidityEndD The date to which the compliance audit No

ate status is valid, in the format YYYY-MM-
DD.
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, in the format YYYY-MM-DD.
otherAuditValidityEndDate The date to which the other audit status No

is valid, in the format YYYY-MM-DD.

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.
active A Boolean value that specifies whether No

the supplier factory described by the cur
rent row is active (TRUE) or deactivated
(FALSE). If this field is empty, the row is
flagged as active.
Purchasing organization data file format

Your company is divided into various purchasing organizations that do business with your suppliers..
You use the Purchasing organization data data import task to import the purchasing organizations associated
with your suppliers into your site. The task reads from a CSV file that contains the following fields
erpVendorId For existing SAP Ariba suppliers, if the Yes


in Supplier.csv.


not, use SM.

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 partner No

function.
defaultIndicator A Boolean value that indicates whether No

or not the purchasing organization is to
be used as the default.
The following example shows lines of a supplier purchasing organization CSV file, as well as the mandatory header:
erpVendorId,sourceSystem,purchasingOrganisationId,partyRoleCode,partyInternalID,defa
ultIndicator
VDR100001,SAP,1200,BA,DE1005,TRUE
Custom display name data file format

Customizing the labels your site uses for registration and qualification statuses allows you to make sure that they
match your supplier management processes and terminology.
You use the Custom display names data import task to import suppliers into your site. The task reads from a CSV
file that contains the following fields

fieldName The name of the registration, qualifica- Yes

tion, or disqualification status field, in dot
notation. Valid values are:
● Registration.Unknown
● Registration.NotInvited
● Registration.Invited
● Registration.InRegistrat
ion
● Registration.PendingAppr
oval
● Registration.PendingResu
bmit
● Registration.Registered
● Registration.Registratio
nDenied
● Qualification.Unknown
● Qualification.NotQualifi
ed
● Qualification.Qualificat
ionStarted
● Qualification.InQualific
ation
● Qualification.PendingQua
lificationApproval
● Qualification.PendingQua
lificationResubmit
● Qualification.Qualified
ionRejected
● Qualification.InDisquali
fication
● Qualification.PendingDis
qualificationApproval
ionRestricted
● Qualification.Disqualifi
ed
● Qualification.QualifiedW
ithException
● Qualification.Expired

● Disqualification.NotDisq
ualified
● Disqualification.InDisqu
alification
● Disqualification.Pending
DisqualificationApproval
● Disqualification.Restric
ted
● Disqualification.Disqual
ified
locale The ISO code for the language used for Yes
the displayName.
displayName The custom label to use for the registra Yes

tion or qualification status.
The following example shows lines of a custom display name CSV file, as well as the mandatory header:
fieldName,locale,displayName
Registration.Invited,en,Onboarding Started
Restrictions
Only buyer user can view the custom display labels. The supplier user can not view the custom display labels.
Primary supplier manager data file format
Primary supplier managers are the contacts within your company who either interface with or can answer
questions about a supplier.
Primary supplier manger import data format
Primary and alternate supplier managers do not have any role in supplier projects; they are for information only.
You use the Primary supplier manager data import task to import primary supplier managers into your site. The
task reads from a CSV file that contains the following fields:



in Supplier.csv.

not, use SM.

primarySupplierManager The username of the buyer user who is Yes

the primary internal contact for the sup
plier.
The following example shows lines of a primary supplier manager CSV file, as well as the mandatory header:
erpVendorId,sourceSystem,primarySupplrManager
VDR100001,SM,ayang
Primary supplier manager export file fromat
The export CSV file contains the following fields:
Field Description
erpVendorId For existing SAP Ariba suppliers, if the

SupplierOrganizationOrganizationIdPart_Exp
ort.csv file contains a Domain and Value entry for the
supplier, use the Value in this field. If not, use the
Parent.SystemID.
For suppliers imported from outside SAP Ariba, use the

erpVendorId specified in Supplier.csv.

Field Description
sourceSystem For existing SAP Ariba suppliers, if the

SupplierOrganizationOrganizationIdPart_Exp
ort.csv file contains a Domain and Value entry for the
supplier, use the Domain in this field. If not, use SM.
For suppliers imported from outside SAP Ariba, use the

sourceSystem specified in Supplier.csv.
primarySupplierManager The username of the buyer user who is the primary internal
contact for the supplier.
supplierName This field is solely to make the exported data easier to read, by
showing the supplier name alongside the primary supplier
manager data. If the field is present in the file you import (for
example, if you export your current data, update it in the ex
ported file, and import the updated file without removing the
supplierName column), the import will succeed; however,
all data in the supplierName column is ignored in data im
ports
User matrix (buyer category assignment) data file format
Assigning users or global user groups to supplier processes involves importing a CSV file that defines user or group
assignments to commodities, regions, departments, and project groups.
 Note
Assignments to departments are only made in sites with the business unit matrix enhancement feature
enabled. If that feature is not enabled in your site, department data in the user matrix data import file is
ignored.
For example, you can assign the specific user John Smith to computer equipment in North America for the IT
department for the Project Owner project group. The supplier request template adds the Project Owner project
group to the approval flow of all supplier requests. When a user at your company submits a supplier request
indicating that the supplier provides computer equipment in North America for the IT department, John Smith
automatically becomes a member of the Project Owner project group for that request, and therefore becomes an
approver for it.
Or you can create a custom global user group called IT Category Managers and add users John Smith, Susan
Harris, Don Cortez, and Jane Yang to it. You can then assign the group to computer equipment in North America for
the IT department for the Project Owner project group. When a user at your company submits a supplier request
indicating that the supplier provides computer equipment in North America for the IT department, the IT Category
Managers user group becomes a member of the Project Owner project group for that request, and any user in the
IT Category Managers group can approve the request. Assigning a group rather than an individual user is useful
because if one user leaves the company, other members of the group are still assigned as approvers. You can add
or remove members of user groups at any time.

You can assign either an individual user or a global user group to a combination of commodities, regions,
departments and project groups. You can also assign a user to only a region (by specifying the region and using
All for commodity and department), or to only a commodity (by specifying the commodity and using All for
region and department), or to only a department (by specifying department and using All for commodity and
region).
 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.
● If the current buyer category assignment (user matrix) data in your site does not include an assignment
that exactly matches the commodities, regions, and departments in a project, a matching algorithm
identifies an assignment further up in the commodity, region, or department hierarchy and uses that
assignment instead. See below for a detailed explanation of how this matching works.
● When you assign a user to a project group, that group must also exist in the appropriate template.
You use the User Matrix data import task to specify user assignments to categories and regions. The task reads
from a CSV file that contains the following fields:
Field Description
commodityCodeDomain The domain of the commodity code; for example, unspsc.
commodityCode The code for the commodity to which to assign the user or
group. This code must match the commodity master data
loaded in your SAP Ariba site.
region The region to which to assign the user or group. This code
must match the commodity master data loaded in your SAP
Ariba site.
businessUnit The department to which to assign the user or group. This

code must match the commodity master data loaded in your
SAP Ariba site.
userName The username of the user to which you are assigning commod
ities, regions, departments, and project groups. Use this field
only for assignments to individual users. Leave it blank for as
signments to global user groups. Rows that contain values in
both the userName and groupUniqueName fields cause
import errors.

Field Description
groupUniqueName The unique name of the global system or custom user group to
which you are assigning commodities, regions, departments,
and project groups.
You can use either SAP Ariba default (SYSTEM) or your own
custom (AribaManaged or External) user groups. Group
unique names are visible in user group data exports from
Site Manager Data Import/Export and in the group
descriptions you see when clicking a group name in User
Manager Groups in Ariba Administrator.
Use this field only for assignments to global user groups. Leave
it blank for assignments to individual users. Rows that contain
values in both the userName and groupUniqueName fields
cause import errors.
projectGroup The name of the project group to which the user is assigned.
Note that this group must exist in the project; the assignment
does not automatically create it.
passwordAdapter The user's password adapter, usually PasswordAdapter1.
active A Boolean value that specifies whether the assignment descri

bed by the current row is active (TRUE) or deactivated
(FALSE). If this field is empty, the row is flagged as active.
The following example shows lines of a user matrix CSV file, as well as the mandatory header:
commodityCodeDomain,commodityCode,region,businessUnit,userName,groupUniqueName,proje
ctGroup,passwordAdapter,active
unspsc,All,North America,Corporate,tjones,,Legal,PasswordAdapter1,TRUE
unspsc,4213,All,Corporate,ljenkins,,Project Owner,PasswordAdapter1,TRUE
unspsc,All,Los Angeles,Corporate,grooney,,Project Owner,PasswordAdapter1,TRUE
unspsc,All,San Diego,grooney,,Project Owner,PasswordAdapter1,TRUE
unspsc,All,All,IT,,IT Category Managers,Project Owner,PasswordAdapter1,TRUE
To assign a single user to multiple commodity, region, and department combinations, 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 for the Corporate department.
You can use the active field to update assignments by deactivating the currently assigned user and assigning
another user in their place. For example, if Terry Jones leaves the company, and you can replace her with George
Smith by importing a user matrix CSV file with the following lines:
commodityCodeDomain,commodityCode,region,businessUnit,userName,groupUniqueName,proje
ctGroup,passwordAdapter,active
unspsc,All,North America,HR,tjones,,Legal,PasswordAdapter1,FALSE
unspsc,All,North America,HR,gsmith,,Legal,PasswordAdapter1,TRUE
If the current buyer category assignment (user matrix) data in your site does not include an assignment that
exactly matches the commodities, regions, and departments in a project, a matching algorithm identifies an

assignment further up in the commodity, region, or department hierarchy and uses that assignment instead. The
matching algorithm starts with the hierarchy that has the lowest-level value and, if it does not identify an
assignment, continues with the hierarchy with the next-lowest value. If all project hierarchy values are at the same
level, the matching algorithm prioritizes the commodity hierarchy. For example, say that commodity, region, and
department hierarchies include the following values:
Level Commodity Region Department
0 All All All
1 42 EMEA Manufacturing
2 4213 Western Europe Product Manufacturing
3 421324 Germany Logistics
4 42132489 Munich Transportation
If a project has a commodity of 42, a region of Germany, and a department of Product Manufacturing, and there is
no buyer category assignment that exactly matches those values, the matching algorithm starts looking for
assignments higher up in the region hierarchy, since the region is the lowest-level value. If it does not find any
matches up to the highest level of the region hierarchy, it then starts looking for assignments higher up in the
department hierarchy, since the department is the second lowest-level value. However, if a project has a
commodity of 4213, a region of Western Europe, and a department of Product Manufacturing and there is no
exactly matching assignment, the matching algorithm starts looking for assignments higher up the commodity
hierarchy, since when all hierarchy values are at the same level, it prioritizes commodity.
When looking for assignments higher up in a hierarchy, the matching algorithm iterates through progressive
searches until it finds an assignment. For example, say the user matrix (buyer category assignments) in a site
include the following assignments:
User Commodity Region Department
A 421324 All All
B 4213 All All
For a project with a commodity of 42132489, a region of EMEA, and no department set (a department of 0), the
matching algorithm starts with those exact values and then, when it does not find a match, performs additional
searches progressively higher up the commodity hierarchy in the first iteration:
Search Commodity Region Department Match?
1 42132489 EMEA 0 No
2 42132489, 421324 EMEA 0 No
3 42132489, 421324, EMEA 0 No

4213
4 42132489, 421324, EMEA 0 No

4213, 42
5 42132489, 421324, EMEA 0 No

4213, 42, All
In this case, since the available buyer category assignments all specify a region of All, and the project region is
EMEA, the matching algorithm does not find an assignment by looking higher up the commodity hierarchy alone. In
the second iteration, it looks higher up the region hierarchy:

1 42132489, 421324, EMEA, All 0 No

4213, 42, All
In this case, since the available buyer category assignments all specify a department of All, and the project
department is 0, the matching algorithm does not find an assignment by looking higher up in the commodity
hierarchy and then in the region hierarchy. In a third iteration, it looks higher up the department hierarchy:
1 42132489, 421324, EMEA, All 0, All Yes

4213, 42, All
Based on these iterations, the matching algorithm identifies User A (the user with the more specific commodity)
for the buyer category assignment.
Internal supplier registration data file format
Supplier internal registration data designates suppliers as internally registered so that they have a registration
status of Registered without use of a registration project.
Suppliers that achieve Registered registration status through this data import are automatically flagged as
internally registered. The data import changes suppliers' registration status to Registered but does not create
underlying registration projects. When a supplier is flagged as internally registered through data import,
registration managers can manually start an internal registration or invite the supplier to register later, creating a
registration project so that recipients can fill out questionnaires to provide profile information.
Internal supplier registrations import file format
You use the Internal supplier registrations data import task to designate suppliers as internally registered. The
task reads from a CSV file that contains the following fields:
smVendorId The SM vendor ID for the supplier, which Yes

is an ID that SAP Ariba automatically as
signs to every supplier created in the sys
tem.
name1 The supplier name stored in the Yes

vendor.vendorInfo.name1 field in
the supplier database.
The import only affects suppliers in Not Invited status registration status. Once a supplier has achieved at least
Invited registration status, you cannot set their registration status to Registered using this data import.

 Tip
You can use the Suppliers data export to see SM vendor IDs and vendor.vendorInfo.name1 values for all
suppliers in your site.
The following example shows lines of a supplier internal registration CSV file, as well as the mandatory header:
UTF-8
smVendorId,name1
S10202900,Supplier 1
S10165792,Supplier 2
 Restriction
The data import must only include new internal registrations and can only include the smVendorId and name1
fields. Importing a file that includes the additional columns in the data export, vendorActive,
registrationStatus, registrationStatusId, and registrationSource, results in a success message
but does not successfully add data. Importing a file that includes existing internal registrations results in errors.
For this data import, always use the sample file to import new data sets that include only the smVendorId and
name1 fields.
Internal supplier registrations export file format
The corresponding data export for Internal supplier registrations includes all of the internally registered suppliers
in your site, whether they were registered using the data import or manually in a registration project. The export
includes the following fields:
Field Description
smVendorId The SM vendor ID for the supplier, which is an ID that SAP

Ariba automatically assigns to every supplier created in the
system.
name1 The supplier name stored in the

vendor.vendorInfo.name1 field in the supplier data
base.
vendorActive A Boolean value indicating whether the supplier is active or in

active.
registrationStatus The registration status of the supplier.
registrationStatusId The project (workspace) ID of the registration project for the

internal registration.

Field Description
registrationSource One of the following values:
● InternallyRegisteredViaCsv, which means that

the supplier's registration status was achieved through in
ternal supplier registration data import and there is no
registration project associated with the supplier.
● InternallyRegisteredViaUi, which means that
the supplier's registration status was achieved by a regis
tration manager starting an internal registration in the
user interface and creating a registration project.
 Note
● The Internal supplier registrations data export includes suppliers that were originally registered internally
but who were later invited to participate in their registrations and are therefore no longer flagged as
internally registered.
How to import custom SAP region codes for supplier

extended addresses
If your integrated SAP ERP, SAP S/4HANA, SAP S/4HANA Cloud, or SAP MDG-S system uses custom region
codes, you can ensure that supplier extended addresses use the same codes by importing them in Ariba
Administrator.
Prerequisites
The region code data import feature is not available by default. To enable this feature, have your Designated
Support Contact log a service request. An SAP Ariba Customer Support representative will follow up to complete
the request.
To import SAP region code data in Ariba Administrator, you must be a member of the Customer Administrator
group.
Context
Imported SAP region codes show in the Region dropdown menu of Extended Address questions only. All other
region fields in your site use your site's region master data. The Extended Address Region menu only shows the
region codes you import; it does not add them to your site's existing region master data. Therefore, make sure that
you import the full set of region codes you want to use.

Procedure
1. In the integrated SAP system, export the T005S and T005U tables to separate Microsoft Excel XLSX files.
2. Add both of the exported XLSX files to a ZIP file.
3. On the dashboard of your SAP Ariba site, click Manage Administration .
4. Choose SM Manager SAP Region Codes .

5. On the Sap Region Upload tab, click Choose File.
6. Navigate to the ZIP file containing your SAP region codes and click Open.
7. Click Upload.
Results
You can monitor the status of your SAP region code upload and see any error messages on the Sap Region Upload
Status tab.
After the upload is complete, users in your site who answer an Extended Address question (for example, when
filling out a supplier request) choose from among the uploaded SAP region codes for the Region field, and that
region code is stored in the corresponding vendor.addressExt.postalAddress.regionCode field. When the
supplier is synchronized with the integrated system, the supplier address information includes region codes
recognized by that system.
Next Steps
Make sure that your custom SAP region codes are correctly mapped to the country codes used for supplier
addresses on Ariba Network. If your Extended Address questions are also mapped to Ariba Network supplier
profile address fields and a supplier updates their address in their Ariba Network profile, that update is
synchronized back to your site. Your site includes default mappings [page 423], but if you use custom SAP region
codes, you must maintain custom mappings using master data imports [page 60].
Related Information
Default fields and field mappings in address question answer types [page 270]

Importing business partner IDs for ERP suppliers
added through SAP Ariba Procurement solutions
If your solution includes SAP Ariba Procurement solutions and you add suppliers from an integrated SAP ERP
system using SAP Ariba Procurement solutions supplier data import tasks, including the business partner IDs for
those suppliers ensures that the ERP system recognizes them.
The SupplierIDs.csv file used by SAP Ariba Procurement solutions supplier organization data import tasks can
include two domains that are used in SAP Ariba Supplier Lifecycle and Performance and SAP Ariba Supplier
Information and Performance Management (new architecture):
smbpid 100023 The SAP ERP business partner ID for the

supplier.
If your solution includes SAP Ariba Sup

plier Lifecycle and Performance but you
add suppliers from SAP ERP in SAP Ariba
Procurement solutions, it is important to
include an smbpid value for every ERP
supplier. This smbpid ensures that
when a supplier synchronizes back from
SAP Ariba Supplier Lifecycle and Per
formance to the ERP system, that syn
chronization includes the supplier's busi
ness partner ID, which identifies it as an
existing supplier. Otherwise, SAP ERP
creates a new, duplicate supplier.
smsupplierid vdr70073 A supplier ID used in SAP Ariba Supplier

Lifecycle and Performance, typically the
supplier's ERP vendor ID. For integrated
suppliers, this ID is the same as their
sap ID. In cases where there are IDs de
fined for a supplier in both sap and
smsupplierid domains, the
smsupplierid domain takes prece
dence.
For more information about supplier data import tasks in SAP Ariba Procurement solutions, see the Common data
import and administration guide for SAP Ariba Procurement solutions.

Topics about setting up optional features for
supplier and supplier contact names
Showing supplier names longer than 35 characters in SAP Ariba solutions [page 107]
How to set up your site to show contact names with family name first [page 109]
Showing supplier names longer than 35 characters in

SAP Ariba solutions
By default, in sites that include SAP Ariba Supplier Lifecycle and Performance, supplier display names have a
maximum length of 35 characters. An optional feature allows you to show supplier names of up to 140 characters
across all SAP Ariba solutions.
Both SAP ERP and the unified vendor model that SAP Ariba Supplier Management solutions use includes 4 name
fields, vendor.vendorInfo.name1 through vendor.vendorInfo.name4, each of which has a maximum length
of 35 characters, and which can form the full name of the supplier when concatenated. By default, only the values
in the vendor.vendorInfo.name1 field show in SAP Ariba Supplier Management solutions and in other SAP
Ariba solutions such as SAP Ariba Contracts, SAP Ariba Sourcing, and SAP Ariba Buying solutions. When a supplier
name is longer than 35 characters, the remaining portions of the name are truncated. Some suppliers have
multiple legal entities, each with the same name plus a suffix to differentiate it from the others. If the portion of a
supplier name that differentiated it from other related entities falls outside of the vendor.vendorInfoname1 field
due to length, and all of the values in the vendor.vendorInfo.name1 are identical, it is difficult for users in SAP
Ariba solutions to identify the correct supplier in supplier searches, supplier profiles, and when adding suppliers to
transactions such as contracts.
An optional supplier full name feature, SM-14213, allows you to display full or long names for suppliers across SAP
Ariba solutions. It adds a separate vendor database field, vendor.vendorInfo.fullName, to store full supplier
names. vendor.vendorInfo.fullName has a maximum length of 140 characters. SAP Ariba trims any leading or
following whitespace from full name values. Other SAP Ariba solutions then show the value in this field as the
supplier name.
 Note
Currently, the supplier full name feature does not support supplier names in Chinese, Japanese, or Korean.
To collect supplier full names directly using this field:
● Map a question to vendor.vendorInfo.fullName in supplier management questionnaires such as the

supplier request and external registration questionnaires.
● Make sure that none of the supplier management questionnaires in your site contain any questions mapped to
any of the numbered name fields, vendor.vendorInfo.name1 through vendor.vendorInfo.name4.

Topics about setting up optional features for supplier and supplier contact names PUBLIC 107
 Restriction
Mapping to both the full name field and the numbered name fields in questionnaires is not supported. Choose
which type of name data you want to collect from supplier management questionnaires, either the full name in
one field or different parts of the name in the 4 numbered fields, and map the name questions in the supplier
management questionnaires in your site accordingly. Collecting both types of name data can introduce errors
and distortions in supplier names.
SAP Ariba uses whatever type of name data you collect for a supplier to populate both types of name fields.
If a mapped question does not directly add full name data to the vendor.vendorInfo.fullName field for a
supplier, SAP Ariba automatically concatenates existing data in vendor.vendorInfo.name1 through
vendor.vendorInfo.name4 fields to populate it.
 Note
Because of this automatic concatenation of values in numbered name fields, the supplier full name feature is
not suitable for sites that use any of the numbered name fields to collect alternate names for suppliers.
If mapped questions, data import, or synchronization from an integrated ERP system do not directly add name
data to the numbered name fields for a supplier, but there is data in the vendor.vendorInfo.fullName field,
SAP Ariba automatically splits that data up and populates the numbered name fields with it as follows:
● If the full name is 35 characters or less, SAP Ariba adds the entire name to vendor.vendorInfo.name1.
● If the full name is between 36 and 70 characters, SAP Ariba adds the remaining characters above 35 to
vendor.vendorInfo.name2.
● If the full name is longer than 70 characters, SAP Ariba adds additional characters to the
vendor.vendorInfo.name3 and then vendor.vendorInfo.name4 fields in the same way.
SAP Ariba does not consider spaces when splitting up full names..
In sites that include SAP Ariba Procurement solutions, you must fulfill the following prerequisites before enabling
the full name feature:
● If you use the SAP Ariba integration toolkit to integrate your ERP system with SAP Ariba Procurement
solutions, you must implement an enhancement in your ERP system to send the full supplier name
(concatenating all numbered name fields) through the SAP Ariba integration toolkit. Currently, SAP Ariba
integration toolkit integration sends only the first name field.
● The configuration of your ERP system integration with SAP Ariba must ensure that suppliers synchronize from
the ERP system to SAP Ariba Supplier Management solutions before they synchronize with SAP Ariba
Procurement solutions.

108 PUBLIC Topics about setting up optional features for supplier and supplier contact names
How to set up your site to show contact names with
family name first
You can set up your site to show existing external contacts with their family names first.
Prerequisites
To use the Data Import/Export task in Ariba Administrator, you must be a member of the Customer
The site configuration parameter Application.SM.VendorContactPushTaskEnabled (set by SAP Ariba

Support) must be disabled before you update existing supplier contact data and while the family name first feature
is enabled. SAP Ariba uses spaces in a contact's name as delimiters when adding it to the first, middle, and last
name fields in the supplier database, which can introduce errors. Contact SAP Ariba support to disable this site
configuration parameter.
Context
If your organization wants to address existing external contacts with family names first, you can contact SAP Ariba
support to enable the family name first feature.
 Note
The family name first feature is dependent on which version of the supplier 360° profile your site uses. If your
site uses the classic supplier 360° profile, contact SAP Ariba support to enable SM-15622. If your site uses the
new supplier 360° profile, contact SAP Ariba support to enable SM-17591.
While it is enabled, the family name first feature reverses the order in which all new supplier contact names show,
but contact name data is unaffected in your database. Contact first names are still stored in the
contact.firstName field, and last names are stored in the contact.lastName field. To show existing supplier
contact names in reverse order after the feature is enabled, you must use the Data Import/Export task in Ariba
Administrator to update contact name data added before the feature is enabled.
For example, if you want an existing supplier named "John Doe" to show as "Doe John", you must update the
contact name data to be "Doe John" before enabling the feature. After the feature is enabled, if you create a new
supplier contact named "Jane Doe", the name shows as "Doe Jane".
Procedure
1. In Ariba Administrator, choose Site Manager Data Import/Export .

2. Export supplier contacts using the Export Supplier Users data export task.

Topics about setting up optional features for supplier and supplier contact names PUBLIC 109
3. Edit the order of contact names in the FullName field so that they are in the order you want them shown in
your site.
4. Import the edited file using the Import Supplier Users data import task.
5. Contact SAP Ariba support to enable the family name first.
Next Steps
If you disable the family name first feature at a later time and want to show supplier contact names as they were
before enabling the family name first feature, with family names shown last, repeat the data export and import
steps above.

110 PUBLIC Topics about setting up optional features for supplier and supplier contact names
Topics about supplier management project
template basics
Understanding supplier management project templates [page 111]
Using SPM project templates in SAP Ariba Supplier Management solutions that use the unified vendor model
[page 115]
Exporting and importing supplier management project templates [page 116]
Topics about editing and publishing project templates [page 117]
Topics about upgrading supplier management projects to the latest template version [page 123]
Understanding supplier management project

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 supplier management processes:
● Supplier Request Project Template [page 135]

● Supplier Self-Registration Request Template. [page 139] (in sites with the external supplier request feature
enabled)
● Supplier Registration Project Template [page 148]
● Supplier Qualificaton Project Template [page 176] (SAP Ariba Supplier Lifecycle and Performance solutions
only)
● Preferred Supplier Management Project Template [page 187] (SAP Ariba Supplier Lifecycle and Performance
solutions only)
● Supplier Disqualification Project Template [page 184] (SAP Ariba Supplier Lifecycle and Performance
solutions only)
There is only one template for each of these project types in a site. There is also an SM Modular Questionnaire
[page 190] project type. You can create multiple templates of this type, one per modular questionnaire.
Template upgrade is only supported for supplier registration projects and modular supplier management
questionnaire project templates. If you edit any of these other templates, only new projects created after the new
template version is published reflect those changes.
Supplier management project templates function in much the same way as project templates in other SAP Ariba
solutions: 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 manage them as separate projects, or see
the classic project interface with its tabs for documents, tasks, team, and so forth. Instead, they work in the 360°
profiles of individual suppliers. A supplier's 360° profile includes all supplier management projects for the supplier.

Topics about supplier management project template basics PUBLIC 111
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. They do not manage the project's team, upload additional documents, or perform
other activities associated with the classic project interface in other SAP Ariba projects.
These supplier management project templates are designed to support these special workflows and user
experiences. The classic project interface is available in the advanced view. To see the advanced view of a supplier
management project, the Advanced View link for that project type must be enabled in your site and you must have
appropriate group membership permissions. For more information, see How to manage access to the advanced
view of supplier management projects [page 372].
Commodity, region, department, and user combinations in supplier management projects [page 112]
Documents in supplier management projects: forms and questionnaires [page 113]
Tasks in supplier management projects: To Do's and form and questionnaire approvals [page 114]
Team in supplier management projects: automatic assignment by commodity, region, and department [page
115]
Related Information
Commodity, region, department, and user combinations in supplier management projects [page 112]
Documents in supplier management projects: forms and questionnaires [page 113]
Tasks in supplier management projects: To Do's and form and questionnaire approvals [page 114]
Team in supplier management projects: automatic assignment by commodity, region, and department [page 115]
Commodity, region, department, and user combinations in

supplier management projects
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.
If the business unit matrix enhancement is enabled in your site, templates use a combination of commodities,
regions, and departments.
Commodity, region, and department combinations are used in the following areas of supplier management:
● Targeting qualification questionnaires: In solutions that include SAP Ariba Supplier Lifecycle and
Performance, template creators create different qualification questionnaire segments with questions
pertaining to specific commodities, regions, or departments (or any combination of the three). When a supplier
or category manager sends a qualification questionnaire to a supplier, the questionnaire can include all of the
template segments that apply to the supplier's commodities, regions, and departments.
● Assigning the appropriate project owners, approvers, and other team members: If user assignments to
commodities, regions, departments, 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.

112 PUBLIC Topics about supplier management project template basics
Related Information

How to set up a targeted supplier qualification questionnaire [page 226]
How to create a targeted supplier qualification questionnaire segment [page 228]
Understanding buyer category assignments (the user matrix) [page 312]
Documents in supplier management projects: forms and

questionnaires
Supplier management project templates use survey documents to create forms and questionnaires. Some types of
projects involve questionnaires that are targeted to specific commodity, region, and department combinations.
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 questionnaires 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.
Content in forms is not numbered.
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, such as questions.
● Simple questionnaires: for projects that need a larger set of information, you use the default survey document
in the project, without any additional content documents, to create the simple questionnaire. Content in
questionnaires is always numbered.
For example, an external (supplier-facing) registration questionnaire typically involves a long set of general
questions. You create the registration questionnaire by editing the default template survey to set its type to
Questionnaire and add all of the questionnaire content.
● Internal forms or questionnaires: some supplier management projects support additional survey documents
to allow category or supplier managers to supplement the information gathered in the project's external
(supplier-facing) questionnaires.
For example, suppliers fill out external registration questionnaires, but there is some supplier profile
information that can only be provided by internal users; for example, internal users often specify purchasing
organization information for suppliers. In this case, you create an additional survey document in the project,
set its content type to either Form or Questionnaireand specify that it is internal. You then add questions to it.
● Dynamic qualification questionnaires: qualification projects assemble a dynamic external (supplier-facing)
questionnaire using an empty survey document and a set of content document questionnaire segments
targeted to specific commodity, region, and department combinations. Qualification projects are only available
in SAP Ariba Supplier Lifecycle and Performance.

Related Information

How to create a supplier form or questionnaire [page 222]
How to create a supplier-related internal questionnaire [page 229]
How to set up a modular supplier management questionnaire [page 195]
Tasks in supplier management projects: To Do's and form

and questionnaire approvals
Supplier management projects use approval tasks and approval flows to define approval processes for forms and
questionnaires. They also support To Do tasks. They do not support any other type of project task.
Supplier management projects are designed to use approval tasks on the template's survey document to route
approvals for various supplier management processes. The approval flow is defined in the approval task.
Although SAP Ariba projects also support To Do tasks, 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 Registration
Manager or Legal) and project groups (such as Project Owner). If you are using buyer category assignments (the
user matrix) 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, regions, and (in sites with the business user matrix enhancement feature enabled),
departments. You can also use special field mappings on hidden questions in the project's questionnaire or form in
order to add approvers based on answers to a parent question.
Supplier management projects also support To Do; for example, a To Do task that requires a category or supplier
manager to complete the project's internal survey.
Users complete these approval and To Do tasks in the supplier's 360° profile. Users must complete any other
project tasks outside of the supplier's 360° view by clicking Manage My Tasks on the dashboard.
All of a project's tasks must be completed in order for that stage of the supplier management workflow to be
completed. For example, if a supplier registration project includes To Do tasks as well as approval tasks on multiple
registration questionnaires, each registration questionnaire sent to the supplier must be approved and all of the To
Do tasks must be marked complete for the supplier to be considered registered.
Related Information

Topics about setting up supplier form and questionnaire approvals [page 316]

Team in supplier management projects: automatic
assignment by commodity, region, and department
Projects in SAP Ariba Supplier Management solutions 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 can be set up to dynamically add users to project groups
on the Team tab, including Project Owner, based on their assignments to categories and regions. In sites with the
business unit matrix enhancement feature enabled, supplier management project templates can also add users to
project groups based on their assignment to departments.
Buyer category assignments (the user matrix) ensure that each supplier management project automatically has
the correct team members based on the supplier's commodities, regions, and departments. If a supplier's
commodity, region, or department is not assigned to a specific user, the project automatically adds the user
assigned to the commodity, region, or department above it in the hierarchy to the project team. For example, if a
supplier's region is Illinois, and no user is assigned to Illinois, the project adds the user assigned to the United
States to the project team. This feature is especially useful in sites that work with large numbers of individual
commodity codes, because you do not have to assign a buyer user to every low-level commodity code you use; the
project will automatically add the user with a higher-level commodity code assignment in the same branch of the
hierarchy to the project team.
Related Information

How to use buyer category assignments to add team members to project groups [page 314]
Using SPM project templates in SAP Ariba Supplier

Management solutions that use the unified vendor
model
Your site might use Supplier Performance Management (SPM) projects to periodically review the performance of
your suppliers. These projects function differently from the other supplier management projects in your site in
some significant ways.
SPM projects use the classic SAP Ariba project infrastructure, meaning that they are not visible in supplier 360°
profiles on the Supplier Management tab. They exist as individual projects and are not tied to the supplier's profile
or linked to other supplier management projects. Supplier or category managers create them by clicking Create
SPM Project on the Home dashboard, and view them by searching for projects. Project owners can add
documents and tasks to the project and modify the project team.
SPM project templates do not include the following supplier management features:

● Buyer category assignments to project teams. In order to assign category or supplier managers to an SPM
project team, you must use team member rules.
● Management per commodity/region/department combination. SPM projects evaluate performance per
supplier; in order to show content based on the supplier's commodities, regions, and (optionally) departments,
you must either add conditional content to a single template or create separate templates for different
commodity/region combination and rely on category or supplier managers to choose the correct template
when they create an SPM project for the supplier.
● Dynamic questionnaires. Content documents are not available in SPM project templates. Each survey
document in the project acts as an independent survey, which participants must fill out separately.
These topics do not discuss setting up SPM project templates. For information on SPM project template setup, see
the Project Template Guide and Configuring Supplier Performance Management Reviews topics.
Exporting and importing supplier management

project templates
 Note
Once a registration or modular supplier management questionnaire project template is in use in your
production site and has projects created from it, updating it by re-importing it from the test site can replace the
KI IDs of individual pieces of content. Upgrading those projects to the latest template version can then replace
existing content in individual projects with "new" content identified by different KI IDs, causing loss of data in
questionnaires. Exporting and importing registration and modular supplier management questionnaire project
templates is therefore most useful during the initial template setup, before these templates are in use in your
production site.
Default supplier management project templates
SAP Ariba creates and installs the following supplier management project templates. Each of the project templates
have identifiers that are the same for all sites. Only one of each can exist per site, but each can be imported to
another site, thereby overwriting the existing version. This enables you to export these project templates from one
site (such as a test site) to a different site (such as a production site) without having to modify identifiers.
● Preferred Supplier Management Project Template

● Supplier Disqualification Project Template
● Supplier Qualification Project Template
● Supplier Registration Project Template
● Supplier Request Project Template
Modular supplier management questionnaire project templates
Members of the SM Modular Questionnaire Manager group create modular supplier management questionnaire
projects from templates. To create modular questionnaire templates, you must be in both the Template Creator

and SM Modular Questionnaire Manager groups. You create multiple modular supplier management
questionnaire templates in your site, one for each questionnaire. These templates all have the project type SM
Modular Questionnaire and automatically generate identifiers.
If you have a test site and a production site, you can create a modular questionnaire on the test site and an
identifier is generated for the template. You can then export the template and import it to the production site; the
template will retain the identifier from the test site. If you modify the template on the test site and export it again,
you can re-import it to the production site because the identifier is the same.
Related Information
Topics about editing and publishing project

templates
How to edit a project template [page 117]
How to set validation rules for publishing new template versions [page 119]
Using the project template Overview tab [page 120]
How to publish supplier management project templates [page 121]
How to revert a project template [page 122]
How to edit a project template

If a project template is published and you want to edit it, you must create a new, draft version of the template.
Prerequisites
To create or edit project templates, you must be a member of the global Template Creator group or the template
project’s Templates Creator team. To create or edit a modular supplier management questionnaire project
template, you must also be a member of the global SM Modular Questionnaire Manager group.
Context
To edit a template, the template status must be Draft. If you have published a template, you must create a new,
draft version of the template to edit. When you are done editing a template, you must publish the template to make
the changes affect subsequent projects created using the template.

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 .

You can modify and add items to the template.
Results
To make the changes available to users creating projects, you must publish the new version of the template.
The following table describes how editing different types of templates affects existing projects created from those
templates.
Editing a template of this type... Affects existing projects created from the template in this way...
● Knowledge projects Editing a template and publishing a new version does not affect any projects created with
● Sourcing projects (both full previous versions of the template. When a user creates a project, the system copies tem
and quick, including events) plate data as it exists in the current template version. Any subsequent changes to the tem
plate have no effect on projects already in existence.
● Contract requests
● Supplier requests (both in If a user creates a project from a template while you are editing it (you have created a new
ternal and external) template version but have not published it), the system uses data from the last published
● Supplier qualifications version of the template.
● Supplier disqualifications
● Preferred supplier manage
ment category status re
quests
● Contract workspaces Editing a template and publishing a new version does not affect any contract workspaces
created with the previous version of the template by default. However, SAP Ariba Contracts
has an option for updating a contract workspace created from an updated template when
the project owner amends the contract workspace. If your site does not support upgrading
template versions in contract workspaces, contact SAP Ariba Customer Support.
● SPM projects Editing a template and publishing a new version will update all of the projects created with
● Supplier workspaces the previous version of the template if you specify that you want to upgrade those projects
before you publish the new version of the template.
● Supplier registrations Editing a template and publishing a new version does not affect any projects created with
previous version of the template. In sites where the template upgrade feature is enabled,
● Modular supplier manage
members of the SM Ops Administrator group can perform a separate template upgrade
ment questionnaires operation to upgrade eligible projects created from previous versions of the template to the
current version.
Related Information
Topics about upgrading supplier workspace and SPM project templates

Topics about upgrading supplier management projects to the latest template version [page 123]
How to set validation rules for publishing new template

versions
You can set document matching and content matching validation rules for new template versions of supplier
registration and modular supplier management questionnaire project templates.
Prerequisites
project's Template Creator team. To create or edit a modular supplier management questionnaire project
template, you must be a member of the global SM Modular Questionnaire Manager group.
Context
By default, the template upgrade validation system flags all discrepancies when publishing a new template version
for supplier registration and modular supplier management questionnaire project templates. You can set your own
value for the Required content match (%) property on the Overview tab of supplier registration and modular
supplier management questionnaire project templates. This property controls the percentage of template
document content that must match against the previous template version. For example, if a template survey
document has 10 questions and you change one of them in a new template version, the Required content match
(%) property must have a value of 90 or higher for you to publish the new template version.
You can also set the Skip pre-publication validation? property on the Overview tab of supplier registration and
modular supplier management questionnaire project templates. When this property is set to Yes, it ignores
document matching and content matching validations and allows you to publish new template versions regardless
of the changes you make.
 Note
SAP Ariba recommends setting the Skip pre-publication validation? property to No. If you set the property to
Yes, you may unintentionally lose supplier response data. After publishing a new template version, Skip pre-
publication validation? resets to No.
Procedure
1. From the Overview tab of an active template, choose Actions New Version .
2. Choose Actions Edit Properties .

3. Enter a value for Required content matching (%).
This value determines the percentage of content within a document that must match to the previous version of
that document. The default value is 100.
4. Set the Skip pre-publication validation? property.
This property allows you to publish new template versions that contain documents or content that does not
match. It is set to No by default, and resets to No after template upgrades.
 Note
SAP Ariba recommends setting the Skip pre-publication validation? property to No. If you set the
property to Yes, you may unintentionally lose supplier response data.
Using the project template Overview tab
The following table lists the tasks you can perform on a project 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, status,
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 ac
tion.
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 SAP Ariba Sourcing quick projects only use compact view.

How to publish supplier management project templates
You must publish a project template to make it available to users who are creating projects.
Prerequisites
project's Template Creator team. To create or edit a modular supplier management questionnaire project
template, you must be a member of the global SM Modular Questionnaire Manager group.
Context
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.
Supplier registration and modular supplier management project template documents are validated when you
attempt to publish the template. By default, the template upgrade validation system flags all discrepancies when
you publish a new template version for supplier registration and modular supplier management questionnaire
project templates. However, you can set your own value for the Required content match (%) property or set the
Skip pre-publication validation? property on the Overview tab of supplier registration and modular supplier
management questionnaire project templates. For more information about setting validation rules, see How to set
validation rules for publishing new template versions [page 119].
Error messages alert you to issues that require attention in order to publish the template. You need to fix any
validation errors in template documents or questionnaire content before you can successfully publish a template.
Alternatively, you can set the Skip pre-publication validation? to Yes to ignore validation errors. SAP Ariba
recommends setting the Skip pre-publication validation? property to No. If you set the property to Yes, you may
unintentionally lose supplier response data. After publishing a new template version, Skip pre-publication
validation? reset to No.
 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.
Procedure
● Choose Actions Publish on the Overview tab.
 Note
If changes you have made to the current template version have generated validation errors and you are
concerned that they might cause data loss, you can choose Actions Revert on the Overview tab

instead of publishing a new template version. Reverting template versions undoes any changes you made,
such as deleting a template document, and allows you to create another new template version.
Next Steps
After you have completed work on a template, you can export it to a ZIP file and import it for later use.
Related Information
How to set validation rules for publishing new template versions [page 119]
How to revert a project template
You can create a new version of a project template from the contents of a previous version.
Prerequisites
Context
You can create a new version of a project template from the contents of a previous version. The new version
becomes the most recent version of the template. Creating a new version of an older version reverts the template
to a previous version without losing its history.
Procedure
1. Open the project template. If the template state is not Active, go to the Properties area and select Actions
Publish .
The template must be in the Active state before you can create a new version.
2. Open the previous version of the template you want to revert to.

a. Open the Overview tab and scroll down to the Version History area.
b. Select the version that you want to use to create a new version, then select Action Open .
3. On the Overview tab of the previous template version, go to the Properties area and select Actions New
Version .
SAP Ariba copies the contents of the older template version and creates a new version in the Draft state.
4. On the Overview tab of the new template version, go to the Properties area and select Actions Publish .
Results
All projects that were created with previous versions of the template continue to use the version from which they
were created. When project owners amend the contract workspace created from the updated template, they can
choose to use the updated version or the original version. If your site does not support upgrading template versions
in contract workspaces, contact SAP Ariba Customer Support.
Topics about upgrading supplier management

projects to the latest template version
About supplier management project template upgrade [page 123]
Which supplier management projects are eligible for template upgrade? [page 125]
How template upgrade affects supplier management projects [page 126]
How to upgrade supplier management projects to the latest template version [page 132]
About supplier management project template upgrade

Template upgrade enables you to automatically update existing projects with any changes you have made to the
template from which they were created.
Currently, supplier registration projects and modular supplier management questionnaire projects are the only
supplier management projects that support template upgrade. Both of these project types support ongoing
updates to questionnaires. With registration projects, questionnaires are open to updates unless the registration is
denied or a questionnaire update is currently in approval. With modular supplier management questionnaire
projects, you must check the Always open rule in the template questionnaire survey document to enable updates.
These projects remain open so that respondents can edit and resubmit questionnaires at any time after the initial
questionnaire is approved, including updating them to answer additional questions added in a template upgrade.
However, even if the project is otherwise closed, template upgrade allows recipients to revise their responses to
questionnaires and restarts any approval tasks associated with them on a one-time basis. This one-time upgrade-
related update ensures that questionnaire data and approvals are consistent and match your current processes
regardless of when a recipient filled out the questionnaire.

Template upgrade is a version-based process, meaning that you upgrade all of the eligible projects on a previous
version of the template to the current published version in one upgrade operation, and all of the eligible projects on
a different previous version of the template to the current published version in a separate upgrade operation. For
supplier registration and external (supplier-facing) modular questionnaire templates, upgrade operations include a
notification option that allows you to alert suppliers to changes that affect them. Internal users do not receive
notifications of template upgrades.
Safeguards ensure that you cannot upgrade projects with active tasks to prevent them from being disrupted by
template changes while they are in progress. For a given previous version of the template, typically some number of
projects fewer than the total number created from that version are eligible for upgrade at a given time due to task
activity in some of the projects. Therefore, you typically perform an upgrade for a specific version several times
over a period of time until you have finally upgraded all of the projects to that version.
Template upgrade always upgrades projects directly to the current published version of the template. It is possible
to have some projects in your site that are multiple version behind the current version of the template because they
were not eligible for upgrade to previous versions when they were current. For example, if your current version is 6,
you might have a project in version 3 that was not eligible for upgrade to version 4 or 5 when they were current, and
is only now eligible for upgrade. In this case, the project is upgraded directly from version 3 to version 6.
The template upgrade operation automatically creates new projects and copies the data from the previous
projects, which it archives. The original project and each upgraded project all have unique IDs, but upgraded
projects are linked to their previous projects, The History tab of each upgraded logs the template upgrade with an
entry labeled Upgraded to a new version of template. It does not, however, show specific details about which
elements of the project were modified during the upgrade. However, information from previous projects, such as
previous questionnaire versions and previous project documents and tasks, is accessible in various places in the
supplier 360° profile, questionnaire details pages, and advanced views of the projects.
 Note
If your site uses Supplier Performance Management (SPM) projects, those projects also support template
upgrade, but they use a different upgrade process with different functionality. See the Project Template Guide
for details on upgrading SPM projects.
Related Information
How to manage access to the advanced view of supplier management projects [page 372]
How to view supplier registration projects based on previous template versions after template upgrade

Which supplier management projects are eligible for
template upgrade?
In general, a supplier registration or modular supplier management questionnaire project is only eligible for
template upgrade if none of its tasks are currently active.
More specifically, a supplier registration or modular supplier management questionnaire project is eligible for
upgrade if it meets the following conditions:
● The supplier is not deactivated. Suppliers may be deactivated, which disables the ability for them to receive
upgraded templates. All active suppliers will continue to receive template upgrades.
● The project exists. For supplier registration projects, the project exists if the supplier has been invited to
register either automatically, manually, or through mass invitation, or if the supplier has been migrated with
supplier profile questionnaire data. For modular supplier management questionnaire projects, the project
exists if the questionnaire has been sent to a recipient.
● None of the project's tasks has started or all of its tasks have been completed. For projects that allow
updates and have tasks in both new and update phases, this means that either none of the tasks in either
phase have started; that all of the tasks in the new phase have been completed but none of the tasks in the
update phase have started; or that all of the tasks in both phases have been completed.
The following table describes upgrade eligibility by project status:
Upgrade eligibility Registration status Modular questionnaire status
Always eligible for template upgrade ● Invited ● Not Responded

● In Registration ● Denied
● Registration Denied ● Expiring
● Expired
Never eligible for template upgrade ● Not Invited ● Pending Submission

● Pending Approval ● Pending Approval
● Pending Resubmit
Eligible for template upgrade only if an ● Registered ● Approved

update is not in approval
Regardless of project status, a project is never eligible for template upgrade if one of its approval tasks is in
approval.
Note that denied projects show as eligible for upgrade. However, respondents cannot update their questionnaires
as they can for approved projects that are upgraded.
Related Information


How template upgrade affects supplier management
projects
Template upgrades can affect questionnaires, tasks, phases, teams, conditions, and project attributes in supplier
registration and modular supplier management questionnaire projects.
Template upgrade creates a new supplier registration or modular supplier management questionnaire project
based on the current published version of the template and copies the data from the previous project to it. This
new, upgraded project shows in the relevant area of the supplier's 360° profile and in search results for projects of
that type. Links in invitation emails to suppliers automatically point to the new, upgraded project's questionnaires,
and suppliers see the new, upgraded questionnaires when filling out or updating them.
The new, upgraded project is treated as an updated version of the previous project. Questionnaire version histories
include all versions of the questionnaire from all previous projects. The previous project is archived and is
accessible if you view previous project versions in the supplier 360° profile or in project advanced view.
Even if the project template is not configured to allow updates, upgrading registration projects with Registered
status or modular supplier management questionnaire projects with Approved status automatically reopens them
and restarts their tasks one time so that suppliers and internal users can update their questionnaires due to the
upgrade. If the template does not allow updates, any updates made due to the upgrade are processed using the
workflow for new registrations or questionnaires. If the template does allow updates, any updates made due to the
upgrade are processed using the workflow for registration or questionnaire updates. In both cases, the updates
from suppliers and internal users are processed using the tasks defined in the current published version of the
template.
Template upgrade updates projects in Denied status. However, in this case, the projects do not reopen, and
suppliers and internal users cannot update answers. This behavior preserves the original answers that triggered
the denial.
Questionnaires in supplier management project template upgrade [page 127]
Tasks in supplier management project template upgrades [page 128]
Phases in supplier management project template upgrades [page 130]
Teams in supplier management project template upgrades [page 130]
Project attributes and project-level conditions in supplier management project template upgrades [page 131]
Related Information


Questionnaires in supplier management project template upgrade
Supplier management template upgrade can modify questionnaire survey documents and their content.
Supplier registration projects support multiple internal and external (supplier-facing) questionnaires, and template
upgrade can add or remove questionnaires from a project in some cases. Modular supplier management project
support only one external (supplier-facing) questionnaire.
The following table describes how template upgrade modifies questionnaire survey documents and their content in
projects that are eligible for template upgrade:
If you modify this in the template... Template upgrade makes this change in upgraded projects...
Add a new external (supplier-facing) questionnaire survey None. Just as a user cannot manually send a supplier addi
document to a registration project template tional registration questionnaires after the initial invitation,
template upgrade cannot add questionnaires to an existing
registration project post-invitation.
Add a new internal questionnaire survey document to a regis Adds the internal questionnaire.
tration project template
Remove an internal or external questionnaire survey document Removes the questionnaire. The questionnaire and its answers
in a registration project template are retained in the previous, archived versions of those
projects.
Adds, removes, or modifies a question or other piece of con Adds, removes, or modifies the question or other piece of con
tent in a questionnaire tent in the questionnaire. If the content triggers a visibility or
editability condition, the change affects those pieces of con
tent triggered by the condition. For example, if a new question
includes a visibility condition, its addition might hide another
piece of content that was previously always visible.
 Note
If the new version of the template removes a question that
is mapped to a field in the vendor database, the upgrade
removes the question from the questionnaire, but any pre
vious answers stored in the mapped database field remain
after upgrade.
Adds, removes, or modifies a visibility or editability condition Adds, removes, or modifies the condition.
 Note
Performing a template upgrade will not add the Keep questionnaire reopened indefinitely setting to existing
projects. The setting will appear in new projects.
For both internal and external (supplier-facing) questionnaires, if a supplier or internal user has not yet opened the
questionnaire before the template upgrade, they see the updated questionnaire when they first open it. If they have
opened the questionnaire before upgrade and are in the process of filling it out when the upgrade occurs, the
questionnaire loads the changes and they fill out the updated questionnaire before submitting it.

If an internal questionnaire is approved before the template upgrade, internal users see the updated questionnaire
the next time they open it (for example, to revise their responses). If an external (supplier-facing) questionnaire is
approved before the template upgrade, the supplier sees the updated questionnaire the next time they open it and
click Revise Response; simply opening the approved questionnaire does not show the updates.
The notify option allows customer administrators to alert suppliers to update external questionnaires after an
upgrade. There is no notification for internal questionnaires.
Related Information

Tasks in supplier management project template upgrades
Supplier management project template upgrade can add, remove, or modify tasks in supplier registration and
modular supplier management questionnaire projects.
A supplier registration or modular supplier management project is only eligible for template upgrade [page 125] if
none of its tasks have started or all of its tasks have been completed.
For eligible projects that use new and update phases, template upgrade only modifies the tasks in the new phase in
projects where none of the tasks in the new phase have started yet. Once all of the tasks in the new phase have
been completed, template upgrade only modifies tasks in the update phase. It does not modify tasks in the new
phase, even if those tasks have been modified in the new version of the template, since that phase is a one-time
process and any updates that suppliers or internal users make to the project's questionnaires are handled by the
tasks in the update phase.
If the project template does not use new and update phases, project tasks are modified during upgrade and restart
after upgrade so that the respondent can make one-time updates.
The following table describes how template upgrade modifies tasks in eligible projects:

Template upgrade makes this change in
If you modify this in the template... In this phase... upgraded projects...
Add a new approval or To Do task on a No phase (if your project does not use None. Since a new questionnaire cannot
new external (supplier-facing) registra them), new phase, or update phase be added to an upgraded project, the as
tion questionnaire survey document. sociated task is not added either.
Applicable only to registration projects,

which support multiple questionnaires.
Add, remove, or modify an approval or To New phase Adds, removes, or modifies the task in
Do task on an existing external (supplier- projects that include that questionnaire
facing) questionnaire survey document. and have not yet started the new phase.
Makes no change in projects that do not
include that questionnaire or that have
already completed the new phase.
No phase or update phase Adds, removes or modifies the task in all

projects that include that questionnaire.
Makes no change in projects that do not
include that questionnaire.
Add a new approval or To Do task on a New phase Adds the task to projects that have not
new internal registration questionnaire yet started the new phase. Makes no
survey document. change in projects that have already
completed the new phase.
Applicable only to registration projects,
which support multiple questionnaires.
No phase or update phase Adds the task to all upgraded projects.
Adds, removes, or modifies an approval New phase Adds, removes, or modifies the task in
projects that have not yet started the
or To Do task on an existing internal
new phase. Makes no change in projects
questionnaire survey document.
that have already completed the new
phase.
No phase or update phase Adds, removes, or modifies the task in all

upgraded projects.
Adds, removes, or modifies a To Do task New phase Adds, removes, or modifies the task in
(not associated with a questionnaire) in projects that have not yet started the
the template. new phase. Makes no change in projects
that have already completed the new
phase.
No phase or update phase Adds, removes, or modifies the task in all

upgraded projects.
Related Information

Phases in supplier management project template upgrades
Supplier management project template upgrade can add, remove, or modify phases in supplier registration and
modular supplier management questionnaire projects.
If you add new and update phases to a supplier registration or modular supplier management questionnaire project
template, during upgrade:
● The phases are added to eligible projects.

● Any tasks from the previous version that you moved into the phases in the template are moved to the same
locations in eligible projects if they are included in the update. For example, if you move an approval task for an
external (supplier-facing) registration questionnaire to the new registration phase, and that questionnaire was
sent to a supplier who has just been invited to a new registration, it is moved to the new registration phase in
the upgraded project. However, if the questionnaire was not sent to the supplier, or if the supplier had already
completed a new registration, its task is not included in the upgrade at all.
Related Information

Teams in supplier management project template upgrades
Supplier management project template upgrade can add, remove, or modify project teams in supplier registration
and modular supplier management questionnaire projects.
The following table describes how template upgrade modifies teams in supplier registration and modular supplier
management questionnaire projects:

If you modify this in the template... Template upgrade makes this change in upgraded projects...
Add a new project group Adds the new group.
Add a new project group member or role Adds the new project group member or role.
Remove a project group Removes the group only if they do not have any tasks assigned
to them. If a project group has one or more tasks assigned to it
in a project, template upgrade does not remove it.
Remove a project group member or role Removes the project group member or role.
Modify a project owner Modifies membership in the Project Owner group, if applica
ble, in sites that do not use buyer category assignments (team
member rules) to assign membership automatically.
Does not modify the explicit project owner, which remains the
user who created the project.
Related Information

Project attributes and project-level conditions in supplier

management project template upgrades
Supplier management project template upgrade can add, remove, or modify project attributes and project-level
conditions in supplier registration and modular supplier management questionnaire projects.
Template upgrade applies changes to project-level conditions to eligible projects. It adds, removes, or modifies
conditions and modifies project content depending on those changes. For example, if you a add project-level
condition for legacy suppliers to a supplier registration project template and use it to hide an existing To Do task,
upgraded projects for legacy suppliers no longer show that task.
Template upgrade also applies changes to the project attributes defined on the Overview tab of the project
template, such as commodity, region, department, and questionnaire type for modular supplier management
questionnaire project templates.

Related Information

How to upgrade supplier management projects to the latest

template version
Upgrading eligible supplier registration or modular supplier management questionnaire projects from a previous
template version to the currently published version allows you to update them with all of the current template
settings.
Prerequisites
To upgrade supplier management projects to the latest template version, you must be a member of the SM Ops
Template upgrade is only available for supplier registration and modular supplier management questionnaire
projects. Those projects must be eligible for upgrade [page 125].
Template upgrade for supplier registration projects is available by default. Template upgrade for modular supplier
management projects must be enabled in your site.
Context
Template upgrade of registration and external (supplier-facing) modular questionnaire projects includes an option
that allows you to notify the primary supplier contact for each supplier with a project included in that upgrade to let
them know about changes that might need their attention. If you use the notification option, you can insert a
specific message into these notifications to provide details that the supplier might need to know about the
upgrade.
For supplier registration projects, which support multiple external and internal questionnaires, if the previous
version of the template included more than one external (supplier-facing) questionnaire, the upgrade sends a
separate notification for each questionnaire sent to the supplier. The notification references the questionnaire
name, but otherwise uses the same text for all of the external questionnaires included in the upgrade.

 Tip
For registration project template upgrades, since the upgrade generates notifications for all of the registration
project's questionnaires, regardless of whether not they are affected by the upgrade, it's a good idea to
reference questionnaire names in your message when providing details about specific changes to specific
questionnaires.
Before starting the upgrade operation, you choose the type and title of the template whose projects you want to
upgrade. You only have one supplier registration project template in your site, so when you choose the registration
template for the upgrade, there is only one title option and it is the default selection. However, you can have
multiple modular supplier management questionnaire project templates in your site, and you must specify the title
of the template to see the projects that are eligible for upgrade.
Procedure
1. On the dashboard, choose Manage SM Administration .

2. In the left-hand navigation pane, click Template upgrade.
3. On the Project template dropdown menu, choose the type of the template for the upgrade.
4. If you chose Modular questionnaire as the template type, on the Template title dropdown menu, choose the
name of the modular questionnaire template for the upgrade.
5. Click Find projects
The Start upgrade tab displays a table with a row for each previous template version that is in use by at least
one project. Each row shows the total number of projects in the site that are still using that template version
and the number of those projects that are currently eligible for upgrade.
6. Locate the template version that you want to upgrade to the currently published version.
7. (Optional) To notify primary supplier contacts that there are changes to their projects' questionnaires that
require their attention, check Notify.
8. Click Upgrade.
9. If you checked the Notify option, enter a message to insert into the notification to supplier contacts informing
them of template changes that affect them.
10. Click OK to confirm the upgrade.
11. Click the Upgrade status tab to monitor the progress of the upgrade and download status summary
information. The status summary includes the SM vendor IDs of the suppliers associated with the upgraded
projects.
Results
All of the eligible supplier projects using that version of the template are upgraded to the currently published
version. See How template upgrade affects supplier management projects [page 126] for details on how upgrades
modify project questionnaires, tasks, phases, teams, and conditions.
The upgrade might result in respondents revising responses to previously submitted or approved questionnaires.

In projects that do not allow updates, respondents suppliers normally cannot revise previously submitted
questionnaires. However, if the template upgrade modifies the content of a questionnaire in an approved project,
the upgrade operation reopens the questionnaire so that the respondent can revise their responses and resubmit
them, and restarts the associated tasks once the revisions are submitted, for a one-time update.
In projects that do allow updates, respondents can update questionnaires at any time as long as any previous
updates are fully approved. The update process is defined in the project template's update phase.
Denied projects are also upgraded, but their primary supplier contacts are not included in any notifications and
respondents cannot update their questionnaires.
Next Steps
As other projects using the same previous version of the template become eligible for upgrade, usually by being
finally approved or denied, you can repeat these steps to upgrade them to the current version of the template until
all projects on that previous version are upgraded.
Related Information


Topics about setting up supplier requests
About the internal supplier request project template [page 135]
Restrictions, requirements, and helpful hints for setting up the internal supplier request project template [page
136]
About the external supplier request project template [page 139]
Restrictions, requirements, and helpful hints for setting up the external supplier request project template [page
140]
Setting up external supplier request by business unit [page 143]
Default supplier request duplicate checks and setting up custom duplicate checks [page 144]
About the internal supplier request project template

The internal supplier request project template defines the process by which internal users at your company
manually create suppliers in your site. The project template must always include an internal request form with an
approval task.
Internal users with the appropriate permissions create internal supplier request projects by choosing Create
Supplier Request , then submitting the internal supplier request form. The user who creates the internal request
is the explicit project owner as well as a member of the Project Owner project group. There are separate project
templates for external requests, which suppliers create by clicking a custom URL, and internal requests, which your
company’s users create in your site. The different types of request typically require different sets of questions, and
potentially different approval flows. The Create Supplier Request menu action always opens the default
survey document in the Supplier Request Template.
There are separate project templates for external and internal supplier requests because the different scenarios
typically require different forms and different approval flows. Internal users typically create internal supplier
requests because they are interested in working with specific new suppliers for specific reasons, and they can
prove internally-focused information such as purchasing organization, the supplier's applicability to specific
company processes, and so on.
The supplier request process is designed to solicit basic profile information about the supplier: the supplier’s name
and address, the name of at least one contact, which commodities they supply and in what regions, and so on. The
internal supplier request can also solicit information that is specific to your company’s processes, such as the
department that wants to use the supplier, cost center information, and so on. These answers display in the Origin
of the Supplier area of the Overview tab of the supplier 360° profile.
The internal supplier request process is a one-time process. The requester can edit their submitted requests up
until the time that the first approver in the approval flow has approved or denied it. After that, the request is no
longer editable. Approvers cannot edit submitted requests. If a request is approved, the supplier is created based
on its information, and that information is captured in the Origin of the Supplier area. However, if you map a
question in the supplier request to a vendor database field, and you also map a question in a subsequent project

Topics about setting up supplier requests PUBLIC 135
(such as registration) to the same vendor database field, the later answer overwrites the request answer in the
database and is displayed in the subsequent questionnaire.
Deployment of your solution includes an internal supplier request project template with the following default
configuration, which includes an empty request survey document and an approval task. You must edit the template
to define your company's specific processes.
Template element Default configuration
Version and Status Version 1, Active
Documents Supplier request form (an empty survey document with the
form questionnaire type) in Draft status
Tasks Approval for supplier request (an approval task for the inter
nal supplier request form document with members of the
Project Owner group as approvers)
Team The default team has one project group, Project Owner, with
system user aribasystem and the Template Creator user
group as approvers.
By default, membership in these groups is not assigned by

commodity, region, and department.
Related Information
Restrictions, requirements, and helpful hints for setting up the internal supplier request project template [page
136]
Restrictions, requirements, and helpful hints for

setting up the internal supplier request project
template
Internal supplier requests function within a specific supplier management workflow, and there are some
restrictions and requirements in their configuration that ensure they fit successfully in that workflow.
Restrictions
● Use the template's default survey document for the internal supplier request form or questionnaire and create
questions directly in the survey document. The supplier request project template does not support any
additional documents.

136 PUBLIC Topics about setting up supplier requests
● You can add approval tasks in addition to the template's default approval task on the internal request survey
document and chain them together as predecessors, but do not add any other type of task to the template.
The supplier request project template only supports approval tasks on its single survey document.
Requirements
● The following question configurations are required because they are necessary for creating the supplier in the
database once the request is approved:
○ Supplier name, mapped to the vendor.vendorInfo.name1 field in the supplier database. If your site
uses the optional supplier full name feature [page 107], SM-14213, you can map the required name
question to vendor.vendorInfo.fullName instead.
○ Supplier contact first, last name, and email address, mapped to the contact.firstName,
contact.lastName, and contact.email fields in the supplier database.
● If you want to use buyer category assignments (the user matrix) to add approvers to supplier requests, the
following question configurations are required:
○ Supplier commodities, with Commodity as the answer type, mapped to matrix.Categories.
○ Supplier regions, with Region as the answer type, mapped to matrix.Regions.
○ (Only required if your site uses the business unit supplier management matrix enhancement feature)
Supplier departments, with Department as the answer type, mapped to matrix.Departments.
● If your site is integrated with Dun & Bradstreet, see Setting up the internal supplier request for Dun &
Bradstreeet integration [page 388] for additional requirements.
Helpful hints
● SAP Ariba recommends using modular questionnaires for managing supplier certificates. You can include
certificate questions in internal supplier request project templates, but respondents are able to answer "Yes"
without providing details about the certificate. Modular questionnaires require details about a certificate if the
respondent answers "Yes". For more information, see Setting up supplier certificate management using
modular questionnaires [page 201].
● SAP Ariba recommends enabling auto-approval for approval tasks on internal supplier request if you plan to
have the requester also be the approver and if you do not need additional approvers.
● The content in forms is unnumbered, while the content in questionnaires is numbered. Since the internal
request process is the initial stage of your relationship with the supplier and is designed to solicit only basic
information, SAP Ariba recommends using the Form questionnaire format. If you do want to use a
questionnaire, set the survey document's questionnaire format to Questionnaire.
● SAP Ariba recommends that you add no more than 500 pieces of content to an individual questionnaire.
Adding more than 500 pieces of content might cause performance to degrade progressively as you add more
content.
● The survey document in the supplier request project template is automatically internal, regardless of the value
you set for Specify questionnaire type.
● SAP Ariba also recommends asking for the supplier contact's locale based on the locale information in your
site. This locale information allows you 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 contact.locale.

● SAP Ariba's default time zone for supplier contacts is Pacific Daylight Time (PDT), but you can set a different
time zone with a question mapped to contact.timeZoneID. Valid time zone values are defined by master
data in your site.
○ You can allow the requester to set the time zone with a question that has the Acceptable Values setting set
to Master Data Value, the Type of master data for answer setting set to Time Zone, and the Visible to
Participant setting set to Yes.
○ You can set a default time zone with a question that has the Acceptable Values setting set to Master Data
Value, the Response Require? setting set to Not Required, the Visible to Participant setting set to No,
the Type of master data for answer setting set to Time Zone, and the Initial Value setting set to your
desired time zone. The initial value must be an exact match to the master data value.
 Note
○ SAP Ariba defines time zone master data. You can't import custom time zone master data.
○ When a supplier contact becomes public, they can set their own time zone.
○ For private supplier contacts, users with appropriate permission can edit the supplier request contact's
time zone.
● Although it is not required, you can also ask a question for the contact's middle name and map it to
contact.middleName.
● You do not need to publish the internal supplier request survey document. Instead, simply publish the new
template version to activate your changes to the template's survey document.
● If any of your questions involve sensitive data, you can mask the answers [page 297] so that only users with the
appropriate permissions can see them.
● In addition to SAP Ariba's default duplicate check on name, street address, city, state, country, postal code,
and D-U-N-S Number, you can specify additional questions in the internal supplier request for use in the
duplicate check. There are some configuration considerations and requirements [page 144] for both types of
duplicate check.
● If you map a question in the internal supplier request and a question in a supplier registration questionnaire to
the same vendor database field, inviting a supplier to register automatically adds the answer from the request
to the question in the registration questionnaire. Respondents can keep that initial answer or edit it; any
changes they make are then stored in the mapped database field as the current value. This automatic
population of registration questionnaires from the request occurs for questions mapped to vendor database
fields, but not to matrix fields (matrix.Categories, matrix.Regions, and matrix.Departments).
● Keep in mind that once any internal supplier request is approved, its original information is permanently
preserved in the supplier's 360° profile, even if the information in an underlying database field is updated
(through ERP synchronization or updates to a mapped Ariba Network profile field, for example). On the other
hand, the supplier registration template supports ongoing updates to questions in both internal and external
(supplier-facing) questionnaires, including approvals for those updates and the ability to view previous answers
to external questionnaires during approval. Therefore:
○ If you want to record the initial answer in the supplier profile, ask the question in the supplier request.
○ If you want to allow either the supplier or an internal user to update the answer, ask the question in an
external supplier registration questionnaire (for supplier update) or the internal registration questionnaire
(for internal updates) and configure new and updated registration phases in the supplier registration
project template.
○ If you ask the same question in both the internal supplier request and a registration questionnaire, and
map it to the same vendor database field, the supplier's initial answer is added to the Summary area, and
registration questionnaire answer is updated in the database and shown elsewhere.
● You can enable internal users to set ERP profile data in the supplier request, and then maintain it in the internal
registration questionnaire. [page 170]

● You can enable users to set and maintain ERP profile data in questions with answer options populated by
integrated master data [page 248] such as purchasing organization, company code, incoterms, and payment
terms.
● If your questionnaire includes an Extended Address question, the respondent must provide an answer in the
Region field in order to submit the questionnaire.
About the external supplier request project template

The external supplier request project template defines the process by which suppliers ask to be added to your site.
This process, which is sometimes referred to as self-registration, always includes an external request form or
questionnaire with an approval task.
The external supplier request project template is only available in sites with the external supplier request feature
enabled. As external supplier request enablement, SAP Ariba Customer Support provides your company with an
external supplier request URL that is specific to your site. Your company might provide this URL to potential new
suppliers through specific outreach programs, by publishing it on a corporate website, or through other means.
Suppliers create external supplier request projects by clicking the external supplier request URL and filling out and
submitting the external supplier request form. The system user aribasystem is the explicit owner of external
supplier request projects as well as the requester. If the request is approved, the supplier is created in the database.
The external supplier request URL always opens the survey document from the Supplier Self-Registration
Request Template.
There are separate project templates for external and internal supplier requests because each scenario typically
requires different forms and different approval flows. Internal users typically create internal supplier requests
because they are interested in working with specific new suppliers for specific reasons, and they can prove
internally-focused information such as purchasing organization, the supplier's applicability to specific company
processes, and so on. External supplier requests can involve any type of supplier and might not be directly solicited;
suppliers cannot provide internally-focused information, nor is it often desirable to show those questions to them.
You also might want to ask suppliers a specific set of questions to help you categorize them and identify their
usefulness, but omit those questions for internal users to whom they are not relevant. Furthermore, suppliers who
submit external requests might warrant an additional degree of scrutiny, or different scrutiny, during the approval
process.
The external supplier request process is designed to solicit basic profile information about the supplier: the
supplier’s name and address, the name of at least one contact, and so forth. These answers display in the Origin of
the Supplier area of the Summary tab on the Overview tile of the supplier 360° profile.
The external supplier request process is a one-time process. Approvers cannot edit submitted external requests. If
an external request is approved, the supplier is created based on its information, and that information is captured
in the Origin of the Supplier area. However, if you map a question in the external supplier request to a vendor
database field, and you also map a question in a subsequent project (such as registration) to the same vendor
database field, the later answer overwrites the external request answer in the database and is displayed in the
subsequent questionnaire.
The initial enablement of the external supplier request feature in your site adds the external supplier request
project template in a default configuration that includes an empty request survey document and approval task flow.
You must edit the template to define your company's specific processes.

Documents Supplier self-registration request form (an empty survey

document with the Form questionnaire format) in Draft status
Tasks Approval for supplier self-registration request (an empty ap

proval task for the external supplier request form document)
Team The default team has two project groups:
● Project Owner, with system user aribasystem as the only

member.
● Template Creators, with the Template Creator group as
the only member.

Related Information
140]
About the internal supplier request project template [page 135]

setting up the external supplier request project
template
External supplier requests function within a specific supplier management workflow, and there are some
restrictions and requirements in their configuration that ensure they fit successfully in that workflow.
Restrictions
● Use the template's default survey document for the external supplier request form or questionnaire and create
questions directly in the survey document. The external supplier request project template does not support
any additional documents.
● You can add approval tasks in addition to the template's default approval task on the external request survey
document and chain them together as predecessors, but do not add any other type of task to the template.
The external supplier request project template only supports approval tasks on its single survey document.

● Unlike registration and qualification questionnaires, which suppliers fill out on Ariba Network for Suppliers, the
external supplier request is served directly in your site. The external supplier request URL allows suppliers to
access the external supplier request form in your site as guest users for this strictly limited purpose. Although
the external supplier request is supplier-facing, it is not an external questionnaire served on Ariba Network for
Suppliers, and functions in the same way as an internal form does. Therefore, you can only use question or
other content configurations that are supported in internal forms in the external supplier request. You cannot
use question or other content configurations that are supported in external (supplier-facing) questionnaires
that suppliers answer on Ariba Network for Suppliers but not on internal forms.
Requirements
● The following question configurations are required because they are necessary for creating the supplier in the
database once the request is approved:
○ Supplier name, mapped to the vendor.vendorInfo.name1 field in the supplier database. If your site
uses the optional supplier full name feature [page 107], SM-14213, you can map the required name
question to vendor.vendorInfo.fullName instead..
○ Supplier contact first, last name, and email address, mapped to the contact.firstName,
contact.lastName, and contact.email fields in the supplier database.
● If you want to use buyer category assignments (the user matrix) to add approvers to external supplier
requests, the following question configurations are required:
○ Supplier commodities, with Commodity as the answer type, mapped to matrix.Categories.
 Note
Supplier management projects do not support commodity level restrictions in external questionnaires.
Specifying the Allowed Commodity Level property on the template Overview tab does not restrict
acceptable answers for suppliers choosing commodities in external questionnaires.
○ Supplier regions, with Region as the answer type, mapped to matrix.Regions.

○ (Only required if your site uses the business unit supplier management matrix enhancement feature or the
self-registration by business unit feature) Supplier departments, with Department as the answer type,
mapped to matrix.Departments.
Helpful hints
● SAP Ariba recommends using modular questionnaires for managing supplier certificates. You can include
certificate questions in external supplier requests project templates, but respondents are able to answer "Yes"
without providing details about the certificate. Modular questionnaires require details about a certificate if the
respondent answers "Yes". For more information, see Setting up supplier certificate management using
modular questionnaires [page 201].
● Internal users who are not approvers cannot edit external supplier requests. Do not add questions intended for
internal users to external supplier requests; add them to the internal supplier registration questionnaire
instead.
● SAP Ariba does not prepopulate fields in Bank Account questions with values defined by master data in your
site such as country-specific bank IDs or bank control keys, and does not show country-specific fields defined

by master in your site data in Tax questions, in the supplier view of the external supplier request. Suppliers are
unable to complete Bank Account and Tax questions, which rely on this master data. Making these questions
required prevents suppliers from submitting requests.
SAP Ariba does prepopulate these fields for internal users. Approvers can edit external supplier requests to
select master data for these questions during the approval process.
● The content in forms is unnumbered, while the content in questionnaires is numbered. Since the request
process is the initial stage of your relationship with the supplier and is designed to solicit only basic
information, SAP Ariba recommends using the Form questionnaire format. If you do want to use a
questionnaire, set the survey document's questionnaire format to Questionnaire.
content.
● SAP Ariba also recommends asking for the supplier contact's locale based on the locale information in your
site. This locale information allows you 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 contact.locale.
● SAP Ariba's default time zone for supplier contacts is Pacific Daylight Time (PDT), but you can set a different
time zone with a question mapped to contact.timeZoneID. Valid time zone values are defined by master
data in your site.
○ You can allow the requester to set the time zone with a question that has the Acceptable Values setting set
to Master Data Value, the Type of master data for answer setting set to Time Zone, and the Visible to
Participant setting set to Yes.
○ You can set a default time zone with a question that has the Acceptable Values setting set to Master Data
Value, the Response Require? setting set to Not Required, the Visible to Participant setting set to No,
the Type of master data for answer setting set to Time Zone, and the Initial Value setting set to your
desired time zone. The initial value must be an exact match to the master data value.
 Note
○ SAP Ariba defines time zone master data. You can't import custom time zone master data.
○ When a supplier contact becomes public, they can set their own time zone.
○ For private supplier contacts, users with appropriate permission can edit the supplier request contact's
time zone.
● Although it is not required, you can also ask a question for the contact's middle name and map it to
contact.middleName.
● You do not need to publish the external supplier request survey document. Instead, simply publish the new
template version to activate your changes to the template's survey document.
● If any of your questions involve sensitive data, you can mask the answers so that only users with the
appropriate permissions can see them.
● In addition to SAP Ariba's default duplicate check on name, street address, city, state, country, postal code,
and D-U-N-S Number, you can specify additional questions in the internal supplier request for use in the
duplicate check. There are some configuration considerations and requirements [page 144] for both types of
duplicate check.
● If your site uses the external request by business unit feature, there are some specific requirements and
settings [page 143] for that feature.
● Keep in mind that once any supplier request is approved, its original information is permanently preserved in
the supplier's 360° profile, even if the information in an underlying database field is updated (through ERP
synchronization or updates to a mapped Ariba Network profile field, for example). On the other hand, the
supplier registration template supports ongoing updates to questions in both internal and external (supplier-

facing) questionnaires, including approvals for those updates and the ability to view previous answers to
external questionnaires during approval. Therefore:
○ If you want to record the supplier's initial answer in its profile, ask the question in the external supplier
request.
○ If you want to allow the supplier to update their answer, ask the question in an external supplier registration
questionnaire and configure new and updated registration phases in the supplier registration project
template.
○ If you ask the same question in both the external supplier request and an external registration
questionnaire, and map it to the same vendor database field, the supplier's initial answer is added to the
Overview tile, and registration questionnaire answer is updated in the database and shown elsewhere.
● If your questionnaire includes an Extended Address question, you must provide an answer in the Region field
in order to submit the questionnaire.
Related Information

Mapping questions to supplier database fields [page 260]
Mapping questions to Ariba Network supplier profile fields [page 280]
Masking sensitive data in supplier forms and questionnaires [page 297]
Setting up external supplier request by business unit

The external supplier request by business unit feature allows suppliers to see familiar business unit names in the
external supplier request, confirmation pages, and notifications.
If your organization is divided into specialized or regional business units, suppliers might be more familiar with the
name and function of one of those business units than with your organization's overall name and function. For
example, you might do business in a country under a different name, or a variation of your organization's name.
External supplier request by business unit is not enabled by default. When it is enabled and set up in your site:
● Suppliers choose the business unit to which they request to be added when filling out the external supplier
request. After they submit requests, the confirmation screen shows the name of the business unit instead of
your organization's name.
● Request approvals are routed to the appropriate stakeholders in the specific business units specified in the
external supplier requests.
● External supplier request notifications for both suppliers and approvers show the name of the business unit
instead of your organization's name.
To set up external supplier request by business unit, you:
1. Import your business units as department master data: in the Ariba Administrator Site Manager Data
Import/Export task, use the Import Departments data import task to import your business units. For more
information, see the Common data import and administration guide for SAP Ariba Strategic Sourcing and

2. Ask suppliers to choose a business unit in the external supplier request: in the external supplier request
project template survey document, add a Department question and map it to matrix.Departments. The
presence of this question with this mapping in the external supplier request is required.
3. On the Conditions tab of the external supplier request project template, create a condition for each business
unit using a field match on the Departments field and specifying that the match is on a child of the selected
business unit value. Use these conditions to create a parallel, conditional approval node for each business unit
in the approval task or tasks on the external supplier request. For more information, see the Project Template
Guide.
Related Information

140]
How to add a question to a supplier form or questionnaire [page 236]
Topics about creating approval flows in the approval rules editor [page 316]
Default supplier request duplicate checks and

setting up custom duplicate checks
After either an internal or external supplier request is submitted, duplicate checks identify potential matches to
existing suppliers in your site to help prevent the creation of duplicate suppliers. Your internal and external supplier
request setups can affect how these duplicate checks function.
In both internal and external supplier requests, SAP Ariba Supplier Management solutions run default duplicate
checks on the following information:
Information Fields
Name ● vendor.vendorInfo.name1
● vendor.vendorInfo.name2
● vendor.vendorInfo.fullname
 Note
The name fields vendor.vendorInfo.name2,
vendor.vendorInfo.name3, and
vendor.vendorInfo.name4 are not supported for
duplicate check.

Information Fields
Address ● vendor.address.line1
● vendor.address.line2
● vendor.address.line3
● vendor.address.city
● vendor.address.state
● vendor.address.countryCode
● vendor.address.postalCode
Dun & Bradstreet ID vendor.vendorInfo.dunsId
If you add questions with these field mappings to the internal or external supplier request, the answers are used in
duplicate checks. Note that for address fields, you can use either individual text questions mapped to the individual
vendor.address fields or the Address answer type, mapped to vendor.address. However, Extended Address
fields are not used in the default duplicate check.
If your site has the custom duplicate check feature enabled, you can use additional questions in the internal and
external supplier requests for duplicate check using the Enable duplicate check setting. Custom duplicate check
can increase the probability of matching supplier requests to existing duplicate suppliers by contributing additional
variables to matching algorithms. When setting up questions for use in custom duplicate checks, keep in mind the
following considerations:
● There is no need to enable duplicate check manually on questions that are already used in default duplicate
check.
● You can only enable custom duplicate check for questions of answer type Text (single line limited), Whole
Number, Decimal Number, and Yes/No. These questions must be mapped to at least one vendor database
field.
● To avoid overly broad duplicate checks, enable no more than five questions for custom duplicate check.
● To avoid overly broad matching, make sure that any question you enable for custom duplicate check is likely to
yield a unique answer for each supplier; for example, tax ID or national ID.
● The position of the question (top-level or nested within one or more sections) has no effect on custom
duplicate check.
● If your site uses both internal and external supplier requests, and you include the same custom duplicate
check-enabled question in both the internal and external requests, the vendor database field mappings for
both questions must be identical: they must have the same number of mappings, to the same fields, in the
same order. Otherwise, custom duplicate matching does not work properly. Identical mappings are not a
requirement for questions used in the default duplicate check.
How duplicate checks work in submitted supplier requests

Duplicate checks help prevent the creation of duplicate records for the same supplier in the database. After a
requester submits internal supplier request, or a supplier submits an external supplier request, a duplicate check
matches its information to existing suppliers to identify potential duplicates.
The information in the request that contributes to the duplicate check depends on your site's configuration and the
setup of your organization's supplier requests. External supplier requests and duplicate check based on custom
questions are both optional features.

The supplier request duplicate check searches for existing suppliers in your site's vendor database, by a
combination of:
● Exact match to Dun & Bradstreet ID (D-U-N-S Number).

● Strict match to the full supplier name.
● At least a partial match to supplier name followed by a partial or full address match. At least a partial name
match must occur before address matching is attempted.
● If your site uses custom duplicate check, partial matches to answers are also used for custom duplication
check. For custom duplicate check, the answer must match starting with the first character. If the answer
contains any spaces, each space-separated word or group of characters is matched separately, and each must
either fully or partially match starting with the first character.
For example, if your site has an existing supplier with the value "Green Energy Corporation" in a field used for a
custom duplicate check, "Green," Energy," and "Corporation" are all indexed for matching separately. Any
corresponding supplier request answer that starts with "G," "E," or "C" is considered for matching, and answers
such as "Gre," "Energ," and "Corp" are matched. Answers such as "Greed," "Reen," and "Gre Energion" are not
matched.
Matching is case insensitive. The duplicate check scores these different matches based on predefined logic. The
score is expressed as a percentage between 0 and 100, with scores of 70% and above considered strong matches
and scores of less than 70% considered weak matches.
In match scoring, a D-U-N-S Number match scores either 100% for an exact match or 0% for no match. Strict
name matches score 100%, while partial name matches can vary between 0% and 100%. For matches on country,
the duplicate check assigns maximum scores to exact matches but also accepts synonyms, ignoring case, and
scores synonym matches based on degree of similarity to the request answer, with an exact string match scoring
100%. The duplicate check assigns a total matching score to existing, potentially matching suppliers based on all
matching fields.
When the requester submits the supplier request (for internal requests only) and during supplier request approval
(for both internal and external supplier requests), the duplicate check displays the top 20 matching suppliers,
based on match score, in the following order:
● Exact matches (score of 100%) first.

● Partial matches next, in descending order based on score.
 Restriction
● For default duplicate check on supplier D-U-N-S Number, name, and address, the duplicate check cleanses
the values in those fields and replaces newlines, white spaces, and ASCII punctuation with a single space
before matching values to existing suppliers. Because of this cleansing, a new supplier request with a
supplier name of "Supplier A, Ltd." will match an existing supplier name "Supplier A Ltd" but not an existing
supplier named "Supplier A, Ltd.".
● Default duplicate checks match against existing suppliers in the database regardless of how the matching
supplier information was added; however, custom duplicate checks match internal or external supplier
request response data against mapped response data from existing submitted supplier requests. For this
reason, custom duplicate checks do not match against mapped data that originates from sources outside
of supplier requests, such as data import, ERP integration, or other types of questionnaires.
● Individual questions can have custom field mappings, and the supplier responses that duplicate checks
match against are linked to those custom field mappings. Duplicate checks match question responses
against recorded supplier responses that are associated with that question's custom field mapping. As a
result of this, if you delete and recreate a question using the same custom field mapping as the deleted
question, duplicate check can match responses to the recreated question against stored response data
from the deleted question.

● Duplicate checks do not match against denied supplier requests or inactivated suppliers.

Topics about setting up supplier registration
About the supplier registration project template [page 148]
Restrictions, requirements, and helpful hints for setting up the supplier registration project template [page
151]
Configuration considerations for supporting both internal and external registrations [page 155]
How to set up reminders for suppliers to complete a new registration [page 156]
How to set up periodic reminders for suppliers to update a registration questionnaire [page 158]
How to specify a custom sender name for registration invitations [page 160]
How to set up different workflows for new registrations and registration updates [page 162]
Using registration and registration update status in visibility and editability conditions [page 165]
How to prevent suppliers from updating some registration questionnaire answers using editability conditions
[page 166]
Using conditions to set up alternate workflows for manual and mass invited registrations [page 167]
How to streamline the registration questionnaire for legacy suppliers using editability conditions [page 168]
Enabling users to set and maintain associated sets of ERP profile data by mapping question values to other
questions [page 170]
Setting up supplier blocking and unblocking [page 172]
Enabling users to inactivate suppliers by flagging them for deletion in questionnaire answers [page 174]
About the supplier registration project template

The supplier registration project template defines the process by which your company gathers and maintains
detailed profile information about suppliers from both internal users and the suppliers themselves.
The supplier registration project template must always include, at minimum, an external (supplier-facing)
registration questionnaire with an approval task. However, it supports:
● Internal questionnaires: one or more internal-facing questionnaires that users at your company fill out and
submit to maintain information about the supplier that is specific to your company’s processes, including ERP
profile information such as purchasing organization and company code.
● Multiple external questionnaires: one or more external (supplier-facing) questionnaires that suppliers fill out
and submit to provide information such as their locations, ability to provide various goods and services,
adherence or agreement to various standards, certifications, and so forth. In internal registrations, internal
recipients fill out these external questionnaires on behalf of the supplier instead.
In the registration project, internal users can update internal questionnaires at any time as long as a previous edit is
not currently in approval. Unlike other supplier management projects, the supplier registration project also
supports continuous updates to external questionnaires, and you can use separate phases in the template [page

148 PUBLIC Topics about setting up supplier registration
162] to create different workflows for new registrations and registration updates. You can also always upgrade
supplier registration projects to the latest version of the template [page 132], ensuring consistency in supplier
profile data and registration processes for suppliers who registered at different times. These characteristics make
the questionnaires in the supplier registration project the ideal location for maintaining supplier profile information
that can change over time.
Any of the following methods can create a supplier registration project, depending on your site’s setup:
● Manual invitation: when a user with the appropriate permissions clicks Invite or Start internal registration in
the Registration area of the supplier 360° profile and selects one or more available external registration
questionnaires to send. Manual invitations are typically used to register suppliers that were created manually
through supplier requests. In this case, the user who starts the registration is the explicit project owner.
● Mass invitation: when a customer administrator creates a mass invitation wave [page 362] to invite a number
of suppliers at once and chooses one questionnaire from the available external registration questionnaires.
Mass invitations are typically used to onboard your existing suppliers to SAP Ariba Supplier Management
solutions solutions; these suppliers are typically already known to your company and are created in your site
via data import [page 71] or migration. In this case, the user who issues the mass invitation is the explicit
project owner. The primary supplier manager should be part of Supplier Registration Manager group or SM
Ops Administrator group to invite mass invite suppliers.
● Automatic invitation: when the site configuration parameter Automatically start supplier registrations
(Application.SM.AutoStartRegistration) is enabled in your site and an approver approves a supplier
request. In this case, the project owner of the supplier request from which the supplier was created is the
explicit project owner of the resulting supplier registration project in all cases, whether the request has
automatic or manual approval and whether or not it includes a step for validation in an integrated SAP Master
Data Governance for Suppliers (MDG-S) system.
● Participate in a sourcing event: when a supplier with Not Invited registration status attempts to participate in
a sourcing event to which they have been invited, and the site configuration parameter Set minimum
registration status for event participation
(Application.SM.MinimumRegistrationStatusForEventAccess) in your site is configured to require a
minimum registration status of Registered or higher.
● Migration: when a public supplier (a supplier with an associated Ariba Network profile) with a approved
supplier profile questionnaire is migrated. Migrated suppliers are generally suppliers you already work with;
migrating their legacy supplier profile questionnaire data creates registration projects and populates their
questionnaires with that data as specified in your migration configuration. In this case, the owner of the
supplier workspace project from which the supplier was migrated is the explicit project owner of the supplier
registration project.
It is important to keep these different creation scenarios in mind as you create external supplier registration
questionnaires and their approval flows. For example, if your company uses mass invitation, you can create a
separate questionnaire specifically for mass invited suppliers, or you can use conditions in the questionnaire you
use for all suppliers [page 167].
If a question in the supplier request and the question in any external or internal registration questionnaire are both
mapped to the same vendor database field, the registration invitation automatically prepopulates the registration
questionnaire with the answer from the request. The questionnaire respondent can choose to retain the
prepopulated answer or to change it.
 Note
If a mapped question in the supplier request is hidden by a visibility condition at the time of request approval,
its data is not prepopulated in registration questionnaire questions with the same mapping. However, if a

Topics about setting up supplier registration PUBLIC 149
mapped question in the supplier request is hidden because Visible to Participants is set to No, its data is
prepopulated in registration questionnaire questions with the same mapping.
Internal registration questionnaires show as sections of the Summary tab of the Overview tile in supplier 360°
profiles. By default, when a user submits an internal questionnaire, the Summary tab displays the answers
immediately, even if there is an approval flow for the questionnaire and it is not yet approved. In sites that are
integrated with SAP ERP and that are configured to synchronize with the ERP before registration is completed,
mapped answers also synchronize immediately with SAP ERP. There is an optional feature that requires final
approval of any internal questionnaire with approval tasks before synchronizing the mapped answers to an
integrated ERP system.
Users can view completed external registration questionnaires on the Registration tile. Only approvers can see
unapproved questionnaires. After a questionnaire is approved, any user who has permission to view the
Registration tile can see the answers.
Deployment of your solution includes a supplier registration project template with the following default
configuration, which includes an empty external questionnaire survey document and an approval task. You must
edit the template to define your company's specific processes.
Documents Supplier registration questionnaire (an empty survey docu

ment with the questionnaire type) in Draft status
Tasks Approval for supplier registration

questionnaire (an approval task for the supplier registra
tion questionnaire survey document with members of the
Project Owner group as approvers)
group as approvers.

Related Information
Restrictions, requirements, and helpful hints for setting up the supplier registration project template [page 151]
How to set up different workflows for new registrations and registration updates [page 162]
How to prevent suppliers from updating some registration questionnaire answers using editability conditions [page
166]
How to streamline the registration questionnaire for legacy suppliers using editability conditions [page 168]
Enabling users to set and maintain associated sets of ERP profile data by mapping question values to other

Setting up supplier blocking and unblocking [page 172]
Automatically start supplier registrations [page 517]
Set minimum registration status for event participation [page 520]

setting up the supplier registration project template
Supplier registration projects function within a specific supplier management workflow, and need some specific
configurations to ensure that they fit successfully in that workflow. Since they can collect both new and updated
information from both suppliers and internal users, they can also support a number of specialized supplier
management activities.
Restrictions
● The supplier registration project template only supports survey documents. Do not add any other type of
document to it.
● The supplier registration project template only supports To Do and approval tasks. Do not add any other type of
task to it.
● Tasks are not supported for folders or documents within folders in supplier management project templates. Do
not add a task to a folder or document within a folder in supplier management project templates.
● Supplier management projects do not support commodity level restrictions in external questionnaires.
Specifying the Allowed Commodity Level property on the template Overview tab does not restrict acceptable
answers for suppliers choosing commodities in external questionnaires.
● Supplier management projects do not support recurring phases. If you add new registration and registration
update phases to the supplier registration project template, once a new registration is approved, the
registration update phase reopens automatically.
Requirements
● The supplier registration project template must contain at least one external survey document with an
associated approval task.
● If you want to require submission of an internal registration questionnaire as part of the registration workflow,
but you do not want to require approval for it, you can create a To Do task on it. The To Do task ensures that the
task owner must submit the questionnaire to complete the registration. The To Do task is not required for
editing the internal questionnaire, and is not necessary if your registration process does not require that it be
filled out.
● Each external (supplier-facing) questionnaire you use must have an approval task. If you are using multiple
external questionnaires, create separate approval and (optionally) To Do tasks for each of them.
● Unlike the supplier request, qualification, disqualification, and preferred supplier management project, the
supplier registration project does not add team members to project groups based on the user matrix (buyer

category assignments) [page 312]. Those other types of projects are always created by submission of a
questionnaire that can include commodity, region, and department questions. Supplier registration projects,
however, are created through invitation, before a questionnaire is submitted, and therefore have no commodity,
region, or department data set in their project attributes. You must define explicit project team membership in
the registration template for use in approval flows.
● If your site is integrated with Dun & Bradstreet, see Setting up supplier registration questionnaires for Dun &
Bradstreet integration [page 390] for additional requirements.
Helpful hints
● Use the template's default survey document and approval task to define an external (supplier-facing)
registration questionnaire. You can add additional survey documents with a questionnaire type of External to
create multiple supplier-facing questionnaires. Each of these questionnaires is treated separately: they
generate separate registration invitations and must have separate approval and To Do tasks. You can also set
up reminder notifications [page 156] for suppliers who have been invited to register and fill out the
questionnaire but have not yet submitted it.
● SAP Ariba recommends that you use modular supplier management questionnaire projects to collect
certificate information from suppliers rather than creating certificate questions in registration questionnaires.
Collecting supplier certificate information in modular questionnaires provides key benefits that are not
available for certificates collected in registration questionnaires, including expiration schedules and
notifications at both the certificate and questionnaire level and the ability to search for suppliers by certificate
type. For details, see Setting up supplier certificate management using modular questionnaires [page 201].
● Registration managers can either invite a supplier to register to start an internal registration. In an internal
registration, recipients in your organization complete external registration questionnaires on behalf of the
supplier, who is not involved in the registration at all. There are some considerations to keep in mind [page 155]
when setting up supplier registrations, since they might start as internal registrations.
● In the classic supplier 360° profile, each internal registration questionnaire is displayed as a section on the
Summary tab of the Overview tile, with the name of the survey document as the section heading in the user
interface. If your site still uses the classic supplier 360° profile, make sure that the name you give to an internal
questionnaire survey document makes sense in the user interface in this context. Note as well that space on
the Summary tab is limited, and lengthy or numerous internal questionnaires will not display well. These
naming considerations are not an issue in the new supplier 360° profile (SM-14322), where both internal and
external questionnaires show in the Questionnaires table in the Registration area.
● You can use the questionnaire type setting to control whether or not approval or rejection of an internal
questionnaire affects the supplier's registration status. By default, the rejection of any approval task on any
questionnaire in a supplier registration project sets the registration's status to Denied and all of the project's
questionnaires close to further editing. To reopen the registration, a user with permission to work in the
advanced view of the project must manually monitor and reopen the applicable questionnaires. Note that to
see the advanced view of a supplier management project, the Advanced View link for supplier registration
projects must be enabled in your site. If you set Specify questionnaire type to Internal for an internal
questionnaire, this default behavior applies: if an approver rejects the internal survey, the registration changes
to Denied status. However, internal questionnaires have a special questionnaire type, Supplier profile, that
specifies that the questionnaire's approval status does not affect the supplier's overall registration status.
The Supplier profile setting also specifies that the questionnaire is internal, and is useful in cases where your
company's registration process includes continuous internal updates. An approver can reject a particular
update (meaning that its answers are not committed to the database) without changing the supplier's
registration status and closing the registration project to further action. Other internal users then have the
opportunity to submit different updates for approval or rejection going forward.

● For registration updates, you can:
○ You can use phases to set up different workflows for new registrations and registration updates. [page 162]
○ You can use the Send reminders for periodic updates setting in the Timing Rules section of survey
documents for external (supplier-facing) questionnaires to set up periodic reminders for suppliers to
update those questionnaires [page 158].
● For new registrations, the Due Date setting in the Timing Rules section of survey documents for external
(supplier-facing) questionnaires defines the amount of time the supplier contact has to fill out the
questionnaire after the invitation is sent. If the supplier contact does not fill and submit the questionnaire in
that time, the questionnaire closes and the supplier contact can no longer edit it. Reinviting the supplier to
register and sending the same questionnaire reopens it so that the supplier can fill out and submit it again. The
default due date value is 30 days, but you can change that time period by editing the Due Date field in the
questionnaire survey document. This setting is ignored in internal questionnaires, but it does apply to external
registration questionnaires that are sent to internal recipients in an internal registration.
If you have configured phases for new registrations and registration updates, once all of the tasks in the new
registration phase are completed, the external questionnaires associated with that registration automatically
reopen so that the supplier can submit updates. Depending on your site's configuration, the Due Date setting
might also determine how long the questionnaires remain reopened for updates. For details, see Supplier form
or questionnaire closing, reopening, and due dates [page 221].
content.
● The following aspects of mass registration invitations are useful to keep in mind as you set up the supplier
registration project template:
○ The supplier registration project template includes an Is Legacy field. Suppliers who are invited to register
in a mass invitation wave [page 363] are flagged as legacy suppliers. You can use this field to create
project-level conditions for legacy and non-legacy suppliers, and then apply those conditions to both
content in questionnaires and approval flows. These conditions allow you to set up a specialized
registration for existing suppliers for whom you already have profile information, but whom you are
onboarding to SAP Ariba Supplier Management solutions for the first time.
○ Customer administrators who send mass registration invitations can choose which external questionnaire
to send with the wave, but can only send one questionnaire. Sending multiple external questionnaires with
mass registration invitations is not supported.
● Editability conditions are particularly useful in the supplier registration project template. You can use them to
prevent suppliers from updating initial answers [page 166] and to streamline questionnaires for legacy
suppliers [page 168].
● Mapping questions to Ariba Network supplier profile fields [page 280] ensures that when a supplier updates
information in their profile on Ariba Network, the update is also automatically synchronized to their registration
project in your site without any further action from the supplier. Otherwise, the supplier must explicitly update
your registration questionnaire before you see the update in your site. Since suppliers typically update their
Ariba Network profiles with new addresses, additional commodities or regions, and other important
information, but might not take the time to update individual registration questionnaires for their customers,
mapping questions of this type to Ariba Network profile fields ensures that the supplier profile information in
your site is as current as possible.
However, when a supplier updates an Ariba Network profile field that is mapped to a question in a registration
questionnaire, the approval task associated with that questionnaire restarts. If you do not use new registration
and registration update phases in your registration projects, denial of that approval task sets supplier's entire
registration status to Registration Denied. To manage updates from Ariba Network profile changes, as well as
other types of questionnaire updates, set up a separate approval flow in a registration update phase. That way,
approval or denial of individual updates do not affect the supplier's overall registration status.

● Since internal users with the appropriate permissions can always update internal registration questionnaires,
you can use them to enable internal users to:
○ Block and unblock suppliers. [page 172]
○ Set and maintain associated sets of ERP profile data [page 170] such as purchasing organization or
company code details.
○ Set and maintain ERP profile data in questions with answer options populated by integrated master data
[page 248] such as purchasing organization, company code, incoterms, and payment terms.
○ Inactivate suppliers by flagging them for deletion [page 174].
○ Set ERP search terms and keywords. If your site is integrated with SAP ERP, SAP S/4HANA, SAP S/4HANA
Cloud, or SAP MDG-S, you can create up to three questions for search terms in the internal questionnaire
and map them [page 260] to the vendor.vendorInfoExt.searchTerms1,
vendor.vendorInfoExt.searchTerms2, and vendor.vendorInfoExt.searchTerms3 fields in the
supplier database. You can do the same for keywords, mapping them to
vendor.vendorInfoExt.keyWordsText and vendor.vendorInfoExt.additionalKeyWordsText.
The answers to these questions are then synchronized with the search term or keyword fields in the
integrated system. You can also turn these questions into filters for [page 255] supplier searches in SAP
Ariba Supplier Management solutions.
● Your organization can implement custom labels for registration status [page 94].
● You can customize templates for email notifications to suppliers [page 345] to include approver comments
from approval tasks with the [TASK_COMMENT_TEXT] email token.
● By default, registration invitation emails use a system email alias for the sender name, and suppliers might not
recognize the alias. There are two different options for adding a custom sender name to the "From" and "Reply-
To" fields of registration invitations. You can use either or both of these options:
○ Custom default sender name [page 160] settings in survey documents for external questionnaires allow
you to configure a custom default sender name. This name is always used for registration invitations sent
through mass invitation, and is the only way to customize the sender name for those invitations. To make
this setting available, a customer administrator must set the self-service configuration parameter Enable
configurable default sender for supplier invitations [page 518]
(Application.SM.EnableCustomSenderName) to Yes in Intelligent Configuration Manager.
○ If the registration requester feature is enabled in your site and you have also configured a custom default
sender name for an external registration questionnaire, the questionnaire invitation uses the requester
selected by the registration manager during the manual invitation workflow in the "From" and "Reply-To"
fields of the invitation for that questionnaire. If the registration manager does not choose a requester for
the registration, the questionnaire invitation uses the custom default sender name instead. An optional
feature, SM-20904, allows registration managers to choose a requester for the registration in the manual
invitation workflow. The selected registration requester shows in the "From" and "Reply-to" fields in
registration invitations to the supplier. For suppliers created from approved supplier requests, the default
requester is the owner of the supplier request project, who might be a person with whom the supplier
already has a relationship. To have this feature enabled in your site, contact SAP Ariba Support.
You can use the [CUSTOM_SENDER_NAME] email template token to insert the custom sender name or
registration requester into the subject or body of registration invitations as well. The [CUSTOM_SENDER_NAME]
token is only available in sites where the self-service configuration parameter Enable configurable default
sender for supplier invitations [page 518] (Application.SM.EnableCustomSenderName) is enabled. This
token also inserts the name of the registration requester if one is selected during registration invitation, and
otherwise inserts the custom default sender for the questionnaire
.

Related Information
Topics about creating supplier forms and questionnaires [page 220]

Configuration considerations for supporting both

internal and external registrations
Internal and external registrations both use the same supplier registration project template, but suppliers to not
participate in internal registrations. Since registrations can have either internal or external recipients for external
registration questionnaires, there are some considerations to keep in mind when setting up the registration project
template.
In external registrations, a registration manager invites a supplier to register, and the invited supplier contact fills
out and submits external registration questionnaires by creating or logging into an account on Ariba Network.
Registration managers invite suppliers to register when they want to collect detailed profile information directly
from them.
In internal registrations, a registration manager starts a registration on behalf of a supplier and assigns internal
recipients to fill out and submit external registration questionnaires. Registration managers start internal
registrations when they want to onboard and work with a supplier that is low-volume or one-time, is not tech-savvy,
is a government entity or third party, or where they otherwise want to register a supplier without requiring them to
create an account on Ariba Network and complete external questionnaires.
Both types of registration use the same supplier registration project template. Keep the following considerations in
mind when setting it up:
● The supplier registration project template does not support creating conditional content or workflows based
on whether a registration is external or internal. Therefore, plan to use the same registration questionnaire
content and workflow for both types of registrations.
● When registration managers invite suppliers to participate in registrations based on previously-approved
internal registration projects, they cannot change the questionnaires in the project. Therefore, plan to use the
same external registration questionnaires for both types of registrations.
● When making questions or other content required in questionnaires, make sure that both internal and external
recipients can fulfill those requirements.

How to set up reminders for suppliers to complete a
new registration
You can remind suppliers to complete their registrations by setting up reminders in the timing rules of external
questionnaire survey documents in the supplier registration project template.
Prerequisites
To enable registration reminders and edit registration reminder notification templates in individual questionnaires,
you must be a member of the Template Creator group.
To edit registration reminder email notification templates in Manage Administration Event Manager
Messaging Templates , you must be a member of the Customer Administrator group. These templates apply to
all questionnaires where notifications are not individually customized.
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 documents.
Context
In the supplier registration project template, due date settings in the survey documents for external questionnaires
allow you to configure reminders for questionnaire due dates in new registrations. These reminder settings
generate email notifications that are specific to supplier registrations.
If you configure reminders, SAP Ariba sends the following email notifications:
Questionnaire types Notifications
Internal (both internal and supplier profile) Default template survey document reminders, which are
shared with sourcing events
External Specific reminders for new registration completion.
Template creators can customize the messages for individual questionnaires in the Customize Messages area of
the Summary step in survey documents.
You must configure reminders separately for each registration questionnaire for which you want to use them.
Respondents receive a separate notification for each questionnaire in their registration for which reminders are set
up.
Note that you can also configure reminders for external questionnaires in other projects, such as supplier
qualifications and modular supplier management questionnaires. However, those reminders use the same email
notification templates as sourcing events.

Procedure
1. Open the supplier registration project template. If it is not in Draft, create a new version.
2. Click the Documents tab.
3. Click the external registration questionnaire for which you want to configure update reminders and choose
Action Edit .
4. In the Timing Rules area of the Rules step, for the due date, choose Reminder.
5. Click Edit and specify at least one of following settings:
○ Start reminders: Specifies when to send the first reminder. If you enter 0 in this field, no initial reminder is
sent. If this is the only reminder field for which you specify a number other than 0, the system sends one
reminder in total.
○ Send reminders every: Specifies the frequency with which to send reminders in addition to the start and
last reminders. If you enter a number other than 0 for this setting, you must also set either the start
reminder, the last reminder, or both. If this is the only reminder field for which you specify a number other
than 0, the system does not send any reminders.
○ Send last reminder: Specifies when to send the last reminder. If you enter 0 in this field, no final reminder
is sent. If this is the only reminder field for which you specify a number other than 0, the system sends one
reminder in total.
a. Click OK.
6. After you have finished making all necessary changes to the supplier registration project template, publish the
new version.
Results
If a respondent has not submitted a registration questionnaire for which reminders are set up, they start receiving
those reminders at the intervals you specified.
Related Information

How to set up periodic reminders for suppliers to
update a registration questionnaire
To keep supplier profile information current, you can set up external supplier registration questionnaires so that
they generate periodic email notifications reminding suppliers to submit updates.
Prerequisites
To set up update reminders for external supplier registration questionnaires, you must be a member of the
Template Creator group.
You must be working with a new version of the template, so that the template itself is open for editing, to edit its
survey documents.
Context
In the supplier registration project template, update reminder settings in the survey documents for external
questionnaires allow you to define an update interval and specify when and how frequently to send suppliers
reminders to update the questionnaires. These settings only apply to external questionnaires. Update reminders
are not supported for internal questionnaires. Registration update reminder emails are based on a email
notification templates.
You must configure update reminders separately for each external registration questionnaire for which you want to
use them. Suppliers receive a separate update reminder for each external questionnaire in their registration for
which reminders are set up.
The update interval you specify determines when periodic updates are due. For a newly completed registration, the
update intervals for all questionnaires with periodic reminders in the registration start when the overall registration
is finally approved and the supplier moves to Registered status. Subsequent update intervals for each individual
questionnaire start when the most recent update to the questionnaire is finally approved.
For example, if you specify an update interval of 365 days, the first update for a questionnaire is due 365 days after
the final approval of the new registration. If the supplier submits the first update before the end of the first update
interval and it is finally approved, for example on day 200, a new update interval starts for the questionnaire and the
second update is due in 365 days (565 days from the registration completion date).
If a supplier does not submit an update by the end of an update interval, a new update interval cannot start and
they receive no further update reminders. If the supplier subsequently submits an update on their own after the
end of the previous update interval, a new update interval starts at that point and the supplier receives the
associated reminder for the next update.
 Tip
If you have not enabled the Keep questionnaire reopened indefinitely setting for an external questionnaire, it
automatically closes to further updates in the amount of time specifies in the site configuration parameter
Application.AQS.RFX.ReopenIfClosedInterval (set by SAP Ariba Support). When setting up periodic

update reminders for a questionnaire, either enable the Keep questionnaire reopened indefinitely setting or
make sure that the reminder interval you set is shorter than the amount of time specified in your site's
Application.AQS.RFX.ReopenIfClosedInterval setting. Otherwise, it is possible to send reminder
updates for a closed questionnaire that the supplier cannot update.
Procedure
3. Click the external registration questionnaire for which you want to configure update reminders and choose
Action Edit .
4. In the Timing Rules area of the Rules step, choose Yes for Send reminders for periodic updates.
5. Specify the update interval.
6. Choose Reminder.
7. Click Edit and specify at least one of following settings:
○ Start reminders: Specifies when to send the first reminder. If you enter 0 in this field, no initial reminder is
sent. If this is the only reminder field for which you specify a number other than 0, the system sends one
reminder in total.
○ Send reminders every: Specifies the frequency with which to send reminders in addition to the start and
last reminders. If you enter a number other than 0 for this setting, you must also set either the start
reminder, the last reminder, or both. If this is the only reminder field for which you specify a number other
than 0, the system does not send any reminders.
○ Send last reminder: Specifies when to send the last reminder. If you enter 0 in this field, no final reminder
is sent. If this is the only reminder field for which you specify a number other than 0, the system sends one
reminder in total.
a. Click OK.
8. After you have finished making all necessary changes to the supplier registration project template, publish the
new version.
Results
In registration projects, registered suppliers receive email notifications reminding them to update the questionnaire
at the intervals and frequency you specified. These reminders show on the Event Messages tab in the advanced
view of individual registration projects. Note that to see the advanced view of a supplier management project, the
Advanced View link for that project type must be enabled in your site and you must have appropriate group
membership permissions. For more information, see How to manage access to the advanced view of supplier
management projects [page 372].

Related Information

How to specify a custom sender name for

registration invitations
By default, registration invitation emails use a system email alias for the sender name, and suppliers might not
recognize the alias. Specifying a custom sender name that the supplier recognizes, such as a clearly labeled
onboarding group or other name, helps registration invitations get suppliers' attention.
Prerequisites
The self-service site configuration parameter Enable configurable default sender for supplier invitations [page
518] (Application.SM.EnableCustomSenderName) must be enabled in your site.
To specify a custom default sender name for an external registration questionnaire in the supplier registration
project template, you must be a member of the Template Creator group.
Context
You can specify custom default sender names for the invitations to external registration questionnaires in their
survey documents in the supplier registration project template. The custom default sender name replaces the
generic system sender name in the following places in the "From" field in registration invitation notifications.
Depending on how a supplier is created and invited to register, the explicit registration project owner might be the
customer administrator who sent a mass registration invitations, the registration manager who manually invited a
supplier to register, or the supplier requester. Especially in the case of mass registration invitations, the supplier
might not recognize the sender name and might therefore ignore the invitation.
For mass or automatic registration invitations, the only way to specify a custom sender name is by using the
Sender name used for the 'From' and 'Reply To' fields in emails to participants setting in the Message Board
area of the Rules step in the survey documents for external questionnaires. The Other sender name you specify in
that setting is always the default custom sender name for the questionnaire.
 Note
● If you specify an Other sender name for the Sender name used for the 'From' and 'Reply To' fields in
emails to participants setting, make sure that the Email address used for the ‘From’ and Reply To fields
in emails to participants setting is not set to Owner email address.

If the sender selection during manual registration invitation feature (SM-20904) is also enabled in your site, the
registration manager can choose the requester, and that selection overrides the template-configured default
sender name. If you do not specify a custom default sender name in the template survey document and the
registration manager does not choose a requester when manually inviting the supplier to register, the notifications
for that questionnaire use the generic system sender name.
You must configure custom sender names separately for each external registration questionnaire for which you
want to use them. Suppliers receive separate questionnaire-level notifications for each external questionnaire in
their registration.
This setting applies only to those email notifications that you customize in individual questionnaire template survey
documents or in Event Manager Messaging Templates task in Ariba Administrator, which include
registration invitations and new registration reminders. It does not apply to email notifications that you configure in
the Project Manager Project Email Templates task, which include notifications of registration approval and
requests for additional information during approval. Those notifications continue to use the generic system sender
name.
 Tip
You can use the [CUSTOM_SENDER_NAME] email template token, which is available for these message
templates, to insert the custom sender name you specify here into notification emails.
Procedure
3. Click the name of an external registration questionnaire and choose Edit.
4. Click Rules and navigate to the Message Board area.
5. For the Sender name used for the 'From' and 'Reply To' fields in emails to participants setting, choose
Other sender name.
6. Enter the custom default sender name you want to show in registration invitations for the questionnaire.
7. Click Exit, then click Save and then exit.
Results
Once you publish the new version of the template, registration invitation notifications for the questionnaire show
the sender name you specified in the From" field by default.
Next Steps
To add this setting to existing registration projects, a customer administrator can upgrade those projects to the
latest template version [page 123].

Related Information

How to set up different workflows for new

registrations and registration updates
Supplier registration projects support the use of different types of phases to manage separate sets of tasks for new
registrations and registration updates.
Prerequisites
To add phases and tasks in the supplier registration template, you must be a member of the Template Creator
group.
Context
The supplier registration project template supports phases with special New Registration and Registration
Update settings to control the order in which the phases start and whether the tasks in a phase are one-time-only
(for new registrations) or recur (for every registration update). The New Registration phase starts one time,
immediately when the supplier is invited to register. Registration Update phases start again every time a supplier
updates a registration questionnaire.
Within the new registration and update phases, you can add separate approval and To Do tasks on the same
questionnaire survey documents to define their workflows in new and updated registrations. For example, for an
external registration questionnaire, you can set up an approval task with a full approval flow involving all relevant
stakeholders in the new registration phase, and an approval task with a more streamlined approval flow in the
update phase. The order in which tasks appear in a phase on the template Tasks tab does not affect the order in
which they start. You can chain the tasks in a phase together as predecessors to define the order in which they start
and create a workflow.
You can create multiple registration update phases to group tasks for different registration questionnaires, or you
can keep all update-related tasks in a single update phase. Regardless of how you organize update-related tasks,
when a supplier or internal user updates a registration questionnaire, that update only starts the tasks that are
associated with that questionnaire. After tasks for an individual external questionnaire update are completed,
approved answers are committed to the supplier database and synchronized to the integrated ERP system
regardless of the status of the overall update phase or of the other questionnaire tasks in it. Approval tasks on
external questionnaires in registration update phases do not include an option to deny the questionnaire. The
status of the overall registration update is still based on the entire workflow defined by all of the tasks in registration
update phases.

 Note
Questionnaire updates submitted using questionnaire data import or the Supplier Data API with Pagination do
not trigger approval or other tasks.
When setting up registration phases and their tasks, keep the following in mind:
● The use of phases is only supported in supplier registration projects. These phases do not use the Subscribe
For, Rank, or Predecessor settings. The new registration phase always proceeds registration update phases.
● If you use phases, make sure that all of the template tasks are inside either the new registration phase or an
update phase. If you use these phases in the registration project, adding tasks outside of them is not
supported.
● Make sure that the tasks you specify as predecessors are within the same phase. Do not make tasks in one
phase predecessors of tasks in a different phase.
● You cannot apply conditions to registration tasks or phases.
 Note
As part of setting up different workflows for new and updated registrations, you can also use editability
conditions [page 165] to make different questions either hidden or read-only.
Procedure
2. Click the Tasks tab.
3. Create a phase for new registrations by performing the following steps:
a. Click Actions Create Phase .
The Create Phase page opens.

b. Enter a name for the phase, such as New Registration.
c. Check only the New Registration option.
d. Click OK.
The new phase, indicated by the unstarted phase icon (), appears on the Tasks tab.
4. Move the registration template's default approval task and any other existing tasks that you want to use for
new registration by dragging and dropping them into the new registration phase. Add new tasks as needed.
If you are using two conditional approval tasks for the registration questionnaire to define different approval
flows for mass invited (legacy) and non-legacy suppliers [page 167], make sure that they are both in the new
registration phase.
5. Create at least one phase for registration updates by performing the following steps:
a. Click Actions Create Phase .

b. Enter a name for the phase, such as Updated Registration.
c. Check only the Registration Update option.
d. Make sure that Recurring Schedule is set to No. Tasks in this phase automatically restart with every
registration update.

e. Click OK.
6. Add an approval task for the registration questionnaire updates by performing the following steps:
a. On the Tasks tab, click the registration questionnaire and choose Create New Tasks Approval .
b. Enter a name for the task.
c. Define an approval flow or, if you want to automatically approve registration updates, choose Yes for Allow
auto approval.
d. Specify other settings for the task as needed and click OK.
The new approval task is created on the Tasks tab outside of the phases.
e. On the Tasks tab, drag and drop the new approval task into the update phase.
7. Add other To Do or approval tasks to the phase as needed.
8. After you have finished making changes to the supplier registration template, publish it.
Results
When a supplier is first invited to register, the new registration phase starts. Final approval of the new registration
automatically completes the new registration phase.
In sites that do not use the new supplier 360° profile, after the new registration phase is completed, submitting an
update to a registration questionnaire starts all tasks in all update phases, even those associated with other
questionnaires. The update phases are completed when all questionnaires are resubmitted and all tasks in them
are completed. Respondents cannot update individual questionnaires again until all tasks for the current update
are completed.
In sites that use the new supplier 360° profile, after registration phase is completed, submitting an update to a
registration questionnaire starts only those tasks in an update phase that are associated with that questionnaire.
After those tasks are completed, respondents can update the questionnaire again.
Related Information


Using registration and registration update status in
visibility and editability conditions
You can create conditions based on registration status and registration update status in the supplier registration
template. You can then apply those conditions as either editability or visibility conditions based on whether the
supplier is registering for the first time or updating the registration questionnaire.
A visibility condition hides content by default, and only show it when the condition is met. Hidden content is hidden
from both suppliers and internal users. An editability condition makes an answer read-only by default, and only
allows participants to edit it when the condition is met. Read-only content is always visible to participants.
For example, the registration questionnaire might contain questions requiring suppliers to agree to certain terms
and conditions; you can make those questions editable in new registrations but hide them in updates so that
suppliers cannot change their answers later. Or you might want to create follow-up questions that only show when
a supplier updates the answers to certain questions.
The following table describes the status fields and values that you can use to build field match conditions for initial
and updated registrations:
Field Description
Registration Status Conditions based on this field can be triggered by matches to

the following registration statuses:
● No Choice
● Not Invited
● Invited
● In Registration
● Pending Approval
● Registered
● Registration Denied
Registration Update Status Conditions based on this field can be triggered by matches to
the following registration update statuses:
● No Choice
● Pending Approval
● Approved
● Denied
 Note
Do not use project-level conditions on registration approval tasks to define different approval flows for initial
registrations and registration updates. Use registration phases instead [page 162].

Related Information
Using visibility conditions to show or hide content based on answers [page 299]
How to prevent suppliers from updating some registration questionnaire answers using editability conditions [page
166]
How to prevent suppliers from updating some

registration questionnaire answers using editability
conditions
You can use editability conditions to prevent suppliers from updating their initial answers when the update the
registration questionnaire. The questions and their initial answers remain visible to both suppliers and to your
company's internal users.
Prerequisites
To create project-level conditions and edit template survey documents, you must be a member of the Template
Creator or Customer Administrator group.
Context
Visibility conditions based on registration status can hide questions from suppliers who are updating the
registration questionnaire after their initial registration. However, if the question is hidden from the supplier during
the update, both the question and the supplier's original answer are also hidden from your company's internal
users when they review the supplier's registration.
If you apply an editability condition based on registration status instead, the questions and the supplier's initial
answers are visible to both suppliers updating the questionnaire and to your company's internal users. However,
the supplier cannot change their initial answers.
By default, all questions are editable. If you apply an editability to the question, it is only editable when the condition
is met, and otherwise cannot be edited.
Procedure
2. If the template does not already include a project-level condition for registered suppliers, create one by
performing the following steps:

a. Click the Conditions tab.
b. Click Add Condition.
c. Enter a name and description for the condition.
d. In the expression editor, choose None Is True.
e. Click the action triangle button () next to None Is True and choose Add Condition Field Match .
A new condition component for selecting the field appears.

f. Click Select and choose Select Other Fields more fields .
g. In the field browser, to the right of the Registration Status field, click Select.
h. For the operator, choose is equal to.
i. Click the Select menu to the right of (No Value Selected) and choose Select Value.
j. From the Registration Status dropdown menu, choose Registered and click OK.
k. Click OK to create the condition.
4. Click the external (supplier-facing) registration questionnaire survey document and choose Action Edit .
5. Click Content.
6. Add or edit a question that you do not want already-registered suppliers to be able to update.
7. For the Editability Conditions setting, choose none Select Condition Other .
8. To the right of the editability condition for new suppliers you just created, click Select.
9. Continue to add or edit questions in the supplier registration questionnaire as needed and apply the new
supplier condition to any questions you do not want already-registered suppliers to be able to update.
Related Information
Using conditions to set up alternate workflows for

manual and mass invited registrations
You can use the Is Legacy project field in the supplier registration project template to create conditional tasks,
documents, and questionnaire content in registration projects for manual and mass invited suppliers.
Suppliers that are created manually through approved supplier requests and are then invited to register individually
are typically unknown, and your main registration process is designed to solicit complete information from them
and have them vetted by a full set of approvers. Mass registration invitations [page 362] are designed to quickly
bring a large number of suppliers into your SAP Ariba supplier management solution; these suppliers might have
been created by being imported from another of your company's systems, in which case you already have some of
their information. If you plan to use mass registration invitations to onboard existing suppliers, you can create a
separate, conditional registration process for them in order to streamline the process..
Supplier registration projects include a special Is Legacy field that you can use to create both project and visibility
conditions (for example, legacy and non-legacy). You can then use those conditions to:

● Create separate approval flows for legacy and non-legacy supplier registrations. Conditions based on the Is
Legacy field do not work in approval flows, so you cannot use them to create conditional approval flows in a
single approval task. However, you can create two separate approval tasks on the registration questionnaire
document and apply the conditions to the approval tasks.
● Show different questionnaire content to legacy and non-legacy suppliers by applying visibility conditions in the
● Make some questionnaire content read-only for legacy or non-legacy suppliers by applying editability
conditions in the questionnaire survey document.
● Use the conditions in To Do tasks and on internal survey documents.
 Note
Content that is hidden from the supplier is also not visible to internal users. Hidden or read-only content also
continues to be hidden or read-only not only in new registrations but in all subsequent registration updates.
All suppliers that are invited to register through the mass invitation feature or are migrated from supplier
organizations are marked as legacy suppliers, while all suppliers that are invited to register following an approved
supplier request are marked as non-legacy suppliers. The registration projects created for both sets of suppliers
will automatically apply the conditions you create based on the Is Legacy field.
For more information about project-level conditions, see the Project Template Guide.
Related Information
Using editability conditions to control the editability of answers in a form or questionnaire [page 304]
How to streamline the registration questionnaire for

legacy suppliers using editability conditions
You can use editability conditions to allow the suppliers you already work with to skip the questions in the
registration questionnaire that apply to new suppliers. Both suppliers and internal users can see the questions, and
if you import or migrate your legacy suppliers' previous answers, they are also visible.
Prerequisites
To create project-level conditions and edit template survey documents, you must be a member of the Template
Creator or Customer Administrator group.

Context
All suppliers who are either migrated from supplier organizations or invited to register through the mass invitation
feature are marked as legacy suppliers, while all suppliers who are invited to register following an approved supplier
request are marked as non-legacy suppliers. You can therefore use the Is Legacy field to create project-level
conditions to streamline the registration questionnaire for those known suppliers, since you already have some of
the information you otherwise use the questionnaire to solicit from new suppliers.
Visibility conditions can hide questions from legacy suppliers and show them to new suppliers. However, if you
apply a visibility condition based on the Is Legacy field, the question and answer are also hidden from your
company's internal users when they review the registration questionnaires of legacy suppliers.
If you apply an editability condition for new suppliers instead, the questions (and any imported or migrated
answers) are visible to both legacy suppliers and to internal users who review the registration questionnaire.
However, the legacy suppliers cannot edit them and can therefore skip them, even if they are required questions
Any imported or migrated answers are also visible. New suppliers, on the other hand, can edit the questions to
answer them, and must answer them if they are required.
By default, all questions in the supplier registration questionnaire and editable. If you apply an editability to the
question, it is only editable when the condition is met, and otherwise cannot be edited.
Procedure
2. If the template does not already include a project-level condition for new (non-legacy) suppliers, create one by
performing the following steps:
a. Click the Conditions tab.
b. Click Add Condition.
c. Enter a name and description for the condition.
d. In the expression editor, choose All are true.
e. Click the action triangle button () next to All Are True and choose Add Condition Field Match .

f. Click Select and choose Select Other Fields more fields .
g. In the field browser, to the right of the Is Legacy field, click Select.
h. For the operator, choose is equal to.
i. Click the Select menu to the right of (No Value Selected) and choose Select Value.
j. Choose No and click OK.
k. Click OK to create the condition.
4. Click an external (supplier-facing) registration questionnaire survey document and choose Action Edit .
5. Click Content.
6. Add or edit a question that you want new suppliers to answer but legacy suppliers to skip.
7. For the Editability Conditions setting, choose none Select Condition Other .
8. To the right of the editability condition for new suppliers you just created, click Select.

9. Continue to add or edit questions in the supplier registration questionnaire as needed and apply the new
supplier condition to any questions you want legacy suppliers to be able to skip.
Results
When you publish the template, new suppliers are able to edit and answer the questions to which you applied the
editability condition, and must answer it if it is required. Legacy suppliers can see the question but cannot edit it
and are able to skip it, even if it is otherwise required. In both cases, internal users reviewing the registration are
able to see the question.
Enabling users to set and maintain associated sets

of ERP profile data by mapping question values to
other questions
A special syntax in supplier field mappings allows you to map one question answer to another question answer.
This mapping allows internal users to set and maintain associated sets of ERP profile data for sectors or vendor
database classes such as purchasing organization and company code in supplier management questionnaires.
Mapping question values to other questions is designed to support maintaining ERP supplier profile data in SAP
Ariba Supplier Management solutions in a very specific scenario where a user sets the initial details associated with
a lookup key field value for a supplier, and then they or another user updates the associated details in the internal
supplier registration questionnaire when necessary.
The question answers to which you map other question answers must themselves be mapped to the lookup key
field for an array class in the vendor database [page 279], such as
vendor.purchasingOrg.purchasingOrganisationID or vendor.companyCode.companyCode. The
questions that you map to the lookup key field question must be about detail fields in the same array class, such as
vendor.purchasingOrg or vendor.companyCode.
To map question values to other questions, you use the following syntax in the Supplier Field Mapping field on the
Add Questions page:
vendor.arrayClass($answer.lookupKeyQuestionNumber).fieldName
lookupKeyQuestionNumber is always the number of the question on the survey document content table. For
example, the first question in section 4.1 is numbered 4.1.1.
 Note
Questions are always numbered in the order in which they appear in the content table of template survey
documents, and inclusion in sections affects question numbering. Note that adding a new question ahead of a
mapped lookup key question, changing its position in a list of questions, or moving it in or out of a section will
change its numbering. If this occurs, you must update the mappings in all questions that reference it.

Setting up the questions that establish initial values between associated fields
You can set up the questions that establish initial values between associated fields either in the supplier request or
the internal supplier registration questionnaire. These two scenarios require different mapping configurations for
the lookup key field question.
To set up the questions in the supplier request: You first create a question about the lookup key field, and then
map it to both the lookup key field and to itself. For example, you can create question 5.1.1 about the supplier's
purchasing organization ID, mapping it both to the lookup key field in the vendor database and itself:
vendor.purchasingOrg($answer.5.1.1).purchasingOrganisationID
This mapping establishes that the answer to the purchasing organization ID question is the value associated with
any mapped detail questions.
To set up the questions in the internal registration questionnaire: You first create a question about the lookup
key field and then map it only to the lookup key field. For example, you can create question 5.1.1 about the supplier's
purchasing organization ID, mapping it to vendor.purchasingOrg.purchasingOrganizationID.
 Tip
If you ask the questions that set the initial values in the internal registration questionnaire, consider putting
them in a section with a title makes that purpose clear, so that they are distinguished from the second set of
questions in the same questionnaire that update the values.
In both cases: Typically, you create a list of choices for the answers to the initial lookup key question, so that users
must choose from a list of valid purchasing organization IDs. You can allow users to choose multiple answers to this
question.
Next, you create questions about detail fields in the same array class and map them to both the associated vendor
database field and the lookup key answer. For example, you can create questions 5.1.2 about the purchasing
organization payment terms and question 5.1.3 about the purchasing organization's currency code, and map them
to the purchasing organization ID answer:
vendor.purchasingOrg($answer.5.1.1).incoTerms
vendor.purchasingOrg($answer.5.1.1).purchaseOrgCurrencyCode
Typically, you also create lists of choices for the answers to these questions so that users must choose from lists of
valid values, specifying that users must choose only one value for each answer.
In this example, a user might create a supplier request or submit the initial internal registration questionnaire and
choose both P20 and P30 as purchasing organization IDs for the supplier, then choose 60 days for the payment
terms and USD for the currency code. The mapping associates a 60 day purchasing organization payment term
and a currency code of USD with both purchasing organization IDs P20 and P30. After the questionnaire is
approved, these values display on the ERP Profile tab of the supplier's 360° profile and are synchronized to any
integrated SAP ERP system.

Setting up the internal supplier registration questionnaire to maintain and update values
between associated fields
Creating duplicate mapped questions in the supplier internal registration questionnaire allows internal users to
update the initial values set by the first set of questions. Internal users with the appropriate permissions can edit
the internal registration questionnaire at any time to update those values.
In the internal registration questionnaire, you first create a duplicate question about the lookup key field. However,
unlike in the initial set of questions, you do not map it to anything. The self-referential mapping in the initial
question associated the mapped detail answers with the lookup key answer, while the second question is designed
simply to specify which lookup key value will have updated details. A separate mapping in the second lookup key
question in the internal registration questionnaire would allow a new user's answer to replace the original
purchasing organization IDs, which is why you omit it in this case. For example, you can create question 8.3.1 about
which purchasing organization ID to update information about and leave the Supplier Field Mapping field blank.
Next, you create duplicate questions about the detail fields in the same array class and map them to both the
associated vendor database field and the answer to the second lookup key question. For example, you can create
questions 8.3.2 about the purchasing organization payment terms and question 8.3.3 about the purchasing
organization's currency code, and map them to the purchasing organization ID answer:
vendor.purchasingOrg($answer.8.3.1).incoTerms
vendor.purchasingOrg($answer.8.3.1).purchaseOrgCurrencyCode
In this example, a user might edit the internal registration questionnaire and choose the purchasing organization
P30, then change the currency code answer to EUR. After the update is approved, purchasing organization P20 still
has a payment term of 60 days and a currency code of USD. But purchasing organization P30 now has a payment
term of 60 days and a currency code of EUR. The updated values display on the ERP Profile tab of the supplier's
360° profile and are synchronized to any integrated SAP ERP system.
 Tip
If you ask the questions that set the initial values in the internal registration questionnaire, consider putting the
update questions in a section with a title makes that purpose clear, so that they are distinguished from the first
set of questions in the same questionnaire that set the initial values.
Setting up supplier blocking and unblocking

Blocking offers a way of indicating that your company does not currently want to transact with a supplier, typically
because of an issue that has a potential resolution. It is a less drastic step than deactivating a supplier.
 Note
At this time, SAP Ariba Supplier Management solutions do not enforce supplier blocks; for example, users can
still invite blocked suppliers to sourcing events and create contracts and purchase orders for blocked suppliers
in solutions where those features are available. However, blocking and unblocking does provide a visual
indicator of a supplier's blocked status in their ° profile.

To set up supplier blocking and unblocking, you create Yes/No questions in the internal registration questionnaire
and map them to blockedIndicator fields in the vendor database. There are five types of blocks you can set up:
Field mapping Description
vendor.vendorInfoExt.commonBlockedIndicato A central block on the supplier.

r
vendor.vendorInfoExt.postingBlockedIndicat A payment block on the supplier.

or
vendor.vendorInfoExt.purchasingBlockedIndi A purchasing block on the supplier.

cator
vendor.companyCode(company A company code-specific block on the supplier.

code).blockedIndicator
vendor.purchasingOrg(purchasing A purchasing organization-specific block on the supplier.

organization
ID).purchasingBlockedIndicator
You must use answer type Yes/No for questions mapped to these fields.
The common, payment, and purchasing blocks are general. Blocks by company code and purchasing organization
are specific to a single purchasing organization ID or company code, and you must set them up by:
1. Creating a separate Yes/No question for every purchasing organization ID or company code. You can use
visibility conditions to show only the question that applies to the specific purchasing organization ID or
company code selected in another question. For example, you might create a question called Block for
CC1? or Block for P1? that is only shown when a user selects CC1 or P1.
2. Mapping each question to the corresponding purchase organization ID or company code value using
parentheses; for example, vendor.companyCode(CC1).blockedIndicator or
vendor.purchasingOrg(P1).blockedIndicator.
When a category or supplier manager edits the internal registration questionnaire to block a supplier (by answering
Yes) or unblock a supplier (by answering No), the supplier 360° profile shows the current blocking status for the
supplier as an answer to the mapped question. The blocked statuses for the
vendor.companyCode.blockedIndicator and vendor.purchasingOrg.purchasingBlockedIndicator
fields also show in the company code and purchasing organization details on the ERP Profile tab of the supplier
360° profile overview.
 Note
If your site is integrated with SAP ERP, your integration synchronization settings determine when a supplier in
SAP Ariba Supplier Management solutions is initially synchronized with SAP ERP. Until that initial
synchronization occurs, SAP Ariba Supplier Management solutions do not receive or send blocked indicators,
and the supplier is only blocked or unblocked in SAP Ariba Supplier Management solutions.

Enabling users to inactivate suppliers by flagging
them for deletion in questionnaire answers
Flagging a supplier for deletion can inactivate the supplier in the SAP Ariba vendor database or set a deletion flag
for a specific company code or purchasing organization, depending on the deletedIndicator mapping you use
in the question.
To allow users to flag suppliers for deletion, you create Yes/No questions in the internal registration questionnaire
and map them to deletedIndicator fields in the vendor database. SAP Ariba Supplier Management solutions
supports the following three deletion indicators:
Field mapping Description
vendor.vendorInfoExt.supplierDeletedIndica Flags the supplier for overall deletion and inactivates it in the
tor SAP Ariba vendor database.
vendor.purchasingOrg(purchasing Flags the supplier for deletion for a specific purchasing organi
organization ID).deletedIndicator zation.
vendor.companyCode(company Flags the supplier for deletion for a specific company code.
code).deletedIndicator
To set up the internal registration questionnaire so that users can use it to set deletion flags, you must use answer
type Yes/No for questions mapped to these fields.
Deletion flags by company code and purchasing organization are specific to a single purchasing organization ID or
company code. There are two different ways you can set them up. The first involves using individual questions for
different purchasing organizations or company codes and performing the following steps:
1. Creating a separate Yes/No question for every purchasing organization ID or company code. You can use
visibility conditions to show only the question that applies to the specific purchasing organization ID or
company code selected in another question. For example, you might create a question called Delete for
CC1? or Delete for P1? that is only shown when a user selects CC1 or P1.
2. Mapping each question to the corresponding purchase organization ID or company code value using
parentheses; for example, vendor.companyCode(CC1).deletedIndicator or
vendor.purchasingOrg(P1).deletedIndicator.
The second involves using question mappings [page 170] to associate initial deletedIndicator values with
specific purchasing organization IDs or company codes and then update them later.
When a user edits the internal registration questionnaire to delete a supplier (by answering Yes to the question
mapped to vendor.vendorInfoExt.supplierDeletedIndicator, once the questionnaire update is
approved, the supplier is inactivated in the SAP Ariba. When a user edits the internal registration questionnaire to
delete a supplier for a specific purchasing organization or company code (by answering Yes to a question mapped
to a purchasing organization or company code deletion indicator), the deletion flag shows in the company code or
purchasing organization details on the ERP Profile tab of the supplier 360° profile overview.
 Note

synchronization occurs, SAP Ariba Supplier Management solutions do not receive or send deletion flags, and
deletion flags are only set for the supplier in SAP Ariba Supplier Management solutions.
Related Information
Inactivating and reactivating suppliers [page 368]

Topics about setting up supplier qualifications
About the supplier qualification project template [page 176]
Restrictions, requirements, and helpful hints for setting up the supplier qualification project template [page
178]
Setting up the prequalification questionnaire [page 180]
About the supplier qualification project template

The supplier qualification project template defines the process by which your company qualifies suppliers for
specific combinations of commodities, regions, and departments.
The supplier qualification project template must always include an external (supplier-facing) qualification
questionnaire with an approval task. It can also include an internal questionnaire. Supplier qualifications are always
based on a combination of commodities, regions, and, if your site has the supplier management business unit
matrix enhancement enabled, departments. The external qualification questionnaire is a dynamic questionnaire
generated from two different types of template documents:
● An empty survey document [page 226], which functions as a vehicle for serving the qualification content.
Approval and other tasks are always on this empty survey document.
● Content documents [page 228], which define questionnaire segments for specific combinations of commodity,
region, and department.
Internal users with the appropriate permissions create qualification projects on the Qualification tile in supplier
360° profiles. In this case, the user who starts a qualification is the explicit project owner and also a member of the
Project Owner project group. Suppliers can also be qualified via data import [page 82]. The qualification data
import does not create a corresponding qualification project. However, if the qualification expires, a user with the
appropriate permissions can requalify the supplier. In this case, the requalification action creates a qualification
project based on the supplier's previous, data import-defined qualification, and the user who initiates the
requalification is the explicit project owner. Users cannot start a manual qualification for a supplier until the
supplier has the registration status Registered; however, data imports can qualify suppliers who have not achieved
that status.
Unlike request and registration projects, a supplier can have multiple separate qualification projects, each for a
different combination of commodity, region, and department. A supplier's qualifications and associated
questionnaires display on the Qualification tile. Only approvers can see unapproved questionnaires. After a
questionnaire is approved, any user who has permission to view the Qualification tile can see the answers.
There are two possible ways users can start a new qualification; your supplier qualification project template
determines which method is used in your site.
● Static application page: by default, users who start an application page are presented with a static application
page, where they specify the commodities and regions for the qualification. Submitting these answers creates
the qualification project. The page does not allow users to specify department or expiration information for the
qualification.

176 PUBLIC Topics about setting up supplier qualifications
● Prequalification questionnaire: you can set up a prequalification questionnaire [page 180]. If you set one up,
users who start qualifications are presented with it rather than with the default application page. If your
company uses departments in qualifications, you must set up a prequalification questionnaire. You can also
use it to specify an expiration date and a requalification eligibility date. If you do not use the prequalification
questionnaire but want to allow users to set expiration and requalification eligibility dates, you must set up an
internal questionnaire instead.
A qualification project closes after its final task is completed; however, if a qualification expires, a user can initiate a
requalification. When a user requalifies a supplier that was previously qualified using a project (rather than via data
import), the original qualification project reopens and all of its tasks start again.
Deployment of your solution includes a supplier qualification project template with the following default
configuration, which includes an empty qualification questionnaire survey document and an approval task. You
must edit the template to define your company's specific processes.
Documents Supplier qualification questionnaire (an empty survey docu

ment with the questionnaire questionnaire type) in Draft sta
tus
Tasks Approval for supplier qualification (an approval task for the
supplier qualification questionnaire survey document with
members of the Project Owner group as approvers)
group as approvers.

Related Information
Restrictions, requirements, and helpful hints for setting up the supplier qualification project template [page 178]
Setting up the prequalification questionnaire [page 180]

Topics about setting up supplier qualifications PUBLIC 177
setting up the supplier qualification project template
Supplier qualification projects function within a specific supplier management workflow, and need some specific
configurations to ensure that they fit successfully in that workflow.
Restrictions
● The supplier qualification project template only supports survey and content documents. Do not add any other
type of document to it.
● The supplier qualification project template only supports To Do and approval tasks. Do not add any other type
of task to it.
● The supplier qualification project template supports one external questionnaire survey document. You define
the content of the external questionnaire in multiple content documents; the survey document itself must be
empty. Adding content to the external questionnaire survey document itself causes the questionnaire to fail
with errors.
● The supplier qualification project template supports multiple internal questionnaire survey documents. You
define the content of internal questionnaires in the survey documents themselves; they do not use content
documents. You can have internal surveys in addition to the prequalification questionnaire; however, note that
the project team is defined by commodity, region, and (optionally) department values set in either the static
application page for starting qualifications or the prequalification questionnaire, not an internal survey.
● Do not apply project-level visibility conditions based on commodity, region, or department to the content
documents that define qualification questionnaire segments. When a user starts a qualification, only the
questionnaire segments that apply to the qualification's commodities, regions, and departments display.
Requirements
● The supplier qualification project template must contain one external survey document with an associated
approval task.
● You must create a To Do task for each internal registration questionnaire survey document you add. The task
ensures that the correct users can edit the survey to fill it out.
● If you want to qualify suppliers based on department as well as commodity and region, you must use a
prequalification questionnaire. [page 180]
● If you want to qualifications in your site to expire, you must create a question with answer type Date and map it
[page 260] to project.ExpirationDate. If you want to allow a category or supplier manager to establish a
waiting period before an expired qualification can be requalified, add a second date question and map it to
project.RequalificationEligibilityDate. Depending on how you set up your supplier qualification
project template, you can add these questions in the prequalification questionnaire (if you use one) or in an
internal questionnaire (if you do not use the prequalification questionnaire).

Helpful hints
● Each qualification questionnaire segment content document is tied to specific commodities, regions, and
departments. You can apply visibility conditions [page 299] 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, regions, and departments to which the segment is targeted.
content.
● Unlike registration, which is a one-time process, the qualification process is designed so that qualification
managers can run multiple separate qualifications on the same supplier for different commodities, regions, or
departments. A supplier contact will potentially answer multiple qualification questionnaires from you.
Therefore, it's a good idea to choose the levels of the commodity, region, and department 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, qualification
questionnaires for all states in the United Statues include that required segment for the US. If you need to
gather information about a supplier that is broadly applicable across multiple commodities, regions, or
departments, consider either doing so during registration or making sure that the questionnaire segment is not
required so that qualification managers can omit it from successive qualifications.
● Plan a consistent strategy for organizing each questionnaire segment's contents using sections [page 231]. 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.
● SAP Ariba recommends that you use modular supplier management questionnaire projects to collect
certificate information from suppliers rather than creating certificate questions in the qualification
questionnaire. Collecting supplier certificate information in modular questionnaires provides key benefits that
are not available for certificates collected in qualification questionnaires, including expiration schedules and
notifications at both the certificate and questionnaire level and the ability to search for suppliers by certificate
type. For details, see Setting up supplier certificate management using modular questionnaires [page 201].
● There is no need to add questions about the supplier's commodities, regions, and departments to the external
qualification questionnaire. The qualification manager who starts the qualification sets it commodities, regions,
and departments at that time, and indeed, having a second set of mapped commodity, region, and department
questions in the same questionnaire can cause problems.
● If you add any internal surveys to the project, make sure to set Specify questionnaire type to Internal for
them.
● Commodity level restrictions in qualification templates only apply to users starting qualifications if your project
uses a prequalification questionnaire [page 180] prequalification questionnaire. If your site uses the default,
static application page to start qualifications, the commodity chooser in that page does not recognize
commodity level restrictions set in the project template, since the static application page is not created from
the template.
● You can customize templates for email notifications to suppliers [page 345] to include approver comments
from approval tasks with the [TASK_COMMENT_TEXT] email token.

Related Information
About the supplier qualification project template [page 176]

How to set up the prequalification questionnaire [page 181]
How to remove an existing internal qualification survey [page 183]
Setting up the prequalification questionnaire

By default, when a category or supplier manager starts a qualification, they open an application page where they
select a category or region. The prequalification questionnaire replaces that page and allows you to add
department and qualification expiration dates to that prequalification step.
When you create a prequalification questionnaire in your site's qualification project template, it automatically
replaces the static application page as the first step in starting a qualification. The category or supplier manager
who starts a qualification fills out the prequalification questionnaire, and their answers determine the questionnaire
segments [page 228] that are available for them to send to the supplier as part of the qualification questionnaire.
SAP Ariba strongly recommends that you set up your own prequalification questionnaire instead of using the
default static application page. The prequalification questionnaire offers two distinct advantages:
● You can add Department as a third filter for qualification questionnaire content. The static application page
only allows users to select category and region as filters, but the prequalification questionnaire supports
filtering by the department master data in your site as well. Department data is only used in qualifications if the
business unit supplier management matrix enhancement feature is enabled in your site.
● It provides a convenient way to set up qualification expiration. Mapped questions enable qualification
expiration; if you do not put them in the prequalification questionnaire, you must create a separate internal
survey in the qualification project for that purpose.
The prequalification questionnaire currently supports up to five questions: up to three questions to filter
questionnaire segments based on commodity, region, and department, and up to two questions on qualification
expiration. The answers to questions in the prequalification questionnaire are used to filter the questionnaire
segments that are available for the qualification and to set the expiration dates; they not displayed anywhere in the
supplier 360° profile, so you should not use the prequalification questionnaire to solicit any other information.
Related Information

How to set up the prequalification questionnaire
The prequalification questionnaire defines the commodity category, region, and department for the supplier
qualification. It can also define the qualification's expiration date and the date on which the supplier is eligible for
requalification for the same commodity/region/department combination.
Prerequisites
To set up the prequalification questionnaire, you must be a member of the Template Creator group.
To qualify suppliers by department, the business unit supplier management matrix enhancement feature must be
enabled in your site.
You must make sure that the content documents that define your qualification questionnaire segments have the
appropriate Commodity, Region, and (optionally) Department settings. If you have a qualification project template
implementation based on commodity and region, and are adding the prequalification questionnaire with the third
department filter to this existing setup for the first time, makes sure that all of the content documents that define
qualification questionnaire segments also have a Department setting. You might need to adjust your questionnaire
segment strategy, edit existing content documents, and create new content documents to define segments that
apply to department as well as commodity and region.
Context
The supplier qualification questionnaire is assembled from a set of segments targeted to different commodities,
regions, and departments. In the supplier qualification project template, those segments are defined by a set of
separate content documents with commodity, region, and department settings.
The prequalification questionnaire is an initial form that supplier or category managers fill out when they start a
new qualification. The values they choose for commodity, region, and department define the list of available
questionnaire segments they can select to assemble a qualification questionnaire to send to the supplier. Only the
content documents that match all three values (or any values below them in a hierarchy) are shown as available
questionnaire segments.
The answers to questions in the prequalification questionnaire are not displayed anywhere in the supplier 360°
profile, so you cannot use it to solicit information. You can only use it to filter the list of available qualification
questionnaire segments and to optionally enable qualification expiration. Do not add any other questions besides
the three mapped filtering questions and (optionally) up to two mapped qualification expiration questions, because
category or supplier managers have no way to see the answers.
The specialized Qualification Request setting in the prequalification questionnaire survey document ensures that
the prequalification questionnaire is always automatically displayed when a category or supplier manager starts a
new qualification. This setting is not available in the default template survey document, which forms the basis of
the qualification questionnaire; it is only available in new survey documents. Only one prequalification
questionnaire per supplier qualification project template is supported.
Currently, if you are using buyer category assignments (the user matrix) to assign ownership of and approvers for
qualification projects, the Commodity and Region values in the prequalification questionnaire are used for those
assignments. However, the Department value is not.

Procedure
1. Open the supplier qualification project template. If it is not in Draft, create a new version.
3. Choose Actions Create Survey .

4. On the Rules page, in the Supplier Management area, specify the following settings:
a. On the Specify question format dropdown menu, choose Form.
b. On the Specify questionnaire type dropdown menu, choose Qualification Request.
The Is questionnaire required? setting has no effect on the prequalification questionnaire and is ignored.
5. On the Content page, add the following questions:
○ For the category filter, create a question with answer type Commodity and enter matrix.Categories in
the Supplier field mapping field.
○ For the region filter, create a question with answer type Region and enter matrix.Regions in the
Supplier field mapping field.
○ (Optional) For the department filter, create a question with answer type Department and enter
matrix.Departments in the Supplier field mapping field.
○ (Optional) To enable qualification expiration, create a question with answer type Date and enter
project.ExpirationDate in the Supplier field mapping field.
○ (Optional) To specify a date before which an expired qualification cannot be requalified, create a question
with answer type Date and enter project.RequalificationEligibilityDate in the Supplier field
mapping field.
6. Click Exit to save the survey.
7. After you have finished making changes to the supplier qualification template, publish it.
Next Steps
It is important that the supplier qualification project template include only one mapped qualification expiration
question and one mapped requalification eligibility question. If you are adding the prequalification questionnaire to
an existing qualification process where the current template has an internal survey that already includes one or
both of these questions, and you have decided to include them in the prequalification questionnaire instead,
perform one of the following actions:
● If the internal survey includes other questions, edit it to delete the mapped expiration and requalification
eligibility question.
● If the internal survey was added solely to enable qualification expiration, and does not include any other
questions, remove it from the template [page 183].

How to remove an existing internal qualification survey
If your site used an internal qualification survey solely to enable qualification expirations, and you have added the
expiration questions to the prequalification questionnaire instead, you can remove the now-obsolete internal
survey from the supplier qualification template.
Prerequisites
To remove an existing internal qualification survey, you must be a member of the Template Creator group.
Context
Qualifications created before you published the new version of the template with the deleted internal survey and To
Do task still include that survey regardless of when they are completed. Qualifications created after you published
the new version do not.
To remove an obsolete internal survey from the qualification workflow, you must delete both the survey document
and its associated To Do task from the supplier qualification template.
Procedure
1. Open the supplier qualification project template. If it is not in Draft, create a new version.
3. Click the To Do task for the internal survey and choose Action View Task Details .
4. On the task details page, choose Actions Task Delete .

5. Click OK.
7. Click the internal survey document and choose Action View Details .
8. On the survey Overview tab, choose Actions Document Delete .

9. Click Delete.

Topics about setting up supplier
disqualifications
About the supplier disqualification project template [page 184]
Restrictions, requirements, and helpful hints for setting up the supplier disqualification project template [page
185]
About the supplier disqualification project template

The supplier disqualification project template defines the process by which your company disqualifies suppliers for
the specific combinations of commodities, regions, and departments for which they were previously qualified.
The supplier disqualification project template must always include an internal disqualification questionnaire with an
approval task. Supplier disqualification is always an internal process; there is no external (supplier-facing)
disqualification questionnaire. Supplier disqualifications are always based on a combination of commodities,
regions, and, if your site has the supplier management business unit matrix enhancement enabled, departments.
Internal users with the appropriate permissions create disqualification projects on the Qualification tile in supplier
360° profiles. In this case, the user who starts a disqualification is the explicit project owner and also a member of
the Project Owner project group. Suppliers can also be disqualified via data import [page 82]. The disqualification
data import does not create a corresponding disqualification project. Users can only start a manual disqualification
for a supplier based on an existing qualification; however, data imports can disqualify suppliers who have not
previously been qualified.
As with qualifications, a supplier can have multiple separate disqualification projects, each for a different
combination of commodity, region, and department. A supplier's disqualifications and associated questionnaires
display on the Qualification tile. Only approvers can see unapproved questionnaires. After a questionnaire is
approved, any user who has permission to view the Qualification tile can see the answers.
Depending on how you set up the disqualification questionnaire, disqualifications in your site can take effect
immediately, or only after a specified phase-out period.
Deployment of your solution includes a supplier disqualification project template with the following default
configuration, which includes an empty disqualification questionnaire survey document and an approval task. You
Documents Supplier disqualification questionnaire (an empty survey

document with the questionnaire questionnaire type) in Draft
status

184 PUBLIC Topics about setting up supplier disqualifications
Tasks Approval for supplier disqualification (an approval task for

the supplier disqualification questionnaire survey document
with members of the Project Owner group as approvers)
group as approvers.

Related Information
Restrictions, requirements, and helpful hints for setting up the supplier disqualification project template [page 185]

setting up the supplier disqualification project
template
Supplier disqualification projects function within a specific supplier management workflow, and need some specific
configurations to ensure that they fit successfully in that workflow.
Restrictions
● The supplier qualification project template only supports one survey document for one internal questionnaire.
Do not add any other type of document to it, and do not add any more survey documents beside the template's
default disqualification questionnaire.
● The supplier disqualification project template only supports To Do and approval tasks. Do not add any other
type of task to it.

Topics about setting up supplier disqualifications PUBLIC 185
Requirements
● The supplier qualification project template must contain one internal survey document with an associated
approval task.
● A disqualification is always tied to a previous qualification's commodities, regions, and departments, so setting
that data for the project is required. To do so, you must create commodity and region questions in the
disqualification questionnaire using the Commodity and Region answer types and mapping them to the
matrix.Categories and matrix.Regions fields in the supplier database. If your site has the business unit
matrix enhancement feature enabled and you also qualify suppliers by department, you must also add a
question of answer type Department and map it to matrix.Departments. These settings ensure that
disqualifications use the same commodity, region, and department data that is used for qualifications and
preferred supplier levels.
Helpful hints
● You can make the disqualification date-based and introduce a phase-out period in the following ways:
○ If you add date questions to the disqualification questionnaire without mapping, they are for information
only.
○ If there are no mapped date questions in the disqualification questionnaire, once the questionnaire is
approved, the supplier is immediately disqualified.
○ If you create a date question and map it to project.DisqualificationDate, once the questionnaire is
approved, the supplier has Restricted status for a phase-out period until the date is reached, and is then
automatically disqualified on that date. This mapped question is the only way to achieve a restricted
qualification phase for the supplier before disqualification.
○ If you create a date question and map it to project.DisqualifiedUntilDate, once the questionnaire
is approved, the supplier cannot be requalified for the same commodities, regions, and departments until
the date is reached.
content.
Related Information
About the supplier disqualification project template [page 184]


186 PUBLIC Topics about setting up supplier disqualifications
Topics about setting up preferred supplier
management
About the preferred supplier management project template [page 187]
Restrictions, requirements, and helpful hints for setting up the preferred supplier management template [page
188]
About the preferred supplier management project

template
The preferred supplier management project template defines the process by which your company grants preferred
category status suppliers for specific combinations of commodities and regions.
The preferred supplier management project template must always include an internal (supplier-facing) category
status questionnaire with an approval task. Your company's preferred levels are defined in your site [page 39] using
master data import, and up to five preferred levels are supported. Preferred designations are always based on a
combination of commodities, regions, and, if your site has the supplier management business unit matrix
enhancement enabled, departments.
Internal users with the appropriate permissions request a category status change for a specific combination of
commodities, regions and departments on the Overview tile in supplier 360° profiles. In this case, the user who
requests the status change is the explicit project owner and also a member of the Project Owner project group.
Suppliers can also gain preferred levels via data import [page 86]. The preferred data import does not create a
corresponding preferred supplier management project. However, a user with the appropriate permissions can
always request a change for an existing preferred category status. In this case, the action of editing a preferred
category status creates a preferred supplier management project based on the supplier's previous, data import-
defined preferred levels, and the user who requests the change is the explicit project owner. Users cannot manually
request a preferred category level for a combination of commodities, regions, and departments until the supplier
has been qualified for that combination.
As with qualifications, a supplier can have multiple separate preferred supplier management projects, each for a
different combination of commodity, region, and department.
Users can always request changes to existing preferred category levels to either upgrade, downgrade, or remove a
supplier's preferred status. A preferred supplier management project closes after its final task is completed; when
a user requests a preferred category status change a supplier that was previously designated as preferred using a
project (rather than via data import), the original preferred supplier management project reopens and all of its
tasks start again. If a supplier is disqualified for a commodity, region, and department combination for which it is
also preferred, the final approval of the disqualification automatically removes the corresponding preferred status
without reopening any associated preferred supplier management project.
Deployment of your solution includes a preferred supplier management project template with the following default
configuration, which includes an empty category status questionnaire survey document and an approval task. You

Topics about setting up preferred supplier management PUBLIC 187
Documents Category status (an empty survey document with the ques
tionnaire questionnaire type) in Draft status
Tasks Approval for category status change (an approval task for the
category status questionnaire survey document with members
of the Project Owner group as approvers)
group as approvers.

Related Information
Restrictions, requirements, and helpful hints for setting up the preferred supplier management template [page
188]

setting up the preferred supplier management
template
Preferred supplier management projects function within a specific supplier management workflow, and need some
specific configurations to ensure that they fit successfully in that workflow.
Restrictions
● The preferred supplier management project template only supports one survey document for one internal
questionnaire. Do not add any other type of document to it, and do not add any more survey documents beside
the template's default disqualification questionnaire.
● The preferred supplier management project template only supports To Do and approval tasks. Do not add any
other type of task to it.

188 PUBLIC Topics about setting up preferred supplier management
Requirements
● The preferred supplier management project template must contain one internal survey document with an
associated approval task. If you do not want to require approvals for preferred category status changes, you
can set the task to auto-approve.
● A preferred category status is always tied to a previous qualification's commodities, regions, and departments,
so setting that data for the project is required. To do so, you must create commodity and region questions in
the category status questionnaire using the Commodity and Region answer types and mapping them to the
matrix.Categories and matrix.Regions fields in the supplier database. If your site has the business unit
matrix enhancement feature enabled and you also qualify suppliers by department, you must also add a
question of answer type Department and map it to matrix.Departments. These settings ensure that
preferred category status designations use the same commodity, region, and department data that is used for
qualifications and disqualifications.
Helpful hints
● The preferred supplier management questionnaire is automatically internal-only, regardless of whether you set
Specify questionnaire type to Internal or External.
● For the question asking which preferred supplier level to use for the supplier, use your site's preferred supplier
level master data [page 310] for acceptable answers and map the question to project.Level in the supplier
database.
content.
Related Information
About the preferred supplier management project template [page 187]

Topics about creating supplier forms and questionnaires [page 220]

Topics about setting up preferred supplier management PUBLIC 189
Topics about setting up modular supplier
management questionnaires
About modular supplier management questionnaire project templates [page 190]
Restrictions, requirements, and helpful hints for modular supplier management questionnaire project
templates [page 192]
How to create a modular supplier management questionnaire project template [page 194]
How to set up separate workflows for new and updated modular supplier management questionnaires [page
199]
Setting up supplier certificate management using modular questionnaires [page 201]
About modular supplier management questionnaire

project templates
Modular supplier management questionnaire project templates define the processes by which your company
gather and maintain discrete sets of related information, such as certificate information, qualification information,
or risk assessments, about suppliers or engagement risk.
Unlike other supplier management projects, you create multiple modular supplier management templates in your
site, one for each questionnaire. These templates all have the project type SM Modular Questionnaire.
Each modular supplier management project template must contain one questionnaire. You set a questionnaire type
for it and specify the commodities, regions, and departments to which its questionnaire applies. You can also
specify an expiration schedule for the questionnaire. This schedule is specific to the questionnaire itself, and
operates independently of the expirations of any of the certificate questions it might contain.
Internal users with the appropriate permissions can create standalone external modular supplier management
questionnaire projects outside of other supplier management processes by choosing Manage SM Modular
Questionnaires on the dashboard and inviting one or more suppliers to fill out one or more questionnaires.
During this process, they select from a list of available questionnaires; the list shows each questionnaire's type and
the commodities, regions, and departments to which it applies. This process creates a modular supplier
management questionnaire project for each selected questionnaire, for each invited supplier. The user who issues
the invitation is the explicit project owner.
After an external modular supplier questionnaire project is finally approved, if either the same or a different internal
user sends the same modular questionnaire to the same supplier again using Manage SM Modular
Questionnaires , the existing project reopens and its tasks restart. The explicit project owner remains the original
user who sent the questionnaire.

190 PUBLIC Topics about setting up modular supplier management questionnaires
In sites that include SAP Ariba Supplier Risk, sending risk assessments for a control-based engagement risk
assessment project also creates modular supplier management questionnaire projects for the required
assessments, which can be either internal or external. In this case, the person who sends the assessments
becomes the explicit project owner of the modular supplier management questionnaire projects created by their
action. Sending assessments always creates new internal modular questionnaires, which are used once per
engagement risk assessment project. It only creates external modular questionnaires for engagement risk
assessment projects where the selected supplier does not already have a valid questionnaire from a previous
engagement risk assessment project.
Unlike registration projects, which collect basic profile information in one project, modular supplier management
questionnaire projects are designed to collect specific, limited sets of information, such as a certificate or set of
related certificates or information that is applicable to a specific risk area or domain. A supplier can have any
number of external modular supplier management questionnaire projects. A supplier's external modular supplier
management questionnaires and their associated tasks display on the Questionnaires tile in their 360° profiles;
after a questionnaire is approved, any user who has permission to see the Questionnaires tile can see its answers.
Internal modular supplier management questionnaires show on the engagement page of the control-based
engagement risk assessment project in which they are created and are also visible to recipients in the To Do
content item of their Home dashboard.
Modular supplier management questionnaire template survey documents include an Always open setting. If this
setting is not enabled in an external questionnaire, once the final task is complete, the project closes. If it is
enabled, the project stays open and suppliers can update an external questionnaire on a continuous basis. If you do
not use phases for template tasks, all of the project's tasks are for new questionnaires; however, you can use
phases to set up workflows for new questionnaires and questionnaire updates [page 199]. Internal modular
supplier management questionnaires are used once per control-based engagement risk assessment project and
never reopen.
Neither deployments of new solutions nor enablement of the modular supplier management feature in existing
solutions creates a default modular supplier management project template. Instead, you create these templates
[page 194] yourself.
Related Information
Restrictions, requirements, and helpful hints for modular supplier management questionnaire project templates
[page 192]
How to set up separate workflows for new and updated modular supplier management questionnaires [page 199]

Topics about setting up modular supplier management questionnaires PUBLIC 191
modular supplier management questionnaire project
templates
Modular supplier management projects function as standalone projects with a specific workflow, and include some
specialized settings to facilitate that workflow. They require some specific configuration settings to function
properly.
Restrictions
● Modular supplier management questionnaire project templates only supports one survey document. Do not
add any other type of document, or more than one survey document, to them.
● External (supplier-facing) modular supplier management questionnaire project templates only support To Do
and approval tasks. Internal modular supplier management questionnaire project templates for internal
assessments in control-based engagement risk assessment projects only support approval tasks. Do not add
any other type of task to them.
● Supplier management projects do not support commodity level restrictions in external questionnaires.
Specifying the Allowed Commodity Level property on the template Overview tab does not restrict acceptable
answers for suppliers choosing commodities in external questionnaires.
● Modular supplier management questionnaire project templates only support the use of phases in this
configuration [page 199].
Requirements
● Each modular supplier management questionnaire project template must contain one survey document.
● You must set the questionnaire type for each modular supplier management questionnaire project template
you create, and therefore your site must have questionnaire types defined for it. Your site's questionnaire types
are defined using a master data import.
● For most uses, you must set the Commodity and Region properties for each modular supplier management
questionnaire project template you create. If your site uses the business unit supplier management matrix
enhancement feature, you must also set the Department property. Modular supplier management
questionnaire projects are designed to apply to specific commodity, region, and department combinations in
most cases.
Supplier request, qualifications, disqualification, and preferred supplier management projects are created by
submission of a questionnaire that can include commodity, region, and department questions. Standalone
modular supplier management questionnaire projects, however, are created via invitation, before a
questionnaire is submitted. The Commodity, Region, and Department properties in the project template
therefore determine buyer category assignments for standalone modular supplier management questionnaire
projects created outside of other supplier management processes.
● If you enable the Always open setting in the Supplier Management area of the template survey document's
rules, the external modular supplier management questionnaire projects created from it reopen after every

final approval, and suppliers can update their questionnaires on an ongoing basis. There is no need to configure
phases in the template to support this update capability. However, without phases, the tasks in the template
only apply to new modular questionnaires and all updates are automatically approved. To enable approval of
questionnaire updates, you must set up phases and add separate tasks to them [page 199]. You can use these
phases to define separate workflows for new external questionnaires and questionnaire updates.
Helpful hints
● Modular supplier management questionnaire projects do not require any tasks, including approval tasks. If you
do not add an approval task on the project template survey document, the project is automatically approved
when the respondent submits the questionnaire.
● Suppliers can have many external modular supplier management questionnaire projects; the project
questionnaires and associated tasks display in separate Questionnaire and Task tables on the Questionnaires
tile. Make sure that the names you give to tasks clearly associate them with the questionnaires to which they
belong so that users can easily identify the associations on the Questionnaires tile.
● Modular supplier management projects are useful for collecting certificate information from suppliers. For
specific guidance about setting templates up for certificate management, see the topic on setting up
certificate management.
● For new questionnaires, the Due Date setting in the Timing Rules section of survey documents defines the
amount of time the supplier contact has to fill out the questionnaire after the invitation is sent. If the supplier
contact does not fill and submit the questionnaire in that time, the questionnaire closes and the supplier
contact can no longer edit it. Reminding the supplier to fill out the questionnaire reopens it so that the supplier
can fill out and submit it again. The default due date value is 30 days, but you can change that time period by
editing the Due Date field in the questionnaire survey document.
If you have set Always open to Yes for the questionnaire, once all of the tasks for a new questionnaire
completed, it automatically reopens so that the supplier can submit updates. Depending on your site's
configuration, the Due Date setting might also determine how long the questionnaire remains reopened for
updates. For details, see Supplier form or questionnaire closing, reopening, and due dates [page 221].
content.
● You can customize templates for email notifications to suppliers to include approver comments from approval
tasks with the [TASK_COMMENT_TEXT] email token. You can also use the [MQ_REQUEST_UPDATE_COMMENT]
email token to insert comments that users make when they request a modular questionnaire update. For more
information, see topics about customizing email notifications.
Related Information


About customizing supplier management notification templates [page 345]
How to create a modular supplier management

questionnaire project template
Every modular supplier management questionnaire is defined by a separate template, which specifies the type of
questionnaire, its content, and its approval flow.
Prerequisites
You must be a member of the Template Creator and SM Questionnaire Manager groups to create modular
supplier management questionnaire templates.
Questionnaire types must be defined in your site's master data.
The Department attribute in modular supplier questionnaire templates is only used in sites with the business unit
supplier management matrix feature enabled. Otherwise, it is ignored.
Context
You must set the Questionnaire Type attribute for each modular supplier management questionnaire template you
create. A customer administrator defines the questionnaire types in your site using master data import.
You can also set the template's Commodity, Region, and Department attributes so that projects created from it
are applicable to a specific commodity, region, and department combination.
Do not set access control or apply conditions to modular supplier management questionnaire templates. Since
users do not explicitly create projects from them, access control or condition settings might interfere with the
workflow by which users select the questionnaires and send them to suppliers.
Procedure
1. On the dashboard, choose Manage Templates .
2. On the Documents tab of the Templates area, choose Actions Create Template .
3. For project type, choose SM Modular Questionnaire.
4. Click OK.
5. Enter a name and optional description for the new template. Template names can have a maximum of 255
characters and cannot contain these special characters: \ / : ? “ < > | # + % &.
6. Choose a language from the Base Language dropdown menu. The base language is the language in which you
plan to author the template's content and is shown to its users by default unless you provide translations.

7. Click OK.
The new template opens on the Overview tab. It is in Draft status.
8. In the Properties area, choose Actions Edit Properties .

9. Set the type for the modular supplier management questionnaire by performing the following actions:
a. For Questionnaire Type, click the dropdown menu, then choose Search more.
b. Click Select for one of the questionnaire types defined in your site, then click Done.
10. (Optional) Repeat the previous step to set specific values for Commodity, Region, and Department. If you do
not specify specific values, the questionnaire is available for all commodities, regions, and departments.
11. Click Save.
Next Steps
Set up the template's modular supplier management questionnaire [page 195].
Related Information
How to set up a modular supplier management

questionnaire
Setting up a modular supplier management questionnaire involves creating a survey document and specifying
settings for how it is used.
Prerequisites
You must be a member of both the Template Creator and SM Questionnaire Manager groups to edit and publish
modular supplier management questionnaire templates.
Context
The properties of the modular supplier management project template [page 194] to which you are adding a
questionnaire specify a combination of commodities, regions, and departments. The questionnaire that you set up
is designed to hold content that is applicable to that combination.

In general, modular supplier management questionnaire survey documents support the same types of content and
question answer types as the survey documents in other supplier management project templates, including the
use of visibility and editability conditions, supplier database field mapping, sensitive data masking, and other
settings. However, since one of the purposes of these questionnaires is to collect certificate information from
suppliers, questions of answer type Certificate in modular supplier management questionnaire project templates
have specialized settings to support certificate management.
 Note
Template survey documents contain a number of settings (supplier eligibility criteria, definitions, participants,
and so forth) that are not relevant to modular supplier management processes. These settings are ignored in
modular supplier management questionnaire projects. Only the timing rule and supplier management settings
on the survey's Rules page and the content on its Content page are used in modular supplier management
questionnaire projects.
Timing rules in modular supplier management questionnaires determine how much time a recipient has to fill out
and submit the form or questionnaire after being invited to do so. For external questionnaires, if you specify Yes for
the Always open setting in the supplier management rules, once the questionnaire is approved, it automatically
reopens so that the supplier can update it. If you specify Yes for the Keep questionnaire reopened indefinitely
setting in the timing rules, the reopened external questionnaire will remain open indefinitely.
Procedure
1. Open the supplier modular supplier management questionnaire template. If it is not in Draft, create a new
version.

4. In the Title field, enter a descriptive title for the questionnaire.
 Tip
Modular questionnaire titles display in lists of questionnaires that category and supplier managers can
send to suppliers and in the 360° profiles of suppliers who have been invited to fill them out, so make sure
that the title you give the questionnaire identifies its purpose clearly.
5. (Optional) In the Description field, enter descriptive information about the survey. This information is only
visible in the template.
6. For Test Event, choose No.
7. Choose a language from the Base Language dropdown menu. The base language is the language in which you
plan to author the survey's content, and is shown to its users by default unless you provide translations.
8. Click Create.
9. On the questionnaire's Rules page, navigate to the Supplier Management rules and perform the following
actions:

For this setting... Choose...
Specify questionnaire format Form to create a questionnaire with an unnumbered list of

questions, or Questionnaire to create a questionnaire with
numbered questions.
Is questionnaire required? Yes.
 Note
This setting is ignored in questionnaires created in SAP
Ariba Supplier Risk control-based engagement risk as
sessment projects.
Specify questionnaire type Specify External for questionnaires that suppliers fill out, or
Internal for questionnaires that stakeholders in your organi
zation fill out. Currently, internal modular supplier manage
ment questionnaires are only supported in SAP Ariba Sup
plier Risk control-based engagement risk assessment
projects.
Reuse Yes if you want to be able to reuse the questionnaire in other

supplier management processes in the future, or No if you
want the questionnaire to exist only as a standalone ques
tionnaire.
 Note
Currently, SAP Ariba Supplier Management solutions do
not support reusing modular questionnaires in other
supplier management processes such as qualification or
performance management. However, this functionality
is planned for a future release. SAP Ariba Supplier Risk
ignores this setting.
Always open Yes to automatically reopen the external questionnaire for

supplier updates after approval, or No to permanently close
the questionnaire after the initial approval or denial.
If you are creating the questionnaire to collect certificate in

formation, always choose Yes so that suppliers can always
update their certificate information. If you set the question
naire to expire, it is also useful to keep it open so that the
supplier can update an expiring or expired questionnaire.
Otherwise, once it expires, it remains permanently expired.
Can expire? Yes if you want the questionnaire to expire on a specific date;
otherwise No.
If you choose Yes, set the expiration schedule and the

amount of time before expiration that email reminders are
sent to the supplier contact who submitted the question
naire. You also have the option of sending expiration notifica-

For this setting... Choose...
tions to the supplier's primary supplier manager and to the

members of the questionnaire's Project Owners group.
If a questionnaire project created from this template is ap

proved, its status changes to Expiring or Expired based on
the reminder and expiration date settings in the expiration
schedule.
These expiration settings apply to the questionnaire itself. If

you add certificate questions to the questionnaire, each of
them also has its own expiration date, and each certificate
expiration also generates notifications. A setting in certifi-
cate questions allows you to base the questionnaire project's
Expiring and Expired status on the expiration schedule for
the certificate rather than the questionnaire.
10. In the Timing Rules area, perform the following actions:
○ (Optional) Edit the default due date. The due date affects how long new questionnaires remain open. It
does not affect how long reopened questionnaires remain open.
○ (Optional) Enable reminders to the supplier as the due date approaches. If you set Always open to Yes,
after the questionnaire is approved for the first time, the due date determines only affects the reminder
schedule. The questionnaire never closes, and if the recipient does not update it by the due date, the
reminder schedule restarts and the recipient receives a new set of reminders on the next dates in the
reminder schedule.
○ If you set Always open to Yes, choose a setting for Keep questionnaire reopened indefinitely. Choose Yes
to keep an external questionnaire reopened indefinitely.
For details, see Supplier form or questionnaire closing, reopening, and due dates [page 221].
11. In the navigation pane on the left side of the page, click Content.
12. Add questions and other content to the questionnaire as needed.
13. Click Exit to save your changes and exit the survey document.
Next Steps
After you have created the questionnaire survey document:
● (Optional) Create at least one approval task for it and configure the approval flow. If you do not create an
approval task with an approval flow, modular supplier management questionnaire projects created from the
template are automatically approved when the respondent submits the questionnaire. You can also create
multiple approval tasks for the questionnaire and chain them together as predecessors. If you do not use
phases, the approval tasks in the project template apply only to new questionnaires, and questionnaire updates
are always auto-approved.
● (Optional) Create one or more To Do tasks for the survey document. If you do not use phases, the To Do tasks
in the project template apply only to new questionnaires.
● Create new questionnaire and questionnaire update phases [page 199] to apply approval and To Do tasks
separately to new questionnaires and questionnaire updates.

● Publish the modular supplier management project template.
Related Information
How to add a certificate question to a modular supplier management questionnaire for certificate management
[page 245]
[page 192]
About modular supplier management questionnaires in control-based engagement risk assessment projects
Supplier form or questionnaire closing, reopening, and due dates [page 221]
How to set up separate workflows for new and

updated modular supplier management
questionnaires
Modular supplier management questionnaire projects support the use of two phases to apply separate approval
and To Do tasks to new questionnaires and questionnaire updates. Questionnaire updates are automatically
approved unless the project template includes an approval task in the update phase.
Prerequisites
To add phases and tasks in a modular supplier management project template, you must be a member of the
Template Creator and SM Modular Questionnaire Manager groups.
Context
Each modular supplier management questionnaire project template requires at least one approval task. If you use
phases, it must be in the new questionnaire phase.
Suppliers can always update modular questionnaires set to Always Open, but tasks only apply to updates if they
are in an update phase or if a user re-sends the same questionnaire to the same supplier. If the modular
questionnaire project template does not use phases, its tasks apply only to new or re-sent questionnaires; once a
new or re-sent questionnaire is approved and the project's tasks are completed, updating the questionnaire does
not restart them. If you want to apply tasks to questionnaire updates, including approval tasks, you must create a

new questionnaire phase and a questionnaire update phase and add tasks to each phase to define separate
workflows and approvals for the different stages of the questionnaire's lifecycle.
Modular supplier management project templates support phases with special New Questionnaire and
Questionnaire Update settings to control the order in which the phases start and whether the tasks in the phase
are one-time-only (for new questionnaires) or recur (for every questionnaire update). The New Questionnaire
phase starts one time, immediately when the supplier is invited to fill out the questionnaire. The Questionnaire
Update phase starts again every time supplier updates the modular questionnaire.
Within the new questionnaire and questionnaire update phases, you add separate approval and To Do tasks on the
same questionnaire survey document to define the workflows for new and updated questionnaires. For example,
you can set up an approval task with a full approval flow involving all relevant stakeholders in the new questionnaire
phase, and an approval task with a more streamlined approval flow in the update phase. The order in which tasks
appear in a phase does not affect the order in which they start. When the phase starts, all of its tasks automatically
start unless they are predecessors of other tasks. You can chain the tasks in a phase together as predecessors to
define the order in which they start and create a workflow.
When setting up modular questionnaire phases and their tasks, keep in mind the following considerations:
● You can only add two phases to modular supplier management questionnaire projects: one with the New
Questionnaire setting and one with the Questionnaire Update setting. These phases do not use the Subscribe
For, Rank, or Predecessor settings; the new questionnaire phase automatically precedes the questionnaire
update phase.
● Make sure that all of the template tasks are inside either the new questionnaire phase or the update
questionnaire phase. If you use these phases in a modular supplier management project template, adding
tasks outside of them is not supported.
● Make sure that the tasks you specify as predecessors are within the same phase. Do not make tasks in one
phase predecessors of tasks in a different phase.
● You cannot apply conditions to modular supplier management questionnaire tasks or phases themselves.
For details on adding tasks and phases to project templates, see Managing Projects, Teams, Documents and Tasks
and the Project Template Guide, keeping in mind the restrictions on tasks and phases in modular supplier
management project templates.
Procedure
1. Open the modular supplier management questionnaire project template. If it is not in Draft, create a new
version.
3. Create a phase for new questionnaires by performing the following steps:
a. Click Action Create Phase .

b. Enter a name for the phase, such as New Questionnaire
c. Check only the New Questionnaire option.
d. Make sure that Recurring Schedule is set to No so that the tasks in the phase are used only once, when
the questionnaire is first submitted.
e. Click OK.

4. If you have not already done so, add the required approval task, plus any additional approval and To Do tasks
you want to use for new questionnaires, and make sure that they are located inside the new questionnaire
phase. On the Tasks tab, you can move tasks into phases using drag and drop.
5. Create a phase for questionnaire updates by performing the following steps:
a. Click Action Create Phase .

b. Enter a name for the phase, such as Questionnaire Updates
c. Check only the Questionnaire Update option.
d. Make sure that Recurring Schedule is set to No so that the tasks in the phase are used only once, when
the questionnaire is first submitted.
e. Click OK.
6. Add any approval tasks and To Do tasks you want to use for questionnaire updates, and make sure that they
are located inside the questionnaire update phase.
7. After you have finished setting up the modular supplier management project template, publish it.
Results
When a category or supplier manager first invites a supplier to fill out a modular questionnaire, the new
questionnaire phase starts. Final approval of the new questionnaire completes the new questionnaire phase. After
that, every time recipient updates the questionnaire, the update phase starts again. Final approval of the
questionnaire update completes that recurrence of the questionnaire update phase.
Related Information

[page 192]
Setting up supplier certificate management using

modular questionnaires
Modular supplier management questionnaire projects are designed to collect supplier certificate information in
dedicated, standalone projects with their own approval flows. Certificates collected in these projects display on the
Certificate tab of the supplier's 360° profile.
A modular supplier management questionnaire can contain one or more questions of type Certificate, along with
related non-certificate questions and other types of content. Modular supplier management questionnaire project

templates, and the certificate questions in their survey documents, include the following features to support
certificate management:
● Commodity, Region, and Department properties for the project template, which allow you to tie a certificate
or set of certificates to the specific combinations of commodity, region, and department to which they are
applicable.
● Both a questionnaire type (in the template properties) and a certificate type (in the settings for certificate
questions), which allow you to differentiate between modular supplier management questionnaire projects that
serve different purposes, and to categorize the certificates they contain.
● Expiration schedules and notification settings for both individual certificate questions (in question settings)
and entire questionnaires (in the questionnaire survey document's Supplier Management rules).
Certificates always have expiration dates; certificate questions in modular supplier management questionnaire
projects generate notifications for upcoming expirations (in the amount of time before the expiration you
specify) and when the expiration date has passed. You can also configure the questionnaire itself to expire, in
which case the questionnaire also generates notifications for upcoming expirations (in the amount of time
before the expiration you specify) and when the expiration has passed. For both certificate and questionnaire
expirations, you can also notify the supplier's primary supplier manager and/or the members of the project
owner group. For certificate expirations, you can also specify that the certificate's expiration update the status
of the entire questionnaire project to Expiring or Expired.
● Most certificate fields in Certificate questions can be optional when the site configuration parameter Require
only attachment and expiration date for supplier certificates is enabled. All Certificate question fields,
except for Expiration Date and Attachment are optional in external questionnaires. For more information, see
Require only attachment and expiration date for supplier certificates [page 519].
You create different modular supplier management questionnaire project templates to collect different certificates
or sets of certificates for different commodity, region, and department combinations. Since each questionnaire has
its own template, it also has its own approval flow, and you can leverage that feature to route specific certificates to
the relevant approvers.
Setting up certificate management in your site involves:
1. Defining questionnaire [page 40] and certificate [page 44] types in your site.
2. Creating templates for certificate-related modular supplier management questionnaire projects [page 194].
3. Setting up the questionnaires [page 195] in those templates and adding certificate questions to them. [page
245].
4. Defining an approval flow for each questionnaire using template approval tasks.
For certificates that are critical to your company in one way or another, SAP Ariba recommends that you create
separate, dedicated modular supplier management questionnaire project templates for each critical certificate,
defining both a questionnaire type and certificate type for each. Doing so gives each critical certificate its own
approval flow, category, region, and department combination, and project-level expiration status, and makes it
available for use in possible future supplier management processes in its own dedicated module. You can group
multiple questions about related non-critical certificates in the same modular supplier management questionnaire
template. For that purpose, define a general questionnaire type for certificates or several questionnaire types for
broad categories of certificates, and specific a certificate type for each certificate.
Example
ABC Company company wants suppliers of chemicals to its German manufacturing department to have Certificate
X. A customer administrator at ABC Company therefore defines both a questionnaire type and a certificate type of

Certificate X. A template creator then creates a modular supplier management questionnaire project template
with Commodities of chemicals, Region of Germany, and Department of manufacturing, and questionnaire type of
Certificate X. In that project template, they can create a questionnaire survey document called Certificate
X Questionnaire for German chemical suppliers, enabling Always open but not enabling an expiration
schedule, since the certificate itself expire. They add a certificate question, Do you have certificate X?, to
the questionnaire, making it required, setting its certificate type to Certificate X, setting the expiration
reminder and the options to notify the primary supplier manager and project owners, and specifying that the
certificate expiration updates the questionnaire status. They then add an approval task that routes the
questionnaire's approval to relevant stakeholders for this particular certificate, such as category or supplier
managers who handle German chemicals, the German legal department, and so on.
Once the template creator publishes the template, a user at ABC company can send the questionnaire to its
German chemical suppliers. Once a questionnaire project is approved, category or supplier managers, can see it in
the supplier's profile and initiate actions such as qualifications or, for expired certificates, disqualifications.
Notifications let both suppliers and internal stakeholders know when a questionnaire is about to expire or has
expired, and suppliers can update the questionnaire with more recent versions of the certificate.
If ABC Company is also interested to know whether its French suppliers have Certificate X, but do not consider it
critical for any commodity or department, a template creator can add a question about it to a more general
questionnaire about multiple non-critical certificates in a separate modular supplier management questionnaire
project template with Commodities of All, Region of France, and Department of All, using a more general
questionnaire type such as Certificates. They can then add multiple certificate questions to the template
survey document, including Do you have certificate X?. In this case, they might set an expiration schedule
for the questionnaire itself, but would not opt to have any one of its certificates' expirations change the
questionnaire status. Certificate expirations and the questionnaire's expiration both generate notifications to
suppliers and (optionally) primary supplier managers and/or project owners.
Adding scoring and score bands to modular supplier

management questionnaires
Modular supplier management questionnaires can include scoring to apply standardized, template-driven
judgments to respondent answers. You define scoring for a modular supplier management questionnaire in its
project template.
Scoring provides approvers and other stakeholders with guidelines and indicators of the desirability or acceptability
of respondent answers, reducing the need for subjective judgments and applying uniform criteria to the answers
from all of the respondents who fill out a given modular questionnaire.
In modular supplier management questionnaire scoring, pre-grades for individual questions combine with their
importance and the weight of their sections to produce numerical scores for the sections, and section scores roll
up into an overall numerical score for the questionnaire. Section and questionnaire scores are percentages that
express how many points the questionnaire answers earned out of the maximum number of possible points. Every
score falls within a scoring band, or grouping of scores. All scores within a band receive the same judgment and the
same label, such as "Good," "Average," or "Poor." Next to each score, a colored dot provides a visual indicator of the
band into which the score falls, and hover text identifies the band by name and shows its associated score range.
Adding scoring to modular supplier management questionnaires involves several components:
● Defining scoring bands for your site: master data in your site defines:

○ Whether the questionnaire type of the modular supplier management questionnaire supports scoring.
Questionnaire type master data includes an evaluation type for each questionnaire type. You can only add
scoring to a modular supplier management questionnaire if its questionnaire type has an evaluation type of
Graded.
○ The scoring bands that you can use for a scored questionnaire. Scoring band category master data [page
45] defines the categories or types of bands in your site; for example, you can have a Compliance
category of scoring bands, a Legal category, a Quality category, and so on. There is no limit to the
number of band categories your site can use. Scoring band master data [page 47] defines all of the
different possible scoring bands in each category, their names, and the colors of their indicators.
● Adding scoring to the questionnaire: you add scoring [page 217] in the survey document of the modular
supplier management questionnaire project template by enabling scoring, then pre-grading and weighting
questions and adding importance to sections.
● Setting up the scoring bands for the questionnaire: you set up the scoring bands for the overall
questionnaire score [page 213] on the Overview tab of the modular supplier management questionnaire
project template by choosing the band category, specifying the score ranges for each band in the category, and
optionally enabling banding at the section level. If you do not enable section-level scoring bands, each section
score uses the questionnaire band settings.
● (Optional) Setting up section-level scoring bands: if you enable section-level banding for the questionnaire,
you set up the scoring bands for individual sections [page 215] in the survey document by choosing the band
category and specifying the score ranges for each band. You can use section level scoring bands to either use
different band categories for different sections within the same questionnaire, or to use the same band
category for multiple sections but specify different scoring ranges for the bands in that category in the different
sections.
 Note
If you enable section-level banding in a questionnaire, you must set up scoring bands for each of the
questionnaire's sections individually. Whether or not you plan to add scoring to an individual section and its
questions, you cannot publish the questionnaire template unless all of its sections have banding settings.
Sections with no scoring do not show associated scoring bands, but the band settings are required.
 Note
● The Questionnaires tile of the classic supplier 360° profile does not show overall questionnaire scores or
scoring band indicators. The Questionnaires area of the new supplier 360° profile does. Regardless of the
version of the supplier 360° profile your site uses, the questionnaire detail pages shows scores and score
bands for a questionnaire.
● Neither scoring nor section-level banding is currently supported for repeatable sections.
If your site includes SAP Ariba Supplier Risk and you use modular supplier management questionnaires as
assessments in control-based engagement risk assessment projects, you can add scoring to those
questionnaires, but scores do not show on the engagement page and are not used in control-based
engagement risk assessment projects.
About scoring points [page 205]
About pre-grading supplier questionnaires [page 207]
Structural considerations for scoring supplier questionnaire content [page 211]
How to set up scoring bands for a modular supplier management questionnaire [page 213]
How to set up scoring bands for individual questionnaire sections [page 215]
How to add scoring to a modular supplier management questionnaire [page 217]

Related Information

About pre-grading supplier questionnaires [page 207]
Structural considerations for scoring supplier questionnaire content [page 211]
About scoring points
The more scoring points you assign each piece of event or questionnaire content, the more that content
contributes toward the final score. There are two different types of scoring points, Weight and Importance, that
work together in score calculations for hierarchical content.
About weight
Weight is the relative level of importance of a section of content. It is used with the score you assign each response
and contributes to the overall score for each respondent.
Assign Weight points to “container” content types such as sections and event line items (for scoring purposes, a
line item “contains” its terms). Altering a section or lot’s Weight allows you to alter the Overall % for all the section
content.
For example, suppose there are 30 scoring points assigned to a Car Performance section, and 70 to a Car
Financing section. (Assign a total of 100 scoring points to cause the Overall % to be equal to the number of
assigned scoring points).
For sections, the Overall % column shows how the section contributes to the overall score based in the following
formula:
● section weight / total number of weight points = overall % of section
Using the previous example to verify the Overall % of the Car Financing section, the numbers would look like
this:
● 70 / 100 = 70%
If you do not assign exactly 100 weight scoring points, it complicates the math. For example, if you assign 27 points
to the Car Performance section, and 88 points to the Car Financing section, the total of the weight scoring
points is 115. In this case, the Overall % of the Car Financing section is:
● 88/115 = 76.52%
The following table demonstrates the breakdown of scoring calculations based on the preceding example:
Number Name Weight (base level) Overall %
1 Section 1 – Car Performance 27 27 / 115 = 23.48%

Number Name Weight (base level) Overall %
2 Section 2 – Car Financing 88 88 / 115 = 76.52%
Maximum points for content 115
About importance
Importance is the relative level of importance for individual pieces of content that require answers from suppliers
or other respondents, such as questions and event line item terms.
Assign each question or other piece of individual content between 0–10 Importance scoring points, with 10 being
the most important. Content to which you assign 0 scoring points does not count towards the score.
In the following graphic, question 1.2 has the highest importance with 10 Importance points, and question 1.1 is half
as important as question 1.2 with 5 Importance points.
>The Overall % of questions changes depending on how you weight the section they are located in. To calculate
the Overall % of the questions in the Car Performance section, first calculate their percentage within the Car
Performance section, and then multiply that by the Overall % of the Car Performance section. The formula for
the numbers in the example would be:
● (importance of question 1.1 (5) / total number of importance points in the Car Performance section (15)) *
overall % of Car Performance section (30) = overall % of question 1.1 (10%)
Written numerically:
(5/15) * 0.3 = 0.1

The following table combines section Weight and question Importance to calculate the overall % of the questions
within section 1:
Number Name Weight Importance Overall %
1 Section 1 – Car Performance 30 30 / 100 = 30%
1.1 Question 1.1 5 10% = 30%*5/15
1.2 Question 1.2 10 20% = 30%*10/15
Maximum points for content in Sec 15

tion 1
2 Section 2 – Car Financing 70 70 / 100 = 70%
Maximum points for content 100
About pre-grading supplier questionnaires
The pre-grade you assign to a specific answer to a question determines the amount that the answer contributes to
the total score of the questionnaire relative to other answers to the same question.
When you pre-grade a question, you assign a grade to each possible answer to the question. You can only pre-grade
questions that have defined or quantifiable answers.
In percentage-based scoring, pre-grades are always percentage values between 0 and 100, with 0 being the lowest
and 100 being the highest grade. They specify the percentage of the question's available scoring points each
answer earns, and that question-level scoring point calculation rolls up into the calculation of both section-level and
overall questionnaire scores based on the question's importance and its section's weight.
In point-based scoring, pre-grades are always point values, which add up to section-level and overall questionnaire
scores. Point-based scoring is available in the engagement request and assessment questionnaires in legacy
engagement risk assessment projects and the engagement request inherent risk screening questionnaire in
control-bases engagement risk assessment projects in sites that include SAP Ariba Supplier Risk. It is not available
in sourcing events or modular supplier management questionnaires.
You can only pre-grade questions that have defined or quantifiable answers.
Questions with defined answers include multiple choice and Yes/No questions. For example, you cannot pre-grade
a question of type Text (single line limited) with no defined acceptable answers because a respondent can answer
with any possible text, and there is no way to quantify and grade such an answer. However, if you set the
Acceptable Values option to List of Choices for the question, so that the respondent must choose from a set of
predefined answers, you can pre-grade each answer. Yes/No questions automatically include two defined answers:
yes and no.
Questions with quantifiable answers include Whole Number, Money, and Date. Answers to these questions are
numerical quantities that can be calculated or, in the case of dates, counted.
Related Information

About pre-grading Yes/No questions
To pre-grade questions with Yes/No answers, enable pre-grading and specify the pre-grades for the answers.
To pre-grade Yes/No questions in a Microsoft Excel spreadsheet, you must map No or the Boolean false value first,
or to the left of the pipe character. For example, if the pre-grade values are No=0 and Yes=100, enter 0|100 in the
Microsoft Excel spreadsheet. If No=100 and Yes=0 then enter 100|0 in the Microsoft Excel spreadsheet.
Pre-grading for Yes/No questions is based on the values you specify. For example, if you assign a pre-grade of 100
to a Yes answer, then it receives a grade of 100%.
About pre-grading multiple-choice questions
To pre-grade questions with a predefined list of possible answers, enable pre-grading and specify the grades to
assign each available answer in advance.
For example,you might have a multiple choice question with four possible choices, A, B, C, and D. You assign A 0%,
B 50%, C 70%, and D 100%. Each possible choice can have an assigned grade between 0% and 100%.
Pre-grading for the answers to multiple choice questions is based on the values you specify.
 Note
● If the question has the Allow participants to specify other value? option set to Yes, the other values
supplied by respondents cannot be pre-graded and therefore are not included in score calculations.
● If the question has the Allow participants to select multiple values? option set to Yes, the grade assigned
to each answer the respondent selects is included in the score calculation. In percentage-based scoring,
this option might contribute to a total score of over 100%.
About pre-grading number and date questions
Since questions that require numerical answers can receive answers that span a range of values, a calculation
assigns them a grade.
The calculation is based on three values you specify: From (a minimum possible value), To (a maximum possible
value), and Ideal (your preferred value). The calculation assigns the grade based on the answer's position relative
to those three values.

When pre-grading number and date questions, keep the following points in mind:
● The Ideal value must be a number between the To and From values.
● Negative numbers produce no special behavior. For example, assigning From= -5, Ideal=1, and To=10 results in
a pre-grade of 0% for -5, which ramps up to 100% for 1, and drops back down to 0% at 10.
● It is important to determine the range of likely answers to your question as accurately as possible and set the
To and From values accordingly. Setting the To and From values too closely together increases the likelihood
that more answers will fall outside of the range and be assigned a grade of 0%. If you set them too far apart, a
great many answers might qualify as nearer your ideal value than is accurate, rendering your results less
useful.
You can assign numeric values to all, one, or a combination of From, To, and Ideal values.
Assigning From, To, and Ideal values
Assign From, To, and Ideal values to favor answers that are neither too great nor too small.
Assigned grades start at 0% for the From value, climb to 100% for the Ideal value, and descend again to 0% for the
To value.
For example, you might be selecting a model of car to add you your company’s fleet. You do not want a car that is
too slow at top speed, but also one that has too much horsepower. In this case you might assign the slowest
acceptable top speed in the From value to 100 MPH, the fastest acceptable top speed in the To value to 160 MPH,
and the ideal top speed in the Ideal value to 120 MPH.
In this example, assigned grades start at 0% for 100 MPH, climb to 100% for 120 MPH, and descend again to 0%
for 160 MPH.
Assigning From and Ideal values, but no To value
Assign From and Ideal values without specifying a To value when you do not want to place a restriction on the
maximum value a respondent can provide for a question.
The assigned grade is 0% for answers less than or equal to the From value, rising to 100% for answers equal to or
greater than the Ideal value.
For example, you might be selecting a model of car to add to your company’s fleet. You want the car to hold at least
three passengers, ideally five passengers, with no upper limit. In this case you assign a value of 3 to the From value,
a value of 5 to the Ideal value, and assign no value to To.
In this example, the assigned grade is 0% for answers of 3 or fewer, and 100% for answers of 5 or greater.

Assigning Ideal and To values, but no From value
Assign Ideal and To values without specifying a From value when you do not want to place a restriction on the
minimum value a respondent can provide to a question.
The assigned grade is 0% for answers equal to or greater than the To value and rises to 100% for answers less than
or equal to the Ideal value.
For example, you might be selecting a model of car to add to your company’s fleet. You want the car to cost no
more than $30,000 USD, ideally $22,000 USD, but without setting a lower limit. In this case you assign a value of
30000 to the To value, a value of 22000 to the Ideal value, and assign no value to From.
In this example, the assigned grade is 0% for answers of 30000 or greater and 100% for answers of 22000 and
less.
Assigning only an Ideal value
Assign an Ideal value but no From or To values when you want to solicit a single, specific answer.
The assigned grade is 100% for answers of the Ideal value and 0% for all other answers.
For example, you might be selecting which model of car to purchase for your company’s fleet. You want it to have a
four-cylinder engine, no more, no less. In this case you specify an Ideal value of 4, and leave the From and To values
empty.
In this example, the assigned grade is 100% for answers of 4 and 0% for all other answers.
Assigning only a From value
Assign a From value but no To or Ideal values when you have a specific maximum threshold value that you require,
after which a greater answer does not add value for you.
The assigned grade is 0% for answers less than the From value and 100% for all answers equal to or greater than
the From value.
For example, you might be selecting which model of car to purchase for your company’s fleet. Your company has a
policy of only purchasing cars that have been in production for at least ten years. Set the From value to 10, and
leave the To and Ideal values empty.
In this example, the assigned grade is 0% for answers less 10 and 100% for all answers equal to or greater than 10.

Assigning only a To value
Assign a To value but no From or Ideal values when you have a specific minimum threshold value that you require,
after which a lesser answer does not add value for you.
The assigned grade is 0% for answers greater than the To value and 100% for answers equal to or less than the To
value.
For example, you might be selecting which model of car to purchase for your company’s fleet. In order to purchase
a car, your company requires it to be financed with a loan of 4% APR. or lower. Set the To value to 4, and leave the
From and Ideal values empty.
In this example, the assigned grade is 0% for answers greater than 4%, and 100% for answers equal to or less than
4%.
Structural considerations for scoring supplier

questionnaire content
The hierarchical structure of the content in a supplier questionnaire affects its scoring. Combining questions
outside of sections with questions in sections, or nesting sections within sections, produces specific scoring
behavior.
In supplier questionnaires, the base level is the root or beginning of the hierarchical scoring structure. Content in
the base level has a number with no decimal points such as 1 or 2.
Supplier questionnaire scoring is simplest when:
● Either the questionnaire does not use sections at all and every question is at the base level, or the
questionnaire does use sections and every question is in a section. Note that if the questionnaire does not use
sections, you cannot use weight points in scoring. If the questionnaire includes both questions and sections at
the base level, both contribute equally to the maxinum number of scoring points for the questionnaire [page
211], which can produce unexpected results.
● In questionnaires with sections, all sections are at the base level rather than nested. Only sections at the base
level contribute to the questionnaire's maximum number of scoring points, and the weights of nested sections
only apply to scoring within the section [page 213].
You can score questionnaires with more complicated structures, but keep these behaviors in mind if you do so.
 Note
Currently, scoring is only supported for static sections. It is not supported for repeatable sections.
About scoring for questions in the base level
Scoring is simplest when you place questions and event line items inside sections. Structuring content differently
(for example, placing a question outside of a section) can cause confusion about the resulting scores.
The base level is the root or beginning of the hierarchical scoring structure. Content in the base level has a number
with no decimal points, for example, notice 1 Section 1, or 3 A question created outside of a

section in the following graphic. Content numbering with a decimal point (for example 1.2) indicates that the
content is nested inside a section.
In the following graphic, the Maximum points for content field does not equal the sum of the Weight column. That
is because the Maximum points for content field is the sum of all the scoring points in the base level. Both Weight
and Importance are scoring points.
The Maximum points for content field in the previous graphic equals 7, and not 2, because there is a question at
the base level, outside of any section, causing its Importance points to be added into the Maximum points for
content field.
The Overall % of any piece of content is calculated in relation to other content in the same hierarchical location.
Since there is a question at the base level, its Overall % is calculated in comparison to the Weight of the sections at
the same level. The total number of scoring points assigned in that hierarchical location is 7, five of which belong to
the question. So the Overall % of question 3 is 5/7, or 71.43%.
Place the question inside of Section 2, as shown in the following graphic, to cause the Maximum points for
content to reset to 2. Then the Overall % of the question is calculated in the standard way.
Related Information
About Importance [page 206]

About weight [page 205]
About scoring nested sections
If you nest sections inside of other sections, the resulting scoring can produce unexpected results because
sections nested within other sections are not scored with their parents.
For example, in the following graphic, Section 2 is nested inside of Section 1. The weight points of Section 2
do not count towards the Maximum points for content field since they are not located in the base level. Only the
weight points of Section 1 are located in the base level.
The event or survey document indents Weight fields to illustrate the hierarchical scoring structure. For example,
since Section 1 is the only content located in the base level, it contributes all of the scoring points to that level
and receives an Overall % of 100%. Likewise with Section 2. It is the only content nested within Section 1 and
contributes all of the scoring points to that level, causing it to receive all of Section 1’s Overall %.
How to set up scoring bands for a modular supplier

management questionnaire
To categorize and label questionnaire scores in scoring bands, you specify the scoring band category you want to
use and then define the range of questionnaire scores for each band in the category.
Prerequisites
To set up scoring bands for a modular supplier management questionnaire, you must be a member of both the
Template Creator and SM Modular Questionnaire Manager groups.
Scoring band category and scoring bands must be defined in your site.
The type of the modular supplier management questionnaire for which you want to set up scoring bands must have
an evaluation type of Graded.

To generate a numerical score that translates into a scoring band, you must also add scoring [page 217] to the
questions and sections in the questionnaire survey document. You can add scoring to the questionnaire before or
after setting up scoring bands for it.
Context
Scoring bands are or grouping of scores. All scores within a band receive the same judgment and the same label,
such as "Good," "Average," or "Poor." Next to each score, a colored dot provides a visual indicator of the band into
which the score falls, and hover text identifies the band by name and shows its associated score range.
You enter Score From and Score To values define the score ranges for each band in the selected band category.
You must define a range for every band in the category, and the ranges you define must, in total, include every
number from 0 to 100. A band range goes from the Score From value up to, but not including, the Score To value.
Except for the band that starts at 0, the Score From value you specify must always be the same number as the
Score To value of the immediately lower band. For example, you can define a score range of 0-25 for band A and a
score range of 25-50 for band B. Scores from 0 through 24 fall in Band A, but a score of 25 falls in band B.
The scoring bands you set up here always apply to the overall questionnaire score. By default, they also apply all of
the scores for individual sections in the questionnaire. If you enable section-level scoring for this particular
questionnaire, the scoring bands you set up here apply only to the overall questionnaire score, and you must set up
scoring bands for each individual section separately [page 215].
Procedure
1. If the modular supplier management questionnaire project template is not in Draft status, create a new version
of it.
2. On the Overview tab, choose Actions Edit Properties .

3. On the Band Category dropdown menu, choose the type of scoring band you want to apply to the
questionnaire score.
The Band Score Range setting shows all of the bands defined for the category you selected.
4. Enter a score range for each band in its Score From and Score To fields.
5. (Optional) To set up scoring bands at the individual section level, for Enable Section Level Band, choose Yes.
Results
When you publish the modular supplier management questionnaire project template with scoring bands and
questionnaire scoring [page 217], whenever a respondent submits a questionnaire created from it, their answers
generate an overall score for the questionnaire. To the left of the score, a colored band indicator and label identify
the band into which the score falls based on the scoring band setup for the questionnaire.
If you did not enable section-level scoring bands for the questionnaire, the questionnaire band settings also apply
to section scores.

Next Steps
If you enabled section-level scoring bands for this questionnaire, set up scoring bands for each individual section
[page 215].
Related Information
How to set up scoring bands for individual questionnaire

sections
To categorize and label scores for individual questionnaire sections in scoring bands, you specify the scoring band
category you want to use and then define the range of section scores for each band in the category.
Prerequisites
To set up scoring bands for individual sections in a modular supplier management questionnaire, you must be a
member of both the Template Creator and SM Modular Questionnaire Manager groups.
Scoring band category and scoring bands must be defined in your site.
The type of the modular supplier management questionnaire for which you want to set up section-level scoring
bands must have an evaluation type of Graded.
Section-level scoring bands must be enabled on the template Overview tab [page 213].
Context
Scoring bands are or grouping of scores. All scores within a band receive the same judgment and the same label,
such as "Good," "Average," or "Poor." Next to each score, a colored dot provides a visual indicator of the band into
which the score falls, and hover text identifies the band by name and shows its associated score range.
Section-level scoring bands apply only to the current section. You can use them to:
● Apply different scoring band categories to different sections in the same questionnaire. For example, you
might apply code of conduct scoring bands to a section of questions about compliance with your
organization's code of conduct and regulatory compliance scoring bands to a section of questions about
compliance with legal regulatory requirements. The code of conduct band category might have three bands:

one for compliant scores, one for non-compliant scores, and one for undecided scores, all with names specific
to code of conduct agreement. You can then associate the scores that mean agreement to your code of
conduct with the compliant band, scores that mean provision of an alternative code of conduct with the
unknown band, and scores that mean lack of agreement with the non-compliant band. This setup provides
clear guidance about the answers to the code of conduct questions, but it is very specific to code of conduct
questions. The regulatory compliance band category might have a larger number of bands with more general
names. By applying the most appropriate band category to each individual section, you can provide more
precise guidance to approvers and other stakeholders who need to evaluate its answers and decide how
acceptable they are.
● Define different scoring ranges for the same bands in different sections of the same questionnaire: For
example, you might apply a control effectiveness scoring band category with two bands (effective and
ineffective) to two different sections of questions about security controls. One section might contain questions
about optional controls, and you might define a score range of 20-100 for the effective band to indicate that a
fairly low score for this section is acceptable. The other section might contain questions about important or
critical controls, and you might define a score range of 90-100 for the effective band to indicate that only a very
high score for this section is acceptable.
You enter Score From and Score To values define the score ranges for each band in the selected band category.
You must define a range for every band in the category, and the ranges you define must, in total, include every
number from 0 to 100. A band range goes from the Score From value up to, but not including, the Score To value.
Except for the band that starts at 0, the Score From value you specify must always be the same number as the
Score To value of the immediately lower band. For example, you can define a score range of 0-25 for band A and a
score range of 25-50 for band B. Scores from 0 through 24 fall in Band A, but a score of 25 falls in band B.
The scoring bands you set up here apply only to this section.
You can only set up scoring bands for static sections. They are not supported in repeatable sections.
 Note
If you have enabled section-level banding in a questionnaire, you must set up scoring bands for each of the
questionnaire's sections individually. Whether or not you plan to add scoring to an individual section and its
questions, you cannot publish the questionnaire template unless all of its sections have banding settings.
Sections with no scoring do not show associated scoring bands, but the band settings are required.
Procedure
version.
2. On the Documents tab, click the questionnaire survey document and choose Edit.
3. Click Content.
○ To set up scoring bands for an existing section, click the section and choose Edit.
○ To add scoring bands to a new section, choose Add Section .
5. On the Band Category dropdown menu, choose the type of scoring band you want to apply to the
questionnaire score.
The Band Score Range setting shows all of the bands defined for the category you selected.

6. Enter a score range for each band in its Score From and Score To fields.
Results
When you publish the modular supplier management questionnaire project template with scoring bands and
questionnaire scoring [page 217], whenever a respondent submits a questionnaire created from it, their answers
generate scores for each question and section as well as the overall questionnaire. To the left of each section score,
a colored band indicator and label identify the band into which the section score falls based on the scoring band
setup for the section.
Related Information
How to add scoring to a modular supplier management

questionnaire
Adding weights to sections and importance and pre-grades to questions with defined or quantifiable answers in a
modular supplier management questionnaire allows the questionnaire to calculate scores based on respondent
answers.
Prerequisites
You must be a member of both the Template Creator and SM Modular Questionnaire Manager groups to add
scoring to survey documents in modular supplier management project templates.
To group questionnaire scores into scoring bands and show color-coded indicators for those bands, band category
[page 45] and band [page 47] data must be defined for your site.
Context
Modular supplier management questionnaires calculate scores at the section level and those scores roll up to an
overall questionnaire score. You set up scoring bands [page 213] with defined score ranges for the questionnaire.
These bands apply to section scores as well unless you set up scoring bands at the individual section level [page
215].

Modular supplier management questionnaires use percentage-based scoring. They do not support point-based
scoring. Percentage-based scoring uses question pre-grades [page 207] together with question importance and
section weight [page 205] to calculate section and overall questionnaire scores. Before you start scoring a modular
supplier management questionnaire, it is important to understand how pre-grades and scoring points work.
Target Grade values are not currently used in modular supplier management questionnaire scoring.
Procedure
version.
2. On the Documents tab, click the questionnaire survey document and choose Edit.
3. Click Rules.
4. In the Bidding Rules area, make sure that Choose Scoring Type is set to Percentage Based Scoring and
Delegated.
5. Click Content.
6. On the Display dropdown menu, choose Scoring.
The Content table shows scoring-related fields.

7. Enter a Weight value [page 205] for each section you want to contribute to the questionnaire score calculation.
Sections with a weigh of 0 do not contribute to scores.
 Tip
The values you specify for section weights can be any numbers, but using numbers that add up to a total of
100 makes it easier to determine how your weight and importance settings contribute to the overall score
calculation for the questionnaire.
8. Choose an Importance value [page 206] of 1-10 for each question you want to contribute to the questionnaire
score calculation, with 10 being the highest importance. Questions with an importance of 0 do not contribute
to scores.
9. Pre-grade [page 207] possible answers to questions with defined answers, such as number, date, multiple
choice, or Yes/No questions, by performing the following actions:
a. In the Pre-grade column, choose Yes from the dropdown menu.
b. For multiple choice and Yes/No questions, select a pre-grade percentage value from 0-100 for each
available answer. For number and date questions, enter values in one, two, or all of the From, Ideal, and To
fields to define the pre-grading for a range of possible answers.
10. Click Update at any time to recalculate the Overall % for the current scoring configuration.
11. When you have finished adding scoring to the questionnaire, click Exit, then click Save and then exit.
Results
Once you publish the new version of the template and a respondent submits a questionnaire created from that
version, the questionnaire automatically calculates section and overall scores based on your settings. The overall
questionnaire score and scoring band indicator show in the Questionnaire area of the new supplier 360° profile.

Both the overall questionnaire score and individual section scores and band indicators show on the questionnaire
details page.
Related Information

Topics about creating supplier forms and
questionnaires
About creating supplier forms and questionnaires [page 220]
How to create a supplier-related internal questionnaire [page 229]
Topics about adding content to a supplier form or questionnaire [page 231]
Topics about using visibility conditions to show or hide questionnaire content based on answers [page 299]
Topics with supplier management questionnaire content examples [page 305]
About creating supplier forms and questionnaires

SAP Ariba Supplier Management solutions use forms and questionnaires to collect information about suppliers
from both internal stakeholders and the suppliers themselves.
Supplier management projects such as supplier requests and registrations uses template survey documents to
create forms and simple questionnaires. The qualification project (available only in SAP Ariba Supplier Lifecycle
and Performance) uses template survey and content documents to create dynamic questionnaires with segments
targeted by commodity, region, and, in sites with the business unit supplier management matrix enhancement
enabled, departments.
Some supplier management projects can also use survey documents to solicit information from internal
stakeholders.
You can map questions [page 260] in supplier management forms and questionnaires to specific fields in the
vendor database so that their answers are always stored in an appropriate database field.
Related Information


220 PUBLIC Topics about creating supplier forms and questionnaires
Supplier form or questionnaire closing, reopening,

and due dates
External (supplier-facing) questionnaires close when a supplier submits them and reopen under certain
circumstances. The questionnaire due date always determines how much time a supplier has to fill out a new
questionnaire before it closes, and might affect how long a supplier has to update a questionnaire after it reopens.
The timing rules of the template survey document for a supplier form or questionnaire include a Due date setting.
It defines how much time a supplier has to fill out and submit a new questionnaire before it closes. The countdown
to the due date starts when the supplier is invited to fill out the questionnaire.
The questionnaire closes either when the supplier has submitted the questionnaire or when the due date is
reached, whichever comes first. When the questionnaire is closed, the supplier can no longer edit it.
The questionnaire reopens automatically when:
These questionnaire types... Reopen when...
All external questionnaires An approver requests additional information during the appro
val process.
External registration and qualification questionnaires When a registration or qualification manager reinvites a sup
plier to fill out the questionnaire because the supplier did not
respond to the previous invitation by the due date.
External registration questionnaires in projects with new regis When either the new questionnaire or a questionnaire update
tration and registration update phases is approved.
External modular supplier management questionnaires ● When a category or supplier manager reminds the sup
plier to fill out the questionnaire because the supplier did
not respond to the previous invitation by the due date.
● If the Always open setting in the template survey docu
ment is set to Yes, when either the new questionnaire or a
questionnaire update is approved.
Once a questionnaire has reopened, the supplier can edit and resubmit it until it closes again. Questionnaires in
registration and modular supplier management questionnaire projects include a Keep questionnaire reopened
indefinitely setting. If you specify Yes for this setting, every time the external questionnaire reopens, it remains
reopened indefinitely. For modular questionnaires, the Always open setting performs the same function, and if it is
set to Yes, the Keep questionnaire reopened indefinitely setting has no impact.
If the Keep questionnaire reopened indefinitely setting is set to No, the amount of time a questionnaire remains
reopened is determined by the site configuration parameter
Application.AQS.RFX.ReopenIfClosedInterval (set by SAP Ariba Support) in your site. The default
amount of time is 365 days, but your site might use a different number of days. If the setting for the parameter is 0,
the amount of time a reopened questionnaire remains open is determined by the template survey document Due
date setting instead. In this case, make sure that the due date you set for the questionnaire takes into account not

Topics about creating supplier forms and questionnaires PUBLIC 221
just the expected response time for a new questionnaire but its expected update cycle. If the Keep questionnaire
reopened indefinitely setting is set to Yes, the template ignores the
Application.AQS.RFX.ReopenIfClosedInterval site parameter and remains reopened indefinitely.
For modular questionnaires, if Always open is set to Yes and you have enabled reminders, after the new
questionnaire is approved and it reopens for updates, the Due date setting determines when its reminder schedule
resets. For example, if you set a due date of 180 days, after the questionnaire reopens, it generates reminders
relative to that due date. If the recipient submits an update on day 50, the reminder schedule resets to 180 days. If
the recipient does not update the questionnaire by the due date, the reminder schedule resets to 180 days on the
due date, but the questionnaire remains open.
After a questionnaire has closed, the only way to reopen it is for a user to work in the advanced view of the project
to manually monitor and reopen the questionnaire. Note that to see the advanced view of a supplier management
project, your site must be configured to show Advanced View links and you must have appropriate group
membership permissions.
Modular supplier management questionnaires can expire, but questionnaire expiration is a status change that
indicates the current validity of the questionnaire content. It is not related to whether or not the questionnaire is
open or the questionnaire due date. An expiring or expired questionnaire that is set to always be open only closes if
the supplier does not update it before it due date. Otherwise, it remains open until the supplier submits an update.
Related Information

About creating supplier forms and questionnaires [page 220]
How to create a supplier form or questionnaire

Forms are useful if you have a relatively small set of content, such as with a request. The content in forms is not
numbered. Questionnaires are useful if you have a large set of content and want it to be numbered.
Prerequisites
You must be working with a new version of the template, so that the template itself is open for editing, to edit an
existing survey document or create a new one.

Context
 Note
and so forth) that are not relevant to supplier management processes. These settings are ignored in supplier
management projects. Certain settings on its Rules page and the content on its Content page are used in
supplier management projects.
Depending on the project type for the form or questionnaire, you might use the following settings on the Rules page
of template survey documents:
Rule type Setting Applicable project types Description
Timing Rules Due date All projects with external Determines how much time a
questionnaires supplier has to fill out and
submit the form or question
naire before it closes. See
Supplier form or questionnaire
closing, reopening, and due
dates [page 221] for more in
formation.
Reminder for the Due date Supplier registration Generates reminders to sup
setting
pliers who have not yet sub
mitted the questionnaire at
the times you specify relative
to the due date.
Due date reminder settings

are available in questionnaires
in all supplier management
project types. However, in all
projects except for supplier
registrations, they generate
notifications based the default
survey document message
templates, which are shared
with sourcing events. For ex
ternal supplier registration
questionnaires, there are reg
istration-specific message
templates.
Keep questionnaire Supplier registration After initial project approval or

reopened indefinitely update approval, keeps the ex
Modular supplier manage ternal questionnaire reopened
ment questionnaire indefinitely for further up
dates.

Rule type Setting Applicable project types Description
Send reminders for periodic Supplier registration Generates periodic notifica-

updates tions reminding the supplier to
update the questionnaire at
the defined intervals.
Supplier Management Specify questionnaire format All Specifies whether the survey
document is an unnumbered
form or a numbered question
naire.
Is questionnaire required? Supplier registration Specifies whether or not a reg

istration manager can opt not
to include the questionnaire
when starting a supplier regis
tration.
Specify questionnaire type Supplier registration Specifies whether the audi

ence for the questionnaire is
Supplier qualification internal users in your site or
external suppliers.
Modular supplier manage
ment questionnaire (for as Questionnaires in registration
sessments used in SAP Ariba projects have a third option,
Supplier Risk engagement risk Supplier Profile, which speci
assessment projects only) fies that the questionnaire is
internal and its approval or de
nial does not affect registra
tion status.
Questionnaires in qualification
projects have a third option,
Qualification Request, which
specifies that the question
naire is used to start supplier
qualifications.
Reuse, Always open, and Can Modular supplier manage See How to set up a modular
expire? ment questionnaire supplier management ques
tionnaire [page 195].
Message Board Sender name used for the Supplier registration Specifies a default custom
'From' and 'Reply To' fields in sender name to use in the
emails to participants "From" and "Reply To" fields in
questionnaire-specific notifi-
cations for external registra
tion questionnaires. This set
ting is only available if the self-
service configuration parame
ter Enable configurable
default sender for supplier
invitations is enabled in your
site.

Procedure

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 Timing Rules area, perform the following actions:
a. For Response start date, choose When I Click the Publish button on the Summary page.
In supplier management projects, this setting specifies that the amount of time the respondent has to fill
out the form or questionnaire is counted starting when the project is created. Do not schedule the survey
for the future. Supplier management forms and questionnaires are not designed to work with that setting.
b. For Due Date, choose Duration and specify a duration in days, such as 30 days.
The countdown to the due date starts when the invitation to fill out the questionnaire is sent to the supplier.
For details about the due date setting, see Supplier form or questionnaire closing, reopening, and due
dates [page 221].
c. Specify Delegated where that option is offered.
7. 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 required?, choose Yes.
○ For Specify questionnaire type, choose Internal if only your organization's employees will be filling the
form or questionnaire, or External if external people such as supplier contacts will be filling it out. For
internal registration questionnaires, choose Supplier Profile instead of Internal if you do not want approval
or denial of the internal questionnaire to affect the supplier's registration status.
8. Click Content.
9. Add content to the form or questionnaire. [page 231]
10. Click Summary.
11. Click Exit, then click Save and then exit
Results
Once you publish the new version of the template, the form or questionnaire is available to users.
Related Information


How to set up reminders for suppliers to complete a new registration [page 156]
Enable configurable default sender for supplier invitations [page 518]
How to set up a targeted supplier qualification

questionnaire
Setting up a supplier qualification questionnaire with segments targeted to specific commodities, regions, and
departments 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
edit its survey document..
Context
When you are setting up the targeted qualification questionnaire by editing the survey, do not add any content to it
directly. You add questionnaire content in separate content documents. Qualification projects are the only projects
that support a questionnaire targeted by commodity, region, and department.
 Note
and so forth) that are not relevant to supplier management processes. These settings are ignored in supplier
management projects. Only the timing rule and supplier management settings on the survey's Overview page
and the content on its Content page are used in supplier management projects.
Timing rules for template survey documents are used in supplier-facing forms and questionnaires; they are ignored
in internal surveys. Timing rules determine how much time a supplier has to fill out and submit the form or
questionnaire. They survey is automatically closed once the supplier submits it.

Procedure

its contents.`
5. Click the template's survey document and choose Edit.
6. On the Rules page, in the Timing Rules area, perform the following actions:
a. Choose When I Click the Publish button on the Summary page.
This setting means that the countdown to the due date starts when an internal user starts a qualification
and sends the qualification questionnaire to the supplier.
b. For Due Date, choose Duration and specify a duration in days, such as 30 days.
c. Specify Delegated where that option is offered.
Do not schedule the survey for the future or set a fixed duration. Supplier management forms and
questionnaires are not designed to work with those settings.
7. In the Supplier Management area, perform the following actions:
○ For Specify questionnaire format, choose Questionnaire.

○ For Is questionnaire required?, choose Yes.
○ For Specify questionnaire type, choose External because the qualification questionnaire is sent to
suppliers external to your company.
8. Click Summary.
Results
The qualification questionnaire framework is now ready. The next step is to add content to it by creating
questionnaire segments [page 228].
 Note
Do not publish the survey. Once you publish the new version of the template, your changes become active.
Related Information

How to create a targeted supplier qualification
questionnaire segment
Qualification questionnaire segments are targeted at specific commodities, regions, and departments; category or
supplier managers can add them to the qualification questionnaire based on the commodities, regions, and
departments for which the supplier is qualifying. .
Prerequisites
create questionnaire segments.
If you plan to target questionnaire segments by department, the business unit supplier management matrix
enhancement feature must be enabled in your site, and you must set up a prequalification questionnaire [page 181]
with a mapped department question. The default application page that category or suppliers use to start a
qualification does not include a department setting. The prequalification questionnaire replaces that page and
allows category or supplier managers to specify a department for the qualification as well as the commodity and
region.
Context
Selecting at least one commodity and one region (and if you are using a prequalification questionnaire with a
mapped department question, one department) for each questionnaire segments is required, because it is how you
make sure that the current questionnaire segment is sent to suppliers for those commodities, regions, and
departments.
Commodities, regions, and departments are hierarchical, ranging from high-level (general) to low-level (specific)
values in a hierarchy tree. A questionnaire segment is included in the questionnaire for qualifications at its targeted
level and also at any levels above or below it in its branch of the hierarchy. For example, if you create a questionnaire
segment targeted to the state of California in the United States, it is included in qualifications where the
qualification manager selects a location within California as the region (lower in that branch of the region
hierarchy), or where the qualification manager selects the United States, North America, or all regions (higher up
that branch of the region hierarchy). However, it is not included in qualifications where the qualification manager
selects a different state such as Texas as the region (a different, parallel branch of the region hierarchy at the state
level).
To include a questionnaire segment in all possible qualifications that include a specific commodity, region, or
department, including any subdivisions of that commodity, region, or department, target it to that commodity,
region, or department. To include a questionnaire segment in all qualifications for all suppliers, choose All for
 Note
If you edit content documents in your supplier qualification template and publish the changes, the sequence of
the content documents in future questionnaires is not guaranteed.

Procedure

its contents.`
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 value from the Commodities, Regions, and Departments dropdown menus.
If the commodity, region, or department you want to specify does not appear on the menu, click select more,
select a value, and click Done. If you want to send the questionnaire segment to all suppliers, choose All
9. (Optional) To add more commodities, regions, or departments, click add more to the right of the dropdown
menus and repeat the previous step.
10. Click Create.
11. Add content to the questionnaire segment. [page 231]
12. Click Done.
Related Information

How to create a supplier-related internal

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

Context
In most cases, internal questionnaires are displayed the supplier 360° tile related to the project. For example, in
solutions that include SAP Ariba Supplier Lifecycle and Performance, internal questionnaires in qualification
projects are displayed on the Qualification tile. The exception to this rule is for supplier registration projects, where
internal questionnaires are displayed on the Overview tile; this design allows you to use an internal questionnaire 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 internal surveys. These settings are ignored in internal
surveys. Only the supplier management settings on the survey's Overview page and the content on its Content
page are used in internal surveys.
Procedure

its contents.`

6. In the Title field, enter a descriptive title for the questionnaire. The title displays as the heading for the
questionnaire in supplier 360° profiles.
7. (Optional) In the Description field, enter descriptive information about the questionnaire. This information is
only visible in the template.
8. Click Create.
9. On the Rules page, in the Supplier Management area, perform the following actions:
○ For Specify questionnaire format, choose Form.

○ For Specify questionnaire type, choose Internal.
○ To make the questionnaire required, for Is questionnaire required?, choose Yes.
10. Click Content.
11. Add content to the questionnaire. [page 231]
12. Click Summary.
Results
Once you publish the new version of the template, the internal questionnaire is available to users.

Related Information
Topics about adding content to a supplier form or

questionnaire
How to add a section to a supplier form or questionnaire [page 231]
How to add a repeatable section to a supplier form or questionnaire [page 232]
Topics about adding questions to supplier forms and questionnaires [page 235]
How to add a requirement to a supplier form or questionnaire [page 294]
How to add translations for some form and questionnaire content fields [page 295]
How to add an attachment to a supplier form or questionnaire [page 296]
How to add a section to a supplier form or questionnaire
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.
If your solution includes SAP Ariba Supplier Lifecycle and Performance, top-level sections in questionnaire
segments are useful for organizing content in the final qualification 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.
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 299] for details.
7. Click OK.
Related Information

[page 245]
How to add a repeatable section to a supplier form or

questionnaire
A repeatable section is a container in which you organize other content, such as questions, requirements,
attachments, static sections, and nested repeatable sections. The questionnaire shows an initial instance of the
repeatable section and its content; respondents can then add as many repetitions as they need.
Prerequisites
Repeatable sections are not supported in internal questionnaires in sites that use the classic 360° profile under any
circumstances. For the new supplier 360° profile (SM-14322), although the release guide information stated that
the new supplier 360° profile supports editing repeatable sections in internal questionnaires, this functionality is
not currently supported and has been disabled by default. To preserve backward compatibility, SAP Ariba has
enabled it in customer sites where it is already in use, but repeatable sections in internal questionnaires might not
function as expected in all use cases. SAP Ariba will announce general availability of this functionality when it
supported.

Repeatable sections are supported in external (supplier facing) questionnaires. Note that because suppliers access
the external supplier request in your site rather than through Ariba Network, it functions like an internal
questionnaire and has the same restrictions.
Context
Repeatable sections are useful for collecting any type of information that involves a set of questions and for which
respondents typically have an unknown multiple number of answers, such as locations, contacts, bank and tax
details, and so on. For example, if you about supplier bank accounts using a repeatable section, the questionnaire
recipient can add repetitions for each supplier bank account.
You can nest repeatable sections in other repeatable sections to capture sets of information in a hierarchical
structure. For example, if you want to ask a supplier about contacts in different roles, you can nest a repeatable
Contacts section inside a repeatable Contact Roles section (Contact Roles > Contacts). Then, when a
supplier adds a new contact role to the questionnaire, they can add one or more contacts to it. The contacts are
associated with the roles to which they are added. The supplier can then add a second role with different contacts.
 Note
Repeatable sections have the following restrictions related to integration with SAP ERP, SAP S/4 HANA, SAP
S/4 HANA Cloud, and SAP MDG-S systems:
● Supplier contact information is not synchronized to the integrated system.

● While you can collect multiple supplier extended addresses in repeatable sections, replicating multiple
addresses to the integrated system is not currently supported.
● Data in nested repeatable sections is not synchronized to the integrated system.
In template survey and content documents, you use two pieces of content to create a repeatable section: a
repeatable section parent and the repeatable section itself. These pieces of content are always paired together,
with the repeatable section parent serving as an otherwise empty container for the repeatable section and its
content. You can only add a repeatable section inside a repeatable section parent, and you add content such as
questions in the repeatable section, not the parent. You can only add one repeatable section inside a repeatable
section parent.
The repeatable section parent defines the overall section, and its name provides the section heading. Inside the
repeatable section parent, the repeatable section contains the questions and other content that repeats. The name
you give it defines the repeating unit. Both parent and section names appear in various user interface controls that
both suppliers and people in your organization use to interact with repeatable sections. Keep this usage in mind
when naming both the parent and the section in the template:

This name... Is used in these places...
Repeatable section parent name; for example, Contact For suppliers filling out questionnaires:
Roles ● In the links they click to add or edit repetitions of the sec
tion; for example, Add Contact Roles (1).
● As the page title for the page where they answer questions
in the section and add or remove repetitions.
For internal users reviewing questionnaires:
● As the top-level heading for the repeatable section on the

questionnaire page; for example, 3 Contact Roles.
Repeatable section name; for example, Contact For suppliers filling out questionnaires:
● As the numbered title of each repetition of the section

they add; for example, if a supplier adds two factories, the
page on which they edit the answers labels those repeti
tions Contact #1 and Contact #2.
● In the label of the button they use to add more repetitions;
for example, Add Contact.
For internal users reviewing questionnaires:
● As the heading for the section on the questionnaire page

and the link to click to review section answers; for exam
ple, 3.1 Contact (2).
You can nest repeatable sections inside static sections; you can also add static sections to repeatable sections to
further organize their content. You can use visibility and editability conditions with repeatable sections and their
content in the following circumstances:
● In all types of questionnaires, you can apply visibility and editability conditions to a repeatable section as a
whole so that a question outside the repeatable section triggers the condition on the repeatable section itself.
● In external questionnaires, you can apply visibility and editability conditions on content within a repeatable
section so that a question outside the repeatable section triggers the condition on the repeatable section
content. You cannot use content within a repeatable section to trigger conditions on content outside of the
repeatable section.
● In internal questionnaires, you cannot use content outside of a repeatable section to trigger a condition on
content within a repeatable section or use a question within a repeatable section to trigger content outside of
the repeatable section.
Procedure
1. Open the supplier management template for editing. If it is not in Draft, create a new version.
2. Add or edit the template survey or content document to which you want to add the repeatable section.
3. At the bottom of the content table, choose Add Repeatable Section Parent .
4. Enter a title for the repeatable section parent.

5. (Optional) To apply a visibility or editability condition to the entire repeatable section, click none and choose an
existing condition or create a new condition.
6. Click OK.
7. In the content table, click the repeatable section parent you just created and choose Repeatable Section.
8. Enter a title for the repeatable section.
9. Click OK.
10. In the content table, click the repeatable section you just created and add questions, attachments,
requirements, or sections to it as needed. You can also nest another repeatable section in it by adding a
repeatable section parent to it, then adding a repeatable section inside the parent.
 Note
The following restrictions apply to questions in repeatable sections:

○ Questions of type Address are not supported in repeatable sections. You can add questions of type
Extended Address to repeatable sections. However, note that multiple supplier addresses are not
replicated to an integrated ERP system.
○ Do not create mapped questions of type Commodity, Region, or Department in repeatable sections.
There can be only one mapped question of each type in a single supplier management project.
○ Mapping repeatable sections to vendor database fields requires a specialized mapping syntax, and you
can only map repeatable sections to array fields, which support storing multiple answers in the same
field. See Mapping questions in repeatable sections to supplier database fields [page 261] for details.
11. When you are finished making your changes, publish the new version of the template.
Related Information
Mapping questions in repeatable sections to supplier database fields [page 261]

Topics about adding questions to supplier forms and

questionnaires
Question answer types for supplier forms and questionnaires [page 242]
About automatically applying field restrictions to questions in supplier management questionnaires [page 244]
[page 245]
How to add a question about integrated master data to a supplier form or questionnaire [page 248]
Collecting supplier address information using Address or Extended Address questions [page 250]

Turning questions into search filters using search terms [page 255]
Using code delimiters to associate descriptive questionnaire answers with ERP or other codes [page 257]
Topics about field mappings for questions in supplier management questionnaires [page 259]
How to add a question to a supplier form or questionnaire
A question is a content item that asks the respondent to provide some type of information. The answer type you
specify for a question determines the type of information and the format of the response.
Context
The Add Question page includes a number of settings (include in cost, access control, participant-specific initial
values, and so on) 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. If you are creating a Text (single line limited) or Text (single line) answer type question, you can
optionally use the Apply field restrictions button to have the system suggest a field validation pattern and
maximum length based on the default SAP ERP business partner configurations of the mapped field. The Apply
field restrictions button is not available in SAP Ariba Supplier Risk engagement risk assessment and issue
management projects.
 Tip
● Answers for questions with the Whole Number answer type have a maximum value of 2147483647, making
it suitable for amounts but not for questions that have numerical answers that might exceed the maximum,
such as phone numbers. For questions with large numerical answers that are not amounts, use Text (single
line limited) instead.
● Individual questions have KI ID numbers, which are unique identifiers, and the supplier responses that
duplicate checks match against are linked to KI IDs. Duplicate checks match question responses against
recorded supplier responses that are associated with that question's KI ID. As a result of this, if you delete
and recreate a question, duplicate check does not match responses to the recreated question against
stored response data from the deleted question.
 Note
Make sure that the questions you create in supplier-facing questionnaires do not ask for sensitive personal
information as defined in the SAP Ariba Privacy Statement .

Procedure
○ 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.
○ For questions with answer type Text (single line limited) only, 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 Type of master data for answer dropdown menu.
○ To force respondents to choose from a set of answers you predefine, 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: in external-facing questionnaires, the supplier
must answer the question. In internal-facing questionnaires, the internal
user must answer the question.
○ Yes, Owner Required: Do not use this setting. In supplier management
projects, all internal and external users who complete forms, questionnaires,
and internal surveys act as participants. There is no way to satisfy an owner
requirement, and using this setting will cause users to be unable to submit
the form or questionnaire.
Tooltip Specifies a message to show in a popup that users open by clicking an informa
tion icon next to the question. If you specify a tooltip, you can use the
Translations link to provide translations for it in languages other than your site's
primary language.
 Note
The Tooltip field is only available in engagement request questionnaires in
the supplier engagement risk assessment project.
Reference documents Click Attach a file to attach a reference file to the question; 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.
Mask Attachments Specifies whether or not you want to mask attachments so that only the users
with the appropriate permissions can view or download them.
 Note
The attachment masking setting is not supported in supplier engagement
risk assessment and issue management projects.
Sensitive Data Mask Pattern If you want to mask the answer so that only users with the appropriate permis
sions can view it, you can specify a masking pattern to mask all or part of the an
swer.
 Note
The data mask pattern setting is not supported in supplier engagement risk
assessment and issue management projects.

Code Delimiters Specifies the characters that enclose the codes you associate with descriptive
answers in a list of choices. If you specify code delimiters, and then create a list of
choices that includes codes enclosed by those delimiters, that enclosed informa
tion is the only part of the answer stored in a mapped database field.
 Note
The code delimiters setting is not supported in supplier engagement risk as
sessment and issue management projects.
Visible to Participants Specifies whether or not suppliers can see the question. Do not add internal-only
questions to external questionnaires. For external (supplier-facing) question
naires, only choose No if you are setting up a hidden question that triggers a con
ditional approval.
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.
Max length Specifies the maximum character length for text questions. The length you spec
ify must be shorter than the absolute maximum length of the question (255 for
Text (single line limited), 4000 for Text (single line), and unlimited for Text
(multiple lines) answers. Answers cannot exceed the absolute maximum length
for an answer type regardless of the setting you apply in this field.
If you are mapping a question to a supplier database field and the question has a
Text (single line limited) or Text (single line) answer type, you can use the op
tional Apply field restrictions button to automatically generate a suggested max
length. The Max Length setting helps to make sure that the answer does not ex
ceed the maximum length of that field. For mapped questions, the length of the
database field is the ultimate determiner of the stored answer length.
 Note
The maximum length setting is not supported in supplier engagement risk
assessment and issue management projects.
Supplier field mapping If you want to map the question to a supplier database field, enter the field name.
You can also use project and matrix mappings in this field.
The optional Apply field restrictions button can help validate your supplier field
mapping entry. If it does not recognize a supplier field mapping, it suggests alter
native field mappings. The feature can also suggest a Max length and Validation
pattern based on the supplier field mapping.
 Note
Supplier engagement risk assessment and issue management projects do
not support mapping to supplier database fields. They support a specific set
of project and matrix mappings only. See the topics about setting up those
templates for details.

Search term If you want to turn the question into a filter for supplier searches, enter the filter
name.
 Note
○ You can only turn some answer types into search filters, and you should
keep in mind best practices for constructing effective search filters.
Turning questions into search filters is not supported in supplier risk en
gagements
○ Search terms are not supported in supplier engagement risk assess
ment and issue management projects.
.
Validation Pattern and Validation If you want to specify that the answer must be provided in a specific format, en
Pattern Error Message ter a regular expression to define that format and an optional custom error mes
sage that users see when they try to submit an answer that does not fit the pat
tern.
If you are mapping a question to a supplier database field and the question has a
Text (single line limited) or Text (single line) answer type, you can use the op
tional Apply field restrictions button to automatically generate a suggested vali
dation pattern.
 Note
Validation patterns are not supported in supplier engagement risk assess
ment and issue management projects.
Enable duplicate check Specifies whether or not the answer is used to identify duplicate suppliers during
the supplier request process. In both internal and external supplier requests,
questions mapped to name, street address, city, state, country, postal code, and
D-U-N-S Number fields are automatically used in duplicate check. This setting al
lows you to specify additional questions to use in duplicate check. This field is
only available for Text (single line limited) questions in internal and external sup
plier requests in sites with the custom duplicate check feature enabled.
 Tip
Only enable this setting for questions that are likely to yield unique answers
for each supplier. SAP Ariba recommends that you enable this setting for no
more than 5 questions total in an internal or external supplier request. Overly
broad duplicate checks result in a higher number of false positives..
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 299].
8. (Optional) To communicate your expectations of how respondents should answer, provide an initial value 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
Turning questions into search filters using search terms [page 255]
Creating conditional approval flows based on form and questionnaire answers [page 333]
Using code delimiters to associate descriptive questionnaire answers with ERP or other codes [page 257]
[page 245]
Default supplier request duplicate checks and setting up custom duplicate checks [page 144]
About automatically applying field restrictions to questions in supplier management questionnaires [page 244]

Question answer types for supplier forms and questionnaires
For each question you add to a supplier form or questionnaire, 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 ex
panded indefinitely with a vertical scroll bar and no character
limit.
Whole Number A whole number; for example, 20. Answers have a maximum
value of 2147483647. For questions with large numerical an
swers that are not amounts, such as phone numbers or IDs,
use Text (single line limited) instead.
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.
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, num
ber, location, type, and effective and expiration dates, and to
upload a certificate file as an attachment.
 Note
● SAP Ariba does not validate the details in certificate
answers (effective date, expiration date, and so on)
against associated certificate attachments.
● Questions of this type include settings for expiration
notifications in modular supplier management ques
tionnaires only.
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.
Extended Address The answer is an extended set of address fields; the country
and region fields use dropdown menus to allow users to select
from a list of available values. A limited number of fields, in
cluding any fields with values, is shown in a Show Less view;
users can click Show More to see the full set of fields.
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.
Department The answer field is a dropdown menu that allows respondents

to select from the departments or cost centers used in your
site.
Supplier The answer field is a dropdown menu that allows respondents

to select from the suppliers in your site.
This answer type is only available in SAP Ariba Supplier Risk.

Bank Account The answer field is a complete set of bank account fields. This
answer type is only available in sites with the bank component
feature enabled.
This answer type is not available in SAP Ariba Supplier Risk.
Tax The answer field is a dropdown menu for country and a set of
country-specific tax fields defined by master data in your site.
This answer type is only available in sites with the tax compo
nent feature enabled.
This answer type is not available in SAP Ariba Supplier Risk.
Related Information
[page 245]
Predefined fields and field mappings in Bank Account questions [page 278]
About automatically applying field restrictions to questions in

supplier management questionnaires
You can automatically apply multiple field restrictions when you are creating survey questions.
If SM-12250, which introduces a tool that validates supplier field mappings and suggests field restrictions, is
enabled in your site, you can use the Apply field restrictions button. When the question answer type is Text (single
line limited) or Text (single line), the Apply field restrictions button becomes available. If you enter a valid
supplier field mapping, the Apply field restrictions button suggests a field validation pattern and maximum length
based on default SAP ERP business partner configurations.
 Note
If you enter an invalid supplier field mapping, the system offers suggestions.
Related Information

Topics about field mappings for questions in supplier management questionnaires [page 259]

Topics about adding questions to supplier forms and questionnaires [page 235]
How to add a certificate question to a modular supplier

management questionnaire for certificate management
One of the purposes of the modular supplier management questionnaire is to collect certificate information from
suppliers. Questions of answer type Certificate in modular supplier management questionnaire templates have
special settings for certificate management.
Prerequisites
You must be a member of the Template Creator group to create modular supplier management questionnaire
templates.
Certificate types [page 44] must be defined for your site.
Context
Questions of answer type Certificate in modular supplier management questionnaires automatically include the
following detail fields that suppliers see when they answer Yes:
● Certificate Type, which you define in the question settings. Suppliers cannot edit this field.
● Issuer
● Year of publication
● Certificate Number
● Certificate Location
● Effective Date
● Expiration Date
● Attachment
● Description
Regardless of whether or not you make the question itself required, if a supplier answers Yes to the question, they
are required to provide answers in all of these fields except for Certificate Type. To make most certificate fields in
Certificate questions optional, you can enable the site configuration parameter Require only attachment and
expiration date for supplier certificates. All Certificate question fields, except for Expiration Date and
Attachment are optional in external questionnaires. For more information, see Require only attachment and
expiration date for supplier certificates [page 519].
 Note
SAP Ariba does not validate the details in certificate answers (effective date, expiration date, and so on) against
associated certificate attachments.

The certificate answer inherits the commodity, region, and department of its modular supplier management
questionnaire.
You must set the Certificate Type for each certificate question you create. A customer administrator defines the
certificate types in your site via data import.
Questions of answer type Certificate in modular supplier management questionnaires are automatically mapped
to the vendor.certificate database field, and therefore do not include a Supplier Field Mapping setting. In
sites where the certificate management feature is not enabled, add the vendor.certificate mapping manually.
This mapping ensures that certificates provided in answer to the question show in the Certificates area of the
supplier 360° profile. This mapping is the only mapping that does not require the [$index] [page 261] syntax if
the question is in a repeatable section.
The Add Question page includes a number of settings (access control, participant-specific initial values, and so on)
that are not relevant to modular supplier management questionnaires. These settings are ignored in modular
supplier management questionnaire projects. Only the settings discussed in the following steps are used in
modular supplier questionnaire management projects.
Procedure
1. Open the supplier modular supplier management questionnaire template. If it is not in Draft, create a new
version.
3. Click the questionnaire survey document and choose Action Edit .

4. In the left-hand navigation pane, click Content.
○ 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.
6. If you selected a location for the new question, select Add Inside to add the new question nested inside
7. Choose Certificate from the Answer Type dropdown menu.
9. Specify the following settings for the question:
Setting Description and options
Response Required? Specifies whether or not you want to require the supplier to
answer the question. Options are:
○ Not Required
○ Yes, Participant Required: The supplier must answer
the question.

Setting Description and options
○ Yes, Owner Required: Do not use this setting. In sup

plier management projects, all internal and external
users who complete forms, questionnaires, and internal
surveys act as participants. There is no way to satisfy an
owner requirement, and using this setting will cause
users to be unable to submit the form or questionnaire.
Note that for Certificate questions, even if you don't require
a response, if the supplier answers Yes, they must answer all
of the detail questions.
Reference Documents Click Attach a file to attach a reference file to the question;
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.
Visible to Participant Specifies whether or not suppliers can see the question.
Only choose No if you are setting up a hidden question that
triggers a conditional approval.
Certificate Type Choose the applicable certificate type for the question.
Expiration schedule Specifies certain automatic actions that occur when the ex
piration date the supplier provides in the question answer
has passed. You can set the following options:
○ Specify the amount of time before the expiration date
when an automatic notification is sent to the supplier to
remind them to update their answer.
○ Check Notify primary supplier manager and/or Notify
project owners to send automatic notifications to the
applicable internal users at the same time as the sup
plier reminder is sent.
○ Check Update status on the questionnaire when the
certificate is expiring or expired to change the modu
lar supplier management questionnaire project status
to Expiring when the reminder notification for the ques
tion is sent, and to Expired when the certificate expira
tion date provided by the supplier has passed. Note that
if the questionnaire also has an expiration schedule, but
the certificate question reminder or expiration come be
fore the questionnaire's, the certificate settings trigger
the status change for the questionnaire.
Visibility Conditions Specifies the conditions under which suppliers and internal
users at your company see the question. Click none and se
lect an existing condition, or select Create Condition to cre
ate a new condition.
10. (Optional) Provide an initial value as an example, to communicate your expectations of how respondents
should answer by choosing Yes or No as a default value. If you choose Yes, you can click Details and provide
default certificate information such as issuer to communicate your expectations for how suppliers will answer
the question.
11. Click Done.

Related Information
How to add a question about integrated master data to a supplier

form or questionnaire
You can create a master data question that asks respondents to choose from a list of answers that is automatically
populated by values from integrated master data such as company codes, purchasing organizations, payment
terms, and incoterms.
Prerequisites
The feature to support questions about integrated master data (SM-3049) must be enabled in your site.
Integrated master data questions are only supported in internal supplier requests in the enhanced supplier request
(SM-15774) and internal registration questionnaires in the new supplier 360° profile (SM-14322). They are not
supported in external questionnaires.
To create or edit questions in questionnaires in internal supplier request and supplier registration project
templates, you must be a member of the Template Creator group. .
Your site must be configured for SAP material master data integration, and the material master data integration
must use the same business system ID for that integration must be the same business system ID that is specified
in the integration settings in SM Administration. You can only create an integrated master data question for a type
of master data that is loaded in your site. Currently supported types are company code, purchasing organization,
payment terms, and incoterms (the Purchase Org, Company Code, Payment Terms, and IncoTerms elements
in SAP ERP). For details, see To create or edit questions in questionnaires in internal supplier request andTopics
about managing SAP material master data integration in the Common data import and administration guide for SAP
Ariba Strategic Sourcing and Supplier Management solutions
 Note
Questions about integrated master data are currently not supported in integration landscapes that consolidate
master data from multiple ERP systems in SAP Master Data Governance (MDG).
Context
Integrated master data questions are useful because their list of possible answers is automatically populated with
the current values from the integrated master data. The answer dropdown menu shows the following master data
fields:

Type of master data Master data fields in answer dropdown menu
CompanyCode Description [UniqueName]
PurchaseOrg Name [UniqueName]
Incoterms Description [UniqueName]
 Note
SAP Ariba automatically shows descriptions in the lan
guage that matches a user's locale if available.
PaymentTerms Description [UniqueName]
Some types of master data reference other master data. For example, purchase organization master data includes
a CompanyCodeUniqueName field to associate specific company codes with specific purchasing organizations. For
these types of master data, you can set up either of the following types of answer filters:
● Filters on specific related values: you can filter the list of available answers for a master data question so that
it only includes answers associated with a specific related master data value. For example, you can filter a list of
purchasing organization answers so that it only shows those values that are associated with a specific
company code.
● Filters based on answers to related master data questions: you can filter the list of available answers for a
master data question based on the answer to a related master data question. For example, you can filter a list
of purchasing organization answers so that it only shows those values that are associated with the company
code that the respondent selected as the answer to a previous question.
Procedure
○ To add the question to the end of the form or questionnaire, choose Add Question at the bottom of
the content table.
○ Select the section to which you want to add the question and choose Add Question at the bottom of
the content table.
○ To add the question inside or after a section, click its name and choose Add Question .
2. If you selected a location for the new question, choose Add Inside to add the new question nested inside
3. On the Answer Type dropdown menu, choose Text (single line limited).
5. On the Acceptable Values dropdown menu, choose Master Data Value.
6. On the Type of master data for answer dropdown menu, choose a type of integrated master data.
7. (Optional) To set up answer filters, perform the following actions:
a. For Filter list of answers?, choose Yes.
b. On the Filter column dropdown menu, choose the column in the master data file by which you want to
filter the list of answers.
c. In the Filter values field, either enter a static value or reference the answer to another question in the
questionnaire using the format ($answer.{QuestionNumber}).

8. Specify any other necessary settings for the question, including field mappings.
9. Click Done.
Related Information
Topics about managing SAP material master data integration

Collecting supplier address information using Address or Extended

Address questions
Template survey documents in supplier management projects include Address and Extended Address question
answer types, which have special features that are designed specifically for collecting supplier address information.
By default, Address questions include basic address fields such as street, city, region, country, and postal code,
while Extended Address questions include a larger set of fields such as house number, building, district, and PO
box that are useful for international and non-residential addresses. See Default fields and field mappings in address
question answer types [page 270] for a complete list of fields and their database field mappings.
 Note
For supplier request questionnaires that include Extended Address questions, respondents must provide an
answer in the Region field in order to submit the questionnaire.
The following table describes the functionality supported for each answer type:
Functionality Address Extended Address
Supported in repeatable sections No Yes
Supports visibility and editability condi Yes No

tions based on underlying fields
Required for Dun & Bradstreet integra No Yes

tion
Your site's Extended Address configura-
tion must include specific fields for Dun
& Bradstreet integration [page 386].
Used in default duplicate check Yes No
Supports use of custom SAP region co No Yes

des [page 104]
Supports available field customizations, Yes Yes, with restrictions

which SAP Ariba must configure for you

Functionality Address Extended Address
Uses customizable master data to define Yes Yes

country-specific syntax validation for
postal codes [page 61]
SAP Ariba supports the following customizations for Extended Address:
● Field labels and help text, which appears when users click the information icon next to the field.
● Which fields are included in Extended Address questions.
● Whether or not individual fields are required.
● The order in which the fields appear from top to bottom.
● Whether a field appears in the initial Show Less view, or only after the user clicks a Show More link.
● The width of the field into which users add text. Note that this setting has no relation to the field's maximum
number of characters.
The following customizations are not supported for Extended Address:
● Adding new fields to Extended Address questions. You can include or exclude the default fields, but you cannot
add custom fields.
● Field length.
Related Information
Collecting supplier bank information using Bank Account questions
Template survey documents in supplier management projects include a Bank Account question answer type,
which has special features that are designed specifically for collecting supplier bank information.
 Note
Bank Account questions are designed for use in repeatable sections. You cannot add a Bank Account question
inside a repeatable section and another Bank Account question outside of a repeatable section in the same
questionnaire. Repeatable sections provide a mechanism for questionnaire respondents to remove bank
accounts from a questionnaire.
Bank Account questions include a set of predefined fields [page 278]. Using Bank Account questions in supplier
management questionnaires enables you to ask for these bank details automatically without having to create a
separate question for each detail field.
By default, respondents must provide an answer for Country, Bank ID, and either IBAN number or both Bank
key/ABA routing number and Account number. If the bank ID management feature (SM-9657) is enabled in your
site, the Bank ID field is read-only, and SAP Ariba automatically generates bank IDs for supplier using sequential

numerical values and, optionally, a country-specific prefix [page 52] defined by master data in your site. Once SAP
Ariba generates a bank ID for a bank account, its Country field also becomes read-only. The self-service
configuration parameter Define the length of supplier bank IDs (Application.SM.BankIdSize) defines the
maximum length of automatically-generated bank IDs.
 Note
Since the bank ID management feature (SM-9657) makes some fields in Bank Account questions read-only,
SAP Ariba recommends using repeatable sections for Bank Account questions. Repeatable sections allow
respondents to remove bank accounts from the questionnaire. Without a repeatable section, respondents are
not able to remove bank account information in read-only fields in Bank Account questions.
SAP Ariba validates Bank Account answers to ensure that there are values present in mandatory fields. By default,
there is no other validation (for example, for syntax, or to verify that the bank account exists) in SAP Ariba. If the
bank account syntax validation feature (SM-9656) is enabled in your site, SAP Ariba performs syntax validation on
some fields in Bank Account questions [page 253] using country-specific syntax definitions in master data in your
site, which you can customize.
When you add a Bank Account question to a questionnaire, keep in mind the following considerations:
● IBAN number and Account number are always masked so that only users in the Sensitive Data Access group
can see the full numbers. By default, Bank Account questions use a masking pattern of (.*).(4), which
masks all but the last 4 digits of every IBAN or account number. You can edit or remove this masking pattern,
but if you remove it entirely, the default masking pattern of (.*).(4) still applies.
● Bank Account questions use the field mapping vendor.bankInfos (for individual questions) or
vendor.bankInfos[$index] (for questions in repeatable sections). This mapping stores answers in the
corresponding bank fields [page 278] in the supplier database and synchronizes them to those fields in any
integrated ERP system.
Otherwise, you do not apply settings to any of the individual fields in the question. For example, you can apply a
visibility condition to the entire question, but you cannot show or hide individual fields.
In the supplier 360° profile, the answers to Bank Account questions automatically show on the ERP Profile tab on
the Overview tile.
 Note
After a supplier has been flagged as inactive in your site for 30 days, SAP Ariba automatically deletes all data in
bank, tax, and supplier contact database fields. If you reactivate the supplier after more than 30 days, you must
re-collect that information.
Related Information

Syntax validation for supplier bank account information
Syntax validation for supplier bank account information helps ensure that the supplier bank account information
you collect in supplier management questionnaires only includes values that are valid in an integrated ERP system.
If the bank account syntax validation feature (SM-9656) is enabled in your site, SAP Ariba automatically validates
the answers in the IBAN, bank account holder name, account number, and bank key or ABA routing number fields
in Bank Account questions in supplier requests (both internal and external) and registration, qualification, and
modular supplier management questionnaires using syntax master data. The feature also replaces the previous
Bank Account Type field with a Bank Control Key field in Bank Account questions and defines country-specific
bank control keys using master data. The functionality associated with this feature also requires the bank
component feature (SM-5590).
By default, bank account syntax validation uses default, country-specific master data definitions. You can use data
import tasks to customize bank account syntax validation in your site.
Field Default values Custom values
Bank Control Key Default bank control keys in Bank Ac Import country-specific bank control key
count questions [page 409] [page 54] master data to define custom
values for this field. After a respondent
selects the bank country, they choose
from the list of valid bank key values you
have defined for that country.
IBAN Number Default syntax for IBAN numbers in Bank Import country-specific IBAN syntax
Account questions [page 410] master data [page 56] for this field.
When a respondent submits a question
naire, an automatic validation check de
termines whether or not their answer is
valid for the selected bank country based
on this master data.
Account Holder Name, Account Default syntax validation for account Import country-specific syntax master
Number, and Bank Key/ABA Routing holder names, account numbers, and data [page 58] for these fields. When a
Number bank keys in Bank Account questions respondent submits a questionnaire, an
[page 414] automatic validation check determines
whether or not their answers are valid for
the selected bank country based on this
master data.
Respondents who provide invalid answers see error messages informing them of the required syntax for their
answers based on the syntax validations you have defined for them and are unable to submit questionnaires with
invalid answers for those fields.
Related Information

Default syntax validation for account holder names, account numbers, and bank keys in Bank Account questions
[page 414]
Collecting supplier tax information using Tax questions
Template survey documents in supplier management projects include a Tax question answer type, which has
special features that are designed specifically for collecting supplier tax information.
 Note
Tax questions are designed for use in repeatable sections. You cannot add a Tax question inside a repeatable
section and another Tax question outside of a repeatable section in the same questionnaire. Repeatable
sections provide a mechanism for questionnaire respondents to remove sets of tax details from a
questionnaire.
Tax questions automatically include an initial field for country. Once the respondent chooses the country, the
question displays the tax ID fields for that country, which are defined in your site via a metadata file import [page
50]. The CSV that defines your tax ID fields also allows you to specify which tax ID fields show for each country,
including validation patterns, sample values that display in validation error messages, and mappings to different tax
number fields in the vendor database. Using Tax questions in supplier management questionnaires enables you to
automatically ask for those country-specific tax IDs instead of having to create a separate conditional question for
each individual tax ID in each country in the questionnaire. All tax ID fields for the chosen country are required by
default. To allow respondents to submit a blank answer for a tax field, you can define a validation pattern of (^$) in
your tax metadata CSV. To both allow blank answers and ensure that if the supplier does answer the question, their
answer must have a valid format, you can place the (^$) pattern at the beginning or end of an existing validation
pattern, separated by a pipe character (|). For example, either of the following patterns allows the supplier to
submit either a blank answer or an answer with a length of 10: (^$)|(^\d{10}$) or (^\d{10}$)|(^$).
Tax questions currently do not support the collection of personal tax information as defined in your site's tax
metadata file. They only support the collection of organization-level tax information.
When you add a Tax question to a supplier management questionnaire, keep in mind the following considerations:
● By default, Tax questions use a masking pattern of (.*).(4), which masks all but the last 4 digits of every tax
ID. You can edit or remove this masking pattern.
● Tax questions use the field mapping vendor.taxExt (in single questions) or vendor.taxExt[$index] (in
questions in repeatable sections). This mapping stores answers in the supplier database fields that correspond
to different tax IDs as defined in the TaxCode column of your tax metadata CSV file.
Since validation patterns are defined in your tax metadata CSV file, you do not specify them when adding or editing
a Tax question.
Since suppliers can have multiple tax IDs in one or more countries, you can include Tax questions in repeatable
sections in external (supplier-facing) questionnaires. You can also include single Tax questions in internal
questionnaires, but the use of repeatable sections is not supported in internal questionnaires. The SAP Ariba
supplier database can store multiple tax IDs for each supplier, and all tax information in mapped Tax questions is
synchronized to integrated ERP systems.
In the supplier 360° profile, the answers to Tax questions automatically show on the ERP Profile tab on the
Overview tile.

In the SAP Ariba supplier database, the country, and tax ID fields in Tax questions are encrypted.
 Note
After a supplier has been flagged as inactive in your site for 30 days, SAP Ariba Supplier Management solutions
automatically delete all data in bank, tax, and supplier contact database fields. If you reactivate the supplier
after more than 30 days, you must re-collect that information.
Related Information
Turning questions into search filters using search terms

Adding search terms to a form, questionnaire, or internal survey question makes that question a filter in supplier
searches. Users can then filter their supplier searches based on answers to the question.
Template creators can define questions as search terms in survey and content documents in the following projects:
● Internal and external supplier requests

● Supplier registrations
● Supplier qualifications and disqualifications (SAP Ariba Supplier Lifecycle and Performance only)
● Preferred supplier management projects (SAP Ariba Supplier Lifecycle and Performance only)
● Modular supplier management questionnaires
In order to turn a question into a filter in supplier searches, you add text to the Search Term field on the Create
Question page. Before you start adding them to questions, it is important to understand how they are displayed on
the supplier search page.
The search term text you enter becomes the name of the search filter. Users can choose it from a list of available
filters to add it to their searches; once the filter is added to the search, it is displayed alongside search results on
the search page, together with permanent search filters such as Category, Region, and Registration status. If you
use List of Choices as the acceptable answer type, those choices become filter options that users can check.
For example, if you create a question with answer type Text (single line limited), choose List of Choices for the
acceptable answer, enter Search Term Text in the Search Term field, and add First choice, Second
choice, and Third choice as answer choices, the search filter looks like this on the search page:

When turning questions into search filters, keep the following considerations in mind:
● Search terms can be up to 50 characters long, but shorter terms display better on the search page.
● Make sure the search terms you use accurately and briefly describe how the filter will work and is unique. Users
performing supplier searches need to understand what the filter does when they add it to their searches based
on the search terms/filter name. Keep in mind that all search filters appear in a single list of available filters
with no indication of which project or survey they came from; for example, there is no way for users to tell if a
search filter came from a question in the supplier request, the supplier questionnaire in a registration project,
or an internal survey in a registration project.
● There is no limit to the number of questions you can turn into search filters. However, using search terms for
only a limited number of strategic questions keeps the list of search filters that users can add to a search
manageable.
● The search filters for text questions consist of a field in which the user enters search terms; the search returns
the suppliers whose answers include that text. This type of filtering can be overly broad. Text questions that use
a list of choices as acceptable answers make more effective search filters.
● You can provide translations for search terms in all of the languages enabled in your site by clicking the
Translations link to the right of the Search term field. An individual user's locale setting in their profile
automatically determines which translation they see. If you do not provide translations, users in all locales see
the search term in the original language in which you created it (the base language). You must be a member of
the Translator group to provide translations.
The following table describes the question answer types that support search terms and the way the resulting filters
work:t
This answer type... With this acceptable answer setting... Creates this search filter...
● Text (single line limited) None A field into which users enter text. The
● Text (single line) search only include suppliers whose an
swers include that text.
List of Choices Options that allow users to filter the

search by checking one or more of the
choices.
Text (multiple lines) n/a A field into which users enter text. The
search only include suppliers whose an
swers include that text.
● Whole Number None or Limited Range From and To fields where users can enter
● Decimal a range of numbers by which to filter the
● Money search.

choices.
Date None or Limited Range From and To fields with calendar icons
where users choose date range by which
to filter the search.

This answer type... With this acceptable answer setting... Creates this search filter...

choices.
Yes/No n/a Yes and No options; users can choose

one or the other to filter the search.
● Percentage None A field into which users enter a number.

● Quantity
Limited Range From and To fields with calendar icons
where users choose date range by which
to filter the search.

choices.
Turning questions of type Attachment, Certificate, Address, Extended Address, and Supplier into search filters is
not supported at this time.
You also cannot turn questions of type Commodity, Region, or Department into search filters, but there is no
reason to do so since search page includes permanent search filters for commodity category and region and (in
sites with the business unit supplier management matrix enhancement feature enabled) department.
Although you can turn questions of type Text (single line limited) with either no acceptable answers or a list of
choices into search filters, you cannot do so for Text (single line limited) questions with acceptable answers set to
use master data values at this time.
Related Information
Using code delimiters to associate descriptive questionnaire

answers with ERP or other codes
Code delimiters provide a mechanism for providing descriptive answers to questions but saving those answers as
codes, so that users who might not be familiar with various internal codes can easily provide those required codes
as answers.
Code delimiters are particularly useful in sites integrated with an ERP system, which require valid code values for
some fields. Users who answer supplier management don’t have to have all of your ERP system’s codes
memorized; they can select a descriptive answer, and the associated code is automatically stored in the mapped
vendor database field and synchronized with the integrated ERP system.

You use the following two question settings to create associations between codes and answers in supplier
management questionnaires:
● The Code Delimiters field in questions of type Text (single line) and Text (single line limited), where you
define the characters that enclose codes in question answers; for example, () or [].
● List of choices answers that use the code delimiters. Once you have defined your code delimiters, you create a
list of choices as the acceptable answers to the question. For each choice, you include both a descriptive
answer and the associated code, enclosed by the delimiters.
You then map the question to the appropriate vendor database field. Only the portion of the answer enclosed by
code delimiters is stored in the mapped database field and synchronized with the ERP, so you can provide whatever
description you like while satisfying the ERP system’s requirement for a valid code in that field.
For example, if you want to associate codes with descriptive incoterms for purchasing organizations, you can create
a question about them in the internal registration questionnaire. For that question, you can define () as the code
delimiters and map the question [page 260] to vendor.purchasingOrg.incotermsClassificationCode. You
can then create a list of choices that includes FOB Shipping Point (M1) and FOB Destination (Z1).
In this example, when a user edits the internal registration questionnaire and selects FOB Shipping Point
(M1), the M1 code is stored in the mapped vendor database field and synchronized with the ERP.
Related Information

Automatically validating question answers
Adding a validation pattern to a question defines the format of the answer. Respondents who provide answers that
don't use the format you specify see an error message and are unable to submit the form or questionnaire until
they correct the problem.
For example, you can make sure that an answer includes only numbers, or only uppercase letters; more precisely,
you can make sure that answers include exactly 9 numbers, or two uppercase letters followed by a dash (-)
followed by four numbers. Validation patterns help to ensure the quality of your supplier data by making it much
more likely that you get the correct answer the first time the respondent submits the form or questionnaire, and
that you do not have to rely on individual approvers noticing incorrect or incomplete answers and requesting
additional information during the approval process.
You define the validation pattern using a regular expression, which is a sequence of characters that defines the
pattern. Regular expressions use standard text strings and syntax to define patterns to which matching text must
conform. There are a number of websites on the Internet that can help you understand, formulate, and test regular
expressions. You enter the regular expression in the Validation Pattern field on the Add Question page. This field is
only available for the answer types Text (single line) and Text (single line limited).
You can provide a custom error message in the related Validation Pattern Error Message field. If you do not
provide a custom error message, a generic error message displaying the expected format is used instead. You can
also provide translations for these error messages in all of the languages enabled in your site by clicking the

Translations link to the right of the Validation Pattern Error Message field. An individual user's locale setting in
their profile automatically determines which translation they see. If you do not provide translations, users in all
locales see the error message in the original language in which you created it (the base language). You must be a
member of the Translator group to provide translations.
The following example regular expressions define simple validation patterns:
● ^[0-9]*$: the answer must use only numbers

● ^[A-Z]*$: the answer must use only upper-case letters
● ^[a-z]*$: the answer must use only lower-case letters
● ^[a-zA-Z0-9]*$: the answer can use any number or upper- or lower-case letter
However, regular expressions can also define more complex validation patterns. For example, an answer that must
use seven numbers in the format XXX-XXXX, would use the regular expression ^[0-9]{3}-[0-9]{4}$ as the
validation pattern.
Example
In a supplier registration questionnaire, you might ask for the employer identification of suppliers in the United
States. US employer identification numbers are 9-digit codes in the format XX-XXXXXXX. To specify this format,
you enter ^\d{2}\-\d{7}$ in the Validation Pattern field. You can also add something like Your employer
identification number must be in the format XX-XXXXXXX in the Validation Pattern Error Message
field.
Topics about field mappings for questions in supplier management

questionnaires
Supplier field mappings with additional requirements [page 261]
Common supplier database field names for mapping [page 262]
Vendor database array classes and their lookup key fields [page 279]
Ariba Network supplier profile field mappings [page 281]
How Ariba Network for Suppliers profile information synchronizes to supplier forms, questionnaires, and
internal surveys [page 290]
Mapping supplier name and extended address questions to international versions in an integrated ERP system
[page 292]
Field encryption in the vendor database [page 293]

Mapping questions to supplier database fields
Mapping specific questions in template forms and questionnaires to specific supplier database fields ensures that
the values entered for that content are written to those specific supplier database 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 a value associated with the question. However, if you
map the question to the vendor.vendorInfo.name1 field, the answer is stored in the database as the supplier's
name.
When supplier is initially synchronized with the integrated ERP system, 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 SAP Ariba.
Most questions do not need to be mapped. However, any question answer that you want to synchronize with the
ERP system must be mapped to a supplier database field. You can also map name and extended address questions
to international versions [page 292].
In some cases, that mapping is required; for example, a supplier request form must include mapped questions for
the supplier's name and the supplier contact's name and email address. If you site is integrated with Dun &
Bradstreet, there are also specific mapping requirements [page 394].
The questions you map to vendor database fields are automatically prepopulated with any current data from the
database; respondents can update the data by editing the prepopulated answers. This behavior does not occur in
the supplier request, since the supplier is not created in the database yet, but does occur in other supplier
management forms, questionnaires, and internal surveys, including supplier-facing registration and (in SAP Ariba
Supplier Lifecycle and Performance solutions only) qualification questionnaires: suppliers filling out a questionnaire
on Ariba Network for Suppliers see prepopulated answers to mapped questions if there is data available for them.
If you map a question to a custom field in the vendor.businessPartnerGenericCustomField or

vendor.supplierGenericCustomField class, that field is automatically created in the SAP Ariba supplier
database. Replicating a supplier from an integrated SAP ERP system with data in custom fields in those classes
class also creates those fields in the SAP Ariba supplier database.
 Note
SAP Ariba Supplier Management solutions do support storing multiple values in the same database field for
fields in array classes [page 279]. However, those mappings typically require special syntax. For example,
repeatable sections [page 232] allow you to ask for multiple sets of answers to the same questions; questions
in repeatable section require a special mapping syntax [page 261]. You can also use a special syntax to map
question values to other questions [page 170] to enable users to set and maintain associated sets of ERP profile
data with those questions.
Related Information


Mapping supplier name and extended address questions to international versions in an integrated ERP system
[page 292]
Supplier field mappings with additional requirements
When you create a questionnaire with mapped questions that have additional requirements, you must include
questions mapped to corresponding supplier database fields. Otherwise, the response data of the initial mapped
question is not included in the XML integration message when synchronizing to your ERP system.
Questions that are mapped to the following initial field mappings require another question mapped to the
corresponding field mapping in order to synchronize to your ERP system.
Initial supplier database field Required corresponding field mapping
vendor.companyCode.withholdingTaxApis.with vendor.companyCode.withholdingTaxApis.curr
holdingTaxExemptionRateAmnt encyCode
Related Information

Mapping questions in repeatable sections to supplier database fields
You can map questions in repeatable sections to supplier database fields in array classes, which support storing
multiple values for the field. Mappings for repeatable sections use a special syntax that defines the section as an
index for the questions it contains.
The structure of nested repeatable subsections should reflect the structure of the database fields to which you
want to map them. Inside a top-level repeatable section for the class, nest repeatable subsections for the
subclasses and add questions to about subclass fields in those nested subsections.
The syntax for mapping repeatable sections and their nested repeatable subsections is as follows:
Repeatable section position Syntax
Top-level repeatable section vendor.fieldClass[$index].fieldName
Repeatable subsection nested within another repeatable sec vendor.fieldClass[$index].subclassName[$in

tion dex].fieldName
Mapping questions in repeatable sections to fields which store single values only are not supported, with the
exception of the vendor.certificate field, which you use to map Certificate questions in repeatable sections.
You can use the [$index] syntax to map questions in repeatable sections to any vendor database field in the
following array classes:

● vendor.bankInfos
● vendor.companyCode
● vendor.contact
● vendor.industrySector
● vendor.purchasingOrg
● vendor.roleExt
● vendor.subRange
● vendor.taxExt
● vendor.taxGrouping
● vendor.text
● vendor.vendorExtIdentification
● vendor.vendorPCardIssuerApis
 Restriction
● While vendor.addressExt is an array class, SAP ERP, SAP S/4HANA, and SAP MDG systems only
support one explicit address per supplier record and use partner functions to store multiple addresses for
divisions within a supplier such as locations. SAP Ariba Supplier Management solutions do not currently
support partner functions, and synchronizing repeatable sections mapped to vendor.addressExt to
SAP ERP causes integration errors because SAP ERP does not recognize multiple address values for the
main vendor record.
● Supplier contact information is not synchronized to the integrated system.
● Data in nested repeatable sections is not synchronized to the integrated system.
Users in the SM ERP Administrator and SM Ops Administrator groups can download a complete list of available
supplier database field names by clicking Manage SM Administrator on the dashboard, navigating to the
Default field values area, and downloading the Default_properties_sample.csv file.
Related Information
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.
Users in the SM ERP Admin 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.
This list also includes field mappings that are used internally within projects to map question answers to project
data such as commodity, region, department, and various approval fields. Those fields nore not synchronized with
the integrated ERP system.

● Supplier name and ID fields [page 263]
● Supplier contact fields [page 265]
● Supplier address fields [page 266]
● Supplier tax fields [page 266]
● Supplier bank account fields [page 267]
● Project fields [page 268]
● SAP ERP keyword fields [page 269]
Supplier name and ID fields
The information in these fields is used to determine possible matches to existing suppliers in the database.
Field Name Description
vendor.vendorInfo.name1 The name of the supplier.
 Note
Either this field or vendor.vendorInfo.fullName
is required in supplier request forms.
vendor.vendorInfo.name2 An alternate name for the supplier, or the name of a supplier's

parent company.
vendor.vendorInfo.name3 A second alternate name for the supplier, or the name of a sup
plier's parent company.
vendor.vendorInfo.name4 A third alternate name for the supplier, or the name of a suppli
er's parent company.
vendor.vendorInfo.fullName An alternate field for storing supplier names of up to 140 char

acters in sites that use the optional supplier full name feature
[page 107].
vendor.vendorInfo.erpVendorId The ID of the supplier in your organization's ERP vendor mas

ter.
A supplier created in SAP Ariba will not have an ERP vendor ID

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

vendor.vendorInfo.dunsId The supplier's Dun & Bradstreet DUNS number.
 Note
This mapping is useful in conjunction with the mapping to
the related Ariba Network profile field [page 281] for syn
chronizing the supplier's DUNS number from their Ariba
Network profile to a questionnaire answer; however, the
data in this field does not synchronize to an integrated
ERP system.
vendor.vendorInfo.s4OrgSystemId A unique organization ID that SAP Ariba assigns to each sup

plier. This ID is different from the supplier SM ID, which SAP
Ariba Supplier Management solutions assign to each supplier
and show in the supplier 360° profile. In suppliers migrated
from supplier organizations, an integrated SAP ERP or SAP S/
4HANA system might use the organization ID to identify the
supplier, rather than the SM ID. If you create a question with
this mapping in the supplier request or a supplier registration
questionnaire, it is automatically populated with the supplier's
organization ID, and that ID then synchronizes with the ERP
system along with other profile information.
vendor.certificate Any certificates that the supplier provides, such as diversity or

green certifications. Map questions with the Certificate an
swer type to this field. Use this mapping for both standalone
Certificate questions and Certificate questions in repeatable
sections.
 Note
The following fields are important ID fields for suppliers. Once a value is added to any of these fields in the
database, if you add a question mapped to it to a questionnaire and a respondent removes the value, the value
is removed in the questionnaire but not in the database:
● vendor.vendorInfo.erpVendorId
● vendor.vendorInfo.anId
● vendor.vendorInfo.dunsId
● vendor.vendorInfo.sourceSystem
● vendor.vendorInfo.s4OrgSystemId

Supplier contact fields
 Note
Supplier contact field mappings are only supported in supplier requests. After the request creates the supplier
in the SAP Ariba database, you can manage a supplier's contacts either manually in the 360° profile or via data
import.
Field name Description
contact.firstName 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.
contact.middleName The middle name of the supplier contact, the person to whom
the registration questionnaire invitation is sent by default.
contact.lastName The last name of the supplier contact, the person to whom the
registration questionnaire invitation is sent by default.
 Note
contact.email The email address of the supplier contact.
 Note
contact.telephone The phone number of the supplier contact.
 Note
This field is recommended in supplier request forms.
contact.locale 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

contact.timeZoneID The geographical time zone of the supplier contact.
 Note
Supplier address fields
vendor.address.line1 The first line of the supplier's street address.
vendor.address.line2 The second line of the supplier's street address.
vendor.address.line3 The third line of the supplier's street address.
vendor.address.city The city of the supplier's street address.
vendor.address.state The state or province of the supplier's street address.
vendor.address.postalCode The postal code of the supplier's street address..
vendor.address.countryCode The country of the supplier's street address.
vendor.address.languageCode The ISO language code for the language of the supplier's ad
dress.
vendor.address.url The supplier's website URL.
 Note
This mapping is useful in conjunction with the mapping to
the related Ariba Network profile field [page 281] for syn
chronizing the supplier's website URL from their Ariba
Network profile to a questionnaire answer; however, the
data in this field does not synchronize to an integrated
SAP ERP.
Supplier tax fields

vendor.taxInfo.taxAuthorityPartyID An identifier for the tax authority to which the supplier reports.
vendor.taxInfo.taxNumber1 A set of unique identifiers for the taxes to which the supplier is
subject, as defined by the tax authority.
vendor.taxInfo.taxNumber2
vendor.taxInfo.taxNumberType The tax number type.
vendor.taxInfo.taxSplitIndicator An indicator for whether or not the tax is split.
vendor.taxInfo.taxType The type of the tax, such as withholding.
vendor.taxInfo.vatRegistrationNumber The VAT number assigned to the supplier.
vendor.taxInfo.taxGroupCode The supplier tax group code.
vendor.taxInfo.taxBasePercentageCode An identifier for the base percentage subject to tax.
vendor.taxInfo.equalizationTaxRelevanceInd An indicator for whether or not the supplier is subject to sales

icator tax.
vendor.taxInfo.valueAddedTaxRelevanceIndic An indicator for whether or not the supplier is subject to VAT.

ator
Supplier bank account fields
vendor.bankInfos.accountName A name for the supplier's bank account.
vendor.bankInfos.accountNumber The supplier's bank account number.
vendor.bankInfos.bankDetails 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.
vendor.bankInfos.bankType The type of the supplier bank account; for example, checking.
vendor.bankInfos.controlKey The control key for the bank.

vendor.bankInfos.country The country in which the supplier's bank operates.
vendor.bankInfos.key A unique identified, which is usually assigned to the bank by

the country in which it operates.
vendor.bankInfos.validFrom The date from which the supplier bank information is valid.
vendor.bankInfos.validTo The date to which the supplier bank information is valid.
Project fields
These fields are for SAP Ariba use only and are not synchronized with an ERP system.
matrix.Categories The commodities associated with the supplier.
Map questions with answer type Commodity to this field.
matrix.Regions The regions associated with the supplier.
Map questions with answer type Region to this field.
matrix.Departments The buyer organization departments or business units associ

ated with the supplier.
Map questions with answer type Department to this field.
project.Level 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. This field mapping is only used in preferred
supplier management projects.
project.ExpirationDate The date on which the supplier qualification expires. This field
mapping is only used in qualificatoin projects.
project.RequalificationEligibilityDate The date after which an expired qualification can be requali

fied. This field mapping is only used in qualification projects.
project.DisqualificationDate The date on which the supplier is disqualified. This field map
ping is only used in disqualification projects.
project.DisqualificationUntilDate The date until which the supplier is in Restricted status, after
which disqualification is automatic. This field mapping is only
used in disqualification projects.

project.RiskScore A manually entered risk score.
project.LegalApprovalLevel Used in hidden questions that are designed to insert the legal
department into an approval flow based on the answer to an
other question, using a condition based on the Legal Approval
Level project field.
project.FinanceApprovalLevel Used in hidden questions that are designed to insert the fi-
nance department into an approval flow based on the answer
to another question, using a condition based on the Finance
Approval Level project field.
project.QualityApprovalLevel Used in hidden questions that are designed to insert a quality

officer into an approval flow based on the answer to another
question, using a condition based on the Quality Approval
Level project field.
project.SustainabilityApprovalLevel Used in hidden questions that are designed to insert a sustain

ability officer into an approval flow based on the answer to an
other question, using a condition based on the Sustainability
project.PurchasingApprovalLevel Used in hidden questions that are designed to insert procure

ment managers into an approval flow based on the answer to
another question, using a condition based on the Purchasing
project.LOBApprovalLevel Used in hidden questions that are designed to insert a line of

business into an approval flow based on the answer to another
question, using a condition based on the Line of Business
SAP ERP keyword fields
If your solution is integrated with SAP ERP, you can map two questions to the two supplier keyword fields in SAP
ERP. SAP Ariba recommends that you create the questions mapped to these fields in an internal survey in the
registration project, so that internal users can always edit the keyword values.
vendor.vendorInfoExt.keyWordsText The first SAP ERP supplier keyword field.
vendor.vendorInfoExt.additionalKeyWordsTex The second SAP ERP supplier keyword field.

t

Related Information
Default fields and field mappings in address question answer types
Address fields
For the Address question answer type, you use the vendor.address field mapping to map the underlying fields to
vendor database fields all at once using one question. The corresponding Ariba Network mapping is
network.legal.address. You can also map individual text questions to these vendor database fields. Unless
otherwise noted, all fields are text fields and transmit string data to any integrated ERP system.
 Note
Customization of address questions is supported. The address fields you see in Address questions might be
different from the default fields listed here.
Vendor database field map In Address questions by de Maximum field length (in
Underlying field ping fault? characters)
Street vendor.address.line1 Yes 255
City vendor.address.city Yes 40
State/Province/Region vendor.address.state Yes 6
Postal Code vendor.address.posta Yes 10

lCode
Country vendor.address.count Yes 3

ryCode
(users select the country from
a chooser, and their choice is
transmitted to any integrated
ERP system as a country code
of 2-3 characters)
Street 2 vendor.address.line2 No 255
Street 3 vendor.address.line3 No 255

Extended Address fields
For the Extended Address question answer type, you use the vendor.addressExt.postalAddress field
mapping in order to map the underlying fields to vendor database fields all at once using one question. The
corresponding Ariba Network mapping is network.legal.addressExt.postal. You can also map individual
text questions to these vendor database fields. If you plan to collect extended address information in different
languages for storage in international tables in an integrated ERP system, you can include international version
identifiers [page 292] in extended address mappings. Unless otherwise noted, all fields are text fields and transmit
string data to any integrated ERP system.
 Note
Some types of customization [page 250] of extended address questions are supported. The fields you see in
Extended Address questions, and their inclusion in the Show Less or Show More might be different from the
defaults listed here.
Vendor database field map In Extended Address ques Maximum field length (in
Underlying field ping tions by default? characters)
Building/Room/Floor vendor.addressExt.po Yes (Show More view) 10/20/10

(combo field) stalAddress.building
ID /
vendor.addressExt.po
stalAddress.roomID /
stalAddress.floorID
c/o vendor.addressExt.po Yes (Show More view) 40

stalAddress.careOfNa
me
Street 2 vendor.addressExt.po Yes (Show More view) 40

stalAddress.streetPr
efixName

stalAddress.addition
alStreetPrefixName
House No./Street/Suppl. vendor.addressExt.po Yes (Show Less view) 10/60/10

(combo field) stalAddress.houseID /
stalAddress.streetNa
me /
alHouseID


stalAddress.streetSu
ffixName

alStreetSuffixName
District vendor.addressExt.po Yes (Show More view) 40

stalAddress.district
Name
Different City vendor.addressExt.po Yes (Show More view) 40

alCityName
Postal Code/City (combo vendor.addressExt.po Yes (Show Less view) 10/40

field) stalAddress.streetPo
stalCode /
stalAddress.cityName
Country/Region (combo vendor.addressExt.po Yes (Show Less view) 3/3

field) stalAddress.countryC
(users select the country and (users select the country and
ode / region from choosers, and region from choosers, and
vendor.addressExt.po their choices are transmitted their choices are transmitted
stalAddress.regionCo to any integrated ERP system to any integrated ERP system
de as a country code and region as a country code and region
code of 2-3 characters) code of 2-3 characters)
If your integrated ERP system If your integrated ERP system

uses custom region codes, uses custom region codes,
you can import your SAP re you can import your SAP re
gion codes [page 104] for use gion codes [page 104] for use
in extended address Region in extended address Region
fields. fields.
Time Zone (single field) vendor.addressExt.po Yes (Show More view) 6

stalAddress.timeZone
Code
Tax Jurisdiction (single field) vendor.addressExt.po Yes (Show More view) 15

stalAddress.taxJuris
dictionCode

Transportation Zone vendor.addressExt.po Yes (Show More view) 20

stalAddress.transpor
tationZoneID
Reg. Struct. Grp. vendor.addressExt.po Yes (Show More view) 8

stalAddress.regional
StructureElementGrou
pCode
Undeliverable vendor.addressExt.po Yes (Show More view) 4

stalAddress.streetAd
dressMailNonDelivery
ReasonCode
PO Box (single field) vendor.addressExt.po Yes (Show More view) 10

stalAddress.poBoxID
PO Box w/o No. (single field) vendor.addressExt.po Yes (Show More view) n/a (Boolean value)
stalAddress.poBoxIDV
isibleIndicator
PO Box Delivery Service Type vendor.addressExt.po Yes (Show More view) 4

(single field) stalAddress.poBoxDel
iveryServiceTypeCode
PO Box Delivery Service No. vendor.addressExt.po Yes (Show More view) 10

(single field) stalAddress.poBoxDel
iveryServiceID
PO Box Lobby vendor.addressExt.po Yes (Show More view) 40

stalAddress.poBoxLob
byName
PO Box Postal Code (single vendor.addressExt.po Yes (Show More view) 10

field) stalAddress.poBoxPos
talCode
PO Box Other City (single vendor.addressExt.po Yes (Show More view) 40

field) stalAddress.poBoxDev
iatingCityName

PO Box Other Country (single vendor.addressExt.po Yes (Show More view) 3

iatingCountryCode a chooser, and their choice is
of 2-3 characters)
PO Box Other Region (single vendor.addressExt.po Yes (Show More view) 3

(users select the region from a
iatingRegionCode chooser, and their choice is
ERP system as a region code
of 2-3 characters)
If your integrated ERP system

uses custom region codes,
you can import your SAP re
gion codes [page 104] for use
in extended address Region
fields.
Company Postal Code vendor.addressExt.po Yes (Show More view) 10

stalAddress.companyP
ostalCode
PO Box Undeliverable vendor.addressExt.po Yes (Show More view) 4

stalAddress.poBoxAdd
ressMainNonDeliveryR
easonCode
PO Box Other Reg. Struct. vendor.addressExt.po No 12

City stalAddress.poBoxDev
iatingRegionalStruct
ureCityCode
Reg. Struct. City vendor.addressExt.re No 12

gionalStructureCityC
ode
Reg. Struct. City Code vendor.addressExt.po No 12

alRegionalStructureC
ityCode

Reg. Struct. Consistency vendor.addressExt.po No 1

StructureAddressCons
istencyStatusCode
Reg. Struct. District vendor.addressExt.po No 8

StructureDistrictCod
e
Reg. Struct. Street vendor.addressExt.po No 12

StructureStreetCode
Address Representation vendor.addressExt.po No 4

Code stalAddress.addressR
epresentationCode
House No. (single field) vendor.addressExt.po No 10

stalAddress.houseID
Suppl. (single field) vendor.addressExt.po No 10

alHouseID
Street (single field) vendor.addressExt.po No 60

stalAddress.streetNa
me
City (single field) vendor.addressExt.po No 40

stalAddress.cityName
Postal Code (single field) vendor.addressExt.po No 10

stalAddress.streetPo
stalCode

Region (single field) vendor.addressExt.po No 3

stalAddress.regionCo
(users select the region from a
de chooser, and their choice is
ERP system as a region code
of 2-3 characters)

fields.
Country (single field) vendor.addressExt.po No 3

stalAddress.countryC
ode a chooser, and their choice is
of 2-3 characters)
Room (single field) vendor.addressExt.po No 20

stalAddress.roomID
Floor (single field) vendor.addressExt.po No 10

stalAddress.floorID
Building (single field) vendor.addressExt.po No 10

stalAddress.building
ID
PO Box Other Country/PO vendor.addressExt.po No 3/3

Box Other Region stalAddress.poBoxDev
(users select the country and
iatingCountryCode / region from a chooser, and
vendor.addressExt.po their choice is transmitted to
stalAddress.poBoxDev any integrated ERP system as
iatingRegionCode region and country codes of
2-3 characters)

fields.

PO Box Delivery Service vendor.addressExt.po No 4/10

Type/PO Box Delivery stalAddress.poBoxDel
Service No. (combo field) iveryServiceTypeCode
/
stalAddress.poBoxDel
iveryServiceID
PO Box/ PO Box w/o No. vendor.addressExt.po No 10/N/A (Boolean value)

(combo field) stalAddress.poBoxID /
stalAddress.poBoxIDV
isibleIndicator
PO Box Postal Code/PO Box vendor.addressExt.po No 10/40

Other City (combo field) stalAddress.poBoxPos
talCode /
stalAddress.poBoxDev
iatingCityName
Time Zone/Tax Jurisdiction vendor.addressExt.po No 6/15

(combo field) stalAddress.timeZone
Code /
stalAddress.taxJuris
dictionCode
Related Information

How to import custom SAP region codes for supplier extended addresses [page 104]
Collecting supplier address information using Address or Extended Address questions [page 250]

Predefined fields and field mappings in Bank Account questions
Questions with the Bank Account answer type include a set of predefined fields. You cannot edit these individual
fields.
Mapping a Bank Account question to vendor.bankInfos (for a single question) or

vendor.bankInfos[$index] (for a question in a repeatable section) automatically creates the following
underlying mappings for the bank detail fields in the question:
Field Notes Underlying mapping
Bank Type Users can choose No Choice, Domestic, vendor.bankInfos.bankType

or Foreign.
Bank Id This field is mandatory. vendor.bankInfos.id
This field is encrypted in the SAP Ariba

supplier database.
Country Users select a country from a chooser. vendor.bankInfos.country
This field is mandatory.
Name vendor.bankInfos.name
Bank Branch
Street
City
State/Province/Region
Postal Code
Account Holder Name vendor.bankInfos.accountNam

e

supplier database.
Bank Key/ABA Routing Number Either IBAN Number or a combination of vendor.bankInfos.BankIntern

Bank Key/ABA Routing Number and alId,
Account Number is mandatory. vendor.bankInfos.bankStanda
rdID, and
vendor.bankInfos.bankDirect
oryReferenceBankStandardID.
These fields are encrypted in the SAP

Ariba supplier database.

Field Notes Underlying mapping
Account Number Either IBAN Number or a combination of vendor.bankInfos.accountNum

Bank Key/ABA Routing Number and ber
Account Number is mandatory.
supplier database.
IBAN Number Either IBAN Number or a combination of vendor.bankInfos.bankAccoun

Bank Key/ABA Routing Number and tStandardID
Account Number is mandatory.
supplier database.
SWIFT Code vendor.bankInfos.bankAccoun

tExternalID

supplier database.
Bank Account Type Users choose No Choice, Savings,

Checking, or Investment
Related Information
Vendor database array classes and their lookup key fields
Array classes in the vendor database can store multiple values per supplier. You can use these array classes and
their lookup key fields to set default values and map question values to other questions.
Field class Lookup key field
vendor.bankInfos vendor.bankInfos.accountNumber
vendor.companyCode vendor.companyCode.companyCode
vendor.industrySector vendor.industrySector.industryClassificati
onSystemCode
vendor.purchasingOrg vendor.purchasingOrg.purchasingOrganisatio
nID
vendor.roleExt vendor.roleExt.roleCode

vendor.subRange vendor.subRange.vendorSubrangeCode
vendor.taxExt vendor.taxExt.vendor.taxExt.taxIdentificat
ionNumberTypeCode
vendor.text vendor.text.textTypeCode
vendor.vendorExtIdentification vendor.vendorExtIdentification.partyIdenti
fierTypeCode
vendor.vendorPCardIssuerAPIs vendor.vendorPCardIssuerAPIs.paymentCardIs
suerPartyInternalID
Mapping questions to Ariba Network supplier profile fields
Mapping questions to Ariba Network supplier profile fields established a connection so that when a supplier
updates their profile on Ariba Network for Suppliers, the update is pushed to their profile in your site.
If a supplier has a connected Ariba Network for Suppliers account, their Ariba Network for Suppliers profile
information automatically displays on the Public Profile tab in their supplier 360° profile. However, data from an
Ariba Network for Suppliers profile field is not automatically linked to the corresponding field the vendor database.
You must create the link by mapping a supplier management form or questionnaire question to both the Ariba
Network for Suppliers field and a vendor database field.
You can add both mappings, separated by commas to map a question to both an Ariba Network supplier profile
field and a vendor database field to ensure that updates to a supplier's Ariba Network for Suppliers profile are also
updated in the vendor database.
 Note
If you map a question in an internal or external registration questionnaire to both an Ariba Network supplier
profile field and a vendor database field, after a supplier is registered, the supplier registration project treats
any update to the Ariba Network profile field as an update to the questionnaire that contains the mapped
question. The profile field update restarts any approval tasks for updates to the questionnaire, as well as any
registration update phases associated with those approval tasks.
A template creator creates a question in the supplier registration that asks for the supplier's name and adds the
following mappings to the question Supplier field mapping field:
vendor.vendorInfo.name,network.corporate.legalName
This mapping connects the question to the designated name field in the vendor database and to the Legal
Name field in the supplier's Ariba Network for Suppliers profile.
With this mapping, when a user creates a supplier registration and enters Company A for the name question,
after the supplier registration is approved, the supplier is created in the database with Company A in the name
field and that process connects the supplier record in SAP Ariba Supplier Management solutions to the
supplier's Ariba Network for Suppliers account, where the Legal Name value is actually Company A, Inc..

The vendor database name field is then automatically updated with that value as well as with any subsequent
changes that the supplier makes to the Legal Name field in their Ariba Network for Suppliers profile. Those
updates in turn show wherever in the supplier profile the database field displays.
Note that the Ariba Network supplier profile includes both Name and Legal Name fields. In this example, the
template creator has chosen to use the more precise Legal Name value for the supplier's name in SAP Ariba
Note that if you do not have registration update approvals configured, the update is automatically pushed to
your site. Updates that suppliers make to the registration questionnaire itself trigger the registration update
process, and if a supplier enters one value in a profile field and a different value for a question mapped to the
same profile field, the value in the profile field overwrites the value in the question.
Ariba Network supplier profile field mappings
All Ariba Network supplier profile fields are text strings unless otherwise noted, and should be mapped to questions
of answer type Text (single line) or Text (single line limited).
Supplier fields
Supplier profile field Ariba Network field mapping
Company Name network.org.name
Other names, if any (two fields) network.org.alias1 and network.org.alias2
NetworkId network.org.anId
Short Description network.org.description
 Note
This description has a maximum length of 100 characters.
Website network.legal.address.url
Public Profile network.org.anLogoURL
Address Name network.legal.address.addressName
Address ID network.legal.address.addressType
Address 1 network.legal.address.line1

City network.legal.address.city
Municipality / Comuna network.legal.address.district
State network.legal.address.state
Province network.legal.address.province
Region network.legal.address.region
Country network.legal.address.countryCode
Postal Code network.legal.address.postalCode
PO Box network.legal.address.poBox
Address network.legal.address
 Note
This field mapping is the Ariba Network equivalent of the
vendor.address vendor mapping for Address type
questions. For more information about the corresponding
vendor database field, see Default fields and field map
pings in address question answer types [page 270].
Extended Address network.legal.addressExt.postal
 Note
This field mapping is the Ariba Network equivalent of the
vendor.addressExt.postalAddress vendor
mapping for Extended Address type questions. For more
information about the corresponding vendor database
field, see Default fields and field mappings in address
question answer types [page 270].
Product and Service Categories network.org.categories
 Note
Suppliers specify one or more UNSPSC commodity cate
gories in this field. Map to this field in a question that ei
ther has the Commodity answer type or uses commodity
master data for acceptable answers.

Ship-to or Service Locations network.org.serviceLocations
 Note
Suppliers specify one or more regions in this field. Map to
this field in a question that either has the Region answer
type or uses region master data for acceptable answers.
Industries network.org.industries
 Note
Suppliers choose one or more values from a pre-defined
list for this field.
Year Founded network.corporate.yearFounded
Number of Employees network.corporate.numberOfEmployees
Annual Revenue network.corporate.annualRevenueMax,

network.corporate.annualRevenueMaxCurrency,
network.corporate.annualRevenueMin,
network.corporate.annualRevenueMinCurrency
 Note
Suppliers choose from a list of number ranges for this
field. Those number ranges consist of four separate pieces
of data: minimum number, minimum number currency,
maximum number, and maximum number currency; for
example, $100K to $1M USD. You must use multiple,
comma separated mappings in a question to capture this
data, but you do not have to use all of the mappings; for
example, to pull only the maximum annual revenue data,
map the question to
"network.corporate.annualRevenueMax,
network.corporate.annualRevenueMaxCurre
ncy".
Stock Symbol network.corporate.stockSymbol

Type of Organization network.corporate.businessType
 Note
Suppliers choose one value from a pre-defined list for this
field.
Legal Name network.corporate.legalName
State of Incorporation network.corporate.stateOfIncorporation
D-U-N-S Number network.org.dunsId
Global Location Number network.org.globalLocationNumber
Tax Classification No mapping supported.
 Note
Suppliers choose a value from a pre-defined list for this
field.
Taxation Type No mapping supported.
 Note
Suppliers choose a value from a pre-defined list for this
field.
Tax ID network.legal.taxId
State Tax ID network.legal.stateTaxId
Regional Tax ID network.legal.regionalTaxId
VAT ID network.legal.vatId
VAT Registration Document No mapping supported.
 Note
Suppliers upload a file attachment for this field.
Tax Clearance No mapping supported.
Tax Clearance Number No mapping supported.

Tax Clearance Document No mapping supported.
 Note
Suppliers upload a file attachment for this field.
Tax Clearance Expiry Date No mapping supported.
 Note
Suppliers choose a date from a calendar chooser for this
field.
Exempt from Backup Withholding network.legal.isExemptFromBackupWithholdin

g
 Note
This field is a Boolean value; suppliers choose Yes or No.
Map it to a question with the Yes/No answer type.
Business Type network.corporate.businessType
 Note
Suppliers choose one or more pre-defined values for this
field.
Company Description network.org.companyFullDescription
 Note
This field supports a lengthy description. Map it to a ques
tion with the Text (multiple lines) answer type.
Sustainability Initiatives - Plan network.org.greenPlan
 Note
This field is a Boolean value; suppliers either have the op
tion checked or they do not. Map it to a question with the
Yes/No answer type.

Sustainability Initiatives - Products & Services network.org.greenProductsAndServices
 Note
Yes/No answer type.
Sustainability Initiatives - Energy network.org.greenEnergy
 Note
Yes/No answer type.
Sustainability Initiatives - Carbon network.org.greenCarbon
 Note
Yes/No answer type.
Sustainability Initiatives - Transportation network.org.greenTransportation
 Note
Yes/No answer type.
Small Disadvantaged Business No mapping supported.
Women-Owned Business network.org.womanOwned
 Note
Yes/No answer type. Mapping for the certification type
options for this field are not supported.

Minority-Owned Business network.org.minorityOwned
 Note
Yes/No answer type. Mapping for the different minority-
owned business types for this field is supported, but map
ping for certification type options for this field are not sup
ported.
Minority-Owned Business - Asian network.org.minorityAsian
 Note
Yes/No answer type.
Minority-Owned - African American network.org.minorityBlack
 Note
Yes/No answer type.
Minority-Owned - Native American network.org.minorityNativeAmerican
 Note
Yes/No answer type.
Minority-Owned - Hispanic network.org.minorityHispanic
 Note
Yes/No answer type.

Minority-Owned - Indian Subcontinent network.org.IndianSubcontinent
 Note
Yes/No answer type.
Minority Owned - Other network.org.minorityOther
 Note
Unlike the other minority-owned fields, this is a text field
where suppliers specify a minority not included on the list.
Veteran Owned - Veteral Owned network.org.veteranOwned
 Note
Yes/No answer type.
Veteran Owned - Disabled Veteran Owned network.org.disabledVeteranOwned
 Note
Yes/No answer type.
Veteran Owned - Vietnam Veteran Owned network.org.vietnamVeteranOwned
ISO Certification No mapping supported.
Not Certified No mapping supported.
Preferred Timezone network.org.timezone
 Note
This data is derived from the account settings of the main
supplier contact in the Ariba Network for Suppliers ac
count.

Default Currency network.org.currency
 Note
count.
Preferred Language network.org.language
 Note
count.
Supplier contact fields
Business Title network.contacts.title
Email network.contacts.email
Phone network.contacts.telephone
Fax network.contacts.fax
Name network.contacts.firstname and

network.contacts.lastName
Address 1 network.contacts.line1
City network.contacts.city
Municipality / Comuna network.contacts.district
State network.contacts.state
Province network.contacts.province

Region network.contacts.region
Country network.contacts.countryCode
Postal Code network.contacts.postalCode
PO Box network.contacts.poBox
Business Role network.contacts.departmentFunction
Related Information
How Ariba Network for Suppliers profile information synchronizes to supplier

forms, questionnaires, and internal surveys
In general, the updates a supplier makes to their profile on Ariba Network for Suppliers are synchronized with
mapped questions in various supplier management forms, questionnaires, and internal surveys within minutes
unless there is an approval or update pending, in which case they are held until the pending action is completed.
There are several variations on this general rule for specific projects. For example, a supplier request does not
contain information from a supplier's Ariba Network for Suppliers account because the supplier is not connected to
that account until they submit the registration questionnaire; after that point, information in the supplier's Ariba
Network for Suppliers profile is synchronized to mapped fields in the supplier's database record, but the supplier
request in the Origin of the Supplier area of the supplier 360 profile preserves the original request information.
After the supplier submits the registration questionnaire, Ariba Network for Suppliers profile information is also
synchronized to mapped questions in registration internal questionnaires unless a category or supplier manager is
editing it; if the internal survey is in edit mode, profile information is held until the edits are submitted, at which
point it is synchronized.
Since the registration questionnaire is supplier-facing, and can be configured to use an initial registration phase
and a registration update phase with separate approvals, the synchronization of Ariba Network for Suppliers profile
information with mapped registration questionnaire answers depends on the registration's status. The following
table describes how Ariba Network for Suppliers profile information synchronizes with the registration
questionnaire at various stages in the registration workflow:

Status Profile synchronization
Registration Status: In Registration Once the supplier has accepted the invitation, logged into
Ariba Network for Suppliers, and saved but not submitted a
draft questionnaire, updates to mapped profile fields are
synchronized to the supplier-facing, draft questionnaire. Un
less the supplier edits them, they are then submitted as an
swers to the questionnaire.
Registration Status: Pending Approval After the supplier has submitted the questionnaire, any up
dates they make to mapped Ariba Network for Suppliers profile
fields are held. No updates are synchronized with the registra
tion questionnaire while it is in approval; approvers review and
approve or deny the registration based on the answers the
supplier provided at submission.
Registration Status: Registration Denied If a category or supplier manager denies the registration, no
updates that the supplier made to mapped Ariba Network for
Suppliers profile fields after submitting the registration ques
tionnaire are synchronized with the questionnaire. In your site,
the questionnaire retains the answers the supplier provided at
submission, which might be the basis for the denial, for audit
ing purposes.
Registration Status: Pending Resubmit If a category or supplier manager requests additional informa
tion before approving or denying the registration, the supplier
can edit the draft questionnaire again, and updates to mapped
Ariba Network for Suppliers profile fields are synchronized to
the supplier-facing, draft questionnaire. Unless the supplier ed
its them, they are then submitted as answers to the question
naire.
Registration Status: Registered After the registration is approved, any updates a supplier
makes to mapped Ariba Network for Suppliers profile fields are
synchronized to the registration questionnaire within minutes.
Registration Update Status: Pending Approval After the supplier has submitted a questionnaire update, any
updates they make to mapped Ariba Network for Suppliers
profile fields are held. No updates are synchronized with the
registration questionnaire while the update is in approval; ap
provers review and approve or deny the updated registration
based on the answers the supplier provided at submission.
Registration Update Status: Denied If a category or supplier manager denies the registration up
date, no updates that the supplier made to mapped Ariba Net
work for Suppliers profile fields after submitting the registra
tion questionnaire update are synchronized with the question
naire. In your site, the questionnaire retains the answers of the
previous, approved version of the questionnaire.

Status Profile synchronization
Registration Update Status: Pending Resubmit If a category or supplier manager requests additional informa
tion before approving or denying the updated registration, the
supplier can edit the draft questionnaire again, and updates to
mapped Ariba Network for Suppliers profile fields are
synchronized to the supplier-facing, draft questionnaire. Un
less the supplier edits them, they are then submitted as an
swers to the questionnaire update.
Registration Update Status: Approved After the registration update is approved, any updates a sup
plier makes to mapped Ariba Network for Suppliers profile
fields continue to be synchronized to the registration question
naire within minutes.
Mapping supplier name and extended address questions to international

versions in an integrated ERP system
SAP ERP and SAP S/4 HANA can store vendor information in different languages using international tables. You
can use questions about supplier names and extended addresses mapped to international versions to collect this
information in supplier management questionnaires and synchronize it to the integrated ERP system.
In SAP, international versions are identified by letters or numbers; for example, I for International, C for Chinese,
and so on.
To collect supplier name and extended address information in different languages, create separate questions for
each language and use the following field mappings, specifying the identifier for the version in parentheses:
● vendor.addressExt.orgName(versionID).name1
● vendor.addressExt.orgName(versionID).name2
● vendor.addressExt.postalAddress(versionID)
For example, for name1, vendor.addressExt.orgName(I).name1 maps to the International version,

vendor.addressExt.orgName(C).name2 maps to the Chinese version, and so on. If you want to collect
information for multiple international versions in one questionnaire, you can create separate questions for each
version and use visibility conditions to show or hide those questions based on the characteristics of each project.
Related Information


Field encryption in the vendor database
SAP Ariba encrypts certain database fields, including fields in the SAP Ariba Supplier Management solutions
unified vendor model, to provide an additional layer of protection for sensitive data.
If you map a question in a supplier management questionnaire [page 260] to an encrypted database field, the
answer is encrypted.
SAP Ariba Uses 256-bit AES encryption with Java Cryptography Extension (JCE) to apply a double layer of
encryption using keys that are specific to your site. The following fields in the vendor database are encrypted using
this method:
● vendor.taxInfo.vatRegistrationNumber
● vendor.bankInfos.accountName
● vendor.bankInfos.accountNumber
● vendor.bankInfos.bankAccountExternalID
● vendor.bankInfos.bankAccountStandardID
● vendor.bankInfos.bankInternalID
● vendor.bankInfos.bankStandardID
● vendor.bankInfos.controlKey
● vendor.bankInfos.id
● vendor.bankInfos.substituteBusinessPartnerBankDetailsID
● vendor.taxExt.countryCode
● vendor.taxExt.longPartyTaxID
● vendor.taxExt.partyTaxID
● vendor.taxExt.taxIdentificationNumberTypeCode
● vendor.taxInfo.taxNumber1
The shared secret used for authentication is also encrypted using this method.
Related Information


How to add a requirement to a supplier form or
questionnaire
A requirement is a statement that communicates your expectations or other information to suppliers and internal
stakeholders.
Procedure
○ 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.
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 in a supplier-facing questionnaire, 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 299] for details.
7. Click OK.
Related Information

[page 245]

How to add translations for some form and questionnaire
content fields
When you provide translations of form or questionnaire content fields 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 fields in the original language in which you created them (the base language).
Prerequisites
To edit project templates you must be a member of the Template Creator group. To add translations to form or
questionnaire content fields, you must also belong to the Translator group.
Context
You can provide translations for the names of all supported content types in supplier forms and questionnaires. For
questions with answer types that support these features, you can also provide translations for the Search Term
and Validation Pattern Error Message fields.
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 fields, so you can also duplicate the formatting.
 Note
When you provide a translation for the Name field of a question, that translation applies only to the name itself.
There is no way to translate pre-defined 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.
 Tip
If you are providing translations for content names, you can add translations for all of the content names in a
template survey document in one place by choosing Actions Translate on the content table of the
survey document. You must add translations for other supported fields while adding or editing individual
questions, and you can also add translations for the name this way.

Procedure
1. Add or edit a piece of content in a supplier management template survey document.

2. Click the Translations link immediately below the Name field, or to the right of any other field that supports
translations.
3. Enter a translation for the field in the corresponding translation field. If you have already entered translations,
they are displayed and you can edit them.
4. Click OK.
How to add an attachment to a supplier form or

questionnaire
An attachment in a form or questionnaire is 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
○ 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.
○ 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.
Next Steps
You can apply settings such as visibility conditions by editing the newly created attachment. Settings are only
available when the attachment is in edit mode. You can also mask attachments so that only the internal users with
the appropriate permissions can view or download them.
 Note
The attachment masking setting is not supported in supplier risk engagements.
Related Information
[page 245]
Masking sensitive data in supplier forms and

questionnaires
Masking sensitive data allows you to control who can view it. Internal users cannot view or edit sensitive data
unless they have specific permissions.
You can mask both question answers and attachments.
The following table describes who can view masked data:

These people... Can...
Members of the Sensitive Data Access group View masked answers and open masked attachments in the
user interface.
Supplier contacts See an icon next to questions with defined masking patterns
and attachments with masking settings indicating that ability
to view their answer will be restricted in their customer’s sys
tem.
Data is not masked for suppliers, but only the supplier contact
who is asked to fill out the questionnaire can view or edit it.
Masked data is never visible in exported questionnaire CSV files or exported SOAP XML integration messages.
● Masking sensitive question answers [page 298]

● Masking sensitive attachments [page 299]
Masking sensitive question answers
For questions of type Text (single line) and Text (single line limited), you can use the Sensitive Data Mask
Pattern field to define a data masking pattern using a regular expression, which is a sequence of characters that
defines the pattern. Users who do not have permission to view masked data see an asterisk (*) in place of each
masked character.
Regular expressions use standard text strings and syntax to define patterns. The masking pattern you define
specifies how to mask the answer by enclosing the part of the pattern you intend to mask with parentheses; for
example, you can mask all of an answer, all but the last four characters, and so forth. There are a number of
websites on the Internet that can help you understand, formulate, and test regular expressions.
The following example regular expressions define some common masking patterns:
Regular Expression Description Example
(.*) Masks the entire answer. The answer Bob Smith is masked as
********.
(.*)@.* Masks the answer up to the @ symbol. The answer [email protected] is

masked as ****@mycompany.com.
(\d*)[0-9]{4} Masks all numbers up to the last four. The answer 123456789 is masked as
*****6789.
([0-9-]+)[0-9]{3} Mask all numbers and dashes except last The answer 123-456-789 is masked as
3 numbers. ********789.
[0-9]{3}(\d*)[0-9]{3} Masks all numbers except for the first The answer 123456789 is masked as
three and last three numbers. 123***789

Regular Expression Description Example
[^0-9]*([0-9]+) Masks all numbers to the end of the an The answer ABC-1234 is masked as ABC-
swer. ****.
Unless you are just masking the entire answer in a generic way, you must know the format of the answer before you
can construct a regular expression that masks it exactly the way you want. You can use validation patterns to define
and enforce the format of the answer and ensure that your masking pattern will mask the answer correctly.
Masking sensitive attachments
For attachment content, questions of type Attachment, and all questions that support attaching reference
documents or allowing suppliers to add attachments to their answers, you can use the Mask Attachment
dropdown menu to restrict who can open the attachment. Depending on whether you are providing the attachment
or allowing the supplier to do so, or both, you might have some or all of the following options:
● None: No attachments associated with the current content are masked. This is the default setting.
● Reference Documents: Reference documents that you have attached to the current content are masked.
● Participant Documents: Documents that the supplier has attached to the current content are masked.
● All: all attachments associated with the current content are masked.
Related Information
Topics about using visibility conditions to show or

hide questionnaire content based on answers
How to create a basic visibility condition in a form or questionnaire [page 301]
How to create an advanced visibility condition in a form or questionnaire [page 302]
Expressions for advanced visibility conditions [page 304]
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 fulfills 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.
● Basic visibility conditions [page 301] are based on the answer to one question.
● Advanced visibility conditions [page 302] 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:
● For forms and most types of questionnaires, all respondents see the single form, and visibility conditions based
on region can be useful for displaying content dynamically based on answers. But qualification questionnaires
are assembled from content document segments that are targeted to specific commodities, regions, and (if
the business unit supplier management matrix enhancement is enabled in your site) departments. It is
therefore important be aware of all of your existing segments and the commodity, region, and department
settings you have applied to each segment, and only apply visibility conditions based on commodity, region, or
department in segments where it makes sense.
For example, 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 with the answer type Text (multiple lines) or on the
"complex" answer types Address, Extended Address, Bank Account, and Tax. You can create conditions
based on questions of any other answer type. For questions of answer type Certificate, you can create
conditions based on the initial Yes or No answer, but not on certificate detail fields.
● If you set a visibility condition for content in external (supplier-facing) questionnaires, make sure that the
question that triggers the condition is visible to participants.
● In internal supplier management questionnaires such as the internal supplier request, you can create
questions based on Locale master data, but you must specify field matches to locale codes rather than locale
names. Members of the Customer Administrator group can export the locale codes used in your site using the
Export Locale (CSV) data export task in Manage Administration Site Manager Data Import/
Export , where they are listed in the UniqueName field of the exported CSV file.
● Internal questionnaires in supplier request, registration, qualification, disqualification, and preferred supplier
management projects support visibility conditions based on the following answer types:
○ Text (single line limited)
○ Text (single line)
○ Whole Number
○ Decimal Number
○ Percentage
○ Money
○ Quantity
○ Date
○ Yes/No
○ Certificate (for the initial Yes or No answer, but not any certificate detail fields)
○ Commodity

○ Region
○ Department
Related Information
How to create a basic visibility condition in a form or

questionnaire
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
 Note
You cannot create conditions based on questions of answer type Text (multiple lines) or the individual fields in
questions of answer type Bank Account, Address, Extended Address, or Tax. You can create conditions based
on the initial Yes or No answer for Certificate questions, but not on individual certificate detail fields.
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 content. When you are creating or editing the content, for
Visibility Condition, click none and choose from the list of available conditions.
How to create an advanced visibility condition in a form or

questionnaire
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.
Context

 Note
You cannot create conditions based on questions of answer type Text (multiple lines) or the individual fields in
questions of answer type Bank Account, Address, Extended Address, or Tax. You can create conditions based
on the initial Yes or No answer for Certificate questions, but not on individual certificate detail fields.
Procedure
1. Use an existing question or create a new question on which to base the condition.
○ 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 304]
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 the
content, for Visibility Condition, click none and choose from the list of available conditions.

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 ex
pressions to match (AND). You can use the All of expression to make a condition true under specific,
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.
Using editability conditions to control the editability

of answers in a form or questionnaire
The content to which you have applied an editability condition is read-only unless the condition is met. At that
point, the page refreshes and the conditional content becomes editable.
Editability conditions function much like visibility conditions [page 299]. You can create them based on answers to
other questions, or based on the specific characteristics of a project.
To create an editability condition based on the answer to another question, follow the procedure for creating a basic
[page 301] or advanced [page 302] visibility condition, then apply it to a question using the Editability Conditions
setting rather than the Visibility Conditions setting.
To create an editability condition based on a project characteristic, create a project-level condition as described in
the Project Template Guide. The basic steps for creating project-level conditions and visibility conditions are the
same; however, you create project-level conditions on the template Conditions tab and use field matches based on
project-level attributes such as status, owner, or other fields.
You can use editability conditions in survey content documents in any supplier management project template.
However, they are particularly useful in external (supplier-facing) questionnaires in the supplier registration project
template, where you can use them to:
● Streamline the registration questionnaire for legacy suppliers while keeping questions visible [page 168]

● Prevent suppliers from changing some answers when they update the registration questionnaire [page 166]
Topics with supplier management questionnaire

content examples
Example: how to create a dropdown menu with predefined values on a supplier form or questionnaire [page
305]
Example: how to automatically reject answers that don't fall within a limited range on supplier forms and
questionnaires [page 306]
Example: how to ask for a supplier certificate [page 307]
Example: how to ask for a supplier's address and map the answer to the supplier database [page 308]
Example: how to create a question that is only to visible suppliers with green certifications [page 309]
Example: how to ask about preferred supplier levels using master data values [page 310]
Example: 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
● 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.
Example: how to automatically reject answers that don't fall

within a limited range on supplier forms and questionnaires
When you add a question with a limited range answer to a form or questionnaire, 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
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 respondent’s answer be in the current year, current month,
previous fiscal quarter, and so forth.
Procedure

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.
Example: how to ask for a supplier certificate

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

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 Supplier field mapping field, enter vendor.certificate.
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.
Any certificates a supplier uploads in response to a question of type Certificate are shows on the Certificates tab
of the Overview tile in the supplier's 360° profile.

Example: how to ask for a supplier's address and map the
answer to the supplier database
Context
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 address street:
a. Click the address section and choose Add Question .

b. For Location, choose Add Inside.
c. Enter a name for the question, such as Street:.
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 Supplier field mapping field, enter vendor.address.line1
g. 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 Supplier field mapping field, enter vendor.address.city
g. Click Done.
4. Repeat the procedure to create questions in the address section for state, region, or province (mapped to
vendor.address.state), postal code (mapped to (vendor.address.postalCode), and country (mapped
to vendor.address.countryCode).

Example: how to create a question that is only to 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 Supplier field mapping field, enter vendor.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.

Example: 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 qualified suppliers they work with.
Procedure

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 Supplier field mapping field, enter project.Level.
7. On the Master data type to use for values dropdown menu, choose Supplier Preferred Level.
Results
Users answering this question select from among the supplier preferred levels defined in your site's master data on
a dropdown menu.

Topics about adding project groups and team
members to project templates
Adding project groups and team members to project templates [page 311]
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, qualification, disqualification,
preferred supplier management, modular supplier management questionnaire, and control-based engagement
risk assessment project groups, if your site includes user assignments to project groups based on project
commodities and regions (the user matrix), you can specify that members of a project group are added
dynamically based on assignment (Use commodity and region assignments). Note that user matrix
assignments are not supported in modular questionnaire projects created by sending assessments in
● 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. They are not supported in supplier request, registration, qualification, disqualification,
preferred supplier management, modular supplier management questionnaire, and control-based engagement
risk assessment projects.
Note that while you can specify that project owners can edit project groups in legacy engagement risk assessment,
supplier request, supplier registration, supplier qualification, supplier disqualification, preferred supplier
management, and modular supplier management questionnaire project templates, many of the users who work
with those projects do not have access to the advanced view, where they can use the Team tab. Users who do not
have access to the advanced view of those projects cannot edit their project groups even if they are project owners
and the groups in the project allow project owners to edit them. Note that to see the advanced view of a supplier
management project, the Advanced View link for that project type must be enabled in your site and you must have
appropriate group membership permissions. See How to manage access to the advanced view of supplier
management projects in the Supplier management setup and administration guide.

Topics about adding project groups and team members to project templates PUBLIC 311
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.
 Note
In control-based and legacy engagement risk assessment, issue management, supplier request, supplier
registration, supplier qualification, supplier disqualification, preferred supplier management, and modular
supplier management questionnaire projects the user who creates the project (by requesting a supplier or
engagement, inviting a supplier to register, and so on) is the initial project owner in most circumstances. With
supplier registration projects, project ownership depends on whether the project was created manually,
automatically, or through mass invitation. Control-based engagement risk assessment and issue management
projects support changing the project owner after project creation.
Understanding buyer category assignments (the user

matrix)
User matrix data loaded in your site assigns specific users to project groups for specific commodities, regions, and
departments. These assignments allow you to route supplier management projects to the category or supplier
managers who are responsible for those commodities and regions.
Buyer category assignments automatically add project team members when a supplier management project is
created. In fact, they are the only way to add team members to the Project Owner group from a template, since
individual users added to a template's Project Owner group are not inherited by any projects that are created from
the template.
Buyer category assignments are created by a combination of two components:
● User matrix data, which an administrator imports into your site as a CSV data file [page 98]. The file assigns
either individual users or global user groups to project groups for specific commodities, regions, and
departments.
● Template project groups with the Use commodity and region assignments setting enabled. Importing user
matrix data does not automatically create the project groups it references. Default template project groups
such as Project Owner do not automatically use user matrix data to assign team membership. You must create
or edit the project groups referenced in your site's user matrix data and enable the assignment setting [page
98] so that the user matrix data is used to add team members to them.
Buyer category assignments are always based on a combination of commodity and region. The combination can be
general (all commodities or all regions), narrow (solid-fiber cardboard crates or London), or anywhere between in
the commodity and region hierarchies. When a supplier management project is created, it checks to see if there are
users assigned to the supplier's commodity code and region; if there is no exact match, it looks for the users who
are assigned to the commodity code and region above them in the hierarchy and adds those users to the team
instead. Since sites often have thousands of low-level commodity codes, and hundreds of low-level regions, buyer

312 PUBLIC Topics about adding project groups and team members to project templates
category assignments ensure that the most appropriate users are always added to supplier management project
teams. For example, if there is no user assigned to Vermont, a supplier registration project will add the user
assigned to the United States to the project team instead.
If your site has the business unit supplier management matrix enhancement feature enabled, buyer category
assignments are based on a combination of commodity, region, and department. The assignments work the same
way with your company's department hierarchy as they do with commodity and region hierarchies.
For details on how specific project commodities, regions, and departments translate into buyer category
assignments, see User matrix (buyer category assignment) data file format [page 98].
Buyer category assignments function in substantially the same way as team member rules do in other SAP Ariba
projects. However, they are designed specifically for supplier management workflows, so they have the following
advantages over team member rules:
● They are applied only based on commodity, region, and department which are the most common metrics by
which companies organize their supplier management processes.
● They apply to all supplier management projects in a site, meaning:
○ A single source of assignment data. A template creator must upload team member rules files to each
individual project, but a customer administrator can upload and maintain buyer category assignments for
all supplier management projects in a single CSV file.
○ Continuity of team membership across the entire supplier lifecycle. Since assignments apply to all supplier
management projects in a site, the same category or supplier managers and other team members manage
the same suppliers across all related supplier management projects.
● More flexibility: team member rules with assign users to projects based on exact matches to a field value, while
buyer category assignments will also look for matches above the specified value in a hierarchy if there are no
exact matches.
 Restriction
● Since supplier qualification, disqualification, and preferred supplier management projects are always based
on a commodity/region/department combination, buyer category assignments are automatically applied
to the project groups where they are enabled in these projects. They are also applied to supplier request
projects if the supplier request form includes questions based on commodity, region, and department
master data that are mapped to matrix.Categories, matrix.Regions, and matrix.Departments
respectively, since those questions set the commodity, region, and department for the request project.
They are not applied to supplier registration projects, where there is currently no way of setting the
project's commodity, region, and department from mapped questions or other content.
● In solutions that include SAP Ariba Supplier Risk, buyer category assignments are not applied to the
modular questionnaire projects that are created by sending assessments for engagement risk assessment
projects.
Related Information
User groups in supplier management buyer category assignments (the user matrix) [page 36]

How to use buyer category assignments to add team
members to project groups
You must configure project groups to use buyer category assignments, which specify the users that are added to
project groups in supplier request, qualification, disqualification, and preferred supplier management projects
based on the project's commodities, regions, and departments.
Prerequisites
Commodity and region assignments work automatically in supplier qualification, disqualification, an preferred
supplier management in the project groups that are configured to use them. They will only work in request projects
if the request form includes questions based on commodity and region master data that are mapped to
matrix.Categories and matrix.Regions respectively. They also include department in sites with the business
unit supplier management matrix feature enabled.
 Note
Buyer category assignments are not currently supported in supplier registration projects or in the modular
supplier management questionnaire projects that are created by sending assessments in control-based
Commodity, region, and department assignment data (the user matrix) must be imported into your site in order for
users to be added to project groups based on those assignments.
To make supplier or category managers the owners of those supplier projects based on commodity, region, and
department assignments, you must edit the Project Owner group to apply the assignments (user 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.
2. On the Team tab, choose Actions Team Members Edit .

○ 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 Use commodity and region assignments, 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.

314 PUBLIC Topics about adding project groups and team members to project templates
Related Information

How to edit a project template [page 117]

Topics about setting up supplier form and
questionnaire approvals
You define the approval process for a supplier form or questionnaire in an associated approval task.
Topics about creating approval flows in the approval rules editor [page 316]
Using commodity, region, and department assignments for form and questionnaire approvals [page 329]
Creating conditional approval flows based on form and questionnaire answers [page 333]
Setting up external approval of SAP Ariba project approval tasks [page 337]
Topics about creating approval flows in the approval

rules editor
About approval rules in project templates [page 316]
How to create or edit approval rules [page 318]
About the approval rules editor [page 320]
How to create a simple approval rule [page 321]
How to edit approval flows with the approval process diagram [page 323]
Using approval rule conditions [page 324]
How to add approvers in the approval rule editor [page 328]
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.
 Note
Do not add approvers to an approval task that you have set to auto approve. You cannot publish supplier
request, supplier registration, supplier qualification, supplier qualification request, supplier disqualification,
preferred supplier management, or modular supplier management questionnaire project templates that
include an approval task with approvers and Allow auto approval set to Yes.

316 PUBLIC Topics about setting up supplier form and questionnaire approvals
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). SAP Ariba 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, SAP Ariba first assigns the task to user AAA. After AAA submits his or her approval, SAP Ariba assigns the
task to user BBB.
Parallel approvers are assigned simultaneously. SAP Ariba assigns the task to the approvers at the same time. In
the following approval flow, SAP 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, SAP Ariba 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, SAP Ariba inserts the group as a single unit in the approval
flow. If you select Yes, SAP Ariba expands the group and inserts each user as a parallel approver. The default
value is No.

Topics about setting up supplier form and questionnaire approvals PUBLIC 317
● 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, SAP Ariba does not expand the group.
● If the group was inherited from an approver lookup table file in the template, SAP Ariba does not expand the
group.
How to create or edit approval rules
Approval rules specify who has to review or approve a document.
Prerequisites
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 117].
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 Restrictions when specifying approvers in
the approvers or reviewers field [page 319] for restrictions.
○ 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.
Restrictions 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 restrictions:
● 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.
● 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 328].
● 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.
Related Information
How to create notification profiles

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.
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 323].
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
324].
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 328].
Related Information
How to create a simple approval rule [page 321]
How to create a simple approval rule
Prerequisites

Context
You can 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 324].
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 328].
○ 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 328].
○ 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.
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 320]

How to edit approval flows with the approval process

diagram
Approval rules in approval flows specify who has to review or approve a document. You can define an approval flow
with multiple rules using an approval process diagram.
Prerequisites
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 ().
Procedure
1. Open the approval flow editor as described in Creating or Editing Approval Rules [page 318].
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 Rule or Add Parallel Rule.
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 324]).
● Add approvers.
Related Information
How to add approvers in the approval rule editor [page 328]

How to add approvers from approver lookup tables
How to configure supervisor rules
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.
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 [page 325]
Subconditions [page 325]
How to define approval rule conditions [page 326]
Related Information
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 326].
Subconditions
Subconditions enable you to group and evaluate a set of condition components as a whole.
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 318].
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 325].
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.

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.
Related Information
Condition Expressions
Guidelines for Defining Conditions
Defining approval rule conditions with document fields

How to add approvers in the approval rule editor
Prerequisites
Procedure
1. Open the approval rule editor as described in How to create or edit approval rules [page 318].
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
326].
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.
○ 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 SAP 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 site configuration parameter Let project creators bypass approvals for runtime edits
(Application.AQS.RFX.SuppressRuntimeEditApprovals) is set to No. For more information, see
the topic Let project creators bypass approvals for runtime edits in Intelligent Configuration Management
parameters reference.
○ Add Contract Approver: adds the Contract Approver global group in SAP Ariba Contracts 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.

 Note
For supplier management project approval flows, only add project groups. In the case of a missing approver
in a supplier management project approval flow, the add missing approver tool only works when the
missing approver is in an empty project group. It does not support adding approvers to other approver
categories.
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 configure supervisor rules

Let project creators bypass approvals for runtime edits
Using commodity, region, and department

assignments for form and questionnaire approvals
After adding members to supplier project teams using buyer category assignments (the user matrix), 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.
● 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
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 Request 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 117].
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 Use commodity and region assignments, 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 .

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
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
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.
Creating conditional approval flows based on form

and questionnaire answers
Conditional approval flows in supplier management projects can add relevant departments, such as the legal or
finance department, to the approval flow of a form of questionnaire based on the answers to specific questions.
These conditions are triggered by hidden questions in the form or questionnaire.
Supplier management projects include six specialized project-level fields (with project field mappings [page 260])
that allow you to create conditional approval flows based on answers to questions. They are:
● Finance Approval Level (mapped to project.FinanceApprovalLevel)

● Legal Approval Level (mapped to project.LegalApprovalLevel)
● Line of Business Approval Level (mapped to project.LOBApprovalLevel)
● Purchasing Approval Level (mapped to project.PurchasingApprovalLevel)
● Quality Approval Level (mapped to project.QualityApprovalLevel)
● Sustainability Approval Level (mapped to project.SustainabilityApprovalLevel )
You use these field mappings in hidden questions to set numeric values between 1 and 5 in these project fields, and
then use them to trigger the conditional approval flow.
The high-level workflow for adding project groups to an approval flow based on answers to a question is as follows:
1. (Optional) If you want to add users to the project group dynamically, perform the following steps:
○ Set up buyer category assignments [page 311] so that users are added to the project group you want to
use in the conditional approval flow based on the supplier's characteristics.
○ On the project's Team tab, add the project group you want to use in the conditional approval.
2. In the form or questionnaire, create the question [page 236] on which you want to base the conditional
approval flow. Make sure that the question you create either uses a list of choices or master data value for the
acceptable answer, or has an answer type of Yes/No or Date, so that possible answers are limited to a specific
set of values that you can use to define a condition.
3. Create a simple visibility condition [page 301] with a content match to the previous question and specify the
answer that you want to use to trigger the conditional approval flow.
4. Add another question under the previous question with the following settings:
○ For Answer Type, choose Whole Number.

○ For Response Required?, choose Not Required.
○ For Visible to Participant, choose No.
○ For Supplier field mapping, enter the project level field mapping for the field you want to use in the
conditional approval, such as project.LegalApprovalLevel.
○ For Visibility Conditions, choose the condition you just created for the answer.
○ For Initial Value, enter a numeric value between 1 and 5.
 Note
There can be only one of each available combination of field mapping and initial value present a single
questionnaire. For example, there can only be one question mapped to project.LegalApprovalLevel
with an initial value of 2 in a single registration questionnaire. For qualification questionnaires assembled
from content document questionnaire segments, the assembled questionnaire can only contain one of
each available combination of field mapping and initial value total. If different content documents with the
same mapping and initial value combination are included in the same qualification questionnaire, the
conditions built on that combination do not function correctly in that questionnaire.
5. On the project's Conditions tab, create a project-level condition using a field match. Select the field that
corresponds to the field mapping you used in the hidden question and set a value equal to the initial value you
used in the hidden question.
6. Create or edit the approval task on the questionnaire survey document [page 318]. Specify a custom approval
flow and use the project-level condition [page 324] to add the project group to the approval flow.
With this configuration, when a supplier enters the answer specified in the questionnaire visibility condition, the
hidden question is activated, but it is not visible. The hidden question adds the specified initial value to the mapped
project-level field, which triggers the project-level condition. The project-level condition adds the specified project
group to the approval flow, and the buyer category assignments or team member rules add specific users to the
project group, where they become approvers for the supplier.
This process describes the simplest configuration using a single hidden question to trigger conditional approval.
You can use multiple hidden questions and project conditions to create more complex conditional approvals. For
example, if you have a question with a list of choices defined for its acceptable answers, you can use multiple
hidden questions to define a unique initial values for each choice, and create a separate project condition for each
hidden question value, in order to define a different conditional approval flow for each possible answer to the
question.
Since there are 6 specialized project-level fields, and you can use each of them to trigger 5 separate conditions
(using numbers 1 through 5), you can create up to 30 separate approval conditions in total.
Example: How to add the legal department to an approval

flow when a supplier won't agree to your code of conduct
Prerequisites
This example assumes that you are using buyer category assignments to assign specific users to the Legal
Approvers project group based on region.

Context
This example uses a question in the external supplier request questionnaire asking suppliers to agree to your code
of conduct. If the supplier answers yes, you do not need to change the approval flow for the external supplier
request. However, if the suppliers answers no, you will require them to upload their own code of conduct, and you
want to add a member of your legal department to the approval flow so that they can review and approve it before
the external supplier request goes to any other approvers. You will use the Legal Approval Level project field in a
hidden question to set up the conditional approval.
Procedure
1. Open the external supplier request 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 117].
2. On the Documents tab, click the external request and choose Edit.
3. Create the question about your code of conduct by performing the following steps:
a. In the content area of the questionnaire, click Add Question .

b. Enter a name for your question, such as Do you agree to my company's Code of Conduct?
c. On the Answer Type dropdown menu, choose Yes/No.
d. On the Response Required dropdown menu, choose Yes, Participant Required.
e. Click Attach a file and attach your code of conduct document to the question.
f. On the Visible to Participant dropdown menu, choose Yes.
g. Click Done.
4. Create a visibility condition based on an answer of No to this question by performing the following steps:
a. Click the question you just created and choose Edit.
b. Choose Add Condition .
c. On the Edit Conditions page, click Add.
d. Enter a name for the condition, such as Does not accept Code of Conduct.
e. (Optional) Enter a description for the condition.
f. For the expression, click Undefined and choose the code of conduct question.
g. Choose No from the available answers.
h. Click OK.
i. Click Done.
5. Require any supplier who answers No to upload their own code of conduct by performing the following steps:
a. In the content area of the external request, select the code of conduct question, then click Add
Question .
b. On the Add Question page, choose Add After.
c. Enter a name for the question, such as Please attach your own code of conduct.
d. On the Answer Type dropdown menu, choose Attachment.
e. On the Response Required dropdown menu, choose Yes, Participant Required.
f. On the Visible to Participant dropdown menu, choose Yes.
g. On the Participant can add additional comments and attachments dropdown menu, choose Yes.
h. For Visibility Conditions, click none and choose the condition you just created based on a No answer to
the first code of conduct question.

i. Click Done.
6. Create a hidden question that sets a value of 1 for the Legal Approval Level field by performing the following
steps:
a. In the content area of the external request, click Add Question .

b. Enter a name for the hidden question, such as Trigger for legal approval level.
c. On the Answer Type dropdown menu, choose Whole Number.
d. On the Response Required dropdown menu, choose Not Required.
e. On the Visible to Participant dropdown menu, choose No.
f. In the Supplier field mapping field, enter project.LegalApprovalLevel.
g. For Visibility Conditions, click none and choose the condition you created based on a No answer to the
first code of conduct question.
h. In the Initial Value field, enter 1.
i. Click Done.
7. Create a project condition based on a value of 1 for the Legal Approval Level field by performing the following
steps:
a. To save your changes to the external request and return to the project, click Exit, then click return to
project.
b. Click the Conditions tab.
c. Click Add Condition.
d. Enter a name for the project condition, such as Requires legal review.
e. (Optional) Enter a description for the condition.
f. For the expression, click All are true and choose Field Match.
g. Choose Select more fields... .
h. Locate Legal Approval Level on the list of available fields and click Select.
i. For the operator, choose is equal to.
j. To set the value, choose Select Select Value , then enter 1 and click OK.
k. Click OK.
8. Create a new project group for legal approvers by performing the following steps:
a. Click the Team tab.
b. Choose Actions Team Members Edit .
c. Click Add Group.
d. For Use commodity and region assignments, choose Yes.
e. In the Title field, enter a name for the group, as Legal Approvers
f. Click OK.
9. Create a new approval rule that adds the new group as an approver to every external supplier request where
the supplier answers No to the code of conduct question by performing the following steps:
a. Click the Tasks tab.
b. Click the approval task for the external request and choose Edit Task.
c. For Approval Rule Flow Type, choose Custom.
d. Click Custom to open the approval flow editor.
e. In the Approval Process Diagram area, click the action triangle button () to the left of the Project Owner
approval node and choose Add Serial Rule.
A new, untitled node appears to the left of the Project Owner node.

f. In the Approval Rule Editor area, enter a name for the node, such as Legal, and a description, such as
Adds a member of the legal department to the approval flow if the supplier does
not agree to our code of conduct and uploads their own instead.
g. In the Condition area, click the action triangle button () next to All Are True and choose Add
h. On the Reference to Condition dropdown menu, choose Search more, then click the Select button to the
right of the Requires legal review condition.
i. Click OK.
j. In the Action area, for Type, choose Add Approvers and Groups.
k. From the Action dropdown menu, choose Add Project Group.
l. Make sure that All users in group have to approve is not selected. In this scenario, you only need one user
from the legal department to approve the request.
m. Select Approval Required.
n. For ProjectGroup to be added to the flow?, on the dropdown menu, choose Search more. Click the
Select button next to Legal Approvers, then click Done.
o. For Reason for the specified approver(s) to be added to the flow , enter a reason such as A legal
representative must approve all codes of conduct submitted by suppliers.
10. Click Done.
Results
When you publish the template, and a supplier answers No to your code of conduct question, the following actions
occur in the external supplier request project:
● The No answer makes your follow-up question, requiring the supplier to attach their own code of conduct when
they submit the request, visible.
● The No answer activates the hidden question, which sets the value of the project's Legal Approval Level field to
1.
● Setting the Legal Approval Level field to 1 triggers the project legal approval condition.
● The project adds the Legal node to the external request's approval flow.
● Buyer category assignments add the appropriate users to the project's Legal Approvers group, and one of
them is responsible for reviewing and approving the supplier's code of conduct.
Setting up external approval of SAP Ariba project

approval tasks
The SAP Ariba external approval API allows users in external systems to approve or deny approval tasks in SAP
Ariba projects. There are some specific approval task settings that enable external processing using this API and
ensure that it runs smoothly.
To enable external approval of an SAP Ariba project approval task, set External System Approval to Yes. With this
setting, the external approval API can process approval, denial, or request for additional information with the task.

Keep the following considerations in mind when configuring approval in this task and any related tasks:
● Make sure that any approval task configured for external approval is not also set to auto-approve. These two
settings are incompatible.
● SAP Ariba recommends that you include only one approval node in tasks that allow external approval. To
combine external and SAP Ariba approvers for a single document, use separate approval tasks and chain them
together as predecessors.
● Within an approval node in a task configured for external approval, at least one of the available approvers must
also be a user in the external system. To process an external approval correctly, the approving external user
must match an existing SAP Ariba user who is an approver in that node.

Topics about setting default values for vendor
database fields
Setting default values for vendor database fields [page 339]
Default_properties.csv [page 341]
Defining lookup key field-based default values for company code, purchasing organization, and other array
fields [page 342]
Defining default values based on condition fields [page 344]
Setting default values for vendor database fields

Default field values allow you to specify initial values for fields in the vendor database. You set default values by
importing a CSV file that defines them.
There are several situations for which it is useful to set default values:
● To supply initial values for fields that are required in the integrated ERP system: Setting default values
ensures that required fields are populated with initial values when the supplier is first synchronized to an
integrated SAP ERP system. In this situation, they are particularly useful if you synchronize new suppliers
before registration or do not plan to include mapped questions for some required fields in 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.
● To set detail data based on the value supplied in a lookup key field: Category or supplier managers are
unlikely to know all of the details associated with each of your company's purchasing organization, company
code, and other data structures. Setting default values for detail fields in an array class based on the value
specified for the lookup key field [page 342] ensures that the data in the detail fields is always correct. For
example, you can define default purchasing organization details for each purchasing organization ID. The fields
for which you set defaults must belong to the same array class as the lookup key field.
You can then set up a question in a supplier form or questionnaire with a list of predefined choices for answers,
where each of the choices is associated with one of the lookup key values you have defined, and map these
questions to the lookup key field. When a user chooses an answer to the question mapped to the lookup key
field, that answer sets the associated default values.
● To set default values in one field based on the value in another field: If the value in field A is always
dependent on the value in field B, setting the default value for field A conditionally based on the value in field B
[page 344] ensures that the data in field A is always correct. For example, if your company codes are based on
the supplier's location, you can set default company codes conditionally based on one or more values in the
supplier's address, such as state or country.
You can then set up questions with a list of predefined choices for answers, where each answer matches a
value in a condition field, or you can use condition fields that are associated with master data such as country

Topics about setting default values for vendor database fields PUBLIC 339
or region codes or departments. When a user chooses answers that match a defined condition, those answers
set the associated default value.
You can define simple default, defaults based on lookup keys, and conditional defaults in the same
Default_properties.csv file.
The Default field values area of SM Administration provides samples and allows you to download your current
default settings and upload new default settings. Members of the SM Ops Administrator and SM ERP
Administrator groups can download sample files and import the default definition CSV file in this area.
There are two sample files available:
● Default_properties_sample.csv, which has 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
vendor.vendorInfoExt.categoryCode to 2.
● Default_properties_special_names.csv, which has a number of SAP Ariba-specific variables you can
use to set default field values. For example, if you set a field default to ${current.date}, when the supplier
data is sent to SAP ERP, the field value is set to the current date. SAP Ariba provides variables for system
information (current date, user names) and supplier management information (commodity, region,
department, preferred level, qualification status).
 Tip
Using variables to set initial default field values is a useful way of ensuring that information that is included in
the SAP Ariba data model, but not in the default SAP ERP data model, is synchronized to the ERP system after
supplier creation. This information is often set automatically in SAP Ariba (for example, ANID) rather than
included in mapped questions in questionnaires. For example, you can use variables to send the supplier ANID
and S4 org system ID to generic custom fields in the ERP system.
 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.
● Default_properties.csv and Default_properties_special_names.csv set initial default values
in vendor database fields for suppliers created directly in SAP Ariba Supplier Management solutions. They
do not set default values for suppliers created by synchronization from the ERP system.
Related Information
Default_properties.csv [page 341]

340 PUBLIC Topics about setting default values for vendor database fields
Default_properties.csv
Default field values specify the initial values set for supplier fields. You import data defining default field values in
the Default field values area of SM Administration 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 Default field values area of SM
Administration.
value The default value to set for the field. This can be a concrete
value or a variable.
To obtain a list of SAP Ariba-specific variables, export the sam

ple file from the Default field values area of SM
Administration.
You can also construct a variable based on any field in the ven
dor model using the syntax ${complete.Field.Name}.
For example, ${vendor.vendorInfo.anId}. The sam
ple default field values file includes the complete field names
for all fields in the vendor model in the name column.
The following example shows lines of the Default_properties.csv file that define simple defaults:
name,value
vendor.vendorInfoExt.categoryCode,2
vendor.companyCode.generalLedgerAccountReferenceID,33001
vendor.addressExt.email.validityPeriodStartDate,${current.date}
vendor.supplierGenericCustomField.ZS4ID,${vendor.vendorInfo.s4OrgSystemId}
You can also use the file to define default values for detail fields in an array class based on the value in the lookup
key field [page 342] and default values for one field conditionally values on other, unrelated fields [page 344].
 Caution
Do not set default values for any of the database fields in the vendor.contacts class. Default values in these
fields are not supported and might cause errors during supplier creation.
Related Information
Setting default values for vendor database fields [page 339]

Defining lookup key field-based default values for
company code, purchasing organization, and other
array fields
A specific syntax in the default field values CSV data import file allows you to define default values based on the
values in associated lookup key fields for some types of supplier data. When a user submits a questionnaire with a
lookup key value, the associated default field values are automatically added to the supplier record.
You can dynamically set default field values for some fields based on the value specified in an associated lookup
key field. You can only set defaults for fields that are in the same class as the lookup key field using this method.
The syntax for creating these definitions in the default field values CSV file is:
vendor.lookupKeyFieldName(lookupKeyFieldValue?).defaultingFieldName,defaultFieldValu
e
For example, to define a default value for vendor.purchasingOrg.organisationalCentreID based on the

vendor.purchasingOrg.purchasingOrganisationID lookup key, you can add a row like this::
vendor.purchasingOrg(P1?).organisationalCentreId,Center1
SAP Ariba Supplier Management solutions support setting defaults based on associated lookup key values for
most vendor database fields of type array, which can store multiple values for the same supplier in the same
database field. For example, a supplier can have multiple purchasing organizations. Each purchasing organization
has a number of associated data fields (for currency code, partner function data, discount terms code, and so on),
and the vendor.purchasingOrg.purchasingOrganisationID field is the lookup key for data in all other
vendor.purchasingOrg fields. You can specify default data sets for different purchasing organizations in the
default values CSV file like this:
vendor.purchasingOrg(P1?).partnerFunctions(PF1?).partyInternalID,92220
vendor.purchasingOrg(P1?).incotermsClassificationCode,100
vendor.purchasingOrg(P1?).incotermsTransferLocationName,SFO
vendor.purchasingOrg(P2?).partnerFunctions(PF1?).partyInternalId,43320
vendor.purchasingOrg(P2?).incotermsClassificationCode,400
vendor.purchasingOrg(P2?).incotermsTransferLocationName,DFW
In this example, when the supplier's purchasing organization ID is P1, the associated organizational center ID,
partner functions party internal ID, incoterms classification code, and incoterms transfer location name data
defaults to one set of values. When the supplier's purchasing organization ID is P2, those associated fields default
to a different set of values. Note that in the case of
vendor.purchasingOrg.partnerFunctions.partyInternalId, the supplier's purchasing organization ID
and SAP ERP partner function code values must both match the specified values to set the associated default party
internal ID.
The initial lookup key field value is set through a question in a supplier management project template survey
document. This question must specify a list of choices as acceptable answers, and that list of choices must
correspond to the lookup key field values you use to define the default field values in the CSV file. The question
must also be mapped to the lookup key field.
In this example, a template creator would create a question with a title such as Purchasing Organization,
choose List of Choices as the acceptable answer type, and define answers that match the purchasing organization
IDs in the default field values CSV file, including P1 and P2. They would also enter

vendor.purchasingOrg.purchasingOrganisationID in the Supplier Field Mapping field. This configuration
causes the question's answers to set the associated default field values.
 Tip
Although template creators can set up the questions that set these default values in any supplier form or
questionnaire in any supplier management project template (request, registration, qualification,
disqualification, and preferred supplier management), the types of data involved are almost always known and
used by only internal users at your company. Internal users can always update answers in the internal
questionnaire in the registration project, while questionnaires in other projects are closed after they are
submitted. In sites integrated with SAP ERP, updates from the ERP are automatically pushed to the supplier
request and both internal and external supplier registration questionnaires. Therefore, SAP Ariba recommends
that you create the questions that trigger defaults in the internal registration questionnaire or the supplier
request..
The following table lists the classes of vendor database fields that you can use to set default field values based on
lookup key fields:
vendor.bankInfos vendor.bankInfos.accountNumber
vendor.companyCode vendor.companyCode.companyCode
vendor.industrySector vendor.industrySector.industryClassificati
onSystemCode
vendor.purchasingOrg vendor.purchasingOrg.purchasingOrganisatio
nID
vendor.roleExt vendor.roleExt.roleCode
vendor.subRange vendor.subRange.vendorSubrangeCode
vendor.taxExt vendor.taxExt.vendor.taxExt.taxIdentificat
ionNumberTypeCode
vendor.text vendor.text.textTypeCode
vendor.vendorExtIdentification vendor.vendorExtIdentification.partyIdenti
fierTypeCode
vendor.vendorPCardIssuerAPIs vendor.vendorPCardIssuerAPIs.paymentCardIs
suerPartyInternalID
In the user interface, the data in most of these fields is displayed on the ERP Info tab of the Overview tile in supplier
360° profiles. Note that to view purchasing organization and company code data on the ERP Info tab of the
Overview tile in supplier 360° profiles, you must be a member of the SM Ops Administrator or SM ERP
Administrator group. Members of the SM Ops Administrator group can also view bank details there.

Defining default values based on condition fields
You can add up to three additional columns to the default field values CSV data import file to define default field
values based on the values in other fields. When a user submits a questionnaire with values that meet a condition,
the associated default value is automatically added to the supplier record.
You can dynamically set default field values for any field based on the values in up to three other fields, which
function as conditions. To do so, you add up to three columns in the default field values CSV file, specifying the
condition field names as the headers for those columns. You then use parentheses to define the default value to set
for each set of conditional values:
name,value,conditionField1,conditionField2,conditionField3
defaultingFieldName(defaultValue),defaultValue,condition1,condition2,condition3
For example, you might assign company codes to suppliers based on their location. You can define default
company codes based on the country and state fields in supplier addresses like this:
name,value,vendor.address.countryCode,vendor.address.state
vendor.companyCode(CC1),CC1,USA,NY
vendor.companyCode(CC2),CC2,USA,NJ
In this example, if the supplier's address is in New York state in the US, it is automatically assigned company code
CC1, while if the supplier's address is in New Jersey, it is automatically assigned company code CC2.
The condition values are set through questions in a supplier management project template survey document. This
question must have a defined set of answers, whether it is a list of choices as acceptable answers or master data
such as region or department. The answer set must correspond to the condition values you use to define the
default field values in the CSV file. The questions must also be mapped to the condition fields.
In this example, a template creator would create a question of type Address in the supplier request and enter
vendor.address in the Supplier Field Mapping field. They do not have to define answers for the state and
country questions in the address question, since those values are defined in site master data. The
vendor.address field mapping automatically maps the state question to vendor.address.state and the
country question to vendor.address.countryCode. This configuration causes the question's answers to set the
associated default field values.
The three condition fields in the default field values CSV file can function either together or independently. In the
above example, the supplier's state and country must both match a defined default company code to set the
default code. However, you can use each supported condition column to set an unrelated default for a separate
field, or you can use all three condition columns together to set the default for the same field. If you do not want to
use a condition for a particular field, leave that condition column blank for that row.

Topics about customizing supplier management
notifications
Topics about customizing project-level supplier management notifications [page 346]
How to customize the questionnaire invitations sent to suppliers [page 357]
How to add email template tokens [page 359]
How to add translated text to email notification templates [page 360]
About customizing supplier management

notification templates
Email notification templates define the content of notifications for various activities in supplier management
projects. You can customize these notifications.
There are two different types of supplier management notification templates:
● Project-level notifications, which you manage in the Project Manager Project Email Templates task in
Ariba Administrator. These notifications are sent to stakeholders when a user creates a supplier management
project, needs to complete a To Do or approval task, and when other project-related activities occur.
● Questionnaire invitations to suppliers, which you manage in the Event Manager Messaging
Templates task in Ariba Administrator. (External (supplier-facing) supplier management questionnaires
share some basic infrastructure with sourcing events.) These notifications are sent to suppliers and invite them
to respond to your questionnaire. They automatically include
The Project Email Templates task includes a specific set of project-level notification templates that are tailored to
supplier management workflows. There are also standard, generic notifications for projects and tasks that you can
apply to supplier management projects. This section describes the notifications that are specific to supplier
management projects. For details on generic project-level notifications, see the Managing project email
notifications guide.
 Note
Supplier management questionnaire approval tasks use the specific approval task notification templates for
each supplier management project type in addition to the generic notifications for all approval tasks. For
example, there are specific notifications for approval tasks for supplier registration questionnaires. You can
customize these generic notifications or disable them altogether.
You can customize email notifications by:
● Modifying 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:

Topics about customizing supplier management notifications PUBLIC 345
○ Font changes
○ Bold, italic, and underlined text
○ 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 pre-configured with email notification templates 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 be 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.
 Note
Notifications sent to suppliers must always clearly identify your company as the sender. You can use the
[SYSTEM_CORPORATE_NAME] email token (in project-level email templates) or the
[SPONSOR_CORPORATE_NAME] email token (in questionnaire invitations) to automatically insert your
company's name into the notification.
 Tip
By default, approval task email notifications do not include any comments that approvers might have added
during the approval process. You can add those comments to approval task notifications using the
[TASK_COMMENT_TEXT] email token.
Related Information
How to customize project-level email templates [page 347]

How to customize the questionnaire invitations sent to suppliers [page 357]
Topics about customizing project-level supplier

management notifications
How to customize project-level email templates [page 347]
How to delete customized project-level email templates [page 348]
Notifications related to supplier requests [page 349]

346 PUBLIC Topics about customizing supplier management notifications
Notifications related to supplier registration projects [page 350]
Notifications related to supplier qualification projects [page 352]
Notifications related to preferred supplier status changes [page 352]
Notifications related to supplier disqualification projects [page 353]
Notifications related to modular supplier management questionnaires [page 354]
Notifications related to certificate questions in modular supplier management questionnaires [page 355]
Notifications related to supplier management project template upgrades [page 355]
Supplier management-specific notifications related to tasks [page 356]
Other supplier management notifications [page 357]
How to customize project-level email templates
You customize project-level 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:
● Project Email Templates Administrator

● Contract Administrator
● Project Administrator
● Customer Administrator
● A group with the Project Email Templates Administrator role
You must be a member of the Template Creator or Customer Administrator group to edit email templates in
survey documents in project templates.
You must be the project owner to edit email templates in survey documents in individual projects, and the event
owner to edit email templates in individual sourcing events.
Context
 Note
Notifications sent to suppliers or other third parties must always clearly identify your company as the sender.
You can use the [SYSTEM_CORPORATE_NAME] email template token (in project-level email templates) or the
[SPONSOR_CORPORATE_NAME] email template token (in assessment invitations) to automatically insert your

Procedure
1. Click Manage Administration .
2. Choose Project Manager Project Email Templates Project Manager.

3. Select the template you want to edit and click Edit.
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.
How to delete customized project-level email templates

You can delete a customized email template for a specific project type and revert to the default email template.
Prerequisites


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.
Procedure
1. Choose the template you want to delete.

2. Click Delete to open the Delete Email Template Confirmation window.
3. Click OK.
Notifications related to supplier requests
SAP Ariba sends notifications for various activities related to supplier requests.
● Submitted: Your request to add <supplier name> as a supplier

Sent to the user who submitted the internal supplier request.
● <Buyer name> is reviewing your registration request
Sent to the supplier who submitted the external supplier request.
● Action needed: Approve request to add <supplier name> as a supplier
Sent 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 internal supplier request if the request is finally denied, and includes any
comments the approver made to explain the denial.
● Declined: your request to add <supplier name>
Sent to the requester and all active team members of the supplier request project, including approvers, when
SAP ERP MDG-S finds an existing duplicate supplier for the current supplier request and the newly requested
supplier is therefore marked as an inactive duplicate. The notification includes a link to 360° profile of the
existing supplier that MDG-S has matched to the duplicate request. This notification is only sent when the
supplier request is configured for manual approval; it is not sent if the supplier request is configured for auto-
approval.
● <Buyer name> declined your registration request
Sent to the supplier who submitted the external supplier request if the request is finally denied, and includes
any comments the approver made to explain the denial.

Related Information

Notifications related to supplier registration projects
SAP Ariba sends notifications for various activities related to supplier registration projects.
The following notifications are defined by project email notification templates:
● 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
questionnaire.
● 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.
● Action needed: Please update <questionnaire name> for <buyer name>
Sent to suppliers who have completed registrations to remind them to update an external registration
questionnaire at the intervals specified in questionnaire update reminder settings in the supplier registration
project template. Suppliers receive a separate instance of this notification for each external questionnaire in
their completed registration that has been set up to issue update reminders.
● Action needed: Approve an update to <questionnaire name> for <supplier name>
Sent to approvers when a supplier submits an update to an external registration questionnaire.
● Action needed: <buyer name> requires additional information for <questionnaire name>
Sent to the supplier who submitted a registration questionnaire update when an approver requests additional
information.
● Approved: Updates to <questionnaire name>
Sent to the supplier who submitted a registration questionnaire update when approvers have finally approved
the update.

The following notifications are defined by event messaging templates in Event Manager Messaging
Templates and in individual questionnaire survey documents in the supplier registration project template:
● For registrations that invite the supplier to fill out external questionnaires:
○ 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 (for automatic invitations) or the supplier contact invited to register (for manual invitations).
Suppliers receive a separate instance of this notification for each external questionnaire in their
registration. This notification is sent both for new registrations where the supplier is invited to register and
for existing internal registrations to which the supplier is invited to participate.
○ Action needed: Complete your registration for <buyer name>
Sent to suppliers who have not yet submitted an external registration questionnaire that has been set up to
issue reminders at the times specified in its due date reminder settings in the template survey document.
Suppliers receive a separate instance of this notification for each external questionnaire in their
registration that they have not yet submitted and that has been set up to issue reminders.
There are two templates for both these notification: one for suppliers who are new to SAP Ariba, which
contains a link for registering on Ariba Network before opening the questionnaire, and one for suppliers who
already have Ariba Network accounts, which contains a link for logging into their account and opening the
questionnaire.
 Tip
If the self-service configuration parameter Enable configurable default sender for supplier invitations is
enabled in your site, you can use the [CUSTOM_SENDER_NAME] email template token to insert the custom
sender name or, if the feature for specifying a requester during registration invitations (SM-20904) is also
enabled in your site, registration requester into both of these notifications.
● For internal registrations, where internal users complete registration questionnaires on behalf of the supplier:
○ Action needed: Submit a registration questionnaire for <supplier name>
Sent to the internal user who has been specified as the recipient of an external registration questionnaire in
an internal supplier registration.
Related Information


Notifications related to supplier qualification projects
SAP Ariba sends notifications for various activities related to supplier qualification projects.
● Action needed: Fill out qualification questionnaire to become a qualified supplier with <buyer name>
Sent to the supplier's main 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: Qualification for <supplier name> is expired
Sent to the qualification project's team members on the qualification's expiration date if it has one.
● Notification: <supplier name> is eligible for requalification with <buyer name>
Sent to the qualification project's team members on the date specified as the end of the requalification period,
if the qualification has one.
Related Information

Notifications related to preferred supplier status changes

SAP Ariba sends notifications for various activities related to preferred supplier management projects.
● 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.
Related Information

Notifications related to supplier disqualification projects
SAP Ariba sends notifications for various activities related to supplier disqualification projects.
● Action needed: Review disqualification for <supplier name>

Sent to the users in the disqualification questionnaire 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.
Related Information


Notifications related to modular supplier management

questionnaires
SAP Ariba sends notifications for various activities related to modular supplier management questionnaires.
● Action needed: Provide additional information to <buyer name>

Sent to the supplier contact when an approver has denied the questionnaire but allowed the supplier to
resubmit answers, and includes any comments the approver made to explain the denial.
● Approved: <questionnaire title> submitted to <buyer name>
Sent to the supplier contact when the questionnaire is finally approved.
● Declined: <questionnaire title> submitted to <buyer name>
Sent to the supplier contact when the questionnaire is finally denied.
● Your <questionnaire title> with <buyer name> expires on <project expiration date>
Sent to the supplier contact before the questionnaire's expiration date. This notification is not automatic. It is
only sent if a template creator in your site has specified that the questionnaire expires in the template survey
document's Supplier Management rules. The template creator also specifies the expiration schedule and the
amount of time before the expiration date this notification is sent there.
● Your <questionnaire title> with <buyer name> has expired
Sent to the supplier contact when the questionnaire's expiration date has elapsed and the supplier has not
edited and resubmitted the questionnaire. This notification is not automatic. It is only sent if a template creator
in your site has specified that the questionnaire expires in the questionnaire template survey document's
Supplier Management rules. The template creator also specifies the expiration schedule there.
● <questionnaire project name> of <supplier name> expires on <expiration date>
Sent to the internal user who sent the questionnaire before the questionnaire's expiration date. This
notification is only sent if a template creator in your site has specified that the questionnaire expires in the
template survey document's Supplier Management rules. The template creator also specifies the expiration
schedule and the amount of time before the expiration date this notification is sent, and can specify that this
notification also be sent to the primary supplier manager and/or members of the Project Owner group as well
as the user who sent the questionnaire.
● <questionnaire project name> of <supplier name> has expired
Sent to internal users when the questionnaire's expiration date has elapsed and the supplier has not edited and
resubmitted the questionnaire. This notification is only sent if a template creator in your site has specified that
the questionnaire expires and set an expiration schedule in the template survey document's Supplier
Management rules. The template creator can specify that this notification also be sent to the primary supplier
manager and/or members of the Project Owner group as well as the user who sent the questionnaire.
● Action needed: <task title>
Sent to internal users when the approval node to which they are assigned becomes active in the approval flow.
 Note
The questionnaire invitation notification and any reminders related to its due date that are sent to the supplier
contact, if enabled, are defined in the customized messages in the questionnaire survey document.

Notifications related to certificate questions in modular
supplier management questionnaires
SAP Ariba sends notifications for various activities related to individual certificate questions in modular supplier
● Your <certificate type> with <buyer name> expires on <certificate expiration date>
Sent to the supplier contact before the certificate's expiration date. The supplier specifies the expiration date in
the answer to the certificate question, and a template creator in your site specifies the amount of time before
the expiration date this notification is sent in the settings for the certificate question.
● Your <certificate type> with <buyer name> has expired
Sent to the supplier contact when the certificate expiration date they provided has passed.
● <certificate type> of <supplier name> in <modular questionnaire project template title> expires on
<expiration date>
Sent to the internal user who sent the questionnaire that includes the certificate before the certificate's
expiration date. A template creator in your site can specify that this notification also be sent to the primary
supplier manager and members of the Project Owner group in the settings for the certificate question; the
template creator also specifies the amount of time before the expiration date this notification is sent. The
supplier specifies the expiration date in the answer to the certificate question.
● <certificate type> of <supplier name> in <modular questionnaire project template title> expired on
<expiration date>
Sent to the internal user who sent the questionnaire that includes the certificate question when the certificate's
expiration date has passed and the supplier has not updated and resubmitted the certificate with a later
expiration date. A template creator in your site can specify that this notification also be sent to the primary
supplier manager and members of the Project Owner group in the settings for the certificate question. The
supplier specifies the expiration date in the answer to the certificate question.
Related Information

Notifications related to supplier management project

template upgrades
SAP Ariba sends the following notifications related to supplier management project template upgrades.
● <buyer name> has updated a questionnaire and requires your attention

Sent to the supplier's primary supplier contact when a customer administrator upgrades their existing supplier
registration project to the latest published version of the template and includes the notification option in the
upgrade. The body of the notification email includes the questionnaire name and a details with the message
the administrator specified during upgrade to describing the nature of the changes. A separate instance of this
notification is sent for each of the supplier's registration questionnaires regardless of whether or not they were
modified in the upgrade.
● Project state update: <supplier registration project ID > - Supplier Registration for <supplier name>
Sent to the project owner when a customer administrator upgrades a supplier registration project they created
to the latest published version of the template to notify them that the previous version of the project (the one
that used the previous template version) has been archived.
 Note
Project owners of supplier registration projects can be category or supplier managers who are otherwise
unfamiliar with underlying project architecture and versioning. The default text in this notification assumes
familiarity with project architecture and versioning. SAP Ariba recommends customizing that text to make
sure that the recipients understand why it was sent and making the customization specific to supplier
registration projects.
Related Information
Supplier management-specific notifications related to

tasks
SAP Ariba sends supplier management-specific notifications for some project tasks.
The following task notification is sent only for approval tasks in supplier request, registration, qualification,
disqualification, and preferred supplier management projects:
● One or more tasks in <supplier management project name> are missing approvers
Sent to the user who created a supplier request, registration, qualification, disqualification, or preferred
supplier management project when one or more approval nodes in one or more approval tasks in the project is
missing an approver. The project cannot proceed until the project owner or another user with the appropriate
permissions adds approvers to those nodes.
Related Information


Other supplier management notifications

SAP Ariba sends the following other notifications related to supplier management activities.
● Action needed: Integration confirmation failure messages for supplier data on <date>
Sent to members of the SM ERP Administrator group at approximately 1am PST every day with a list of the SM
vendor IDs and names of every supplier associated with a confirmation failure message received from an
integrated ERP system in the previous 24 hours.
How to customize the questionnaire invitations sent

to suppliers
You customize the questionnaire invitations sent to suppliers by editing the email notifications associated with the
Prerequisites
You must be a member of the Customer Administrator or Event Administrator group to customize the
questionnaire invitations sent to suppliers.
To include your company's logo in registration questionnaire invitations, the you must enable the self-service site
configuration parameter Use custom logo and footer for emails sent to
suppliers( Application.EnableCustomEmailLogoAndFooter) must be enabled in your site, and one of your
company's customer administrators must upload the logo on the Custom Email tab of the Customization
Manager Branding Settings task in Ariba Administrator. See the Common data import and administration
guide for SAP Ariba Strategic Sourcing and Supplier Management solutions for details.
Context
Supplier management questionnaires share some underlying infrastructure with sourcing events, and you
customize their supplier invitations in the Event Manager Messaging Templates task in Ariba
Administrator. Although you can also customize invitations in individual questionnaire template survey documents,
SAP Ariba recommends using the Messaging Templates task. Depending on your company's solution and the
types of supplier management projects available in your site, you can use this task to customize supplier invitations
for registration, qualification, and modular supplier management questionnaires.

Suppliers answer questionnaires by logging into Ariba Network for Suppliers, filling out the questionnaire, and
submitting their answers. If the supplier does not already have an Ariba Network for Suppliers account, they must
create one at this time.
The external (supplier-facing) questionnaires in supplier management projects use the following two email
notification templates for supplier invitations:
● Publish Event; Invitation for participants, which is sent to suppliers who have already registered with Ariba
Network for Suppliers.t
● Invitation for participants who have not used Ariba before, which is sent to suppliers who have not
registered with Ariba Network for Suppliers, and includes information about the registration requirement.
In sites created after the SAP Ariba April 2018 release, registration invitation templates automatically include a
SUPPLIER_REG_DEADLINE token that displays the deadline by which the supplier must respond to the invitation
before the temporary password generated by the invitation expires; a RECIPIENT_NAME token that specifies the
name of the invited supplier contact; and a PASSWORD_URL token that automatically renders as a link that the
invited contact can click to create a new Ariba Network for Suppliers account. The deadline displayed by
SUPPLIER_REG_DEADLINE is defined by the Application.Password.NewPasswordTokenLifeSpan site
configuration parameter. The SUPPLIER_REG_DEADLINE and RECIPIENT_NAME tokens are not available in sites
created before the SAP Ariba April 2018 release.
 Tip
Make sure that when you complete your customized invitations, the invitation for existing suppliers still
includes the [SITE_URL] email token, which is automatically rendered as a link that the invited supplier
contact can click to log into their existing Ariba Network for Suppliers account, and that the invitation for new
suppliers still includes the [PASSWORD_URL] email token, which is automatically rendered as a link that the
invited supplier contact can click to create a new Ariba Network for Suppliers account. The supplier contact
must use one of these links to access your questionnaire.
Procedure
1. On the dashboard, choose Manage Administration .
2. Choose Event Manager Messaging Templates .

3. Choose one of the two supplier invitation templates and click Edit.
4. Make changes or additions to the text and add formatting to meet your needs.
5. (Optional) Add or remove email template tokens. To remove email template tokens, delete the text and the
square brackets.
6. (Optional) Add any translations.
7. Click Save.
Related Information


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 be
generated by the system for the email message itself, such as the recipient’s email address.
Prerequisites

You must be a member of the Template Creator or Customer Administrator group to edit email templates in
survey documents in project templates.
You must be the project owner to edit email templates in survey documents in individual projects, and the event
owner to edit email templates in individual sourcing events.
Context
Email template tokens are delimited by square brackets ([ ]). For example, the text [Workspace.Title] 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.
 Note
Notifications sent to suppliers or other third parties must always clearly identify your company as the sender.
You can use the [SYSTEM_CORPORATE_NAME] email template token (in project-level email templates) or the
[SPONSOR_CORPORATE_NAME] email template token (in assessment invitations) to automatically insert your
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.
○ 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 an Email Template for the Content or Choose an Email Template for the
Subject 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.
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.

○ To provide translations of the email subject, below the Subject field, click Translations.
○ To provide 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.

Topics about issuing mass registration
invitations to suppliers
Issuing mass registration invitations to suppliers [page 362]
How to issue a mass registration invitation to suppliers [page 363]
How to monitor the progress of mass registration invitations [page 365]
Mass registration invitation data import file format [page 366]
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.
Mass invitations are a useful tool for onboarding large numbers of suppliers to SAP Ariba Supplier Management
solutions. You define separate waves or groups of suppliers and upload a list of suppliers to include in each wave.
You can then monitor the waves to see how many suppliers have responded to the invitation and submitted
registration questionnaires.
You can choose to establish a fulfillment relationship in addition to a sourcing relationship with suppliers that you
invite to register using a mass invitation. The presence of a value in the Fulfillment column of the
MassInvite.csv indicates that a fulfillment relationship should also be established for the supplier's ERP Vendor
ID
Supplier registration projects include an Is Legacy field. If a supplier is invited to register using a mass invitation,
they are flagged as a legacy supplier. You can use this setting to create different registration processes for legacy
and non-legacy suppliers [page 167].
Integration settings also allow you to control how the registration data generated by mass invitation waves is
synchronized with an integrated ERP system. See the SAP Ariba Cloud Integration Gateway documentation for
details.
Related Information

Mass registration invitation data import file format [page 366]
How to download the vendor onboarding report to track supplier registration and qualification progress [page 367]

362 PUBLIC Topics about issuing mass registration invitations to suppliers
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.
The primary supplier manager should be part of Supplier Registration Manager group or SM Ops Administrator
group to invite mass invite suppliers.
You must import supplier contact data for the suppliers you want to invite before issuing a mass registration
invitation.
You must have set up and published the supplier registration project template in your site.
In order to specify the list of suppliers to include in a mass registration invitation wave, you must add their ERP
vendor IDs to a Mass registration invitation data import file format [page 366] file. These suppliers must already
exist in the site.
Context
Suppliers created individually through approved supplier requests are invited to register individually, either
automatically or manually depending on site configuration. However, when you are getting started with SAP Ariba
Supplier Management solutions, or whenever you create a large number of suppliers using data import, supplier
mass registration allows you to automatically send invitations to a specified list of suppliers.
When you import supplier data (either existing SAP Ariba suppliers or suppliers from outside SAP Ariba), they are
created in the database with Not Invited status. When you import supplier preferred or qualification data, the
suppliers are associated with specific commodities and regions and have a preferred or qualified status, but still
have the Not Invited status because they have not completed the registration process. When a user at your
company requests a supplier and the supplier request is approved, the supplier is created in the database with Not
Invited status. Any supplier with Not Invited status can be included in a mass registration invitation.
You can create distinct waves of invitations to onboard suppliers in a controlled way. For example, you can invite the
suppliers from one region in the first wave, another region in the second wave, and so forth. Wave end dates are for
informational purposes only. The invitations are all sent after you import the list of suppliers and click Send Invite,
and invited suppliers can fill out the registration questionnaire as long as it is still open, regardless of the wave end
date. You cannot schedule waves in advance.
If your site uses multiple external (supplier-facing) registration questionnaires, you can choose which questionnaire
to use for the wave. You can only send one questionnaire with a wave.
 Caution
Sending registration invitations for a mass invitation wave creates a supplier registration project for every
supplier in that wave. Before you start sending mass invitations, make sure that your organization's supplier

Topics about issuing mass registration invitations to suppliers PUBLIC 363
registration project template is finalized and published. While you can upgrade existing supplier registration
projects to the latest version of the template, it can take multiple days to upgrade a large number of projects on
the same template version. Starting mass invitation waves using a finalized project template means that the
registration projects for mass-invited suppliers include your organization's complete current questionnaires
and workflow from the start, and you only need to perform template upgrades for subsequent changes.
Procedure
1. On the dashboard, click Manage SM Administration .

2. Click Mass invite.
○ To create a new invitation wave, choose Create new wave from the Choose a wave dropdown menu and
enter a name for the wave.
○ To use an existing wave, choose it from the Choose a wave dropdown menu
4. Specify an end date for the wave by clicking the calender icon (calender icon) and choosing a date.
5. Click Browse file and navigate to the CSV file that contains the list of suppliers you want to include in the
current mass registration invitation wave.
6. Click Upload spreadsheet
The Summary area displays the results of your upload. If your file contained errors, it shows you the number of
suppliers with missing contacts, number of suppliers with invalid vendor IDs, and number of suppliers that are
already registered, and you can click Download all errors to download a list of all errors in the file.
7. If your file contained errors, correct them and then click Re-upload to upload the corrected file from the same
location.
8. (Optional), if your site uses multiple external (supplier-facing) registration questionnaires, choose a
questionnaire from the Choose the questionnaire to send dropdown menu.
9. Click Send invitation.
Results
The registration invitation is sent to all suppliers in the current wave.
Next Steps
Use the Track history tab to monitor the progress of mass registration invitation waves. Once the current wave has
achieved the results you want, you can create additional waves of mass registration invitations as needed.

Related Information
How to monitor the progress of mass registration

invitations
Once you have sent a wave of mass registration invitations, you can monitor the number of suppliers who have
answered and been approved for registration.
Prerequisites
You must be a member of the SM Ops Admin group to monitor the progress of mass registration invitations in SM
Administration.
Context
The Track history tab displays the name of the invitation wave, the number of suppliers invited in the wave, the
date the invitation was issued, and the number of suppliers in the wave whose registrations have been approved.
From there, you can download a CSV file that contains your mass registration invitation history. The CSV file
includes important additional information: a list of all of the suppliers invited in each wave, including their ERP
vendor IDs, and their current registration status. This file shows not only the suppliers in the wave who have been
invited or successfully registered, but also those who are in the process of registering and who have had their
registrations denied. You can provide this file to interested parties in your company such as category or supplier
managers who do not have access to SM Administration.
Procedure
1. On the dashboard, click Manage SM Administration .

2. Click Mass invite.
3. Click the Track history tab.
4. (Optional) Perform one of the following actions:
○ To update the data on the tab (for example, to show a newly created wave or the most recent number of
registered suppliers), click Refresh.
○ To download your mass invitation registration history as a CSV file, click Download and save the file to the
location of your choice.

Topics about issuing mass registration invitations to suppliers PUBLIC 365
Related Information
Mass registration invitation data import file format

Mass registration invitations use a CSV file import to specify the list of suppliers you want to automatically invite to
register all in the current wave.
If you want to assign primary and alternate supplier managers to the suppliers in an invitation wave, you must
import the data file that defines managers for those suppliers before importing the mass invitation data. Primary
supplier managers are for information only; if any suppliers in the invitation wave do not have a primary or alternate
supplier manager, the user who sends the mass invitation is assigned as the primary supplier manager.
The mass registration invitation data import task reads from a CSV file that contains the following fields:
Field Definition Required


in Supplier.csv.
Fulfillment Determines whether a fulfillment rela No

tionship should be established for the
supplier's ERP Vendor ID, in addition to
the sourcing relationship.
Related Information

Topics about performing administrative tasks
for supplier management
How to download the vendor onboarding report to track supplier registration and qualification progress [page
367]
Topics about inactivating and reactivating suppliers [page 368]
How to cancel a qualification project that is in progress [page 370]
How to download the vendor onboarding report to

track supplier registration and qualification progress
You can track your suppliers' registration and qualification progress with the vendor onboarding report, a delimiter-
separated value file that shows their latest registration and qualification statuses and when those statuses were
achieved.
Prerequisites
To view the Reports workspace and download the vender onboarding report, the SM Reports feature must be
enabled. Contact SAP Ariba support to enable this feature.
To download the vendor onboarding report, you must be a member of the SM Ops Administrator group.
Context
The vendor onboarding report shows the latest status for each supplier registration and qualification along with the
timestamp for that latest status update. Data for qualifications includes the commodity, region, and department of
the qualification; qualifications are only available in SAP Ariba Supplier Lifecycle and Performance. You can
download the report as a comma-separated values (CSV) file, the default export delimited, or choose from other
common delimiters such as the semicolon (;). When you generate the report, you specify the range of status
update dates to include in the report up to a maximum range of three months and schedule it to run. After it has
finished running, you can download it to the location of your choice and either open it or transfer it to a third-party
system for processing.
The status update timestamp in the report allows you to identify and track stalled registrations and qualifications.
For example, you can use the report to see all of the registrations in Invited status where the registration invitations
(indicated by the change from Not Registered to Invited status, the last status change) were issued three to nine

Topics about performing administrative tasks for supplier management PUBLIC 367
months ago and follow up with those suppliers. Or you can see all of the registrations with a change to Pending
Approval status in the last three months to identify registrations that have not been approved or denied in a timely
fashion and that might indicate internal bottlenecks in your organization's approval processes.
The Reports workspace shows previously generated reports and their date ranges, allowing you to generate a new
report with a starting date right after the end date of the previous report. Currently, the only report available in this
workspace is the vendor onboarding report.
Procedure

2. Click Reports.
3. (Optional) Perform any of the following actions:
○ On the CSV Delimiter dropdown menu, choose the value delimiter to use in the report file.
○ Enter a name for the report file in the Report name field.
4. For the From and To dates, use the calendar and time choosers to specify the start and end dates and times for
the range of status update timestamps to include in the generated report.
5. Click Schedule.
SAP Ariba Supplier Management solutions start generating the report and a new entry for it appears at the top
of the generated reports table. The amount of time it takes to generate a report depends on several factors,
including the amount of data included in the specified date range.
6. Click Refresh report details to see if the report is ready to download, or navigate away from the Reports
workspace and return later. When the report is ready to download, it shows a report status of Created.
7. Click the download icon () and save the report file to the location of your choice.
Topics about inactivating and reactivating suppliers
Inactivating and reactivating suppliers [page 368]
How to view and manually reactivate inactive suppliers [page 369]
Inactivating and reactivating suppliers

Once you inactivate a supplier, users in your site can no longer work with them. Typically, you inactivate your
suppliers when you are sure you don't want to work with them any more.
SAP Ariba Supplier Management solutions never outright delete suppliers. Instead, they mark deleted suppliers as
inactive. Inactivation is a more permanent action than a block. Inactive suppliers:
● Are no longer visible in supplier search results, including searches for available participants for sourcing events
and available suppliers for contract creation.

368 PUBLIC Topics about performing administrative tasks for supplier management
● Cannot be edited or worked with. Supplier profiles for inactive suppliers become read-only, and users can no
longer edit internal registration questionnaires or initiate processes such as registration, qualification, or
preferred supplier designation. Users also cannot edit existing preferred levels. Tasks associated with those
processes also become read-only; users can no longer complete them.
 Note
Although a supplier is never outright deleted, after a supplier has been inactive for 30 days, SAP Ariba does
permanently delete all of the data stored for it in the contact, bank, and tax fields in the database. If you
reactivate a supplier before the 30 days has elapsed, the reactivated supplier record includes any contact,
bank, and tax data you have collected for it. If you reactivate a supplier after the 30 days has elapsed, the
contact, bank and tax data has been deleted and you must re-collect it.
Supplier inactivation and reactivation can occur in several different ways in SAP Ariba Supplier Management
solutions:
● A customer administrator can use the Suppliers data import/export task to import a supplier data in a CSV file
with the active column set to TRUE (active) or FALSE (deactivated). Blank values in this column are assumed
to be TRUE.
● If a supplier is marked with a delete indicator in an integrated SAP ERP system, and the supplier has already
been synchronized with the ERP, SAP Ariba Supplier Management solutions automatically inactivates that
supplier. If the delete indicator is removed in SAP ERP, SAP Ariba Supplier Management solutions reactivates
the supplier.
● If the internal question includes a question about inactivating or deleting the supplier, a user answering the
question inactivates the supplier. A template creator can also flag suppliers for deletion at the individual
purchasing organization or company code level; these flags to not inactivate the supplier in SAP Ariba Supplier
Management solutions. See Enabling users to inactivate suppliers by flagging them for deletion in
questionnaire answers [page 174] for details.
● If a supplier is inactivated, a customer administrator can manually reactivate them in SM Administration.
 Note
synchronization occurs, SAP Ariba Supplier Management solutions cannot receive or send the delete indicators
that inactivate or reactivate a supplier.
How to view and manually reactivate inactive suppliers
Inactive suppliers do not show in search results. You can view and manually reactivate them in SM Administration.
Prerequisites
To view and manually reactivate inactive suppliers in SM Administration, you must be a member of the SM Ops

Context
Typically, companies make suppliers inactive when they no longer want to do business with them for one reason or
another. Users cannot add inactive suppliers to sourcing events or contracts, and can't initiate processes for
qualification and preferred designation for them. However, inactive suppliers remain in the database and retain
existing registration information, unexpired qualifications, and preferred supplier designations. If your company
decides to start doing business with a supplier again, you can reactivate them.
Procedure

2. Click Inactive Suppliers.
3. To locate one or more specific suppliers, perform one of the following actions:
○ Click a column head to sort the supplier list by that column.

○ Click the filter icon (), enter a partial or full ID in the search field, and check one or more IDs to filter the
supplier list by specific SM vendor IDs or ERP vendor IDs.
○ To view the inactive supplier's 360 ° profile, click its SM vendor ID.
○ To reactivate the supplier, click Reactivate.
Results
Reactivated suppliers show up once more in search results, and users can edit them, add them to sourcing events
and contracts, and initiate qualifications and preferred supplier designation processes for them.
How to cancel a qualification project that is in

progress
If project-based qualification has not yet approved or rejected, you can cancel it by deleting the underlying
qualification project. Cancellation allows a user to start a new qualification project for the same combination of
commodities, regions, and departments.
Prerequisites
To cancel an in-progress qualification project, you must be a member of the SM Ops Administrator group.

You must know a supplier's SM Vendor ID to search for and cancel their in-progress qualification projects. SM
Vendor IDs are available in supplier 360Ҙ profiles and in the Suppliers data export in SM Administration.
Context
When a qualification manager starts a qualification for a specific commodity, region, and department, SAP Ariba
Supplier Lifecycle and Performance creates a qualification project for that combination. If an approver denies the
qualification, the qualification project with that commodity, region, and department combination remains in the
supplier's profile and prevents creation of a qualification for the same combination.
You can cancel an existing qualification project that is in Qualification Started, In Qualification, Pending
Qualification Resubmit or Pending Qualification Approval qualification status by deleting the qualification
project. Once the qualification is deleted, a qualification manager can create a new qualification project for the
same combination of commodity, region, and department.
 Note
Qualification statuses set by data import are not associated with qualification projects, and can only by
canceled using a data import that updates their qualification status to Cancelled.
Procedure

2. Click Cancel qualification.
3. Enter the supplier's SM Vendor ID and press Enter or click the search icon ().
4. In the list of available qualification projects, locate the project you want to cancel and click the delete icon ().
5. Click Continue to confirm that you want to cancel the project.
Results
The qualification is now canceled and the underlying qualification project is flagged as deleted in the database,
meaning that:
● The qualification no longer displays on the Qualification tile in the supplier's 360° profile and the Supplier
Management dashboard or in supplier search.
● Approvers attempting to access the qualification approval page using links in notification emails, or attempting
to submit approvals, see a message letting them know that the qualification has been canceled.
● Suppliers attempting to access or submit the qualification questionnaire on Ariba Network for Suppliers can no
longer access the questionnaire and see a message letting them know that the qualification is canceled.
● Qualification managers can start new qualifications based on the same commodity, region, and department
combination as the previously canceled qualification.

If the canceled qualification is the only one that had been started for the supplier, the supplier's overall qualification
status reverts to Qualification Not Started.
Related Information
How to manage access to the advanced view of

supplier management projects
The Advanced view link in supplier management projects allows users with the appropriate permissions to perform
advanced actions such as reopening questionnaires or editing project groups and tasks. You can enable or disable
this link for specific project types and control who has access to it.
Prerequisites
To manage access to the Advanced view link in supplier management projects, you must be a member of the SM
Ops Administrator group.
This configuration option only applies to advanced view links in the new supplier 360° profile. There is no way to
disable access to the advanced view in the classic supplier 360° profile.
Context
The Advanced view link allows users with the appropriate permission to edit project components such as tasks
and the team. Some of the most common uses of the advanced view include:
● Adding approvers to approval flows. Some organizations find it useful to provide project owners with the
flexibility to add approvers to approval tasks on questionnaires, or to the project groups that are already
defined as approvers, to handle cases where the template-defined approval flow does not include all relevant
stakeholders.
● Reopening closed questionnaires. If an approver denies a registration or modular supplier management
questionnaire, it closes permanently and is no longer available for updates unless a user manually monitors
and reopens it in the advanced view. Note that there is no other way to reopen the questionnaire in this
situation.
You can enable or disable the advanced view for the following types of supplier management projects:

Project Default setting
Modular Questionnaire Off
This setting is only available in sites that use modular supplier

Registration On
Qualification On
Supplier Request On
Disqualification On
Your advanced view configuration for a project type applies to all projects of that type in your site. You cannot
enable or disable the Advanced view link in individual projects.
If you enable the Advanced View link for a project type on your site, project owners, members of the SM Ops
Administrator group, and members of the SM ERP Administrator group can access this link. If you also enable the
Control access by group setting, only members of the SM Advanced View Access group can access the link.
Procedure

2. Click Advanced view configuration.
3. Slide the toggle for a project type to enable or disable the Advanced view link in all projects of that type.
4. (Optional) Slice the toggle for the Control access by group setting to enable or disable it.
Results
If you have enabled the advanced view for a project type, users with the appropriate permission see the Advanced
view link on project pages.

Topics about managing ERP integration
 Note
For information on setting up integration with SAP ERP or SAP S/4 HANA, see SAP Ariba cloud integration
documentation.
How to manage schema validation errors in outbound integration messages [page 374]
How to enable email notifications with daily summaries of integration failures [page 376]
When updates from the ERP system are pushed to external supplier management questionnaires [page 377]
How to manage schema validation errors in

outbound integration messages
Schema validation errors can cause supplier synchronization with the ERP system to become blocked. You can
manage schema validation errors in outbound integration messages by viewing them, troubleshooting them, and
ignoring the errors that are not relevant to your ERP configuration.
Prerequisites
To view ERP integration messages and manage schema validation errors, you must be a member of the SM Ops
To ignore schema validation errors, the enhanced ERP integration error handling feature must be enabled in your
site.
Context
SAP Ariba automatically validates outbound integration messages against the default SAP business partner WSDL
before queuing them for synchronization to the integrated SAP ERP or SAP S/4HANA system and blocks messages
with schema validation errors from the queue so that they do not fail XML validation in the ERP and block the
synchronization queue.
If the business partner data model in your ERP system differs from the default SAP business partner model, and
SAP Ariba identifies a schema validation error that is not relevant to your ERP system, you can ignore the error.
Once you ignore a schema validation error, SAP Ariba marks it as ignored in all subsequent outbound integration
messages. Outbound messages that have no schema validation errors or that only have ignored errors are
automatically queued for synchronization to the ERP system.

374 PUBLIC Topics about managing ERP integration
For inbound failure confirmation messages, the error message details page shows all errors generated by the ERP
system during schema validation of the integration message XML payload. You can compare the errors that caused
integration failures in the ERP to the initial SAP Ariba schema validation to determine which SAP Ariba-identified
errors you can ignore.
You can only ignore schema validation errors at the element level and the data type level, but you cannot ignore
errors at the level of specific violations of maximum field length, minimum field length, and regular expression
patterns for an element and data type. For example, if you ignore a maximum length error for the address element
FirstLineName of data type LANGUAGEINDEPENDENT_MEDIUM_Name, SAP Ariba ignores all maximum field
length, minimum field length, enumeration, regular expression pattern, and other validation errors for both the
element FirstLineName and the data type LANGUAGEINDEPENDENT_MEDIUM_Name.
If you ignore an SAP Ariba schema validation error, but the error also fails ERP XML validation, you can stop
ignoring the error. Once you stop ignoring a schema validation error, SAP Ariba again automatically blocks the
outbound integration messages in which it occurs.
For information on configuring bi-directional integration using SAP Ariba cloud integration or SAP Ariba Cloud
Integration Gateway, see the integration configuration documentation for those tools.
Procedure

2. Click ERP integration status.
3. (Optional) Filter integration messages by performing any of the following actions:
○ Search for messages by type, date, or other criteria.

○ Filter the message list by SM vendor ID.
○ Enable the Show only entries with potential XML errors toggle.
 Tip
To manage outbound schema validation errors, search for outbound messages and show only messages
with potential XML errors.
4. In the Messages column for the message, click View.
The Schema validation errors tab of the error details page shows all errors for the message, including both the
active errors that blocked the message from the synchronization queue and any ignored errors. The Ignored
errors shows errors all of the errors that are currently ignored in your site.
○ If the error also causes a corresponding error in the ERP system, correct it in the supplier data.
○ If the error is not relevant to the ERP system business partner configuration, select it and click Ignore.
Note that each schema validation error generates two entries on the Schema validation errors tab: one for
the element and the other for its data type. To successfully ignore a validation error, you must select both
entries before clicking Ignore.
○ If the error is currently ignored but has caused previous synchronization failures in the ERP system, click
the Ignored errors tab, select the error, and click Stop Ignoring.

Topics about managing ERP integration PUBLIC 375
Results
Any validation errors you ignored are ignored in all subsequent outbound integration messages in which they occur.
Any validation errors you stopped ignoring block all subsequent outbound integration messages in which they
occur.
Next Steps
If you corrected or ignored validation errors, you can resynchronize the supplier to the ERP system manually in
their 360° profile to generate a new outbound integration message.
Related Information
How to enable email notifications with daily summaries of integration failures [page 376]
How to enable email notifications with daily

summaries of integration failures
SAP Ariba can send administrators daily email notifications that contain summary information for all integration
failures that occurred that day. Administrators can use these notifications to identify and troubleshoot integration
problems in a timely manner.
Prerequisites
To enable email notifications of integration errors and to receive those notifications, you must be a member of the
SM ERP Administrator group.
Context
Integration failure email notifications contain the SM vendor ID and name of every supplier associated with a failure
confirmation message from the ERP system in the previous 24 hours. The notifications are sent daily at 1am PST.
Clicking the link in the notification opens the login page for your SAP Ariba site.
Enabling integration failure summary notifications enables them for all members of the SM ERP Administrator
group. Individual users within that group can disable the notifications in the email preferences in their user
accounts.

Procedure

2. Click ERP integration.
3. In the Notifications setting area, check Send daily notifications of synchronization failures.
4. Click Save.
Results
All members of the SM ERP Administrator group receive daily integration failure notifications.
Related Information
How to manage schema validation errors in outbound integration messages [page 374]
When updates from the ERP system are pushed to

external supplier management questionnaires
When an integrated SAP ERP or SAP S/4HANA system sends updates to your site, the supplier database
automatically updates the corresponding fields in the vendor database. The updates are also pushed to mapped
questions in external questionnaires in certain circumstances.
If a supplier is already synchronized with an integrated ERP system, updates from an integrated ERP system are
always committed to the supplier record in the database. SAP Ariba also immediately pushes those updates to
mapped questions in any internal questionnaires. SAP Ariba pushes updates from an integrated ERP system to
mapped questions in external questionnaires as follows:
Status when ERP update occurs ERP update pushed to questionnaire? Update behavior
New questionnaires:
Registration: Not Invited N/A The project has not yet been created, and
therefore there is no questionnaire to up
Modular questionnaire: N/A
date.
Registration: Invited Yes Questionnaires are prepopulated with

data from the ERP system, and those an
Modular questionnaire: Not Responded
swers show to the supplier when they
first open the questionnaire.

Registration: In Registration Yes If the supplier has saved current answers

and reopens the questionnaire, it auto
Modular questionnaire: Pending
matically shows the updates from the
Submission
ERP system and a message lets them
know that some answers have changed.
If a supplier is currently editing the ques

tionnaire when SAP Ariba pushes the up
date, when they attempt to save or sub
mit the questionnaire, the questionnaire
refreshes with the updates from the ERP
system and a message lets them know
that some answers have changed. The
updates do not show until the supplier
saves or submits the questionnaire.
Registration: Pending Approval No Approvers see and approve or deny the

answers submitted by the supplier, even
Modular questionnaire: Pending if updates received from the ERP system
Approval during approval conflict with those an
swers.

Registration: Pending Resubmit No In the supplier view of the question

naire: If the supplier has saved current
Modular questionnaire: Pending
answers and reopens the questionnaire,
Resubmission
it automatically shows the updates from
the ERP system and a message lets them

In the buyer view of the questionnaire:

Since the approval task on the question
naire is already in progress, and one or
more approvers might already have ap
proved previous answers, SAP Ariba does
not push updates to the buyer view of the
questionnaire. Once the supplier resub
mits answers, any ERP updates pushed
to their view of the questionnaire are in
cluded in the resubmission. Note that
ERP updates do show immediately in the
ERP data area of the supplier profile, just
not in the questionnaire.
Registration: Registered Yes When a supplier views their approved

questionnaire, it shows any updates from
Modular questionnaire: Approved, the ERP system that occurred after ap
Expiring, or Expired proval. A message lets them know that
some answers have changed.
 Note
This behavior applies only to modu
lar supplier management question
naires that allow updates. If the mod
ular questionnaire does not allow up
dates, SAP Ariba does not push up
dates from the ERP system to it after
the initial approval.

Registration: Registration Denied No The denied questionnaire captures the

supplier-submitted answers that resulted
Modular questionnaire: Denied in denial. SAP Ariba does not push any
updates from the ERP system to it. In the
new questionnaire phase, a denied ques
tionnaire does not reopen for further up
dates.
Questionnaire updates:
 Note
This behavior only applies to modular supplier management questionnaires that allow updates (the Always open setting in
the template survey document is set to Yes).
Registration: Registered Yes If the supplier has saved current answers

and reopens the questionnaire, it auto
Modular questionnaire: Approved,
matically shows the updates from the
Expiring, or Expired
ERP system and a message lets them

saves or submits the questionnaire
Registration update: Pending Approval No Approvers see and approve or deny the
answers submitted by the supplier, even
Modular questionnaire update: Pending if updates received from the ERP system
Approval in the meantime conflict with those an
swers.

Registration update: Pending Resubmit No In the supplier view of the question

naire: If the supplier has saved current
Modular questionnaire update: Pending
answers and reopens the questionnaire,
Resubmission
it automatically shows the updates from
the ERP system and a message lets them

In the buyer view of the questionnaire:

Since the approval task on the question
naire is already in progress, and one or
more approvers might already have ap
proved previous answers, SAP Ariba does
not push updates to the buyer view of the
questionnaire. Once the supplier resub
mits answers, any ERP updates pushed
to their view of the questionnaire are in
cluded in the resubmission. Note that
ERP updates do show immediately in the
ERP data area of the supplier profile, just
not in the questionnaire.
Registration update: Approved Yes When a supplier views their approved

questionnaire, it shows any updates from
Modular questionnaire update: the ERP system that occurred after ap
Approved, Expiring, or Expired proval. A message lets them know that
some answers have changed.
Registration update: Denied No The denied questionnaire captures the

supplier-submitted answers that resulted
Modular questionnaire update: in denial. SAP Ariba does not push any
Approved, Expiring, or Expired updates from the ERP system to it until
the supplier reopens it to revise re
sponses.
 Note
● These update scenarios apply only to data received from an integrated ERP system. They do not apply to
data imported in SM Administration.
● SAP Ariba does not push updates from the ERP system to external registration and modular questionnaires
that are in approval. If there is a discrepancy between data received from the ERP while the questionnaire is

in approval and the current answers in the questionnaire, approval of the questionnaire overwrites the ERP
data.

Topics about setting up Dun & Bradstreet
integration with SAP Ariba Supplier Lifecycle
and Performance
Integrating SAP Ariba Supplier Lifecycle and Performance with Dun & Bradstreet [page 383]
Workflow for Dun & Bradstreet integration with SAP Ariba Supplier Lifecycle and Performance [page 384]
Prerequisites for integrating Dun & Bradstreet with SAP Ariba Supplier Lifecycle and Performance [page 386]
How to configure Dun & Bradstreet integration in your site [page 387]
Setting up the internal supplier request for Dun & Bradstreeet integration [page 388]
Setting up supplier registration questionnaires for Dun & Bradstreet integration [page 390]
Field mappings for Dun & Bradstreet questions in the internal supplier request and registration questionnaires
[page 390]
Deleting Dun & Bradstreet data from your site [page 393]
Field reference for Dun & Bradstreet integration [page 394]
Integrating SAP Ariba Supplier Lifecycle and

Performance with Dun & Bradstreet
Dun & Bradstreet integration allows you to require requesters at your company to search for potential new
suppliers in the D&B database during the internal supplier request process and include D&B data in supplier
profiles.
Dun & Bradstreet integration is available in SAP Ariba Supplier Lifecycle and Performance. It integrates SAP Ariba
Supplier Lifecycle and Performance with third-party provider Dun & Bradstreet (D&B) to retrieve data for selected
fields from D&B Worldbase Marketing Plus with Linkage product using D&B's Data Integration Toolkit (DIT -
https://toolkit-api.dnb.com ). This integration enables you to use D&B supplier data to:
● Require requesters in your organization to search for potential new suppliers in the D&B database during the
internal supplier request process, ensuring that all new suppliers created in SAP Ariba Supplier Lifecycle and
Performance either have D-U-N-S numbers or are approved for an exception.
● Include other D&B data in supplier profiles. With D&B integration, the request process adds basic D&B data
such as address to the supplier request. After the supplier request is approved, SAP Ariba pulls additional from
D&B and adds it to the SAP Ariba vendor record and, based on your configuration, to supplier registration
questionnaires.
D&B integration automates inclusion of this standard and verified data in supplier profiles, eliminating the need for
category or supplier managers to manually enter not only D-U-N-S numbers, but other detailed supplier data
maintained by Dun & Bradstreet. You choose which D&B data to include in the supplier profile by adding mapped
questions to the internal supplier request and registration questionnaires in your site's supplier management
project templates.
Topics about setting up Dun & Bradstreet integration with SAP Ariba Supplier
Lifecycle and Performance PUBLIC 383
 Note
Dun & Bradstreet integration:
● Involves only the Worldbase Marketing Plus with Linkage and the Data Integration Toolkit product.
● Supports the use of integrated Dun & Bradstreet data in internal supplier requests and both internal and
external (supplier-facing) supplier registration questionnaires. It does not support the use of D&B data in
supplier self-registration request.
● Pulls additional data from Dun & Bradstreet and adds it to D&B-integrated vendor database fields after
approval of a supplier request based on a D&B supplier. There is currently no way to update the data after
this point.
Related Information
[page 390]
Workflow for Dun & Bradstreet integration with SAP

Ariba Supplier Lifecycle and Performance
The following high-level steps describe the workflow for Dun & Bradstreet integration with SAP Ariba Supplier
Lifecycle and Performance after the feature is enabled in your site:
1. A customer administrator from your company configures the feature with your Dun & Bradstreet Data
Integration Toolkit user ID and password.
2. A template creator updates the internal supplier request project template in your site to include:
○ Questions mapped to the vendor database fields required for D&B supplier lookup, as well as any other
mapped D&B fields that you want to include in the request. See the separate Dun & Bradstreet field
reference Excel file for reference.
○ Questions asking the requester to explain why they need an exception to the D-U-N-S number requirement
if they do not see the supplier they are requesting in the D&B search results.
The template creator publishes the new version of the template.
3. A template creator updates internal and/or external (supplier-facing) questionnaires in the supplier
registration project template in your site to add mapped questions for D&B data and published the new version
of the template.
4. A requester at your company creates an internal supplier request by choosing Create Supplier Request
with D&B Lookup and the D&B search page opens.
5. The requester performs one of the following actions on the D&B search page:
○ Enters the supplier's D-U-N-S number, if they know it or can obtain it from the supplier before submitting
the request.
384 PUBLIC Lifecycle and Performance
○ Enters other information, such as name and address, that can be used to look up an existing supplier in the
D&B database.
This step might include requesting that the supplier create a Dun & Bradstreet account to obtain a D-U-N-S
number if they don't already have one.
6. SAP Ariba searches the integrated D&B database using the specified search criteria and displays a list of
matching suppliers to the requester. This search is in principle free of D&B charges unless there is an abuse of
the customer agreement.
7. One of the following two scenarios occurs:
○ If the requester recognizes a supplier from the D&B search results as the supplier they wanted to request,
they check the supplier and click Next. The supplier request form defined by your site's template opens
with the mapped D&B questions automatically populated with basic D&B data; the requester cannot edit
this information. Questions with mapping to fields that are pulled from D&B after request approval are
automatically hidden to avoid the requester entering data that will be overwritten by the subsequent D&B
data pull. The D&B exception-related questions added in Step 3 are also automatically hidden. The
requester fills out the rest of the request and submits it.
○ If the requester does not recognize any of the suppliers in the D&B search results, they click Can't find
supplier. The supplier request form opens displaying the D&B exception questions configured in Step 2.
Questions mapped to D-U-N-S number and legal supplier name are automatically hidden. The requester
fills out the request and submits it.
8. SAP Ariba checks for duplicate suppliers in your site. If duplicates are identified, the requester can still opt to
submit the supplier request.
9. The supplier request enters the approval workflow. Approvers review and approve the request, and the new
supplier is created in the SAP Ariba supplier database.
10. If the supplier request was based on a D&B supplier, after it is approved, a second D&B data pull adds
additional data from Worldbase Marketing Plus to the supplier record in SAP Ariba Supplier Lifecycle and
Performance for any D&B-integrated database fields that are mapped in request or registration questionnaires.
Depending on your licensing agreement with D&B, this second data pull might incur D&B fees. It only occurs
after the approval of the supplier request.
11. Once the D&B data is pulled into the SAP Ariba supplier record, it is available in the supplier's 360° profile. The
locations in the profile where it is visible depend on the underlying data field and your questionnaire
configurations:
○ D&B-integrated data fields mapped to questions in the supplier request show in the Origins of the
Supplier area with other supplier request details.
○ In standard vendor fields displayed in other areas of the profile that are integrated with D&B, such as
supplier name (name1), the D&B data displays.
○ All D&B-integrated data fields automatically show in the profile ERP data, including custom fields.
12. The new supplier is invited to register. When the registration project is created:
○ Any questions in registration questionnaires that are mapped to the same vendor database fields as
questions in the supplier request are automatically populated with the values from the request, including
any D&B data.
○ Any additional questions in registration questionnaires that are mapped to database fields enriched by the
second D&B data pull are automatically populated with that data. Note that your registration questionnaire
should make these questions read-only to avoid having suppliers or internal users overwrite data retrieved
from D&B.

Related Information
How to configure Dun & Bradstreet integration in your site [page 387]
Prerequisites for integrating Dun & Bradstreet with

SAP Ariba Supplier Lifecycle and Performance
Before integrating SAP Ariba Supplier Lifecycle and Performance with Dun & Bradstreet, make sure that you have
fulfilled the prerequisites for both Dun & Bradstreet licensing and configuration and configuration in your SAP Ariba
Supplier Lifecycle and Performance site.
For integration with SAP Ariba Supplier Lifecycle and Performance, you must have licensed Dun & Bradstreet's
Worldbase Marketing Plus with Linkage and Data Integration Toolkit, the product must be activated, and you must
have a user ID and password for the Data Integration Toolkit. Your agreement with Dun & Bradstreet must allow you
to access the D&B service from your SAP Ariba cloud service and receive data from your D&B account in your SAP
Ariba site. SAP Ariba assumes no responsibility for the D&B service or support for that service. All materials or data
you receive from the D&B service are considered Customer Data or Customer Materials under your agreement
with SAP. The feature enabling access to this external service may be removed from the SAP Ariba cloud service by
SAP Ariba with advanced notice to you (or immediately to protect SAP's interest in case of a security, system
integrity, or intellectual property infringement concern).
The enhanced supplier request, SM-15774, must be enabled in your site.
To configure Dun & Bradstreet integration in SAP Ariba Supplier Lifecycle and Performance, you must be a member
of the SM Ops Administrator group.
To add mapped questions in internal supplier requests and registration questionnaires to support Dun & Bradstreet
searches, you must be a member of the Template Creator group.
Your site must use the Extended Address rather than Address answer type to collect address information about
suppliers, and the extended address configuration in your site must include the following fields, which are required
for D&B integration:
● House No./Street/Suppl.
● Street 2
● Postal Code/City
● Country/Region
● Dun & Bradstreet integration with supplier addresses occurs only in extended address fields (which have field
names that start with vendor.addressExt.postalAddress). Integration with regular address fields (which
start with vendor.address) is not supported.
If you want an integrated SAP ERP system to consume D&B data stored in SAP Ariba Supplier Lifecycle and
Performance custom vendor database fields, which start with the vendor.supplierGenericCustomField
extension, you must customize your integration.
How to configure Dun & Bradstreet integration in
your site
Dun & Bradstreet integration automatically adds data from third-party provider Dun & Bradstreet to SAP Ariba
Supplier Lifecycle and Performance vendor records and supplier profiles. To set up integration, you must add your
Dun & Bradstreet Data Integration Toolkit username and password to your SAP Ariba Supplier Lifecycle and
Performance site.
Prerequisites
 Note
As an SAP Ariba customer, when you configure D&B integration in your site, you have the following
responsibilities:
● You are fully responsible for having an agreement with D&B that allows you to access the D&B service from
the SAP Ariba cloud and receive data from your D&B account in your SAP Ariba cloud site.
● You are responsible for setting up and managing the D&B license key.
● You are responsible for paying D&B fees based on your agreement with D&B.
● You must notify SAP Ariba promptly if you see a problem with how the feature is obtaining records from
D&B (for example, if it generates too many payable D&B searches)
● Support for D&B services is only provided by D&B.
● D&B data is considered as "Customer Owned Data" under SAP Ariba agreements.
If you do not agree to these responsibilities, you should not enable and configure the D&B integration feature.
To set up Dun & Bradstreet integration, you must be a member of the SM Ops Administration group.
You must have licenses to Dun & Bradstreet's Worldbase Marketing Plus with Linkage and Data Integration Toolkit,
the products must be activated, and you must have a user ID and password for the Data Integration Toolkit. Your
agreement with Dun & Bradstreet must allow you to access the Dun & Bradstreet service from your SAP Ariba
cloud service and receive data from your Dun & Bradstreet account in your SAP Ariba site.
Before you set up Dun & Bradstreet integration, set up your internal supplier request [page 388] (required) and
supplier registration questionnaires [page 390] (optional) to support integration.
Context
SAP Ariba Supplier Lifecycle and Performance stores your Dun & Bradstreet Data Integration Toolkit username and
password in encrypted database fields, which only retain the currently submitted values.

Procedure

2. Click Config.
3. On the Credentials for dropdown menu, choose DNB.
4. Enter your Dun & Bradstreet Data Integration Toolkit username and password.
5. Re-enter your password to confirm it.
6. Click Submit.
Results
The Config page records the timestamp when you added your credentials and your username. The page does not
show your credentials after you submit them. Your SAP Ariba site is now integrated with your Dun & Bradstreet
products. Supplier request creation now includes an initial search for the requested supplier in the Dun &
Bradstreet database, and if the request is approved, the supplier's profile includes the additional set of D&B data.
Next Steps
You can update your Dun & Bradstreet credentials at any time by entering new username and password values and
clicking Submit, or delete your credentials by clicking Delete.
Setting up the internal supplier request for Dun &

Bradstreeet integration
If your site uses D&B integration, your supplier request must include questions mapped to required D&B fields, as
well as one or more questions that enable requesters to ask for an exception for suppliers that are not included in
the D&B database.
D&B integration is designed to enforce a requirement that all suppliers added to the your site's supplier database
via approved internal supplier requests either have D-U-N-S numbers or go through an exception process. Users
creating supplier requests perform a D&B lookup on an initial search page and either choose an existing D&B
supplier or specify that they can't find a matching D&B supplier before opening the request questionnaire defined
by the survey document in your site's supplier request project template. If they choose an existing D&B supplier,
certain fields in the supplier request are automatically populated with D&B data, which the requester cannot edit. If
they choose to create a request that is not based on an existing D&B supplier, you can ask them questions to justify
the exception as well as questions about information that would otherwise be automatically provided by D&B.
Setting up questions with required D&B lookup fields
Add questions the D&B fields that are required for looking up complete D&B data, as well as any optional fields you
want to use, to the supplier request. See Field mappings for Dun & Bradstreet questions in the internal supplier
request and registration questionnaires [page 390] for a list of required and optional fields.
Setting up questions about exceptions for requests that are not based on a D&B supplier
For supplier requests that are not based on a D&B supplier, create one or more questions asking the requester
about the exception. For example, you can create a text question with a list of predefined reasons for the exception.
For all exception-related questions, enter vendor.external.exception.reason in the Supplier field mapping
field.
The vendor.external.exception.reason field mapping ensures that a question only displays in supplier
request forms that open after a requester has clicked Can't find supplier on the D&B search page, meaning that
the request is not created based on an existing D&B supplier. It is always hidden in requests created based on
existing D&B suppliers. You do not need to add any visibility conditions to the question; this behavior is automatic
with the vendor.external.exception reason mapping.
 Tip
If you group your D&B exception questions in a section but only include questions mapped to
vendor.external.exception.reason in it, all of those questions are hidden in requests based on D&B
suppliers, but the section heading is still visible and shows as an empty section. To avoid showing an empty
section in requests based on D&B suppliers, make sure to add other content not mapped to
vendor.external.exception.reason to the section as well.
Considerations for approval flows in supplier requests that use D&B data
The initial D&B lookup that a requester performs before creating a D&B-integrated supplier request does not incur
D&B charges. After a request based on a D&B supplier is approved, a second search populates additional D&B-
integrated fields in the supplier database with data from D&B Worldbase Marketing Plus, and D&B usage charges
might apply to this search. The final approvers you specify for supplier requests that use D&B data should be users
who can be responsible for making judgments in which D&B charges might be a factor.
Related Information
[page 390]
Setting up supplier registration questionnaires for
Dun & Bradstreet integration
If your site uses Dun & Bradstreet integration, you can prepopulate answers in supplier registration questionnaires
with D&B data.
If your site uses D&B integration, your internal or external supplier questionnaires can include questions mapped to
D&B fields. See Field mappings for Dun & Bradstreet questions in the internal supplier request and registration
questionnaires [page 390] for a list of D&B-integrated fields. If a supplier was created from a request based on a
D&B supplier, those fields are automatically populated with data from D&B.
 Tip
To avoid having suppliers or internal users overwrite that data with new answers, use editability conditions to
make them read-only.
In addition to showing in registration questionnaires, data from D&B-integrated fields shows in supplier 360°
profiles.
Related Information
[page 390]
Field mappings for Dun & Bradstreet questions in the

internal supplier request and registration
questionnaires
If your site uses Dun & Bradstreet integration, can map questions in the internal supplier request and registration
questionnaires to specific fields that hold D&B information. In the supplier request, some of these mappings are
required.
 Note
● Unless otherwise noted, the questions listed in this section should use a text answer type.
● For complete details on SAP Ariba Supplier Lifecycle and Performance vendor database fields used in D&B
integration and their corresponding fields in the D&B data model, see Field reference for Dun & Bradstreet
integration [page 394].
● Due to legal requirements, D&B data pulls for suppliers in Germany require a mandatory reason code. SAP
Ariba Supplier Lifecycle and Performance automatically includes a reason code of 3 ("Credit Check –
Ongoing Business Connection") without any field configuration on your part.

Questions with the following field mappings are required in the supplier request and use free D&B lookup services.
Approval of supplier requests that include these fields do not incur usage charges for D&B Worldbase Marketing
Plus with Linkage. You can also include them in internal or external supplier registration questionnaires.
Question Required Field Mapping Notes
Supplier name vendor.vendorInfo.name1 SAP Ariba requires this field, as well as

supplier contact fields, in supplier re
quests. It is not required for D&B integra
tion.
Legal supplier name vendor.vendorInfo.name3 This question is automatically hidden in

requests that are not based on existing
D&B suppliers.
In requests based on existing D&B sup

pliers, the supplier name and legal sup
plier name (name1 and name3) fields are
populated with the same value from
D&B. The requester can edit the name1
field, but cannot edit the name3 field.
D-U-N-S number vendor.vendorInfo.dunsId This question is automatically hidden in

requests that are not based on existing
D&B suppliers.
In requests based on existing D&B sup

pliers, the value is added automatically
by the D&B lookup and the requester
cannot edit this field.
Extended address vendor.addressExt.postalAdd Use the Extended Address answer type

ress for this question.
Field mappings are automatic for the in

dividual fields of an Extended Address
question based on the vendor.addres
sExt.postalAddress mapping.
Your site's Extended Address configura-

tion must include the fields that are re
quired for D&B search; see the Prerequi
sites for integrating Dun & Bradstreet
with SAP Ariba Supplier Lifecycle and
Performance [page 386] section for de
tails.
If your site's Extended Address configu-

ration does not include any of the re
quired fields listed in Prerequisites for in
tegrating Dun & Bradstreet with SAP
Ariba Supplier Lifecycle and Performance
[page 386], add them as separate ques
tions and manually enter their corre
sponding mappings.

Exception for requests not matched to an vendor.external.exception.r You can use this mapping for one or more
existing D&B supplier eason questions that define an exception proc
ess for requests that do not match an ex
isting D&B supplier.
Questions with this mapping are always

hidden in requests for existing D&B sup
pliers.
The following ERP vendor fields are automatically populated with data from D&B when the supplier request is
approved. You can also include them in internal or external supplier registration questionnaires and in the supplier
request for the D&B exception case. For complete details on SAP Ariba Supplier Lifecycle and Performance vendor
database fields used in D&B integration and their corresponding fields in the D&B data model, see Field reference
for Dun & Bradstreet integration [page 394].
Primary fax number vendor.addressExt.fax.numbe

rSubscriberID
Primary phone number vendor.adressExt.telephone.

numberSubscriberID
National business ID vendor.supplierGenericCusto

mField.nationalId
National business ID type vendor.supplierGenericCusto

mField.nationalType
Number of employees vendor.supplierGenericCusto Use the Number answer type for this
mField.numberOfEmployees question.
Year established vendor.supplierGenericCusto Use the Number answer type for this
mField.yearEstablished question.
Out of business? vendor.supplierGenericCusto Use the Number answer type for this
mField.outOfBusiness question.
Name of global ultimate (GU) parent vendor.supplierGenericCusto

mField.guDunsName
D-U-N-S number of global ultimate (GU) vendor.supplierGenericCusto

parent mField.guDunsNumber
Headquarters or parent company vendor.supplierGenericCusto

mField.headquarters
Line of business vendor.supplierGenericCusto

mField.lineOfBusiness
Legal status vendor.supplierGenericCusto

mField.legalIdDescription
CEO name vendor.supplierGenericCusto

mField.ceoName

CEO corporate title vendor.supplierGenericCutom

Field.ceoTitle
Industry standard code 1 vendor.industrySector[0].in Vector field

dustrialSectorCode

dustrialSectorCode

dustrialSectorCode

dustrialSectorCode

dustrialSectorCode
Industry standard code 6 vendor.industrysector[5].in Vector field

dustrialSectorCode
Deleting Dun & Bradstreet data from your site

If you terminate your agreement with Dun & Bradstreet, you might need to delete any data you previously received
from them.
To delete D&B data from standard vendor database fields, you must overwrite the field values provided by D&B
with different field values in your SAP Ariba Supplier Lifecycle and Performance site.
To delete D&B data that is stored in custom SAP Ariba Supplier Lifecycle and Performance vendor fields that begin
with the extension vendor.supplierGenericCustomField, your Designated Support Contact must log a
service request to delete D&B data stored in a dedicated D&B table.
SAP Ariba will first run a select query to identify the to-be deleted items and share the results with you. After your
confirmation, these records will be deleted.
You are responsible for deleting impacted D&B data that was synchronized to and then stored in an integrated ERP
system.

Field reference for Dun & Bradstreet integration
If your site integrates with Dun & Bradstreet, D&B data can populate specific fields in the unified vendor model.
Lookups are typically free, but Dun & Bradstreet Worldbase Marketing Plus Linkage data pulls can incur charges.
Visibility/editabil
D&B DIT data ele ity in requests for
ment/DIT tag existing D&B sup Required in sup
SAP Ariba field mapping name D&B data package pliers plier request?
vender.vendorInfo.name1 BUSINESS Lookup/WBM+Link Visible and editable Yes

NAME /
MKT_PRIM_NME
(not pulled)
vendor.vendorInfo.name3 BUSINESS Lookup/WBM+Link Visible and read- Yes

NAME / only
MKT_PRIM_NME
This field always
(not pulled)
hidden in requests
that are not based
on an existing D&B
supplier
vendor.vendorInfo.dunsId D&B® D-U-N-S® Lookup/WBM+Link Visible and read- Yes

Number / only
MKT_DUNS_NBR
This field always
(not pulled)
hidden in requests
that are not based
on an existing D&B
supplier
vendor.addres vendor.addres STREET Lookup/WBM+Link Visible and read- Yes

sExt.postalAd sExt.postalAd ADDRESS / only
dress dress.streetN MKT_PHYS_ADR_
ame LINE (not pulled)
 Note
vendor.addres STREET Lookup/WBM+Link Visible and read- Yes
Field mappings sExt.postalAd ADDRESS / only
are automatic dress.streetP MKT_PHYS_ADR_
for the individ refixName LINE (not pulled)
ual fields in an
vendor.addres CITY NAME / Lookup/WBM+Link Visible and read- Yes
Extended
sExt.postalAd MKT_PHYS_POST only
Address ques
dress.cityNam _TOWN_TEXT (not
tion based on
e pulled)
the
vendor.add vendor.addres STATE/ Lookup/WMB+Link Visible and read- Yes
sExt.postalAd PROVINCE only
ressExt.po
dress.regionC NAME /
stalAddres
ode MKT_PHYS_GEO_
s mapping. If
AREA_TEXT (not
your Extended pulled

Visibility/editabil
Address con vendor.addres COUNTRY NAME / Lookup/WBM+Link Visible and read- Yes
sExt.postalAd MKT_PHYS_CTRY only
figuration does
dress.country _TEXT
not include re
Code
quired fields,
you must cre vendor.suppli CONTINENT WBM+Link Always hidden No
ate individual erGenericCust CODE /
mapped ques omField.regio MKT_PHYS_CONT
tions for those n _CD
fields in the Lookup/WBM+Link Visible and read- Yes
vendor.addres ZIP/POSTAL
supplier re sExt.postalAd CODE / only
quest. dress.streetP MKT_PHYS_POST
ostalCode _TOWN_CD (not
pulled)
vendor.addres MAILING WBM+Link Always hidden No

sExt.postalAd ADDRESS /
dress.poBoxID MKT_MLG_ADR_L
INE
vendor.addres MAILING CITY WBM+Link Always hidden No

sExt.postalAd NAME /
dress.poBoxDe MKT_MLG_POST_
viatingCityNa TOWN_TEXT
me
vendor.addres MAILING ZIP/ WBM+Link Always hidden No

sExt.postalAd POSTAL CODE /
dress.poBoxPo MKT_MLG_POST_
stalCode TOWN_CD
vendor.addres FAX NUMBER / WBM+Link Always hidden No

sExt.fax.numb MKT_FAX_NBR
erSubscriberI
D
vendor.addres TELEPHONE WBM+Link Always hidden No

sExt.telephon NUMBER /
e.numberSubsc MKT_PHON_NBR
riberID
vendor.supplierGenericCusto NATIONAL ID / WBM+Link Always hidden No

mField.nationalId MKT_BUS_REGN_
NBR_TYPE_CD

Visibility/editabil
vendor.supplierGenericCusto NATIONAL WBM+Link Always hidden No

mField.nationalIdType IDENTIFICATIO
N SYSTEM
CODE /
MKT_BUS_REGN_
NBR_TYPE
vendor.supplierGenericCusto EMPLOYEES WBM+Link Always hidden No

mField.numberOfEmployees HERE /
MKT_EMPL_AT_P
HYS_ADR
vendor.supplierGenericCusto YEAR STARTED / WBM+Link Always hidden No

mField.yearEstablished MKT_STRT_YR
vendor.supplierGenericCusto OUT OF WBM+Link Always hidden No

mField.outOfBusiness BUSINESS
STATUS CODE /
MKT_OUT_BUS_I
ND
vendor.supplierGenericCusto BUSINESS Lookup/WBM+Link Always hidden No

mField.locationTypeIndicato STRUCTURE
r CODE /
MKT_BUS_STRUC
_CD (not pulled)
vendor.supplierGenericCusto GLOBAL WBM+Link Always hidden No

mField.guDunsName ULTIMATE
BUSINESS
NAME /
MKT_GBL_ULT_P
RIM_NME
vendor.supplierGenericCusto GLOBAL WBM+Link Always hidden No

mField.guDunsNumber ULTIMATE D&B®
D-U-N-S
NUMBER /
MKT_GLBL_ULT_
PNT_DUNS
vendor.supplierGenericCusto HEADQUARTERS WBM+Link Always hidden No

mField.hqDunsNumber / PARENT D&B®
D-U-N-S®
NUMBER /
MKT_HDQ_PNT_D
UNS

Visibility/editabil
vendor.supplierGenericCusto HEADQUARTERS WBM+Link Always hidden No

mField.headquarters / PARENT
BUSINESS
NAME /
MKT_HDQ_PNT_P
RIM_NME
vendor.supplierGenericCusto LINE OF WBM+Link Always hidden No

mField.lineOfBusiness BUSINESS /
MKT_LOB
vendor.supplierGenericCusto LEGAL STATUS / WBM+Link Always hidden No

mField.legalIdDescription MKT_LGL_FORM
vendor.supplierGenericCusto CEO NAME / WMB+Link Always hidden No

mField.ceoName MKT_CEO_NME
vendor.supplierGenericCusto CEO TITLE / WBM+Link Always hidden No

mField.ceoTitle MKT_CEO_TITL
vendor.industrySector[0].in SIC CODE / WBM+Link Always hidden No

dustrialSectorCode MKT_SIC8
(Leading
zeroes must
be kept)

(Leading
zeroes must
be kept)

(Leading
zeroes must
be kept)

(Leading
zeroes must
be kept)

(Leading
zeroes must
be kept)

Visibility/editabil

(Leading
zeroes must
be kept)
Related Information

Quick reference to optional supplier
management features
SAP Ariba Supplier Lifecycle and Performance and SAP Ariba Supplier Information and Performance Management
(new architecture) include some optional features that are not enabled by default.
ID Feature Description Enablement
SM-6182 Customer-configurable dupli Enables template creators to Configure in the supplier re
quest [page 144]
cate checks in supplier re specify questions in internal
quests and external supplier requests
to be used in checks for dupli
cate suppliers.
Department Dimension Supplier management matrix Adds business unit (depart Contact SAP Ariba Support to
enable
enhancement: business unit ment) as a third dimension
along with commodity and re
gion in buyer category assign
ments, qualifications, disquali
fications, preferred supplier
management, and modular
supplier management ques
tionnaire projects.
SIPM to SM Migration Mode Supplier management migra Provides tools for migrating Contact SAP Ariba Support to
tion tools enable
supplier organizations, users,
and the supplier profile ques
tionnaire to suppliers, supplier
contacts, and supplier regis
tration questionnaires in the
unified vendor model using
manual file import and export.
SIPM to SM Auto Migration Supplier management migra Provides an automatic, one- Contact SAP Ariba Support to
Mode enable
tion tools: auto-migration click tool for migrating sup
plier organizations, users, and
the supplier profile question
naire to suppliers, supplier
contacts, and supplier regis
tration questionnaires in the
unified vendor model. In some
cases, migration of supplier
profile questionnaires can still
involve manual steps.

Quick reference to optional supplier management features PUBLIC 399
SM-2861 External supplier request Provides a method for new Contact SAP Ariba Support to
enable
(supplier self-registration) suppliers to introduce them
selves to you by clicking a cus
tom URL and filling out a dedi
cated external supplier re
quest form.
SM-5590 Bank component in supplier Enables the Bank Account Contact SAP Ariba Support to
enable
management questionnaires question answer type, which
includes a predefined set of
mapped fields for collecting
supplier bank information.
SM-3492 Enhancements to the work Specifies that when an ap Contact SAP Ariba Support to
prover requests additional in enable
flow for requesting additional
formation, only the current
information during approval
node of the approval flow re
starts. By default, when an ap
prover requests additional in
formation, the approval flow
restarts from the beginning.
When this feature is enabled,
the approval flow retains ap
provers added to nodes that
were missing approvers. By
default, when the approval
flow restarts, it discards any
added approvers in approval
nodes that were missing ap
provers.
SM-4994 Approval requirement for syn Requires that all internal regis Contact SAP Ariba Support to
tration questionnaires be ap enable
chronizing internal registra
proved before synchronization
tion questionnaires to the ERP
to an integrated ERP system.
system By default, internal registra
tion questionnaires synchron
ize to the ERP system after
submission.
SM-5060 Access to classic Supplier Per Allows you to measure sup Contact SAP Ariba Support to
enable
formance Management plier performance using clas
projects sic SPM projects, which exist
as standalone projects and are
not linked to other supplier
management processes.

400 PUBLIC Quick reference to optional supplier management features
SM-5144 Assigning fulfillment and Allows users in your site to es Contact SAP Ariba Support to
enable
sourcing relationships to sup tablish a fulfillment relation
pliers ship with a supplier as they
register for any event, estab
lish a sourcing relationship
with a supplier as they register
for Ariba Network, or establish
a fulfillment relationship with a
supplier after a sourcing rela
tionship has already been es
tablished.
SM-5116 Status tracker for supplier Displays registration invitation Contact SAP Ariba Support to
enable
management email notifica- email delivery status so that
tions category or supplier managers
can re-send invitations that
have bounced or that have not
been answered promptly.
SM-6129 Modular supplier manage Enables separate, template- Contact SAP Ariba Support to
enable
ment questionnaire based modular questionnaires
for collecting specific sets of
information from suppliers.
SM-6752 Supplier certificate manage Enables a specialized certifi- Contact SAP Ariba Support to
enable
ment cate question in modular sup
plier management question
naires for the collection of
supplier certificate informa
tion.
SM-6316 External approval API Enables external approval API Contact SAP Ariba Support to
enable
access for approval tasks in
supplier management
projects.
SM-6380 Business unit-specific notifi- Allows you to import business Contact SAP Ariba Support to
enable
cations in supplier request units as department master
process data and display the business
unit name rather than your
company's name in the exter
nal supplier request and re
lated notifications to suppliers
and approvers.

SM-7213 Supplier management Dun & Integrates SAP Ariba Supplier Contact SAP Ariba Support to
Bradstreet integration Lifecycle and Performance enable
with third-party provider Dun
& Bradstreet to automate in
cludes of standard and veri
fied Dun & Bradstreet data in
supplier profiles.
SM-7917 Configure output fields for Adds the ability to configure Contact SAP Ariba Support to
supplier data API which fields are included in enable
output for the Supplier Data
API with Pagination
vendorDataRequests
endpoint.
SM-9657 Enhancements to supplier Automatically generates bank Contact SAP Ariba Support to
bank ID management IDs for supplier banks using enable, then define the bank
optional country-specific pre ID length in Intelligent
fixes instead of requiring sup Configuration Manager [page
pliers to provide those IDs 519] and optionally import
when answering bank ques master data to define country-
tions. specific prefixes [page 52]
SM-12249 Enhancements to ERP inte Blocks any integration mes Contact SAP Ariba Support to
enable
gration error handling and er sages with validation errors in
ror display for supplier data the outbound ERP integration
message queue and provides
tools that allow customer ad
ministrators to ignore errors
that do not apply to their ERP
configuration.
SM-12250 Enhanced questionnaire con Adds validation for supplier Contact SAP Ariba Support to
enable
figuration capabilities for in field mapping data and a user
creased ERP integration accu interface tool to generate sug
racy gested field restrictions when
you create questions with text
answer types in question
naires.
SM-14213 Support for displaying full Adds a Contact SAP Ariba Support to
supplier names longer than 35 vendor.vendorInfo.fu enable
characters llName database field with a
maximum length of 140 char
acters for storing supplier
names. The value in this field
shows in other SAP Ariba solu
tions such as SAP Ariba Buy
ing solutions, SAP Ariba Con
tracts, and SAP Ariba Sourc
ing.

SM-14322 New supplier 360° profile A new 360° profile for suppli Contact SAP Ariba Support to
ers. It includes a more consis enable
tent look and feel with other
SAP Ariba and SAP applica
tions; improved navigation,
better use of space, and more
intuitive organization of sup
plier profile information and
supplier management activi
ties; improved task manage
ment; enhancements to the
workflow for supplier qualifi-
cation expirations and requali
fications; and compatibility
with the Microsoft Internet Ex
plorer.
 Note
Some features and func
tions are only supported
in the new supplier 360°
profile [page 407].
SM-15622 Display new supplier contact Displays new supplier contact Contact SAP Ariba Support to
names with family names first names in the reverse order of enable
how they are created. This ap
plies to all areas that supplier
contact names are displayed,
including external notifica-
tions.
 Note
This feature applies to
sites that use the classic
supplier 360° profile.

SM-15774 Enhancements to the supplier Enhances the look and feel of Contact SAP Ariba Support to
request both internal and external enable
supplier requests and adds
type-ahead duplicate check
with user interface improve
ments for displaying potential
matches, match scores, and
ratings of weak or strong.
 Note
When this feature is not
enabled, the State/
Region/Province field in
Address questions uses
state master data. When
this feature is enabled, it
uses region master data.
SM-3049 Support for questions based Adds the ability to create mas Contact SAP Ariba Support to
on additional types of master ter data questions in supplier enable
data management questionnaires
Configure in the supplier re
based on company code, pur
chasing organization, pay quest and internal registration
ment terms, and incoterms questionnaires [page 248]
master data from an inte
grated ERP system. The list of
possible answers for these
questions is populated directly
from integrated master data,
eliminating the need to man
ually maintain answers that
match the current data in the
ERP system.
With the 2011 (Q4 2020) re

lease, SAP Ariba plans to turn
this feature on for all custom
ers whose sites use the new
supplier 360° profile
(SM-14322).

SM-9656 Syntax validation for supplier Validates some fields in Bank Contact SAP Ariba Support to
bank account information Account questions to help en enable
sure that the bank information
provided by suppliers is in the
expected format before it is
synchronized with an inte
grated ERP system. It includes
default syntax validations and
data import tasks that allow
you to define your own coun
try-specific syntax validations
so that they match the syntax
requirements of your ERP sys
tem, helping to prevent inte
gration errors caused by inva
lid supplier bank account in
formation.
 Note
With the 2011 (Q4 2020)
release, SAP Ariba plans
to turn this feature on for
all customers.
SM-16802 Ability to remind suppliers to Adds configuration options Configure in external registra
submit periodic registration that allow you to remind sup tion questionnaires [page 158]
updates pliers to update registration
questionnaires at periodic in
tervals so that those question
naires always contain current
information.
SM-17591 Display new supplier contact Displays new supplier contact Contact SAP Ariba Support to
names with family names first names in the reverse order of enable
in the new supplier 360° pro how they are created. This ap
file plies to all areas that supplier
contact names are displayed,
including external notifica-
tions.
 Note
This feature applies to
sites that use the new

SM-18117 Ability for buyer to configure Adds a new template-level set Enable in Intelligent
sender name in invitation ting that allows template crea Configuration Manager [page
emails tors to specify a custom 518] in your site and then
sender name for external reg configure in external registra
istration questionnaires. This tion questionnaires [page 160]
custom sender name replaces
the generic system alias in the
"From" field in new registra
tion invitations and invitation
reminders.
SM-18305 New email notifications for Adds new email notification Configure in external registra
supplier registration remind templates for reminding sup tion questionnaires [page 156]
ers pliers to complete their regis
trations. These templates in
clude language that is specific
to supplier registrations and
links to registration question
naires.
SM-20904 Ability to specify requester Adds a new step in manual Contact SAP Ariba Support to
when inviting a supplier to reg registration invitations where enable
ister registration managers can
choose the requester for the
registration, such as an indi
vidual in your organization
with whom the supplier is fa
miliar or already has a rela
tionship. The requester's
name shows in the "From"
field of registration invitations.
SM-20598 Configurable mappings be Adds a new master data map Contact SAP Ariba Support to
tween guided buying ship-to ping import that allows you to enable, then enable the
addresses and preferred and define mappings between ENABLE_SM_INTEGRATIO
qualified supplier regions ship-to address country codes N_ON_COUNTRYCODE pa
used in guided buying and the rameter in guided buying.
region code master data used
for preferred and qualified
suppliers so that guided buy
ing searches can identify the
appropriate preferred and
qualified suppliers regardless
of the region codes you use.
SM-20886 Ability to save supplier re Adds the ability to save inter Automatically on when the en
quests as draft nal supplier requests as hanced supplier request
drafts. This feature allows you (SM-15774) is enabled in your
to exit an internal supplier re site.
quest form without losing your
progress.
SM-17808 Make most fields in Certificate Makes all Certificate question Enable in Intelligent
questions optional fields, except for Expiration Configuration Manager [page
Date and Attachment, op 519] in your site.
tional.

Supplier management features and functions that
require the new supplier 360° profile
There are some supplier management features and functions that are only supported in the new supplier 360°
profile. They do not work in the classic supplier 360° profile.
If you plan to use any of the following features or functions in your site, your site must use the new supplier 360°
profile (SM-14322):
Feature or function Notes
Support for comments and attachments that respondents add The classic supplier 360° profile does display the attachments
to answers in external or internal questionnaires. added to attachment questions as the direct answer, but it not
display comments and attachments added to the answers of
other questions.
Ability to edit qualification expiration and requalification eligi The classic supplier 360° profile does not provide a way to edit
bility dates during requalification. these dates when starting a requalification.
Advanced view link configuration. Members of the SM Ops Administrator group can enable or
disable links to the advanced view of supplier management
projects in the new supplier 360° profile.
Single location for all registration activities In the new supplier 360° profile, users manage internal and ex
ternal registration questionnaires and associated tasks in the
Registration area. In the classic supplier 360° profile, internal
questionnaires are located on a separate tile.
SM-15772: Ability to export individual supplier management The Export button is only available on the new questionnaire
questionnaires to Excel. details page associated with the new supplier 360° profile.
SM-9830: Scoring and score banding in modular supplier man The overall feature is also supported in the classic supplier
agement questionnaires. 360° profile, but its Questionnaires tile does not show ques
tionnaire scores in the questionnaire summary.
SM-4721: Ability to restart denied supplier registrations. Both the ability to start a new round of a denied approval task
and the ability to reinvite a supplier to a denied registration are
available only in the new supplier 360° profile.
SM-11558: Enhancements to the registration update phase to Enhancements to the registration process flow graph to show
support individual questionnaire updates. the questionnaires and tasks associated with the most recent
registration update are only available in the new supplier 360°
profile.
SM-14205: Enhancements to handling of denied question Approval decision labels and task comment enhancements to
naires show the name of the task owner are only available in the new
questionnaire and task details pages associated with the new
SM-20904: Ability to specify requester when inviting a supplier This feature is only available in the registration invitation work
to register flow in the new supplier 360° profile.
SM-17415: Activity log for supplier 360° profiles This feature is only available in the new supplier 360° profile.
SM-3049: Support for questions based on additional types of This feature is only available in the new supplier 360° profile
master data and the enhanced supplier request (SM-15774).
SM-8960: Ability to reassign questionnaires in completed reg This feature is only available in the new supplier 360° profile.
istrations to different supplier contacts

Feature or function Notes
SM-15932: Access to previous questionnaire versions and pre The template version menu is only available in sites that use
vious project information after template upgrade the new supplier 360° profile. The Previous Project field in
project advanced views is also available in sites that use the
classic supplier 360° profile, but it does not allow you to navi
gate selectively between archived projects based on different
template versions.
SM-16687: Improved user experience for internal question This feature is only available in the new supplier 360° profile
naires with visibility conditions and the enhanced supplier request (SM-15774).
SM-17690: SAP Qualtrics feedback surveys for supplier man This feature is only available in the new supplier 360° profile.
agement users
SM-19056: Configurable postal code validation in address an This feature is only available in the new supplier 360° profile
swers and the enhanced supplier request (SM-15774).
 Note
The release guide information for the new supplier 360° profile (SM-14322) and previous versions of this topic
stated that the new supplier 360° profile supports editing repeatable sections in internal questionnaires. This
functionality is not currently supported and has been disabled by default. To preserve backward compatibility,
SAP Ariba has enabled it in customer sites where it is already in use, but repeatable sections in internal
questionnaires might not function as expected in all use cases. SAP Ariba will announce general availability of
this functionality when it supported.

Topics about default master data for supplier
management
Default syntax validation for account holder names, account numbers, and bank keys in Bank Account
Default country-specific ERP region code mappings [page 423]
Default syntax validation for postal codes in supplier addresses [page 504]
Default bank control keys in Bank Account questions

The bank account syntax validation feature (SM-9656) includes a default set of bank control key master data. You
can use these default values or import custom definitions.
A bank control key specifies the type of the supplier bank account, such as savings or checking. Different countries
can have different bank control keys. In sites where the bank account syntax validation feature (SM-9656) is
enabled, a Bank Control Key field replaces the previous Bank Account Type field in Bank Account questions.
Bank Account questions also include a Country field for the bank address. Once a respondent has chosen a
country, the Bank Control Key dropdown menu shows the bank control keys defined in your site's master data.
You can use the Import Country-Specific Bank Control Key and Import Country-Specific Bank Control Key
Translations data import tasks to define custom, country-specific bank control keys [page 54].
The following table describes the default bank control key master data included with the bank account syntax
validation feature (SM-9656):
UniqueName ControlKeyCode ControlKeyDesc CountryCode
CTRL001 CC Current Account AR
CTRL002 CA Savings Account AR
CTRL003 CE Special Savings AR

Account
CTRL004 CS Salary Account AR
CTRL005 1 Checking Account US
CTRL006 2 Savings Account US
CTRL007 3 Loan US
CTRL008 4 General Ledger US

Topics about default master data for supplier management PUBLIC 409
UniqueName ControlKeyCode ControlKeyDesc CountryCode
CTRL009 1 FUTSU JP
CTRL010 2 TOUZA JP
CTRL011 4 CHOCHIKU JP
CTRL012 9 Other bank accounts JP
CTRL013 1 Current (Cheque) ZA

Account
CTRL014 2 Savings Account ZA
CTRL015 3 Transmission Account ZA
CTRL016 4 Bond Account ZA
CTRL017 9 Subscription Share ZA

Account
CTRL018 CC Checking Account VE
CTRL019 CA Savings Account VE
CTRL020 CE Special Savings VE

Account
CTRL021 CS Salary Account VE
CTRL022 10 Savings Account IN
CTRL023 11 Checking Account IN
Related Information

Default syntax for IBAN numbers in Bank Account

questions
The bank account syntax validation feature (SM-9656) includes a default set of IBAN syntax validation master
data. You can use these default values or import custom definitions.
The International Bank Account Number (IBAN) is a system for identifying bank accounts across national borders.
This system uses a specific syntax that includes a country code, check digits, and other bank information. In sites
that are integrated with an SAP ERP system, integration errors can occur when a supplier synchronized to the ERP
system has an IBAN number that does not use the required syntax.
You can use the Import Country-Specific Bank IBAN fields data import task to define custom, country-specific
IBAN syntax [page 56].

410 PUBLIC Topics about default master data for supplier management
The following table describes the default IBAN syntax master data included with the bank account syntax validation
feature (SM-9656):
CountryCode IBANFormat IBANLength IBANRegex
AL AL2!n8!n16!c 28 AL\d{10}[A-Z0-9]{16}
AD AD2!n4!n4!n12!c 24 AD\d{10}[A-Z0-9]{12}
AT AT2!n5!n11!n 20 AT\d{18}
AZ AZ2!n4!a20!c 28 AZ\d{2}[A-Z]{4}[A-
Z0-9]{20}
BH BH2!n4!a14!c 22 BH\d{2}[A-Z]{4}[A-
Z0-9]{14}
BE BE2!n3!n7!n2!n 16 BE\d{14}
BA BA2!n3!n3!n8!n2!n 20 BA\d{18}
BR BR2!n8!n5!n10!n1!a1! 29 BR\d{25}[A-Z]{1}[A-
c Z0-9]{1}
BG BG2!n4!a4!n2!n8!c 22 BG\d{2}[A-Z]{4}\d{6}
[A-Z0-9]{8}
CR CR2!n3!n14!n 21 CR\d{20}
HR HR2!n7!n10!n 21 HR\d{19}
CY CY2!n3!n5!n16!c 28 CY\d{10}[A-Z0-9]{16}
CZ CZ2!n4!n6!n10!n 24 CZ\d{22}
DK DK2!n4!n9!n1!n 18 DK\d{16}
DO DO2!n4!c20!n 28 DO\d{2}[A-Z0-9]
{4}\d{20}
EE EE2!n2!n2!n11!n1!n 20 EE\d{18}
FI FI2!n6!n7!n1!n 18 FI\d{16}
FR FR2!n5!n5!n11!c2! 27 FR\d{12}[A-Z0-9]
{11}\d{2}
GE GE2!n2!a16!n 22 GE\d{2}[A-Z]
{2}\d{16}
DE DE2!n8!n10!n 22 DE\d{20}
GI GI2!n4!a15!c 23 GI\d{2}[A-Z]{4}[A-
Z0-9]{15}
GR GR2!n3!n4!n16!c 27 GR\d{9}[A-Z0-9]{16}
GT GT2!n4!c20!c 28 GT\d{2}[A-Z0-9]{24}
HU HU2!n3!n4!n1!n15!n1! 28 HU\d{26}
n
IS IS2!n4!n2!n6!n10!n 26 IS\d{24}

IE IE2!n4!a6!n8!n 22 IE\d{2}[A-Z]
{4}\d{14}
IL IL2!n3!n3!n13!n 23 IL\d{21}
IT IT2!n1!a5!n5!n12!c 27 IT\d{2}[A-Z]
{1}\d{10}[A-Z0-9]
{12}
JO JO2!n4!a4!n18!c 30 JO\d{2}[A-Z]{4}\d{4}
[A-Z0-9]{18}
KZ KZ2!n3!n13!c 20 KZ\d{5}[A-Z0-9]{13}
KW KW2!n4!a22!c 30 KW\d{2}[A-Z]{4}[A-
Z0-9]{22}
LV LV2!n4!a13!c 21 LV\d{2}[A-Z]{4}[A-
Z0-9]{13}
LB LB2!n4!n20!c 28 LB\d{6}[A-Z0-9]{20}
LI LI2!n5!n12!c 21 LI\d{7}[A-Z0-9]{12}
LT LT2!n5!n11!n 20 LT\d{18}
LU LU2!n3!n13!c 20 LU\d{5}[A-Z0-9]{13}
MK MK2!n3!n10!c2!n 19 MK\d{5}[A-Z0-9]
{10}\d{2}
MT MT2!n4!a5!n18!c 31 MT\d{2}[A-Z]{4}\d{5}
[A-Z0-9]{18}
MR MR2!n5!n5!n11!n2!n 27 MR\d{25}
MU MU2!n4!a2!n2!n12!n3! 30 MU\d{2}[A-Z]
n3!a {4}\d{19}[A-Z]{3}
MD MD2!n2!c18!c 24 MD\d{2}[A-Z0-9]{20}
MC MC2!n5!n5!n11!c2!n 27 MC\d{12}[A-Z0-9]
{11}\d{2}
ME ME2!n3!n13!n2!n 22 ME\d{20}
NL NL2!n4!a10!n 18 NL\d{2}[A-Z]
{4}\d{10}
NO NO2!n4!n6!n1!n 15 NO\d{13}
PK PK2!n4!a16!c 24 PK\d{2}[A-Z]{4}[A-
Z0-9]{16}
PS PS2!n4!a21!c 29 PS\d{2}[A-Z]{4}[A-
Z0-9]{21}
PL PL2!n8!n16!n 28 PL\d{26}
PT PT2!n4!n4!n11!n2!n 25 PT\d{23}

QA QA2!n4!a21!c 29 QA\d{2}[A-Z]{4}[A-
Z0-9]{21}
RO RO2!n4!a16!c 24 RO\d{2}[A-Z]{4}[A-
Z0-9]{16}
LC LC2!n4!a24!c 32 LC\d{2}[A-Z]{4}[A-
Z0-9]{24}
SM SM2!n1!a5!n5!n12!c 27 SM\d{2}[A-Z]
{1}\d{10}[A-Z0-9]
{12}
ST ST2!n8!n11!n2!n 25 ST\d{23}
SA SA2!n2!n18!c 24 SA\d{4}[A-Z0-9]{18}
RS RS2!n3!n13!n2!n 22 RS\d{20}
SC SC2!n4a!2n!2n!16n! 31 SC\d{2}[A-Z]
3a! {4}\d{20}[A-Z]{3}
SK SK2!n4!n6!n10!n 24 SK\d{22}
SI SI2!n5!n8!n2!n 19 SI\d{17}
ES ES2!n4!n4!n1!n1!n10! 24 ES\d{22}
n
SE SE2!n3!n16!n1!n 24 SE\d{22}
CH CH2!n5!n12!c 21 CH\d{7}[A-Z0-9]{12}
TL TL2!n3!n14!n2!n 23 TL\d{21}
TN TN2!n2!n3!n13!n2!n 24 TN\d{22}
TR TR2!n5!n1!n16!c 26 TR\d{8}[A-Z0-9]{16}
UA UA2!n6!n19!c 29 UA\d{8}[A-Z0-9]{19}
AE AE2!n3!n16!n 23 AE\d{21}
GB GB2!n4!a6!n8!n 22 GB\d{2}[A-Z]
{4}\d{14}
VG VG2!n4!a16!n 24 VG\d{2}[A-Z]
{4}\d{16}
Related Information


Default syntax validation for account holder names,
account numbers, and bank keys in Bank Account
questions
The bank account syntax validation feature (SM-9656) includes a default set of syntax validation master data for
account holder names, account numbers, and bank keys or ABA routing numbers. You can use these default values
or import custom definitions.
You can use the Import Country-Specific Bank validation fields data import task to define country-specific syntax
for these fields. Bank account field validation definitions include fields where you specify which check rule to use
during syntax validation using a number between 1 and 8. For details on defining custom, country-specific syntax
validation for these fields and the check rules that correspond to these numbers, see Defining country-specific
syntax validation for supplier bank account holder name, account number, and bank key or ABA routing number
[page 58]
The following table describes the default syntax validation for bank account holder name, account number, and
bank key or ABA routing number master data included with the bank account syntax validation feature (SM-9656):
Account
Ho
lderNam Account Account Account BankKey
e HolderN HolderN NumberC Accoun Accoun C
Countr CheckRu a a h tNumbe tNumbe heckRul BankKe BankK
yCode le meRegex meSize eckRule rRegex rSize e yRegex eySize
AD 5 60 5 15
AE 5 60 1 11
AF 5 60 5 15
AG 5 60 1 11
AI 5 60 1 12
AL 5 60 5 15
AM 5 60 1 11
AO 5 60 1 11
AQ 5 60 1 15
AR 5 60 5 15
AS 5 60 5 15
AT 5 60 2 11 4 5
AU 5 60 8 9 3 7
AW 5 60 1 11
AX 5 60
AZ 5 60 1 11

Account
Ho
BA 5 60 1 11
BB 5 60 1 11
BD 5 60 1 11
BE 5 60 3 14 3 3
BF 5 60 1 11
BG 5 60 3 10 7 8
BH 5 60 1 11
BI 5 60 1 11
BJ 5 60 1 11
BL 5 60
BM 5 60 1 11
BN 5 60
BO 5 60 1 11
BQ 5 60
BR 5 60 1 15 2 9
BS 5 60
BV 5 60 1 11
BW 5 60 1 11
BY 5 60 1 11
BZ 5 60 1 11
CA 5 60 5 10 5 10
CC 5 60 1 11
CD 5 60
CF 5 60 1 11
CG 5 60
CH 5 60 5 18 2 7
CI 5 60 1 11
CK 5 60 1 11
CN 5 60

Account
Ho
CO 5 60 5 15
CR 5 60 5 15
CV 5 60 1 11
CW 5 60
CX 5 60 1 11
CY 5 60 1 11
CZ 5 60 5 18 5 4
DE 5 60 2 14 4 8
DJ 5 60 1 11
DK 5 60 2 10 5 4
DM 5 60 1 11
DO 5 60 1 11
DZ 5 60 1 11
EC 5 60 1 11
EE 5 60 2 14 4 2
EG 5 60 1 11
EH 5 60
ER 5 60 1 11
ES 5 60 4 10 4 8
ET 5 60 1 11
FI 5 60 1 18 1 11
FJ 5 60 1 11
FK 5 60 1 11
FM 5 60
FO 5 60 5 15
FR 5 60 3 11 4 10
GA 5 60 1 11
GB 5 60 1 8 1 6
GD 5 60 1 11

Account
Ho
GE 5 60 5 15
GF 5 60 1 11
GG 5 60
GH 5 60 1 11
GI 5 60 1 11
GL 5 60 1 11
GM 5 60 1 11
GN 5 60 1 11
GP 5 60 1 11
GQ 5 60 1 11
GR 5 60 1 11
GT 5 60 1 11
GU 5 60 1 11
GW 5 60 1 11
GY 5 60 1 11
HK 5 60 1 12 1 3
HM 5 60 1 11
HN 5 60 1 11
HR 5 60 1 11
HT 5 60 1 11
HU 5 60 1 17 4 8
ID 5 60 5 15
IE 5 60 5 15
IL 5 60 1 11
IM 5 60
IN 5 60 1 11
IO 5 60 1 11
IQ 5 60 1 11
IS 5 60 5 15

Account
Ho
IT 5 60 1 12 4 10
JE 5 60
JM 5 60 5 15
JO 5 60 1 11
JP 5 60 2 7 4 7
KE 5 60 1 11
KG 5 60 5 15
KH 5 60 5 15
KI 5 60 1 11
KM 5 60 1 11
KN 5 60 1 11
KR 5 60 1 11
KW 5 60 1 11
KY 5 60 1 11
KZ 5 60 4 12 5 15
LA 5 60 5 15
LB 5 60 1 11
LC 5 60 1 11
LI 5 60 5 18 5 15
LK 5 60 5 15
LR 5 60 1 11
LS 5 60 1 11
LT 5 60 5 15
LU 5 60 5 15 5 8
LV 5 60 5 15
LY 5 60 1 11
MA 5 60 1 11
MC 5 60 5 15
MD 5 60 1 11

Account
Ho
ME 5 60
MF 5 60
MG 5 60 1 11
MH 5 60 1 11
MK 5 60
ML 5 60 1 11
MM 5 60 1 11
MN 5 60 5 15
MO 5 60 1 11
MP 5 60
MQ 5 60 1 11
MR 5 60 1 11
MS 5 60 1 11
MT 5 60 1 11
MU 5 60 1 11
MV 5 60 1 11
MW 5 60 1 11
MX 5 60 5 10 6 4
MY 5 60 5 15
MZ 5 60 1 11
NA 5 60 2 17 4 6
NC 5 60 1 11
NE 5 60 1 11
NF 5 60 1 11
NG 5 60 1 11
NI 5 60 1 11
NL 5 60 4 10 1 11
NO 5 60 4 11 1 4
NP 5 60 5 15

Account
Ho
NR 5 60 1 11
NU 5 60 1 11
NZ 5 60 2 14 1 6
OM 5 60 1 11
PA 5 60 1 11
PE 5 60 5 15
PF 5 60 5 15
PG 5 60 5 15
PH 5 60 1 11
PK 5 60 5 15
PL 5 60 5 11
PM 5 60 1 11
PN 5 60 1 11
PR 5 60 5 15
PS 5 60
PT 5 60 2 11 4 8
PW 5 60 1 11
PY 5 60 1 11
QA 5 60 1 11
RE 5 60 1 11
RO 5 60 1 11
RS 5 60
RU 5 60 4 18 5 15
RW 5 60 1 11
SA 5 60 1 11
SB 5 60 5 15
SC 5 60 1 11
SE 5 60 1 11 8 4
SG 5 60 5 10 5 10

Account
Ho
SH 5 60 1 11
SI 5 60 1 11
SJ 5 60 1 11
SK 5 60 5 10 5 10
SL 5 60 1 11
SM 5 60 5 15
SN 5 60 5 15
SO 5 60 1 11
SR 5 60 1 11
SS 5 60
ST 5 60 1 11
SV 5 60 1 11
SX 5 60
SZ 5 60 1 11
TC 5 60 1 11
TD 5 60 1 11
TF 5 60
TG 5 60 1 11
TH 5 60 1 15 5 15
TJ 5 60 1 11
TK 5 60 1 11
TL 5 60
TM 5 60 1 11
TN 5 60 1 11
TO 5 60 1 11
TR 5 60 5 15
TT 5 60 5 15
TV 5 60 1 11
TW 5 60 1 11

Account
Ho
TZ 5 60 1 11
UA 5 60 5 18 4 8
UG 5 60 1 11
UM 5 60 1 1
US 5 60 6 17 6 9
UY 5 60 5 15
UZ 5 60 5 15
VA 5 60 1 11
VC 5 60 1 11
VE 5 60 5 15
VG 5 60 5 15
VI 5 60 5 15
VN 5 60 5 15
VU 5 60 5 15
WF 5 60 1 11
WS 5 60 5 15
YE 5 60 1 11
YT 5 60 1 11
ZA 5 60 2 17 4 6
ZM 5 60 1 11
ZW 5 60 5 15
Related Information


Default country-specific ERP region code mappings
SAP Ariba provides default master data to define mappings between ERP region codes in Extended Address
questions and the state codes in supplier profile addresses on Ariba Network.
If you import custom SAP region codes from T005S and T005U tables to populate the region field in Extended
Address, you can customize these mappings [page 60].
PrevANStateCo PrevERPRegion
UniqueName CountryCode ANStateCode ERPRegionCode de Code
"anrm_0000003 "AR" "AR-Z" "23" "Z"

7"
"anrm_0000003 "AR" "AR-X" "03" "X"

8"
"anrm_0000003 "AR" "AR-Y" "06" "Y"

9"
"anrm"0000004 "AR" "AR-V" "24" "V"

0"
"anrm_0000004 "AR" "AR-W" "04" "W"

1"
"anrm_0000004 "AR" "AR-T" "14" "T"

2"
"anrm_0000004 "AR" "AR-U" "17" "U"

3"
"anrm_0000004 "AR" "AR-R" "22" "R"

4"
"anrm_0000004 "AR" "AR-S" "12" "S"

5"
"anrm_0000004 "AR" "AR-P" "18" "P"

6"
"anrm_0000004 "AR" "AR-Q" "20" "Q"

7"
"anrm_0000004 "AR" "AR-N" "19" "N"

8"
"anrm_0000004 "AR" "AR-L" "21" "L"

9"
"anrm_0000005 "AR" "AR-M" "07" "M"

0"
"anrm_0000005 "AR" "AR-J" "10" "J"

1"
"anrm_0000005 "AR" "AR-K" "02" "K"

2"

"anrm_0000005 "AR" "AR-H" "16" "H"

3"
"anrm_0000005 "AR" "AR-F" "08" "F"

4"
"anrm_0000005 "AR" "AR-G" "13" "G"

5"
"anrm_0000005 "AR" "AR-D" "11" "D"

6"
"anrm_0000000 "AR" "AR-E" "05" "E"

57"
"anrm_0000005 "AR" "AR-B" "01" "B"

8"
"anrm_0000005 "AR" "AR-C" "00" "C"

9"
"anrm_0000006 "AR" "AR-A" "09" "A"

0"
"anrm_0000006 "AT" "AT-8" "V" "8"

1"
"anrm_0000000 "AT" "AT-9" "W" "9"

62"
"anrm_0000006 "AT" "AT-6" "ST" "6"

3"
"anrm_0000000 "AT" "AT-7" "T" "7"

64"
"anrm_0000000 "AT" "AT-4" "OOE" "4"

65"
"anrm_0000006 "AT" "AT-5" "S" "5"

6"
"anrm_0000006 "AT" "AT-2" "K" "2"

7"
"anrm_0000006 "AT" "AT-3" "NOE" "3"

8"
"anrm_0000006 "AT" "AT-1" "B" "1"

9"
"anrm_0000007 "AU" "AU-TAS" "TAS" "TAS"

0"
"anrm_0000007 "AU" "AU-NT" "NT" "NT"

1"

"anrm_0000007 "AU" "AU-ACT" "ACT" "ACT"

2"
"anrm_0000007 "AU" "AU-NSW" "NSW" "NSW"

3"
"anrm_0000007 "AU" "AU-WA" "WA" "WA"

4"
"anrm_0000007 "AU" "AU-VIC" "VIC" "VIC"

5"
"anrm_0000007 "AU" "AU-SA" "SA" "SA"

6"
"anrm_0000007 "AU" "AU-QLD" "QLD" "QLD"

7"
"anrm_0000007 "BE" "BE-WNA" "07" "WNA"

8"
"anrm_0000007 "BE" "BE-VOV" "08" "VOV"

9"
"anrm_0000008 "BE" "BE-VAN" "01" "VAN"

0"
"anrm_0000008 "BE" "BE-VLI" "05" "VLI"

1"
"anrm_0000008 "BE" "BE-WHT" "03" "WHT"

2"
"anrm_0000008 "BE" "BE-WLX" "06" "WLX"

3"
"anrm_0000008 "BE" "BE-WLG" "04" "WLG"

4"
"anrm_0000008 "BE" "BE-BRU" "11" "BRU"

5"
"anrm_0000008 "BE" "BE-VWV" "09" "VWV"

6"
"anrm_0000008 "BE" "BE-WBR" "10" "WBR"

7"
"anrm_0000008 "BE" "BE-VBR" "02" "VBR"

8"
"anrm_0000008 "BG" "BG-03" "09" "03"

9"
"anrm_0000009 "BG" "BG-02" "01" "02"

0"

"anrm_0000009 "BG" "BG-23" "08" "23"

1"
"anrm_0000009 "BG" "BG-22" "02" "22"

2"
"anrm_0000009 "BG" "BG-26" "03" "26"

3"
"anrm_0000009 "BG" "BG-12" "05" "12"

4"
"anrm_0000009 "BG" "BG-11" "04" "11"

5"
"anrm_0000009 "BG" "BG-18" "07" "18"

6"
"anrm_0000009 "BG" "BG-16" "06" "16"

7"
"anrm_0000009 "BR" "BR-AL" "AL" "AL"

8"
"anrm-0000009 "BR" "BR-AM" "AM" "AM"

9"
"anrm_0000010 "BR" "BR-ES" "ES" "ES"

0"
"anrm_0000010 "BR" "BR-AP" "AP "AP"

1"
"anrm_0000010 "BR" "BR-PA" "PA" "PA"

2"
"anrm_0000010 "BR" "BR-PB" "PB" "PB"

3"
"anrm_0000010 "BR" "BR-MS" "MS" "MS"

4"
"anrm_0000010 "BR" "BR-MT" "MT" "MT"

5"
"anrm_0000010 "BR" "BR-GO" "GO" "GO"

6"
"anrm_0000010 "BR" "BR-TO" "TO" "TO"

7"
"anrm_0000010 "BR" "BR-RN" "RN" "RN"

8"
"anrm_0000010 "BR" "BR-RO" "RO" "RO"

9"

"anrm_0000011 "BR" "BR-BA" "BA" "BA"

0"
"anrm_0000011 "BR" "BR-RR" "RR" "RR"

1"
"anrm_0000011 "BR" "BR-RS" "RS" "RS"

2"
"anrm_0000011 "BR" "BR-DF" "DF" "DF"

3"
"anrm_0000011 "BR" "BR-PR" "PR" "PR"

4"
"anrm_0000011 "BR" "BR-PE" "PE" "PE"

5"
"anrm_0000011 "BR" "BR-RJ" "RJ" "RJ"

6"
"anrm_0000011 "BR" "BR-PI" "PI" "PI"

7"
"anrm_0000011 "BR" "BR-SC" "SC" "SC"

8"
"anrm_0000011 "BR" "BR-SE" "SE" "SE"

9"
"anrm_0000012 "BR" "BR-SP" "SP" "SP"

0"
"anrm_0000012 "BR" "BR-AC" "AC" "AC"

1"
"anrm_0000012 "BR" "BR-CE" "CE" "CE"

2"
"anrm_0000012 "BR" "BR-MA" "MA" "MA"

3"
"anrm_0000012 "BR" "BR-MG" "MG" "MG"

4"
"anrm_0000012 "CA" "CA-ON" "ON" "ON"

5"
"anrm_0000012 "CA" CA-NL" "NL" "NL"

6"
"anrm_0000012 "CA" "CA-YT" "YT" "YT"

7"
"anrm_0000012 "CA" "CA-SK" "SK" "SK"

8"

"anrm_0000012 "CA" "CA-MB" "MB" "MB"

9"
"anrm_0000013 "CA" "CA-PE" "PE" "PE"

0"
"anrm_0000013 "CA" "CA-NB" "NB" "NB"

1"
"anrm_0000013 "CA" "CA-QC" "QC" "QC"

2"
"anrm_0000013 "CA" "CA-NU" "NU" "NU"

3"
"anrm_0000013 "CA" "CA-NS" "NS" "NS"

4"
"anrm_0000013 "CA" "CA-NT" "NT" "NT"

5"
"anrm_0000013 "CA" "CA-AB" "AB" "AB"

6"
"anrm_0000013 "CA" "CA-BC" "BC" "BC"

7"
"anrm_0000013 "CH" "CH-AI" "AI" "AI"

8"
"anrm_0000013 "CH" "CH-OW" "OW" "OW"

9"
"anrm_0000014 "CH" "CH-GR" "GR" "GR"

0"
"anrm_0000014 "CH" "CH-ZG" "ZG" "ZG"

1"
"anrm_0000014 "CH" "CH-VD" "VD" "VD"

2"
"anrm_0000014 "CH" "CH-ZH" "ZH" "ZH"

3"
"anrm_0000014 "CH" "CH-AR" "AR" "AR"

4"
"anrm_0000001 "CH" "CH-TG" "TG" "TG"

45"
"anrm_0000014 "CH" "CH-TI" "TI" "TI"

6"
"anrm_0000014 "CH" "CH-NE" "NE" "NE"

7"

"anrm_0000014 "CH" "CH-UR" "UR" "UR"

8"
"anrm_0000014 "CH" "CH-SO" "SO" "SO"

9"
"anrm_0000015 "CH" "CH-GE" "GE" "GE"

0"
"anrm_0000015 "CH" "CH-GL" "GL" "GL"

1"
"anrm_0000015 "CH" "CH-SZ" "SZ" "SZ"

2"
"anrm_0000015 "CH" "CH-AG" "AG" "AG"

3"
"anrm_0000015 "CH" "CH-LU" "LU" "LU"

4"
"anrm_0000015 "CH" "CH-NW" "NW" "NW"

5"
"anrm_0000015 "CH" "CH-JU" "JU" "JU"

6"
"anrm_0000015 "CH" "CH-BL" "BL" "BL"

7"
"anrm_0000015 "CH" "CH-FR" "FR" "FR"

8"
"anrm-0000015 "CH" "CH-BS" "BS" "BS"

9"
"anrm-0000016 "CH" "CH-SH" "SH" "SH"

0"
"anrm_0000016 "CH" "CH-SG" "SG" "SG"

1"
"anrm_0000016 "CH" "CH-VS" "VS" "VS"

2"
"anrm_0000016 "CH" "CH-BE" "BE" "BE"

3"
"anrm_0000016 "CL" "CL-AP" "15" "AP"

4"
"anrm_0000016 "CL" "CL-AN" "02" "AN"

5"
"anrm_0000016 "CL" "CL-TA" "01" "TA"

6"

"anrm_0000016 "CL" "CL-CO" "04" "CO"

7"
"anrm_0000016 "CL" "CL-AT" "03" "AT"

8"
"anrm_0000016 "CL" "CL-AR" "09" "AR"

9"
"anrm_0000017 "CL" "CL-MA" "12" "MA"

0"
"anrm_0000017 "CL" CL-RM" "13" "RM"

1"
"anrm_0000017 "CL" "CL-ML" "07" "ML"

2"
"anrm_0000017 "CL" "CL-LI" "06" "LI"

3"
"anrm_0000017 "CL" "CL-VS" "05" "VS"

4"
"anrm_0000017 "CL" "CL-LL" "10" "LL"

5"
"anrm_0000017 "CL" "CL-BI" "08" "BI"

6"
"anrm_0000017 "CL" "CL-LR" "14" "LR"

7"
"anrm_0000017 "CL" "CL-AI" "11" "AI"

8"
"anrm_0000017 "CN" "CN-BJ" "010" "11"

9"
"anrm_0000018 "CN" "CN-TJ" "030" "12"

0"
"anrm_0000018 "CN" "CN-HE" "060" "13"

1"
anrm_00000182 "CN" "CN-SX" "050" "14"

"
"anrm_0000018 "CN" "CN-NM" "040" "15"

3"
"anrm_0000018 "CN" "CN-LN" "070" "21"

4"
"anrm_0000018 "CN" "CN-JL" "080" "22"

5"

"anrm_0000018 "CN" "CN-HL" "090" "23"

6"
"anrm_0000018 "CN" "CN-SH" "020" "31"

7"
"anrm_0000018 "CN" "CN-JS" "100" "32"

8"
"anrm_0000018 "CN" "CN-ZJ" "130" "33"

9"
"anrm_0000019 "CN" "CN-AH" "110" "34"

0"
"anrm_0000019 "CN" "CN-FJ" "150" "35"

1"
"anrm_0000019 "CN" "CN-JX" "140" "36"

2"
"anrm_0000019 "CN" "CN-SD" "120" "37"

3"
"anrm_0000019 "CN" "CN-HA" "180" "41"

4"
"anrm_0000019 "CN" CN-HB" "170" "42"

5"
"anrm_0000019 "CN" "CN-HN" "160" "43"

6"
"anrm_0000019 "CN" "CN-GD" "190" "44"

7"
"anrm_0000019 "CN" "CN-GX" "210" "45"

8"
"anrm_0000019 "CN" "CN-HI" "200" "46"

9"
"anrm_0000020 "CN" "CN-CQ" "320" "50"

0"
"anrm_0000020 "CN" "CN-SC" "230" "51"

1"
"anrm_0000020 "CN" "CN-GZ" "220" "52"

2"
"anrm_0000020 "CN" "CN-YN" "240" "53"

3"
"anrm_0000020 "CN" "CN-XZ" "300" "54"

4"

"anrm_0000020 "CN" "CN-SN" "250" "61"

5"
"anrm_0000020 "CN" "CN-GS" "260" "62"

6"
"anrm_0000020 "CN" "CN-QH" "280" "63"

7"
"anrm_0000020 "CN" "CN-NX" "270" "64"

8"
"anrm_0000020 "CN" "CN-XJ" "290" "65"

9"
"anrm_0000021 "CO" "CO-SUC" "70" "SUC"

0"
"anrm_0000021 "CO" "CO-GUV" "95" "GUV"

1"
"anrm_0000021 "CO" "CO-COR" "23" "COR"

2"
"anrm_0000021 "CO" "CO-QUI" "63" "QUI"

3"
"anrm_0000021 "CO" "CO-BOY" "15" "BOY"

4"
"anrm_0000021 "CO" "CO-ARA" "81" "ARA"

5"
"anrm_0000021 "CO" "CO-PUT" "86" "PUT"

6"
"anrm_0000021 "CO" "CO-CAL" "17" "CAL"

7"
"anrm_0000021 "CO" "CO-CAQ" "18" "CAQ"

8"
"anrm_0000021 "CO" "CO-MAG" "47" "MAG"

9"
"anrm_0000022 "CO" "CO-LAG" "44" "LAG"

0"
"anrm_0000022 "CO" "CO-CES" "20" "CES"

1"
"anrm_0000022 "CO" "CO-TOL" "73" "TOL"

2"
"anrm_0000022 "CO" "CO-VID" "99" "VID"

3"

"anrm"0000022 "CO" "CO-DC" "11" "DC"

4"
"anrm_0000022 "CO" "CO-VAC" "76" "VAC"

5"
"anrm_0000022 "CO" "CO-CAU" "19" "CAU"

6"
"anrm_0000022 "CO" "CO-CAS" "85" "CAS"

7"
"anrm_0000022 "CO" "CO-MET" "50" "MET"

8"
"anrm_0000022 "CO" "CO-RIS" "66" "RIS"

9"
"anrm_0000023 "CO" "CO-ATL" "08" "ATL"

0"
"anrm_0000023 "CO" "CO-SAN" "68" "SAN"

1"
"anrm_0000023 "CO" "CO-NAR" "52" "NAR"

2"
"anrm_0000023 "CO" "CO-SAP" "88" "SAP

3"
"anrm_0000023 "CO" "CO-ANT" "05" "ANT"

4"
"anrm_0000023 "CO" "CO-CHO" "27" "CHO"

5"
"anrm_0000023 "CO" "CO-VAU" "97" "VAU"

6"
"anrm_0000023 "CO" "CO_GUA" "94" "GUA"

7"
"anrm_0000023 "CO" "CO-AMA" "91" "AMA"

8"
"anrm_0000023 "CO" "CO-CUN" "25" "CUN"

9"
"anrm_0000024 "CO" "CO-HUI" "41" "HUI"

0"
"anrm_0000024 "CO" "CO-NSA" "54" "NSA"

1"
"anrm_0000024 "CO" "CO-BOL" "13" "BOL"

2"

"anrm_0000024 "CZ" "CZ-31" "31" "JC"

3"
"anrm_0000024 "CZ" "CZ-64" "64" "JM"

4"
"anrm_0000024 "CZ" "CZ-41" "41" "KA"

5"
"anrm_0000024 "CZ" "CZ-81" "81" "MO"

6"
"anrm_0000024 "CZ" "CZ-51" "51" "LI"

7"
"anrm_0000024 "CZ" "CZ-81" "81" "MO"

8"
"anrm_0000024 "CZ" "CZ-71" "71" "OL"

9"
"anrm_0000025 "CZ" "CZ-53" "53" "PA"

0"
"anrm_0000025 "CZ" "CZ-32" "32" "PL"

1"
"anrm_0000025 "CZ" "CZ-11" "11" "PR"

2"
"anrm_0000025 "CZ" "CZ-21" "21" "ST"

3"
"anrm_0000025 "CZ" "CZ-42" "42" "US"

4"
"anrm_0000025 "CZ" "CZ-63" "63" "VY"

5"
"anrm_0000025 "CZ" "CZ-72" "72" "ZL"

6"
"anrm_0000025 "DE" "DE-MV" "13" "MV"

7"
"anrm_0000025 "DE" "DE-NW" "05" "NW"

8"
"anrm_0000025 "DE" "DE-BE" "11" "BE"

9"
"anrm_0000026 "DE" "DE-BB" "12" "BB"

0"
"anrm_0000026 "DE" "DE-HH" "02" "HH"

1"

"anrm_0000026 "DE" "DE-ST" "15" "ST"

2"
"anrm_0000026 "DE" "DE-RP" "07" "RP"

3"
"anrm_0000026 "DE" "DE-HE" "06" "HE"

4"
"anrm_0000026 "DE" "DE-HB" "04" "HB"

5"
"anrm_0000026 "DE" "DE-NI" "03" "NI"

6"
"anrm_0000026 "DE" "DE-SN" "14" "SN"

7"
"anrm_0000026 "DE" "DE-SL" "10" "SL"

8"
"anrm_0000026 "DE" "DE-BY" "09" "BY"

9"
"anrm_0000027 "DE" "DE-TH" "16" "TH"

0"
"anrm_0000027 "DE" "DE-BW" "08" "BW"

1"
"anrm_0000027 "DE" "DE-SH" "01" "SH"

2"
"anrm_0000027 "DK" "DK-83" "004" "83"

3"
"anrm_0000027 "DK" "DK-82" "002" "82"

4"
"anrm_0000027 "DK" "DK-85" "003" "85"

5"
"anrm_0000027 "DK" "DK-84" "001" "84"

6"
"anrm_0000027 "DK" "DK-81" "005" "81"

7"
"anrm_0000027 "EG" "EG-GH" "09" "GH"

8"
"anrm_0000027 "EG" "EG-MN" "07" "MN"

9"
"anrm_0000028 "EG" "EG-KN" "13" "KN"

0"

"anrm_0000028 "EG" "EG-AST" "11" "AST"

1"
"anrm_0000028 "EG" "EG-ASN" "17" "ASN"

2"
"anrm_0000028 "EG" "EG-SHR" "03" "SHR"

3"
"anrm_0000028 "EG" "EG-KB" "06" "KB"

4"
"anrm_0000028 "EG" "EG-KFS" "14" "KFS"

5"
"anrm_0000028 "EG" "EG-FYM" "15" "FYM"

6"
"anrm_0000028 "EG" "EG-GZ" "02" "GZ"

7"
"anrm_0000028 "EG" "EG-IS" "19" "IS"

8"
"anrm_0000028 "EG" "EG-PTS" "20" "PTS"

9"
"anrm_0000029 "EG" "EG-SHG" "10" "SHG"

0"
"anrm_0000029 "EG" "EG-ALX" "08" "ALX"

1"
"anrm_0000029 "EG" "EG-MT" "24" "MT"

2"
"anrm_0000029 "EG" "EG-BNS" "16" "BNS"

3"
"anrm_0000029 "EG" "EG-MNF" "12" "MNF"

4"
"anrm_0000029 "EG" "EG-BA" "25" "BA"

5"
"anrm_0000029 "EG" "EG-SIN" "23" "SIN"

6"
"anrm_0000029 "EG" "EG-SUZ" "21" "SUZ"

7"
"anrm_0000029 "EG" "EG-WAD" "26" "WAD"

8"
"anrm_0000029 "EG" "EG-DT" "18" "DT"

9"

"anrm_0000030 "EG" "EG-C" "01" "C"

0"
"anrm_0000030 "EG" "EG-JS" "27" "JS"

1"
"anrm_0000030 "EG" "EG-LX" "22" "LX"

2"
"anrm_0000030 "EG" "EG-BH" "05" "BH"

3"
"anrm_0000030 "EG" "EG-DK" "04" "DK"

4"
"anrm_0000030 "ES" "ES-TE" "44" "TE"

5"
"anrm_0000030 "ES" "ES-CU" "16" "CU"

6"
"anrm_0000030 "ES" "ES-TF" "38" "TF"

7"
"anrm_0000030 "ES" "ES-TO" "45" "TO"

8"
"anrm_0000030 "ES" "ES-LE" "24" "LE"

9"
"anrm_0000031 "ES" "ES-PO" "36" "PO"

0"
"anrm_0000031 "ES" "ES-OR" "32" "OR"

1"
"anrm_0000031 "ES" "ES-GI" "17" "GI"

2"
"anrm_0000031 "ES" "ES-GR" "l8" "GR"

3"
"anrm_0000031 "ES" "ES-CO" "14" "CO"

4"
"anrm_0000031 "ES" "ES-CR" "13" "CR"

5"
"anrm_0000031 "ES" "ES-CS" "12" "CS"

6"
"anrm_0000031 "ES" "ES-GU" "19" "GU"

7"
"anrm_0000031 "ES" "ES-BU" "09" "BU"

8"

"anrm_0000031 "ES" "ES-SG" "40" "SG"

9"
"anrm_0000032 "ES" "ES-SE" "41" "SE"

0"
"anrm_0000032 "ES" "ES-GC" "35" "GC"

1"
"anrm_0000032 "ES" "ES-SO" "42" "SO"

2"
"anrm_0000032 "ES" "ES-CB" "39" "CB"

3"
"anrm_0000032 "ES" "ES-CC" "10" "CC"

4"
"anrm_0000032 "ES" "ES-SS" "20" "SS"

5"
"anrm_0000032 "ES" "ES-CA" "11" "CA"

6"
"anrm_0000032 "ES" "ES-BI" "48" "BI"

7"
"anrm_0000032 "ES" "ES-SA" "37" "SA"

8"
"anrm_0000032 "ES" "ES-NA" "31" "NA"

9"
"anrm_0000033 "ES" "ES-VI" "01" "VI"

0"
"anrm_0000033 "ES" "ES-A" "03" "A"

1"
"anrm_0000033 "ES" "ES-B" "08" "B"

2"
"anrm_0000033 "ES" "ES-C" "15" "C"

3"
"anrm_0000033 "ES" "ES-AV" "05" "AV"

4"
"anrm_0000033 "ES" "ES-H" "21" "H"

5"
"anrm_0000033 "ES" "ES-J" "23" "J"

6"
"anrm_0000033 "ES" "ES-BA" "06" "BA"

7"

"anrm_0000033 "ES" "ES-L" "25" "L"

8"
"anrm_0000033 "ES" "ES-M" "28" "M"

9"
"anrm_0000034 "ES" "ES-O" "33" "O"

0"
"anrm_0000034 "ES" "ES-P" "34" "P"

1"
"anrm_0000034 "ES" "ES-AB" "02" "AB"

2"
"anrm_0000034 "ES" "ES-ZA" "49" "ZA"

3"
"anrm_0000034 "ES" "ES-MU" "30" "MU"

4"
"anrm_0000034 "ES" "ES-T" "43" "T"

5"
"anrm_0000034 "ES" "ES-V" "46" "V"

6"
"anrm_0000034 "ES" "ES-AL" "04" "AL"

7"
"anrm_0000034 "ES" "ES-VA" "47" "VA"

8"
"anrm_0000034 "ES" "ES-Z" "50" "Z"

9"
"anrm_0000035 "ES" "ES-MA" "29" "MA"

0"
"anrm_0000035 "ES" "ES-LO" "26" "LO"

1"
"anrm_0000035 "ES" "ES-LU" "27" "LU"

2"
"anrm_0000035 "ES" "ES-HU" "22" "HU"

3"
"anrm_0000035 "FI" "FI-AL" "001" "AL"

4"
"anrm_0000035 "FI" "FI-LL" "004" "LL"

5"
"anrm_0000035 "FI" "FI-ES" "002" "ES"

6"

"anrm_0000035 "FI" "FI-IS" "003" "IS"

7"
"anrm_0000035 "FI" "FI-LS" "005" "LS"

8"
"anrm_0000035 "FI" "FI-OL" "006" "OL"

9"
"anrm_0000036 "FR" "FR-ARA" "01" "01"

0"
"anrm_0000036 "FR" "FR-HDF" "02" "02"

1"
"anrm_0000036 "FR" "FR-ARA" "03" "03"

2"
"anrm_0000036 "FR" "FR-PAC" "04"

3"
"anrm_0000036 "FR" "FR-PAC" "05" "05"

4"
"anrm_0000036 "FR" "FR-PAC" "06" "06"

5"
"anrm_0000036 "FR" "FR-ARA" "07" "07"

6"
"anrm_0000036 "FR" "FR-GES" "08" "08"

7"
"anrm_0000036 "FR" "FR-OCC" "09" "09"

8"
"anrm_0000036 "FR" "FR-GES" "10" "10"

9"
"anrm_0000037 "FR" "FR-OCC" "11" "11"

0"
"anrm_0000037 "FR" "FR-OCC" "12" "12"

1"
"anrm_0000037 "FR" "FR-PAC" "13" "13"

2"
"anrm_0000037 "FR" "FR-NOR" "14" "14"

3"
"anrm_0000037 "FR" "FR-ARA" "15" "15"

4"
"anrm_0000037 "FR" "FR-NAQ" "16" "16"

5"

"anrm_0000037 "FR" "FR-NAQ" "17" "17"

6"
"anrm_0000037 "FR" "FR-CVL" "18" "18"

7"
"anrm_0000037 "FR" "FR-NAQ" "19" "19"

8"
"anrm_0000037 "FR" "FR-BFC" "21" "21"

9"
"anrm_0000038 "FR" "FR-BRE" "22" "22"

0"
"anrm_0000038 "FR" "FR-NAQ" "23" "23"

1"
"anrm_0000038 "FR" "FR-NAQ" "24" "24"

2"
"anrm_0000038 "FR" "FR-BFC" "25" "25"

3"
"anrm_0000038 "FR" "FR-ARA" "26" "26"

4"
"anrm_0000038 "FR" "FR-NOR" "27" "27"

5"
"anrm_0000038 "FR" "FR-CVL" "28" "28"

6"
"anrm_0000038 "FR" "FR-BRE" "29" "29"

7"
"anrm_0000038 "FR" "FR-COR" "2A" "2A"

8"
"anrm_0000038 "FR" "FR-COR" "2B" "2B"

9"
"anrm_0000039 "FR" "FR-OCC" "30" "30"

0"
"anrm_0000039 "FR" "FR-OCC" "31" "31"

1"
"anrm_0000039 "FR" "FR-OCC" "32" "32"

2"
"anrm_0000039 "FR" "FR-NAQ" "33" "33"

3"
"anrm_0000039 "FR" "FR-OCC" "34" "34"

4"

"anrm_0000039 "FR" "FR-BRE" "35" "35"

5"
"anrm_0000039 "FR" "FR-CVL" "36" "36"

6"
"anrm_0000039 "FR" "FR-CVL" "37" "37"

7"
"anrm_0000039 "FR" "FR-ARA" "38" "38"

8"
"anrm_0000039 "FR" "FR-BFC" "39" "39"

9"
"anrm_0000040 "FR" "FR-NAQ" "40" "40"

0"
"anrm_0000040 "FR" "FR-CVL" "41" "41"

1"
"anrm_0000040 "FR" "FR-ARA" "42" "42"

2"
"anrm_0000040 "FR" "FR-ARA" "43" "43"

3"
"anrm_0000040 "FR" "FR-PDL" "44" "44"

4"
"anrm_0000040 "FR" "FR-CVL" "45" "45"

5"
"anrm_0000040 "FR" "FR-OCC" "46" "46"

6"
"anrm_0000040 "FR" "FR-NAQ" "47" "47"

7"
"anrm_0000040 "FR" "FR-OCC" "48" "48"

8"
"anrm_0000040 "FR" "FR-PDL" "49" "49"

9"
"anrm_0000041 "FR" "FR-PAC" "04" "04"

0"
"anrm_0000041 "FR" "FR-NOR" "50" "50"

1"
"anrm_0000041 "FR" "FR-GES" "51" "51"

2"
"anrm_0000041 "FR" "FR-GES" "52" "52"

3"

"anrm_0000041 "FR" "FR-PDL" "53" "53"

4"
"anrm_0000041 "FR" "FR-GES" "54" "54"

5"
"anrm_0000041 "FR" "FR-GES" "55" "55"

6"
"anrm_0000041 "FR" "FR-BRE" "56" "56"

7"
"anrm_0000041 "FR" "FR-GES" "57" "57"

8"
"anrm_0000041 "FR" "FR-BFC" "58" "58"

9"
"anrm_0000042 "FR" "FR-HDF" "59" "59"

0"
"anrm_0000042 "FR" "FR-HDF" "60" "60"

1"
"anrm_0000042 "FR" "FR-NOR" "61" "61"

2"
"anrm_0000042 "FR" "FR-HDF" "62" "62"

3"
"anrm_0000042 "FR" "FR-ARA" "63" "63"

4"
"anrm_0000042 "FR" "FR-NAQ" "64" "64"

5"
"anrm_0000042 "FR" "FR-OCC" "65" "65"

6"
"anrm_0000042 "FR" "FR-OCC" "66" "66"

7"
"anrm_0000042 "FR" "FR-GES" "67" "67"

8"
"anrm_0000042 "FR" "FR-GES" "68" "68"

9"
"anrm_0000043 "FR" "FR-ARA" "69" "69"

0"
"anrm_0000043 "FR" "FR-BFC" "70" "70"

1"
"anrm_0000043 "FR" "FR-BFC" "71" "71"

2"

"anrm_0000043 "FR" FR-PDL" "72" "72"

3"
"anrm_0000043 "FR" "FR-ARA" "73" "73"

4"
"anrm_0000043 "FR" "FR-ARA" "74" "74"

5"
"anrm_0000043 "FR" "FR-IDF" "75" "75"

6"
"anrm_0000043 "FR" "FR-NOR" "76" "76"

7"
"anrm_0000043 "FR" "FR-IDF" "77" "77"

8"
"anrm_0000043 "FR" "FR-IDF" "78" "78"

9"
"anrm_0000044 "FR" "FR-NAQ" "79" "79"

0"
"anrm_0000044 "FR" "FR-HDF" "80" "80"

1"
"anrm_0000044 "FR" "FR-OCC" "81" "81"

2"
"anrm_0000044 "FR" "FR-OCC" "82" "82"

3"
"anrm_0000044 "FR" "FR-PAC" "83" "83"

4"
"anrm_0000044 "FR" "FR-PAC" "84" "84"

5"
"anrm_0000044 "FR" "FR-PDL" "85" "85"

6"
"anrm_0000044 "FR" "FR-NAQ" "86" "86"

7"
"anrm_0000044 "FR" "FR-NAQ" "87" "87"

8"
"anrm_0000044 "FR" "FR-GES" "88" "88"

9"
"anrm_0000045 "FR" "FR-BFC" "89" "89"

0"
"anrm_0000045 "FR" "FR_BFC"" "90" "90"

1"

"anrm_0000045 "FR" "FR-IDF" "91" "91"

2"
"anrm_0000045 "FR" FR-IDF" "92" "92"

3"
"anrm_0000045 "FR" FR-IDF" "93" "93"

4"
"anrm_0000045 "FR" FR-IDF" "94" "94"

5"
"anrm_0000045 "FR" "FR-IDF" "95" "95"

6"
"anrm_0000045 "GB" "GB-ORK" "OR" "ORK"

7"
"anrm_0000045 "GB" "GB-WAR" "WA" "WAR"

8"
"anrm_0000045 "GB" "GB-BGW" "MM" "BGW"

9"
"anrm_0000046 "GB" "GB-HEF" "HW" "HEF"

0"
"anrm_0000046 "GB" "GB-MLN" "MD" "MLN"

1"
"anrm_0000046 "GB" "GB-HRT" "HT" "HRT"

2"
"anrm_0000046 "GB" "GB-ZET" "SL" "ZET"

3"
"anrm_0000046 "GB" "GB-ELN" "EL" "ELN"

4"
"anrm_0000046 "GB" "GB-WOR" "WC" "WOR"

5"
"anrm_0000046 "GB" "GB-HAM" "HA" "HAM"

6"
"anrm_0000046 "GB" "GB-RFW" "RE" "RFW"

7"
"anrm_0000046 "GB" "GB-SHR" "SH" "SHR"

8"
"anrm_0000046 "GB" "GB-BDF" "BE" "BDF"

9"
"anrm_0000047 "GB" "GB-ABD" "AB" "ABD"

0"

"anrm_0000047 "GB" "GB_ARM" "AM" "ARM"

1"
"anrm_0000047 "GB" "GB-POW" "MT" "POW"

2"
"anrm_0000047 "GB" "GB-DGY" "DF" "DGY"

3"
"anrm_0000047 "GB" "GB-KEN" "KE" "KEN"

4"
"anrm_0000047 "GB" "GB-RCC" "YN" "RCC"

5"
"anrm_0000047 "GB" "GB-LIN" "LI" "LIN"

6"
"anrm_0000047 "GB" "GB-SFK" "SK" "SFK"

7"
"anrm_0000047 "GB" "GB-GLS" "GL" "GLS"

8"
"anrm_0000047 "GB" "GB-DEV" "DV" "DEV"

9"
"anrm_0000048 "GB" "GB-WLN" "WK" "WLN"

0"
"anrm_0000048 "GB" "GB-STS" "ST" "STS"

1"
"anrm_0000048 "GB" "GB-ANS" "AN" "ANS"

2"
"anrm_0000048 "GB" "GB-VGL" "MG" "VGL"

3"
"anrm_0000048 "GB" "GB-WIL" "WI" "WIL"

4"
"anrm_0000048 "GB" "GB-IOW" "IW" "IOW"

5"
"anrm_0000048 "GB" "GB-IOS" "CO" "IOS"

6"
"anrm_0000048 "GB" "GB-LEC" "LE" "LEC"

7"
"anrm_0000048 "GB" "GB-FIF" "FI" "FIF"

8"
"anrm_0000048 "GB" "GB-DUR" "DU" "DUR"

9"

"anrm_0000049 "GB" "GB-NYK" "YN" "NYK"

0"
"anrm_0000049 "GB" "GB-SRY" "SY" "SRY"

1"
"anrm_0000049 "GB" "GB-OXF" "OX" "OXF

2"
"anrm_0000049 "GB" "GB-LAN" "LA" "LAN"

3"
"anrm_0000049 "GB" "GB-CAM" "CA" "CAM"

4"
"anrm_0000049 "GB" "GB-DBY" "DB" "DBY"

5"
"anrm_0000049 "GB" "GB-NFK" "NK" "NFK"

6"
"anrm_0000049 "GB" "GB-NTT" "NT" "NTT"

7"
"anrm_0000049 "GB" "GB-SND" "SU" "SND"

8"
"anrm_0000049 "GB" "GB-NTH" "NH" "NTH"

9"
"anrm_0000050 "GB" "GB-SOM" "SO" "SOM"

0"
"anrm_0000050 "GB" "GB-ESX" "SE" "ESX"

1"
"anrm_0000050 "GB" "GB-ESS" "ESS" "ESS"

2"
"anrm_0000050 "GB" "GB-CON" "CO" "CON"

3"
"anrm_0000050 "GB" "GB-GWN" "CF" "GWN"

4"
"anrm_0000050 "GB" "GB-NAY" "AY" "NAY"

5"
"anrm_0000050 "GB" "GB-CLK" "CN" "CLK"

6"
"anrm_0000050 "GB" "GB-WSX" "SW" "WSX"

7"
"anrm_0000050 "GB" "GB-DOR" "DO" "DOR"

8"

"anrm_0000050 "GB" "GB-BKM" "BU" "BKM"

9"
"anrm_0000051 "GB" "GB-NBL" "NU" "NBL"

0"
"anrm_0000051 "GB" "GB-CMA" "CU" "CMA"

1"
"anrm_0000051 "GB" "GB-SOM" "BS" "SOM"

2"
"anrm_0000051 "GB" "GB-BFD" "YW" "NYK"

3"
"anrm_0000051 "GB" "GB-CLD" "YW" "NYK"

4"
"anrm_0000051 "GB" "GB-KIR" "YW" "NYK"

5"
"anrm_0000051 "GB" "GB-LDS" "YW" "NYK"

6"
"anrm_0000051 "GB" "GB-WKF" "YW" "NYK"

7"
"anrm_0000051 "GB" "GB-BNS" "YS" "NYK"

8"
"anrm_0000051 "GB" "GB-DNC" "YS" "NYK"

9"
"anrm_0000052 "GB" "GB" "GB-ROT" "YS"

0"
"anrm_0000052 "GB" "GB-SHF" "YS" "NYK"

1"
"anrm_0000052 "GB" "GB-SOM" "BS" "SOM"

2"
"anrm_0000052 "GB" "GB-AGY" "AL" "GWN"

3"
"anrm_0000052 "GB" "GB-GWN" "ME" "GWN"

4"
"anrm_0000052 "GB" "GB-DEN" "DD" "GWN"

5"
"anrm_0000052 "GB" "GB-FLN" "FL" "GWN"

6"
"anrm_0000052 "GB" "GB-GWN" "ME" "GWN"

7"

"anrm_0000052 "GB" "GB-BRC" "BF" "ABD"

8"
"anrm_0000052 "GB" "GB-RDG" "BF" "ABD"

9"
"anrm_0000053 "GB" "GB-SLG" "BF" "ABD"

0"
"anrm_0000053 "GB" "GB-WBK" "BF" "ABD"

1"
"anrm_0000053 "GB" "GB-WNM" "BF" "ABD"

2"
"anrm_0000053 "GB" "GB-WOK" "BF" "ABD"

3"
"anrm_0000053 "GB" "GB-ABD" "KI" "ABD"

4"
"anrm_0000053 "GB" "GB-ABD" "MR" "ABD"

5"
"anrm_0000053 "GB" "GB-ABD" "NR" "ABD"

6"
"anrm_0000053 "GB" "GB-ANS" "AN" "ANS"

7"
"anrm_0000053 "GB" "GB-ANN" "AT" "ANT"

8"
"anrm_0000053 "GB" "GB-AND" "AT" "ANT"

9"
"anrm_0000054 "GB" "GB-ABC" "AT" "ANT"

0"
"anrm_0000054 "GB" "GB-BFS" "AT" "ANT"

1"
"anrm_0000054 "GB" GB-LBC" "AT" "ANT"

2"
"anrm_0000054 "GB" "GB-ARM" "TY" "ARM"

3"
"anrm_0000054 "GB" "GB-CAM" "HU" "CAM"

4"
"anrm_0000054 "GB" "GB-CMA" "WE" "CMA"

5"
"anrm_0000054 "GB" "GB-CGN" "CD" "DFD"

6"

"anrm_0000054 "GB" "GB-PEM" "PM" "DFD"

7"
"anrm_0000054 "GB" "GB-DGY" "BW" "DGY"

8"
"anrm_0000054 "GB" "GB-DGY" "KK" "DGY"

9"
"anrm_0000055 "GB" "GB-NLK" "LN" "DGY"

0"
"anrm_0000055 "GB" "GB-SLK" "LN" "DGY"

1"
"anrm_0000055 "GB" "GB-DGY" "PE" "DGY"

2"
"anrm_0000055 "GB" "GB-DGY" "RX" "DGY"

3"
"anrm_0000055 "GB" "GB-DGY" "SF" "DGY"

4"
"anrm_0000055 "GB" "GB-DGY" "SV" "DGY"

5"
"anrm_0000055 "GB" "GB-FIF" "KN" "FIF"

6"
"anrm_0000055 "GB" "GB-FIF" "PR" "FIF"

7"
"anrm_0000055 "GB" "GB-HRT" "MX" "HRT"

8"
"anrm_0000055 "GB" "GB-RUT" "RU" "LEC"

9"
"anrm_0000056 "GB" "GB-AGB" "AG" "NAY"

0"
"anrm_0000056 "GB" "GB-AGB" "BT" "NAY"

1"
"anrm_0000056 "GB" "GB-EDU" "DT" "NAY"

2"
"anrm_0000056 "GB" "GB-WDU" "DT" "NAY"

3"
"anrm_0000056 "GB" "GB-NAY" "WT" "NAY"

4"
"anrm_0000056 "GB" "GB-OXF" "BK" "OXF"

5"

"anrm_0000056 "GB" "GB-POW" "BR" "POW"

6"
"anrm_0000056 "GB" "GB-POW" "RA" "POW"

7"
"anrm_0000056 "GB" "GB-SND" "CM" "SND"

8"
"anrm_0000056 "GB" "GB-SND" "CT" "SND"

9"
"anrm_0000057 "GB" "GB-SND" "IN" "SND"

0"
"anrm_0000057 "GB" "GB-SND" "RO" "SND"

1"
"anrm_0000057 "GR" "GR-G" "01" "01"

2"
"anrm_0000057 "GR" "GR-H" "50" "03"

3"
"anrm_0000057 "GR" "GR-H" "11" "04"

4"
"anrm_0000057 "GR" "GR-H" "09" "05"

5"
"anrm_0000057 "GR" "GR-H" "14" "06"

6"
"anrm_0000057 "GR" "GR-H" "13" "07"

7"
"anrm_0000057 "GR" "GR-J" "13" "07"

8"
"anrm_0000057 "GR" "GR-J" "03" "11"

9"
"anrm_0000058 "GR" "GR-J" "04" "12"

0"
"anrm_0000058 "GR" "GR-G" "02" "13"

1"
"anrm_0000058 "GR" "GR-G" "16" "14"

2"
"anrm_0000058 "GR" "GR-J" "30" "15"

3"
"anrm_0000058 "GR" "GR-J" "32" "16"

4"

"anrm_0000058 "GR" "GR-J" "38" "17"

5"
"anrm_0000058 "GR" "GR-F" "52" "21"

6"
"anrm_0000058 "GR" "GR-F" "24" "22"

7"
"anrm_0000058 "GR" "GR-F" "23" "23"

8"
"anrm-0000058 "GR" "GR-F" "24" "36"

9"
"anrm_0000059 "GR" GR-D" "05" "31"

0"
"anrm_0000059 "GR" "GR-D" "47" "32"

1"
"anrm_0000059 "GR" "GR-D" "18" "33"

2"
"anrm_0000059 "GR" "GR-D" "42" "34"

3"
"anrm_0000059 "GR" "GR-E" "20" "41"

4"
"anrm_0000059 "GR" "GR-E" "33" "42"

5"
"anrm_0000059 "GR" "GR-E" "37" "43"

6"
"anrm_0000059 "GR" "GR-E" "49" "44"

7"
"anrm_0000059 "GR" "GR-C" "15" "51"

8"
"anrm_0000059 "GR" "GR-A" "08" "52"

9"
"anrm_0000060 "GR" "GR-B" "17" "53"

0"
"anrm_0000060 "GR" "GR-B" "48" "54"

1"
"anrm_0000060 "GR" "GR-A" "22" "55"

2"
"anrm_0000060 "GR" "GR-C" "21" "56"

3"

"anrm_0000060 "GR" "GR-B" "29" "57"

4"
"anrm_0000060 "GR" "GR-C" "31" "58"

5"
"anrm_0000060 "GR" "GR-B" "39" "59"

6"
"anrm_0000060 "GR" "GR-B" "40" "61"

7"
"anrm-0000060 "GR" "GR-B" "46" "62"

8"
"anrm_0000060 "GR" "GR-C" "12" "63"

9"
"anrm_0000061 "GR" "GR-B" "25" "64"

0"
"anrm_0000061 "GR" "GR-A" "10" "71"

1"
"anrm_0000061 "GR" "GR-A" "51" "72"

2"
"anrm_0000061 "GR" "GR-A" "44" "73"

3"
"anrm_0000061 "GR" "GR-L" "07" "81"

4"
"anrm_0000061 "GR" "GR-L" "28" "82"

5"
"anrm_0000061 "GR" "GR-K" "35" "83"

6"
"anrm_0000061 "GR" "GR-K" "45" "84"

7"
"anrm_0000061 "GR" "GR-K" "27" "85"

8"
"anrm_0000061 "GR" "GR-M" "19" "91"

9"
"anrm_0000062 "GR" "GR-M" "34" "92"

0"
"anrm_0000062 "GR" "GR-M" "43" "93"

1"
"anrm_0000062 "GR" "GR-M" "26" "94"

2"

"anrm_0000062 "GR" "GR-I" "06" "A1"

3"
"anrm_0000062 "GR" "GR-I" "41" "A1"

4"
"anrm_0000062 "HR" "HR-09" "I00" "09"

5"
"anrm_0000062 "HR" "HR-05" "E00" "05"

6"
"anrm_0000062 "HR" "HR-16" "P00" "16"

7"
"anrm_0000062 "HR" "HR-06" "F00" "06"

8"
"anrm_0000629 "HR" "HR-17" "R00" "17"

"
"anrm_0000063 "HR" "HR-07" "G00" "07"

0"
"anrm_0000063 "HR" "HR-18" "S00" "18"

1"
"anrm_0000063 "HR" "HR-08" "H00" "08"

2"
"anrm_0000063 "HR" "HR-19" "T00" "19"

3"
"anrm_0000063 "HR" "HR-01" "A00" "01"

4"
"anrm_0000063 "HR" "HR-12" "L00" "12"

5"
"anrm_0000063 "HR" "HR-02" "B00" "02"

6"
"anrm_0000063 "HR" "HR-13" "M00" "13"

7"
"anrm_0000063 "HR" "HR-03" "C00" "03"

8"
"anrm_0000063 "HR" "HR-14" "N00" "14"

9"
"anrm_0000064 "HR" "HR-04" "D00" "04"

0"
"anrm_0000064 "HR" "HR-15" "O00" "15"

1"

"anrm_0000064 "HR" "HR-20" "U00" "20"

2"
"anrm_0000064 "HR" "HR-10" "J00" "10"

3"
"anrm_0000064 "HR" "HR-21" "V00" "21"

4"
"anrm_0000064 "HR" "HR-11" "K00" "11"

5"
"anrm_0000064 "ID" "ID-PB" "26" "PB"

6"
"anrm_0000064 "ID" "ID-NB" "23" "NB"

7"
"anrm_0000064 "ID" "ID-LA" "13" "LA"

8"
"anrm_0000064 "ID" "ID-PA" "26" "PA"

9"
"anrm_0000065 "ID" "ID-JA" "10" "JA"

0"
"anrm_0000065 "ID" "ID-RI" "09" "RI"

1"
"anrm_0000065 "ID" "ID-JB" "02" "JB"

2"
"anrm_0000065 "ID" "ID-BE" "12" "BE"

3"
"anrm_0000065 "ID" "ID-BA" "22" "BA"

4"
"anrm_0000065 "ID" "ID-JI" "04" "JI"

5"
"anrm_0000065 "ID" "ID-BB" "11" "BB"

6"
"anrm_0000065 "ID" "ID-JK" "01" "JK"

7"
"anrm_0000065 "ID" "ID-JT" "03" "JT"

8"
"anrm_0000065 "ID" "ID-NT" "24" "NT"

9"
"anrm_0000066 "ID" "ID-BT" "02" "BT"

0"

"anrm_0000066 "ID" "ID-MA" "25" "MA"

1"
"anrm_0000066 "ID" "ID-SG" "19" "SG"

2"
"anrm_0000066 "ID" "ID-SA" "21" "SA"

3"
"anrm_0000066 "ID" "ID-SB" "09" "SB"

4"
"anrm_0000066 "ID" "ID-SN" "18" "SN"

5"
"anrm_0000066 "ID" "ID-YO" "05" "YO"

6"
"anrm_0000066 "ID" "ID-KB" "15" "KB"

7"
"anrm_0000066 "ID" "ID-AC" "06" "AC"

8"
"anrm_0000066 "ID" "ID-SU" "07" "SU"

9"
"anrm_0000067 "ID" "ID-KI" "17" "KI"

0"
"anrm_0000067 "ID" "ID-SR" "18" "SR"

1"
"anrm_0000067 "ID" "ID-SS" "11" "SS"

2"
"anrm_0000067 "ID" "ID-ST" "20" "ST"

3"
"anrm_0000067 "ID" "ID-KR" "09" "KR"

4"
"anrm_0000067 "ID" "ID-GO" "21" "GO"

5"
"anrm_0000067 "ID" "ID-KS" "14" "KS"

6"
"anrm_0000067 "ID" "ID-MU" "25" "MU"

7"
"anrm_0000067 "ID" "ID-KT" "16" "KT"

8"
"anrm_0000067 "IE" "IE-WH" "WH" "WH"

9"

"anrm_0000068 "IE" "IE-MH" "MH" "MH"

0"
"anrm_0000068 "IE" "IE-SO" "SO" "SO"

1"
"anrm_0000068 "IE" "IE-KE" "KE" "KE"

2"
"anrm_0000068 "IE" "IE-KK" "KK" "KK"

3"
"anrm_0000068 "IE" "IE-WW" "WW" "WW"

4"
"anrm_0000068 "IE" "IE-MN" "MN" "MN"

5"
"anrm_0000068 "IE" "IE-WX" "WX" "WX"

6"
"anrm_0000068 "IE" "IE-CE" "CE" "CE"

7"
"anrm_0000068 "IE" "IE-MO" "MO" "MO"

8"
"anrm_0000068 "IE" "IE-CN" "CN" "CN"

9"
"anrm_0000069 "IE" "IE-TA" "TA" "TA"

0"
"anrm_0000069 "IE" "IE-KY" "KY" "KY"

1"
"anrm_0000069 "IE" "IE-OY" "OY" "OY"

2"
"anrm_0000069 "IE" "IE-CW" "CW" "CW"

3"
"anrm_0000069 "IE" "IE-LH" "LH" "LH"

4"
"anrm_0000069 "IE" "IE-RN" "RN" "RN"

5"
"anrm_0000069 "IE" "IE-LD" "LD" "LD"

6"
"anrm_0000069 "IE" "IE-D" "D" "D"

7"
"anrm_0000069 "IE" "IE-G" "G" "G"

8"

"anrm_0000069 "IE" "IE-LK" "LK" "LK"

9"
"anrm_0000070 "IE" "IE-LM" "LM" "LM"

0"
"anrm_0000070 "IE" "IE-WD" "WD" "WD"

1"
"anrm_0000070 "IE" "IE-LS" "LS" "LS"

2"
"anrm_0000070 "IE" "IE-DL" "DL" "DL"

3"
"anrm_0000070 "IT" "IT-BI" "BI" "BI"

4"
"anrm_0000070 "IT" "IT-BO" "BO" "BO"

5"
"anrm_0000070 "IT" "IT-BN" "BN" "BN"

6"
"anrm_0000070 "IT" "IT-BL" "BL" "BL"

7"
"anrm_0000070 "IT" "IT-BA" "BA" "BA"

8"
"anrm_0000070 "IT" "IT-BG" "BG" "BG"

9"
"anrm_0000071 "IT" "IT-BZ" "BZ" "BZ"

0"
"anrm_0000071 "IT" "IT-SI" "SI" "SI"

1"
"anrm_0000071 "IT" "IT-SP" "SP" "SP"

2"
"anrm_0000071 "IT" "IT-SO" "SO" "SO"

3"
"anrm_0000071 "IT" "IT-BS" "BS" "BS"

4"
"anrm_0000071 "IT" "IT-BR" "BR" "BR"

5"
"anrm_0000071 "IT" "IT-SA" "SA" "SA"

6"
"anrm_0000071 "IT" "IT-BT" "BT" "BT"

7"

"anrm_0000071 "IT" "IT-AG" "AG" "AG"

8"
"anrm_0000071 "IT" "IT-AN" "AN" "AN"

9"
"anrm_0000072 "IT" "IT-AL" "AL" "AL"

0"
"anrm_0000072 "IT" "IT-IS" "IS" "IS"

1"
"anrm_0000072 "IT" "IT-IM" "IM" "IM"

2"
"anrm_0000072 "IT" "IT-RI" "RI" "RI"

3"
"anrm_0000072 "IT" "IT-RO" "RO" "RO"

4"
"anrm_0000072 "IT" "IT-RN" "RN" "RN"

5"
"anrm_0000072 "IT" "IT-RM" "RM" "RM"

6"
"anrm_0000072 "IT" "IT-AR" "AR" "AR"

7"
"anrm_0000072 "IT" "IT-RC" "RC" "RC"

8"
"anrm_0000072 "IT" "IT-AQ" "AQ" "AQ"

9"
"anrm_0000073 "IT" "IT-AP" "AP" "AP"

0"
"anrm_0000073 "IT" "IT-RA" "RA" "RA"

1"
"anrm_0000073 "IT" "IT-AO" "AO" "AO"

2"
"anrm_0000073 "IT" "IT-AV" "AV" "AV"

3"
"anrm_0000073 "IT" "IT-RG" "RG" "RG"

4"
"anrm_0000073 "IT" "IT-AT" "AT" "AT"

5"
"anrm_0000073 "IT" "IT-RE" "RE" "RE"

6"

"anrm_0000073 "IT" "IT-LU" "LU" "LU"

7"
"anrm_0000073 "IT" "IT-LT" "LT" "LT"

8"
"anrm_0000073 "IT" "IT-TS" "TS" "TS"

9"
"anrm_0000074 "IT" "IT-TR" "TR" "TR"

0"
"anrm_0000074 "IT" "IT-LO" "LO" "LO"

1"
"anrm_0000074 "IT" "IT-TV" "TV" "TV"

2"
"anrm_0000074 "IT" "IT-ME" "ME" "ME"

3"
"anrm_0000074 "IT" "IT-MC" "MC" "MC"

4"
"anrm_0000074 "IT" "IT-MI" "MI" "MI"

5"
"anrm_0000074 "IT" "IT-UD" "UD" "UD"

6"
"anrm_0000074 "IT" "IT-MB" "MB" "MB"

7"
"anrm_0000074 "IT" "IT-CL" "CL" "CL"

8"
"anrm_0000074 "IT" "IT-KR" "KR" "KR"

9"
"anrm_0000075 "IT" "IT-CI" "CI" "CI"

0"
"anrm_0000075 "IT" "IT-TA" "TA" "TA"

1"
"anrm_0000075 "IT" "IT-CO" "CO" "CO"

2"
"anrm_0000075 "IT" "IT-CN" "CN" "CN"

3"
"anrm_0000075 "IT" "IT-SS" "SS" "SS"

4"
"anrm_0000075 "IT" "IT-CB" "CB" "CB"

5"

"anrm_0000075 "IT" "IT-SR" "SR" "SR"

6"
"anrm_0000075 "IT" "IT-CA" "CA" "CA"

7"
"anrm_0000075 "IT" "IT-CH" "CH" "CH"

8"
"anrm_0000075 "IT" "IT-SV" "SV" "SV"

9"
"anrm_0000076 "IT" "IT-CE" "CE" "CE"

0"
"anrm_0000076 "IT" "IT-LE" "LE" "LE"

1"
"anrm_0000076 "IT" "IT-CZ" "CZ" "CZ"

2"
"anrm_0000076 "IT" "IT-LC" "LC" "LC"

3"
"anrm_0000076 "IT" "IT-LI" "LI" "LI"

4"
"anrm_0000076 "IT" "IT-TP" "TP" "TP"

5"
"anrm_0000076 "IT" "IT-TO" "TO" "TO"

6"
"anrm_0000076 "IT" "IT-TN" "TN" "TN"

7"
"anrm_0000076 "IT" "IT-CT" "CT" "CT"

8"
"anrm_0000076 "IT" "IT-TE" "TE" "TE"

9"
"anrm_0000077 "IT" "IT-CS" "CS" "CS"

0"
"anrm_0000077 "IT" "IT-CR" "CR" "CR"

1"
"anrm_0000077 "IT" "IT-FM" "FM" "FM"

2"
"anrm_0000077 "IT" "IT-NU" "NU" "NU"

3""
"anrm_0000077 "IT" "IT-FR" "FR" "FR"

4"

"anrm_0000077 "IT" "IT-FG" "FG" "FG"

5"
"anrm_0000077 "IT" "IT-NO" "NO" "NO"

6"
"anrm_0000077 "IT" "IT-VV" "VV" "VV"

7"
"anrm_0000077 "IT" "IT-FE" "FE" "FE"

8"
"anrm_0000077 "IT" "IT-VT" "VT" "VT"

9"
"anrm_0000078 "IT" "IT-FI" "FI" "FI"

0"
"anrm_0000078 "IT" "IT-OG" "OG" "OG"

1"
"anrm_0000078 "IT" "IT-EN" "EN" "EN"

2"
"anrm_0000078 "IT" "IT-MT" "MT" "MT"

3"
"anrm_0000078 "IT" "IT-MS" "MS" "MS"

4"
"anrm_0000078 "IT" "IT-VC" "VC" "VC"

5"
"anrm_0000078 "IT" "IT-VB" "VB" "VB"

6"
"anrm_0000078 "IT" "IT-VA" "VA" "VA"

7"
"anrm_0000078 "IT" "IT-MN" "MN" "MN"

8"
"anrm_0000078 "IT" "IT-MO" "MO" "MO"

9"
"anrm_0000079 "IT" "IT-FC" "FC" "FC"

0"
"anrm_0000079 "IT" "IT-VS" "VS" "VS"

1"
"anrm_0000079 "IT" "IT-VR" "VR" "VR"

2"
"anrm_0000079 "IT" "IT-VE" "VE" "VE"

3"

"anrm_0000079 "IT" "IT-HA" "HA" "HA"

4"
"anrm_0000079 "IT" "IT-VI" "VI" "VI"

5"
"anrm_0000079 "IT" "IT-PV" "PV" "PV"

6"
"anrm_0000079 "IT" "IT-PZ" "PZ" "PZ"

7"
"anrm_0000079 "IT" "IT-PO" "PO" "PO"

8"
"anrm_0000079 "IT" "IT-PN" "PN" "PN"

9"
"anrm_0000080 "IT" "IT-PU" "PU" "PU"

0"
"anrm_0000080 "IT" "IT-PT" "PT" "PT"

1"
"anrm_0000080 "IT" "IT-PR" "PR" "PR"

2"
"anrm_0000080 "IT" "IT-GO" "GO" "GO"

3"
"anrm_0000080 "IT" "IT-GR" "GR" "GR"

4"
"anrm_0000080 "IT" "IT-GE" "GE" "GE"

5"
"anrm_0000080 "IT" "IT-OT" "OT" "OT"

6"
"anrm_0000080 "IT" "IT-OR" "OR" "OR"

7"
"anrm_0000080 "IT" "IT-PI" "PI" "PI"

8"
"anrm_0000080 "IT" "IT-PG" "PG" "PG"

9"
"anrm_0000081 "IT" "IT-PA" "PA" "PA"

0"
"anrm_0000081 "IT" "IT-PE" "PE" "PE"

1"
"anrm_0000081 "IT" "IT-PD" "PD" "PD"

2"

"anrm_0000081 "IT" "IT-PC" "PC" "PC"

3"
"anrm_0000081 "JP" "JP-09" "09" "09"

4"
"anrm_0000081 "JP" "JP-22" "22" "22"

5"
"anrm_0000081 "JP" "JP-44" "44" "44"

6"
"anrm_0000081 "JP" "JP-21" "21" "21"

7"
"anrm_0000081 "JP" "JP-43" "43" "43"

8"
"anrm_0000081 "JP" "JP-20" "20" "20"

9"
"anrm_0000082 "JP" "JP-42" "42" "42"

0"
"anrm_0000082 "JP" "JP-41" "41" "41"

1"
"anrm_0000082 "JP" "JP-40" "40" "40"

2"
"anrm_0000082 "JP" "JP-08" "08" "08"

3"
"anrm_0000082 "JP" "JP-07" "07" "07"

4"
"anrm_0000082 "JP" "JP-29" "29" "29"

5"
"anrm_0000082 "JP" "JP-06" "05" "06"

6"
"anrm_0000082 "JP" "JP-28" "28" "28"

7"
"anrm_0000082 "JP" "JP-05" "05" "05"

8"
"anrm_0000082 "JP" "JP-27" "27" "27"

9"
"anrm_0000083 "JP" "JP-04" "04" "04"

0"
"anrm_0000083 "JP" "JP-26" "26" "26"

1"

"anrm_0000083 "JP" "JP-03" "03" "03"

2"
"anrm_0000083 "JP" "JP-25" "25" "25"

3"
"anrm_0000083 "JP" "JP-47" "47" "47"

4"
"anrm_0000083 "JP" "JP-02" "02" "02"

5"
"anrm_0000083 "JP" "JP-24" "24" "24"

6"
"anrm_0000083 "JP" "JP-46" "46" "46"

7"
"anrm_0000083 "JP" "JP-01" "01" "01"

8"
"anrm_0000083 "JP" "JP-23" "23" "23"

9"
"anrm_0000084 "JP" "JP-45" "45" "45"

0"
"anrm_0000084 "JP" "JP-11" "11" "11"

1"
"anrm_0000084 "JP" "JP-33" "33" "33"

2"
"anrm_0000084 "JP" "JP-10" "10" "10"

3"
"anrm_0000084 "JP" "JP-32" "32" "32"

4"
"anrm_0000084 "JP" "JP-31" "31" "31"

5"
"anrm_0000084 "JP" "JP-30" "30" "30"

6"
"anrm_0000084 "JP" "JP-19" "19" "19"

7"
"anrm_0000084 "JP" "JP-18" "18" "18"

8"
"anrm_0000084 "JP" "JP-17" "17" "17"

9"
"anrm_0000085 "JP" "JP-39" "39" "39"

0"

"anrm_0000085 "JP" "JP-16" "16" "16"

1"
"anrm_0000085 "JP" "JP-38" "38" "38"

2"
"anrm_0000085 "JP" "JP-15" "15" "15"

3"
"anrm_0000085 "JP" "JP-37" "37" "37"

4"
"anrm_0000085 "JP" "JP-14" "14" "14"

5"
"anrm_0000085 "JP" "JP-36" "36" "36"

6"
"anrm_0000085 "JP" "JP-13" "13" "13"

7"
"anrm_0000085 "JP" "JP-35" "35" "35"

8"
"anrm_0000085 "JP" "JP-12" "12" "12"

9"
"anrm_0000086 "JP" "JP-34" "34" "34"

0"
"anrm_0000086 "KR" "KR-11" "13" "11"

1"
"anrm_0000086 "KR" "KR-44" "05" "44"

2"
"anrm_0000086 "KR" "KR-45" "02" "45"

3"
"anrm_0000086 "KR" "KR-31" "16" "31"

4"
"anrm_0000086 "KR" "KR-42" "07" "42"

5"
"anrm_0000086 "KR" "KR-43" "04" "43"

6"
"anrm_0000086 "KR" "KR-30" "15" "30"

7"
"anrm_0000086 "KR" "KR-41" "09" "41"

8"
"anrm_0000086 "KR" "KR-28" "06" "28"

9"

"anrm_0000087 "KR" "KR-29" "08" "29"

0"
"anrm_0000087 "KR" "KR-26" "12" "26"

1"
"anrm_0000087 "KR" "KR-48" "11" "48"

2"
"anrm_0000087 "KR" "KR-27" "14" "27"

3"
"anrm_0000087 "KR" "KR-49" "01" "49"

4"
"anrm_0000087 "KR" "KR-46" "03" "46"

5"
"anrm_0000087 "KR" "KR-47" "10" "47"

6"
"anrm_0000087 "KW" "KW-KU" "KW" "KW"

7"
"anrm_0000087 "KZ" "KZ-AKM" "04" "AKM"

8"
"anrm_0000087 "KZ" "KZ-ALM" "00" "ALM"

9"
"anrm_0000088 "KZ" "KZ-AST" "04" "AST"

0"
"anrm_0000088 "KZ" "KZ-PAV" "03" "PAV"

1"
"anrm_0000088 "KZ" "KZ-SEV" "02" "SEV"

2"
"anrm_0000088 "KZ" "KZ-YUZ" "11" "YUZ"

3"
"anrm_0000088 "KZ" "KZ-AKT" "05" "AKT"

4"
"anrm_0000088 "KZ" "KZ-KZY" "12" KZY"

5"
"anrm_0000088 "KZ" "KZ-ATY" "06" "ATY"

6"
"anrm_0000088 "KZ" "KZ-KUS" "02" "KUS"

7"
"anrm_0000088 "KZ" "KZ-ZAP" "07" "ZAP"

8"

"anrm_0000088 "KZ" "KZ-ZHA" "11" "ZHA"

9"
"anrm_0000089 "KZ" "KZ-BAY" "12" "BAY"

0"
"anrm_0000089 "KZ" "KZ-MAN" "08" "MAN"

1"
"anrm_0000089 "KZ" "KZ-VOS" "10" "VOS"

2"
"anrm_0000089 "KZ" "KZ-KAR" "09" "KAR"

3"
"anrm_0000089 "KZ" "KZ-ALA" "00" "ALA"

4"
"anrm_0000089 "MX" "MX-JAL" "JAL" "JAL"

5"
"anrm_0000089 "MX" "MX-TAB" "TAB" "TAB"

6"
"anrm_0000089 "MX" "MX-BCS" "BCS" "BCS"

7"
"anrm_0000089 "MX" "MX-ROO" "QR" "ROO"

8"
"anrm_0000089 "MX" "MX-SON" "SON" "SON"

9"
"anrm_0000090 "MX" "MX-SIN" "SIN" "SIN"

0"
"anrm_0000090 "MX" "MX-ZAC" "ZAC" "ZAC"

1"
"anrm_0000090 "MX" "MX-MEX" "MEX" "MEX"

2"
"anrm_0000090 "MX" "MX-TAM" "TMS" "TAM"

3"
"anrm_0000090 "MX" "MX-HID" "HGO" "HID"

4"
"anrm_0000090 "MX" "MX-YUC" "YUC" "YUC"

5"
"anrm_0000090 "MX" "MX-MIC" "MCH" "MIC"

6"
"anrm_0000090 "MX" "MX-BCN" "MX-BC" "BCN"

7"

"anrm_0000090 "MX" "MX-MOR" "MOR" "MOR"

8"
"anrm_0000090 "MX" "MX-AGU" "AGS" "AGU"

9"
"anrm_0000091 "MX" "MX-CAM" "CMP" "CAM"

0"
"anrm_0000091 "MX" "MX-COA" "COA" "COA"

1"
"anrm_0000091 "MX" "MX-GUA" "GTO" "MX-GUA"

2"
"anrm_0000091 "MX" "MX-SLP" "SLP" "SLP"

3"
"anrm_0000091 "MX" "MX-COL" "COL" "COL"

4"
"anrm_0000091 "MX" "MX-PUE" "PUE" "PUE"

5"
"anrm_0000091 "MX" "MX-DUR" "DGO" "DUR"

6"
"anrm_0000091 "MX" "MX-QUE" "QRO" "QUE"

7"
"anrm_0000091 "MX" "MX-GRO" "GRO" "GRO"

8"
"anrm_0000091 "MX" "MX-CHH "CHI" "CHH"

9"
"anrm_0000092 "MX" "MX-VER" "VER" "VER"

0"
"anrm_0000092 "MX" "MX-TLA" "TLX" "TLA"

1"
"anrm_0000922 "MX" "MX-NAY" "NAY" "NAY"

"
"anrm_0000092 "MX" "MX-OAX" "OAX" "OAX"

3"
"anrm_0000092 "MX" "MX-NLE" "NL" "NLE"

4"
"anrm_0000092 "MX" "MX-CHP" "CHS" "CHP"

5"
"anrm_0000092 "MY" "MY-05" "SER" "05"

6"

"anrm_0000092 "MY" "MY-16" "PSK"

7"
"anrm_0000092 "MY" "MY-06" "PAH" "06"

8"
"anrm_0000092 "MY" "MY-03" "KEL" "03"

9"
"anrm_0000093 "MY" "MY-14" "KUL" "14"

0"
"anrm_0000093 "MY" "MY-04" "MEL" "04"

1"
"anrm_0000093 "MY" "MY-15" "LAB" "15"

2"
"anrm_0000093 "MY" "MY-01" "JOH" "01"

3"
"anrm_0000093 "MY" "MY-12" "SAB" "12"

4"
"anrm_0000093 "MY" "MY-02" "KED" "02"

5"
"anrm_0000093 "MY" "MY-13" "SAR" "13"

6"
"anrm_0000093 "MY" "MY-10" "SEL" "10"

7"
"anrm_0000093 "MY" "MY-11" "TRE" "11"

8"
"anrm_0000093 "MY" "MY-09" "PEL" "09"

9"
"anrm_0000094 "MY" "MY-07" "PIN" "07"

0"
"anrm_0000094 "MY" "MY-08" "PER" "08"

1"
"anrm_0000094 "NL" "NL-UT" "10" "UT"

2"
"anrm_0000094 "NL" "NL-LI" "06" "LI"

3"
"anrm_0000094 "NL" "NL-DR" "01" "DR"

4"
"anrm_0000094 "NL" "NL-GE" "04" "GE"

5"

"anrm_0000094 "NL" "NL-ZH" "12" "ZH"

6"
"anrm_0000094 "NL" "NL-GR" "05" "GR"

7"
"anrm_0000094 "NL" "NL-ZE" "11" "ZE"

8"
"anrm_0000094 "NL" "NL-FR" "03" "FR"

9"
"anrm_0000095 "NL" "NL-NH" "08" "NH"

0"
"anrm_0000095 "NL" "NL-OV" "09" "OV"

2"
"anrm_0000095 "NL" NL-NB" "07" "NB"

3"
"anrm_0000095 "NO" "NO-03" "03" "03"

4"
"anrm_0000095 "NO" "NO-14" "14" "14"

5"
"arnm_0000095 "NO" "NO-02" "02" "02"

6"
"anrm_0000095 "NO" "NO-01" "01" "01"

7"
"anrm_0000095 "NO" "NO-12" "12" "12"

8"
"anrm_0000095 "NO" "NO-11" "11" "11"

9"
"anrm_0000096 "NO" "NO-10" "10" "10"

0"
"anrm_0000096 "NO" "NO-20" "20" "20"

1"
"anrm_0000096 "NO" "NO-09" "09" "09"

2"
"anrm_0000096 "NO" "NO-08" "08" "08"

3"
"anrm_0000964 "NO" "NO-19" "19" "19"

"
"anrm_0000096 "NO" "NO-07" "07" "07"

5"

"anrm_0000096 "NO" "NO-18" "18" "18"

6"
"anrm_0000096 "NO" "NO-06" "06" "06"

7"
"anrm_0000096 "NO" "NO-05" "05" "05"

8"
"anrm_0000096 "NO" "NO-04" "04" "04"

9"
"anrm_0000097 "NO" "NO-15" "15" "15"

0"
"anrm_0000097 "NZ" "NZ-BOP" "BOP" "BOP"

1"
"anrm_0000097 "NZ" "NZ-WTC" "WEC" "WTC"

2"
"anrm_0000097 "NZ" "NZ-NTL" "NTL" "NTL"

3"
"anrm_0000097 "NZ" "NZ-STL" "STL" "STL"

4"
"anrm_0000097 "NZ" "NZ-MWT" "MAN" "MWT"

5"
"anrm_0000097 "NZ" "NZ-CAN" "CAN" "CAN"

6"
"anrm_0000097 "NZ" "NZ-TKI" "TAR" "TKI"

7"
"anrm_0000097 "NZ" "NZ-AUK" "AKL" "AUK"

8"
"anrm_0000097 "NZ" "NZ-OTA" "OTA" "OTA"

9"
"anrm_0000098 "NZ" "NZ-WGN" "WLG" "WGN"

0"
"anrm_0000098 "NZ" "NZ-HKB" "HAB" "HKB"

1"
"arnm_0000098 "NZ" "NZ-WKO" "WAI" "WKO"

2"
"anrm_0000098 "PE" "PE-PIU" "02" "PIU"

3"
"anrm_0000098 "PE" "PE-SAM" "13" "SAM"

4"

"anrm_0000098 "PE" "PE-LAM" "03" "LAM"

5"
"anrm_0000098 "PE" "PE-APU" "19" "APU"

6"
"anrm_0000098 "PE" "PE-PAS" "15" "PAS"

7"
"anrm_0000098 "PE" "PE-MDD" "24" "MDD"

8"
"anrm_0000098 "PE" "PE-AYA" "18" "AYA"

9"
"anrm_0000099 "PE" "PE-AMA" "11" "AMA"

0"
"anrm_0000099 "PE" "PE-HUC" "14" "HUC"

1"
"anrm_0000099 "PE" "PE-ICA" "07" "ICA"

2"
"anrm_0000099 "PE" "PE-CUS" "20" "20"

3"
"anrm_0000099 "PE" "PE-LMA" "06" "LMA"

4"
"anrm_0000099 "PE" "PE-JUN" "16" "JUN"

5"
"anrm_0000099 "PE" "PE-CAJ" "12" "CAJ"

6"
"anrm_0000099 "PE" "PE-TUM" "01" "TUM"

7"
"anrm_0000099 "PE" "PE-LOR" "22" "LOR"

8"
"anrm_0000099 "PE" "PE-MOQ" "09" "MOQ"

9"
"anrm_0000100 "PE" "PE-CAL" "06" "CAL"

0"
"anrm_0000100 "PE" "PE-HUV" "17" "HUV"

1"
"anrm_0000100 "PE" "PE-PUN" "21" "PUN"

2"
"anrm_0000100 "PE" "PE-ARE" "08" "ARE"

3"

"anrm_0000100 "PE" "PE-LAL" "04" "LAL"

4"
"anrm_0000100 "PE" "PE-ANC" "05" "ANC"

5"
"anrm_0000100 "PE" "PE-TAC" "10" "TAC"

6"
"anrm_0000100 "PE" "PE-LIM" "06" "LIM"

7"
"anrm_0000100 "PE" "PE-UCA" "23" "UCA"

8"
"anrm_0000100 "PH" "PH-WSA" "08" "WSA"

9"
"anrm_0000101 "PH" "PH-AKL" "06" "AKL"

0"
"anrm_0000101 "PH" "PH-COM" "12" "COM"

1"
"anrm_0000101 "PH" "PH-NUE" "03" "NUE"

2"
"anrm_0000101 "PH" "PH-MSC" "10" "MSC"

3"
"anrm_0000101 "PH" "PH-PLW" "04" "PLW"

4"
"anrm_0000101 "PH" "PH-ZMB" "09" "ZMB"

5"
"anrm_0000101 "PH" "PH-BUL" "03" "BUL"

6"
"anrm_0000101 "PH" "PH-BUK" "10" "BUK"

7"
"anrm_0000101 "PH" "PH-IFU" "03" "IFU"

8"
"anrm_0000101 "PH" "PH-ISA" "02" "ISA"

9"
"anrm_0000102 "PH" "PH-BAS" "11" "BAS"

0"
"anrm_0000102 "PH" "PH-MOU" "03" "MOU"

1"
"anrm_0000102 "PH" "PH-APA" "03" "APA"

2"

"anrm_0000102 "PH" "PH-DAO" "12" "DAO"

3"
"anrm_0000102 "PH" "PH-LAG" "04" "LAG"

4
"anrm_0000102 "PH" "PH-BAN" "03" "BAN"

5"
"anrm_0000102 "PH" "PH-NUV" "02" "NUV"

6"
"anrm_0000102 "PH" "PH-AGS" "10" "AGS"

7"
"anrm_0000102 "PH" "PH-MSR" "10" "MSR"

8"
"anrm_0000102 "PH" "PH-NEC" "07" "NEC"

9"
"anrm_0000103 "PH" "H-BEN" "03" "BEN"

0"
"anrm_0000103 "PH" "PH-AGN" "10" "AGN"

1"
"anrm_0000103 "PH" "PH-BIL" "08" "BIL"

2"
"anrm_0000103 "PH" "PH-LUN" "01" "LUN"

3"
"anrm_0000103 "PH" "PH-TAR" "03" "TAR"

4"
"anrm_0000103 "PH" "PH-RIZ" "04" "RIZ"

5"
"anrm_0000103 "PH" "PH-ZAN" "09" "ZAN"

6"
"anrm_0000103 "PH" "PH-LEY" "08" "LEY"

7"
"anrm_0000103 "PH" "PH-TAW" "11" "TAW"

8"
"anrm_0000103 "PH" "PH-LAS" "11" "LAS"

9"
"anrm_0000104 "PH" "PH-PAN" "01" "PAN"

0"
"anrm_0000104 "PH" "PH-SLE" "08" "SLE"

1"

"anrm_0000104 "PH" "PH-ZAS" "09" "ZAS"

2"
"anrm_0000104 "PH" "PH-PAM" "03" "PAM"

3"
"anrm_0000104 "PH" "PH-NER" "07" "NER"

4"
"anrm_0000104 "PH" "PH-DAV" "12" "DAV"

5"
"anrm_0000104 "PH" "PH-LAN" "10" "LAN"

6"
"anrm_0000104 "PH" "PH-ALB" "05" "ALB"

7"
"anrm_0000104 "PH" "PH-DAS" "12" "DAS"

8"
"anrm_0000104 "PH" "PH-SOR" "05" "SOR"

9"
"anrm_0000105 "PH" "PH-ILS" "01" "ILS"

0"
"anrm_0000105 "PH" "PH-MDC" "04" "MDC"

1"
"anrm_0000105 "PH" "PH-ILN" "01" "ILN"

2"
"anrm_0000105 "PH" "PH-SCO" "11" "SCO"

3"
"anrm_0000105 "PH" "PH-ILI" "06" "ILI"

4"
"anrm_0000105 "PH" "PH-QUE" "04" "QUE"

5"
"anrm_0000105 "PH" "PH-CEB" "07" "CEB"

6"
"anrm_0000105 "PH" "PH-SUK" "11" "SUK"

7"
"anrm_0000105 "PH" "PH-AUR" "03" "AUR"

8"
"anrm_0000105 "PH" "PH-SUN" "10" "SUN"

9"
"anrm_0000106 "PH" "PH-NSA" "08" "NSA"

0"

"anrm_0000106 "PH" "PH-BOH" "07" "BOH"

1"
"anrm_0000106 "PH" "PH-GUI" "06" "GUI"

2"
"anrm_0000106 "PH" "PH-MDR" "04" "MDR"

3"
"anrm_0000106 "PH" "PH-ROM" "04" "ROM"

4"
"anrm_0000106 "PH" "PH-SUR" "10" "SUR"

5"
"anrm_0000106 "PH" "PH-ZSI" "09" "ZSI"

6"
"anrm_0000106 "PH" "PH-SIG" "07" "SIG"

7"
"anrm_0000106 "PH" "PH-MAG" "11" "MAG"

8"
"anrm_0000106 "PH" "PH-CAP" "06" "CAP"

9"
"anrm_0000107 "PH" "PH-CAN" "05" "CAN"

0"
"anrm_0000107 "PH" "PH-MAD" "04" "MAD"

1"
"anrm_0000107 "PH" "PH-CAM" "10" "CAM"

2"
"anrm_0000107 "PH" "PH-SLU" "11" "SLU"

3"
"Anrm_0000107 "PH" "PH-CAG" "02" "CAG"

4"
"anrm_0000107 "PH" "PH-QUI" "02" "QUI"

5"
"anrm_0000107 "PH" "PH-MAS" "05" "MAS"

6"
"anrm_0000107 "PH" "PH-BTN" "02" "BTN"

7"
"anrm_0000107 "PH" "PH-NCO" "11" "NCO"

8"
"anrm_0000107 "PH" "PH-CAV" "04" "CAV"

9"

"anrm_0000108 "PH" "PH-EAS" "08" "EAS"

0"
"anrm_0000108 "PH" "PH-CAT" "05" "CAT"

1"
"anrm_0000108 "PH" "PH-KAL" "03" "KAL"

2"
"anrm_0000108 "PH" "PH-BTG" "04" "BTG"

3"
"anrm_0000108 "PH" "PH-CAS" "04" "CAS"

4"
"anrm_0000108 "PH" "PH-ABR" "03" "ABR"

5"
"anrm_0000108 "PH" "PH-ANT" "06" "ANT"

6"
"anrm_0000108 "PH" "PH-SAR" "11" "SAR"

7"
"anrm_0000108 "PL" "PL-02" "DSL" "DS"

8"
"anrm_0000108 "PL" "PL-04" "K-P" "KP"

9"
"anrm_0000109 "PL" "PL-08" "LBS" "LB"

0"
"anrm_0000109 "PL" "PL-10" "LDZ" "LD"

1"
"anrm_0000109 "PL" "PL-06" "LBL" "LU"

2"
"anrm_0000109 "PL" "PL-12" "MAL" "MA"

3"
"anrm_0000109 "PL" "PL-14" "MAZ" "MZ"

4"
"anrm_0000109 "PL" "PL-16" "OPO" "OP"

5"
"anrm_0000109 "PL" "PL-20" "PDL" "PD"

6"
"anrm_0000109 "PL" "PL-18" "PDK" "PK"

7"
"anrm_0000109 "PL" "PL-22" "POM" "PM"

8"

"anrm_0000109 "PL" "PL-26" "SWK "SK"

9"
"anrm_0000110 "PL" "PL-24" "SLS" "SL"

0"
"anrm_0000110 "PL" "PL-28" "W-M" "WN"

1"
"anrm_0000110 "PL" "PL-30" "WLK" "WP"

2"
"anrm_0000110 "PL" "PL-32" "Z-P" "ZP"

3"
"anrm_0000110 "PT" "PT-05" "28" "05"

4"
"anrm_0000110 "PT" "PT-16" "10" "16"

5"
"anrm_0000110 "PT" "PT-06" "21" "06"

6"
"anrm_0000110 "PT" "PT-17" "16" "17"

7"
"anrm_0000110 "PT" "PT-03" "11" "03"

8"
"anrm_0000110 "PT" "PT-14" "34" "14"

9"
"anrm_0000111 "PT" "PT-04" "17" "04"

0"
"anrm_0000111 "PT" "PT-15" "32" "15"

1"
"anrm_0000111 "PT" "PT-01" "20" "01"

2"
"anrm_0000111 "PT" "PT-12" "41" "12"

3"
"anrm_0000111 "PT" "PT-02" "43" "02"

4"
"anrm_0000111 "PT" "PT-13" "13" "13"

5"
"anrm_0000111 "PT" "PT-10" "22" "10"

6"
"anrm_0000111 "PT" "PT-11" "31" "11"

7"

"anrm_0000111 "PT" "PT-30" "70" "30"

8"
"anrm_0000111 "PT" "PT-20" "60" "20"

9"
"anrm_0000112 "PT" "PT-09" "27" "09"

0"
"anrm_0000112 "PT" "Pt-07" "42" "07"

1"
"ANRM_0000112 "PT" "PT-18" "25" "18"

2"
"anrm_0000112 "PT" "PT-08" "50" "08"

3"
"anrm_0000112 "QA" "QA-MS" "002" "MS"

4"
"anrm_0000112 "QA" "QA-WA" "004" "WA"

5"
"anrm_0000112 "QA" "QA-US" "002" "US"

6"
"anrm_0000112 "QA" "QA-DA" "001" "DA"

7"
"anrm_0000112 "QA" "QA-KH" "002" "KH"

8"
"anrm_0000112 "QA" "QA-RA" "003" "RA"

9"
"anrm_0000113 "RO" "RO-BZ" "11" "BZ"

0"
"anrm_0000113 "RO" "RO-SM" "34" "SM"

1"
"anrm_0000113 "RO" "RO-MH" "28" "MH"

2"
"anrm_0000113 "RO" "RO-IF" "26" "IF"

3"
"anrm_0000113 "RO" "RO-BR" "08" "BR"

4"
"anrm_0000113 "RO" "RO-BT" "07" "BT"

5"
"anrm_0000113 "RO" "RO-BV" "09" "BV"

6"

"anrm_0000113 "RO" "RO-SJ" "33" "SJ"

7"
"anrm_0000113 "RO" "RO-CL" "12" "CL"

8"
"anrm_0000113 "RO" "RO-IS" "25" "IS"

9"
"anrm_0000114 "RO" "RO-GR" "21" "GR"

0"
"anrm_0000114 "RO" "RO-B" "10" "B"

1"
"anrm_0000114 "RO" "RO-MM" "27" "MM"

2"
"anrm_0000114 "RO" "RO-AB" "01" "AB"

3"
"anrm_0000114 "RO" "RO-GJ" "20" "GH"

4"
"anrm_0000114 "RO" "RO-IL" "24" "IL"

5"
"anrm_0000114 "RO" "RO-SV" "36" "SV"

6"
"anrm_0000114 "RO" "RO-GL" "19" "GL"

7"
"anrm_0000114 "RO" "RO-OT" "31" "OT"

8"
"anrm_0000114 "RO" "RO-AG" "03" "AG"

9"
"anrm_0000115 "RO" "RO-MS" "29" "MS"

0"
"anrm_0000115 "RO" "RO-CJ" "14" "CJ"

1"
"anrm_0000115 "RO" "RO-PH" "32" "PH"

2"
"anrm_0000115 "RO" "RO-TL" "39" "TL"

3"
"anrm_0000115 "RO" "RO-VN" "42" "VN"

4"
"anrm_0000115 "RO" "RO-TM" "38" "TM"

5"

"anrm_0000115 "RO" "RO-HD" "23" "HD"

6"
"anrm_0000115 "RO" "RO-VS" "40" "VS"

7"
"anrm_0000115 "RO" "RO-DB" "17" "DB"

8"
"anrm_0000115 "RO" "RO-TR" "37" "TR"

9"
"anrm_0000116 "RO" "RO-CS" "13" "CS"

0"
"anrm_0000116 "RO" "RO-AR" "02" "AR"

1"
"anrm_0000116 "RO" "RO-CT" "15" "CT"

2"
"anrm_0000116 "RO" "RO-CV" "16" "CV"

3"
"anrm_0000116 "RO" "RO-VL" "41" "VL"

4"
"anrm_0000116 "RO" "RO-HR" "22" "HR"

5"
"anrm_0000116 "RO" "RO-BN" "06" "BN"

6"
"anrm_0000116 "RO" "RO-SB" "35" "SB"

7"
"anrm_0000116 "RO" "RO-BC" "04" "BC"

8"
"anrm_0000116 "RO" "RO-BH" "05" "BH"

9"
"anrm_0000117 "RO" "RO-DJ" "18" "DJ"

0"
"anrm_0000117 "RO" "RO-NT" "30" "NT"

1"
"anrm_0000117 "RU" "RU-ARK" "29" "ARK"

2"
"anrm_0000117 "RU" "RU-KK" "19" "KK"

3"
"anrm_0000117 "RU" "RU-KL" "08" "KL"

4"

"anrm_0000117 "RU" "RU-SAK" "65" "SAK"

5"
"anrm_0000117 "RU" "RU-KO" "11" "KO'

6"
"anrm_0000117 "RU" "RU-SAM" "63" "SAM"

7"
"anrm_0000117 "RU" "RU-CE" "20" "CE"

8"
"anrm_0000117 "RU" "RU-IRK" "38" "IRK"

9"
"anrm_0000118 "RU" "RU-KC" "09" "KC"

0"
"anrm_0000118 "RU" "RU-ORE" "56" "ORE"

1"
"anrm_0000118 "RU" "RU-SVE" "66" "SVE"

2"
"anrm_0000118 "RU" "RU-SAR" "64" "SAR"

3"
"anrm_0000118 "RU" "RU-KB" "07" "KB"

4"
"anrm_0000118 "RU" "RU-YAN" "89" "YAN"

5"
"anrm_0000118 "RU" "RU-ORL" "57" "ORL"

6"
"anrm_0000118 "RU" "RU-MUR" "51" "MUR"

7"
"anrm_0000118 "RU" "RU-CU" "21" "CU"

8"
"anrm_0000118 "RU" "RU-TOM" "70" "TOM"

9"
"anrm_0000119 "RU" "RU-KEM" "42" "KEM"

0"
"anrm_0000119 "RU" "RU-MAG" "49" "MAG"

1"
"anrm_0000119 "RU" "RU-IVA" "37" "IVA"

2"
"anrm_0000119 "RU" "RU-KIR" "43" "KIR"

3"

"anrm_0000119 "RU" "RU-KR" "10" "KR"

4"
"anrm_0000119 "RU" "RU-OMS" "55" "OMS"

5"
"anrm_0000119 "RU" "RU-SMO" "67" "SMO"

6"
"anrm_0000119 "RU" "RU-ROS" "61" "ROS"

7"
"anrm_0000119 "RU" "RU-VGG" "34" "VGG"

8"
"anrm_0000119 "RU" "RU-KAM" "41" "KAM"

9"
"anrm_0000120 "RU" "RU-TA" "16" "TA"

0"
"anrm_0000120 "RU" "RU-NGR" "53" "NGR"

1"
"anrm_0000120 "RU" "RU-VOR" "36" "VOR"

2"
"anrm_0000120 "RU" "RU-PNZ" "57" "PNZ"

3"
"anrm_0000120 "RU" "RU-BA" "03" "BA"

4"
"anrm_0000120 "RU" "RU-ULY" "73" "ULY"

5"
"anrm_0000120 "RU" "RU-PSK" "60" "PSK"

6"
"anrm_0000120 "RU" "RU-AMU" "28" "AMU"

7"
"anrm_0000120 "RU" "RU-NVS" "54" "NVS"

8"
"anrm_0000120 "RU" "RU-SA" "14" "SA"

9"
"anrm_0000121 "RU" "RU-CHU" "87" "CHU"

0"
"anrm_0000121 "RU" "RU-KHM" "86" "KHM"

1"
"anrm_0000121 "RU" "RU-SE" "15" "SE"

2"

"anrm_0000121 "RU" "RU-BU" "04" "BU"

3"
"anrm_0000121 "RU" "RU-KYA" "24" "KYA"

4"
"anrm_0000121 "RU" "RU-KLU" "40" "KLU"

5"
"anrm_0000121 "RU" "RU-ZAB" "75" "ZAB"

6"
"anrm_0000121 "RU" "RU-PER" "59" "PER"

7"
"anrm_0000121 "RU" "RU-IN" "06" "IN"

8"
"anrm_0000121 "RU" "RU-NIZ" "52" "NIZ"

9"
"anrm_0000122 "RU" "RU-CHE" "74" "CHE"

0"
"anrm_0000122 "RU" "RU-MO" "13" "MO"

1"
"anrm_0000122 "RU" "RU-STA" "26" "STA"

2"
"anrm_0000122 "RU" "RU-TAM" "68" "TAM"

3"
"anrm_0000122 "RU" "RU-AD" "01" "AD"

4"
"anrm_0000122 "RU" "RU-ME" "12" "ME"

5"
"anrm_0000122 "RU" "RU-TVE" "69" "TVE"

6"
"anrm_0000122 "RU" "RU-KHA" "27" "KHA"

7"
"anrm_0000122 "RU" "RU-PRI" "25" "PRI"

8"
"anrm_0000122 "RU" "RU-KDA" "23" "KDA"

9"
"anrm_0000123 "RU" "RU-SPE" "78" "SPE"

0"
"anrm_0000123 "RU" "RU-ALT" "22" "ALT"

1"

"anrm_0000123 "RU" "RU-BRY" "32" "BRY"

2"
"anrm_0000123 "RU" "RU-TUL" "71" "TUL"

3"
"anrm_0000123 "RU" "RU-KOS" "44" "KOS"

4"
"anrm_0000123 "RU" "RU-TYU" "72" "TYU"

5"
"anrm_0000123 "RU" "RU-MOS" "50" "MOS"

6"
"anrm_0000123 "RU" "RU-KGN" "45" "KGN"

7"
"anrm_0000123 "RU" "RU-LIP" "48" "LIP"

8"
"anrm_0000123 "RU" "RU-LEN" "47" "LEN"

9"
"anrm_0000124 "RU" "RU-MOW" "77" "MOW"

0"
"anrm_0000124 "RU" "RU-NEN" "83" "NEN"

1"
"anrm_0000124 "RU" "RU-AL" "02" "AL"

2"
"anrm_0000124 "RU" "RU-RYA" "62" "RYA"

3"
"anrm_0000124 "RU" "RU-TY" "17" "TY"

4"
"anrm_0000124 "RU" "RU-AST" "30" "AST"

5"
"anrm_0000124 "RU" "RU-DA" "05" "DA"

6"
"anrm_0000124 "RU" "RU-KGD" "39" "KDG"

7"
"anrm_0000124 "RU" "RU-BEL" "31" "BEL"

8"
"anrm_0000124 "RU" "RU-YAR" "76" "YAR"

9"
"anrm_0000125 "RU" "RU-YEV" "79" "YEV"

0"

"anrm_0000125 "RU" "RU-VLA" "33" "VLA"

1"
"anrm_0000125 "RU" "RU-KRS" "46" "KRS"

2"
"anrm_0000125 "RU" "RU-UD" "18" "UD"

3"
"anrm_0000125 "RU" "RU-VLG" "35" "VLG"

4"
"anrm_0000125 "SE" "SE-I" "003" "I"

5"
"anrm_0000125 "SE" "SE-G" "009" "G"

6"
"anrm_0000125 "SE" "SE-H" "008" "H"

7"
"anrm_0000125 "SE" "SE-AC" "016" "AC"

8"
"anrm_0000125 "SE" "SE-BD" "010" "BD"

9"
"anrm_0000126 "SE" "SE-E" "021" "E"

0"
"anrm_0000126 "SE" "SE-AB" "012" "AB"

1"
"anrm_0000126 "SE" "SE-F" "007" "F"

2"
"anrm_0000126 "SE" "SE-C" "014" "C"

3"
"anrm_0000126 "SE" "SE-D" "013" "D"

4"
"anrm_0000126 "SE" "SE-O" "019" "O"

5"
"anrm_0000126 "SE" "SE-M" "011" "M"

6"
"anrm_0000126 "SE" "SE-N" "005" "N"

7"
"anrm_0000126 "SE" "SE-K" "001" "K"

8"
"anrm_0000126 "SE" "SE-Y" "017" "Y"

9"

"anrm_0000127 "SE" "SE-Z" "006" "Z"

0"
"anrm_0000127 "SE" "SE-W" "002" "W"

1"
"anrm_0000127 "SE" "SE-X" "004" "X"

2"
"anrm_0000127 "SE" "SE-U" "018" "U"

3"
"anrm_0000127 "SE" "SE-S" "015" "S"

4"
"anrm_0000127 "SE" "SE-T" "020" "T"

5"
"anrm_0000127 "TH" "TH-71" "14" "71"

6"
"anrm_0000127 "TH" "TH-73" "27" "73"

7"
"anrm_0000127 "TH" "TH-31" "03" "31"

8"
"anrm_0000127 "TH" "TH-30" "29" "30"

9"
"anrm_0000128 "TH" "TH-76" "43" "76"

0"
"anrm_0000128 "TH" "TH-37" "01" "37"

1"
"anrm_0000128 "TH" "TH-36" "06" "36"

2"
"anrm_0000128 "TH" "TH-39" "34" "39"

3"
"anrm_0000128 "TH" "TH-80" "31" "80"

4"
"anrm_0000128 "TH" "TH-82" "39" "82"

5"
"anrm_0000128 "TH" "TH-81" "16" "81"

6"
"anrm_0000128 "TH" "TH-40" "15" "40"

7"
"anrm_0000128 "TH" "TH-83" "48" "83"

8"

"anrm_0000128 "TH" "TH-42" "21" "42"

9"
"anrm_0000129 "TH" "TH-86" "11" "86"

0"
"anrm_0000129 "TH" "TH-44" "24" "44"

1"
"anrm_0000129 "TH" "TH-43" "35" "43"

2"
"anrm_0000129 "TH" "TH-46" "12" "46"

3"
"anrm_0000129 "TH" "TH-48" "28" "48"

4"
"anrm_0000129 "TH" "TH-49" "25" "49"

5"
"anrm_0000129 "TH" "TH-93" "40" "93"

6"
"anrm_0000129 "TH" "TH-51" "20" "51"

7"
"anrm_0000129 "TH" "TH-50" "08" "50"

8"
"anrm_0000129 "TH" "TH-94" "38" "94"

9"
"anrm_0000130 "TH" "TH-52" "19" "52"

0"
"anrm_0000130 "TH" "TH-96" "33" "96"

1"
"anrm_0000130 "TH" "TH-55" "32" "55"

2"
"anrm_0000130 "TH" "TH-10" "17" "10"

3"
"anrm_0000130 "TH" "TH-54" "47" "54"

4"
"anrm_0000130 "TH" "TH-13" "37" "13"

5"
"anrm_0000130 "TH" "TH-57" "09" "57"

6"
"anrm_0000130 "TH" "TH-12" "36" "12"

7"

"anrm_0000130 "TH" "TH-56" "41" "56"

8"
"anrm_0000130 "TH" "TH-15" "02" "15"

9"
"anrm_0000131 "TH" "TH-14" "46" "14"

0"
"anrm_0000131 "TH" "TH-58" "23" "58"

1"
"anrm_0000131 "TH" "TH-16" "22" "16"

2"
"anrm_0000131 "TH" "TH-18" "05" "18"

3"
"anrm_0000131 "TH" "TH-60" "30" "60"

4"
"anrm_0000131 "TH" "TH-62" "13" "62"

5"
"anrm_0000131 "TH" "TH-20" "10" "20"

6"
"anrm_0000131 "TH" "TH-22" "07" "22"

7"
"anrm_0000131 "TH" "TH-66" "44" "66"

8"
"anrm_0000131 "TH" "TH-65" "45" "65"

9"
"anrm_0000132 "TH" "TH-24" "04" "24"

0"
"anrm_0000132 "TH" "TH-67" "42" "67"

1"
"anrm_0000132 "TH" "TH-26" "26" "26"

2"
"anrm_0000132 "TH" "TH-25" "49" "25"

3"
"anrm_0000132 "TR" "TR-53" "53" "53"

4"
"anrm_0000132 "TR" "TR-52" "52" "52"

5"
"anrm_0000132 "TR" "TR-11" "11" "11"

6"

"anrm_0000132 "TR" "TR-55" "55" "55"

7"
"anrm_0000132 "TR" "TR-10" "10" "10"

8"
"anrm_0000132 "TR" "TR-54" "54" "54"

9"
"anrm_0000133 "TR" "TR-51" "51" "51"

0"
"anrm_0000133 "TR" "TR-50" "50" "50"

1"
"anrm_0000133 "TR" "TR-17" "17" "17"

2"
"anrm_0000133 "TR" "TR-16" "16" "16"

3"
"anrm_0000133 "TR" "TR-19" "19" "19"

4"
"anrm_0000133 "TR" "TR-18" "18" "18"

5"
"anrm_0000133 "TR" "TR-13" "13" "13"

6"
"anrm_0000133 "TR" "TR-57" "57" "57"

7"
"anrm_0000133 "TR" "TR-12" "12" "12"

8"
"anrm_0000133 "TR" "TR-56" "56" "56"

9"
"anrm_0000134 "TR" "TR-15" "15" "15"

0"
"anrm_0000134 "TR" "TR-59" "59" "59"

1"
"anrm_0000134 "TR" "TR-14" "14" "14"

2"
"anrm_0000134 "TR" "TR-58" "58" "58"

3"
"anrm_0000134 "TR" "TR-20" "20" "20"

4"
"anrm_0000134 "TR" "TR-64" "64" "64"

5"

"anrm_0000134 "TR" "TR-63" "63" "63"

6"
"anrm_0000134 "TR" "TR-22" "22" "22"

7"
"anrm_0000134 "TR" "TR-66" "66" "66"

8"
"anrm_0000134 "TR" "TR-21" "21" "21"

9"
"anrm_0000135 "TR" "TR-65" "65" "65"

0"
"anrm_0000135 "TR" "TR-60" "60" "60"

1"
"anrm_0000135 "TR" "TR-62" "62" "62"

2"
"anrm_0000135 "TR" "61" "61" "61"

3"
"anrm_0000135 "TR" "TR-28" "28" "28"

4"
"anrm_0000135 "TR" "TR-27" "27" "27"

5"
"anrm_0000135 "TR" "TR-29" "29" "29"

6"
"anrm_0000135 "TR" "TR-24" "24" "24"

7"
"anrm_0000135 "TR" "TR-68" "68" "68"

8"
"anrm_0000135 "TR" "TR-23" "23" "23"

9"
"anrm_0000136 "TR" "TR-67" "67" "67"

0"
"anrm_0000136 "TR" "TR-26" "26" "26"

1"
"anrm_0000136 "TR" "TR-25" "25" "25"

2"
"anrm_0000136 "TR" "TR-69" "69" "69"

3"
"anrm_0000136 "TR" "TR-31" "31" "31"

4"

"anrm_0000136 "TR" "TR-75" "75" "75"

5"
"anrm_0000136 "TR" "TR-30" "30" "30"

6"
"anrm_0000136 "TR" "TR-74" "74" "74"

7"
"anrm_0000136 "TR" "TR-33" "33" "33"

8"
"anrm_0000136 "TR" "TR-77" "77" "77"

9"
"anrm_0000137 "TR" "TR-32" "32" "32"

0"
"anrm_0000137 "TR" "TR-76" "76" "76"

1"
"anrm_0000137 "TR" "TR-71" "71" "71"

2"
"anrm_0000137 "TR" "TR-70" "70" "70"

3"
"anrm_0000137 "TR" "TR-73" "73" "73"

4"
"anrm_0000137 "TR" "TR-72" "72" "72"

5"
"anrm_0000137 "TR" "TR-39" "39" "39"

6"
"anrm_0000137 "TR" "TR-38" "38" "38"

7"
"anrm_0000137 "TR" "TR-35" "35" "35"

8"
"anrm_0000137 "TR" "TR-79" "79" "79"

9"
"anrm_0000138 "TR" "TR-34" "34" "34"

0"
"anrm_0000138 "TR" "TR-78" "67" "78"

1"
"anrm_0000138 "TR" "TR-37" "37" "37"

2"
"anrm_0000138 "TR" "TR-36" "36" "36"

3"

"anrm_0000138 "TR" "TR-80" "01" "80"

4"
"anrm_0000138 "TR" "TR-42" "42 "42"

5"
"anrm_0000138 "TR" "TR-41" "41" "41"

6"
"anrm_0000138 "TR" "TR-44" "44" "44"

7"
"anrm_0000138 "TR" "TR-43" "43" "43"

8"
"anrm_0000138 "TR" "TR-81" "14" "81"

9"
"anrm_0000139 "TR" "TR-40" "40" "40"

0"
"anrm_0000139 "TR" "TR-06" "06" "06"

1"
"anrm_0000139 "TR" "TR-05" "05" "05"

2"
"anrm_0000139 "TR" "TR-49" "49" "49"

3"
"anrm_0000139 "TR" "TR-08" "08" "08"

4"
"anrm_0000139 "TR" "TR-07" "07" "07"

5"
"anrm_0000139 "TR" "TR-02" "02" "02"

6"
"anrm_0000139 "TR" "TR-46" "46" "46"

7"
"anrm_0000139 "TR" "TR-01" "01" "01"

8"
"anrm_0000139 "TR" "TR-45" "45" "45"

9"
"anrm_0000140 "TR" "TR-04" "04" "04"

0"
"anrm_0000140 "TR" "TR-48" "48" "48"

1"
"anrm_0000140 "TR" "TR-03" "03" "03"

2"

"anrm_0000140 "TR" "TR-47" "47" "47"

3"
"anrm_0000140 "TR" "TR-09" "09" "09"

4"
"anrm_0000140 "TW" "TW-ILA" "TWN" "ILA"

5"
"anrm_0000140 "TW" "TW-CHA" "TWN" "CHA"

6"
"anrm_0000140 "TW" "TW-CYQ" "TWN" "CYQ"

7"
"anrm_0000140 "TW" "TW-NAN" "TWN" "NAN"

8"
"anrm_0000140 "TW" "TW-TPE" "TPE" "TPE"

9"
"anrm_0000141 "TW" "TW-HSQ" "TWN" "HSQ"

0"
"anrm_0000141 "TW" "TW-MIA" "TWN" "MIA"

1"
"anrm_0000141 "TW" "TW-TAO" "TWN" "TAO"

2"
"anrm_0000141 "TW" "TW-TXG" "TWN" "TXG"

3"
"anrm_0000141 "TW" "TW-HSZ" "TWN" "HSZ"

4"
"anrm_0000141 "TW" "TW-PIF" "TWN" "PIF"

5"
"anrm_0000141 "TW" "TW-KEE" "TWN" "KEE"

6"
"anrm_0000141 "TW" "TW-KHH" "KSH" "KHH"

7"
"anrm_0000141 "TW" "TW-PEN" "TWN" "PEN"

8"
"anrm_0000141 "TW" "TW-HUA" "TWN" "HUA"

9"
"anrm_0000142 "TW" "TW-TNN" "TWN" "TNN"

0"
"anrm_0000142 "TW" "TW-TTT" "TWN" "TTT"

1"

"anrm_0000142 "TW" "TW-YUN" "TWN" "YUN"

2"
"anrm_0000142 "TW" "TW-CYI" "TWN" "CYI"

3"
"anrm_0000142 "UA" "UA-18" "ZHI" "18"

4"
"anrm_0000142 "UA" "UA-14" "DON" "14"

5"
"anrm_0000142 "UA" "UA-59" "SUM" "59"

6"
"anrm_0000142 "UA" "UA-32" "KIE" "32"

7"
"anrm_0000142 "UA" "UA-77" "CHV" "77"

8"
"anrm_0000142 "UA" "UA-12" "DNP" "12"

9"
"anrm_0000143 "UA" "UA-56" "RIV" "56"

0"
"anrm_0000143 "UA" "UA-35" "KIR" "35"

1"
"anrm_0000143 "UA" "UA-61" "TER" "61"

2"
"anrm_0000143 "UA" "UA-40" "M_S" "40"

3"
"anrm_0000143 "UA" "UA-63" "HAR" "63"

4"
"anrm_0000143 "UA" "UA-07" "VOL" "07"

5"
"anrm_0000143 "UA" "UA-09" "LUG" "09"

6"
"anrm_0000143 "UA" "UA-26" "IVF" "26"

7"
"anrm_0000143 "UA" "UA-48" "MIK" "48"

8"
"anrm_0000143 "UA" "UA-05" "VIN" "05"

9"
"anrm_0000144 "UA" "UA-21" "ZAK" "21"

0"

"anrm_0000144 "UA" "UA-43" "KRM" "43"

1"
"anrm_0000144 "UA" "UA-65" "HRS" "65"

2"
"anrm_0000144 "UA" "UA-23" "ZAP" "23"

3"
"anrm_0000144 "UA" "UA-46" "L'V" "46"

4"
"anrm_0000144 "UA" "UA-68" "HML" "68"

5"
"anrm_0000144 "UA" "UA-51" "ODS" "51"

6"
"anrm_0000144 "UA" "UA-30" "M_K" "30"

7"
"anrm_0000144 "UA" "UA-74" "CHG" "74"

8"
"anrm_0000144 "UA" "UA-53" "POL" "53"

9"
"anrm_0000145 "UA" "UA-71" "CHR" "71"

0"
"anrm_0000145 "US" "US-FL" "FL" "FL"

1"
"anrm_0000145 "US" "US-NV" "NV" "NV"

2"
"anrm_0000145 "US" "US-SC" "SC" "SC"

3"
"anrm_0000145 "US" "US-WA" "WA" "WA"

4"
"anrm_0000145 "US" "US-NY" "NY" "NY"

5"
"anrm_0000145 "US" "US-NC" "NC" "NC"

6"
"anrm_0000145 "US" "US-ND" "ND" "ND"

7"
"anrm_0000145 "US" "US-NE" "NE" "NE"

8"
"anrm_0000145 "US" "US-RI" "RI" "RI"

9"

"anrm_0000146 "US" "US-AR" "AR" "AR"

0"
"anrm_0000146 "US" "US-AS" "AS"

1"
"anrm_0000146 "US" "US-VT" "VT" "VT"

2"
"anrm_0000146 "US" "US-NM" "NM" "NM"

3"
"anrm_0000146 "US" "US-AZ" "AZ" "AZ"

4"
"anrm_0000146 "US" "US-NH" "NH" "NH"

5"
"anrm_0000146 "US" "US-NJ" "NJ" "NJ"

6"
"anrm_0000146 "US" "US-KS" "KS" "KS"

7"
"anrm_0000146 "US" "US-WY" "WY" "WY"

8"
"anrm_0000146 "US" "US-OR" "OR" "OR"

9"
"anrm_0000147 "US" "US-KY" "KY" "KY"

0"
"anrm_0000147 "US" "US-CO" "CO" "CO"

1"
"anrm_0000147 "US" "US-SD" "SD" "SD"

2"
"anrm_0000147 "US" "US-WI" "WI" "WI"

3"
"anrm_0000147 "US" "US-CA" "CA" "CA"

4"
"anrm_0000147 "US" "US-WV" "WV" "WV"

5"
"anrm_0000147 "US" "US-OH" "OH" "OH"

6"
"anrm_0000147 "US" "US-GA" "GA" "GA"

7"
"anrm_0000147 "US" "US-OK" "OK" "OK"

8"

"anrm_0000147 "US" "US-DE" "DE" "DE"

9"
"anrm_0000148 "US" "US-HI" "HI" "HI"

0"
"anrm_0000148 "US" "US-PR" "PR"

1"
"anrm_0000148 "US" "US-TX" "TX" "TX"

2"
"anrm_0000148 "US" "US-LA" "LA" "LA"

3"
"anrm_0000148 "US" "US-CT" "CT" "CT"

4"
"anrm_0000148 "US" "US-PA" "PA" "PA"

5"
"anrm_0000148 "US" "US-DC" "DC" "DC"

6"
"anrm_0000148 "US" "US-TN" "TN" "TN"

7"
"anrm_0001488 "US" "US-IN" "IN" "IN"

"
"anrm_0000148 "US" "US-MS" "MS" "MS"

9"
"anrm_0000149 "US" "US-MT" "MT" "MT"

0"
"anrm_0000149 "US" "US-MN" "MN" "MN"

1"
"anrm_0000149 "US" "US-MO" "MO" "MO"

2"
"anrm_0000149 "US" "US-IL" "IL" "IL"

3"
"anrm_0000149 "US" "US-AK" "AK" "AK"

4"
"anrm_0000149 "US" "US-AL" "AL" "AL"

5"
"anrm_0000149 "US" "US-VA" "VA" "VA"

6"
"anrm_0000149 "US" "US-MD" "MD" "MD"

7"

"anrm_0000149 "US" "US-IA" "IA" "IA"

8"
"anrm_0000149 "US" "US-ME" "ME" "ME"

9"
"ANRM_0000150 "US" "US-MA" "MA" "MA"

0"
"anrm_0000150 "US" "US-UT" "UT" "UT"

1"
"anrm_0000150 "US" "US-ID" "ID" "ID"

2"
"anrm_0000150 "US" "US-MI" "MI" "MI"

3"
"anrm_0000150 "VE" "VE-F" "BOL" "F"

4"
"anrm_0000150 "VE" "VE-G" "CAR" "G"

5"
"anrm_0000506 "VE" "VE-H" "COJ" "H"

"
"anrm_0000150 "VE" "VE-I" "FAL" "I"

7"
"anrm_0000150 "VE" "VE-J" "GUA" "J"

8"
"anrm_0000150 "VE" "VE-K" "LAR" "K"

9"
"anrm_0000151 "VE" "VE-L" "MER" "L"

0"
"anrm_0000151 "VE" "VE-M" "MIR" "M"

1"
"anrm_0000151 "VE" "VE-A" "DF" "A"

2"
"anrm_0000151 "VE" "VE-B" "ANZ" "B"

3"
"anrm_0000151 "VE" "VE-C" "APU" "C"

4"
"anrm_0000151 "VE" "VE-D" "ARA" "D"

5"
"anrm_0000151 "VE" "VE-E" "BAR" "E"

6"

"anrm_0000151 "VE" "VE-V" "ZUL" "V"

7"
"anrm_0000151 "VE" "VE-W" "W"

8"
"anrm_0000151 "VE" "VE-X" "VAR" "X"

9"
"anrm_0000152 "VE" "VE-Y" "DA" "Y"

0"
"anrm_0000152 "VE" "VE-Z" "AMA" "Z"

1"
"anrm_0000152 "VE" "VE-N" "MON" "N"

2"
"anrm_0000152 "VE" "VE-O" "NE" "O"

3"
"anrm_0000152 "VE" "VE-P" "POR" "P"

4"
"anrm_0000152 "VE" "VE-R" "SUC" "R"

5"
"anrm_0000152 "VE" "VE-S" "TAC" "S"

6"
"anrm_0000152 "VE" "VE-T" "TRU" "T"

7"
"anrm_0000152 "VE" "VE-U" "YAR" "U"

8"
"anrm_0000152 "ZA" "ZA-WC" "WC" "WC"

9"
"anrm_0000153 "ZA" "ZA-FS" "FS" "FS"

0"
"anrm_0000153 "ZA" "ZA-GT" "GP" "GT"

1"
"anrm_0000153 "ZA" "ZA-EC" "EC" "EC"

2"
"anrm_0000153 "ZA" "ZA-NL" "ZN" "NL"

3"
"anrm_0000153 "ZA" "ZA-LP" "LP" "LP"

4"
"anrm_0000153 "ZA" "ZA-NC" "NC" "NC" `

5"

"anrm_0000153 "ZA" "ZA-MP" "MP" "MP"

6"
"anrm_0000153 "ZA" "ZA-NW" "NW" "NW"

7"
"anrm_0000002 "IN" "IN-ML" "15" "ML"

7"
"anrm_0000003 "IN" "IN-PB" "19" "PB"

2"
"anrm_0000002 "IN" "IN_GA" "05" "GA"

4"
"anrm_0000003 "IN" "IN-CT" "33" "CT"

0"
"anrm_0000002 "IN" "IN-OR" "18" "OR"

1"
"anrm_0000000 "IN" "IN-TN" "22" "TN"

5"
"anrm_0000001 "IN" "IN-MN" "14" "MN"

8"
"anrm_0000001 "IN" "IN_KA" "10" "KA"

0"
"anrm_0000000 "IN" "IN-LD" "31" "LD"

3"
"anrm_0000001 "IN" "IN-HR" "07" "HR"

5"
"anrm_0000000 "IN" "IN-TR" "23" "TR"

8"
"anrm_0000001 "IN" "IN-PY" "32" "PY"

3"
"anrm_0000003 "IN" "IN-AP" "01" "AP"

5"
"anrm_0000000 "IN" "IN-JH" "34" "JH"

6"
"anrm_0000001 "IN" "IN-HP" "08" "HP"

2"
"anrm_0000000 "IN" "IN-JK" "09" "JK"

2"
"anrm_0000000 "IN" "IN-BR" "04" "BR"

9"

"anrm_0000003 "IN" "IN-MZ" "16" "MZ"

4"
"anrm_0000002 "IN" "IN-UP" "24" "UP"

6"
"anrm_0000002 "IN" "IN-SK" "21" "SK"

3"
"anrm_0000002 "IN" "IN-MP" "12" "MP"

0"
"anrm_0000001 "IN" "IN-KL" "11" "KL"

7"
"anrm_0000002 "IN" "IN-AR" "02" "AR"

9"
"anrm_0000001 "IN" "IN-DN" "28" "DN"

4"
"anrm_0000001 "IN" "IN-GJ" "06" "GJ"

9"
"anrm_0000001 "IN" "IN-WB" "25" "WB"

6"
"anrm_0000001 "IN" "IN-DL" "30" "DL"

1"
"anrm_0000003 "IN" "IN-AS" "03" "AS"

1"
"anrm_0000003 "IN" "IN-TS" "02"

6"
"anrm_0000002 "IN" "IN-UT" "35" "UL"

8"
"anrm_0000003 "IN" "IN-AN" "26" "AN"

3"
"anrm_0000002 "IN" "IN-MH" "13" "MH"

5"
"anrm_0000000 "IN" "IN-RJ" "20" "RJ"

4"
"anrm_0000000 "IN" "IN-NL" "17" "NL"

7"
"anrm_0000002 "IN" "IN-CH" "27" "CH"

2"
"anrm_0000000 "IN" "IN-DD" "29" "DD"

1"

Default syntax validation for postal codes in supplier
addresses
SAP Ariba provides default syntax validation master data for the postal codes that respondents provide in answers
to Address and Extended Address questions in supplier management questionnaires..
You can use the Import Country-Specific Postal Code Validations data import task to define custom, country-
specific syntax validation for postal codes [page 61].
 Note
Postal code validation based on configurable master data is only available in sites that use the new supplier
360° profile (SM-14322) and the enhanced supplier request (SM-15774). Sites that do not meet these
prerequisites use static, SAP Ariba-defined postal code validation.
The following table describes SAP Ariba's default postal code validation master data:
CountryCode Country ZipFormat Regex ISO Note
AO Angola AO
AG Antigua and AG
Barbuda
AW Aruba AW
BS Bahamas BS
BZ Belize BZ
BJ Benin BJ
BM Bermuda BM
BO Bolivia BO
BQ "Bonaire, BQ
Sint
Eustatius and
Saba"
BW Botswana BW
BF Burkino Faso BF
BI Burundi BI
CM Cameroon CM
CF Central CF
African
Republic
TD Chad TD
KM Comoros KM

CG Congo CG
(Brazzaville)
CD Congo, CD
Democratic
Republic
CK Cook Islands CK
CI Ivory Coast CI
CW Curacao CW
DJ Djibouti DJ
DM Dominica DM
TL East Timor TL
GQ Equatorial GQ
Guinea
ER Eritrea ER
FJ Fiji FJ
TF French TF
Southern and
Antarctic
Territories
GA Gabon GA
GM Gambia GM
GH Ghana GH
GD Grenada GD
GY Guyana GY
HM Heard and HM
McDonald
Islands
HG Hong Kong HK
IE Ireland IE
KI Kiribati KI
KP "Korea, KP
North"
LY Libya LY
MO Macau MO
MW Malawi MW
ML Mali ML

MR Mauritania MR
NA Namibia NA
NR Nauru NR
NR Netherlands (1-9)N(0-9)NN ^[1-9][0-9] NR

N (!SA|SD| {3}\s(?!SA|
SS)AA SD|SS)[A-Z]
{2}$
NU Nieu NU
QA Qatar QA
RW Rwanda RW
KN Saint Kitts KN
and Nevis
ST Sao Tome and ST

Principe
SC Seychelles SC
SL Sierra Leone SL
SX Sint Maarten SX
SB Solomon SB
Islands
SR Suriname SR
SY Syria SY
TG Togo TG
TK Tokelau TK
TO Tonga TO
TV Tuvalu TV
UG Uganda UG
AE United Arab AE
Emirates
VU Vanuatu VU
YE Yemen YE
ZW Zimbabwe ZW
VA Vatican 120 ^(^00120$)$ VA
SM San Marino 4789N ^(^4789\d{1}$ SM

)$
BL Saint 97133 ^(^97133$)$ BL

Barthelemy

MF Saint Martin 97150 ^(^97150$)$ MF
GP Guadeloupe 971NN ^(^971\d{2}$) GP

$
MQ Martinique 972NN ^(^972\d{2}$) MQ

$
GF French Guiana 973NN ^(^973\d{2}$) GF

$
RE Reunion 974NN ^(^974\d{2}$) RE

$
PM Saint Pierre 97500 ^(^97500$)$ PM

and Miquelon
YT Mayotte 976NN ^(^976\d{2}$) YT

$
MC Monaco 980NN ^(^980\d{2}$) MC

$
WF Wallis and 986NN ^(^986\d{2}$) WF

Futuna $
PF French 987NN ^(^987\d{2}$) PF

Polynesia $
NC New Caledonia 988NN ^(^988\d{2}$) NC

$
GB United A[A]N[A/N] ([Gg][Ii][Rr] GB

Kingdom NAA 0[Aa]{2})|
((([A-Za-z]
[0-9]{1,2})|
(([A-Za-z][A-
Ha-hJ-Yj-y]
[0-9]{1,2})|
(([A-Za-z]
[0-9][A-Za-
z])|([A-Za-z]
[A-Ha-hJ-Yj-
y][0-9][A-Za-
z]?))))\s?
[0-9][A-Za-z]
{2})
SO Somalia AA NNNNN ^(^\S{2}\s SO

\d{5}$)$
MT Malta AAA NNNN ^(^\S{3}\s MT

\d{4}$)$

SH "Saint AAAA 1ZZ ^(^\S{4}\s1ZZ SH

Helena, $)$
Ascension and
Tristan da
Cunha"
GG Guernsey "AAN NAA, AAN ^(^ GG

NAA" \S{2}\d{1}\s
\d{1}\S{2})$|
^(\S{2}\d{2}\
s\d{1}\S{2}$)
$
BN Brunei AANNNN ^(^ BN

\S{2}\d{4}$)$
AI Anguilla AI-2640 ^(ÂI-2640$)$ AI
CA Canada ANA NAN ^(?!.*[DFIOQU CA

])[A-VXY]
[0-9][A-Z] ?
[0-9][A-Z]
[0-9]$
SZ Swaziland ANNN ^(^S{1}\d{3}$ SZ

)$
IO British BBND 1ZZ ^(^BIQQ\s1ZZ IO

Indian Ocean $)$
Territory
IO British BBND 1ZZ ^(^BBND\s1ZZ IO

Antarctic $)$
Territory
LV Latvia CC-NNNN ^(^LV-\d{4}$) LV

$
LT Lithuania CC-NNNNN ^(^LT-\d{5}$) LT

$
IM Isle of Man "CCN NAA, ^(ÎM\d{1}\s IM

CCNN NAA" \d{1}\S{2})$|
^(IM\d{2}\s
\d{1}\S{2}$)$
JE Jersey "CCN NAA, ^(^JE\d{1}\s JE

CCNN NAA" \d{1}\S{2})$|
^(JE\d{2}\s
\d{1}\S{2}$)$
KY Cayman CCN-NNNN ^(^KY\d{1}- KY

Islands \d{4}$)$
AD Andorra CCNNN ^(ÂD\d{3}$)$ AD

AZ Azerbaijan CCNNNN ^(ÂZ\d{4}$)$ AZ
VG British CCNNNN ^(^VG\d{4}$)$ VG

Virgin
Islands
VC Saint Vincent CCNNNN ^(^VC\d{4}$)$ VC

and the
Grenadines
WS Samoa CCNNNN ^(^WS\d{4}$)$ WS
MD Moldova "CCNNNN, CC- ^(^MD\d{4})$| MD

NNNN" ^(MD-\d{4}$)$
BB Barbados CCNNNNN ^(^BB\d{5}$)$ BB
HN Honduras CCNNNNN ^(^HN\d{5}$)$ HN
FK Falkland FIQQ 1ZZ ^(^FIQQ\s1ZZ FK

Islands $)$
GI Gibraltar GX11 1AA ^(^GX11\s1AA GI

$)$
LC Saint Lucia LCNN NN ^(^LC\d{2}\s LC

\d{3}$)$
MS Montserrat MSR 1110-1350 ^[Mm][Ss][Rr] MS

\s{0,1}\d{4}$
DE Germany NNNNN ^(^\d{5}$)$ DE
JM Jamaica NN ^(^\d{2}$)$ JM
SG Singapore NNNNNN ^(^\d{6}$)$ SG
PL Poland NN-NNN ^(^\d{2}- PL

\d{3}$)$
FO Faroe Islands NNN ^(^\d{3}$)$ FO
GN Guinea NNN ^(^\d{3}$)$ GN
IS Iceland NNN ^(^\d{3}$)$ IS
LS Lesotho NNN ^(^\d{3}$)$ LS
MG Madagascar NNN ^(^\d{3}$)$ MG
OM Oman NNN ^(^\d{3}$)$ OM
PS Palestine NNN ^(^\d{3}$)$ PS
PG Papua New NNN ^(^\d{3}$)$ PG

Guinea
CZ Czech NNN NN ^(^\d{3}\s CZ

Republic \d{2}$)$

GR Greece "NNNNN, NNN ^(^\d{5})$| GR

NN" ^(\d{3}\s
\d{2}$)$
SK Slovakia NNN NN ^(^\d{3}\s SK

\d{2}$)$
SE Sweden NNN NN ^(^\d{3}\s SE

\d{2}$)$
TW Taiwan "NNN, NNNNN, ^(^[0-9]{3}) TW

NNN-NN" $|^(^[0-9]
{5})$|^([0-9]
{3}-[0-9]
{2}$)$
BH Bahrain "NNN, NNNN" ^(^\d{3})$| BH

^(\d{4}$)$
JP Japan NNN-NNNN ^(^\d{3}- JP

\d{4}$)$
Afghanistan NNNN ^(^\d{4}$)$
AL Albania NNNN ^(^\d{4}$)$ AL
AR Argentina "ANNNNAAA, ^([A-Za-z] AR

NNNN" {1}\d{4}[a-
zA-Z]{3})$|
^(\d{4}$)$
AM Armenia NNNN ^(^\d{4}$)$ AM
AU Australia NNNN ^(^\d{4}$)$ AU
AT Austria NNNN ^(^\d{4}$)$ AT
BD Bangladesh NNNN ^(^\d{4}$)$ BD
BE Belgium NNNN ^(^\d{4}$)$ BE
BG Bulgaria NNNN ^(^\d{4}$)$ BG
CV Cape Verde NNNN ^(^\d{4}$)$ CV
CX Christmas NNNN ^(^\d{4}$)$ CX

Island
CC Cocos NNNN ^(^\d{4}$)$ CC

(Keeling)
Island
CY Cyprus NNNN ^(^\d{4}$)$ CY
DK Denmark NNNN ^(^\d{4}$)$ DK
SV El Salvador NNNN ^(^\d{4}$)$ SV
ET Ethiopia NNNN ^(^\d{4}$)$ ET

GE Georgia NNNN ^(^\d{4}$)$ GE
GL Greenland NNNN ^(^\d{4}$)$ GL
GW Guinea Bissau NNNN ^(^\d{4}$)$ GW
HT Haiti NNNN ^(^\d{4}$)$ HT
HU Hungary NNNN ^(^\d{4}$)$ HU
LR Liberia NNNN ^(^\d{4}$)$ LR
LI Liechtenstein NNNN ^(^\d{4}$)$ LI
LU Luxembourg NNNN ^(^\d{4}$)$ LU
MK Macedonia NNNN ^(^\d{4}$)$ MK
MZ Mozambique NNNN ^(^\d{4}$)$ MZ
NZ New Zealand NNNN ^(^\d{4}$)$ NZ
NE Niger NNNN ^(^\d{4}$)$ NE
NF Norfolk NNNN ^(^\d{4}$)$ NF

Island
NO Norway NNNN ^(^\d{4}$)$ NO
PA Panama NNNN ^(^\d{4}$)$ PA
PY Paraguay NNNN ^(^\d{4}$)$ PY
PH Philippines NNNN ^(^\d{4}$)$ PH
PT Portugal "NNNN, NNNN- ^(^\d{4})$| PT

NNN" ^(\d{4}-
\d{3}$)$
ZA South Africa NNNN ^(^\d{4}$)$ ZA
CH Switzerland NNNN ^(^\d{4}$)$ CH
SJ Svalbard and NNNN ^(^\d{4}$)$ SJ

Jan Mayen
TN Tunisia NNNN ^(^\d{4}$)$ TN
SI Slovenia "NNNN, CC- ^(^\d{4})$| SI

NNNN" ^(SI-\d{4}$)$
VE Venezuela "NNNN, NNNN- ^(^\d{4})$| VE

A" ^(\d{4}-
\S{1}$)$
DZ Algeria NNNNN ^(^\d{5}$)$ DZ
BT Bhutan NNNNN ^(^\d{5}$)$ BT
BA Bosnia and NNNNN ^(^\d{5}$)$ BA

Herzegovina

KH Cambodia NNNNN ^(^\d{5}$)$ KH
CR Costa Rica NNNNN ^(^\d{5}$)$ CR
HR Croatia NNNNN ^(^\d{5}$)$ HR
CU Cuba NNNNN ^(^\d{5}$)$ CU
DO Dominican NNNNN ^(^\d{5}$)$ DO

Republic
EG Egypt NNNNN ^(^\d{5}$)$ EG
EE Estonia NNNNN ^(^\d{5}$)$ EE
FI Finland NNNNN ^(^\d{5}$)$ FI
FR France NNNNN ^(^\d{5}$)$ FR
GT Guatemala NNNNN ^(^\d{5}$)$ GT
ID Indonesia NNNNN ^(^\d{5}$)$ ID
IT Italy NNNNN ^(^\d{5}$)$ IT
JO Jordan NNNNN ^(^\d{5}$)$ JO
KE Kenya NNNNN ^(^\d{5}$)$ KE
KR "Korea, NNNNN ^(^\d{5}$)$ KR

South"
XK Kosovo NNNNN ^(^\d{5}$)$ XK
KW Kuwait NNNNN ^(^\d{5}$)$ KW
LA Laos NNNNN ^(^\d{5}$)$ LA
MY Malaysia NNNNN ^(^\d{5}$)$ MY
MV Maldives NNNNN ^(^\d{5}$)$ MV
MU Mauritius NNNNN ^(^\d{5}$)$ MU
MX Mexico NNNNN ^(^\d{5}$)$ MX
ME Montenegro NNNNN ^(^\d{5}$)$ ME
MA Morocco NNNNN ^(^\d{5}$)$ MA
MM Myanmar NNNNN ^(^\d{5}$)$ MM
NP Nepal NNNNN ^(^\d{5}$)$ NP
NI Nicaragua NNNNN ^(^\d{5}$)$ NI
PK Pakistan NNNNN ^(^\d{5}$)$ PK
SN Senegal NNNNN ^(^\d{5}$)$ SN
RS Serbia NNNNN ^(^\d{5}$)$ RS
ES Spain NNNNN ^(^\d{5}$)$ ES

LK Sri Lanka NNNNN ^(^\d{5}$)$ LK
SD Sudan NNNNN ^(^\d{5}$)$ SD
TZ Tanzania NNNNN ^(^\d{5}$)$ TZ
TH Thailand NNNNN ^(^\d{5}$)$ TH
TR Turkey NNNNN ^(^\d{5}$)$ TR
UA Ukraine NNNNNN ^(^\d{5}$)$ UA
UY Uruguay NNNNNN ^(^\d{5}$)$ UY
ZM Zambia NNNNN ^(^\d{5}$)$ ZM
PE Peru "NNNNN, CC ^(^\d{5})$| PE

NNNN" ^(PE\s\d{4}$)
$
AX Aland Islands "NNNN, CC- ^(^\d{5})$| AX

NNNN" ^(AX-\d{5}$)$
LB Lebanon "NNNNN, NNNN ^(^\d{5})$| LB

NNNN" ^(\d{4}\s
\d{4}$)$
BR Brazil "NNNNN, ^(^\d{5})$| BR

NNNNN-NNN" ^(\d{5}-
\d{3}$)$
AS American "NNNNN, ^(^\d{5})$| AS

Samoa NNNNN-NNNN" ^(\d{5}-
\d{4}$)$
GU Guam "NNNNN, ^(^\d{5})$| GU

NNNNN-NNNN" ^(\d{5}-
\d{4}$)$
MH Marshall "NNNNN, ^(^\d{5})$| MH

Islands NNNNN-NNNN" ^(\d{5}-
\d{4}$)$
FM Micronesia "NNNNN, ^(^\d{5})$| FM

\d{4}$)$
MP Northern "NNNNN, ^(^\d{5})$| MP

Mariana NNNNN-NNNN" ^(\d{5}-
Islands \d{4}$)$
PW Palau "NNNNN, ^(^\d{5})$| PW

\d{4}$)$
PR Puerto Rico "NNNNN, ^(^\d{5})$| PR

\d{4}$)$

US United States "NNNNN, ^(^\d{5})$| US

\d{4}$)$
VI U.S. Virgin "NNNNN, ^(^\d{5})$| VI

Islands NNNNN-NNNN" ^(\d{5}-
\d{4}$)$
SA Saudi Arabia "NNNNN-NNNN, ^(^\d{5}- SA

NNNNN" \d{4})$|
^(\d{5}$)$
BY Belarus NNNNNN ^(^\d{6}$)$ BY
CN China NNNNNN ^(^\d{6}$)$ CN
CO Colombia NNNNNN ^(^\d{6}$)$ CO
EC Ecuador NNNNNN ^(^\d{6}$)$ EC
KZ Kazakhstan NNNNNN ^(^\d{6}$)$ KZ
KG Kyrgyzstan NNNNNN ^(^\d{6}$)$ KG
MN Mongolia NNNNNN ^(^\d{6}$)$ MN
NG Nigeria NNNNNN ^(^\d{6}$)$ NG
RO Romania NNNNNN ^(^\d{6}$)$ RO
RU Russia NNNNNN ^(^\d{6}$)$ RU
TJTJ Tajikistan NNNNNN ^(^\d{6}$)$
TT Trinidad and NNNNNN ^(^\d{6}$)$ TT

Tobago
TM Turkmenistan NNNNNN ^(^\d{6}$)$ TM
UZ Uzbekistan NNNNNN ^(^\d{6}$)$ UZ
VN Vietnam NNNNN ^(^\d{5}$)$ VN
IN India "NNNNN, \n ^(^\d{6})$| IN

NNN NNN" ^(\d{3}\s
\d{3}$)$
IL Israel "NNNNN, ^(^\d{5})$| IL

NNNNNNN" ^(\d{7}$)$
CL Chile "NNNNNNN, ^(^\d{7})$| CL

NNN-NNNN" ^(\d{3}-
\d{4}$)$
IR Iran NNNNNNNNNN ^(^\d{10}$)$ IR
PN Pitcairn PCRN 1ZZ ^(^PCRN\s1ZZ PN

Islands $)$

GS South Georgia SIQQ 1ZZ ^(^SIQQ\s1ZZ GS

and the South $)$
Sandwich
Islands
TC Turks and TKCA 1ZZ ^(^TKCA\s1ZZ TC

Caicos $)$
Islands
Related Information
Defining country-specific postal code validation for supplier addresses [page 61]

Topics about site configuration parameters for
supplier management
Site configuration parameters for supplier management [page 516]
Self-service site configuration parameters for supplier management [page 517]
Site configuration parameters for supplier

management
Some of the functionality for supplier management is controlled by configuration options that SAP Ariba Support
sets for you. These parameters apply to supplier management in SAP Ariba Supplier Lifecycle and Performance
and SAP Ariba Supplier Information and Performance Management (new architecture).
Application.AOD.EnableAdditionalSupplierUserDataSync (set by SAP Ariba Support)
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,
Application.AOD.EnableAutoApproveSupplierUserOnDataSync, specifies whether
or not the supplier contacts are automatically approved when they are synchronized, or
whether they require manual approval.
Application.AOD.EnableAutoApproveSupplierUserOnDataSync (set by SAP Ariba Support)
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

Application.AOD.EnableAdditionalSupplierUserDataSync is set to Yes.
Application.Password.NewPasswordTokenLifeSpan (set by SAP Ariba Support)

The Application.Password.NewPasswordTokenLifeSpan parameter is an integer
value that specifies the amount of time, in hours, that a temporary password token remains
valid after an administrator generates a password.
This parameter also controls the date displayed by the Supplier Registration Deadline
(SUPPLIER_REG_DEADLINE) token in notifications sent to suppliers.
The default value is 720.

Application.AQS.RFX.ReopenIfClosedInterval (set by SAP Ariba Support)

516 PUBLIC Topics about site configuration parameters for supplier management
Specifies the number of days that an event remains open when it reopens after closing. The
default value is 365 days. If you specify a value of 0, the event remains open for the amount
of time specified in the Due Date setting in the event timing rules.
Self-service site configuration parameters for

supplier management
Some of the functionality for supplier management is controlled by self-service configuration parameters, which
members of the Customer Administrator group can set.
These parameters apply to supplier management in SAP Ariba Supplier Lifecycle and Performance and SAP Ariba
Supplier Information and Performance Management (new architecture).
For information about how to manage parameters, see the Intelligent Configuration Manager administration topics.
Automatically start supplier registrations [page 517]
Enable configurable default sender for supplier invitations [page 518]
Require only attachment and expiration date for supplier certificates [page 519]
Set minimum registration status for event participation [page 520]
Use custom logo and footer for emails sent to suppliers [page 521]
Related Information
Intelligent Configuration Manager administration
Automatically start supplier registrations
Specifies whether to start supplier registrations automatically (automatically create supplier registration projects)
on approval of supplier requests.
ID Application.SM.AutoStartRegistration
Name Automatically start supplier registrations
Default value No
The default value, No, means that a category or supplier manager must manually invite the supplier to register,
either individually or in a mass invitation wave, after the supplier request is approved. Setting this parameter to Yes
automatically sends the registration invitation email to a supplier as soon as the supplier request is approved
without requiring a manual invitation.

Topics about site configuration parameters for supplier management PUBLIC 517
This parameter is only applicable in SAP Ariba Supplier Lifecycle and Performance and SAP Ariba Supplier
Information and Performance Management(new architecture) solutions, which include supplier registration
projects.
Related Information
Enable configurable default sender for supplier invitations

Enables a setting in template external registration questionnaires where template creators can specify a default
sender for registration invitations. This sender shows in the “From” fields of registration invitation emails unless
overridden by requester selection during manual registration invitations.
Full name Application.SM.EnableCustomSenderName
Name Enable configurable default sender for supplier invitations
Default value No
When this parameter is set to Yes, the Message Board area of the Rules step in survey documents in the supplier
registration project template includes a setting, Sender name used for the 'From' and 'Reply To' fields in emails
to participants, that template creators can use to specify a custom sender name such as a supplier onboarding
group for email notifications to suppliers related to registration invitations.
If this parameter is set to No, or if it is set to Yes but a template creator has not configured a custom sender name
for an external registration questionnaire, the associated registration invitations use a generic system alias or the
registration project owner name instead, depending on questionnaire configuration.
Information and Performance Management(new architecture) solutions.
Related Information

Define the length of supplier bank IDs
Specifies the length, in characters, of automatically-generated supplier bank IDs. An automatically-generated bank
ID combines a country-specific prefix, defined by master data, and an automatically generated number. The
maximum length is 4 characters.
ID Application.SM.BankIdSize
Name Define the length of supplier bank IDs
Default value 4
In sites where the automatically-generated supplier bank ID feature, SM-9657, is enabled, SAP Ariba automatically
generates supplier bank IDs as sequential numerical values and, optionally, a country-specific prefix, with a
maximum combined length defined by this parameter. For example, if you set this parameter to 4 and you do not
define country-specific prefixes, SAP Ariba generates sequential, numerical bank IDs starting at 0000 up to a
maximum of 9999 per supplier. If you set this parameter to 4 and define 3-character country-specific prefixes such
as EUR and USD, SAP Ariba generates sequential bank IDs such as EUR0 through EUR9 and USD0 through USD9.
If you use country-specific prefixes for bank IDs, make sure that the value you set for this parameter is at least one
character longer than those prefixes so that automatically-generated bank IDs include at least one number.
Information and Performance Management(new architecture) solutions.
Related Information
Require only attachment and expiration date for supplier

certificates
Specifies that Attachment and Expiration Date are the only two required fields for answers to certificate questions
in external supplier management questionnaires. Otherwise, all certificate fields are required.
ID Application.SM.RequireCertificateAttachmentAndExpirationOnly
Name Require only attachment and expiration date for supplier certificates
Default value False
The default value of False means that all the certificate fields are mandatory and the supplier must enter values in
all the fields. The certificate detail fields are required if a supplier answers Yes to a certificate question. The
certificate detail fields are not required if a supplier answers No to a certificate question.
Setting this parameter to True makes only the Expiration Date and Attachment fields mandatory, which means
that the supplier only needs to enter an expiration date and attach a document to proceed.

 Note
This parameter applies to external supplier management questionnaires.
This parameter is only applicable in sites that include SAP Ariba Supplier Lifecycle and Performance and SAP
Ariba Supplier Information and Performance Management (new architecture), which use supplier registration
projects.
Related Information
Set minimum registration status for event participation

Specifies the minimum registration status that a supplier must have to participate in sourcing events. Valid values
are 0 for Not Invited, 1 for Invited, 2 for Pending Approval, and 3 for Registered.
ID Application.SM.MinimumRegistrationStatusForEventAccess
Name Set minimum registration status for event participation
Default value 0
Suppliers who are below the minimum status can be invited to events, but cannot access them until they have
achieved the minimum status. The restriction applies to suppliers who have been qualified for the event
commodities, regions, and departments using qualification data import but who have not yet achieved the required
registration status.
The default value is 0. The valid values are:
Value Description
0 or Not Invited Suppliers who have not yet been invited to register can partici
pate in sourcing events. No registration invitations are issued.
1 or Invited Suppliers must have already been invited to register to partici

pate in sourcing events. Suppliers who have Not Invited status
when they are invited to events are automatically invited to reg
ister as well, and their registration status changes to Invited.
However, they do not need to submit registration question
naires to participate in events.

Value Description
2 or Pending Approval Suppliers whose registration is pending approval or who are al
ready registered can participate in sourcing events. Suppliers
who have Not Invited status when they are invited to events
are automatically invited to register as well, and their registra
tion status changes to Invited. They must submit registration
questionnaires to participate in events, but their registration
does not need to be approved.
3 or Registered Only suppliers with approved registrations can participate in

sourcing events. Suppliers who have Not Invited status when
they are invited to events are automatically invited to register
as well, and their registration status changes to Invited. They
must submit registration questionnaires and their registrations
must be approved before they can participate in events.
 Note
Note that event templates have a supplier eligibility rule based on registration status. That rule governs whether
or not suppliers can be invited to an event. This parameter governs their ability to participate after invitation.
Changes to this parameter's setting apply only to participants invited to events after they are made.
This parameter is only applicable in sites that include SAP Ariba Supplier Lifecycle and Performance and SAP Ariba
Supplier Information and Performance Management (new architecture), which use supplier registration projects.
Related Information
Use custom logo and footer for emails sent to suppliers

Allows you to specify a custom logo and footer for emails sent to suppliers.
When this parameter is set to Yes, the Custom Email tab appears in Ariba Administrator under Customization
Manager Branding Settings . In addition to the SAP Ariba logo and footer, the custom logo and footer that you
set in this tab appear in emails. When this parameter is set to No, only the SAP Ariba logo and footer appear in
emails.
ID Application.EnableCustomEmailLogoAndFooter
Name Use custom logo and footer for emails sent to suppliers
Default value No
You must be a member of the Customer Administrator or Event Administrator group to customize the invitations
sent to suppliers.

To include your company's logo in registration questionnaire invitations, the parameter
Application.EnableCustomEmailLogoAndFooter must be enabled in your site. In addition, one of your
company's customer administrators must upload the logo on the Custom Email tab. See the Common data import
and administration guide for details.
Related Information
How to customize messages to buyers and suppliers


Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you
agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the
control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at
any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Important Disclaimers and Legal Information PUBLIC 523
www.ariba.com
© 2020 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

SlpSetup English PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SlpSetup English PDF

Uploaded by

Copyright:

Available Formats

PUBLIC

Supplier management setup and administration

SAP Ariba Supplier Information and Performance Management (new

THE BEST RUN

Supplier management setup and administration guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Topics about setting up supplier management users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Topics about importing supplier management data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Supplier management setup and administration guide

Topics about supplier management project template basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Supplier management setup and administration guide

Topics about setting up supplier requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

Topics about setting up supplier registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Topics about setting up supplier qualifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Supplier management setup and administration guide

Topics about setting up preferred supplier management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187

Topics about setting up modular supplier management questionnaires. . . . . . . . . . . . . . . . . . . . 190

Topics about creating supplier forms and questionnaires. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220

Supplier management setup and administration guide

Topics about setting up supplier form and questionnaire approvals. . . . . . . . . . . . . . . . . . . . . . . 316

Topics about customizing supplier management notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . 345

Supplier management setup and administration guide

Topics about issuing mass registration invitations to suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . 362

Topics about performing administrative tasks for supplier management. . . . . . . . . . . . . . . . . . . 367

Topics about managing ERP integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

Supplier management setup and administration guide

Quick reference to optional supplier management features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Topics about default master data for supplier management. . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

Topics about site configuration parameters for supplier management. . . . . . . . . . . . . . . . . . . . . 516

Supplier management setup and administration guide

This guide applies to:

● SAP Ariba Supplier Lifecycle and Performance

Quick reference to SAP Ariba Supplier Management solutions features

Managing suppliers and supplier lifecycles

Supplier Data API with Pagination

Strategic sourcing and supplier management group descriptions

Migrating suppliers to the unified vendor model

Configuring supplier performance management reviews

Running supplier performance management reviews

Managing project email notifications

Project template guide

Managing projects, teams, documents, and tasks

Supplier management setup and administration guide

Supplier management setup checklist [page 24]

APIs for SAP Ariba Supplier Management solutions [page 26]

Where to find more information [page 29]

What is supplier management in SAP Ariba Supplier

Supplier management setup and administration guide

SAP Ariba Supplier Lifecycle and Performance also includes:

About internal supplier requests [page 11]

About internal supplier requests

The internal supplier request template determines:

● What information users need to provide when submitting the request.

Supplier management setup and administration guide

About external supplier requests [page 12]

About external supplier requests

The external supplier request project template determines:

● What information suppliers need to provide when submitting the request.

Supplier management setup and administration guide

About internal supplier requests [page 11]

About new supplier registrations

There are two types of supplier registration:

Registration type Description

External Invites a supplier contact to create an account or log into an

After a supplier completes an external registration, you can es

Through a mass invitation wave, which a customer administra External

ever an uninvited supplier is invited to a sourcing event that re

Set up and publish theinternal supplier request project tem

Set up and publish the supplier disqualification project tem

(Optional) Customize notifications for all supplier manage