Defining the Modeling Elements for the Lean Selective Data Transition Approach

Continue your business transformation journey by creating your transformation model and transformation model version.

There are different key features:

• Manage your transformation models: The transformation model holds all transformation objects, their relations, filters, and rules. You can create one based on a confirmed digital blueprint.
• Create transformation model versions: The transformation model version is a snapshot of the transformation model, and it is used to execute the data transformation.

In the Manage Transformation Models app, you can create and edit transformation models based on a confirmed digital blueprint.

The transformation model holds all transformation objects, their relations, filters, and rules. Its purpose is to describe the totality of the technical definitions and rules for a transformation initiative. This means that there are always extra objects added into the model in addition to what you selected during the scoping phase. These are determined by the following factors:

1. Relation: Scoping relevant objects that are selected in the digital blueprint can have non-scoping relevant related objects, which are always included in the transformation model. Related objects are semantically connected, and relations also exist between non-scoping relevant objects; if one of those objects is in the transformation model, all related objects also appear.

2. Grouped: In some cases, it is not technically possible to create a relation between transformation objects that are otherwise semantically connected, as such objects are grouped together. If one object in the group is included in the transformation model, so are the remaining grouped objects.

3. Digital Blueprint: All standard transformation objects in scope in the confirmed digital blueprint.

4. Baseline: Technical transformation objects that ensure system consistency, included by default in every transformation model.

5. System Scan: Custom transformation objects are identified via a system scan because the tables are not part of the standard content of SAP Business Transformation Center.

In detail, the following option is available:

Create and edit transformation models

• Display transformation filters
• Display all included transformation objects
• Display solution patterns: The solution pattern that SAP Business Transformation Center currently offers is time slice, which can be used within the Selective Data Transition (SDT) scenario. The SDT scenario allows you to selectively exclude data related to specific company codes from your migration project. Using the time-slice solution pattern within the SDT scenario provides you with the additional capability to selectively exclude data before a certain fiscal year from your migration project.

Track data dictionary scan progress

Our standard content does not cover any transformation object that is identified via a system scan. For such objects, we dynamically determine database dictionary information via a data dictionary scan, which is required to ensure that these items are prepared for the move to SAP S/4HANA. This information is then stored in a data dictionary cache, which must be built before creating a transformation model version.

This process starts as soon as you confirm your digital blueprint. You can then create the transformation model immediately, but the data dictionary scan must be completed before creating a transformation model version. This can take several minutes for thousands of tables in custom objects, and you can track the status with progress bar above.

In the Transformation Model Versions app, you can create and review transformation model versions.

The transformation model version is a snapshot of the transformation model, and it is used to execute the actual data transformation. It contains the same transformation objects, their relations, filters, and rules as the corresponding transformation model at the time when you create the version. It can only be created after a successful data dictionary scan; until then, the creation is blocked.

In detail, the following option is available:

Create and review transformation model versions.

Watch the video to learn about transformation objects.

In the  Transformation Filter Content app, you can review the filter assignments in the standard SAP ECC content.

A transformation filter is specified for a table field, a domain or a data element and can be assigned to any number of transformation objects. Each assigned transformation filter is considered during data selection. A transformation filter is always restrictive; if multiple filters are assigned to a single transformation object, all of them are considered.

Here, non-scoping relevant transformation objects are also listed. Non-scoping relevant objects are migrated by default, as they are essential for system stability. Therefore, these do not take part in the scoping of a data transformation project.

In the Content Change Log app, you can review the updates introduced in each content version shipped with SAP Business Transformation Center.

You can navigate to this page from the Related Apps context menu item in the Manage Transformation Models and Transformation Model Versions apps.

In detail, the following option is possible:

Review the changes in each content version.

You can review the following details in this app:

Content Version Timestamp: The exact date and time when the corresponding content version was shipped.

Action: A short description of the type of modification that was made. Possible values are as follows:

• Added
• Modified
• Deleted

Entity ID: The technical name of affected entity.

Entity Name: You can follow the link from this column to view more information about any of the updated entities.

Changes: A short description of what changed in the content.