Conversion HANA

Converting to SAP S/4HANA: Using the
Maintenance Planner for a System Conversion Stack
1
CONVERTING TO SAP S/4HANA: USING THE MAINTENANCE PLANNER FOR A SYSTEM CONVERSION STACK
You use the Maintenance Planner to plan a system maintenance, a new

system installation, or a system conversion.
Would you like to know more about how to use the Maintenance Planner
for a system conversion?
If so, follow this interactive tutorial.
Note -: This tutorial shows the selection for SAP S/4HANA 1511. The
steps for the newer versions of SAP S/HANA are similar.
2
(1) To start the app, choose the Plan for SAP S/4HANA tile.
At first on the Overview screen, you choose your path to SAP S/4HANA.
3
(2) Select Plan an SAP S/4HANA conversion on an existing system.
(3) Choose Next.
4
On the Select Backend System screen, you enter the Back-End Server
Selection as the system that is converted to SAP S/4HANA.
(4) The existing system is S2Y(ABAP).

To find that value quickly, enter S2Y.
5
(5) Select S2Y(ABAP).
(6) To continue with the next step, choose Next.
6
On the Select Additional Systems screen, you define the front-end server
for the FIORI applications.
(7) Select Co-deployed with Backend.
7
(8) Choose the Target Stack list.
(9) Select 02 (05/2016).
8
A list of the Target Product Instances displays.
(10) Choose Next.
9
The Summary shows the result of the preparation checks, like Add-On
support.
(11) Choose Continue Planning.
10
On the Define Change screen, you can choose to install additional

software.
(12) To select the files for the plan, choose Next.
11
In the Select Files step, you choose the required kernel files for your
operating system.
(13) Choose Confirm Selection.
12
The overview step allows you to review the selected files.
(14) To continue with the download of files, choose Next.
13
(15) Choose Download Stack XML.
(16) To save the file, choose OK.
14
(17) Choose Push to Download Basket.
All the selected files are added to the download basket.
15
(18) To complete the transaction, choose Next.
You can save the Maintenance Plan document for later reference.
16
(19) Choose Save.
(20) Choose Set to Complete.
17
(21) Choose Yes.
You have created the Maintenance Plan and completed the transaction.
This concludes the interactive tutorial.
18
Converting to SAP S/4HANA: Custom Code
Migration
1
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
The tool ABAP Test Cockpit (ATC), can be used to analyze the impact of
conversion to SAP S/4HANA, on custom code. ATC facilitates the
adaption of the custom code to SAP S/4HANA.
Would you like to learn about how you can use the ABAP test Cockpit to
manage your custom code activities related to SAP S/4HANA conversion?
If so, follow this interactive tutorial.
Note -: The described steps for the ATC must be performed in an

additional SAP system with AS ABAP 7.51 or above.
2
(1) Enter ATC and press Enter.
(2) Choose Execute.
3
The ABAP Test Cockpit opens.
Here you can find all the activities that can help you with analyzing your
custom code.
(3) To schedule a new ATC check, double-click Schedule Run.
4
(4) To schedule the job that checks the custom code of the source system, you have to
create a run series, with a Code Inspector Check Variant. The Code Inspector Check
Variant determines the checking criteria.
In this demo, the run series S4HANA_READINESS with the Code Inspector Check Variant
S4HANA_READINESS_REMOTE is already created. Select it.
(5) Choose Schedule.
5
(6) Choose Execute.
The job scheduling is a success.
6
(7) Choose Back.
(8) To view the details of the ATC checks, double-click Monitor and Control Runs.
7
To display the log of the ATC check that you previously scheduled, you
can enter it as the run series.
In this demo, the run series S4HANA_READINESS is entered for you.
(9) Choose Execute.
8
The ATC Run Monitor screen opens.
Here you can find the list of ATC checks scheduled and other details such
as State, Duration, Run Series.
(10) To see the results of an ATC check, select it.
9
(11) Choose Result.
Here, you can view all the issues in the custom code that were collected
during the ATC check. The system also lists the Object Names where the
error was found. These objects have to be adjusted for SAP S/4HANA
conversion.
10
(12) To view additional information about an issue, double-click its Check Title cell.
In this demo, double-click the Check Title cell for the first issue.
11
The details of the error displays. Here you can view the details of
the issue such as the Priority of the error, the program name and the line
number where the error was found.
In this demo, there is a priority 1 error in line number 302 of the custom
program ZENGCHG0. In the SAP S/4HANA the field length for MATNR is
40 but the program has a field length of 18.
(13) To navigate to the location in the code where error occurred, choose Display Object.
12
Here you can see that the error occurred in the code line 302 of the
program ZENGCHG0.
Note: From SAP NetWeaver 7.51 and higher, you can navigate to your
source system via RFC connection and adjust your code from ATC.
13
(14) To navigate to the declaration of the internal table type of the variable rtab, double-
click it.
Here, you can you see that in the internal table type declaration, the
length of the field MATNR is 18 characters.
The ATC check resulted in an error because the MATNR field length in
SAP S/4HANA is 40 characters.
14
(15) Choose Exit.
15
Converting to SAP S/4HANA: Stage 1 - Starting SUM
1
CONVERTING TO SAP S/4HANA: STAGE 1 - STARTING SUM
The Software Update Manager (SUM) is used to convert SAP Business

Suite systems to SAP S/4HANA on-premise systems. It supports various
processes, such as:
· Performing a release upgrade
· Installing enhancement packages
· Applying support package stacks
· Installing add-ons or updating single components.
Would you like to know more about how to use SUM to convert to SAP
S/4HANA? If so follow this interactive tutorial.
Note -: For performing an SAP S/4HANA conversion, SUM 2.0 must be

used. This recording shows SUM 1.0 - the steps using SUM 2.0 are
similar.
2
(1) In the STACKFILE field, you can specify the path to the stack.xml. The stack.xml
contains the information about your roadmap.
Note: You use the Maintenance Planner to plan for your system conversion and to
generate the stack XML. This is covered in another demo.
In this demo, enter /usr/sap/S2Y/stack/Stack.xml and press Enter.
3
(2) Choose Next.
The SUM checks the download directory for the required software
archives.
4
Here you can enter the password for the DDIC user client 000 of the
source system. The SUM works with this user to perform all necessary
actions, such as execution of batch jobs and reports, for example, pre-
transition checks.
In this demo the password is already entered for you.
(3) To proceed, choose Next.
5
6
Converting to SAP S/4HANA: Stage 2 - Setting
HANA Parameters in SUM
Learn how to:
 Set the parameters for SAP HANA database in SUM
Duration: 2:00 Min
1
CONVERTING TO SAP S/4HANA: STAGE 2 - SETTING HANA PARAMETERS IN SUM
This is the second part of the conversion to SAP S/4HANA using the
Software Update Manager (SUM). In this demo, you will be guided
through the steps related to the database migration.
Would you like to know more about the steps related to the database
migration? If so, follow this interactive demo.
2
Here you set the required parameters for the SAP HANA database such
as:
 hostname of the target database (SAP HANA database)
 SID of the database
 instance number
 path to the license file of the target system generated on the SAP
Support Portal.
In this demo, these parameters are already set for you.
3
Here you can enter the password for the target database user 'SYSTEM'.
In this demo, the password is entered for you.
4
Here you can enter the password for the DB user 'DBACOCKPIT' and
confirm it.
In this demo, this is entered for you.
5
Here you can enter the password for the DB user 'SAPS2Y' and confirm
it. SAPS2Y is the user for the new schema on the target database and
is used to migrate database tables.
In this demo, the password and its confirmation is entered for you.
6
This concludes the interactive demo.
7
Converting to SAP S/4HANA: Stage 3 - Source
System Downtime
1
CONVERTING TO SAP S/4HANA: STAGE 3 - SOURCE SYSTEM DOWNTIME
In the preprocessing phase, the source system downtime begins. In this

step, the database migration and data conversion takes place.
Would you like to know more about this? If so, follow this interactive
tutorial.
Note -: For performing an SAP S/4HANA conversion, SUM 2.0 must be

used. This recording shows SUM 1.0 - the steps using SUM 2.0 are
similar.
2
When the uptime phase of the source system ends, it means all checks
passed successfully and the shadow system is successfully created. Now
in the preprocessing phase, the source system is available.
In the next phases the source system is not available as it is in downtime.

During downtime, the database migration and data conversion takes
place. This is covered in the demos ‘Converting to SAP S/4HANA: Stage
4 - Migration Cockpit’ and ‘Converting to SAP S/4HANA: Stage 5 - Data
Conversion’.
3
(1) To check the status of the source system, select System.
(2) Select Status.
4
The System: Status dialog window opens. Here you can see the source
system release. The source system DB is ANYDB.
Note: Checking the status of the source system is an optional step. It is

used to show the source system is not upgraded to SAP S/4HANA during
the SUM uptime. In a subsequent demo, you can see the source system
status after the SUM downtime and conversion to SAP S/4HANA.
5
(3) To view the installed components and versions, choose Components.
(4) Choose Installed Product Versions.
6
Here you can see the source system release is SAP ERP 6.0 EHP6.
Note: Checking the source system release is an optional step. It is used

to show the source system is not upgraded to SAP S/4HANA during the
SUM uptime. In a subsequent demo, you can see the source
system release after the conversion to SAP S/4HANA.
(5) To close the Installed Software dialog window, choose OK.
7
(6) To close the System Status dialog window, choose OK.
(7) To display the stock overview, enter MMBE in the command box and choose Execute.
Note: This is an optional step and is used to show the source system functions correctly
before the downtime begins.
8
(8) The transaction for Stock Overview displays.
To display the existing stock for material 10050160, enter 10050160 in the Material field
and press Enter.
(9) To display the stock for the material, choose Execute.
9
The stock details for the material 10050160 display. Here you can view
the details, such as stock available for unrestricted use, blocked stock,
and so on.
Note: Here you see the Stock Overview transaction before the conversion
to SAP S/4HANA. In a subsequent demo, you can see the Fiori App for
stock overview that is installed after the conversion.
10
(10) Choose Next.
The SUM displays a message indicating it is ready to enter the downtime.

Here you can save the current state and backup the source system before
the downtime starts.
11
The source system downtime starts for the conversion to SAP S/4HANA.
12
Converting to SAP S/4HANA: Stage 4 - Monitoring
the Migration Cockpit
Learn how to:
 Monitor the Database Migration Option (DMO) of SUM during SAP

S/4HANA Conversion
Duration: 2:00 Min
1
CONVERTING TO SAP S/4HANA: STAGE 4 - MONITORING THE MIGRATION COCKPIT
In the execution phase, the source database is migrated to the SAP

HANA database. SAP S/4HANA runs on the SAP HANA database.
The conversion process consists of the Database Migration Option
(DMO), which migrates any kind of database to the SAP HANA database.
Would you like to know more about how to monitor the Database
Migration Option (DMO) of SUM during SAP S/4HANA conversion? If so,
follow this interactive demo.
2
(1) In the database migration occurs during the SUM phase EU_CLONE_MIG_DT_RUN.
You can monitor the database migration in the Migration Cockpit.
To open the Migration Cockpit, choose More.
(2) Select Utilities.
3
In the Software Update Manager Utilities window opens,you see

the overview of the SUM utilities and can find information about the
current SUM run such as SUM Parameters and DMO information.
(3) To monitor the database migration in the Migration Cockpit, choose DMO Migration
Control Center.
4
(4) To view a graphical overview of the database migration, choose Charts Control Center.
In the Realtime Migration Graph section, you can see the number of
R3load processes that performs the data migration. In this demo, there
are about twenty R3load processes.
5
The SAP HANA Server Load section, provides information about server
capability, such as memory usage and CPU load.
(5) Drag.
(6) Drop.
6
The Process Buckets section shows details of each R3load process.
Here you can monitor the status of the R3load processes. You can also
restart any of the processes if that fails.
(7) To view the latest status of each process, choose Refresh.
7
The latest status of the process buckets appears.
(8) Drag.
(9) Drop.
8
Depending on the server capability, you can increase the number of

R3load processes in the DMO Migration Control Center.
(10) To increase the number of R3load processes, drag the slider.

(11) Drop the slider.
9
The graphical overview is refreshed and now shows the increased

number of R3load processes.
(12) Close the SUM Utilities window.
10
11
Converting to SAP S/4HANA: Stage 5 - Monitoring
SAP HANA Studio
1
CONVERTING TO SAP S/4HANA: STAGE 5 - MONITORING SAP HANA STUDIO
In SAP S/4HANA the content of some tables is converted to the new data
model. One such data model is the new table MATDOC, which is filled
with data from tables from the logistics area.
Would you like to know more about monitoring the data conversion? If so,
follow this interactive tutorial.
Note -: The name of the SAP HANA database schema should be

SAPABAPn, for example SAPABAP1.
2
During downtime, when SUM executes the phase PARRUN_MKPF1_S4,

you can monitor the data conversion of table MATDOC happens.
(1) To monitor the data conversion, you login in to the SAP HANA Studio with the SAPSID
user. You enter this in the demo 'Converting to SAP S/4HANA: Stage 2 - Setting HANA
Parameters in SUM'. In this demo, you are already logged in to the SAP HANA Studio.
3
Here you can monitor the database tables of the target system. In the current SUM phase
this will be filled with data. In this demo, we monitor the database table MATDOC in the
target system S2Y.
To navigate to the database tables, in the navigation panel, expand the folder
S2Y(SAPS2Y) corresponding to the target system.
(2) Expand Catalog.
4
(3) In the Tables folder, you can view all the database tables in the selected system.
To view the operations that you can perform on tables, right-click the folder.
(4) To display tables with names containing a pattern, select Filters.
(5) Here you can enter the pattern for database table names.
5
Enter MATDOC and choose OK.
(6) The filter pattern 'MATDOC' is now set. To view all the database tables containing this
pattern, expand the Tables folder.
(7) All database tables with names containing the pattern 'MATDOC' are shown.
6
You can select a table and view all the operations that can be performed on it. In this
demo, select MATDOC.
(8) To display the data, choose Open Content.
The structure and the content of the table MATDOC displays. Note that
there is no data in the table.
7
(9) To populate the table with the latest data, choose Refresh.
The MATDOC table is populated with data from tables in the logistics
area.
8
You can convert other database tables using the same approach.
9
Converting to SAP S/4HANA: Stage 6 - Checking
the table ACDOCA
1
CONVERTING TO SAP S/4HANA: STAGE 6 - CHECKING THE TABLE ACDOCA
In the postprocessing phase REQUPFINAL, the conversion process in

SUM is almost done. However, some additional configurations
steps remain, like SAP S/4HANA Finance configuration.
ACDOCA is a new database table in the financial area and is a part of the
new data model in S/4HANA. However, in the postprocessing
REQUPFINAL phase it is empty which means that the SAP S/4HANA
Finance activities have to be performed in the system after the SUM run
to fill ACDOCA with data.
Would you like to know more about how to check if the ACDOCA table is
empty, to ensure that everything is as it should be at this point and you
can proceed? If so, follow this interactive demo.
2
(1) To navigate to the database tables, in the navigation panel, expand the folder
S2Y(SAPS2Y), which corresponds to the target system.
(2) Expand Catalog.
3
(3) Right-click the Tables folder.
(4) Choose Filters.
4
(5) Enter the filter pattern MATDOC and choose OK.
(6) Expand Tables.
5
(7) Right-click the table MATDOC.
(8) Select Open Content.
6
In the demo "Converting to SAP S/4HANA: Stage 5 - Monitoring HANA

Studio", we see that the database table MATDOC was filled with data in a
prior phase of the conversion process.
Here, in this phase of the conversion, you can verify that MATDOC is not
empty, but still contains the previously populated data.
(9) Right-click the Tables folder.
7
(10) Choose Filters.
(11) Enter the filter pattern ACDOCA and choose OK.
8
(12) Right click the table ACDOCA.
(13) To view the contents of the database, choose Open Content.
9
Here, you can see that the table is empty.
You can now perform the manual tasks to complete the conversion
process.
10
Converting to SAP S/4HANA: Stage 7 - Examining
Fiori Apps after the Conversion
1
CONVERTING TO SAP S/4HANA: STAGE 7 - EXAMINING FIORI APPS AFTER THE CONVERSION
After the conversion to SAP S/4HANA, you can check the SAP S/4HANA
system to see if the conversion went well. In addition, your daily business
can now be performed with the new Fiori apps.
Would you like to know more about how to examine the SAP S/4HANA
system and explore the Fiori apps? If so, follow this interactive demo.
(1) To view the software components installed in the SAP system, choose System.
2
(2) Select Status.
(3) The System: Status window displays.
To view all the software components and the versions installed in the system, choose
Display.
3
(4) Select the Installed Product Versions tab.
Here, you can see that the system is now converted to SAP S/4HANA
1610 and that Fiori is also installed.
4
(5) To close the window, choose OK.
(6) To close the window, choose OK.
5
After you have converted to S/4HANA conversion and performed

additional manual activities like SAP S/4HANA Finance configuration and
Fiori configuration, the system can be used in daily business.
(7) In this demo, we use Fiori Apps for analyzing the inventory.
To begin analyzing the inventory, select the Inventory Turnover Analysis tile.
6
(8) To select a start date, choose the date picker.
(9) Here, you can select a start date.
For this demo, select 01-Feb-2017.
7
(10) Enter 2020 in the Plant field.
(11) Select Plant Production -Orlando with plant ID 2020.
8
(12) Choose Go.
The inventory turnover for all materials in plant 2020, display in a graph.
9
(13) Here you see that one material has a large value and want to see if you can optimize
the inventory. To view more details about the material, select it.
The material 10050160 is selected.
10
(14) You can select another material to compare with the material 10050160.
In this demo, select material 10050150.
(15) To begin comparing the two materials, choose Show Selected Materials.
11
The inventory information for the two materials display in the Selected
Material pane.
(16) You can display the inventory information for a material by selecting it in the Selected
Materials pane.
In this demo, select the material 10050160.
12
The inventory information for the material 10050160 displays.
Note: In the demo "Converting to SAP S/4HANA: Stage 3 - Source

System Downtime", we review the material 10050160 with the transaction
MMBE, before the downtime starts.
(17) Choose Related Apps.
13
(18) Select Stock - Single Material.
14
The stock information for material 10050160 displays according to

Plant/Storage Location.
Note: In the demo "Converting to SAP S/4HANA: Stage 3 - Source

System Downtime", we see the stock information for material
10050160 by using the transaction MMBE. The content displayed in the
Fiori app is the same as the content shown in that transaction.
Here we can also see the graphical overview of the stock history for this
material in each plant. This view was not possible in the old transaction
MMBE.
15
(19) You can view the stock information for a plant or storage location by selecting it.
Here, select the Plant 2020.
(20) Choose the Stock History for the plant 2020.
16
The stock history for material 10050160 in the plant 2020 displays.
(21) Choose Close.
17
(22) Choose Material Documents Overview.
(23) Choose Go.
18
All material documents for the selected material and selected plant
display.
(24) Choose material document 490107305.
19
The inventory information for the material 10050160 displays.
(25) Choose Document Flow.
20
Here, you can see the flow of the business documents for the material
document 490107305.
(26) Choose Home.
21
22

Conversion HANA

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Conversion HANA

Uploaded by

Copyright:

Available Formats

Converting to SAP S/4HANA: Using the

Maintenance Planner for a System Conversion Stack

You use the Maintenance Planner to plan a system maintenance, a new

If so, follow this interactive tutorial.

(2) Select Plan an SAP S/4HANA conversion on an existing system.

(3) Choose Next.

(4) The existing system is S2Y(ABAP).

(5) Select S2Y(ABAP).

(6) To continue with the next step, choose Next.

(7) Select Co-deployed with Backend.

(8) Choose the Target Stack list.

(9) Select 02 (05/2016).

A list of the Target Product Instances displays.

(10) Choose Next.

(11) Choose Continue Planning.

On the Define Change screen, you can choose to install additional

(12) To select the files for the plan, choose Next.

(13) Choose Confirm Selection.

The overview step allows you to review the selected files.

(14) To continue with the download of files, choose Next.

(15) Choose Download Stack XML.

(16) To save the file, choose OK.

(17) Choose Push to Download Basket.

All the selected files are added to the download basket.

(18) To complete the transaction, choose Next.

(19) Choose Save.

(20) Choose Set to Complete.

(21) Choose Yes.

This concludes the interactive tutorial.

Note -: The described steps for the ATC must be performed in an

(1) Enter ATC and press Enter.

(2) Choose Execute.

The ABAP Test Cockpit opens.

(3) To schedule a new ATC check, double-click Schedule Run.

(5) Choose Schedule.

(6) Choose Execute.

The job scheduling is a success.

(7) Choose Back.

In this demo, the run series S4HANA_READINESS is entered for you.

(9) Choose Execute.

The ATC Run Monitor screen opens.

(10) To see the results of an ATC check, select it.

(11) Choose Result.

(15) Choose Exit.

This concludes the interactive tutorial.

The Software Update Manager (SUM) is used to convert SAP Business

Note -: For performing an SAP S/4HANA conversion, SUM 2.0 must be

In this demo, enter /usr/sap/S2Y/stack/Stack.xml and press Enter.

(2) Choose Next.

In this demo the password is already entered for you.

(3) To proceed, choose Next.

This concludes the interactive tutorial.

Learn how to:

 Set the parameters for SAP HANA database in SUM

Duration: 2:00 Min

In this demo, these parameters are already set for you.

(1) To proceed, choose Next.

In this demo, the password is entered for you.

(2) To proceed, choose Next.

In this demo, this is entered for you.

(3) To proceed, choose Next.

(4) To proceed, choose Next.

This concludes the interactive demo.

In the preprocessing phase, the source system downtime begins. In this