Professional Documents
Culture Documents
WP02 ACT ReadinessCheck
WP02 ACT ReadinessCheck
April 2020
Version 3.0
10Steps2S4 – Readiness Check – Activity document
1 Introduction........................................................................................................................................3
2
10Steps2S4 – Readiness Check – Activity document
1 Introduction
The activities described in this document should be executed in your system in order to successfully
complete the work-package.
The purpose of this document is to collect these activities using SAP Readiness Check 2.0 for S/4HANA
for your reference with the scope of document all the steps you should perform during a real conversion
project.
The results are consolidated in an interactive dashboard for internal or for SAP communication. SAP
Readiness Check for SAP S/4HANA provides a pre-conversion overview, useful for identifying current
system landscape preparation steps, well in advance of your SAP S/4HANA system conversion project
start date.
The SAP Readiness Check for SAP S/4HANA evaluates specific areas and provides detailed information
about the results. The areas are as follows:
3
10Steps2S4 – Readiness Check – Activity document
4
10Steps2S4 – Readiness Check – Activity document
Choose the managed system in which you want to run the custom code analysis, execute report
RC_COLLECT_ANALYSIS_DATA in transaction SA38 and download the custom code analysis data as
ZIP file.
1. Login to the source system via Sap GUI. System ID is K<XX> where XX is your group number
(e.g. K01, K02, etc.)
2. Call transaction SA38
3. Specify report RC_COLLECT_ANALYSIS_DATA in the field Program
4. Click icon to execute
5. Leave the default options and click on icon to execute
6. Check the progress of the jobs in transaction sm37: RC_COLLECT_ANALYSIS_DATA will trigger
further background jobs based on the options you’ve selected. To ensure the data was collected
properly, you must check the job logs:
• RC_COLLECT_ANALYSIS_DATA Main Job from RC_COLLECT_ANALYSIS_DATA
• TMW_RC_BPA_DATA_COLL for BPA data collection
• TMW_RC_HANAS_DATA_COLL and /SDF/HDB_SIZING_SM for HANA Sizing data
collection
• TMW_RC_DVM_DATA_COLL, BP_APPLICATION_ANALYSIS_01, DANA_ANALYSIS
and TAANA_ANALYSIS for DVM data collection
• TMW_RC_SITEM_DATA_COLL for Simplification Item Check data collection
7. Select the location of the resulting ZIP file in the local terminal server folders and click Save to
continue – you should rename the file e.g. adding an “a” to the end, if you are running and
extracting the Simplification Item check on the same day, it would become the same name
RC2AnalysisDataK0020191119a.zip
5
10Steps2S4 – Readiness Check – Activity document
8. Wait until the extraction is completed and then check the file in the terminal server.
In order to identify all simplifications that apply to your SAP system, you can run the Simplification Item
Checks (SI-Checks). The results will tell you all affected Simplification Items and ensures your system is
in a consistent state so the system conversion or upgrade will succeed. After doing all the necessary
preparations, execute report /SDF/RC_START_CHECK in transaction SA38.
For the most accurate results please execute the report in client 000.
The execution of this report is also covered in the Readiness Check activity document, but with a different
goal.
In this document we will concentrate on how to include SCI result into the Readiness Check report.
1. Login to the source system via Sap GUI. System ID is K<XX> where XX is your group number
(e.g. K01, K02, etc.), client 000.
2. Call transaction SA38
3. Specify report /SDF/RC_START_CHECK in the field Program
4. Click icon to execute
6
10Steps2S4 – Readiness Check – Activity document
Choose option “New check as a Background Job” and click on icon to execute
You can ignore the warning regarding SAP note 2502552 is being out-of-date if it’s the most
current – just check the installed version with the most current on the ONE Support Portal (the
version above is the most current – seems to be a bug…). Generally, it is recommended to use
always the latest available versions of these 2 notes, until the freeze phase of your project.
Right before the productive conversion, update the catalog with the latest available version from
SAP (not needed in your exercise within 10Steps2S4):
7
10Steps2S4 – Readiness Check – Activity document
6. When ready, check the results with “Display Last Check Result” running report
/SDF/RC_START_CHECK in transaction SA38
8
10Steps2S4 – Readiness Check – Activity document
13. Select the location of the resulting ZIP file in the local terminal server folders and click Save to
continue
IMPORTANT: if you download this file on the same day as the main readiness check file, don’t
forget to rename it (e.g. add a “b” to the end like RC2AnalysisDataK0020191119b.zip to not to
overwrite the other one
14. Wait until the extraction is completed and then check the file in the terminal server.
9
10Steps2S4 – Readiness Check – Activity document
To have ATC check data included in the Readiness Check, you have to download the results from the
system where ATC is installed.
https://rc.cfapps.eu10.hana.ondemand.com
2. [IMPORTANT] Login using the user and password published in the JAM group in the folder
“WP02 – Preparation phase” in the document called “Login information for SAP Readiness
Check”.
3. Click on the button to create a new analysis with the manual upload
10
10Steps2S4 – Readiness Check – Activity document
11
10Steps2S4 – Readiness Check – Activity document
5. Press to continue
6. Use the refresh button to update the screen and wait until the status switch from “In Preparation”
to “Ready”
12
10Steps2S4 – Readiness Check – Activity document
7. Once status is “Ready” click on the analysis name you just created to access to the details
13
10Steps2S4 – Readiness Check – Activity document
Here you can check and see all relevant simplification items.
14
10Steps2S4 – Readiness Check – Activity document
Clicking on an item will open a new browser tab or window and bring you to the Simplification Item
Catalog for further details.
15
10Steps2S4 – Readiness Check – Activity document
16
10Steps2S4 – Readiness Check – Activity document
17
10Steps2S4 – Readiness Check – Activity document
You also can add comments for your reference or if you are working in a group to share your
observations.
18
10Steps2S4 – Readiness Check – Activity document
4.6 Sizing
Here you find information about the total sizing estimation for SAP S/4HANA. The values on the tile
reflect the estimated size requirements for the initial installation (Initial target size, ITS) of SAP S/4HANA,
based on the data in your system.
The screen consists 3 main areas, “SAP S/4HANA Sizing Simulation” (Here you can change the
influencing factors to have an estimation about the influence of future data growth, data volume reduction
and new functionality), “SAP S/4HANA Sizing” “with further details on the initial size and top tables) and
Data Volume Management (see further details below).
19
10Steps2S4 – Readiness Check – Activity document
After changing the input for the selected area, push the “Add” button to see the results reflected in the
diagram.
20
10Steps2S4 – Readiness Check – Activity document
This section shows the size of your archiving potential based on the top 30 database tables. In the bar
chart view, one chart shows you, for every document type, how many gigabytes can be archived in
relation to its total size in your source system. The other bar chart shows how much this equals in percent
per document type. The bar charts shows up to ten document types. Switch to the table view to see all
analysed objects.
By default, the residence time is set to 12 months. You can also choose to see the results for 24 months.
It is recommended that you archive as much data as possible before migrating to SAP S/4HANA in order
to reduce the amount of memory that will be consumed in the SAP S/4HANA environment.
NOTE: In our system there is no data since the overall size of the tables is small so the DVM can not find
any optimizations.
You can request a more detailed analysis of your business process data KPIs using the Next Generation
Business Scenario Recommendations (see also SAP note 2758146).
21
10Steps2S4 – Readiness Check – Activity document
4.8 Integration
This section gives a first indication of how the SAP S/4HANA transition will impact the current integration
setup. The checks cover the integration technologies BW extractors and IDoc interfaces.
This section lists all SAP BW Extractors in your ERP system and tells you whether they can still be used
in SAP S/4HANA. For example, it shows if an extractor is no longer available, was replaced by an
alternative, or only works with restrictions due to simplifications in the S/4HANA application. Simplification
items are listed and can be accessed for more detailed information about changes in SAP S/4HANA that
are relevant for a specific extractor.
• DS Working
o No Restrictions: DataSource is available with SAP S/4HANA and works without any
restrictions compared to SAP ERP.
o Restrictions: DataSource is available with SAP S/4HANA but works with noteworthy
restrictions. For example, not all fields are available.
o Regeneration of Extractor: Due to the nature of the extractors, being generated in the
system, we cannot whitelist those in general. Experience so far shows that they should
be working without restrictions.
• DS Not Working
o Alternative Exists: DataSource does not work with SAP S/4HANA, but an alternative is
available, such as a new extractor or CDS view.
o No Alternative Exists: DataSource does not work with SAP S/4HANA and there is no
alternative.
o Alternative Planned: DataSource does not work with SAP S/4HANA, but there will be an
equivalent available on roadmap for future release.
• DS Obsolete: DataSource is obsolete - legacy extractors
The analysis covers all BI content extractors available up to ERP 6.0 EHP8.
22
10Steps2S4 – Readiness Check – Activity document
This section lists the active and inactive IDoc integration scenarios configured in your source SAP ERP
6.0 system. The extracted interfaces are compared against the SAP S/4HANA RFC-enabled function
module blacklist. This list contains remote-enabled function modules that will generate a system dump
when called in SAP S/4HANA. The caller program extracted for each interface from the analyzed system
is used for the comparison.
NOTE: In our system there is no data since no IDoc interfaces are being used.
23
10Steps2S4 – Readiness Check – Activity document
24
10Steps2S4 – Readiness Check – Activity document
25