Completing the Digital Blueprint - with the System Scan

[ChristianeStrasserGler]

The SAP Business Transformation Center – Digital Blueprint provides data insights and supports scoping activities as part of a transformation process.

The Digital Blueprint consists of two elements:

• an Analysis File based on the SAP Readiness Check Capabilities
• a System Scan created via direct access to the source system.

Why

What is the difference, and why do we need those two approaches?

The SAP Readiness Check (UDP version) provides data insights related to a specific set of standard transformation objects, and the data usage in the organizational structure.  These transformation objects are the basis for scoping decisions (“scopable objects”). However, there are more tables in a system than those covered by the Readiness Check.

These tables are covered by the System Scan. It provides a list of all tables that are not covered in the SAP delivered Transformation Object content, which can be migrated from SAP ERP to S/4HANA:

• Customer-specific tables (Z* and Y*)
• Third Party tables (e.g., SAP Add-Ons)
• Dependent standard tables that are required independently of scoping decisions 

It provides information regarding the number of entries counted for each of the tables, to support the users’ scoping decision per table.

Wouldn’t it be possible to implement the UDP RC part into the System Scan?

💡 It would – technically – be an option to derive the information related to the transformation objects within the System Scan, too. However, this would limit the flexibility you have now with the offline approach in the Readiness Check, by manually uploading a file. Remember: With this approach, you can start scoping activities, e.g. in first workshops, without having the hurdle of setting up the system connectivity. 💡

 Note: It is possible to create a Digital Blueprint based on an Analysis File, without assigning a System Scan. However, to be able to confirm the Digital Blueprint and proceed to the Modeling phase, a System Scan is mandatory.

What

The System Scan functionality includes two applications,

• Manage System Scans, where you can create, execute, and monitor the status of a System Scan, and assign it to a Digital Blueprint
• Select Scanned Tables to perform and document scoping decisions per table.

How

Note: Before working with the System Scan Apps, you need to set-up the connectivity for the source system (see below, section prerequisites). But for now, let’s start with creating a system scan by accessing the related tile Manage System Scans on SAP Cloud ALM Launchpad:

In the app, simply press ‘Create new Scan’…

…fill out the required fields, and press create:

After creating a scan, some initial checks are performed, such as

• if the connection to the source system maintained correctly (see section ‘Prerequisites’ below)
• if the required minimum release is met,
• and if all prerequisite ABAP notes are implemented.

 Now the scan can be started (button top right corner); it will take a few minutes. By refreshing the screen, the list in section Scanned Tables will grow gradually; the Activity Log shows the single processing steps:

When finished, the result is displayed in section Scanned Tables. In our example, we see standard tables which are not included by the Readiness Check (because they are mandatory for the migration), as well as a long list of custom tables (Z*). As mentioned above, it would also be the spot where add-on tables and tables in partner name space would appear.

Currently, the result only contains the tables that are relevant for scoping decisions. Tables that are ‘not scopable’ are so far only visible in the Modeling App (in the Transformation Model and Transformation Model Version). However, there will be an update soon to also show auto-scoped tables that will be automatically put into scope (baseline tables) and transferred as part of the migration. This ensures consistency between Scoping and Modeling Apps, and it will help users to gain full transparency on the scope of migration.

Now you can assign this System Scan to your Digital Blueprint.

Next step is covered by the Select Scanned Tables app. It can be reached either via a tile on the Transition tab on the main page, or via ‘Related Apps’.

Same as in the Select Company Codes app, scoping decisions are supported by providing hints and information on the (total and relevant) data count. In this example, tables containing data have been de-scoped:

As this will be a conscious decision, you might want to document it in the detail screen for the table by using the Comment function.

 

Now you are basically done with the scoping of scanned tables, and you might want to set the status to ‘confirmed’ (mass edit or detail) to make it visible. This is not a mandatory step; however, you will receive a reminder (warning) in the Digital Blueprint.

With completing the scoping of Scanned Tables, the second element of the Digital Blueprint is covered. What is still missing, is the selection of Transformation Objects (TOs).

The current scope of the lean Selective Data Transformation covers the scoping based on Company Code level. This means, the set of transformation objects is given. This means you cannot de-scope TOs that have relevant data in the source system. However, there might be TOs for which no relevant data exist, i.e. it is not used in any of the company codes that are in scope. In this case, it is recommended to de-scope the ‘empty’ tables (tables without relevant data), as in this example:

As you can see, all TOs with a relevant data scope of zero are set out of scope here; for Material Ledger Cost Estimation data do exist – but not for the scoped company codes (0001, 1000 in this example). This can be verified in the detail screen for this object:

You might ask why you would do that, if it doesn’t reduce the data footprint, which is true. The reason is that by excluding these TOs, the transformation steps related to those tables are not required - which means this saves effort later in the preparation of the source and target system (see Manage Cycles app, step Preparation).

Now you are done with the scoping activities, and you can review the result in the Digital Blueprint Overview app:

Prerequisites

The System Scan is the first increment that provides – and requires - direct integration of SAP Business Transformation Center and the SAP ERP source system. This means, a connection from the SAP Cloud ALM tenant to the ERP source system needs to be established:

• A Cloud Connector must be configured
• The connection to the source system must be maintained in the Landscape Management Service

For a detailed description on how to set up the connectivity, please refer to the related section in Setup and Administration Guide in SAP Business Transformation Center online help: Setup and Administration Guide