Scribd
Upload
114 views1 page

Custom Code MIgration Steps

The document provides execution steps for custom code related to a Simplification migration to SAP S/4HANA: 1. Process custom development objects related to functionality not available in S/4HANA - remove custom code or consider standard functionality, and create new enhancements if needed. 2. Process objects where functionality has changed - adapt custom code based on migration worklist and code inspector checks. 3. Ensure the newest version of SUM is used, execute transactions SPAU and SPDD, reset candidates with no differences, extend data models and adjust other DDic objects.

Uploaded by

gvrahul
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
114 views1 page

Custom Code MIgration Steps

The document provides execution steps for custom code related to a Simplification migration to SAP S/4HANA: 1. Process custom development objects related to functionality not available in S/4HANA - remove custom code or consider standard functionality, and create new enhancements if needed. 2. Process objects where functionality has changed - adapt custom code based on migration worklist and code inspector checks. 3. Ensure the newest version of SUM is used, execute transactions SPAU and SPDD, reset candidates with no differences, extend data models and adjust other DDic objects.

Uploaded by

gvrahul
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

Custom Code related execution steps:

? Process customer development objects related to Simplification items with


functionality not available
in Sap S/4HANA. Remove the related custom code � consider equivalent standard
functionality � if
required create new enhancements (us recommended extensibility functionality).
? Process customer development objects related to Simplification items where the
functionality has
been changed. Adapt your custom-code based on the information from custom code
migration
worklist and code inspector checks.
? Ensure that you start your system conversion with the newest available version of
SUM
? Execute transaction SPAU
? Execute transaction SPDD
1. Reset all candidates which have no difference between last modified version and
delivered SAP version
(consider log entries
in /usr/sap/SUM/<systemID>/SUM/abap/log/SPDD_RESET_CANDIDATES.<systemID>, which has
been
generated by SUM; see documentation https://websmp203.sapag.
de/~sapidb/011000358700000890302012E > Automatic Reset of Non-Adjusted Repository
Objects to
SAP Original Version)
2. Extend the S/4 core data model by own custom fields, appends (e.g. in SD appends
have to be moved
from old db tables to new db table) as mentioned by pre-checks or related
Simplification DB
3. Adjust all other DDic objects in SPDD
? Find and migrate dynamic usages in your custom code by using Runtime Check
Monitor and Blacklist
Monitor in your Q- and Productive System
Recommendation: Each step above could be parallelized to assign the different tasks
to different
processors. To avoid unnecessary adaptations, the migration for functionality not
available in SAP
S/4HANA should be completed before adaptations take place.

You might also like