Technology Blog Posts by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

SDT Using SAP Business Transformation Center: End to End Process & Technical Configuration

sunildevanda
Explorer
‎2025 Apr 04 1:37 PM
2,079

Introduction:

SAP Business Transformation Center is a SaaS (software-as-a-service) product from SAP, embedded into SAP Cloud ALM. It is a one-stop shop for customers who want to selectively transition from SAP ERP Central Component (SAP ERP) 6.08 to SAP S/4HANA 2023 or beyond using through SHELL CONVERSION method of SDT. Their target can be either to S/4 HANA on-premises or SAP S/4 HANA private cloud edition under RISE. In general, it is available to all the customer with a valid SAP Service Cloud subscriptions and the SAP Enterprise Support agreement and does not involve any additional license cost for usage.

In this blog i will show you End-to-End migration process and setup the connectivity between source and target system with SAP Cloud ALM.

Photo19.png

Technical System Landscape:

SAP Business Transformation Center is a cloud native application which relies on the following components:

  • The source system, which utilizes the current ST-PI add-on to enable the data transformation with SAP Business Transformation Center.
  • The SAP S/4HANA system, which contains all necessary subcomponents already shipped within the SAP S/4HANA CORE component.

Each system is accessed from the cloud layer using the SAP Cloud Connector. The SAP ECC system and the SAP S/4HANA system are connected via OData service bindings from SAP Business Technology Platform. There is an RFC-based connection between the SAP ECC and the SAP S/4HANA system.

Source system:
ECC 6.0 EHP 8
OS: SuSE Linux 15.2
DB: SAP ASE 16.0.04.01

Target system:
Release: SAP S4HANA 2023 FPS02
OS: SuSE Linux 15.5
DB: SAP HANA DB 2.00.081.00.1733303410

Photo2.png

Target system preparation for BTC:

In a shell conversion scenario, all data from the source SAP ERP system is removed, leaving the system with the customizing data only (Without master and transaction data). This empty shell system is then converted to SAP S/4HANA using SUM DMO. After the completion of the conversion, the selected master and transaction data is then migrated to the newly converted S/4HANA system.

Prerequisites Technical Aspects
1. Execution of SAP Readiness Check for conversion
2. Execution of SAP Readiness Check for Usage and Data Profiling
3. Create target system:
a) Creation of a Shell based on customer ECC
b) Conversion of ECC Shell to SAP S/4HANA with SAP SUM and provide as target system

Prerequisites Functional Aspects:
A. Following SAP S/4HANA conversion guide (link):
a) Simplification items
b) CVI
c) Custom Code adaption
d) Inconsistencies

Photo1.png

End-to-End Migration Process and activities in SAP BTC:

Photo3.png

Technical configuration and connectivity of source and target system:

1. Onboarding a New ABAP Source System
a. Technical Prerequisites and Required Add-Ons
b. Required SAP Notes
c. OData Services for Source System
d. Cloud Connector for Source System
e. Connect a Source ABAP System to SAP Cloud ALM
f. Maintenance of Property Store in the Connected Source Systems
g. Additional Technical Prerequisites for Source System
h. Next Steps After Onboarding a Source System

Technical Prerequisites and Required Add-Ons:

Minimum software component version requirement

Our current version

SAP_APPL 618

SAP_APPL 618 SP15

ST-PI 740 SP>=24

ST-PI 740 SP27

DMIS 2011_1_731 >=SP18

DMIS 2011_1_731 SP26


Required SAP Notes:

3443741 - Collective note for SAP Business Transformation Center
Implement following S-Notes: 3548580

OData Services for Source System:

Activate below O-Data Services in source system-
T-Code: /N/IWFND/MAINT_SERVICE
/BDTS/COMMAND_SRV
/BDTS/INSTALLED_SAP_NOTE_SRV
/BDTS/PRESEL_TAB_DATA_SRV
/BDTS/PRESEL_TAB_READ_NAME_SRV
/BDTS/PRESEL_TASK_IS_CREATED_SRV
/BDTS/PRESEL_TASK_PORTION_SRV
/BDTS/PRESEL_TASK_READ_STATUS_SRV
/BDTS/SOFTWARE_COMPONENT_SRV
/BDTS/TABLE_FIELD_STRUCTUR_SRV

Cloud Connector for Source System:

1. Install Cloud Connector
2. Connect your SAP Cloud ALM subaccount to the cloud connector
3. Add backend source system in the cloud connector with HTTPS protocol

Photo4.png

Connect a Source ABAP System to SAP Cloud ALM:

  • Connect the ABAP system to cloud ALM using the 'Landscape management'
  • T-Code /SDF/ALM_SETUP
  • Add endpoint for Business transformation center in the connected system and test the connectivity

Photo5.png

Photo9.png
Maintenance of Property Store in the Connected Source Systems:

  • Execute the /BDTS/ADMIN transaction.
  • Double-click on the /BDTS/PROPERTIES_SET object, or select this object and click Execute.
  • In the Property Store Maintenance transaction, you can create, change or delete a property.

Photo6.png

Photo7.png

Next Steps After Onboarding a Source System:

  • Generate Analysis File:
  • To generate an analysis file in the SAP ECC System, follow the instructions from SAP Note 3275056
  • For analysis file implement below two s-note
  • 3112362 - SAP Readiness Check for SAP ERP Usage and Data Profiling
  • 3275056 - SAP Readiness Check for SAP ERP Usage and Data Profiling: Initial Data Migration Profile 2.0
  • Execute the program RC_UDP_START_DMR2 via transaction SA38 in the productive client of the production system to start the analysis
  • Choose Schedule Analysis to schedule the background job to collect the data.
  • Once the data collection job is finished, choose the Download DMR2 Analysis Data option from within the program RC_UDP_START_DMR2  to download the analysis data to your local file system.
  • Upload the analysis file in Cloud ALM

Photo8.png

Photo10.pngPhoto11.png

Run system scan in Cloud ALM:

Like we had scoped the company code and transformation object for SDT, we must also check the relevance of each of the Z object and scope it based on the customer requirement or based on its last Activity after discussing with the object owner. This scoping can be performed using 'Select Scanned Table' app as shown below. Please note that any Z table with record count zero is automatically marked as out of scope by SAP BTC.

Photo12.png

Photo13.png

Onboarding of target S/4 HANA Shell to SAP BTC:

Technical Prerequisites and Required Add-Ons
Required SAP Notes
OData Services for Target System
Cloud Connector for Target System
Connect a Target ABAP System to SAP Cloud ALM
Create RFC Destination to SAP ECC Source System
Maintenance of Property Store in the Connected Target System
Save the Upgrade Buffers
Start the Command Daemon
Next Steps After Onboarding a Target System

Technical Prerequisites and Required Add-Ons:

Ensure that the minimum version requirement
S4COREOP 108, with corresponding support package level >=FPS1.
ST-PI >=740, with corresponding support package level >=0024.

Required SAP Notes:

Ensure to apply the SAP note 3443741 in target system.

OData Services for Target System:

In the SAP S/4HANA target system, some components from the ST-PI add-on are reused, therefore both OData V2 and V4 services need to be activated.

OData V2 services:
T-Code: /IWFND/MAINT_SERVICES
/BDTS/INSTALLED_SAP_NOTE_SRV
/BDTS/SOFTWARE_COMPONENT_SRV
/BDTS/TABLE_FIELD_STRUCTUR_SRV

OData V4 services:
T-Code: /IWFND/V4_ADMIN
API_BDTSCOMMAND
API_BDTSDESIGNTIMEENTITY
API_BDTSEXECUTIONPLAN
API_BDTSHEALTHCHECK
API_BDTSMIGRATIONSTATUS
API_BDTSTABLEFIELDSTRUCT
API_BDTSVALUEMAPPINGDATA

Cloud Connector for Target System:

1. Install Cloud Connector
2. Connect your SAP Cloud ALM subaccount to the cloud connector
3. Add backend target system in the cloud connector with HTTPS protocol

Connect a Target ABAP System to SAP Cloud ALM:

  • Connect the ABAP system to cloud ALM using the 'Landscape management'
  • T-Code /SDF/ALM_SETUP
  • Add endpoint for Business transformation center in the connected system and test the connectivity

Create RFC Destination to SAP ECC Source System:

Create RFC Destination to SAP ECC Source System in target system and maintain the property store in target as described in Maintenance of Property Store in SAP S/4HANA System.

This RFC will be used by the migration engine of SAP BTC to pull data packages from the SAP ECC source system and hence must be maintained in the property RfcDestinationSender in t-code bdts_admin-> Select BDTS_PROPERTIES_SET.

Photo15.pngPhoto14.png

Maintenance of Property Store in the Connected Target System:

Save the Upgrade Buffers:

During the shell conversion process, the upgrade buffer of the system was updated and this must be saved

  1.   Execute the BDTS_ADMIN transaction.
  2.   Double-click on BDTS_DMC_SAVE_UPG_TRANS object or select Execute.
  3.   Select Save transports from upgrade

Start the Command Daemon:

To enable the handling of cloud commands on the ABAP side, the Command Daemon must be activated

  1. Execute the BDTS_ADMIN transaction.
  2. Double-click on BDTS_CMD_WDOG_START object or select it and click Execute.
  3. Enter BDTS_T_DAE as the daemon user (or whatever you set up for this task) and set the frequency. The recommended frequency to use is 1.000 milliseconds.
  4. In case the daemon is already running, a corresponding notification is issued.

Photo16.png

Next Steps After Onboarding a Target System:

Now that your target system is onboarded, you can run a final check from the BDTS_ADMIN transaction with the BDTS_ADM_SETUP_CHECK health check, as described in Health Checks. This setup check runs health checks that are specific for the setup.

Photo18.pngPhoto17.png

In this way we can prepare and stablished the connectivity for source and target system with SAP Cloud ALM.

Next steps after the technical configuration-

Create digital blueprint
Create transformation model and version
Create cycle and Run cycle

Once we create a version of transformation model from the blueprint and connect it to the source ECC system and target S/4 HANA system, it triggers the application data migration from source to the target.  It happens in 4 phases as shown below.

PHASE 1: CYCLE PREVALIDATION (UPTIME)
PHASE 2: CYCLE PREPARATION (UPTIME)
PHASE 3: RUN CYCLES (DOWNTIME)
PHASE 4: POSTPROCESS CYCLE (DOWNTIME)

All these phases can be managed using the "Manage Cycle" app in SAP BTC.

Photo20.png

1.Cycle Prevalidation:

During the "Cycle prevalidation" phase, several prerequisites of the connected systems are examined.  Making sure there is no business data on the target S/4 HANA shell system. Any problems found are recorded in the cycle log as indicated, and they can be carried out repeatedly until this phase turns green.

Photo21.png

2. Cycle Preparation:

In 'Cycle preparation' phase, the actual preparation and configuration of the migration engine takes place. This phase runs as a part of uptime phase and runs before the cutover. This step along with initial step up, also covers transformation rule creation, sub-transformation object creation and validation followed by the postprocessing items creation. 

Photo22.png

3. Run Cycles:

Based on the specified and scoped elements in the transformation model, the third phase, "Run Cycles," involves the actual physical data migration to the target S/4 SHELL.

Photo23.png

Photo26.png

4. Postprocess Cycles:

In the final step of "Post-processing", all the data that was transferred directly at database table level gets converted into SAP S/4 HANA model. Like all phases, logging is available which enables us to view the progress at a granular level.

Photo24.png

Photo25.png

This blog covers End to End Process & Technical Configuration for SDT using SAP BTC.

Thanks for reading!

4 Comments