SC Mig Guide v3

Configuration Guide CUSTOMER
Document Version: 1.3 – 2018-02-07
Migration of SAP SRM Shopping Carts

during system conversion to SAP S/4 HANA
Typographic Conventions
Type Style Description
Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
Example Emphasized words or expressions.
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as
they appear in the documentation.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .
CUSTOMER Migration of SAP SRM Shopping Carts

2 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Typographic Conventions
Document History
Version Date Change
1.0 2016-03-07 Initial Creation
1.1 2016-09-01 Update
1.2 2017-11-30 Update
1.3 2018-02-07 Update
Migration of SAP SRM Shopping Carts CUSTOMER

Document History © 2016 SAP SE or an SAP affiliate company. All rights reserved. 3
Contents
1 Migration of SAP SRM shopping carts during or after system conversion to SAP S/4
HANA ............................................................................................................................................... 6
2 Getting started .............................................................................................................................. 7

2.1 Design of the migration logic ................................................................................................................ 7
2.2 Supported deployment scenarios........................................................................................................ 7
2.2.1 Overview ................................................................................................................................ 8
2.2.2 One Client Deployment SRM@ERP ..................................................................................... 8
2.2.3 Deployment on separate machine in Classic and Extended Classic Scenario ................ 9
2.3 Which documents are migrated and how will they look like after migration.................................. 10
2.3.1 Shopping Carts..................................................................................................................... 12
2.3.2 Purchase Orders ..................................................................................................................14
2.3.3 Other documents and SAP SRM processes ...................................................................14
2.3.4 Special issues during SC migration ....................................................................................14
2.4 Documents and SAP notes for the migration ....................................................................................16
2.4.1 Required documents and notes .........................................................................................16
2.4.2 Additional documents and SAP Notes ...............................................................................18
3 Installation ................................................................................................................................... 19
3.1 System Requirements .........................................................................................................................19
3.1.1 One Client Scenario .............................................................................................................19
3.1.2 SAP SRM deployed on a separate machine, Conversion to SAP S/4 not yet performed
...............................................................................................................................................19
3.1.3 SAP SRM deployed on a separate machine, Conversion to SAP S/4 not yet performed
.............................................................................................................................................. 20
3.2 Installation of new objects in SRM_SERVER ..................................................................................... 20
3.2.1 Instructions valid for all deployment scenarios ............................................................... 20
3.2.2 Additional instructions if SAP SRM is deployed in One Client Scenario ......................... 21
3.2.3 Installation of new objects in SAP_APPL / S4CORE......................................................... 21
3.2.4 Updating the objects........................................................................................................... 22
4 Preparing the system for SC migration ................................................................................... 23

4.1 General settings ................................................................................................................................... 23
4.1.1 Important information ........................................................................................................ 23
4.1.2 Authorizations ..................................................................................................................... 23
4.2 Settings for downtime migration in One Client Scenario................................................................. 24
4.2.1 Setting up migration scenario............................................................................................ 24
4.2.2 Pre Check Class .................................................................................................................. 25
4.2.3 Plug-In Class for Deletion ................................................................................................... 26
4.2.4 DDIC User ............................................................................................................................ 26
4.2.5 RFC Connections ................................................................................................................ 27
5 Executing the migration reports ................................................................................................. 28

5.1 Standalone Execution ......................................................................................................................... 28

4 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Contents
5.2 Execution during system conversion downtime ...............................................................................29
6 Post Processing ........................................................................................................................... 31
7 BADI interfaces ............................................................................................................................ 33

7.1 BBP_BD_SC_MIG_TO_HANA ............................................................................................................. 33
7.2 BBP_BD_MIG_REQ_AUTH ..................................................................................................................33
Migration of SAP SRM Shopping Carts CUSTOMER

Contents © 2016 SAP SE or an SAP affiliate company. All rights reserved. 5
1 Migration of SAP SRM shopping carts
during or after system conversion to SAP
S/4 HANA
As a SAP Business Suite customer you can move from different SAP ERP start releases to SAP S/4HANA, On-
Premise Edition. SAP S/4 Hana comes with an integrated solution (application) for Self Service Procurement
(SSP). If you use SAP SRM (installed on the same machine as ERP, One Client scenario or installed on a separate
machine) you can migrate your existing SRM shopping carts documents into that new solution.
SAP provides a report for that purpose. After conversion a former SAP SRM SC can be accessed and processed
via SAP S / 4 Hana Self Service Procurement. Manual steps apply. Migration is limited to the documents and the
data itself. You will have to review and adapt your custom coding as well as your processes for the migration to
SAP S / 4 HANA.
What is this document about?
This document guides you to the process of converting and migrating your SAP SRM shopping carts to SAP S/4
HANA purchase requisitions when replacing your current SAP SRM solution with SAP S/4 HANA SSP. It is
designed for customers who are:
 currently using SAP SRM in any deployment scenario in combination with SAP ERP AND
 are planning to convert their SAP ERP system to SAP S/4 HANA On Premise Edition AND
 are planning to introduce Self Service Procurement processes in SAP S/4 HANA after system conversion
Chapter 2 provides general information about the migration logic. It describes which scenarios are supported and
how the migrated documents will be handled during or after conversion.
For a description about the technical setup and information about the steps you need to perform for migration
please refer to chapter 3 - 7
What other documents do you need?
The SC migration may be part of an overall system conversion to SAP S / 4 Hana, especially when SRM is used in
the “One Client Scenario”. In this case, you should refer to the Conversion Guide for SAP S/4HANA On-Premise
edition (see chapter 2.3.2). SAP note 2426277 provides as well important information about the migration
process.
You need to establish your Employee Self Service process in SSP before you can use your migrated purchase
requisitions again. Please refer to the configuration guide and release note 2214564.

6 © 2016 SAP SE or an SAP affiliate company. All rights reserved.
2 Getting started
SAP provides a new functionality and application within SAP S/4 HANA which takes over the functionality of the
known SAP SRM solution. Customers using SAP SRM and SAP ERP solutions might be able to migrate their
shopping carts from SAP SRM to SAP S/4 Hana SSP, depending on their deployment scenario.
Caution
SAP provides a solution to migrate your existing shopping carts documents created in SAP SRM. Only the
documents itself will be migrated, Migration does not apply to the configuration as well to your custom
code. SAP S/4 HANA SSP is a new product and must be configured separately. SAP recommends to
finish your SAP S/4 HANA SSP configuration before finalizing the migration.
2.1 Design of the migration logic
The migration approach is divided into three different phases:
1. Preparation and installation: Before you can start with the migration you must have installed several new
objects and prepared your system for migration. Please refer to chapter 3 detailed instructions.
2. Migration Report: The main logic for SC migration is included in SAP SRM report
BBP_SC_MIGRATE_TO_PR. It will migrate SAP SRM shopping carts into purchase requisitions. You will have
to migrate all shopping carts before SAP SRM is finally disconnected. The report is repeatable and can be
executed several times. Depending on your deployment scenario the execution times differ.
3. Post Processing: Post Processing is executed once the system conversion to SAP S/4 HANA is completed. It
is carried out by SAP S/4 HANA report MMPUR_MIG_EBAN. After Post Processing the purchase requisition
will be available in SAP S/4 HANA SSP processes.
2.2 Supported deployment scenarios
The initial situation is the following. You are using SAP SRM 700 or higher in combination with SAP ERP 600 or
higher any you want to convert your SAP ERP system to SAP S/4 HANA (1511 OP SP02 or higher). Depending on
you deployment scenario there might be a need to migrate your shopping carts or it might be an optional step.
Caution
Migration in this guide refers to Employee Self Service Procurement Scenario only. Other scenarios within
SAP SRM are not supported.
CUSTOMER
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 7
2.2.1 Overview
The following table gives you an on overview about the migration possibilities per SRM deployment scenario:
Deployment Option Classic Extended Classic
Multiple SAP ERP Backend Migration optional (restrictions Migration optional (restrictions
apply) apply)
Single ERP Backend Migration optional Migration optional (restrictions

apply)
One Client Migration mandatory -
2.2.2 One Client Deployment SRM@ERP
One client scenario refers to a co deployed installation of SAP SRM and SAP ERP on the same machine. SAP S/4
does not support this scenario.
Note
SRM_SERVER and S4Core software components cannot be installed together on the same machine in
SAP S/4 HANA.
Therefore while converting SAP ERP with co deployed SAP SRM there is a need to remove the SRM_SERVER
software component. This can be done during the conversion process. For detailed information about the
deinstallation and conversion process please refer to:
 SAP Note 2426277 - Add. info. on converting to SAP S/4HANA using SUM 2.0 SP00
Uninstalling SRM_SERVER will lead to the complete loose of the SAP SRM functionality. SAP S/4 HANA
functionalities as a successor must be configured from scratch. Since SAP SRM objects are completely deleted
this would also result in a complete loose of all business documents created with SAP SRM. Therefore it is
mandatory to deal with the migration of these documents. Before you start the SAP S/4 Hana Conversion for an
ERP with installed SRM_SERVER it is mandatory to choose one of the following migration scenarios for your SC
documents:
 No migration of shopping carts: The migration report will not be executed. Suitable if the SRM_SERVER is
installed on your SAP ERP system, but not used anymore.
Caution
This option will lead to the loose of all existing shopping carts documents in the system!

 Migrate before system conversion: The migration report will be executed before your start your system
conversion. This will speed up the conversion process. However you must complete all your SC before you
start the conversion process. Once this is done SRM should not be used anymore. This will lead into a process
downtime for Self Service procurement processes.
 Migrate during system conversion: The migration report will be executed while the conversion process is
carried out and is a part of the upgrade process. You are able to continue using the full functionality of
SRM_SERVER until the downtime phase of the conversion process starts. However since all shopping carts
are migrated during the system downtime this will increase the downtime significantly.
 Mixed approach: The migration report is executed two or several times. The first execution is carried out
before the conversion starts. It will contain the bulk of all ordered SC with an existing follow on document in
the SAP ERP system. During system conversion all other open shopping carts are migrated. This will combine
a decent performance with the advantage of using SRM_SERVER until the downtime starts. SAP recommends
this approach.
You can select the migration scenario by executing report BBP_MIGRATE_SCEN (see chapter 4.3).
2.2.3 Deployment on separate machine in Classic and

Extended Classic Scenario
SAP S/4 HANA is a valid backend for SAP SRM and after the system conversion of SAP ERP to SAP S/4 HANA
you can continue using SAP SRM if it is deployed on a different machine than SAP S/4 HANA. You can also
choose to replace the SAP SRM SSP functionality with the SAP S/4 HANA SPP functionality and migrate you
shopping carts to SAP S/4 HANA. This is an optional step.
SC migration is supported for both, the classic and extended classic scenario. Restrictions apply for the handling
of purchase orders in classic scenario (see chapter 2.3).The SC migration is decoupled from the conversion of
SAP ERP to SAP S/4 HANA. You can migrate your shopping carts after the conversion to SAP S/4 HANA is
performed.
SAP recommends to perform the SC migration in a Two Step approach:
1. First customize and introduce SAP S/4 HANA SSP and migrate all your completed shopping carts. Start
using SAP S/4 HANA for all your new purchase requisitions.
2. While new requests are handled with SAP S/4 HANA SSP, complete all your remaining documents in SAP
SRM and migrate them before finally discontinuing SAP SRM
CUSTOMER
2.3 Which documents are migrated and how will they look
like after migration
The main document of SAP SRM is the shopping cart. It is a dedicated document for a requestor for a purchase
request which may come up. After approving the shopping cart, usually a follow on document is created in the
SAP ERP system. This might be a purchase requisition or a purchase order. In SAP SRM classic scenario the
purchase order is created directly in SAP ERP while in SAP SRM extended classic scenario it is created in SAP
SRM itself and a copy is transferred to the backend.
Note
The business document "Shopping Cart" is not existing in SAP S/4 HANA. Self Service Procurement in
SAP S/4 HANA is built "On Top" of the purchase requisition.
The known purchase requisition document from SAP ERP is used as a base. SAP S/4 HANA Self Service
Procurement is built On Top of that process and provides an easy FIORI application for the management of
purchase requisitions. Typical SSP features like catalog integration, workflow technologies etc. are included into
that app. As a result of the process a purchase requisition is created out of that application.
There is no differentiation between classic or extended classic scenario in SAP S/4 HANA. All customers will
migrate to the same process in SAP S/4 HANA SSP.
Figure 1: Migration path from SAP SRM classic scenario to SAP S/4 HANA SSP

For SAP SRM classic scenario that means every shopping cart for which not already a purchase requisition is
existing as a follow-on document will be migrated into a purchase requisition. Besides the shopping cart there is
no need to migrate any other documents since the further follow on documents (purchase order, confirmation
and invoice) are already existing in the backend system. Confirmation and invoice documents which were
created in SRM but not yet transferred to the backend are not handled by the migration reports. It is
recommended to finish these transactions before starting the migration.
The migration approach is the same for SAP SRM Extended Classic Scenario. All shopping cart documents can be
migrated to purchase requisitions.
Figure 2: Migration path from SAP SRM Extended Classic Scenario to SAP S/4 HANA
Unlike in classic scenario purchase orders may be created directly in SAP SRM. However a copy is always created
in SAP ERP. Therefore there is no need to migrate the purchase order data, only shopping carts are considered.
Caution
Purchase orders or purchase order updates which are not transferred to SAP ERP before migration will
get lost. It is recommended to complete all open processes before migration.
When a purchase order is transferred from SAP SRM to SAP ERP, you cannot edit the PO in SAP ERP anymore. It
is locked and changes are only possible in SAP SRM. During the migration this PO lock is removed. Purchase
orders which originated from SAP SRM will be changeable in SAP S/4 HANA after the migration.
The migration is split into two parts and for each part there is a dedicated migration report:
CUSTOMER
 BBP_SC_MIGRATE_TO_PR is part of the SRM_SERVER software component. It is executed before or during
the removal of SAP SRM. It can be executed multiple times and will migrate all selected shopping carts into
backend purchase requisitions. If SAP SRM is deployed in the One Client scenario it is mandatory to perform
this step before the system conversion of SAP ERP to SAP S/4 HANA, If SAP SRM is deployed in any other
scenario it can be carried out before or after the conversion. Purchase requisitions migrated with
BBP_SC_MIGRATE_TO_PR are in a transition status (EBAN-ESTKZ ‘1-6’). That means they are not useable in
any backend processes until the second migration part is performed.
 MMPUR_MIG_EBAN is the second migration report and part of S4CORE. It must be executed after the
conversion of SAP ERP to SAP S/4 HANA. After execution the first migration report, purchase requisitions will
be in a transition status. MMPUR_MIG_EBAN will release the PR documents from the transition status and
make them available for all processes again. After executing the report migrated purchase requisitions will
appear in the My Purchase Requisitions application. This second migration report shall only be executed once
your customizing of SAP S/4 HANA SSP is completed.
For a detailed description about the setup of the two report please refer to chapter 5 and 6.
2.3.1 Shopping Carts
As stated in chapter 2.1 all SAP SRM shopping carts can be migrated. The document to which they will be
migrated in SAP S/4 HANA is the purchase requisition. Every purchase requisition which originated from a SAP
SRM shopping cart be accessed via the standard transactions or the SAP S/4 HANA FIORI application My
Purchase Requisitions.
Shopping carts and purchase requisitions are similar but not the same documents, so the newly created purchase
requisition will not look exactly the same like the original shopping cart. In general the same transfer logic applies
as if the shopping carts would be transferred to a SAP ERP purchase requisition in a normal process.
The shopping cart migration is based on the header status of the shopping cart. For every status different actions
must be performed.
 Status Saved: A Shopping cart might have the status saved when it is not yet released. So a saved SC is
basically a draft which may not be completed yet. It can contain faulty data and the check may return error
messages which require further actions from the author. Being a draft actually implicates the logical
equivalent in SAP S/4 HANA. It is the draft instance. It will be listed in the application and the requestor can
continue working on it after the migration. The purchase requisition will be created as a purchase requisition
on hold. (EBAN-MEMORYTYPE = ‘H’)
 Status In Approval: A shopping cart in approval means, that it was released by the customer and there is now
a workflow running to approve the cart. This workflow is not yet completed. There is an existing workitem
which is currently processed by an approver. Workflow concepts between SAP SRM and SAP S /4 HANA
differ, therefore it is impossible to map the workflow status correctly between SAP SRM and SAP S/4 HANA.
The workflow from SAP SRM will not be continued. Once the shopping cart is migrated into a purchase

requisition, its workflow will restart according to the customizing of the release strategy in SAP S/4 HANA.
Former workflow information can be preserved in an attachment to the purchase requisition. (see chapter
2.2.4.2) If an error is encountered while the purchase requisition is created it will be rolled back and
treated like a draft PR on hold.
 Status Ordered: The SC is released and a follow on document was created for every item. The follow on
document might differ per item. So it is necessary to loop over the items and decide for each item how to
handle it:
o Purchase Requisition is existing as follow on document: In this case no new document is created in the
backend since there is already a document existing. The existing purchase requisition is moved into
transition status, custom fields are migrated (see chapter 2.2.4.2) and the approval information from
SAP SRM might be added (see chapter 2.2.4.1)
o Purchase Order is existing as a follow on document: To preserve the complete history about the order
process there is the need to migrate the SC as a purchase requisition. The purchase requisition will
replace the Shopping Cart as a predecessor document to the purchase order. Since we migrate “historic
data”, the purchase requisition will be created without data validation. At the time the SC was released
and the purchase order was created it passed all checks and was in a valid status. All error message which
could usually occur in the creation process will be ignored and the PR created in any case. The PR
creation is only a conversion of data. No follow on processes (Release strategy, commitment, statistical
processes etc.) will be triggered out of that PR. The connection of the purchase requisition to the PO will
be updated. The newly created purchase requisition will be visible in the document flow of the purchase
order. The migrated purchase requisition will be visible in the app My Purchase Requisitions after the
conversion.
o Reservation is existing as a follow on document: Within the standard SAP ERP process one cannot create
a reservation out of a purchase requisition, this is something special and specific to the SAP SRM and its
Self Service Procurement Process. SAP S/4 HANA does not feature the creation of reservation in SSP
yet. Shopping carts with a reservation as follow on document will be migrated to achieve the migration of
all data, but it is a dead end. There will be no relation to the reservation and the purchase requisition will
be closed and not available for further processing. The reservation itself will not be touched.
o Item is rejected or deleted: By user selection it is also possible to migrate SC items which were deleted
or rejected from the shopping cart. After migration the corresponding indicators of the purchase
requisitions are set (LOEKZ and BANPR)
 Status Error in Transmission: A shopping cart might have the status „Error in Transmission”. This status is
usually assigned when the transfer to the backend fails for whatever reason. It might happen during the initial
transfer or a delta update. Shopping carts with Error in Transmission status will be ignored during migration
as it cannot be assured that a valid purchase requisition will be created for that documents. You will have to
resolve all errors before migration.
 Status Release Rejected / Deleted: To achieve a compliant migration with all relevant data you can also
migrate shopping carts which were rejected or deleted and never released. Workflow information will be
preserved for that shopping carts (see chapter 2.2.4.2). The indicators for the migrated purchase requisitions
(LOEKZ and BANPR) are set accordingly. Purchase requisitions will be visible in the app, however it is not
possible to change them anymore.
It is possible to filter by the different shopping cart status and migrate only the documents you want.
CUSTOMER
2.3.2 Purchase Orders
As stated in chapter 2.3 within the SSP process a PO document is always created in the SAP ERP system. Either
directly (classic scenario) or as a copy (Extended Classic Scenario). Therefore there is no need to migrate
purchase orders.
If a purchase order is existing as a follow on document to a SAP SRM shopping cart, the document flow and
linkage of the purchase order will be updated once the shopping cart is migrated. The migrated purchase
requisition will be the predecessor document to the PO.
If SAP SRM is deployed in Extended Classic scenario, the purchase order lock will be removed to make purchase
orders changeable in SAP S/4 HANA once SAP SRM is disconnected.
Also in Extended Classic scenario the PO in SAP SRM and SAP ERP might differ. A purchase order might not be
transferred to the backend system yet or it might already be transferred but there is a change / update existing in
SAP SRM which is not transferred yet. This delta is not fetched by the migration reports. Any PO information
which was not transferred to SAP ERP by the time the migration is executed will be lost.
SAP recommends to complete all open purchase orders before starting the migration.
2.3.3 Other documents and SAP SRM processes
Besides Self Service Procurement and shopping carts SAP SRM features various other procurement processes
like contract management, sourcing with RFX, external requirement, SUS etc.
Caution
There is no migration path to SAP S/4 HANA existing yet for this documents. Besides shopping carts no
other documents are considered for migration and handled by the reports. Data related to this
documents will be lost after migration.
Some of the mentioned processes might create or update shopping carts or purchase orders. The migration of
such purchase orders or shopping carts is handled as described in chapter 2.3.1 and 2.3.2 SAP recommends to
complete all processes before starting the migration.
2.3.4 Special issues during SC migration
When a shopping cart is migrated into a purchase requisition there are some parts which cannot be migrated “1:1”
However the migration report offers a solution for the following topics.

2.3.4.1 Custom fields
The migration report provides the possibility to rescue the data of all custom fields which were created via the
standard SAP SRM extension framework.
Data from custom fields which are existing in both, SAP SRM and SAP ERP and are mapped via the standard
enhancement structure and will be filled as if the shopping cart would be transferred without migration.
The logic for custom fields which are only existing in SAP SRM is different. SAP S/4 HANA is a complete new
product, and if you wish to continue using your custom fields from SAP SRM you will have to create the customs
fields newly in SAP S/4 HANA SSP. A direct takeover of the data is therefore not possible. However the data of
customer field created via the standard framework (existing include to tables BBP_PDHSC and BBP_PDISC) will be
preserved in a dedicated table in SAP S/4 HANA.
After migration you will find the data of your custom fields in table MIG_SC_CUST_FLDS. The table features the
following columns:
 SC Number / Item Number: Number of the former SC or item to which the custom field relates to
 Field Level: Indicates if the custom field was a header, item, table like header or a table like item field
 Field Name: Technical name of the former custom field
 Field Value: Value of the former custom field, converted into CHAR255 format
 PR / PR Item Number: Number and item of the migrated purchase requisition
These information is stored for compliance reasons and to give you a whole overview about the former SC data. It
is not visible or accessible via the FIORI application.
SAP provides a BADI to enhance or reduce the number of custom fields which are handled during migration (see
chapter 7)
2.3.4.2 Approval Workflow
Workflow concepts in SAP SRM and SAP S/4 HANA differ. As stated in chapter 2.3.1 no workflow itself will be
migrated. Every shopping cart workflow which is active when the migration starts will be aborted. After
migration the workflow will restart for the purchase requisition based on the SAP S/4 HANA SSP customizing.
However to achieve compliance and a complete overview of the shopping cart data SAP provides the option to
preserve all “historic” workflow / approval information during SC migration. These data will be read during
migration and attached to the purchase requisition as a PDF file. The file will contain the complete approval
history.
The attachment is based on a smartform. SAP provides a BADI to change the smartform during migration if
additional information is needed.
CUSTOMER
The creation of the document is optional and has a significant impact on the performance.
2.3.4.3 Attachments
Standard logic for attachment transfer applies. Please refer to

http://help.sap.com/saphelp_srm70/helpdata/de/49/b32640632cea01e10000000a155106/content.htm for
more information.
2.3.4.4 Archiving
Archived documents are not considered by the migration reports.
2.3.4.5 Requestor of the purchase requisition in SAP S/4

HANA
Before migrated purchase requisitions will be visible in the application it is necessary to complete the
organizational setup in SAP S/4 HANA SSP. An employee ID must existing for every requestor (please refer to
chapter 6)
By standard the requestor in SAP S/4 HANA will also be the former requestor from the SAP SRM shopping cart.
The User Id from SAP SRM is taken over with the migration. Within One Client scenario it is ensured that the ID is
also existing in the backend, in other scenarios you might need to develop your own logic to determine the
requestor for the new purchase requisition. A BADI for that purpose is provided (see chapter 7).
2.4 Documents and SAP notes for the migration
2.4.1 Required documents and notes
You require at least the following documents and SAP notes:
Document Available At Comment
Migration of SAP SRM shopping

carts during/ after system
conversion to SAP S/4 HANA

Report to set migration scenario SAP Note 2249984 (for all SRM Only relevant for "One Client"
settings releases) scenario
SAP SRM migration Pre check SAP Note 2216943 (for all SRM Only relevant for "One Client"
class releases and S/4 HANA target scenario
releases below 1709 OP) or
2478308 (for all SRM releases
and S/4 HANA target release 1709
OP and higher)
SAP SRM Plug In Class for deletion SAP Note 2317386 Only relevant for One Client
Scenario
Uninstallation of software SAP Note 2348177 Only relevant for One Client
component SRM_SERVER during Scenario
the SRM one client conversion to
S4HANA 1511 SR1
Report to generate SAP SRM DDIC SAP Note 2290018 (only for SRM
objects 7.13 SP11 stack)
SAP Note 2250115 (for all other

releases)
SAP SRM Migration coding SAP Note 2233514 (only for SRM
7.13 SP11 stack)
SAP Note 2341850 (only for SRM
7.13 SP12 stack)
SAP Note 2468792 (only for SRM
7.13 SP13 stack)

SRM releases)
Report to generate SAP ERP DDIC SAP Note 2291147 (only for ERP
objects 6.17 SP11 stack)

ERP releases)
SAP ERP migration coding SAP Note 2233517 (only for ERP
6.17 SP11 stack)
SAP Note 2341826 (only for ERP
6.17 SP12 stack)

ERP releases)
CUSTOMER
2.4.2 Additional documents and SAP Notes
The following table lists important additional documents and SAP notes:
S4TC Delivery of SAP S/4 HANA SAP Note 21827195

System Conversion Check
S/4HANA SSP Configuration SAP Note 2214564

Cookbook
Conversion Guide for SAP S/4 service.sap.com/sltoolset 

HANA, on-premise edition Software Logistic Toolset 1.0 
Section “Documentation” 
System Maintenance
Additional information on SAP Note 2426277

converting to S/4HANA using
SUM 2.0 SP00
S/4 HANA Cookbook: Transition http://scn.sap.com/docs/DOC-

Options 64980
The System Conversion to SAP http://scn.sap.com/docs/DOC-

S/4HANA, on-premise edition 68976
1511 - Technical procedure and
semantic adaption tasks

3 Installation
The following section provides you with a step by step description of how to install the migration reports to your
system.
Note
The delivery is carried out only via SAP Notes. Make sure you have always the latest version installed.
New objects are required to be installed in both systems, SAP SRM as well as the backend system (SAP ERP or
SAP S/4 HANA) For each software component dedicated notes were built (please refer to the table in chapter
2.4.1)
3.1 System Requirements
3.1.1 One Client Scenario
If your SAP SRM system is deployed in One Client scenario the following minimum system requirements for you
software components apply:
 SRM_SERVER >= 700

 SAP_APPL >= 604
The migration is not supported for any SRM_SERVER releases <700. In this case you need to upgrade to SAP
SRM 7.0 first.
3.1.2 SAP SRM deployed on a separate machine, Conversion

to SAP S/4 not yet performed
If your SAP SRM system is deployed on a separate system and you want to perform the SC migration together
with a system conversion of your SAP ERP system to SAP S/4 HANA the following minimum system
requirements for you software components apply:

 SAP_APPL >= 600
CUSTOMER
Also you need to convert your SAP ERP version to S4CORE >= 100 SP 2. Otherwise you won`t be able to execute
the second part of the migration.
3.1.3 SAP SRM deployed on a separate machine, Conversion

to SAP S/4 not yet performed
If your SAP SRM system is deployed on a separate system and you want to perform the SC migration sometime
after the system conversion to SAP S/4 HANA the following minimum system requirements for your software
component apply:

 S4CORE >= 100 SP2
The migration requires at least SP 2 for the S4CORE component.
3.2 Installation of new objects in SRM_SERVER
The first part of the migration logic is executed in SAP SRM. Please follow the following instructions to install the
necessary objects in SRM_SERVER.
Note
Even if you only want to delete SRM_SERVER during the transformation to SAP S/4 HANA without
migration of shopping carts (conversion option "No Migration at all" see chapter 4.2.1) you still need to
install the following migration reports in the SRM_SERVER component. Installation of the PFCG role is
needed as well. Installation of the smartform can be skipped.
3.2.1 Instructions valid for all deployment scenarios
1. Go to TA SNOTE and download and apply SAP Note 2250115 or 2290018 (appropriate to your release, see
chapter 2.4.1)
2. Go to TA SE38 and execute report RBBP_DDIC_OBJECTS_NOTE_2252346 or report
RBBP_DDIC_OBJECTS_NOTE_2233514 (appropriate to SRM release stack, see chapter 2.4.1)
3. In the following screen select Update And Activate
4. Confirm the popup Activate DDIC with Online
5. Go back, select Step 3 Generate maintenance dialog

6. Go to TA SNOTE and download and apply SAP Note 2252346 or 2233514 or 2341850 or
2468792 (appropriate to your release, see chapter 2.4.1) Steps 1 – 5 must be performed successfully
before applying the note!
7. Repeat steps 2-4
8. Download the file “BBP_SC_HANA_MIG_ROLE.zip” from SAP note 2252346 to your local hard disc and unzip
it
9. Go to TA PFCG. Go to the menu Bar  Role  Upload and execute upload of the unzipped role
“bbp_sc_hana_mig_role.sap”
10. Generate the authorization profile of the role and save it
11. Download the file “BBP_SC_MIG_APPR_DATA.zip” from SAP note 2252346 to your local hard disc and unzip
it
12. Go to TA SMARTFORMS. Go to the Menu Bar Utilities  Upload form and execute upload of the unzipped
form “bbp_sc_mig_appr_data.xml”
13. Save and activate the created smartform. In the coming pop-up assign the smartform to the package
BBP_XPRA.
3.2.2 Additional instructions if SAP SRM is deployed in One

Client Scenario
If your SRM system is deployed in One Client Scenario please follow the following instructions in addition to the
steps mentioned in chapter 3.2.1
1. Go to TA SNOTE and download and apply SAP Note 2249984 (to install the report
BBP_SC_S4MIG_SET_SCENARIO "Set options for migration of SRM Shopping Carts to S4HANA")
2. Install the pre-check class for SRM_SERVER (SAP Note 2216943 for all SRM releases and S/4 HANA target
releases below 1709 OP or 2478308 for all SRM releases and S/4 HANA target release 1709 OP and higher).
For more information about the concept of pre-check classes please refer to SAP Note 2182725.
3.2.3 Installation of new objects in SAP_APPL / S4CORE
Note
If you only want to delete SRM_SERVER during the transformation to SAP S/4 HANA, but don't want to
migrate any shopping carts (conversion option "No Migration at all" see chapter 4.2.1), you do not need to
install the migration reports in SAP_APPL component. In this case you can skip the following steps.
CUSTOMER
The second part of the migration logic is performed in SAP_APPL or S4CORE (depending if the migration is
executed before or after the system conversion to SAP S/4 HANA). Please follow the following instructions to
install the necessary objects:
1. Go to TA SNOTE and download and apply SAP Note 2250113 or 2291147 (appropriate to your release, see
chapter 2.4.1)
2. Go to TA SE38 and execute report RBBP_DDIC_OBJECTS_NOTE_2252240 or report
RBBP_DDIC_OBJECTS_NOTE_2233517 appropriate to your release stack
3. In the following screen select Update And Activate
4. Confirm the popup Activate DDIC with Online
5. Go back, select Step 3 Generate maintenance dialog
6. Go to TA SNOTE and download and apply SAP Note 2252240 or 2233517 or 2341826 (appropriate to your
release, see chapter 2.4.1. Steps 1 – 5 must be performed successfully before applying the note!
7. Repeat steps 2-4
8. Download the file “SAP_SC_HANA_MIG_ROLE.zip” from SAP note 2252240 to your local hard disc and unzip
it
9. Go to TA PFCG. Go to the menu Bar  Role  Upload and execute upload of the unzipped role
“sap_sc_hana_mig_role.sap”
10. Generate the authorization profile of the role and save it
If you use SRM as a procurement hub in a multi backend environment you need to perform these steps in every
backend system.
3.2.4 Updating the objects
Make sure you have always the latest version of the notes mentioned above applied. If a new version of a note is
released and you need to update the objects please proceed as per the following:
1. Uninstall the note from your system

2. Install the note again

4 Preparing the system for SC migration
Caution
Before preparing your system make sure the installation as explained in chapter 3 is completed.
4.1 General settings
4.1.1 Important information
Before you start the migration process there are few things to consider:
 The conception of your SAP S/4 HANA SSP process should be known. Besides the SC documents no other
process data will be migrated. You should have a concept about adopting custom logic, fields etc.
 It is recommended that you take care of all faulty shopping carts. Shopping carts with the status Error in
Transmission will not be migrated (see chapter 2.3.1)
 If you would like the workflow attachments to be generated, attachment transfer must be configured, please
refer to
http://help.sap.com/saphelp_srm70/helpdata/de/49/b32640632cea01e10000000a155106/content.htm
4.1.2 Authorizations
To avoid accidental or unwanted execution the migration report, its logic is secured with special authorization
objects. Execution of the migration logic requires the authorization object S_MIG in SRM_SERVER. (Activity
Execute)
SAP provides two reference roles which include all further required authorization objects to execute the reports.
Please perform the following steps:
CUSTOMER
1. In SAP SRM assign the role BBP_SC_HANA_MIG_ROLE to all users who should be able to perform the SC
migration
2. When the migration is carried out a RFC call from SAP SRM into SAP ERP is made. This requires a RFC
connection between SAP SRM and your backend systems. The migration logic uses the standard RFC
connection maintained in BBP_BACKEND_DEST (TA SPRO  Supplier Relationship Management
SRM_SERVER  Technical Basic Settings  Define System Landscape). Find out the RFC connection and
the user which is used to access the backend. Assign the role to this user
4.2 Settings for downtime migration in One Client Scenario
The following settings are only necessary if the report should be executed in one client scenario during the system
conversion downtime.
Also in One Client scenario you can migrate your shopping carts before the system conversion starts. In this case
you do not need to perform the downtime specific settings. However these purchase requisitions are not editable
until the system conversion is finally completed.
If an SAP ERP system with installed SRM_SERVER component is being converted, the SRM_SERVER
component will automatically be removed during the conversion process. So it is mandatory to deal with the
migration.
SC Migration during system conversion downtime allows you to use your SAP SRM system until the last second
before the conversion starts. However, we strongly recommend to migrate the bulk of shopping cart data (SC with
an existing follow-on document) before the system conversion. The remaining and open shopping carts will then
be migrated during system conversion.
4.2.1 Setting up migration scenario
As mentioned the SAP SRM system will be automatically deleted during the system conversion. During the
system conversion and before the deletion of SAP SRM the migration report will automatically be called. You can
influence the behavior during that call by setting up your migration scenario.
Go to TA SE38 and execute report BBP_SC_S4MIG_SET_SCENARIO. You will have the following options:
1. Migration during downtime: Choose this option if you want to continue using SAP SRM until deletion. If
selected, all shopping carts which have not been migrated so far will be migrated during downtime. It is
recommended to keep this number low and migrate the bulk of shopping cart already before downtime
execution. A high amount of shopping carts will lead to a longer runtime and therefore a longer system
downtime.

2. Migration during uptime only: Choose this option if you have already migrated all you documents before the
system conversion. The migration of shopping carts will not be executed during downtime. However certain
pre checks and warnings are issued to assure the migration is completed.
3. No migration at all: Choose this option if you do not want to migrate your documents. Migration will not be
called during downtime, no warnings and errors are issued from the pre check class. This option is feasible for
customers who have installed SAP SRM but do not use it. Only the deletion of SAP SRM will be carried out in
this case.
By default always the scenario 1 – Migration during downtime is considered. To select the migration scenario you
need to implement SAP note 2249984.
4.2.2 Pre Check Class
When SAP ERP is converted to SAP S/4 HANA and SRM_SERVER is installed a pre check class is needed as for
any other application component. Please refer to SAP Note 21827195 to get more information about the concept
of pre check classes. The Pre Check class for SAP SRM is delivered via Note 2216943 (for all SRM releases and
S/4 HANA target releases below 1709 OP) or 2478308 (for all SRM releases and S/4 HANA target release 1709
OP and higher). Make sure you have always the latest version applied.
The Pre Check class for SRM_SERVER has the task to ensure that the system is completely prepared and all
necessary setup is completed before the downtime migration starts. There are two scenarios where the checks
can be called:
 Manual execution before the system conversion to get an overview about the settings which still must be
done.
 Automatic execution during system conversion to SAP S/4 HANA. The Pre Checks are executed several time
during the system conversion to SAP S/4 HANA. If an error is encounter the conversion might be stopped or
aborted.
The pre Checks for SAP SRM can deliver several errors which will stop the conversion and lead to a customer
action:
 SRM_EBP-DDIC_USER: This error is issued if the DDIC user is not created in every productive client. Please
refer to chapter 4.2.3
 SRM_EBP-DDIC_AUTH: This error is issued if the DDIC user does not have sufficient rights. Please refer to
chapter 4.2.3
 SRM_EBP-RFC_CON: If the RFC connection to SAP ERP is faulty, this error will be issued. Please refer to
chapter 4.2.4
CUSTOMER
 SRM_EBP-OBJ_CHECK: This error is issued if not all migration objects are installed. Please refer to chapter 3
for an instruction of how to install the reports
Besides the error which will cause the migration to stop SAP SRM Pre Checks will also deliver warnings with useful
information about topics you should consider for migration:
 SRM_EBP-INVALID_DOC: This warning will be issued if you are using documents or processes which do not
have a migration path. These documents will be deleted. Please refer to chapter 2.3
 SRM_EBP-CUST_FIELDS: This warning will be issued if you are using custom fields in SAP SRM. You should
note the hints in chapter 2.3.4.1
 SRM_EBP-BADI: This information will be issued if you are currently using BADIS within you SAP SRM
implementation. SAP S/4 HANA SSP is a complete new application and all BADI implementation in SAP SRM
will be removed during migration. You should consider adjusting your custom logic for SAP S/4 HANA.
4.2.3 Plug-In Class for Deletion
During the deletion process several generated objects must be identified and be provided to the framework. This
is carried out by a so called plug-in class. You must implement SAP note 2317386 to install the plug-in class to
your system.
4.2.4 DDIC User
During system conversion downtime the DDIC user will be the only user which is not locked. System conversion
and the migration report are starting in client 000. To fetch the data from all clients calls into every client are
made. The logon into every productive client is carried out with the DDIC user. A DDIC user must be existing in
every productive client. If this is not the case please perform the following steps for every productive client in
which you are using SAP SRM functionality:
Caution
Do NOT apply any changes to the DDIC user in clients 000 and 001 as this can seriously harm your upgrade
process. Only create or change DDIC users in clients > 001.
1. Go to TA SU01 enter “DDIC” and create a new user

2. Go to the Tab “Logon Data”. As a user type enter “Service”
3. As a user group enter “SUPER”
4. Choose a password

5. We recommend to restrict the validity of the user to the time your upgrade process is taken place. You can
also delete the user again once the upgrade is completed.
6. Go to the Tab Roles and assign roles “BBP_SC_HANA_MIG_ROLE” and “SAP_SC_HANA_MIG_ROLE” These
roles contain all the authorizations necessary to execute the migration report.
7. Save the user.
If the DDIC user is already existing in a productive client, please make sure it has roles
BBP_SC_HANA_MIG_ROLE and SAP_SC_HANA_MIG_ROLE assigned.
4.2.5 RFC Connections
Before the migration starts you need to replace your RFC connections which you are using for your current SAP
SRM processes with a dedicated RFC connection using DDIC user.
For every productive client please perform the following steps:
1. Go to TA SM59. Create a new RFC destination to the same machine and client you are logged on. Use the
DDIC user as the user for Log On.
2. Go to TA SPRO  Supplier Relationship Management  SRM_SERVER  Technical Basic Settings  Define

System Landscape. For every entry with System Type “ERP_*” and “EBP_ONE” enter the newly created RFC
connection in the field “RFC Destination”
We recommend to remove the RFC connections once the migration is completed as they are no longer
needed then.
CUSTOMER
5 Executing the migration reports
Every shopping cart which will be migrated to a purchase requisition will be in a transition status and not be
available for any further processing until the post processing (see chapter 6) is completed.
5.1 Standalone Execution
The standalone execution can be executed by every user with sufficient authorization (see chapter 4.1.2 ). Go to
TA SE38 and execute report BBP_SC_MIGRATE_TO_PR. Several options are offered:
Object Selection in SAP SRM

The first parameters are dealing with the selection of which shopping cart should be migrated. You can filter by
the following selection criteria:
 Shopping Cart Number

 From / To Date  This refers to the creation date of the shopping cart
 Number of days  All shopping carts created within the last x days
Execution Options
You have the possibility to run the report with the following options:
 Use Parallel Processing: Usually shopping carts are migrated sequentially. Parallel Processing can help to
improve the runtime. Migration tasks are send to available work processes in parallel.
 Send Approval Data as PDF file: If this checkbox is selected the approval and workflow history of the shopping
cart will be read out and attached to the document. (see chapter 2.3.4.2) Caution: Selecting this option will
increase the runtime of the report
 Take PR Number from SRM: Decides whether the system tries to use the SRM number or a number from an
internal number range in the backend to create the PR
 Run in Test Mode

Time phase of migration
 Migrate Ordered Shopping Carts: Every ordered shopping cart with an existing follow on document will be
migrated. This is a suitable option if you want to migrate the first bulk of shopping carts. Shopping carts which
are not ordered yet will stay in SRM and can be processed further
 Migrate All Shopping Carts: Every shopping cart which have not been migrated so far will be migrated. This
option should be selected for the last migration call to fetch all remaining data. Also open documents will be
migrated and can be processed in SAP S/4 HANA after the post processing is carried out
Client
The migration report is client independent and migration can be carried out for all clients at once. It is also
possible to restrict the migration to the client from which the report will be executed.
Status
Further restriction of the shopping carts to be migrated is possible by selecting the status of the shopping carts
which should be migrated. For example if you do not want to migrate rejected shopping carts, you can simply
deselect them
Note
Migrated shopping carts are logged in table BBP_SC_MIG_HIST. Once a shopping carts is migrated, it
cannot be migrated again.
5.2 Execution during system conversion downtime
BBP_SC_MIGRATE_TO_PR will be automatically called by SUM tool during the downtime phase in the system
conversion process. There is a dedicated phase. For more information about the general conversion process
please refer to the Conversion Guide for SAP S/4 HANA. (see chapter 2.4.2)
We strongly recommend that you have already migrated the bulk with all ordered shopping carts when the
downtime migration starts. To ensure the execution of the report without failure please make sure you have
performed all the necessary settings described in chapter 4.2.
In the downtime phase the report will be called with the following parameter:
 All shopping carts are migrated. No restriction to number range / creation date
 Parallel Processing is not activated
 Approval data will be taken into account
CUSTOMER
 By default all SC statuses are relevant. Every SC which was not migrated so far will be migrated.
 Migration start in client 000 and will be executed for all clients
You have the possibility to adjust the shopping cart selection according to your needs via several Badis (please
refer to chapter 7).
After migration you can find the logfile in directory DIR_TRANS.

6 Post Processing
After all shopping carts are migrated and the system conversion is completed you need to perform post
processing steps in order to work with the purchase requisitions again.
Note
Post Processing is executed in your SAP S4 HANA System. As a prerequisite you should have completed
your SAP S4HANA SSP configuration, especially in terms of the organizational structure.
Steps performed during post processing

During post processing the following changes will be applied to the purchase requisitions:
 The transition lock will be removed. Migrated purchase requisitions will be fully available in all purchasing
processes again
 The purchase requisition will be assigned to the requestor. This is determined by the user id of the requestor
of the former SAP SRM shopping cart. In One Client Scenario the User ID will be the same. If SAP SRM was
deployed on separate machine you may need to implement a BADI (see chapter 7)
Please perform the following steps to execute post processing:
1. Go to TA SE38 and open report MMPUR_MIG_EBAN
2. You have the possibility to restrict the purchasing requisitions which should be processed by the number and
the creation indicator. The creation indicator refers to the status of the former shopping cart.
3. Execute the report with your selection. After that step purchase requisitions are useable and visible in the
FIORI application. The migration is competed.
Note
You can find a post processed purchase requisitions, including their processing date in table
MIG_SC_S4H_HIST.
After postprocessing the migrated PR can be accessed via the app My Purchase Requisitions. A status for the
purchase requisition will appear on the UI. Based on the former status of the SC it will be displayed like mentioned
in the table below.
CUSTOMER
ESTKZ after migration Former SC Status New Status In S/4 Requesition Processing
phase 1 HANA UI State (BANPR)
1 Saved Saved 2  Active
2 Awaiting Approval Awaiting Approval 3  In release
3,4,5 Accepted, Follow On Approved 5 Release completed

Document created
6 Rejected Rejected 8  Release refused
7 Deleted Deleted 8

7 BADI interfaces
SAP provides two BADI interfaces which allow you to adjust the migration logic according to your own needs.
7.1 BBP_BD_SC_MIG_TO_HANA
This BADI interface can be implemented in SAP SRM. During the execution of the migration logic there are several
methods to be called:
 ADD_REMOVE_SC_MIG: This method allows you to change the selection list and therefore to decide which
shopping carts should be migrated during the run. Based on the list which is filled by the selection criteria you
can add or remove documents.
 CHANGE_SMARTFORM: You can replace the smartform which is used to generate the approval data with your
own smartform. This allows you to adjust the information which should be displayed.
 MODIFY_SC_DATA: Before the purchase requisition is created you can adjust the data of shopping carts if
needed. This method provides you with the instance of the shopping cart and allows you to change it.
 CHANGE_SC_CUST_FIELDS: Custom fields are migrated and their values are written into a dedicated table
(see chapter 2.3.4.1) This method allows you to change the list of custom fields which should be migrated.
You can as well add standard fields to the list which are existing in SRM but usually would not be transferred
to the purchase requisition (e.g. industry, localization fields)
7.2 BBP_BD_MIG_REQ_AUTH
This BADI interface is implemented in SAP S/4 HANA. It contains a method to determine the author and
requestor of the new purchase requisition.
 GET_REQUESTOR_CREATOR: You can implement your own logic to fill the EBAN fields SC_AUTHOR and
SC_REQUESTOR here.
CUSTOMER
CUSTOMER
www.sap.com/contactsap
© 2016 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.
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 http://www.
sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.

SC Mig Guide v3

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

SC Mig Guide v3

Uploaded by

Copyright:

Available Formats

Configuration Guide CUSTOMER

Document Version: 1.3 – 2018-02-07

Migration of SAP SRM Shopping Carts

Type Style Description

Example Emphasized words or expressions.

EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .

CUSTOMER Migration of SAP SRM Shopping Carts

Version Date Change

1.0 2016-03-07 Initial Creation

1.1 2016-09-01 Update

1.2 2017-11-30 Update

1.3 2018-02-07 Update

Migration of SAP SRM Shopping Carts CUSTOMER

2 Getting started .............................................................................................................................. 7

4 Preparing the system for SC migration ................................................................................... 23

5 Executing the migration reports ................................................................................................. 28

CUSTOMER Migration of SAP SRM Shopping Carts

6 Post Processing ........................................................................................................................... 31

7 BADI interfaces ............................................................................................................................ 33

Migration of SAP SRM Shopping Carts CUSTOMER

What is this document about?

What other documents do you need?

CUSTOMER Migration of SAP SRM Shopping Carts

2.1 Design of the migration logic

The migration approach is divided into three different phases:

2.2 Supported deployment scenarios

Deployment Option Classic Extended Classic

Single ERP Backend Migration optional Migration optional (restrictions

One Client Migration mandatory -

2.2.2 One Client Deployment SRM@ERP

CUSTOMER Migration of SAP SRM Shopping Carts

2.2.3 Deployment on separate machine in Classic and

SAP recommends to perform the SC migration in a Two Step approach:

CUSTOMER Migration of SAP SRM Shopping Carts

2.3.1 Shopping Carts

CUSTOMER Migration of SAP SRM Shopping Carts

2.3.3 Other documents and SAP SRM processes

2.3.4 Special issues during SC migration

CUSTOMER Migration of SAP SRM Shopping Carts

2.3.4.2 Approval Workflow

Standard logic for attachment transfer applies. Please refer to

Archived documents are not considered by the migration reports.

2.3.4.5 Requestor of the purchase requisition in SAP S/4

2.4 Documents and SAP notes for the migration

2.4.1 Required documents and notes

You require at least the following documents and SAP notes:

Document Available At Comment

Migration of SAP SRM shopping

CUSTOMER Migration of SAP SRM Shopping Carts

SAP Note 2250115 (for all other

SAP Note 2252346 (for all other

SAP Note 2250113 (for all other

SAP Note 2252240 (for all other

2.4.2 Additional documents and SAP Notes

Document Available At Comment

S4TC Delivery of SAP S/4 HANA SAP Note 21827195

S/4HANA SSP Configuration SAP Note 2214564

Conversion Guide for SAP S/4 service.sap.com/sltoolset 

Additional information on SAP Note 2426277

S/4 HANA Cookbook: Transition http://scn.sap.com/docs/DOC-

The System Conversion to SAP http://scn.sap.com/docs/DOC-

CUSTOMER Migration of SAP SRM Shopping Carts

3.1 System Requirements