Browse The Book: First-Hand Knowledge

First-hand knowledge.
Browse the Book

This sample chapter illustrates the modification adjustment process. It
first discusses the transactions that make up modification adjustment,
and then focuses on Transaction SPDD, which is the most important and
critical of the modification adjustment transactions when it comes to
upgrades. It also briefly covers Transactions SPAU and SPAU_ENH.
“Modification Adjustment”
Contents
Index
The Authors
Mark Mergaerts, Bert Vanstechelman

SAP S/4HANA System Conversion Guide
537 Pages, 2020, $89.95
ISBN 978-1-4932-1944-5
www.sap-press.com/5035
Chapter 6
Modification Adjustment
The release upgrade imports thousands of objects into the SAP system.
It’s possible, and indeed likely, that developers have changed some
of these objects in the local system to adapt them to the company’s
6
business needs. If these changes are to be kept in the new SAP release,
then they must be combined with the changes SAP itself has made to
the objects in the new version. This is where modification adjustment
comes in, the subject of this chapter.
Modification adjustment is the process of reconciling changes made by SAP to stan-

dard ABAP repository objects (as a result of a release upgrade, Support Package
update, or SAP Note correction) with customer changes to those same objects.
361
6 Modification Adjustment 6.2 Preparing and Running Transaction SPDD
Modification adjustment applies both to Data Dictionary objects (tables, structures, SPAU_ENH on the other. Because Transaction SPDD has to be performed during the
data elements, and domains) and development objects (such as programs, function upgrade, the person who will do so will often be you, providing you have at least an
groups, screens, and menus). Because an upgrade changes SAP objects on a massive adequate knowledge of the Data Dictionary. If you aren’t comfortable with the Data
scale, modification adjustment is critical to ensuring the preservation of data and Dictionary, then you should delegate the task to someone who is.
functionality.
In this chapter, we’ll illustrate the modification adjustment process. We’ll first dis- Note
cuss the transactions that make up modification adjustment, and then focus on Our distinction between Data Dictionary and development objects isn’t entirely
6
Transaction SPDD, which is the more important and critical of the modification accurate. In fact, Transaction SPAU also deals with certain types of Data Dictionary
adjustment transactions when it comes to upgrades. We’ll also briefly cover Transac- objects—namely, those that don’t store data. Examples are views, type groups, table
tions SPAU and SPAU_ENH at the end of this chapter. types, search helps, and lock objects. In addition, Data Dictionary objects are also
development objects: creating a new table can hardly be called anything but devel-
opment. Nonetheless, these terms are in fairly common usage, so we’ll stick to them.
6.1 Modification Adjustment Transactions
After reading these paragraphs, it may seem to you that Transaction SPDD is a real
For technical reasons, modification adjustment is divided into two parts. Each part
challenge and that compared to it, Transaction SPAU is a treat. Not quite: there is one
has its own transaction to carry out the adjustment:
thing that is definitely advantageous about Transaction SPDD. In terms of the num-
1. Modifications of dictionary objects are performed with Transaction SPDD.
ber of objects to adjust, the workload in Transaction SPDD is almost always far
2. Modifications of development objects are performed with Transactions SPAU and smaller than that of Transaction SPAU. Transaction SPDD typically involves fewer
SPAU_ENH. Transaction SPAU deals with customer changes to workbench objects than 100 objects, many of which only require routine handling. Transaction SPAU, on
like programs, screens, or object classes, whereas Transaction SPAU_ENH is used the other hand, can range from just a few to many thousands of objects (the highest
for enhancements. tally we have seen to date is around 7,500). Fortunately (for you, that is), carrying out
This distinction is not a consequence of a developer’s whim or a design flaw. There is Transactions SPAU and SPAU_ENH isn’t a burden that will normally fall on your
an essential difference in the way the two types of objects are handled. Data Dictio- shoulders. In most cases, these adjustments are a task for the developers and, rather
nary objects must be activated during the upgrade because structure changes may than everything being done by one individual, they can distribute the work among
lead to physical conversion in the database, and the upgrade relies on all database themselves. Nevertheless, it’s essential for an upgrade or conversion specialist to
objects having the expected structure. This has two important implications: know about Transactions SPAU and SPAU_ENH, which is why we’ll be spending some
1. The modification adjustment of Data Dictionary objects must happen before the time on them in the last section of this chapter.
activation and thus relatively early in the upgrade process.
2. Omitting the modification adjustment, or doing it wrong, can cause a loss of data.
6.2 Preparing and Running Transaction SPDD
Development objects are less dangerous in this respect. They aren’t used in the
upgrade, so their adjustment can wait until afterwards. They don’t store business Modification adjustment of Data Dictionary objects is performed when the ABAP
data, so mistakes or omissions can cause dysfunctions (like generation errors, short upgrade process stops at the beginning of the activation phase and instructs you to
dumps, or missing functionality) but not irretrievable data loss. run Transaction SPDD. This happens during the Preprocessing roadmap step, which
means that the SAP system is still running productively in the old release. Because
If you are the person performing the technical upgrade, then there’s another import-
modification adjustment is by definition something you do in the target release, you
ant difference between Transaction SPDD on the one hand and Transactions SPAU/
always execute Transaction SPDD in the shadow instance.
362 363
We’ll start this section with an overview of the information and instructions Software transport is available or that you chose not to use one, something SUM prompted
Update Manager (SUM) is giving you, and then move on to Transaction SPDD itself. you about in an earlier phase.
The first steps are logging on to the shadow instance, creating a user in client 000, If you do use an adjustment transport, then most objects will be adjusted automat-
and opening the system and client for repository changes. ically when the upgrade process imports this transport into the system. The num-
ber of objects that still need adjustments is then likely to be very low (or ideally,
zero). Objects still to be adjusted manually either didn’t exist in the source system
6.2.1 Repository Modification
where the adjustment transport was created, or they were modified in a different
The SUM window that you have currently in front of you is the one shown in Figure way in the current system compared with the source system. 6
6.1.
This screenshot comes from a sandbox system, which was the very first in the
company’s landscape to be converted to SAP S/4HANA. This explains why no
adjustment transport exists yet.
2 It’s possible that some modifications were made based on advance corrections
provided by SAP. The new release most probably includes this modification, which
means that the new version of the object that comes in with the upgrade is identi-
cal to the modified version currently in the system. In this case, as we’ll explain
later, you will use the Reset to Original option in Transaction SPDD. Instead of
doing this manually, you can also have the system do it for you by running the
special program RSUPG_SPDD_RESET_CANDIDATES in the shadow instance.
This function is relatively new and, to be honest, we’ve never used it and are
unlikely to do so. It’s always better to have very precise knowledge of the adjust-
ment process for each object and to document this properly. Therefore, running
the complete Transaction SPDD manually at least once is still our preferred way of
working.
3 The message about objects that will be passively deleted won’t always appear.
What it means is this: The SAP standard contains tens of thousands of dictionary
objects, and most of these are long-lived and remain part of the standard from one
Figure 6.1 SUM Stops for Modification Adjustment release to the next. However, some standard objects become obsolete, and SAP
may then decide to leave them out of a new release. During the upgrade, these
There is quite a bit of useful information on this screen, so let’s take a close look at it: obsolete objects are deleted and, where applicable, a replacement object is created.
1 The first sentence informs you of the number of objects that were changed locally This normally goes unnoticed, but if such a condemned object was modified in the
and will therefore appear in Transaction SPDD. In this case, there are 121. That may local system, then a kind of dilemma occurs: Transaction SPDD can’t show the
seem like a substantial number, but often many of these objects will simply need object for adjustment because a new standard version doesn’t exist, but on the
resetting to the original (i.e., SAP standard) version. We discuss the distinction other hand, the object having been modified means that the replacement object in
between an actual modification and a return to the original later in this chapter. the new release is unsuitable.
Here you also learn that 0 objects are automatically maintained by import of an In that case, silently deleting it could lead to potential data loss or corruption. To
adjustment transport. The count of zero simply means that no adjustment avoid such a problem, SUM alerts you to the fact that some now-obsolete objects
364 365
have been modified and creates an upgrade log listing the affected objects. It’s 6.2.3 Creating a User for the Modification Adjustment
essential that you take this up with the system administration and development
Start Transaction SU01 and create a new user ID, preferably as a copy of DDIC or SAP*.
teams. If they decide the objects are still needed, then they should create a copy of Note that even if you already have your own user in client 000 of the main system,
the object in the customer (Y–Z) name range and replace any references to the that user doesn’t exist in the shadow instance and you must create it again there.
obsolete SAP object with a reference to the customer object.
Log off as DDIC and log on with the user you have just created. The upgrade process
4 Skipping Transaction SPDD isn’t an option! If you do this, then all modified objects has unlocked the shadow instance automatically, so logging on as an ordinary user is
will be replaced with the new SAP-standard versions, probably with disastrous now possible. 6
consequences and with the only solution a full reset of the upgrade. A word of cau-
tion is therefore not out of place.
5 These are the steps in the Transaction SPDD process. We describe them in detail in 6.2.4 Enable Development Changes
the following paragraphs. For Transaction SPDD to work, both the system and client 000 must be open for
6 If you accidentally enable this checkbox and let the upgrade continue before workbench changes. Proceed as follows:
Transaction SPDD is completely finished, then point 4 applies and it’s start again 1. Call Transaction SE06 and click System Change Option.
from scratch time. To avoid catastrophic mistakes, it might therefore be better to
2. Change the Global Setting at the top of the screen to Modifiable.
close the browser session in which SUM is running and restart it later when modi-
3. Click Save.
fication adjustment is done.
Note
6.2.2 Logging on to the Shadow Instance
If the current setting is already Modifiable, then we still advise you to click Save any-
There are two ways to open an SAP GUI session in the shadow instance: way. We’ve witnessed situations in the past in which for some reason the setting
쐍 Create a new entry in your SAP Logon menu with the correct system and server wasn’t properly registered and Transaction SPDD thought the system was still in a
name and the instance number of the shadow instance. nonmodifiable state.
쐍 The upgrade process also creates an RFC destination in the primary instance of the
system (see Figure 6.2). This destination, with the name SAP_UPGRADE_SHAD- 4. Next, call Transaction SCC4 (Client Maintenance), select client 000, and choose
OW_SYSTEM, points to the shadow instance. Open the destination in Transaction Change. Confirm the message that the table is cross-client.
SM59 and use Remote Logon. Then log on as user DDIC in client 000. 5. Go to the Cross-Client Object Changes field, and set it to one of the following val-
ues:
– Changes Allowed to Repository and Cross-Client Customizing
– No Changes to Cross-Client Customizing Objects
6. Click Save.
6.2.5 Log on to the Primary System

During modification adjustment with Transaction SPDD, you will probably need to
compare Data Dictionary objects in the shadow instance with their current versions
in the main system. It’s therefore a good idea to also log on to the primary system in
Figure 6.2 RFC Destination for Shadow Instance
parallel with the session you have open in the shadow instance.
366 367
You can expand the top section by dragging down the separator line. This will display
Avoiding Confusion between Sessions the complete program documentation.
A possible problem here is that it isn’t easy to visually distinguish the two sessions, In this example, you’re getting a free pass: no objects at risk of data loss were found.
leading to the risk of inadvertently making changes in the wrong place. A useful tip:
You may leave the program and start Transaction SPDD. If objects do appear here,
in the main system, log on to a client other than 000—for instance, the default client
then you must adjust them. The instructions in the program documentation aren’t
configured for the system. Because the SAP GUI window clearly shows the client
really sufficient to guide you in this; we recommend referring to the text of SAP Note
number, that makes it easy to see where you are. Also, to look at Data Dictionary
2535651, which is more helpful.
objects in the main system, use Transaction SE12 (which is display-only) rather than 6
Transaction SE11 (which allows object maintenance).
6.2.7 Run Transaction SPDD
Now, it’s finally time to run Transaction SPDD itself. Figure 6.4 shows the initial
6.2.6 Checking for Possible Data Loss
screen of the transaction.
Although Transaction SPDD is intended to safeguard modifications to tables and
Here, you can narrow your search to just a subset of Data Dictionary objects. With
structures and thus to prevent data loss, there is one situation in which such loss
Transaction SPDD, however, you normally accept the default selections and click Exe-
could occur without Transaction SPDD being aware of it. This case is described in SAP
cute.
Note 2535651 and applies both to conversions to SAP S/4HANA and to normal release
upgrades—for example, from one Enhancement Package level to a higher one. In
Chapter 4, we mentioned that you have to apply SAP Note 2535651 with Transaction
SNOTE, but we didn’t go into the details of why this SAP Note is necessary.
The potential problem arises if SAP Notes were applied in the system that introduced
new database tables or made structural changes to existing tables (e.g., adding new
fields). If these SAP Notes are part of the target release and Support Package, then there
is no risk of losing data. However, if the SAP Note isn’t part of the new release and Sup-
port Package, then it’s possible that these changes won’t be kept. If the modified object
is a database table or a structure included in the definition of a database table in the
Data Dictionary, not reapplying the modification is likely to cause a data loss.
Before you start Transaction SPDD, call Transaction SE38 and run report RESCUE_
OBJECTS_WITH_DATALOSS. You’ll see a screen like the one shown in Figure 6.3.
Figure 6.4 Transaction SPDD Selection Screen
The first time you run Transaction SPDD, the system will ask you to create a protocol
(log) of the modification adjustments, as shown in Figure 6.5. This protocol holds a
record of all actions in Transaction SPDD (and later Transaction SPAU). If a protocol
from a previous upgrade exists, then it’s possible to use it (the system warns you if
the protocol appears outdated, as you can see in the screenshot), but it’s better to
start a new one for each release upgrade or Support Package update.
Figure 6.3 Report RESCUE_OBJECTS_WITH_DATALOSS
368 369
6 Modification Adjustment 6.3 Transaction SPDD Object List
Transaction SPDD runs because you didn’t formally reset it to original. At the end of
Transaction SPDD, every single object must have been treated!
Looking at the top of the list, you’ll notice that the screen has three tabs: With Assis-
Figure 6.5 Transaction SPDD Protocol Request tant, Without Assistant, and Deletions. The labels of the tabs also show the number of
objects in each group, as you can see in Figure 6.6.
Enter a meaningful title for the protocol and press (Enter). The system now displays
6
the list of modified Data Dictionary objects.
6.3 Transaction SPDD Object List

Figure 6.6 Object List Tabs
Before we dive into the details of the object list, it’s perhaps best to answer a very
basic question: What are you supposed to do here? In essence, Transaction SPDD will
The assistant mentioned in the labels is the Modification Assistant. This is a standard
present a list of SAP-standard objects that were modified locally at some point in the
tool of the ABAP Workbench, which supports developers when making modifications
past. A good example is adding one or more customer fields to a standard table with
to SAP-standard objects and also helps them when they have to reapply modifica-
transaction data to cover some specific business need. For each object, you’ll have to
tions during an upgrade.
decide between two courses of action:
For objects listed in the With Assistant section, the Modification Assistant can reapply
쐍 Adjust
the modification in the new version of the object. This can either be done fully auto-
This means reapplying the modification in the new version. Remember that the
matically (in which case the object is shown with a green traffic light) or partly auto-
upgrade has overwritten the modified version of the SAP object with a new
matically, with some manual actions necessary (the object then has a red traffic light).
unmodified one, so to keep a modification you must reapply it to this new version.
쐍 Reset to original For objects in the Without Modification Assistant section, the Modification Assistant
It’s possible that you don’t want to keep the old modification, perhaps because its is unable to determine unambiguously how the objects need to be adjusted, and a
function is no longer relevant. The modification might also have been incorpo- manual action is therefore necessary. In Transaction SPDD, this is the most critical
rated into the new SAP release, in which case the new standard object and the old group of objects: here you will need to decide upon an action (although, as we will see,
modified one are actually identical. Resetting an object to its original state means Transaction SPDD will in most cases create a proposal, which you can simply accept).
that you accept the new standard version of that object and all changes made to it Unadjusted objects in this section have a yellow traffic light icon.
in the past are discarded. Furthermore, resetting to original sets a flag in the ver- The Deletions list contains SAP objects that were locally changed at some time in the
sion management for that object, indicating that all past custom modifications to past but which no longer exist in the new release. In most cases, such objects are
the object are no longer relevant. The object will then no longer appear in Transac- unproblematic. Exceptions occur when a deleted object is referenced in another cus-
tion SPDD for future upgrades. tomer modification. A typical example of this is customer (Z) tables or structures con-
taining fields that have a standard SAP data type. If that data type no longer exists in
the new release, then the Z table becomes invalid.
Warning
There’s obviously a third possibility, which is to do nothing. In practice, that will get We already mentioned that for every object in the list, Transaction SPDD shows a sta-
you the worst of both worlds: you’ll lose the custom change to the object, and even if tus icon, usually a traffic light. Other icons are possible as well. To give you a good
the new version is identical to the old one, the object will keep appearing in future understanding of how to interpret them, we describe them here in some more detail:
370 371
6 Modification Adjustment 6.5 Adjusting Objects
쐍 Green checkmark that it contains Transaction SPDD modifications; also mention the version (e.g.,
If a modification has a green checkmark as its status, then the modification has “SPDD: Conversion S/4HANA 1909”). You’ll also be prompted for a change request
been successfully applied. No further action is needed (or possible). the first time you reset an object to SAP standard.
쐍 Green traffic light
For modifications shown with a green traffic light, you only have to decide Important
whether to let the system reapply the modification or to reset the object to the SAP It’s very important that all Transaction SPDD actions are registered in just one
original. You choose the action from the menu on the right, which we’ll look at in change request. If several people (e.g., a team of developers) are working on the
6
a moment. Transaction SPDD list, make sure they create a single change request, and let all
쐍 Yellow traffic light developers create tasks and repairs under that request.
For objects with a yellow traffic light, you also have to decide whether to adjust The last action in Transaction SPDD will be to register this transport request for use
them or reset them to original. The difference is that here the Modification Assis- in later upgrades.
tant can’t help you. To reapply a custom change, you must adjust the object man-
ually (although in some cases the system will present a proposal). You’ll therefore
have to compare the new standard version with the custom modification. If you
decide that the modification must remain, apply it manually yourself. The remain-
6.5 Adjusting Objects
der of this chapter is devoted mainly to describing how to deal with the most com- You should now have sufficient background knowledge to get started with the real
mon types of modifications. work, which is to look at each object and adjust it or reset it to the original. Objects in
쐍 Red traffic light the Data Dictionary can have many different attributes, so there are many ways to
In the With Modification Assistant section, a red light means that automatic modify them. We can’t possibly discuss all of these, but long years of using Transac-
adjustment by the Modification Assistant is only able to apply part of the adjust- tion SPDD have given us a good idea of the types of modifications you’re most likely
ment; some additional manual action is necessary. to encounter. We’ll begin by showing you the general procedure flow to follow for
쐍 Dark traffic light (no color) each object, then we’ll cover these modifications in more detail:
This status normally appears only for the Note Corrections category. If you see a 쐍 Data elements and domains
dark traffic light in front of an SAP Note, then the associated correction instruc-
쐍 Customer fields added to SAP tables and structures
tions are obsolete because the correction is contained in the upgrade or in the
쐍 Changes in field format (like data type or length) in SAP tables in structures
imported Support Package.
쐍 Technical settings of tables
쐍 Trash can
This status icon appears only in the Deletions section and means that the object Finally, we’ll walk you through processing deleted objects.
has been, well, deleted.
6.5.1 General Procedure

6.4 Transaction SPDD Transport Request You start by selecting an object in the list. You’ll then see a new pane open on the
right-hand side of the screen. Figure 6.7 shows an example for a data element.
All decisions about objects, either to adjust or reset to the original, are recorded in a
This pane is subdivided into three parts. At the top, you see details about the object,
transport request. The first time you keep a modification, you’ll be prompted to open
such as its dictionary type, description, and application component. This section also
a new change request. Enter a meaningful description for this request so that it’s clear
shows when the object was changed and by whom and in which transport request the
372 373
change was recorded. For several items (object name, transport request, and version 6.5.2 Data Elements and Domains
history), there is a Display icon on the far right, which lets you display the detailed
In the Available Actions section in Figure 6.7, you see three actions:
information directly from Transaction SPDD instead of having to start a separate ses-
1. Compare Versions (new original vs. last modification)
sion.
2. Reset
The second part of the pane lists all the actions that are available for this object. The
contents of this list may differ depending on the type and modification status of the 3. Adjust
object; we’ll discuss the most common actions later in this chapter. To actually per- The logical first step is to find out in what way the object was changed, and you do 6
form the action, double-click its Execute icon. Simply clicking the activity name that by looking at the version history. Therefore, click the Execute icon next to Com-
shows information about it in the bottom part of the pane. pare Versions. As the full name of the action indicates, this brings up a comparison
Let’s now do some real work with the objects in the list. We’ll begin with the object in between the last change—that is, the object as it was before the upgrade replaced it
Figure 6.7, a data element: data elements, along with domains, will almost always with a new version—and the new standard.
appear in the Transaction SPDD list, and in most cases handling them is relatively For data elements and domains, version management compares numerous attri-
straightforward. butes, which can make the screen look a little cluttered. It’s best to choose Delta Dis-
play, which only shows the attributes that are different between the two versions.
With this data element, BIC_SEL_SOURCE, you’re lucky. The delta display (Figure 6.8)
shows that the new standard doesn’t differ from the old modified one. This probably
means that the change has become part of the standard. The correct decision there-
fore is to accept the new standard—in other words, reset to original. In the action list,
click Execute next to the Reset action. Because this is the first object you are process-
ing, you’re asked to open a new change request.
Figure 6.8 Object without Differences
In the main list, you now see the object as shown in Figure 6.9. Note that the status
column shows an icon we didn’t mention before when we described the various sta-
Figure 6.7 Object Information Pane
tus icons.
374 375
Here, the text associated with several fixed values of the domain has changed. The
color pattern helps you to distinguish between the old, modified version (darker
background) and the new standard version (lighter background). Looking at the texts,
it’s clear that this is a case in which you want to preserve the modification: SAP sup-
plies this domain with a series of generic texts, and the customer chose to replace the
Figure 6.9 Object Status after Reset text for values 900000010 to 9000000012 with something more meaningful for
their business (900000013 also differs, but here both texts are generic).
This status means that the object has been reset to original. The reason why we didn’t 6
To process the object, click Execute next to the Adjust action. This opens the mainte-
talk about it is that reset objects disappear from the list as soon as you click Refresh
nance screen for the domain (which you can also reach via Transaction SE11). Open
or when you leave and restart Transaction SPDD. In (very) old releases, an object that
the Value Range tab and replace the three generic texts with the customer’s own, as
was reset to original didn’t disappear from the Transaction SPDD list, and it was even
shown in Figure 6.11.
possible to reverse the Reset status so that you could edit the object again. Unfortu-
nately, these possibilities no longer exist. You must use version management for the
object in question if you want to make any changes after having reset the object to
original in Transaction SPDD or SPAU. To find out which objects were reset, you can
use the Transaction SPDD protocol or Transaction SE95_UTIL (Modification Browser
Utilities). For the next object we’ll examine, a domain, there’s a little more work to do,
as shown in Figure 6.10.
Figure 6.11 Adjustment in Data Dictionary
Save the change (which prompts you for a change request, with the open Transaction
SPDD request as default choice). There’s no need to activate; this will be handled by
the upgrade later.
Press the Back key to return to Transaction SPDD. The status icon of the object has
changed to a green checkmark, showing that the adjustment is finished (Figure 6.12).
Figure 6.12 Object Status after Adjustment
Figure 6.10 Domain Needing Adjustment
376 377
6.5.3 Customer Fields in SAP Tables and Structures By convention, append structures take the name of their parent object, plus the ZA
prefix. Note that this is an object in the customer namespace.
We’ll now move on to a slightly more complex case. It’s possible to extend standard
database tables and structures with extra customer-specific fields. Because the new
SAPTAB
SAP version may itself introduce new fields, these two changes must be merged. Con-
sider the schema shown in Figure 6.13. MANDT MANDT
SAPFLD1 SAPFLD1
ZASAPTAB
SAPTAB SAPTAB SAPTAB SAPTAB SAPFLD2 SAPFLD2 6
SAP ERP 6.0 SAP ERP 6.0 SAP S/4HANA SAP S/4HANA CUSTFLD1
SAP standard Modification SAP standard Modification SAPFLD3 SAPFLD3
CUSTFLD2
CUSTFLD1 SAPFLD4
MANDT MANDT MANDT MANDT
CUSTFLD2 SAPFLD5
SAPFLD1 SAPFLD1 SAPFLD1 SAPFLD1
Append
ZASAPTAB
CUSTFLD1 SAPFLD4 CUSTFLD1

Figure 6.14 Append Structure
CUSTFLD2 SAPFLD5 CUSTFLD2

Let’s look at a real example in Transaction SPDD. Our object list contains an SAP
SAPFLD4 structure, KOMKBZ4. For tables and structures, the list of possible actions will offer two
SAPFLD5 different adjustment modes:
쐍 Adjust with Proposal
Figure 6.13 Structure with Custom Fields and New Standard Fields 쐍 Adjust Manually
Executing Adjust with Proposal brings up the screen shown in Figure 6.15.
In SAP ERP 6.0, SAP delivered the table with the MANDT and SAPFLD1–3 fields. Based on
specific business requirements, the customer added two fields, CUSTFLD1 and CUST-
FLD2. The new standard delivered with SAP S/4HANA contains two extra fields, SAP-
FLD4 and SAPFLD5. However, the customer decides that the added fields remain
relevant and must be preserved. This means that you must end up with a table struc-
ture that contains both the SAP fields and the locally added fields (far right).
The Data Dictionary handles this kind of scenario by placing the customer fields in a
separate object called an append structure. The Data Dictionary definition of the SAP
table contains only the standard fields, but it also contains a reference to the append
structure, which stores the customer fields. When analyzing the Data Dictionary
objects in preparation for Transaction SPDD, the modification adjustment process
notices the conflict between the old modification and the new standard. It then cre-
Figure 6.15 Proposal for Append Structure
ates a proposal, which places the customer fields in a new append structure, as shown
schematically in Figure 6.14.
378 379
Here the customer added the TDLNR field to the standard layout. When you choose This phase deals with format changes for individual fields, which we’ll look at shortly.
Accept Proposal, a pop-up opens showing the name of the generated append struc- In our example, no format changes were detected, so no further adjustment action is
ture (Figure 6.16). needed. Click Back to return to the object list.
What if there are no differences between the old modified version and the new stan-
dard one? You’ll often encounter this situation—for example, if the customer fields
were added as an advance correction that is now part of the SAP standard. In that
case, the adjustment screen informs you that the proposal already corresponds to the
6
current version (Figure 6.19).
Figure 6.16 Name of Append Structure
Confirm this with (Enter). Because this is a new object, you’ll have to assign it to a
customer (Z) package (Figure 6.17).
Figure 6.19 Proposal Corresponds to New Version
There’s no need to choose Accept Proposal here. Simply click Back; Transaction SPDD
informs you that the table will be reset to original, which you only have to confirm.
6.5.4 Field Format Changes

Another type of modification occurs when you change the attributes of a standard
field by assigning a different data type (which may or may not cause the field length
or other physical characteristics to change). This situation is handled in phase 2 of the
adjustment for tables and structures.
Figure 6.17 Register Append Structure in Customer Package
The Transaction SPDD proposal lists the fields for which the data type was changed.
Click Save. The screen now changes, showing information for a Phase 2 (Figure 6.18). For example, look at the screenshot shown in Figure 6.20. Here, a table or structure
contains a VBTYP field, the data type (data element) of which was VBTYP in the old mod-
ified version and becomes VBTYPL in the new standard. An important element is that
the length of the field also changes, from one character to four. If you kept the modi-
fication, then the upgrade would reduce the defined length of that field in the data-
base from four positions down to one. Needless to say, this is very dangerous: any
value longer than one character would be truncated, resulting in corrupt data.
The display has three columns: Old Version shows the previous (modified) version,
Current Version is the new SAP standard, and Proposal is the field format proposed by
Transaction SPDD. Values shown with a red background are those that differ from the
current proposal. In this case, the proposal is for the new, longer data type. If this is
Figure 6.18 Adjustment Phase 2
380 381
indeed what you want (and you have precious little choice here), then you may sim-
ply return to the main object list by clicking Back and reset the object to original.
Figure 6.21 Technical Settings
Changing the technical settings can never lead to data loss or table conversions, but
Figure 6.20 Format of Field Changes that doesn’t mean it’s entirely risk-free. For example, disabling logging when it’s
enabled by default in the SAP standard might upset auditors. Changes to the table
If for some reason you do decide (or, more precisely, the customer decides) that the buffering mode (also part of the technical settings but not shown in this example)
old data type and field length must be kept, then proceed as follows: can cause performance problems. And tinkering with the SAP HANA storage type
1. Double-click in the header of the Old Version column. The old version will then (which is the setting affected in our example) is highly unwise unless SAP tells you to.
become the proposal (and the values in New Version will be displayed with a red This is a case that has reset to original written all over it—which is precisely what we
background). did in this upgrade.
2. Choose Accept Proposal to confirm your decision.

6.5.6 Processing Deleted Objects
6.5.5 Technical Settings Having worked through the adjustments in both the With Modification Assistant and
Without Modification Assistant lists, let’s turn our attention to the Deletions section.
The technical settings of a table determine where and how that table is stored in the
As we explained earlier in this chapter, here you find a list of SAP objects that were
database; they also control certain forms of special treatment for the table inside the
modified locally but no longer exist in the new SAP standard. The fact that they were
SAP application layer, such as logging and buffering. The delta display is comparable
modified at all is of course a strong indication that there was an actual functional
to the one we saw for data elements and domains, where the darker background is for
need for them and that their disappearance might therefore be problematic.
the older version and the lighter background for the new.
Figure 6.22 shows (part of) the deletion list for the upgrade. The status icon is a trash
Figure 6.21 shows an example. In Transaction SPDD, we executed the Compare Ver-
can (a definite improvement over old versions of Transaction SPDD, in which it was a
sions (New Orig. vs. Last Mod.) action and switched to Delta Display in the version
red light, sometimes causing great alarm).
management.
It isn’t a rarity for the deletions list to be quite long, longer even than the two modifi-
Here the new standard enables logging for the table and specifies that in SAP HANA,
cation lists. This is mostly because your predecessors who carried out previous
the table must reside in the Column Store. If the new settings are acceptable, then
upgrades (or was that you?) never bothered to clean up the list. Earlier we said that
execute the Reset action in Transaction SPDD. Otherwise, execute Adjust and make
doing nothing for an object in Transaction SPDD is not an option: you either have to
the necessary changes.
adjust or to reset to original. This isn’t true for deletions. You could just ignore this
382 383
6 Modification Adjustment 6.6 Final Steps
list, which means objects will simply accumulate here (we have even recently seen 6.6 Final Steps
lists with deletions dating back to the last century).
Once you’ve worked through the all the object lists in Transaction SPDD, there are
two things left to do. First, you have the option to register your transport for later use.
Then, you log off from the shadow instance and start the activation phase of the
upgrade.
6
6.6.1 Registering the Transaction SPDD Transport for Later Use
You can use the transport request in which all the Transaction SPDD changes were
collected for the modification adjustment in later upgrades to the same target ver-
sion. The upgrade process will then automatically apply the modifications that are
the same as those in the source system in which the Transaction SPDD request was
created. If the upgrade finds any differences, then you will have to run Transaction
Figure 6.22 List of Deleted Objects
SPDD to handle them.
In the majority of cases, the action you will execute here is Delete Modification Log. If you decide to use this transport technique, then perform the following steps:
This means that you acknowledge that the once-modified object no longer exists— 1. When you’re finished with the adjustments, go to the Transport Organizer (Trans-
that you have no further use for it and don’t want to be reminded again that it once action SE09) and list your open requests. The change request that you opened for
existed. Transaction SPDD will be listed. Click to open this request and show the tasks and/
Another action available to you here is Retrieve Last Version. Although the object has or repairs, then release all the tasks and repairs. You can’t release the change
been deleted, the version database still contains a trace of it. If it’s really (and we request itself because that isn’t allowed at this point in the upgrade; the system
mean really really) necessary to keep the object, then Retrieve Last Version will resur- will refuse to do so. SUM itself will release the transport later on.
rect it. However, having seen plenty of zombie and vampire movies, we think that 2. Leave Transaction SE09 and return to the Transaction SPDD object list. Click the
bringing an object back from the grave isn’t a good idea. First, it’s misleading because Select for Transport button on the far right of the Transaction SPDD toolbar. A
it creates the impression that the object is part of the SAP standard, whereas in reality search window opens. Locate and select the open Transaction SPDD request.
it’s a relict. Second, future upgrades will delete it again, forcing your successor (or 3. Transaction SPDD asks you for which SL Toolset tool you want to flag this modifi-
yourself) to redo the investigation and possibly to decide again to keep it in its cation adjustment transport. You have a choice between Upgrade and OCS (Sup-
undead state. If a standard object that is of use to you disappears, then it’s better to port Package updates or add-on installations). Choose Upgrade. This choice
create a copy of that object in the customer name range (remember, you’re working ensures that SUM only uses these transports for their correct purpose.
in the shadow instance; in the primary instance, the object still exists). 4. You may now leave Transaction SPDD. The upgrade process records the number of
the transport request in a file in the transport directory.
Note
We didn’t mention this explicitly before, but in every object list it’s possible to select
6.6.2 Start Activation
multiple objects at once. Transaction SPDD will then calculate which actions are
common to all objects in the selection and show only those in the action list. This fea- With Transaction SPDD behind you, return to SUM, which is still displaying the
ture is particularly useful when you decide to delete the modification log for an screen shown in Figure 6.1. Enable the Adjustments Made, Continue with Procedure
entire group of objects. checkbox and choose Next. The upgrade process now starts the long activation
384 385
6 Modification Adjustment 6.7 Transaction SPAU
phase. This process and the probable interventions to fix activation errors are changed functionality is now covered by the standard, or perhaps by a new pro-
described in Chapter 5. gram or transaction. There’s no simple way to tell.
This raises another question: Should you know about Transaction SPAU at all? Here
the answer is yes, absolutely. Transaction SPAU is an integral part of the upgrade pro-
6.7 Transaction SPAU
cess, and you must be fully aware of its function and its impact on the upgrade or
The companion transactions of SPDD for development objects (as opposed to Data conversion even if you don’t actually do the work yourself. For this reason, we end
Dictionary objects) are Transactions SPAU and SPAU_ENH; the latter transaction is this chapter by giving you a brief introduction to Transactions SPAU and SPAU_ENH. 6
used for enhancements. Both transactions are built on the modification adjustment We can summarize the main characteristics of Transaction SPAU in a series of bullet
concept and support automatic and semiautomatic reconciliation of changes to points:
objects.
쐍 Like Transaction SPDD, Transaction SPAU adjustments are based on the Modifica-
As we remarked in the beginning of this chapter, it isn’t entirely true that Transaction tion Assistant.
SPAU deals only with non-Data Dictionary objects. Modified ABAP code will always
쐍 The user interface is the same as that of Transaction SPDD, with modified objects
show up in Transaction SPAU, but so will modifications to objects that are technically
assigned to several object lists.
part of the Data Dictionary, like views and search helps. One thing they have in com-
mon is that adjustments in Transaction SPAU can’t give rise to changes in the physi- 쐍 The decision process is also the same: adjust (i.e., keep the modification) or reset
cal structure of data. This is also the reason that, unlike Transaction SPDD, Transac- (forget about the modification and accept the new SAP standard).
tions SPAU and SPAU_ENH are executed after the upgrade. 쐍 Transaction SPAU covers more object types than Transaction SPDD; most are
One question to ask regarding Transaction SPAU is this: Is running it something that ABAP code objects (programs, function modules, object methods), but others are
you (by which we mean the technical expert performing the conversion) should be Data Dictionary-based (like views or search helps) or other noncode objects (like
expected to do? The answer to that is a clear no, and there are at least two good rea- message sets or transaction definitions). Occasionally, some exotic beast may
sons for this: even show up (does anyone know what a HRDSYS Logical Information Object is?),
requiring specialist knowledge.
쐍 The number of objects in Transaction SPAU is often much higher than in Transac-
tion SPDD. Transaction SPAU lists containing several thousand objects are not 쐍 Also like Transaction SPDD, it’s possible to concentrate all Transaction SPAU
exceptional. Performing Transaction SPAU after an upgrade is almost always a adjustments (including resets) in a single transport request, which you can then
team effort, with developers and functional experts in different application areas register for use in subsequent upgrades. For Transaction SPAU, this is less of a
collaborating. Even if you possessed all the technical and functional knowledge to necessity though. Because Transaction SPAU-based modifications are enacted
evaluate and adjust every Transaction SPAU object, it would probably take far too only after the upgrade, it’s perfectly feasible to create several Transaction SPAU
long for a single person to do all this work. requests and import them when the technical upgrade itself has finished. In some
cases, it’s even impossible to keep everything in one request; for example, the
쐍 Not only the number of objects but also the complexity tends to be higher. You
may have learned from what we’ve shown you about Transaction SPDD that you HRDSYS Logical Information Object we mentioned in the previous paragraph is
need to be careful and know what you’re doing, but it’s also true that there’s client-dependent by nature and modifications thus get recorded in a Customizing
rarely much doubt about the decisions. In most cases, the choice to adjust or rather than a workbench request.
reset in Transaction SPDD is fairly straightforward. In Transaction SPAU, it isn’t. Normally, whenever a developer makes a change to an SAP object, the system will ask
When you find that custom code was added in an SAP program two or three for an object key. These keys, which depend on the object itself, the installation num-
releases ago, how can you be sure that those changes are still needed? Perhaps the ber of the system, and the SAP release, can be generated in the SAP Software Change
386 387
6 Modification Adjustment 6.8 Transaction SPAU_ENH
Registration (SSCR) system in the SAP Support Portal. Transaction SPAU may entail longer relevant in the version control system (Reset action), or to keep the change by
having to adjust dozens or even hundreds of objects, and in such circumstances hav- reapplying it or letting the Modification Assistant reapply it (Adjust action).
ing to request an object key for every single one would be tedious and time-consum- If you look again at the screenshot in Figure 6.23, you’ll see an ellipsis (…) to the right
ing. That’s why the end of the technical upgrade marks the beginning of a 14-day of the three screen tabs. When you click here, you’ll see three more areas appear (Fig-
grace period during which SAP objects can be modified with Transaction SPAU with- ure 6.24).
out the need to provide an object key. Transaction SPDD never requests object keys.
As we mentioned earlier, the main Transaction SPAU screen looks very much like
6
that of Transaction SPDD. Figure 6.23 shows an example.
Figure 6.24 Additional Transaction SPAU Tabs
Transaction SPAU also has its Deletions list, and we strongly advise you to deal with
the objects here like you did in Transaction SPDD. The other two lists, which are dese-
lected by default, are used less frequently, although they should of course always be
Figure 6.23 Transaction SPAU Object List looked at. The Migrations tab is for Business Add-Ins (BAdIs) that need to be migrated.
Translations is for language-dependent objects, such as messages or menu items,
The Notes tab lists all SAP Notes that were applied since the last upgrade (or earlier, if that have been translated by SAP but for which a custom translation existed in the
they weren’t handled properly in a past Transaction SPAU run). A dark (gray) traffic old release.
light means that the SAP Note is obsolete; that is, the correction it introduced is now
part of the standard. SAP Notes with a colored traffic light require some kind of
adjustment. 6.8 Transaction SPAU_ENH
The list of available actions on the right will automatically adapt to the type and sta-
Since SAP introduced the enhancement concept, which allows customers to make
tus of the selected object. For example, if you select one or more obsolete SAP Notes,
changes to standard functionality without actually altering the SAP source code
only the Confirm Obsolete SAP Note action will be available.
itself, there has been a third transaction for modification adjustment besides Trans-
You’re already familiar with the With Assistant and Without Assistant sections. They actions SPDD and SPAU: Transaction SPAU_ENH. With this transaction, you adjust
have the same meaning as in Transaction SPDD. The first list contains objects that customer implementations of enhancements to the new release.
can be handled by the Modification Assistant, either fully automatically or with some
The user interface of Transaction SPAU_ENH is different from that of its two compan-
additional manual work. Objects in the second list can’t be adjusted with the Modifi-
ions; actually, Transaction SPAU_ENH calls the ABAP Workbench and specifically the
cation Assistant and require manual adjustment.
Enhancement Information System with the object type Enhancements (Upgrade
The actions for these objects are the same as in Transaction SPDD. You normally View). All objects that need reviewing are listed on the left, as shown in Figure 6.25.
start by comparing the last modified version with the new standard version using We apologize for the ugly blurring of the object names and descriptions, which is nec-
Compare Versions (New Original vs. Last Modification). Based on this comparison, essary for confidentiality reasons, but the objects listed here are the enhancement
you then decide either to accept the new standard and mark past modifications as no implementations that you can call up and display with Transaction SE20.
388 389
6 Modification Adjustment 6.9 Summary
5. Click Display <-> Change to switch to change mode. The toolbar on the right now
changes, as shown in Figure 6.27. If you decide the adjustment must be kept, use
the Process Conflict button to make the necessary changes to the implementation.
Click Adjust Enhancement Implementation, which changes the object status to
Adjusted.
Figure 6.27 Adjusting Enhancement
6.9 Summary
Figure 6.25 Transaction SPAU_ENH Object List In this chapter, we took a detailed look at the transactions used to preserve customer
changes or reset to standard SAP objects, a process known as modification adjust-
You must review, possibly adjust, and confirm each object in the list regardless of the ment. Transaction SPDD deals with Data Dictionary objects and is carried out during
color of the status icon. The normal order of operations is as follows: the upgrade, usually by the technical consultant doing the upgrade. Transaction
1. Double-click the object. This displays its details in the right-hand pane. SPAU (and Transaction SPAU_ENH for enhancements) covers ABAP objects (such as
2. The Adjustment tab shows the reason the object needs to be reviewed and programs or object classes) and Data Dictionary objects that do not affect physical
adjusted. There may even be more than one reason. In the example in Figure 6.26, data storage (e.g., views). Transactions SPAU and SPAU_ENH are performed after the
there are two adjustments: one with medium priority (green) and the other with upgrade, in most cases by a developer or team of developers.
low priority (gray). Modification adjustment, and especially Transaction SPDD, has something of a fear-
some reputation among developers and technical consultants. We have known quite
a few colleagues, both experienced and novice, to quake in their boots at the thought
of having to work their way through an intimidating Transaction SPDD list (just like
we were quaking in ours when we did our first Transaction SPDD run).
With this chapter, we’ve hopefully had some success in demystifying Transactions
SPDD and SPAU. Nevertheless, modification adjustment remains a critical and tech-
nically challenging task, and the ability to perform it correctly requires very good
Figure 6.26 Adjustment List for Enhancement
knowledge of the Data Dictionary and ABAP Workbench.
3. The Conflict Type column informs you why there is a conflict between the two ver-
sions. Click Long Text for a somewhat more complete explanation of the conflict
type.
4. Click Display Conflict to display the differences between the current and new ver-
sions.
390 391
Contents
Acknowledgments .............................................................................................................................. 19
Preface ..................................................................................................................................................... 21
1 Introduction to SAP S/4HANA 25
1.1 New Possibilities, Features, and Functionality ...................................................... 25
1.2 SAP S/4HANA in the Cloud versus On-Premise ...................................................... 27
1.3 New Implementation, System Conversion, and Transformation

Scenarios .................................................................................................................................. 29
1.3.1 Migration Scenarios ............................................................................................. 30
1.3.2 Choosing Your Approach ................................................................................... 35
1.4 Simplification ........................................................................................................................ 38
1.4.1 Technical and Functional Simplifications .................................................... 38
1.4.2 SAP HANA Column Store .................................................................................... 40
1.5 Conversion Methodology ................................................................................................ 44
1.5.1 Preparation Phase ................................................................................................ 45
1.5.2 Executing the Preparation Activities ............................................................. 48
1.5.3 Sandbox Conversion ............................................................................................ 50
1.5.4 Landscape Conversion ........................................................................................ 52
1.5.5 Postconversion ...................................................................................................... 54
1.6 SAP S/4HANA Transformation Enablers ................................................................... 54
1.6.1 SAP Business Scenario Recommendations for SAP S/4HANA ............... 55
1.6.2 SAP Innovation and Optimization Pathfinder ............................................ 56
1.6.3 SAP Transformation Navigator ........................................................................ 57
1.6.4 SAP Roadmap Viewer .......................................................................................... 58
1.6.5 SAP Best Practices and SAP Model Company .............................................. 59
1.7 Summary ................................................................................................................................. 61
7
Contents Contents
2 Architecture, Tools, and Strategy 63 2.10 Upgrading the Frontend Software ............................................................................... 125
2.10.1 SAP GUI’s Lifecycle ............................................................................................... 126
2.10.2 Version Selection .................................................................................................. 126
2.1 SAP S/4HANA Architecture ............................................................................................. 63
2.10.3 Introducing Belize ................................................................................................. 127
2.1.1 Technical Components ...................................................................................... 65
2.1.2 Core Releases ......................................................................................................... 67 2.11 SAP Landscape during Conversion ............................................................................... 128
2.1.3 Corrections and Enhancements ...................................................................... 68 2.11.1 Scenario 1: The Sandbox System .................................................................... 130
2.11.2 Scenario 2: Extra Development and Quality Assurance Systems ........ 132
2.2 SAP S/4HANA and SAP Fiori ........................................................................................... 72
2.11.3 Scenario 3: Contingency System ..................................................................... 134
2.2.1 Deployment Options .......................................................................................... 73
2.2.2 Impact of Conversion on SAP Fiori ................................................................. 74 2.12 Summary ................................................................................................................................. 135
2.3 SAP Solution Manager and SAP S/4HANA ............................................................... 75
2.3.1 Scope and Effort Analyzer ................................................................................. 76
2.3.2 Usage and Procedure Logging ......................................................................... 76 3 Project Planning 137
2.3.3 Custom Code Management ............................................................................. 77
2.3.4 Data Volume Management .............................................................................. 77
3.1 Why Convert to SAP S/4HANA? .................................................................................... 137
2.4 Maintenance Planner ........................................................................................................ 78 3.1.1 SAP Strategy ........................................................................................................... 138
2.5 SAP Readiness Check ......................................................................................................... 83 3.1.2 Outdated SAP Version ......................................................................................... 138
2.5.1 Verification and Prerequisites ......................................................................... 83 3.1.3 Release Support and Maintenance Costs ..................................................... 139
2.5.2 Installing SAP Readiness Check ....................................................................... 86 3.1.4 Enhancement Package Installation versus Converting to
2.5.3 Collecting the Data .............................................................................................. 87 SAP S/4HANA ......................................................................................................... 139
2.5.4 Verifying the Results ........................................................................................... 91 3.1.5 Upgrading Is a Normal Activity ........................................................................ 140
2.6 Simplification Item Check ............................................................................................... 95 3.2 Factors Influencing Conversion Complexity ............................................................ 140
2.6.1 Simplification Item Information ..................................................................... 96 3.2.1 Technology-Related Factors .............................................................................. 141
2.6.2 Running the Simplification Item Check ........................................................ 98 3.2.2 Development-Related Factors .......................................................................... 146
2.6.3 SAP Readiness Check versus the Simplification Item Check ................. 104 3.2.3 Business-Related Factors ................................................................................... 149
3.2.4 Project-Related Factors ....................................................................................... 151
2.7 Sizing for SAP HANA .......................................................................................................... 105
3.2.5 Forgotten Factors ................................................................................................. 152
2.8 Software Update Manager ............................................................................................. 108
3.3 Estimating the Effort .......................................................................................................... 153
2.8.1 System Switch Upgrade ..................................................................................... 109
3.3.1 Technical Conversion to SAP S/4HANA ......................................................... 154
2.8.2 Database Migration Option ............................................................................. 112
3.3.2 Modification to SAP Objects ............................................................................. 156
2.8.3 Performing the DMO with System Move ..................................................... 114
3.3.3 Custom Developments ....................................................................................... 159
2.8.4 Additional Options for Reducing Downtime .............................................. 116
3.3.4 Functional Effort ................................................................................................... 161
2.9 Database- and Operating System-Specific Aspects ............................................. 121 3.3.5 Obsolete Transactions ........................................................................................ 161
2.9.1 Unsupported Operating Systems ................................................................... 121
3.4 Project Team .......................................................................................................................... 162
2.9.2 Multiple Components in One Database ....................................................... 124
3.4.1 Project Management Team .............................................................................. 163
2.9.3 Update of Dual-Stack Systems ........................................................................ 124
3.4.2 Technical Conversion Team .............................................................................. 164
8 9
Contents Contents
3.4.3 Functional Work Groups .................................................................................... 164 4.4.3 Choosing the Conversion Path ......................................................................... 212
3.4.4 Internal versus External Team ......................................................................... 165 4.4.4 Identifying the Backend and Frontend Systems ........................................ 212
3.5 Conversion Project Steps ................................................................................................. 168 4.4.5 Evaluating Errors and Continuing the Plan ................................................. 214
4.4.6 Viewing Target Software List ........................................................................... 215
3.5.1 Conversion Scope ................................................................................................. 169
4.4.7 Selecting Files ........................................................................................................ 216
3.5.2 Planning Levels ..................................................................................................... 169
4.4.8 Downloading the Stack XML File ..................................................................... 219
3.5.3 Critical Success Factors ...................................................................................... 170
4.4.9 Setting Session as Complete ............................................................................ 221
3.5.4 Scheduling the Conversion ............................................................................... 171
4.4.10 Reviewing and Changing a Transaction ....................................................... 222
3.6 Conversion Plan ................................................................................................................... 171
4.5 Preparations in the SAP ERP System ........................................................................... 224
3.6.1 SAP Activate for System Conversions ............................................................ 172
4.5.1 Setting a User ID for the Conversion .............................................................. 225
3.6.2 Master Project Plan ............................................................................................. 175
4.5.2 Applying SAP Notes .............................................................................................. 226
3.6.3 Action Plan ............................................................................................................. 178
4.5.3 Updating Transaction SPAM/Transaction SAINT ...................................... 227
3.6.4 Status Reporting ................................................................................................... 182
4.5.4 Checking Pool and Cluster Tables ................................................................... 228
3.7 Testing Phase ........................................................................................................................ 184
4.6 Final Preparations ............................................................................................................... 232
3.7.1 Test Focus ............................................................................................................... 184
4.6.1 Downloaded Stack and Stack XML File .......................................................... 233
3.7.2 Test Scenarios ....................................................................................................... 185
4.6.2 Certificate Revocation List ................................................................................. 233
3.7.3 Test Stages and Test Progression ................................................................... 186
4.6.3 SAP HANA Client ................................................................................................... 234
3.7.4 Automated Testing ............................................................................................. 189
4.6.4 License Key .............................................................................................................. 235
3.8 Summary ................................................................................................................................. 191 4.6.5 Migration Key ........................................................................................................ 236
4.7 Preparing SUM ...................................................................................................................... 238
4.7.1 Download the Latest SUM Version ................................................................. 239
4 Preparing the Conversion 193 4.7.2 Creating the SUM Directory .............................................................................. 239
4.7.3 Extracting SUM ..................................................................................................... 241
4.1 Introducing the Tools: SUM and DMO ....................................................................... 194 4.7.4 Registering SUM with SAP Host Agent ......................................................... 242
4.7.5 Starting SUM .......................................................................................................... 245
4.2 Conversion Documentation ........................................................................................... 195
4.7.6 SUM Observer ........................................................................................................ 247
4.2.1 Software Logistics Toolset ................................................................................ 196
4.7.7 MailNotifier ............................................................................................................ 247
4.2.2 Collecting the Documentation ........................................................................ 197
4.2.3 Keeping Documentation Up to Date ............................................................. 199 4.8 Summary ................................................................................................................................. 248
4.2.4 Creating Your Own Documentation .............................................................. 200
4.3 Conversion Software ......................................................................................................... 205
4.3.1 Stack XML File ........................................................................................................ 205 5 Converting the System 249
4.3.2 Download Basket and SAP Download Manager ........................................ 206
4.3.3 Download Directory ............................................................................................ 209 5.1 Planning the Conversion .................................................................................................. 249
4.4 Maintenance Planner ........................................................................................................ 209 5.1.1 Conversion of a Sandbox System .................................................................... 250
4.4.1 When to Run the Maintenance Planner ....................................................... 210 5.1.2 Conversion of the Development System ...................................................... 252
4.4.2 Starting the Maintenance Planner ................................................................. 211
10 11
Contents Contents
5.1.3 Conversion of the QA system ........................................................................... 252 5.8 Final Preprocessing Steps ................................................................................................. 306
5.1.4 Conversion of the Production System ........................................................... 252 5.8.1 Backup Request for SUM .................................................................................... 306
5.2 Starting the Conversion with SUM ............................................................................. 257 5.8.2 Switch SAP HANA Log Mode ............................................................................. 307
5.2.1 Roadmap Steps ..................................................................................................... 257 5.9 Roadmap Step: Execution ................................................................................................ 308
5.2.2 Initial Steps ............................................................................................................ 258 5.9.1 Logging On during Downtime .......................................................................... 309
5.2.3 Required Passwords ............................................................................................ 260 5.9.2 Unlocking the System ......................................................................................... 309
5.2.4 Results and Cleanup ........................................................................................... 261 5.9.3 Database Cloning ................................................................................................. 309
5.3 Roadmap Step: Extraction .............................................................................................. 263 5.9.4 Repeat Cloning (with Test Cycle) ..................................................................... 312
5.9.5 Period without Interaction ................................................................................ 313
5.4 Roadmap Step: Configuration ....................................................................................... 266
5.9.6 EU_SWITCH Phase ............................................................................................... 313
5.4.1 Process Parameters ............................................................................................. 267
5.9.7 Additional Downtime Phases ........................................................................... 314
5.4.2 Parameters for SAP HANA ................................................................................. 270
5.9.8 End of Downtime .................................................................................................. 315
5.4.3 Languages and SDMI .......................................................................................... 274
5.4.4 Check Required Notes ........................................................................................ 275 5.10 Roadmap Step: Postprocessing ..................................................................................... 316
5.4.5 Support Packages to Include ............................................................................ 276 5.10.1 Stop for SPAU Modifications ............................................................................ 317
5.4.6 Modification Adjustment Transports ........................................................... 277 5.10.2 Cleanup Processing .............................................................................................. 318
5.4.7 Shadow Instance .................................................................................................. 279 5.10.3 No Active Imports ................................................................................................. 319
5.10.4 Create Evaluation ................................................................................................. 319
5.5 Roadmap Step: Checks ..................................................................................................... 282
5.10.5 Save Upgrade Logs ............................................................................................... 320
5.5.1 Save Variants ......................................................................................................... 282
5.10.6 Procedure Completion ........................................................................................ 321
5.5.2 Security Profile Parameters .............................................................................. 283
5.5.3 Open Update Requests ...................................................................................... 284 5.11 SUM Special Features ......................................................................................................... 322
5.11.1 Conversion Logfiles .............................................................................................. 322
5.6 Roadmap Step: Preprocessing ....................................................................................... 285
5.11.2 Setting Breakpoints ............................................................................................. 325
5.6.1 Inactive Objects and Open Repairs ................................................................ 286
5.11.3 SUM Utilities .......................................................................................................... 327
5.6.2 Development and Transport Lock .................................................................. 288
5.6.3 Database Import Phase ...................................................................................... 289 5.12 Postconversion Activities ................................................................................................. 328
5.6.4 Start of Shadow Instance .................................................................................. 290 5.12.1 Database Backup .................................................................................................. 330
5.6.5 Manually Managing the Shadow Instance ................................................. 291 5.12.2 SAP and Database Parameters ......................................................................... 331
5.6.6 Stop for Modification Adjustment ................................................................. 292 5.12.3 Actions for the SAP Kernel ................................................................................. 332
5.6.7 Activation Phase ACT_UPG ............................................................................... 293 5.12.4 Selectively Release Some Background Jobs ................................................. 334
5.6.8 Activation Errors ................................................................................................... 296 5.12.5 Transport Landscape Changes ......................................................................... 335
5.6.9 Repeat the Activation ......................................................................................... 301 5.12.6 ABAP Load Generation: Transaction SGEN .................................................. 336
5.6.10 Final Phases ............................................................................................................ 301 5.12.7 Imports of Transport Requests ........................................................................ 340
5.6.11 End of Uptime ....................................................................................................... 302 5.12.8 Nonfatal Errors: Type P ....................................................................................... 341
5.12.9 Language Postprocessing .................................................................................. 341
5.7 Preparing for Downtime .................................................................................................. 302
5.12.10 Changes to Roles and Authorizations ........................................................... 344
5.7.1 SAP System Action ............................................................................................... 303
5.12.11 SAP_NEW Profile and Role ................................................................................ 348
5.7.2 Server-Level and Database-Level Actions .................................................... 305
5.12.12 Release Change Requests Opened during the Conversion ..................... 349
12 13
Contents Contents
5.12.13 System and Client Change Options ............................................................... 349 6.6 Final Steps ............................................................................................................................... 385
5.12.14 Unlock Users .......................................................................................................... 349 6.6.1 Registering the Transaction SPDD Transport for Later Use ................... 385
5.12.15 Restart Interfaces ................................................................................................. 349 6.6.2 Start Activation ..................................................................................................... 385
5.12.16 Release Background Jobs ................................................................................... 350
6.7 Transaction SPAU ................................................................................................................ 386
5.12.17 Clean Up Directories ........................................................................................... 350
5.12.18 Preserve the Source Database ......................................................................... 351 6.8 Transaction SPAU_ENH ..................................................................................................... 389
5.13 Post Go-Live ........................................................................................................................... 351 6.9 Summary ................................................................................................................................. 391
5.14 Troubleshooting .................................................................................................................. 354

5.14.1 Error Stops in SUM ............................................................................................... 354
5.14.2 Failed Background Jobs ...................................................................................... 355 7 Custom Code Management 393
5.14.3 Resetting the Conversion .................................................................................. 356
5.15 Summary ................................................................................................................................. 358 7.1 Custom Code Management Process ........................................................................... 395
7.2 Impact of SAP HANA ........................................................................................................... 397
7.3 Impact of Simplification ................................................................................................... 399
6 Modification Adjustment 361 7.3.1 Access to Deleted Repository Objects ............................................................ 400
7.3.2 Access to Disabled Repository Objects .......................................................... 402
6.1 Modification Adjustment Transactions .................................................................... 362 7.3.3 Adjusted Field Lengths ....................................................................................... 403
7.3.4 Append Structures ............................................................................................... 404
6.2 Preparing and Running Transaction SPDD .............................................................. 363
6.2.1 Repository Modification .................................................................................... 364 7.4 Enabling the ABAP Test Cockpit .................................................................................... 404
6.2.2 Logging on to the Shadow Instance .............................................................. 366 7.4.1 Version and System Requirements ................................................................ 404
6.2.3 Creating a User for the Modification Adjustment .................................... 367 7.4.2 Custom Code Adaption Process ....................................................................... 407
6.2.4 Enable Development Changes ........................................................................ 367 7.4.3 Installation and Configuration ........................................................................ 408
6.2.5 Log on to the Primary System .......................................................................... 367 7.5 Custom Code Analysis in the Preparation Phase ................................................... 413
6.2.6 Checking for Possible Data Loss ...................................................................... 368 7.5.1 Collecting Usage Data ........................................................................................ 414
6.2.7 Run Transaction SPDD ........................................................................................ 369 7.5.2 Custom Code Migration App ............................................................................ 419
6.3 Transaction SPDD Object List ......................................................................................... 370 7.5.3 Analyzing the Results .......................................................................................... 420
7.5.4 Changing the Scope of the Migration Project ............................................. 428
6.4 Transaction SPDD Transport Request ........................................................................ 372
7.5.5 Removing Unused Custom Code during the Conversion ........................ 430
6.5 Adjusting Objects ................................................................................................................ 373
7.6 Custom Code Adaptation after the Conversion ..................................................... 430
6.5.1 General Procedure ............................................................................................... 373
7.6.1 Enable the ABAP Test Cockpit .......................................................................... 431
6.5.2 Data Elements and Domains ........................................................................... 375
7.6.2 Adapting Custom Code in ABAP Development Tools ............................... 433
6.5.3 Customer Fields in SAP Tables and Structures ........................................... 378
6.5.4 Field Format Changes ......................................................................................... 381 7.7 Custom Code Adaptation as an Ongoing Process ................................................. 436
6.5.5 Technical Settings ................................................................................................ 382 7.7.1 Runtime Check Monitor ..................................................................................... 436
6.5.6 Processing Deleted Objects .............................................................................. 383 7.7.2 Performance and Tuning Using the SQL Monitor ..................................... 438
7.8 Summary ................................................................................................................................. 441
14 15
Contents Contents
8 Functional Conversion 443 Appendices 511
8.1 Business Partners ................................................................................................................ 444 A References ............................................................................................................................... 511

8.1.1 Impact of Conversion .......................................................................................... 445 B The Authors ............................................................................................................................ 523
8.1.2 Preparation Phase ................................................................................................ 448
8.1.3 Synchronization Phase ....................................................................................... 457
8.1.4 Postprocessing ...................................................................................................... 458
Index ........................................................................................................................................................ 525
8.2 Financials and Accounting .............................................................................................. 458
8.2.1 Impact of the Conversion .................................................................................. 459
8.2.2 Check and Reconcile Your Data ....................................................................... 460
8.2.3 Preparation and Migration of Customizing ................................................ 465
8.2.4 Migration Activities ............................................................................................. 468
8.2.5 Postprocessing Activities ................................................................................... 472
8.3 Credit Management ........................................................................................................... 474
8.3.2 Starting Points ...................................................................................................... 475
8.3.3 Migration Overview ............................................................................................ 481
8.4 International Trade and Trade Finance ..................................................................... 485
8.4.1 Intrastat with SAP S/4HANA International Trade ..................................... 485
8.4.2 Migration to Trade Finance .............................................................................. 487
8.5 Logistics ................................................................................................................................... 490
8.5.2 Preparation Steps ................................................................................................. 495
8.5.3 During the Conversion ....................................................................................... 501
8.5.4 Postconversion Steps .......................................................................................... 502
8.6 Sales and Distribution ....................................................................................................... 502
8.7 SAP Business Warehouse ................................................................................................. 504
8.8 Cleaning Up Obsolete Data after the Conversion ................................................ 506
8.9 Summary ................................................................................................................................. 509
16 17
Index
A Action plan ..................................................... 170, 178

sample .................................................................. 179
ABAP Call Monitor ...................... 49, 396, 407, 414 tasks ...................................................................... 178
activate ................................................................ 415 Activation logs ....................................................... 295
analyze data ...................................................... 416 levels ..................................................................... 295
background jobs ............................................... 416 Add-on compatibility ......................................... 142
enable ................................................................... 415 Add-ons ......................................................... 80, 84, 94
entry points ........................................................ 416 Adjustment list ...................................................... 390
usage data .......................................................... 418 Adjustment transport ......................................... 365
ABAP central service instance Adobe Document Services .................. 46, 79, 144
(ASCS) .......................................................... 114, 305 Aggregate tables ...................................... 39–40, 490
ABAP Development Tools (ADT) .......... 397, 433 Aggregate Usage Data Collector ..................... 414
adapt code .......................................................... 433 Aggregation tools ................................................. 396
ABAP dictionary enhancements .................... 425 AIX .............................................................................. 122
ABAP dictionary views ....................................... 427 AnyDB ....................................................................... 143
ABAP load generation ......................................... 336 Append structure .............................. 378–379, 404
ABAP loads ............................................................... 269 name ..................................................................... 380
ABAP platform ........................................... 46, 64–65 proposal ............................................................... 379
ABAP runtime analysis ....................................... 439 register ................................................................. 380
ABAP Test Cockpit ................ 48, 51, 89, 394, 396, Application indexes ............................................ 472
404–405, 407 Application server ................................................ 333
authorizations .................................................. 409 Application-specific upgrade toolbox ............. 97
browser ................................................................. 433 Architecture ............................................................... 63
compare solutions ........................................... 406 Archive logging (Oracle) .................................... 303
configure ............................................................. 412 Asset accounting .................................................. 467
enable ................................................................... 431 Authentication ...................................................... 245
fix findings .......................................................... 435 Authorization manager ..................................... 165
installation and configuration ................... 408 Authorizations .............................................. 344, 409
results browser .................................................. 433 Automated testing ..................................... 189–190
schedule run ....................................................... 432
version and system requirements ............. 404 B
ABAP Workbench ............................... 371, 389, 433
Acceptance system .................................................. 53 Background jobs ................................................... 355
Accrual engine ....................................................... 467 releasing ..................................................... 334, 350
Acquisition and production costs (APC) ..... 462 suspending before downtime ..................... 303
ACT_UPG phase ........................ 278, 292–293, 503 Backup ....................................................................... 255
errors ..................................................................... 296 database ..................................................... 306, 330
levels ...................................................................... 295 SUM directory ................................................... 306
logfiles .................................................................. 294 Balance carryforward ................................. 461, 473
monitoring ......................................................... 294 Balloon ...................................................................... 321
operation ............................................................. 293 Base tables ............................................................... 427
repeat .................................................................... 301 Basis ........................................................... 65, 217, 320
525
Index Index
Basis administrator .......................... 163–164, 166 Compatibility Packages ........................................ 26 Customer/vendor integration (CVI) ............. 445 Declustering .................................................. 228, 424
BCD errors ..................................................... 231–232 Computer-Aided Test Tool (CATT) ................. 190 approach ............................................................. 447 Decompression errors ........................................ 231
Belize ......................................................................... 127 Condition contract management ................... 504 best practices ..................................................... 447 Deleted objects ...................................................... 383
Bill of materials (BOM) .............................. 493, 499 Consistency check ................................................ 101 customizing ........................................................ 452 Delta display ........................................................... 382
Binary-coded decimal (BCD) ............................ 230 Contingency system .................................. 130, 134 number ranges .................................................. 453 Delta merge ................................................................ 43
Blacklist Monitor .................................................. 402 Controlling ............................................................... 468 reports .................................................................. 452 Delta record and replay technology ............. 117
Bluefield implementation ................................... 34 Conversion control document ........................ 201 synchronization ...................................... 445, 452 Depooling ....................................................... 228, 424
Breakpoints ............................................................. 325 Conversion path .................................................... 212 Cutover plan ........................................................... 181 Development objects ................................. 158, 362
actions .................................................................. 326 Core data services (CDS) views .................. 27, 502 CVI Cockpit .................................................... 449–450 Development system ................................... 52, 131
Brownfield implementation ............................... 32 CREATE_UPGEVAL phase ................................... 319 Alpha testing ..................................................... 177
BSIS view .................................................................. 400 Credit checks ................................................. 478, 481 D conversion .......................................................... 252
Business analyst .................................................... 163 Credit management in SAP ERP Diagnostic agent ................................................... 241
Business functions ................................. 80, 84, 149 Financials ............................................................. 474 Data archiving ........................................................... 77 DIR_PUT profile parameter .............................. 241
Business partners ........................................ 444, 454 crontab ...................................................................... 305 Data browser ................................................. 416, 418 Directories clean up ............................................. 350
archive customer/vendor data .................. 451 Custom Code Analyzer ......................................... 89 Data deletion .......................................................... 507 Document flow ...................................................... 501
conversion impact ........................................... 445 Custom code management 77, 85, 94, 173, 393 Data Dictionary .................................... 51, 262, 378 Documentation ..................................... 93, 195, 450
conversion phases ........................................... 447 adaption process .............................................. 407 objects .......... 110, 156, 279, 317, 362, 369, 503 collecting ............................................................. 197
mapping .............................................................. 456 analyze results ................................................... 420 tables ..................................................................... 293 creation ................................................................ 200
migration ............................................................ 448 code analysis ...................................................... 413 Data elements .............................................. 375, 381 ownership ........................................................... 202
number rangers ................................................ 454 compatibility ...................................................... 405 Data inconsistencies .............................................. 99 postprocessing .................................................. 204
postprocessing .................................................. 458 Data Dictionary views .................................... 427 Data loss ................................................................... 368 structuring ................................................ 202–203
preparation phase ........................................... 448 database operations ....................................... 426 Data migration ....................................................... 463 SUM .............................................................. 198, 203
roles .............................................................. 445, 454 DDIC enhancements ....................................... 425 activities .............................................................. 469 up-to-date ........................................................... 199
verification reports ......................................... 455 field length extensions ................................... 424 complete .............................................................. 471 Domains ................................................................... 375
Business scenarios .................................................. 92 migration project ............................................. 419 postprocessing .................................................. 472 process ................................................................. 377
testing .................................................................. 188 native SQL ........................................................... 424 Data model ............................................. 38, 401, 443 Download basket ........................................ 219–220
ongoing process ................................................ 436 Data volume management .......... 46, 77, 94, 173 Download directory .......................... 209, 259, 350
C pool/cluster tables ........................................... 424 Database cloning ................................ 255, 309–310 Downtime ................................................................ 331
postconversion .................................................. 430 benchmarking ......................................... 265, 312 close repairs ....................................................... 303
Certificate revocation list (CRL) ............. 233, 260 prerequisites for test ....................................... 423 hard kill ................................................................ 311 default client ...................................................... 309
Change manager .......................................... 163, 166 process .................................................................. 395 Database conversions ......................................... 304 delete update requests ................................... 303
Change requests .................................................... 349 quick fixes ............................................................ 434 Database hints ............................................. 398, 424 end ......................................................................... 315
Check variant ......................................................... 431 scoping ................................................................. 428 Database import .......................................... 268, 289 minimize ............................................................. 155
CHECKS.LOG ........................................................... 261 simplified objects .............................................. 428 Database logs .......................................................... 253 prepare ................................................................. 302
Client 000 ........................................................ 464, 466 unused code ........................................................ 430 Database Migration Option (DMO) .... 108, 112, reduction ............................................................. 116
Client 066 .................................................................... 47 usage data ........................................................... 414 194, 236, 249 restrictions .......................................................... 150
Cluster tables ................................................. 228, 398 Custom Code Migration app ...... 44, 48, 52, 160, key notes .............................................................. 114 system locked .................................................... 309
parallel runs ....................................................... 230 394, 405, 412, 418–419 prerequisite check ............................................ 258 Downtime-optimized conversion ................. 119
Clustering ................................................................ 305 enable .................................................................... 410 repeat migration .............................................. 265 Downtime-optimized DMO ................... 117–118
Code freeze ..................................................... 129, 177 roles ........................................................................ 411 system move ...................................................... 115 Dual maintenance period ................................. 147
Code freeze period ............................................... 147 scope ...................................................................... 429 Database operations ............................................ 426 Dual-stack systems ....................................... 46, 124
initiate .................................................................. 148 usage data ........................................................... 420 Database parameters ........................................... 331 Dumps ....................................................................... 403
Code Inspector .......................... 404–405, 409, 431 Custom developments .... 37, 146, 152, 159, 167 Database server ..................................................... 272
Colors in system ................................................... 128 testing ................................................................... 187 Database tables ............................................ 378, 425 E
Column-based storage ................................... 40, 42 Custom objects ...................................................... 286 technical settings ............................................. 382
Commodity codes ................................................ 486 Customer fields ............................................ 378, 381 DB2 UDB ................................................................... 122 EA-GLTRADE add-on ........................................... 504
DDL views ................................................................ 404 eCATT ........................................................................ 190
526 527
Index Index
Eclipse .............................................................. 397, 433 G L Master project plan ........................... 169, 175–176
Effort estimation .................................................. 153 discovery phase ................................................ 176
functional ........................................................... 161 General ledger ........................................................ 467 Landscape Management Database sandbox conversion ........................................ 177
Emergency changes ............................................. 148 Go or no-go decision ............................................ 181 (LMDB) ........................................................... 78, 210 Material Ledger ..................................................... 468
Empty tables ........................................................... 437 Goods receipt .......................................................... 501 Landscape transformation ............................ 29, 33 Material number length .................................... 495
End of life ................................................................. 137 Greenfield implementation ................................ 31 drivers ...................................................................... 33 Material requirements planning (MRP) ...... 491
End user involvement ........................................ 150 Language supplementation ................... 341–343 changes ................................................................ 492
Enhancement Information System .............. 389 H Languages ................................................................ 274 controllers ........................................................... 496
Enhancement Packages ....................... 69–70, 139 Legacy System Migration Workbench list .................................................................. 493, 499
Enterprise extensions ............................................ 65 High availability .................................................... 305 (LSMW) ................................................................. 499 planning run ...................................................... 498
Errors ......................................................................... 296 House bank accounts .......................................... 468 License key .............................................................. 235 MaxDB ...................................................................... 122
data types ........................................................... 300 HP-UX ........................................................................ 122 download ............................................................ 236 Microsoft Management Console .................... 305
faulty objects ..................................................... 300 Human resources .................................................... 65 Licenses ........................................................................ 82 Migration activities ............................................. 468
field defined twice ........................................... 299 Hypercare mode ...................................................... 54 Linux on Power ..................................................... 122 Migration key ...................................... 236–237, 265
identical table indexes ................................... 299 Linux on x86 ........................................................... 122 experiation date ............................................... 238
incorrect source release ................................ 299 I Linux on z/OS ......................................................... 122 Migration scenarios ................................................ 30
logs ............................................................... 324, 354 Lock development ................................................ 288 approach choice .................................................. 35
reference deleted .............................................. 300 icmbnd ...................................................................... 332 LOCKEU_PRE phase ................................... 288–289 business processes .............................................. 37
stops ...................................................................... 354 Implementation effort .......................................... 37 Logfiles ............................................................ 291, 322 comparison ........................................................... 34
type P .................................................................... 341 Import queue .......................................................... 288 Logistics .................................................................... 490 hybrid ...................................................................... 33
EU_CLONE_MIG_DT_RUN phase .................. 309 Inbound delivery ................................................... 501 impact of conversion ...................................... 490 system requirements ......................................... 36
EU_IMPORT phase ............................................... 289 Industry solutions ........................................... 65, 81 postconversion .................................................. 502 Modification adjustment ...... 157, 167, 204, 361
EU_SWITCH phase ............................................... 313 Infrastructure-as-a-service (IaaS) ...................... 28 preparataion steps .......................................... 495 create user .......................................................... 367
Exit codes ................................................................. 341 Installation number ............................................. 237 LONGPOST.LOG file ............................................. 341 Data Dictionary objects ................................ 363
Exit codes (transports) ....................................... 322 Integration testing ................................................ 185 deleted objects .................................................. 383
Explicit sorting ...................................................... 399 Interfaces ........................................................ 253, 304 M domains ............................................................... 376
Extended maintenance support .................... 139 restart .................................................................... 349 enable development changes ..................... 367
International trade ............................................... 485 MailNotifier ............................................................. 247 field changes ...................................................... 381
F Internet Communication Framework .......... 412 Maintenance Optimizer ..................................... 209 log onto primary instance ........................... 367
Internet Communication Manager (ICM) ... 332 Maintenance planner .............. 44, 47, 78, 91, 209 objects .................................................................. 373
Feature Package Stacks (FPS) ........................ 67, 70 Internet Graphics Server (IGS) ......................... 216 checks ....................................................................... 80 passive deletion ................................................ 365
Field changes .......................................................... 382 Intrastat ..................................................................... 485 dependencies check ......................................... 220 protocol logs ...................................................... 369
Field lengths ........................................................... 403 Inventory management ..................................... 494 evaluate errors .................................................. 214 run Transaction SPDD ................................... 369
extensions ........................................................... 424 Issue lists .................................................................. 186 feature overview .................................................. 79 SUM ....................................................................... 364
Financial closing ................................................... 461 file selection ....................................................... 216 transactions ....................................................... 362
Financial documents ................................. 468, 488 J guided steps .......................................................... 81 transports ........................................................... 277
Financials and accounting ................................ 458 identify systems ................................................ 212 version comparison ........................................ 375
impact of conversion ..................................... 459 Java runtime environment (JRE) ..................... 207 language packages .......................................... 218 Modification Assistant ........... 156, 371, 387, 389
migration ............................................................ 465 maintenance transactions ........................... 222 Modification Browser ......................................... 157
reconcile data .................................................... 460 security notes ..................................................... 220 Modification log .................................................... 384
K
Functional conversion ....................................... 443 set session as complete .................................. 221 Modifications ......................................................... 156
Functional downtime ......................................... 254 Kernel ......................................................................... 332 side effects report ............................................. 220 MRP Live ................................................................... 492
Functional work groups ..................................... 164 Key users ................................................................... 165 starting ................................................................. 211 Multidisplay multiprocessing (MDMP) ....... 141
when to run ........................................................ 210 Multiple components in one database
Maintenance transactions ................................ 223 (MCOD) ....................................................... 121, 124
528 529
Index Index
N Passwords ............................................. 260, 271, 274 Regression testing ............................... 71, 185, 188 Runtime Check Monitor .................................... 436
Patch binding .......................................................... 276 Release strategy ........................................................ 71 checks ................................................................... 437
Native SQL ............................................................... 398 Performance tests ................................................. 185 REPACHK2 phase .................................................. 288
Near-Zero Downtime Maintenance (nZDM) ...... Piece list .................................................................... 409 Repairs ............................................................. 286, 303 S
108, 120 Placeholder conventions ................................... 224 objects ................................................................... 287
Near-Zero Downtime Technology Pool tables ................................... 228, 230, 232, 398 Report/program .................................................... 104 S_A.SYSTEM profile .............................................. 225
(nZDT) ................................................................... 120 Postconversion activities ................................... 182 /SDF/HDB_SIZING ........................................... 106 S_DEVELOP profile ............................................... 225
NETPL planning mode ........................................ 493 Postconversion tasks ........................................... 319 /SDF/RC_START_CHECK .................................. 98 S_RFC object ........................................................... 409
New implementation ..................................... 29, 31 Postprocessing activities ................................... 329 /SDF/RC_TROUBLESHOOT ........................... 102 S_YCM object .......................................................... 410
drivers ...................................................................... 31 Postprocessing orders ......................................... 453 BTCTRNS2 .................................................. 334, 350 S4HANA_READINESS_1909 variant ............. 409
overview ................................................................. 31 Prerequisite check ................................................. 258 CS_BOM_PRODVER_MIGRATION02 ....... 499 Sandbox environment ....................................... 178
Non-SAP add-ons ..................................................... 81 Primary application server (PAS) .................... 114 CVI_MIGRATION_PRECHK .......................... 104 Sandbox system .......................... 50, 129–130, 250
Non-SAP systems interfaces ............................ 145 Principle of one ...................................................... 443 FIN_CORR_DISPLAY ....................................... 104 checks ...................................................................... 51
NSDM_E_MSEG view .......................................... 400 Product Availability Matrix (PAM) ................. 142 FIN_CORR_RECONCILE .................................. 104 data migration ................................................. 470
Number ranges ...................................................... 454 Production planning and detailed scheduling FINS_MASS_DATA_MONITOR_MSG_ requirements ..................................................... 250
(PP-DS) .................................................................. 502 TRA .................................................................... 471 tasks ......................................................................... 50
O Production system ................................................. 53 RASUVAR1/2 ....................................................... 282 SAP account manager ......................................... 163
conversion ........................................................... 252 RC_COLLECT_ANALYSIS_DATA ............. 88, 90 SAP Activate ............................................................ 172
Object groups ......................................................... 508 Production versions ................................... 493, 499 REGENERATE_SAP_NEW ............................... 348 deploy phase ...................................................... 174
Object list ........................................................ 370, 388 Profile parameters ................................................ 331 RESCUE_OBJECTS_WITH_DATALOSS ...... 368 discover phase ................................................... 172
change request ................................................. 375 Project management team ................................ 163 RSUPG_SPDD_RESET_CANDIDATES ........ 365 explore phase .................................................... 173
navigation .......................................................... 373 Project manager .......................................... 163, 166 SAPRSEUC .............................................................. 89 methodology ..................................................... 172
reset object ......................................................... 376 Project planning .................................................... 137 SDBI_CHECK_BCD_NUMBERS ......... 231–232 prepare phase .................................................... 173
status icons ........................................................ 371 forgotten factors ............................................... 152 SDBI_CLUSTER_CHECK .............. 229–230, 232 realize phase ...................................................... 174
Object providers ................................................... 413 success factors ................................................... 170 SDBI_POOL_CHECK ........................................ 230 run phase ............................................................ 174
Observer Monitor ................................................. 247 Project scope ........................................................... 151 SDBI_POOL_DECOMPRESSION .................. 231 SAP Analytics Cloud ............................................ 505
Obsolete custom programs .............................. 161 Project team ............................................................ 162 SYCM_DOWNLOAD_REPOSITORY_ SAP ASE ..................................................................... 122
Obsolete data ......................................................... 506 internal vs. external ......................................... 165 INFO ..................................................................... 89 SAP Best Practices .......................................... 59, 175
Obsolete Data Handling tool .................. 506, 508 Proxy objects .......................................................... 401 ZSFW_O502_01 ................................................. 417 SAP Business Client ................................................ 72
Obsolete reports ................................................... 478 Purchasing ............................................................... 494 Repository objects ............................... 49, 402, 428 SAP Business Scenario Recommendations ... 55
Obsolete repository objects ............................. 479 Request entry points ........................................... 429 SAP Business Warehouse (SAP BW) ... 144, 504–
Obsolete tables .......................... 425, 427, 460, 502 Q Reset ........................................................................... 356 505
Obsolete transactions ...................... 161, 477, 494 conversion .......................................................... 356 embedded ........................................................... 506
Offsetting accounts ............................................. 473 QA system ................................................................ 252 point ...................................................................... 357 extractors ............................................................... 94
Online analytical processing (OLAP) ..... 41, 124 Quick fixes ..................................................... 422, 434 timing ................................................................... 357 SAP BW/4HANA ............................................. 27, 505
Online transactional processing (OLTP) 41, 124 RFC connection ...................................................... 413 SAP Cloud Appliance Library ........................... 172
Open SQL .................................................................... 47 R RFC server groups ................................................. 337 SAP Cloud Platform ...................................... 73, 408
Operating systems ............................................... 122 Risk category ........................................................... 484 SAP Credit Management ................ 474, 476, 478
compatibility ..................................................... 142 R3load .............. 265, 267–268, 290, 309–310, 312 Risk checks ............................................................... 489 exposure .............................................................. 484
Operation modes .................................................. 304 R3trans ...................................................................... 267 Roles ........................................................................... 344 further enhancements ................................... 485
Oracle ........................................................................ 122 Random-access memory (RAM) ...................... 142 add catalog ......................................................... 411 impact of conversion ..................................... 475
OS400 ........................................................................ 122 RDDIMPDP job ....................................................... 335 selection screen ................................................. 345 master data ........................................................ 484
Overwrite mode .................................................... 330 Rebate agreement ................................................. 503 Routing ..................................................................... 493 migration ................................................... 477, 483
Reconciliation ledger ........................................... 473 Row-based tables ..................................................... 41 migration overview ........................................ 481
P Recovery point objective (RPO) ......................... 50 RSTLAN_AFTER_UPGRADE job ....................... 342 postmigration activities ............................... 484
Recovery time objective (RTO) .......................... 50 RSVBCHCK job ....................................................... 284 preparatory activities .................................... 482
Packages ................................................................... 429 Red Hat Enterprise ................................................ 121
530 531
Index Index
SAP Credit Management (Cont.) SAP HANA (Cont.) SAP Readiness Check (Cont.) SAP system dependencies ................................ 143
prerequisities ..................................................... 479 syntax requirements ....................................... 160 install ....................................................................... 86 SAP Transformation Navigator ................ 57, 191
requirements ..................................................... 478 SYSTEM user ....................................................... 273 manual procedure .............................................. 86 SAP Transportation Management (SAP
starting points .................................................. 475 table placement strategy .............................. 273 verify results .......................................................... 91 TM) ................................................................ 444, 502
SAP Customer Relationship Management tables ....................................................................... 43 SAP release ............................................................... 138 SAP Treasury and Risk Management .. 444, 485,
(SAP CRM) ........................................... 65, 124, 444 tenant database ................................................ 272 maintenance limit ........................................... 139 487
SAP Digital Business Services ............................. 33 SAP HANA, express edition ............................... 173 SAP Roadmap Viewer ............................................. 58 SAP Workflow ......................................................... 485
SAP Download Manager ........................... 206, 233 SAP Host Agent .................................. 216, 238, 242 SAP S/4HANA ............................................................ 25 SAP_ALL profile ..................................................... 225
configuration .................................................... 208 ports ....................................................................... 244 architecture ........................................................... 63 SAP_NEW ................................................................. 348
installation instructions ............................... 207 registration ......................................................... 244 check reports ...................................................... 449 SAP_NEW_F4 .......................................................... 348
SAP EarlyWatch Alert ............................................. 56 root access ........................................................... 242 cloud vs. on-premise .......................................... 27 SAP_SATC_ADMIN role ..................................... 410
SAP Enterprise Portal ................................... 72, 144 secure connections .......................................... 244 core releases .......................................................... 67
SAP_UPGRADE_SHADOW_SYSTEM ............. 366
SAP ERP ..................................................................... 224 upgrade ................................................................ 242 foundation ............................................................. 64
SAPA* logs ................................................................ 294
preparations ...................................................... 224 version .................................................................. 243 frontend server ..................................................... 74
SAPCAR ..................................................................... 241
SAP ERP Sales and Distribution (SD) .... 486, 502 SAP Innovation and Optimization human resources ................................................. 67
SAProuter ................................................................. 305
SAP Fiori ............................................ 65, 72, 125, 212 Pathfinder ............................................................. 56 layout ....................................................................... 66
SAPup ..................................................... 262, 311, 355
application reference library .................. 55, 79 SAP Integrated Business Planning (SAP migration scenarios ........................................... 29
command line options ................................... 328
apps ................................................................... 85, 94 IBP) ......................................................................... 502 product overview ................................................ 25
control shadow instance .............................. 292
deployment options ................................... 73–74 SAP IQ .......................................................................... 42 roadmap ................................................................. 58
embedded deployment ..................................... 74 SAP Java Virtual Machine (JVM) ...................... 242 strategy ................................................................ 138 locksys/unlocksys ............................................ 309
hub deployment .................................................. 73 SAP landscape ......................................................... 128 target version ....................................................... 98 SAPup.log ................................................................. 323
impact of SAP S/4HANA .................................. 74 contingency system ......................................... 134 technical components ....................................... 65 SAPupConsole.log ................................................ 324
SAP Fiori Cloud ......................................................... 73 extra development and acceptance technical conversion ....................................... 154 sar (Linux command) ......................................... 311
SAP Fiori launchpad ................................... 211, 411 system .............................................................. 132 transformation enablers .................................. 54 Satellite development systems ....................... 133
SAP Global Trade Services (SAP GTS) ............ 485 sandbox system ................................................ 130 UI ............................................................................... 72 SAVELOGS phase .................................................. 320
SAP GUI ..................................................... 72, 125, 146 virtual system ................................ 131–132, 134 why convert ........................................................ 137 Schedule ................................................................... 256
lifecycle ................................................................ 126 SAP Logon ...................................................... 126, 133 SAP S/4HANA Adoption Starter Scope ................................................................. 422, 429
version ......................................................... 126, 185 SAP Master Data Governance ............................ 65 Engagement ....................................................... 191 Scope and Effort Analyzer .......................... 76, 173
SAP HANA ............................... 27, 40, 121, 216, 311 SAP Model Company ...................................... 59–60 SAP S/4HANA Cloud ................................ 28, 30, 67 Secondary index ................................................... 398
certified hardware ........................................... 143 SAP NetWeaver ..................................... 63, 405, 415 SAP S/4HANA Cloud, essentials edition ......... 28 Security profile ...................................................... 283
client ..................................................................... 270 SAP NetWeaver-based system ......................... 195 SAP S/4HANA Cloud, extended edition .......... 28 Selective data transition ....................................... 33
client software .................................................. 234 SAP Notes ............................. 86, 102, 275, 368, 422 SAP S/4HANA embedded analytics ........ 26, 505 Senior program manager .................................. 163
code adaption ................................................... 396 ABAP Test Cockpit ............................................ 410 SAP S/4HANA Finance ........................................... 68 Server groups ......................................................... 337
features ................................................................ 397 apply ...................................................................... 226 SAP S/4HANA for international trade .......... 486 Shadow instance ... 109, 111, 226, 254, 279, 366
impact on code ................................................. 397 for conversion .................................................... 198 SAP S/4HANA Sales .............................................. 502 locked ................................................................... 297
indexes .................................................................... 43 obsolete ................................................................ 388 SAP Simple Finance ................................................ 68 manual control ................................................. 291
infrastructure .................................................... 142 version compare ............................................... 200 SAP Software Change Registration memory ............................................................... 291
installation information ............................... 271 SAP objects ............................................................... 156 (SSCR) .......................................................... 318, 387 parameters ......................................................... 281
log mode .................................................... 307, 330 SAP Process Integration(SAP PI) ...................... 144 SAP Solution Explorer ............................................ 55 profiles ....................................................... 281–282
native SQL ........................................................... 424 SAP Process Orchestration (SAP PO) ............. 144 SAP Solution Manager ....... 40, 75, 210, 212, 420
RFC ......................................................................... 366
parameters ................................................ 270, 332 SAP R/3 ...................................................................... 165 custom code management ............................. 77
startup .................................................................. 290
password rules .................................................. 273 SAP Readiness Check .... 47–49, 83, 85, 104, 142, data volume management ............................. 78
trace files ............................................................. 291
problematic statements ................................ 423 394, 407, 415 Scope and Effort Analyzer ............................... 76
Shadow repository ............................ 113, 279–280
schema name .................................................... 272 analysis ................................................................... 89 Usage and Procedure Logging ....................... 76
Silent Data Migration Infrastructure
search DB operations ..................................... 424 dashboard ............................................................. 91 SAP Supplier Relationship Management (SAP
(SDMI) ................................................ 267, 274, 314
sizing ..................................................................... 105 data collection ..................................................... 87 SRM) ...................................................................... 124
532 533
Index Index
Simplification ................ 38, 85, 95, 393, 443, 503 Software Update Manager (SUM) (Cont.) Space requirements ............................................. 110 System conversion (Cont.)
adjusted field lengths ..................................... 403 downtime-optimized data conversion .... 119 SPAU stop ................................................................. 317 prerequisites ...................................................... 180
data model ............................................................ 39 downtime-optimized DMO .......................... 117 SPDD stop ................................................................ 292 process diagram ............................................... 254
database ..................................................... 396, 409 errors ..................................................................... 296 SQL Monitor .................................. 49, 396, 438–439 process parameters ......................................... 267
deleted repository objects ............................ 400 evaluation ........................................................... 319 configuration ..................................................... 440 project steps ....................................................... 168
disabled repository objects .......................... 402 extraction ............................................................ 241 SQL Server ................................................................ 122 schedule ............................................................... 256
impact ......................................................... 160, 399 HTTP and HTTPS ports ................................... 244 SQL trace ......................................................... 438–439 scheduling ........................................................... 171
item category .................................................... 422 HTTPS address ................................................... 246 SQLM .......................................................................... 396 scope ..................................................................... 169
item consistency ................................................. 90 inactive objects ................................................. 286 ST-A/PI tools ....................................................... 65, 86 software ............................................................... 205
item list ..................................................... 40, 47, 96 job failure ............................................................ 355 Stack XML .................. 82, 205–206, 233, 259, 263 source releases ..................................................... 45
item list version ................................................ 102 languages ............................................................ 274 download ............................................................ 219 user ID .................................................................. 225
items ....................................................... 92–93, 409 late development lock point ........................ 289 Status reporting .................................................... 182 System inconsistencies ...................................... 464
proxy objects ..................................................... 400 migration parameters .................................... 264 Stock provided to vendor .................................. 492 System Installation Check ................................ 334
redundant tables .............................................. 402 near-Zero Downtime Maintenance Storage location MRP areas ........... 491, 495–496 System landscape ................................................. 129
tables replaced by views ............................... 400 (nZDM) ............................................................. 120 ST-PI plug-in ............................................................... 65 System Landscape Directory (SLD) ................... 78
technical ................................................................. 38 Observer Monitor ............................................. 247 ST-PI/A ......................................................................... 48 System requirements ............................................ 45
Simplification Item Check 44, 48, 51–52, 93, 95, open updates ...................................................... 284 Structures ................................................................. 378 System switch ........................................................ 279
97–98, 104, 407, 415, 461 passwords ............................................................ 260 Subcontracting ............................................ 498, 500 System switch upgrade ...................................... 109
return codes ....................................................... 100 patch binding ..................................................... 276 SUMSTART script .................................................. 244
runtime ................................................................ 104 phase failure ....................................................... 354 Support Package Stacks (SPS) .............................. 70 T
start .......................................................................... 98 postconversion activities .............................. 328 Support Packages ........................................... 68, 276
where to run ....................................................... 103 prepare .................................................................. 238 queue ..................................................................... 277 TABIM_UPG phase ............................................... 314
Simplified sourcing ............................................. 493 prerequisite check .................................. 259, 324 Supported browsers ............................................. 246 Table
Sizing ........................................... 45, 85, 92, 105, 107 procedure complete ......................................... 321 SUSE Linux Enterprise ........................................ 121 BSEG ...................................................................... 228
SL Toolset .............................................. 109, 196, 385 Process Control Center ................................... 328 S-user ............................................................... 211, 233 BSIS ........................................................................ 426
patches ................................................................. 197 profile reuse ........................................................ 281 Synchronization Cockpit ................................... 457 BUT000 ............................................................... 446
versions ................................................................ 196 registration ......................................................... 242 System administrator ......................................... 164 CDCLS ................................................................... 228
Software Provisioning Manager (SWPM) .... 196 resetting ............................................................... 356 System change options ...................................... 367 KNA1 ...................................................................... 446
Software Update Manager (SUM) .... 45, 53, 108, roadmap steps ................................................... 257 System conversion .......................... 29, 32, 44, 249 LFA1 ....................................................................... 446
115, 194, 216, 249, 364, 447 SAP Notes ............................................................. 226 advantages ............................................................ 33 MATDOC ..................................................... 301, 427
activation phase .............................................. 292 shadow instance ............................................... 279 checks .................................................................... 282 MSEG ..................................................................... 400
active imports ................................................... 319 space needed ...................................................... 240 complexity .......................................................... 140 VBUK ..................................................................... 402
archive authenticity ....................................... 263 special features .................................................. 322 configuration ..................................................... 266 VBUP ..................................................................... 402
background jobs .............................................. 268 start ........................................................................ 245 execution ............................................................. 308 Table Browser ......................................................... 159
backup .................................................................. 306 start conversion ................................................ 257 extraction ............................................................ 263 Target software list .............................................. 215
breakpoints ........................................................ 325 system move ....................................................... 114 final preparations ............................................ 232 Task Scheduler (Windows) ................................ 305
browser support ............................................... 245 table comparison ............................................. 265 landscape conversion ........................................ 52 Technical configuration testing ..................... 187
canceled jobs ..................................................... 356 tables ..................................................................... 460 methodology ........................................................ 44 Technical conversion ................................. 153, 193
cleanup ................................................................ 261 Transaction SPAM/SAINT ............................. 227 overview .................................................................. 32 Technical conversion team .............................. 164
cleanup processing ......................................... 318 user authentication (Unix/Linux) .............. 245 plan ........................................................................ 171 Test conversions ......................................... 250–251
planning .............................................................. 249 Test migrations ..................................................... 265
CRL ......................................................................... 234 utilities .................................................................. 327
post go-live ......................................................... 351 Test scenarios ......................................................... 185
customer-specific transports ...................... 263 versions ................................................................ 197
postconversion ..................................................... 54 Test stages ............................................................... 186
Database Migration Option (DMO) ......... 112 Solaris ......................................................................... 122
postprocessing .................................................. 316 Testing ................................................... 151, 167, 184
directory ..................................................... 239, 350 Solution gap ............................................................ 138
preparation ........................................................ 193 focus ...................................................................... 184
directory path ................................................... 240 Source database ..................................................... 351
preparation phase .............................................. 45 progression ......................................................... 186
download ............................................................ 239 Source release ......................................................... 141
preprocessing .................................................... 285 top (Linux command) ......................................... 311
534 535
Index Index
Trade finance .......................................................... 485 Transaction (Cont.) Transaction (Cont.) Upgrade strategy
customizing ....................................................... 487 SCMON .............................. 49, 396, 414–415, 419 SU10 ....................................................................... 304 downtime-optimized ...................................... 112
data migration ................................................. 488 SE03 ....................................................................... 225 SU25 ............................................................. 344–346 single system ..................................................... 111
migration ............................................................ 487 SE06 ................................................... 225, 349, 367 SUSG ......................... 49, 396, 414, 418, 420, 438 standard ..................................................... 109, 112
Transaction SE09 ................................................... 286, 303, 385 SYCM ..................................................................... 409 Upgrade Transport Integration Wizard ....... 263
/IWFND/MAINT_SERVICE ............................ 412 SE10 ........................................................................ 286 UKM_BP ............................................................... 477 Uptime ...................................................................... 253
/SDF/SCMON ............................................ 415, 419 SE11 ............................................ 157, 298, 368, 401 UKM_CASE ......................................................... 484 end ......................................................................... 302
AFAB ...................................................................... 462 SE12 ............................................................... 368, 401 UKM_MY_DCDS ............................................... 477 Usage and Procedure Logging .... 40, 48, 76, 160
AJRW ..................................................................... 462 SE14 ......................................................................... 304 VKM1 ........................................................... 476–477 Usage data ...................................................... 418, 420
ASKB ...................................................................... 462 SE16 ........................................................................ 159 VKM4 .................................................................... 476 User acceptance testing (UAT) ................. 50, 188
ATC ........................................................ 89, 412, 431 SE20 ....................................................................... 389 ZWFI2 .................................................................... 429 Users
BP ........................................................................... 484 SE38 .............................................................. 348, 368 Transactional data ................................................ 470 for conversion ................................................... 225
CVI_COCKPIT .................................................... 449 SE80 ....................................................................... 433 Transparent tables ................................................ 283 lock before downtime .................................... 304
CVI_PRECHK ............................................. 449, 451 SE95 ........................................................................ 157 Transport directory .............................................. 320 unlock ................................................................... 349
DB02 ............................................................ 230, 262 SE95_UTIL ............................................................ 376 Transport landscape changes .......................... 335
DBACOCKPIT ..................................... 92, 301, 353 SFW5 ....................................................................... 451 Transport lock ........................................................ 288 V
FD31 ....................................................................... 476 SGEN ..................... 269–270, 280, 336, 338–339 Transport logs ........................................................ 322
FD32 ....................................................................... 476 SICF ......................................................................... 412 Transport management system (TMS) ........ 131 Variant save tool ................................................... 283
FIN_CORR_DISPLAY ....................................... 465 SICK ........................................................................ 334 Transport requests .................. 278, 372, 387, 483 Variants .................................................................... 282
FIN_CORR_RECONCILE ................................. 464 SLICENSE .................................................... 235, 237 imports ................................................................. 340 Version management ................................ 375, 388
GR55 ...................................................................... 462 SM13 ............................................................. 284, 303 register ................................................................. 385 Virtual Data Model (VDM) ................................... 27
KSU5 ...................................................................... 462 SM37 ......................... 88, 334–335, 350, 353, 355 SPDD ..................................................................... 292 Virtual machine (VM) ......................................... 280
KSV5 ...................................................................... 462 SM50 ...................................................................... 296 SPDD/SPAU ........................................................ 278 Visual Studio .......................................................... 126
MASS ..................................................................... 496 SM59 ...................................................................... 366 Transportation management system (TMS) ......
MB11 ............................................................. 162, 402 SM63 ...................................................................... 304 336 W
MD01 .................................................................... 493 SM66 ...................................................................... 352 Troubleshooting ................................................... 354
MDS_LOAD_COCKPIT ................................... 457 SMLT ...................................................................... 342 Windows .................................................................. 122
MDS_PPO2 ......................................................... 458 SNOTE ............................................... 156, 226, 276 U Workload Monitor .................................................. 49
ME12 ...................................................................... 500 SPAM ................................................. 217–218, 227
MIGO ................................................. 162, 402, 494 SPAU .... 51, 158, 278, 317, 362–363, 386–387, Unicode ............................................. 32, 84, 141, 152 X
OB52 ...................................................................... 461 389, 394 Universal Journal ............................... 458–459, 473
obsolete ............................................................... 446 SPAU_ENH ................... 278, 317, 362–363, 389 Unlock system ....................................................... 309 XPRA ............................................. 274, 314–315, 486
OKP1 ...................................................................... 461 SPDD .... 51, 157, 203, 278, 298, 362–363, 365, Unmigrated customers ...................................... 484 XPRAS_AIMMRG phase ..................................... 314
OMSL ..................................................................... 495 370, 373, 376, 385, 394 Unsupported operating systems .................... 121
PFCG ............................................................. 347, 411 SQLM .............................................................. 49, 439 Update requests .................................................... 284 Z
RZ03 ...................................................................... 334 SQLMD .................................................................. 440 Upgrade Dependency Analyzer ...................... 145
RZ04 ...................................................................... 304 SRTCM ................................................................... 437 Upgrade logs ........................................................... 320 Zero Downtime Option (ZDO) ................ 108, 120
RZ10 .............................................................. 241, 334 SRTCMD ...................................................... 437–438
RZ11 ..................................................... 241, 332, 334 ST02 ....................................................................... 352
RZ12 ............................................................. 337–339 ST03 ................................................................ 49, 439
S_ALR_87013611 ................................................ 462 ST03N ...................................................................... 48
SA38 ......................................... 88, 90, 98, 106, 418 ST05 ....................................................................... 438
SAINT ................................................. 217–218, 227 ST22 ........................................................................ 352
SAT ......................................................................... 439 STC01 ..................................................................... 410
SCC4 .......................................... 226, 306, 349, 367 STMS ......................................... 287, 336, 341, 349
SCI ....................................................... 404, 409, 431 SU01 ................................................... 226, 367, 411
536 537
First-hand knowledge.
Bert Vanstechelman is partner of and principal technical

consultant at Expertum, and the founder of Logos Consul-
ting, now a part of Expertum. He has more than 20 years of
SAP experience. Bert specializes in platform migrations, SAP
installations, release upgrades, SAP Business Warehouse,
SAP Supply Chain Management, SAP HANA, and OS/DB
migrations. Bert is an advisor for SAP Professional Journal, an
SAP Solution Manager Expert, and has written four other books for SAP PRESS.
Mark Mergaerts is a principal technical consultant at

Expertum and has more than 20 years of SAP experience.
His activities concentrate on system administration, data-
base management, performance, upgrades, and platform
and Unicode migrations. He has written four other books
for SAP PRESS.
Mark Mergaerts, Bert Vanstechelman

SAP S/4HANA System Conversion Guide
537 Pages, 2020, $89.95
ISBN 978-1-4932-1944-5 We hope you have enjoyed this reading sample. You may recommend
or pass it on to others, but only in its entirety, including all pages. This
www.sap-press.com/5035 reading sample and all its parts are protected by copyright law. All usa-
ge and exploitation rights are reserved by the author and the publisher.

Browse The Book: First-Hand Knowledge

Uploaded by

Copyright:

Available Formats

Browse The Book: First-Hand Knowledge

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

Browse The Book: First-Hand Knowledge

Uploaded by

Copyright:

Available Formats

First-hand knowledge.

Browse the Book

Mark Mergaerts, Bert Vanstechelman

Modification adjustment is the process of reconciling changes made by SAP to stan-

6.2.5 Log on to the Primary System

Figure 6.4 Transaction SPDD Selection Screen

Figure 6.3 Report RESCUE_OBJECTS_WITH_DATALOSS

6.3 Transaction SPDD Object List

6.5.1 General Procedure

Figure 6.8 Object without Differences

Figure 6.11 Adjustment in Data Dictionary

Figure 6.12 Object Status after Adjustment

Figure 6.10 Domain Needing Adjustment

CUSTFLD1 SAPFLD4 CUSTFLD1

CUSTFLD2 SAPFLD5 CUSTFLD2

Figure 6.19 Proposal Corresponds to New Version

6.5.4 Field Format Changes

Figure 6.21 Technical Settings

2. Choose Accept Proposal to confirm your decision.

Figure 6.24 Additional Transaction SPAU Tabs

Figure 6.27 Adjusting Enhancement

1 Introduction to SAP S/4HANA 25

1.1 New Possibilities, Features, and Functionality ...................................................... 25

1.2 SAP S/4HANA in the Cloud versus On-Premise ...................................................... 27

1.3 New Implementation, System Conversion, and Transformation

5.13 Post Go-Live ........................................................................................................................... 351 6.9 Summary ................................................................................................................................. 391

5.14 Troubleshooting .................................................................................................................. 354

8 Functional Conversion 443 Appendices 511

8.1 Business Partners ................................................................................................................ 444 A References ............................................................................................................................... 511

8.7 SAP Business Warehouse ................................................................................................. 504

8.8 Cleaning Up Obsolete Data after the Conversion ................................................ 506

8.9 Summary ................................................................................................................................. 509

A Action plan ..................................................... 170, 178

Bert Vanstechelman is partner of and principal technical

Mark Mergaerts is a principal technical consultant at

Mark Mergaerts, Bert Vanstechelman

You might also like