Exploring the Source ECC System and Scoping Decisions

Start your business transformation journey by analyzing the data from your source SAP ECC system, creating a digital blueprint and defining the scope of the data to be migrated.

• Upload and manage the results of analyses.
• Scan and select custom tables.
• Create and manage digital blueprint.
• Scope the standard SAP ECC content.
• Get an overview of your digital blueprint with an interactive dashboard.

In the Manage Analysis Files app, you can upload and manage analysis files exported from the source SAP ECC system.

SAP Business Transformation Center requires source data which it then migrates to a target system. The following methods of gathering data for migration are currently available:

• By uploading an analysis file with data extracted from the source system.
• By running a system scan on the source system.

An analysis file is used to create an analysis, which is then associated with a digital blueprint so that the data it contains can be scoped and migrated.

First, you have to extract the analysis file from the source SAP ECC system according to the instructions in the SAP Note 3275056.

In detail, the following options are available:

• Upload and save the analysis file.
• Edit the title of the analysis file.
• Edit the note you saved with the analysis file, or add a new note to an already existing file.
• Review the data identified in SAP ECC and included in the analysis file:
  • Company codes.
  • Transformation objects.
  • Human Capital Management (HCM) data.
• Check if the analysis file is associated with any digital blueprints.
• Export the analysis file into a spreadsheet.

You can upload, edit, and delete analysis files.

Watch this video to see how to upload and manage analysis files.

To delete an analysis file from the system:

1. Choose an analysis from the list and open its detail page.
2. Select Delete and confirm the deletion.

The digital blueprint helps customers and partners define the migration and transformation scope for transitioning from SAP ERP Central Component (SAP ECC) to SAP S/4HANA. It provides data-driven guidance and recommendations for decision-making roles, architects, and subject matter experts. Included in SAP Cloud Service subscriptions and SAP Enterprise Support, it offers actionable insights into business data and supports data scope workshops with solution architects or data lead roles at consulting partners. The result is a data specification documentation ("blueprint") that can serve as a basis for migration. Enhancements to the SAP Business Transformation Center will be delivered continuously after general availability and be provisioned according to SAP´s cloud deployment model.

In the Manage Digital Blueprints app, you can create a digital blueprint based on a previously uploaded analysis file.

The digital blueprint is the central repository of technical and business information related to your data transformation project. This app allows you to manage your digital blueprints. In detail, the following options are available:

• Create, edit, and delete the digital blueprints.
• Create copies of existing digital blueprints.
• Define digital blueprint statuses.
• View technical and business details about the digital blueprints.
• Extract digital blueprint data to a PDF file.

You can upload, manage, confirm, and delete digital blueprints.

A digital blueprint is a key artifact of the data migration process. Using a digital blueprint, you assemble data from different sources (analysis files, system scans), put it through the scoping process, and then use it in your business transformation.

Watch this video to see how to create, edit, copy, and delete a digital blueprint.

Watch this video to learn how to apply time slice to your digital blueprint.

The Transition Readiness section lists various activities included in preparing a digital blueprint for data migration.

You can review this section as a checklist of the scoping process steps that may be preventing you from confirming the digital blueprint and proceeding with your data migration.

Note the following severity levels:

• Warning: This does not block the confirmation of the digital blueprint or the further steps of the migration process, but it may have a negative impact on the result of your data transformation. You can confirm the digital blueprint and continue the transformation process at your discretion.
• Error: This is required for the confirmation of the digital blueprint. Until it is done, you cannot confirm the digital blueprint and proceed.

The Details column contains a description of the issue, and the Application column contains the link so that you can navigate to the necessary app and complete the required steps.

Transition readiness information is also displayed in the confirmation pop-up when confirming a digital blueprint.

Applying a time slice allows you to selectively exclude data before a defined fiscal year from the scope of your digital blueprint.

Source systems often contain a long history of data, which can lead to long migration runtimes and a high number of errors or inconsistencies in the post-processing phase (for example, SFIN conversion). In many cases, this historical data is no longer necessary for operational, reporting, or auditing purposes.

The Lean Selective Data Transition SAP ECC to SAP S/4HANA scenario provided with SAP Business Transformation Center allows you to selectively exclude data related to specific organizational units (company codes) from your migration project. The time-slice solution pattern offers the additional option of excluding data before a certain date, which reduces the system size even further.

This data reduction often means you can avoid additional memory extensions and reduce the risks associated with bringing along old and irrelevant data. It not only simplifies the migration process but also ensures a more relevant and valuable dataset at the end of the migration.

The time-slice solution pattern uses a specific key date that determines which data is migrated and which is left behind. Transactional data created before the key date is not migrated, unless it is still in open status on the key date. All master data is migrated independently of the time slice, and transactional data created after the key date is also migrated.

The key date is always the start date of a fiscal year. The fiscal year can be different from the calendar year and is associated with the fiscal year variant.

To apply a time slice, you just need to select the fiscal year after which data should be included in the migration. The key date is the first day of the selected fiscal year, as derived from the fiscal-year variants of all the company codes that are set as In Scope for the digital blueprint.

After applying a time slice, the time-slice related filters are applied to all supported transformation objects in the modeling phase.

More specifically, the following data is migrated:

• All master data is migrated by default, even master data that's time-dependent and is dated before the key date of the time slice.
• Transactional data that is dated after the key date of the time slice.
• Transactional data that is in open status on the key date of the time slice. This could be, for example, transactional data from a Financial Accounting (FI) document with a posting date before the time-slice key date, but with a clearing date that is after the time-slice key date.

All transactional data related to standard transformation objects that come from SAP applications that aren't within the scope of the time-slice solution pattern. Time slice is supported for FI and Controlling (CO) applications. Transactional data that doesn't come from FI and CO applications is migrated, independently of the time slice. The same is the case for all custom transformation objects.

Before applying the time-slice solution pattern, be aware of the following constraints:

• The fiscal-year variant that is currently assigned to a company code (table <T001>  and field <PERIV>) reflects the correct period definition for all fiscal years. If this is not the case, the key date for the time-slice start cannot be determined correctly. This is even more important when a change of the fiscal year has been applied in the past.
• Document reversals might not be possible after the migration if the original document wasn't migrated. For example, it may not be possible to reverse an FI invoice if the corresponding logistics invoice in Material Management (MM) wasn't migrated.
• CO documents for expense postings before the time-slice key date might not be migrated, as the migration of CO documents depends on the object type. Specifically, transactional data before the time-slice key date that is related to object numbers starting with KS, KL, AO, and EO is not migrated. This could mean that CO document line-item postings before the time-slice key date on a cost center are not migrated and this can result in having a FI document with expense lines and an account assignment to a CO object (for example a cost center), but no corresponding CO document.
• FI balances at the beginning of the time slice cannot be explained by their line items for accounts that are not open-item managed. This is because FI documents are migrated with their open items, but the document may also include G/L accounts that are not open-item managed. Balance sheet–account line items with a posting date before the time-slice key date may be migrated while, on the other hand, the balances on the same G/L accounts before the time-slice key date are not migrated. For example, let's say the time-slice key date is January 1, 2021. When you display the balance of a G/L account for the fiscal year 2019, the balance is zero. When you drill down to the line-item display, however, some line items may be present. The reason is that these G/L account line items are included in a FI document with open items.
• Complete document flows are not guaranteed. For example, the sales order of a document flow might not be migrated if it was created before the time-slice key date and has a completed status. However, the related invoice and open item on the customer account are migrated because they are created within the time slice.
• When using standard reports to compare open items on customer, vendor, or G/L accounts, discrepancies may arise between the source and target systems if the report's key date is earlier than the time-slice key date. This occurs because standard reports include items that were open on the report key date (that is, posted on or before it, and cleared after it). However, if an item was both posted and cleared before the time-slice key date, it is not migrated when the time-slice solution pattern is active. Consequently, this can cause differences between the source and target system reports. For example, the time slice key date is January 1 2022. An invoice on a customer account has a posting date of August 13 2020 and a clearing date of January 15 2021. When you report open items with a report key date of January 1 2021, this item will be included in the report from the source system. In the target system, however, this item will not be available and consequently not included in the report. The reason is that this item was not migrated to the target system, as both its posting and clearing date is before the time-slice key date.

In the Manage System Scans app, you can create a system scan and run it to gather data from a source system.

System scans are an additional method of gathering information for your data migration. A system scan analyzes a source system in SAP ECC and gathers identified tables (standard, custom, add-ons, custom namespaces, and so on).

You can find the full list of tables scanned by the system scan in the SAP Business Transformation Center FAQ, question 10:3328319.

After a successful execution, you can associate this data with a digital blueprint using the Select Scanned Tables app.

Performing system scans requires the following setup:

• The source SAP ECC system must be configured in the SAP Landscape Management app according to the instructions in SAP Note 3075880.
• An end point must be created in the SAP Landscape Management app and assigned to the BTC use case.

In detail, the following options are available:

• Create and run system scans.
• Edit the title of a system scan.
• Delete system scans.
• Review the list of the tables returned by the system scan, if there are any.
• Review the list of system scan-related activities in the activity log.
• Share a system scan or export it into a spreadsheet.

You can upload, edit, run, and delete system scans.

Watch this video to see how to create and manage system scans.

In the Select Scanned Tables app, you can apply scoping decisions to scanned tables obtained from system scans generated using the Manage System Scans app.

After configuring your source system in SAP ECC, you can perform system scans. If data is found in the scanned tables, it's included in the digital blueprint by default, but you can edit the scope in this app.

After associating your system scan with a digital blueprint, you can apply scoping decisions to the scanned tables it contains.

Scanned tables included in the system scan are displayed in the digital blueprint details and automatically included in scope.

Watch this video to see how to perform scoping decisions on scanned tables.

In the Select Company Codes app, you can select or deselect company codes to adjust the scope of your digital blueprint.

It displays multiple chart views and a full list of company codes that were imported with the analysis file. The app also provides hints to help you make a decision. In detail, the following options are available:

• View details of any given company code.
• Edit company code scope individually or en masse.
• Receive hints based on your current settings.

Watch this video to see how to select company codes to adjust the scope of digital blueprint.

In the Select Transformation Objects app, you can select or deselect transformation objects to adjust the scope of your digital blueprint.

It displays multiple chart views and a full list of transformation objects that were imported with the analysis file. The app also provides hints to help you make a decision. In detail, the following options are available:

• View details of any given transformation object.
• Edit transformation object scope individually or en masse.
• Receive hints based on your current settings.

Watch this video to see how to select transformation objects to adjust the scope of digital blueprint.

In the Digital Blueprint Overview app, you can review the technical and business details of your digital blueprint.

It displays multiple chart views and area-specific dashboards to display the current configuration. The app also allows you to check currently valid hints. In detail, the following options are available:

• Create a new digital blueprint.
• View technical and business details about the digital blueprints.
• Enter the Select Company Codes app, the Select Transformation Objects app or the Select Scanned Tables app to refine the scoping.

Watch this video to see an overview of the Digital Blueprint Overview app.