SAP Ariba SLP - Actividades de Migración de SM

Migrating suppliers to unified vendor model
Manual Migration step by step

SAP Procurement Services | Intelligent Delivery Group, SAP
22/02/2022
Public
Agenda
• Overview
• Process Flow and Activity Planning
• Migration step by step
• Post-migration activities
• Migration Tool Commercial Implications
© 2022 SAP SE or an SAP affiliate company. All rights reserved. | Public 2

Overview
Process Flow and Activity Planning
Step 1: System Preparation - Migration Mode ON
Step 2
Step 3
Step 4
Step 5
Step 6
Overview
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14: System preparation - SLP activation
Additional Information
Migration Tool Commercial Implications

Overview
Migration Context and Important Considerations 1/2
• What is migration in terms of SLP?
If a customer realm was enabled with Sourcing, Contracts or Legacy SIPM (Not SLP) and if there are suppliers and users created in the
sourcing site, these records need to be migrated from sourcing to SLP data base.
• This guide is an extract from the Migrating Suppliers to the Unified Vendor Model and has some additional considerations included.
To perform the migration we strongly recommend to read all the detailed information included in the guide that can be downloaded in it´s
last version from SAP Ariba Connect.
Migrating suppliers to the unified vendor model - Topics about understanding supplier migration and the unified vendor model at:
https://help.sap.com/viewer/e2f3b8d54c144869bb1377bf822bf836/LATEST/en-US/c7721e54836541fa9c8ee433a765a44e.html
• The activities related to file exporting, preparation and importing should be performed by Customer together with Partner (when apply).
With the support of Ariba CFS team as per described in the SLP Deployment Description.
Ariba CFS team is not able to manipulate any of the files included in this process. Due to compliance policies.
• It is important to simulate/test the supplier onboarding processes in Test realm as closely as possible to what is currently going on
in Prod realm.
• Performing the SM Migration activities in Test realm is important for the customer to get involved with all the considerations they
should follow in order to prepare the Production migration files (Described in this document).
• It is highly recommended to start with the preparation of the Production realm migration files as soon as possible and from the
beginning of the implementation project. Specially if the number of suppliers to migrate is large.
Overview
Migration Context and Important Considerations 2/2
• The migration process should be performed all at once. In other words, once the SLP is active the migration mode should not be
enabled again.
• The migration is performed for each realm individually. You can not migrate suppliers from Prod into Test realm.
o Test realm Test realm.
o Production realm  Production realm.
• If Dev realm is available, it may be used Supplier Request and Supplier Registration templates designing and process testing.
Afterwards, it may be uploaded to Test realm before SPQ migration (Step 9).
• SPQ Test/Prod homologation: It is strongly recommended updating the SPQ in Test realm as per configured in Prod realm to
avoid rework on the mapping and unexpected errors in Prod.
• Suppliers with an associated ANID that the Customer requires to continue working with them, should be all migrated. Otherwise, it
won´t be possible to invite these suppliers after migration.
• All suppliers associated with any Sourcing event or Contract should be migrated.

Overview
Step 2
Step 3
Step 4
Step 5
Process Flow and

Step 6
Step 7
Step 8
Step 9
Step 10
Activity Planning
Step 11
Step 12
Step 13

Process Flow Legend:
Customer / Partner SAP Ariba CFS
Customer / Partner supported by SAP Ariba.
Part 1 - SM Migration Mode SLP templates for configuration only:

Step 1: System Preparation
Request and Registration
Migration Mode ON
Part 1.1 - Export Optional
Step 2: Export Is SPQ Step 4: Export (Prod realm) Does SPQ YES Step 5: Export
Step 3: Export used
YES
Supplier Organization Supplier Profile (SPQ) must be SPQ Template (Supplier
Supplier Users file currently? migrated?
and PartID files answers Profile Questionnaire) Parallel with
NO NO steps 5~9
Part 1.2 – Preparation
Step 7: Prepare Step 9: Prepare

Step 6 : Prepare Step 8: Prepare Supplier Profile Questionnaire
Supplier Organization
Supplier Organization file Supplier Users file (SPQ) Template  Supplier
PartID
Registration Template mapping.
Part 1.3 – Import and monitoring
Step 10: Import Step 11: Import SLP templates for configuration only: Step 12: Import
Supplier Organization files Supplier Users file Request and Registration SPQ Mapping file
Step 13: Monitor the Is migration

migration status finished? NO
YES
Part 2 - SLP activation Performed only once and when all

Step 14: System preparation
migration activities are totally finished.
Migration mode OFF + SLP activation
Supplier Qualification and Preferred
SM Migration is finished and SLP is active! processes are now available.

Activities Planning
Example
XXX = SLP activities

duration depends on the
project planning.
ATTENTION: This is a only a suggestion. Please consider the

period and dates defined in the official Project Plan elaborated
by your Project Manager.

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9 - Migration Mode ON
Step 10
Step 11
Step 12
Step 13

Migration Mode ON
• This step is performed by SAP Ariba CFS (Cloud Functional Services) team.
• Some system features will be set on each realm individually.

o Enable the feature SIPMToSMMigrationMode for a manual migration, into Feature Manager  Feature Availabity Status.
o Enable the feature Migration from SIPM to SM, into SM Administration -> Feature Control
o Add the users to the following groups:
 SM ERP
 SM OPS Administration
• Migration Mode on: Only Supplier Request and Supplier Registration templates. Available for configuration.
o Note: If you don’t see the Supplier Request and Supplier Registration template, you’ll need to run the Scheduled Task
“MigrateSMWorkspaces”.

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 2: Export Supplier
Step 8
Organization and Supplier
PartID files
Step 9
Step 10
Step 11
Step 12
Step 13

Step 2: Export Supplier Organization and PartID files
Data Exporting: Supplier Organization and Supplier PartID
1. Click on Manage  Administration  Data Import/Export. Search for “Export Supplier Organizations (CSV)” and then click on the “export”
button.
2. Once you have saved the SupplierOrganizationExport.zip file locally, note that it will be in a ZIP file format. Extract the “.CSV files from the
*.zip” file.
a) “SupplierOrganization_Export.csv” – file 1
b) “SupplierOrganizationOrganizationIDPart_Export.csv” – file 2
3. Be very careful if you do not have a Text editor and decide to use MS Excel. The FAQ 167082 may help you with some tips.

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9 Users file
Step 10
Step 11
Step 12
Step 13

Step 3: Export Supplier Users file
Data Exporting: Supplier Users
1. Click on Manage  Administration  Data Import/Export. Search for “Export Supplier Users (CSV)” and then click on the “export”
button.
REMINDER NOTE: The Supplier Contacts Files CAN NOT be saved locally on an SAP computer as for legal implications. The customer will
need to download this specific file, save it to their desktop, the manipulation of the file will need to be done on their computer, and then
uploaded to SM admin on the CUSTOMER COMPUTER ONLY at this time.
2. Be very careful if you do not have a Text editor and decide to use MS Excel. The FAQ 167082 may help you with some tips.

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Profile Questionnaire
Step 8
Step 9
(SPQ) answers from
Step 10 Production realm
Step 11
Step 12
Analyze and decide: Are you migrating Supplier Profile
Step 13
Questionnaire (SPQ)?

Step 4: Export Supplier Profile Questionnaire (SPQ) answers
Analyze the supplier’s SPQ answers (Production realm)
• This step is optional. The supplier profile questionnaire answers may be downloaded from Production realm in order to
help you to decide if this information must be migrated to SLP.
• The customer needs to review and analyze the information that have into their production realm:
o Which questions are really relevant?

o Are they answered by the suppliers?
o Do you have enough quality data to performed a SPQ migration?

Step 4: Export Supplier Profile Questionnaire (SPQ) answers
Analyze the supplier’s SPQ answers (Production realm)
1. Click on Manage  Administration  Supplier and Customer Manager  Supplier Profile Import/Export. Click on “Export” button and wait
until the “Exported File” is ready for download:
2. Analyze it carefully: Which questions are really relevant? Which suppliers answered the questions? Finally, are you migrating SPQ to SLP
Registration Questionnaire?

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
(SPQ) Template
Step 9
Step 10
Step 11
Step 12
Step 13

Step 5: Export Supplier Profile Questionnaire Template
Export of the Supplier Profile (SPQ) Questionnaire Template - Questions
• This step needs to be performed for an SAP Ariba user.
• It will export the current set of questions, or fields, that

make the Extended Supplier Profile in a specific
customer realm.
• The supplier profile questionnaire must be exported

while your site is in migration mode. Supplier
Knowledge area is no longer available after exiting
migration mode and fully enabling SAP Ariba Supplier
Lifecycle and Performance or SAP Ariba Supplier
Information and Performance Management (new
architecture).
1. Access Manage  Supplier Knowledge 

Supplier Profile Questionnaire. In Documents
tab, click on the Supplier Profile
Questionnaire  Open option.
2. Click on Excel Export. (Only visible to
‘Customer Support Admin’)
Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 6: Prepare Supplier
Step 9 Organization file
Step 10
Step 11
Step 12
Step 13

Step 6: Prepare Supplier Organization file
Data Preparation – Step by Step: SupplierOrganization_Export
1. Define a strategy about which suppliers you want to migrate to SLP.
a) Define your supplier migration criteria. For example:

• Suppliers you have done business with for the last X months/years.
• Suppliers involved in active Contracts and Sourcing events.
• Do not migrate duplicated suppliers.
b) Analyze the possibility to migrate all suppliers with ANID and all suppliers associated with any Sourcing event or Contract.
c) Analyze the possibility to deactivate in old architecture (SIPM) those organization (IsSupplier=Yes) you decided not migrate
b) Delete those you will not be loading into Ariba SLP from the “SupplierOrganization_Export” file.
c) For SM migration in Production realm, communicate the company about this activity and avoid creating new supplier
organizations after migration files are exported.
d) Never add new organizations into the files. This will cause issues.
e) Some adjustments mentioned in this documents must be done directly in the system and then export the supplier organization
files again for data depuration and others changes must be done in the file. The information is mentioned in the steps.
f) Do not change this information in the file!

2. Only suppliers are supported and Customers organizations will not be migrated.
The adjustment described here must be done directly in the system and then export the supplier organization files again for data
depuration. Do not change this information in the file.
a) No organizations may be set with same value (Yes/Yes or No/No) for the columns “IsCustomer” and “IsSupplier” respectively
as it may cause issued for “Suite Integration”. You must decide if an organization will be kept as customer OR supplier.
b) All customer organization – “IsCustomer = Yes” – must be deleted from the file.
c) Only supplier organization – “IsSupplier = Yes” – will be migrated to SAP Ariba SLP.

3. Review the supplier statuses in SIM/SIPM by analyzing the data in column “IsOrgApproved”.
The adjustment described here must be done directly in the system and then export the supplier organization files again for data
depuration. Do not change this information in the file.
a) You can only migrate active suppliers with Approved or Rejected status.
b) In sites with SAP Ariba Supplier Information and Performance Management (classic architecture) solutions, suppliers with
active approval tasks or supplier profile questionnaire updates that are pending approval are not migrated.
c) Supplier in other then Approved and/or Rejected statuses must be completed in SIM/SIPM first.
d) The Customer can decide if Suppliers in the Rejected statuses may be migrated.
Legend:
• 0: Unapproved - The organization is unapproved (Initial)
• 1: Rejected - The organization is rejected.
• 2: Approved - The organization is approved.
• 3: In Registration - The organization is in the process of being registered.
• 4: Resubmit for Approval.

4. Adjust the file content

a) Do not change the files (inside the *.zip) names.
b) Delete the first line, which specifies UTF-8 encoding.
c) “SytemID” field: Remove the records [Buyer], [Undefined], [System] and [Default]. This field should not be empty.
d) Attention to field maximum length. See the official guide for detailed information. Some examples:
• “CorporateAddress.PostalAddress.State”: Length must be reduced to 2 characters. Example: "Rio de Janeiro" to "RJ". Allow blanks.
• CorporateAddress.PostalAddress.City: Length <= 40 chars
• CorporateFax: Length <= 40 chars
• Organization “Name” and Lines of address: Length <= 125 chars
• Postal Code: <= 10 chars
e) Search for “blank space” at the end of the data and remove it. It generates error in the upload. Examples:
• CorporateEmailAddress, CorporateUrl, mail address, name, etc.
• CorporateURL: Remove the blank spaces, in format http:// or www.
f) “SupplierIntegrationStatus”: Just keep it (Ex.: value=“0”) for integration if the file shows this field.
g) Be careful using commas (,) within any the text of any field, considering we will be working with *.CSV (comma delimited). It is usually
is common in Address Lines, Descriptions, Names, etc. Example: columna1, “Calle 5, número 4”,
h) Avoid to have double quotes (") within any the text of any field. Example “”text””.
i) If you use the “Encoding Type UTF-8” for the Data upload (Step 6), avoid to use some special chars: %, $, &, # etc.

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9 Organization PartID file
Step 10
Step 11
Step 12
Step 13

Step 7: Prepare Supplier Organization PartID file
Data Preparation – Step by Step: OrganizationIDPart_Export
1. Adjust the file content

a) Do not change the file name.
b) Keep the line order as per exported. It is very important when importing by packages.
c) Remove the following records, when present: “Parent.SystemID = [Buyer], [Undefined], [System] and [Default]”.
b) All the suppliers records removed from “SupplierOrganization_Export” must also be removed from
“SupplierOrganizationOrganizationIDPart_Export” file.
c) The Parent.SystemID is unique, do not change it.
You may compare by performing MS Excel

VLOOKUP formula between both files:

Data Preparation – Step by Step: OrganizationIDPart_Export – ERP VendorID
SAP Ariba Supplier Management solutions migrate organization IDs to the unified vendor model as follows:
• OPTION 01: Mandatory migration of organization IDs in the sap (or other) domain: SAP Ariba Supplier Management solutions
always look for organization IDs in the domain sap (or others) and migrates their associated values to ERP vendor ID. Organization
IDs in the sap domain are always migrated to the ERP vendor ID if they are present. The domain name must be an exact match to the
values specified here, including the use of all lowercase letters.
ERP vendor ID's length when SAP, must be 10 digit long. In some customers, SystemID (coming from Sourcing) customers have it
related with ERP vendor ID but without the leading zeros.
(!) Be aware when using MS Excel because sometimes it removes the 0 at the left (see Topic “ Additional Information”). If you upload
the OrganizationIDPart_Export again with correct ERP vendor ID, the system will duplicate the supplier in SLP.
Domain
“sap”

Data Preparation – Step by Step: OrganizationIDPart_Export – ERP VendorID
• OPTION 02: Automatic assignment of an SAP Ariba Supplier Management solutions-generated ERP vendor ID: If a migrating
supplier does not have an organization ID in the sap, (or other) domain, and either it doesn't have an organization ID in one of the
custom domains you specified or you did not specify any custom domains, and you did not use the option to migrate the SystemID, SAP
Ariba Supplier Management solutions automatically assign it an ERP vendor ID that begins with "VDR" during migration.
• OPTION 03: Optional migration of SystemID to ERP vendor ID: You can use the Consider Object ID as ERP Vendor ID data import
option to migrate the value in the supplier organization SystemID field to ERP vendor ID. The SystemID field is a field in supplier
organization import and export files, including the SupplierOrganizations.zip file you use to migrate your supplier organization data.
• OPTION 04: Optional migration of organization IDs in custom domains: See the official guide for detailed information.

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9 Users file
Step 10
Step 11
Step 12
Step 13

Step 8: Prepare Supplier Users file
Data Preparation – Step by Step: NewSupplierUserExportCSV
1. Delete the first line, which specifies UTF-8 encoding.
2. Do not add new supplier contacts appart from the existing ones.
3. Remove invalid supplier contacts

All supplier contacts associated to the supplier organizations removed from “SupplierOrganization_Export” must also be removed
from “NewSupplierUserExportCSV” file.
3. Identify the suppliers contacts you want to migrate

a) Even though you decide to import a supplier organization, you can decide to import or not its respective supplier contact.
b) Supplier contacts with the same email address, within the same organization, are not supported and will generate an error
message upon import.

Step 8: Prepare Supplier Users file
Data Preparation – Step by Step: NewSupplierUserExportCSV
4. After the final TimeZone column, add the following additional columns:
These columns are mandatory for the import but can be empty: firstName, middleName, lastName, countryCode,
Telephone, isPrimary.
a) (Optional) For any FullName values you do not want to break into first, last, and middle names using the automatic system,
enter values in the firstName, middleName, and lastName columns and remove the name from the FullName column on that
row.
b) (Optional) To designate a supplier contact as the primary contact for the supplier, enter TRUE in the isPrimary column.
• In case you have multiples contacts for your supplier, a Primary contact may be defined.
• IsPrimary is True/False field type and can be left empty in case the supplier just have one contact.
• In case of multiple supplier contacts, only one of them can be defined as “IsPrimary = True” to avoid error message upon
import.

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9 (SPQ) mapping to SLP
Registration Template
Step 10
Step 11
Step 12
Step 13

Step 9: Supplier Profile Questionnaire (SPQ) mapping
Mapping steps 1/2
• You need a csv document with three columns
• processID  This column contain the ID of the

destination document, whether the external or
internal questionnaire. You can search it into SM
Administration  Questionnaires

Mapping steps 2/2
• fromId  This column contain the value of the column “Profile Question Id” from the SPQ export. Only questions are
supported, not Sections nor Requirements.
• toId  This column contain the value of the column “KPI Id” from the excel export of the questionnaire where the
destination question was created in the Registration template.

Mapping considerations
• Questions into the SPQ, that were configured to be responded by an intern user, need to go to a Internal Form.
• Questions into the SPQ, that were configured to be responded by the supplier, need to go to the External Registration
Questionnaire.
• The questions to be migrated must have the exact same settings for answer type and acceptable answers.
• The Supplier Registration template must be published and with at least one external registration questionnaire.
• All the tasks from the project, need to be “Approved”:

o Mandatory task that generates SPQ migration error.
o Suppliers that has this type of task “Profile changes need to be approved for this organization” cannot migrate.
o This type of task must be approved for the suppliers that require SPQ migration.

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 10: Import Supplier
Step 8
Organization and
Organizations IDs files
Step 9
Step 10
Step 11
Step 12
Step 13

Step 10: Import Supplier Organization and PartIDs files
How to Import
1. Before you start:
• Make sure you followed all the steps

and orientations described in Steps 05
and 06 of this document.
• SAP Ariba recommends that you divide

the supplier organization export into
batches to prevent performance
problems.
• The Import Summary tab shows the

status of your import.

Step 10: Import Supplier Organization and PartIDs files
How to Import
2. Import the first batch of supplier organizations into the unified vendor model by performing the following steps:
a. On the dashboard, choose Manage  SM Administration  Click Data import and export.
b. On the File type dropdown menu, choose Suppliers from sourcing.
c. Click Choose File  Navigate to SupplierOrganizationExport.zip and select it.
d. (Optional) To migrate organization IDs in one or more domains other than sap, psoft, or oracle to ERP vendor ID, enter the
domain names, separated by commas, in the Optional custom domain names field.
e. (Optional) To migrate the supplier organizations' SystemIDs to ERP vendor ID if no matching sap, psoft, oracle, or custom
organization ID domain is found, check Consider Object Id as ERP Vendor Id.
f. (Optional) If your supplier organization CorporateAddress.PostalAddress.State is longer than 2 characters, to include it in the
migration, check Consider state as state Name.
g. Click Import.
3. Repeat these steps to import all of your batches of supplier organizations.

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 11: Import Supplier
Step 9 Users file
Step 10
Step 11
Step 12
Step 13

Step 10: Import Supplier Users file
Step by Step: NewSupplierUserExportCSV
1. Import the Supplier Contacts using

the Sample File
Go to Manage  SM Administration 
Data import and export File type:
Supplier Contacts from Sourcing 
Import tab  “Choose file to import” 
click on “Choose File”.
You may also chose an “encoding type”

as per your need.
The file must be saved in *.csv format.

We suggest you to perform the upload
by slots.

Step 10: Import Supplier Users file
Step by Step: NewSupplierUserExportCSV
2. Monitor the importing

process
The Import Summary tab
shows the status of your
import.
Attention: Follow the
instructions described in
Step 08 of this document
to avoid errors!

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 12: Supplier Profile
Step 8
Questionnaire mapping
upload
Step 9
Step 10
Step 11
Step 12
Step 13

Step 12: Supplier Profile Questionnaire mapping upload
How to import
1. You have to import the file “Mapping.csv” in SM

Administration  Data import and export
2. On the File type dropdown menu, choose S4 SM
Migration.
3. Click Choose File and navigate to the file and select it.
4. You can migrate the SPQ for some suppliers only, and
to do that, check the option “Only migrate these
suppliers”. It will appear a text box where you have to
indicate the SM ID of those suppliers.
5. Click Import.
6. The Import Summary tab shows the status of your
import.

Step 12: Supplier Profile Questionnaire mapping upload
Considerations
• A successfully SPQ migration, synchronizes the supplier profile questionnaire answers to the mapped supplier
registration questionnaire content.
• Once the migration is done, the suppliers could have the following status:
o Public suppliers that have approved supplier profile questionnaires move to Registered status.
o Public suppliers with denied supplier profile questionnaires move to Denied registration status.
o Private suppliers move to Not Invited registration status and you must invite them to register either
manually or through mass registration invitation waves

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 13: Monitor Manual
Step 9 Migration Status
Step 10
Step 11
Step 12
Step 13

Step 13: Check Manual Migration Status
Control the progress of the migration task
The progress of the migration task can be controlled by downloading the file from SPQ Migration Report.
1. On the dashboard, choose Manage  SM Administration  Click Data import and export  On the File type dropdown menu,
choose SPQ Migration Status Report.
2. Click Export  Save the exported CSV file to the location of your choice.
Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 14: System
Step 7
Step 8
Preparation – Migration
Step 9 mode OFF and SLP
activation
Step 10
Step 11
Step 12
Step 13

Migration Mode OFF and SLP activation
• Disable the feature Migration from SIPM to SM, into SM Administration -> Feature Control
• Disable the feature SIPMToSMMigrationMode for a manual migration, into Feature Manager  Feature Availabity Status or
• Disable the feature SIPMToSMAutoMigrationMode for an automatic migration, into Feature Manager  Feature Availability
Status.
• Go to Edit Site profile and uncheck the option Ariba SPM and checked Ariba Supplier Lifecycle and Performance or SAP Ariba
Supplier Information and Performance Management (new architecture).
• If your solution is SAP Ariba SLP, you need to enable the feature SM-Supplier Lifecycle and Performance Management.

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Post-Migration activities
Step 10
Step 11
Step 12
Step 13

Post-Migration
Activities
• Review and update the following parameters:
Parameter Description SLP

Review the parameter Application.SM.MinimumRegistrationStatusForEventAccess Up to
as it allows you to specify the minimum registration status that a supplier must have customer
before they can access a sourcing event. Event templates can also set registration needs.
or qualification requirements for participating in events. Be aware that while
Application.SM.MinimumRegistrationStatusForEventAccess
migration does not affect sourcing events that are underway during migration, your
https://support.ariba.com/Item/view/182303
settings for registration requirements using this parameter or in event templates
might affect the ability of migrated suppliers to access events that start after SAP
Ariba Supplier Lifecycle and Performance or SAP Ariba Supplier Information and
Performance Management (new architecture) is fully enabled.
User.CanSupplierSelfRegister Controls the showing of the link that lets new suppliers self-register. NO
SupplierRegistrationLinkSetting This parameter controls the behavior of registration link on the supplier login page. 0
Before you invite any new or migrated suppliers to register, participate in a sourcing 0
event, or fill out any other type of external supplier management questionnaire, make
sure that the parameter Application.User.PromptSupplierForProfileAtLogin is set to 0
User.PromptSupplierForProfileAtLogin
in your site. Settings other than 0 require suppliers to fill out the supplier profile
questionnaire before they can participate in sourcing events, and Ariba Network for
Suppliers treats supplier management questionnaires as events.
• Review the groups Supplier/Customer Agent and Supplier/Customer Manager and remove those users that should no
longer be included there.

Post-Migration
Considerations
• If you migrated suppliers with no migrated users associated, you must add at least one valid supplier contact before you can send
them additional questionnaires.
• For migrated private suppliers, if you want them to register and fill out the registration questionnaire, you can either create mass
registration invitation waves or manually invite them to register.
• If your solution is SAP Ariba Supplier Lifecycle and Performance, the supplier qualification, disqualification, and preferred supplier
management project templates are now available in your site (*).
• Migration files relationship with SLP:

o Supplier Organization moves to SLP 360 view;
o Supplier Organization Users moves SLP Supplier contacts;
o Supplier Profile Questionnaire (SPQ) moves Supplier Registration Questionnaires – Depending on the mapping.
• SAP Ariba official SM Migration guide: Migrating suppliers to the unified vendor model
https://help.sap.com/viewer/e2f3b8d54c144869bb1377bf822bf836/LATEST/en-US/c7721e54836541fa9c8ee433a765a44e.html
• SAP Ariba FAQ 167082 - Create UTF-8 CSV file from a Microsoft Excel spreadsheet containing Asian or Special
Characters. How? (!) Be careful with zeros at left side (for example: ERP Vendor ID).

Overview
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Migration Tool
Step 9
Step 10
Commercial Implications
Step 11
Step 12
Step 13

General information
• The Migration tool (export, depuration and import) CAN be completely done by the customer.
• The Migration is done only one time in each realm (Test and Production). In other words, it is not possible to divide the migration
in packages, waves, etc.
• As part of the Deployment Description, the migration tool will is included in the new set up service. Responsibilities will include:
o Migrating Supplier Organizations
o Migrating Supplier Contacts*
*Customers must migrate their own supplier contact data due to PII implications.
o Migrating Up To 20 SPQ Questions to Supplier Registration
• The activities related to file exporting, preparation and importing should be performed by Customer together with Partner (when
apply). With the support of Ariba CFS team.
Ariba CFS team is not able to manipulate any of the files included in this process. Due to compliance policies.
• Additional Services can be purchased if customers would like additional help doing the migration activities or if they have more
SPQ/Supplier Registration questions to be mapped.
Thank you.
Partner logo

SAP Ariba SLP - Actividades de Migración de SM

Uploaded by

Document Information

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

SAP Ariba SLP - Actividades de Migración de SM

Uploaded by

Copyright:

Available Formats

Migrating suppliers to unified vendor model

Manual Migration step by step

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | Public 2

Process Flow and Activity Planning

Step 1: System Preparation - Migration Mode ON

Step 14: System preparation - SLP activation

Migration Tool Commercial Implications

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | Public 5

Process Flow and Activity Planning

Step 1: System Preparation - Migration Mode ON

Process Flow and

Step 14: System preparation - SLP activation

Migration Tool Commercial Implications

Customer / Partner supported by SAP Ariba.

Part 1 - SM Migration Mode SLP templates for configuration only:

Part 1.1 - Export Optional

Part 1.2 – Preparation

Step 7: Prepare Step 9: Prepare

Part 1.3 – Import and monitoring

Step 13: Monitor the Is migration

Part 2 - SLP activation Performed only once and when all

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | Public 7

XXX = SLP activities

ATTENTION: This is a only a suggestion. Please consider the

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | Public 8

Process Flow and Activity Planning

Step 1: System Preparation - Migration Mode ON

Step 14: System preparation - SLP activation

Migration Tool Commercial Implications

• Some system features will be set on each realm individually.

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | Public 10

Process Flow and Activity Planning

Step 1: System Preparation - Migration Mode ON

Step 14: System preparation - SLP activation

Migration Tool Commercial Implications

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | Public 12

Process Flow and Activity Planning

Step 1: System Preparation - Migration Mode ON

Step 14: System preparation - SLP activation

Migration Tool Commercial Implications

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | Public 14

Process Flow and Activity Planning

Step 1: System Preparation - Migration Mode ON

Migration Tool Commercial Implications

o Which questions are really relevant?

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | Public 16

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | Public 17

Process Flow and Activity Planning

Step 1: System Preparation - Migration Mode ON

Step 14: System preparation - SLP activation

Migration Tool Commercial Implications

• This step needs to be performed for an SAP Ariba user.

• It will export the current set of questions, or fields, that

• The supplier profile questionnaire must be exported

1. Access Manage  Supplier Knowledge 

Process Flow and Activity Planning

Step 1: System Preparation - Migration Mode ON

Step 14: System preparation - SLP activation

Migration Tool Commercial Implications

1. Define a strategy about which suppliers you want to migrate to SLP.

a) Define your supplier migration criteria. For example:

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | Public 21

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | Public 22

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | Public 23