What is Business Transformation Center (BTC)?
Companies who wants to go with Bluefield conversion (Selective Data Transition) approach, SAP has given a new Tool to selectively migrate their Master and Transactional data for respective company codes only not for all. The new tool is Business Transformation Center (BTC).
BTC Tool and its process is only supported for Bluefield Projects (Selective Data Transition) not for Brownfield and Greenfield Projects. It can work for On premise and On Cloud (Public) solutions only.
In this blog I’ll show how to create Digital Blueprint in SAP BTC Tool “ Company Code wise” .
How Business Transformation Center (BTC) tool works?
For End to End and Technical configuration of BTC Tool, Please refer the Blog publishes by my colleague.
SDT Using SAP Business Transformation Center: End ... - SAP Community
Company Code wise Data Migration.
BTC tool has 3 major phases:
In this blog we will only cover “Selective Data Transition: Define the Scope of your Transition” Digital Blueprint creation part.
The first task in BTC Tool is to do the Scoping which can be done through “Selective Data Transition: Define the Scope of your Transformation app”.
The first two apps “Manage Analysis Files and Manage System Scan” are Basis activity.
Once the Analysis File is uploaded and system scanning is done next step is to create a Digital Blueprint. Digital Blueprint is a heart of BTC tool process, without Digital Blueprint scoping and the Selective Data Migration is not possible in S4 HANA system.
Before creation of Digital Blueprint, we need to have a detailed workshop with business on organization AS IS business process. After the AS IS workshop with business is completed, we can then discuss with business on the Digital Blueprint scoping like what company codes which company codes will be In scope and Out of Scope. Only the In-scope company codes data will be moved to S4 HANA system. The out-of-scope company codes will not be moved to S4 HANA system.
Digital Blueprint creation Process
We can create Digital Blueprint using “Manage Digital Blueprint App”
Click on Create and fill the necessary details.
After entering details, click on Create Analysis and Create System Scan button
The system will give details of Analysis file and other details which we can navigate and see.
The system will also show us the list of all the company codes from source system, while scrolling down below
Navigate to Company Code App and click on Mass Edit and choose the company codes to be in scope and out of scope
In my test case I took 4 company codes in Scope out of 80 and rest 76 are out of scope
AR01, HK01,TH01 and PH01
We can also see the In scope company code in ‘Mange Digital Blueprint” also. We can also choose Transformation Objects based on business requirement and can make the objects In scope or out of scope.
We can navigate to Select Transformation app by selecting the Related Apps from Select Company Code app itself and click on Select Transformation Objects
System will show you all the Transformation objects in scope initially. In our case Total Transformation Objects were 169
We can discuss with business what Transformation objects to be kept in Scope or out of scope by referring last activity and Total Data Count.
We can exclude data whose Total Data Count= “0” or we can also check if last activity for that objects are very old.
As seen we have chosen all the 169 Transformation Objects in Scope for our 4 company codes which can be seen in the app
The Select Scanned table in “The Select Scanned Table in the Selective Data Transition: Define the Scope of your Transition” app will list all the standard and custom tables in the Digital Blue Print.
We can further navigate to Digital Blueprint overview app to get the graphical detail of the Company Code Selection, Transformation object Selection and so on.
The final step is to confirm the Digital blueprint when all the above scoping is done with business. This step is mandatory to move to the next step of Preparation and Execution of Data Migration
Note: Once Digital Blueprint is confirmed it cannot be changed further. For any new requirement new Digital Blueprint has to be created every time.
Hope this blog has helped you in understanding of how Digital Blueprint works in SAP BTC tool as a starting step for data migration to S4 HANA system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
3 | |
3 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 |