Migration of SAP HANA XS Classic To SAP Cloud Application Programming Model Using SAP HANA Application Migration Assistant

Description

The SAP HANA Application Migration Assistant enables users to migrate XS Classic applications packaged either as a Delivery Unit or as a Package into SAP Cloud Application Programming Model (CAP) projects, targeting SAP HANA Cloud as the database.

In this enhanced version, the assistant performs:

Automated Conversion of Database Artifacts: Source XS Classic Repository database objects (such as .hdbcds, .hdbtable, .hdbview, etc.) are transformed into their corresponding SAP CAP compliant database artifacts (e.g., .cds models), with naming adapted to SAP HANA Cloud conventions.

Service Layer Migration via Generative AI: Using GenAI, the assistant analyzes .xsodata, .xsjs, and .xsjslib files to generate corresponding service.cds, service.js, and custom handler implementations under the CAP srv/ layer. This accelerates the migration of service logic while preserving structure, routes, and functional behavior where possible.

Caution

As generative AI conversion is not guaranteed to be 100% accurate, human intervention is required post-migration to validate, refine, and productionize the application logic and service definitions.

In this sample, conversion of Source XS Classic Repository database artifacts to the corresponding target SAP CAP compliance database artifacts are listed.

Introduction

SAP HANA Interactive Education or SHINE is a demo application that is packaged as HCO_DEMOCONTENT Delivery Unit. It includes the following features:

HDI Features:
- Table
- HDBDD Views
- Sequence
- Calculation Views
- Analytical Views
- Attribute Views
- Associations
- Table Functions
- Synonyms
- Procedures
- Spatial Features
- Local Time Data Generation
- Index
- Structured Privilege
- Analytical Privilege

HCO_DEMOCONTENT follows the XS Classic Programming Model(XSC) and uses SAP HANA on-premise for the database. This article describes the steps to be followed to migrate this Delivery Unit from XS Classic to the SAP Cloud Application Programming Model(CAP) with SAP HANA Cloud as the database along with service layer using the SAP HANA Application Migration Assistant.

Requirements

XS Classic on-premise database source system with the HCO_DEMOCONTENT delivery unit.
SAP Business Technology Platform subaccount with the following
- Service instances:
  - SAP Hana Cloud and
  - SAP Hana Schemas and HDI Containers
- Subscription
  - SAP Business Application Studio or SAP Build. SAP Build is required if you want to convert the service layer as well, since GenAI capabilities are only available in SAP Build plans.
SAP Cloud Connector

Where to Start

To successfully migrate the HCO_DEMOCONTENT sample delivery unit using the SAP HANA Application Migration Assistant, follow the steps below:

Install and configure the SAP Cloud Connector.
Setup an SAP BTP Destination to connect to the source system.
Create a Dev Space in either SAP Business Application Studio or SAP Build with SAP HANA Application Migration Assistant extension installed.
Migrate using the SAP HANA Application Migration Assistant.
Database post migration changes.
Service Layer post migration changes.
Deployment of the migrated database artifacts.

Note

This sample covers only the migration of the database artifacts from SAP Neo Database to SAP Hana Cloud.
The migration steps should be tested in a development environment before production. This guide is directed at single-tenant-applications.

Step-1: Install and Configure the SAP Cloud Connector

Install the SAP Cloud Connector on your local system. For the installation and setup of the cloud connector, please refer to this Documentation.
After installing the cloud connector, you can access it by opening your web browser and going to https://localhost:<port-no>/. Use your credentials to log in.
Once you've successfully logged in, you should set up two connections in the Cloud Connector.
- The first connection should link to the subaccount with the source database, and the second connection should be for the target subaccount with the SAP Hana Cloud. To establish these connections, click on the connector button in the left menu.
- Now, enter the necessary details for your subaccount - this includes the Region, Subaccount ID, Display Name, Subaccount User, Password, and Location ID. After entering all the information, click on 'Save'.

Select the subaccount where the source database is located, then add a service channel under 'on-prem to cloud' using the following details:
- Type: HANA Database
- HANA Instance Name: < DB/Schema ID >
- Local Instance Number: Input any two-digit number between 00 and 09. This number is used to compute the port number needed to access the SAP instance in the SAP Hana Cloud. The local port is calculated from the local instance number (3<n<15). For example, if the number is 7, then the local port would be 30715.
- Connections: 1

In the SAP Business Technology Platform (BTP) Cloud Foundry account where the SAP Business Application Studio (BAS) subscription is created, select 'Cloud to On-Prem' and add a mapping with the following details:
- Back-end Type: SAP Hana
- Protocol: TCP
- Internal Host: localhost
- Internal Port: < portno > (The port number derived from your local instance number)
- Virtual Host: myvirtualhost
- Virtual Port: This should be the same as your internal port
- Principal Type: None

Step-2: Setup an SAP BTP Destination to connect to the source system

Navigate to the SAP BTP Cloud Foundry subaccount and select 'Destination' under 'Connectivity' from the left menu pane. Create a new destination using the following details:

Name: < Destination name >
Type: HTTP
URL: https://<virtual-host>:<virtual-port-no>/
ProxyType: on-premise
Authentication: NoAuthentication
Locationid: Location id as mentioned in cloud connector

And the following additional properties:

HTML5.DynamicDestination : true
WebIDEEnabled : true
WebIDEUsage : xs_hdb

Step-3: Create a SAP Business Application Studio or SAP Build Devspace with the SAP HANA Application Migration Assistant Extension installed

In the SAP BTP subaccount where you created the destination, establish a subscription to SAP Business Application Studio (BAS) or SAP Build. Choose SAP Build if you intend to convert the Service Layer.

Important

Service Layer migration leverages Generative AI capabilities, which are available only in SAP Build plans.

Open SAP Business Application studio or SAP Build subscription.
If selecting SAP Build, it will take it to lobby page. From there switch to Dev space manager.

Select "Create Dev Space". Assign a desired name to your Dev Space and select the "Full Stack Cloud Application" type. Then, choose the SAP HANA Application Migration Assistant Extension to help with migration, as well as the SAP Hana Tools Extension which will be required later for deployment. Finally, click on "Create Dev Space".
Wait for the status of your newly created Dev Space to change to "Running". Once it's running, you can open it by clicking on the name of the Dev space that you just created.
Navigate to the folder by clicking on File -> Open Folder. Enter the path /home/user/projects/ and click on OK.
Once the folder opens, you can select the SAP HANA Application Migration Assistant from the Command Palette (You can access the Command Palette from View -> Command Palette).

Step-4: Migrate using the SAP HANA Application Migration Assistant

Open the the Command Palette and type "SAP HANA Application Migration Assistant" and select the command when it appears.
When the Migration Assistant Wizard opens, select the migration path. Since we are migrating from XS Classic to SAP CAP, select XSC to CAP as your migration path.

In the Data Source page of the wizard, choose the destination you previously created from the dropdown menu.

Enter the user credentials for the SAP HANA Database Migration User - username and password - into their respective fields. Hit the login button to authorize these credentials.Procedure to create migration user

To proceed, click on the Next button.

In the "Migration Options" page, select "Delivery Unit" or "Package Name" as your source type from the drop-down menu. The SAP HANA Application Migration Assistant supports package level migration as well.

Enter the name of your Source Delivery Unit in this case, it would be HCO_DEMOCONTENT or Source Package Name which will be sap.hana.democontent.epm.data:true.

Choose the target directory. This is where the migration results will be stored.

Note: Ensure that the directory you select is a sub-directory of /home/user/projects.

Specify a unique name for the Target Folder, where the migration results will be saved.

Select "Yes" if you would like to convert Service Layer using GenAI capabilities.

Important

Service Layer conversion is available only in SAP Build plans. This feature is currently experimental and free, but is subject to change in the future

Select the XSC Compatilibity Mode by setting it to True, False or Default.

xsc-compatibility-mode is a view property introduced to maintain behavioral compatibility with how Calculation Views, especially those with aggregation nodes or star joins, worked in XS Classic (XSC) when migrating them to HANA Deployment Infrastructure (HDI) in XSA. In the SAP HANA Application Migration Assistant, the UI provides a drop down with 3 options for the xsc-compatibility-mode. They are:

True: Sets the value to true and enables the legacy XS Classic behaviour in CVs

False: Sets the value to false and adopts the native XSA behaviour

Default: Retain the existing values for all CVs

please refer to xscCompatibilitymode.

Select Migration type. By default, "Non-staged Migration" is chosen and Click "Finish" button.

Staged Migration is used when there are objects in our container which have dependent objects in other hdi containers or external schemas. In the case of staged migration, separate hdbsynonyms, hdbsynonymconfigs and hdbgrants will be created for each external hdi container and external schema, the objects in our application depend upon. If all the objects required for deployment are present in our container, a non-staged migration would suffice.

If you choose "Yes", the prompt to browse configuration file must be visible. Choose the valid json file from the devspace. Click "Finish" button.

Note

For further information and creation of configuration file, please refer Staged Migration.

Preview of configuration file

When a notification appears in the bottom-right corner of your screen, it indicates that the migration process has started. This notification will provide real-time updates throughout the process. At the end of the migration, a SAP CAP project will be generated, containing:
- Revised database artifacts
- The service layer (if service layer conversion was selected)
- A report.html file summarizing migration details and areas requiring manual review.

Step-5: Database post migration changes

Once the project is created, there are some adjustments we need to make manually as these are not currently handled by the SAP HANA Application Migration Assistant. We have provided the changed files for HCO_DEMOCONTENT for reference.

If your project contains any files from a different schema, these need to be migrated before migrating the current Delivery Unit and included in this project. If this can't be done immediately, you can remove them for the time being. To utilize objects from other containers, please refer to the SAP HANA Cloud help documentation and configure accordingly.

For the HCO_DEMOCONTENT project, make the following changes:
- Delete the uis folder from db/cfg
- Delete synonym-grantor-service.hdbgrants and synonym-grantor-service.hdbsynonymconfig from db/cfg
- Delete synonym-grantor-service.hdbsynonym from db/src/uis/db
- Delete synonym-grantor-service.hdbsynonym from db/src/models

In order to access objects from other public schemas, you will need to either create a new hdbsynonym file or modify an existing one. For the HCO_DEMOCONTENT project, edit the db/src/synonym-grantor-service.hdbsynonym file with the following configuration:

{
  "SAP_HANA_DEMOCONTENT_EPM_DUMMY": {
     "target": {
       "schema": "SYS",
       "object": "DUMMY"
     }
  },
  "SAP_HANA_DEMOCONTENT_EPM_M_TIME_DIMENSION": {
     "target": {
       "schema": "_SYS_BI",
       "object": "M_TIME_DIMENSION"
     }
  },
  "M_TIME_DIMENSION":{
     "target": {
       "schema": "_SYS_BI",
       "object": "M_TIME_DIMENSION"
     }
  }
}

In addition, please take the time to clear out unused role names from the default_access_role.hdbrole file located in the db/src/defaults folder. If there are specific roles required for your project, ensure to add them as needed. For the HCO_DEMOCONTENT project, Remove SAP_HANA_DEMOCONTENT_EPM_MIGRATION_ALL_ANALYTIC_PRIV role under names.
The assistant will modify the name of the artifacts in your project. Therefore, ensure to update the references to these artifacts accordingly.
- For the HCO_DEMOCONTENT project, you'll need to adjust the references for entities under the currencyConversionTables tag. This is located in the db/src/models/PURCHASE_COMMON_CURRENCY.hdbcalculationview file. Make the changes as follows:
```
<currencyConversionTables rates="SAP_HANA_DEMOCONTENT_EPM_DATA_CONVERSIONS_TCURR" configuration="SAP_HANA_DEMOCONTENT_EPM_DATA_CONVERSIONS_TCURV" prefactors="SAP_HANA_DEMOCONTENT_EPM_DATA_CONVERSIONS_TCURF" notations="SAP_HANA_DEMOCONTENT_EPM_DATA_CONVERSIONS_TCURN" precisions="SAP_HANA_DEMOCONTENT_EPM_DATA_CONVERSIONS_TCURX"/>
```
- In the db/src/models/AP_PURCHASE_ORDER_PROD_CAT_2.hdbanalyticprivilege file, please change the ProductCategory in the filter tag to CATEGORY

Unused configurations should be removed from hdbrole files, or these files should be adjusted to add supported options. For the HCO_DEMOCONTENT project, make the following alterations:

In db/src/roles/User.hdbrole, eliminate the following unused configurations:

{
  "reference": "_SYS_BIC",
  "privileges": [
     "EXECUTE",
     "SELECT"
  ]
},
{
  "reference": "_SYS_REPO",
  "privileges": [
     "EXECUTE",
     "SELECT"
  ]
},
{
  "reference": "_SYS_RT",
  "privileges": [
     "SELECT"
  ]
}

Reason: During the deployment step, access permissions will be granted by executing certain SQL commands.

In db/src/roles/Admin.hdbrole, eliminate the following unused configurations:
```
{
  "name": "REPOSITORY_REST",
  "type": "PROCEDURE",
  "privileges": 
  [
     "EXECUTE"
  ]
}
```
Reason: Roles are not needed for executing procedures in the same container. Instead, you can add authorization based on users in SAP CAP.

Alter db/src/roles/Admin.hdbrole by replacing the existing schema privileges and adding schema analytic privileges:

"schema_privileges": [
{
   "reference": "< Schema Name >",
   "privileges": [
      "SELECT METADATA",
      "SELECT CDS METADATA",
      "SELECT",
      "INSERT",
      "EXECUTE",
      "DELETE",
      "UPDATE",
      "CREATE TEMPORARY TABLE"
   ]
}
],
"schema_analytic_privileges": [
{
   "schema_reference": "< Schema Name >",
   "privileges": [
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_SALES_ORDER_6",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_SALES_ORDER",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_SALES_ORDER_1",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_SALES_ORDER_2",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_SALES_ORDER_4",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_SALES_ORDER_12",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_SALES_ORDER_3",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_SALES_ORDER_9",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_PURCHASE_ORDER_2",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_SALES_ORDER_10",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_PURCHASE_ORDER_PROD_CAT_1",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_PURCHASE_ORDER_3",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_SALES_ORDER_5",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_PURCHASE_ORDER_1",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_SALES_ORDER_7",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_PURCHASE_ORDER_PROD_CAT_2",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_PURCHASE_ORDER",
      "SAP_HANA_DEMOCONTENT_EPM_MODELS_AP_PURCHASE_ORDER_PROD_CAT"
   ]
}
],

Reason: The modifications in the hdbrole file are needed to access calculation views with analytic privileges.

Assign the permission to users with the admin role for accessing the schema. For the HCO_DEMOCONTENT project, create an Admin.hdbroleconfig file in the db/src/roles/ directory. The file should contain the following configuration:
```
{
  "SAP_HANA_DEMOCONTENT_EPM_ROLES_ADMIN": {
     "< Schema Name >": {
        "schema": "< Schema Name >"
     }
  }
}
```
Adjust SQL syntax in procedures. For instance, "UPDATE FROM" should be changed to "MERGE INTO", and "TRUNCATE" statements should be replaced with "DELETE FROM" statements.
Currently, changes to Reptask, and Replication artifacts are not covered. You will need to modify these manually. Unsupported types and functions in the calculation view such as "CE_FUNCTION", "CACHE", etc., need to be noted. Please refer to the SAP HANA Cloud Documentation for more details on how to handle these.
Series entity is not supported in Hana Cloud so they will be removed by the extension. Please check Migration Documentation for more information.
For HdbSynonym, HdbSynonymconfig and Hdbrole files, please check target object parameters before deployment.
- In db/cfg/models/synonym-grantor-service.hdbsynonymconfig file, Change the target.object from sap.hana.democontent.epm.models::SALES_ORDER_RANKING to SAP_HANA_DEMOCONTENT_EPM_MODELS_SALES_ORDER_RANKING.
- In db/src/roles/Admin.hdbrole file, Change the role name from sap.hana.democontent.epm.roles::Admin to SAP_HANA_DEMOCONTENT_EPM_ROLES_ADMIN.
- In db/src/roles/User.hdbrole file, Change the role name from sap.hana.democontent.epm.roles::User to SAP_HANA_DEMOCONTENT_EPM_ROLES_USER.

Step-6: Service Layer Migration

Caution

While the assistant automates a large portion of the migration process, the converted output is not guaranteed to be 100% runnable or semantically equivalent. Manual validation and adjustments are essential to reach production readiness.

Conversion structure

The Gen-AI Migration Assistant converts SAP XS files and components into their equivalent SAP CAP service definitions and handlers, preserving structure and logic for ease of validation and enhancement.

Converted File Mapping

SAP XS	SAP CAP
xsodata	service.cds & service.js
xsjslib	handlers/`source_filename.js`
xsjs	handlers/`source_filename.js`

Directory and File Structure

The original directory structure is preserved during conversion.
All .xsodata files within a folder are consolidated and converted into a single service.cds file with service names derived from the original filenames.
Corresponding service logic is placed in a service.js file,
.xsjslib and .xsjs files are converted into JavaScript files and placed under the handlers/ directory, maintaining the original folder hierarchy.
These handler files are then properly referenced in the implementation via:
- custom-service.cds for additional service definitions, and
- custom-service.js for custom logic implementation.
Finally index.cds is generated at the root folder to import all service definitions.

Before: SAP XS Files

sales/lib/
│       |--- getSales.xsjs
│       |--- salesOrder.xsodata
│       |--- salesHelper.xsjslib
|       |--- utils.xsjslib
|       |--- config.xsjs
manufacture/lib
│       |--- workorder.xsodata
│       |--- jobcard.xsjs
│       |--- workorderHelper.xsjslib

After: SAP CAP Service Definitions & Custom Handlers

srv
|
|---/sales/lib/
│           |--- service.cds           
│           |--- service.js            
│           |--- custom-service.cds            
│           |--- custom-service.js             
│           |--- handlers/
│                  |--- getSales.js
|                  |--- salesHelper.js
|                  |--- config.js
│                  |--- utils.js
|---/manufacture/lib
│           |--- service.cds           
│           |--- service.js  
|           |--- custom-service.cds
|           |--- custom-service.js
|           |--- handlers/
|                   |--- jobcard.js
|                   |--- workorderHelper.js
|--- index.cds

Source Path Reference in converted files

Each code block will have the source code path from which it is been converted.

//converted from: /workspaces/project/sales/lib/salesOrder.xsodata
service salesOrder @(path:'/salesOrder') {

}

Post Migration Common Changes

The following steps are critical to ensure the converted project builds and runs as intended.

service.cds

Entity Imports: Confirm that all entities from DB are correctly imported. Some imports may be missing or incorrectly formatted. Add missing using statements manually. ℹ️ CAP by default converts HANA object names to uppercase with underscores. Refer CAP HANA Naming Convention.
Service Name: Each service.cds file uses the xsodata filename as the service name. There might be duplicate service names due to same .xsodata filenames across directories. Verify and rename if required.
Duplicate Exposed Entities: If multiple services expose the same entity, review and remove duplicates unless explicitly needed.
Entity Columns: Check if column names align with functional logic. If mismatches exist, correct them based on the original .xsodata logic.
Associations & Compositions: If an entity contains complex association or composition relationships, verify that they are correctly structured. The Gen-AI may not always interpret or convert deep associations accurately. You may need to rewrite them manually based on the original data model and business logic.

service.js

Review for correct binding between entity operations and handler functions (e.g., srv.on('READ', ...)).

custom-service.cds

Default service name is CustomService. You must rename it to a unique and meaningful name.
Validate that any additional or extended services are logically separated from the main service.cds.

custom-service.js

Ensure all custom logic handlers are correctly implemented and bound.
Replace or refactor placeholder logic (if any) added by the migration assistant.

handlers

Confirm that all converted xsjs/xsjslib files are present.
Import paths may be incorrect after migration. Review and adjust the import paths in your .js files to ensure all modules and handlers are correctly referenced.
Each file must export a function that binds to its relevant service events. In ES6 script there are multiple ways in which a function or a file can be imported or exported. Please review all the exports done in each file and make sure that they are imported correctly in other files.

Exports	Imports	Ways to call
`export default function;`	`import function from "./file.js";`	`function();`
`export default {function1, function2};`	`import file from "./file.js";`	`file.function1(); file.function2();`
`export async function function1(){};`	`import {function1, function2} from "./file.js";`	`function1(); function2();`
`export { function1, function2 };`	`import * as file from "./file.js;"`	`file.function1(); file.function2();`
`export { function1, function2 };`	`import {function1, function2} from "./file.js";`	`function1(); function2();`

If the original .xsjs code contains raw SQL statements, these may reference tables, views, or columns using SAP HANA naming. But in SAP HANA Cloud, naming conventions follow uppercase with underscores. Review and adjust any raw SQL queries in the code to align with the actual object names referring to migrated db artifacts. Reference DB migration report for the converted/ renames entities.
Verify functionality by comparing with original .xsjs and .xsjslib logic. Some constructs (e.g., response manipulation, error handling) require adaptation to CAP's async/event model.

Tips

Run cds lint to catch syntax and model issues early.
Use cds watch during development for hot-reloading and fast testing.
The entry point for the service layer is index.cds. You can use this file as a starting point to troubleshoot Node.js related issues. To isolate problems:
- Use Node.js debuggers.
- Temporarily comment out services in index.cds one by one to identify which service is causing the failure.
Unexpected Reserved Keyword is a frequently encountered issue. This typically occurs when async and await are used incorrectly. For example, using await outside of an async function or misplacing the async keyword in handler definitions.
For security, define @requires annotations and configure xs-security.json accordingly.
If xsjs logic depends on HANA procedures or views, consider rewriting as CDS views or wrapping them in srv.on(...) handlers.
Refer SAP CAP extensive documentation for HANA Native Object usage, service definitions and custom handlers.

Step-7: Deployment of the Migrated database artifacts

In your dev space, the database connection and artifacts of your project will be visible under the "SAP HANA Projects" section.
Next, log in to your Cloud Foundry account using the following steps:
- Open a new terminal in the SAP Business Application Studio
- Run the command cf login -a < API_URL > and input your username and password
For the Database Connection of the project, click "Bind" and then select "Bind to an HDI Container" and finally select the HDI container created in your SAP BTP Space. Once successfully bound, you will see a .env file with the VCAP services created in the db folder of your project.
Inside .env, extract the current schema value from VCAP services - this is your schema name. Replace < Schema Name > with this value in the Admin.hdbroleconfig and Admin.hdbrole files.
Click the "Open HDI Container" button to open the database explorer.
Open an SQL console with your DBADMIN user or with admin privileges.

Run the following query in SAP HANA Cloud to grant access: should be replaced with your specific schema name. You can also create roles and grant file for granting access.

GRANT SELECT ON SCHEMA "_SYS_BI" TO "< Schema Name >#OO";

GRANT SELECT ON "_SYS_BI"."M_TIME_DIMENSION" TO "< Schema Name >#OO";

GRANT UPDATE ON "_SYS_BI"."M_TIME_DIMENSION" TO "< Schema Name >#OO" WITH GRANT OPTION;

GRANT INSERT, SELECT, UPDATE ON "_SYS_BI"."M_TIME_DIMENSION" TO "< Schema Name >#OO" WITH GRANT OPTION;

GRANT SELECT ON SCHEMA "_SYS_BI" TO "< Schema Name >#OO" WITH GRANT OPTION;

To deploy your application, select the "Deploy" button located in the "SAP HANA Projects" section.

Data Migration

For migration of data using the SAP HANA Application Migration Assistant, please refer to the DataMigration document.

Staged Migration

In case if we have dependent objects outside our application like an external hdi container or schema, we need to migrate via staged migration. For further information, please refer Staged Migration documentation.

Known Issues in SAP HANA Application Migration Assistant

Database:

Some artifacts which are currently not supported in the SAP HANA Application Migration Assistant require manual remodeling before deployment. You can find detailed information on manually migrating these artifacts in the following link.

Service Layer:

Entity Imports: Namespaces in .hdbcds may break using statements
Role Definitions: xsprivileges are not automatically mapped to @requires or security roles
Custom SQL Logic: Complex logic in procedures or views and cases where table is an input, may need manual refactoring
Shared Services: Same entity exposed across multiple services. CAP requires disambiguation

Supported Features

For a detailed list of the features supported by the SAP HANA Application Migration Assistant for Database, please refer to this link.

Unsupported Features

Creating proxy cds for cross container schema
Following Artifacts are not currently supported '.hdbreptask'.
For Virtual table, refer VirtualTable.md
If the source files have any errors, the migration of the Delivery Unit or Package by the SAP HANA Application Migration Assistant will fail. For example: If the javascript files have unknown characters like NUL, the migration will fail with errors. Please check the output logs for the error messages.

Learning Resources

How to obtain support

If you find a bug or have a question about the steps raise ticket under component BC-XS-TLS-MIG. For additional support, ask a question in SAP Community.

Name		Name	Last commit message	Last commit date
Latest commit History 84 Commits
LICENSES		LICENSES
hana-shine-cap-final		hana-shine-cap-final
hana-shine-cap		hana-shine-cap
images		images
DataMigration.md		DataMigration.md
LICENSE		LICENSE
README.md		README.md
REUSE.toml		REUSE.toml
VirtualTable.md		VirtualTable.md
supportedFeatures.md		supportedFeatures.md

License

SAP-samples/xsc-cap-migration

Folders and files

Latest commit

History

Repository files navigation

Migration of SAP HANA XS Classic To SAP Cloud Application Programming Model Using SAP HANA Application Migration Assistant

Table of Contents

Description

Introduction

Requirements

Where to Start

Step-1: Install and Configure the SAP Cloud Connector

Step-2: Setup an SAP BTP Destination to connect to the source system

Step-3: Create a SAP Business Application Studio or SAP Build Devspace with the SAP HANA Application Migration Assistant Extension installed

Step-4: Migrate using the SAP HANA Application Migration Assistant

Preview of configuration file

Step-5: Database post migration changes

Step-6: Service Layer Migration

Conversion structure

Directory and File Structure

Before: SAP XS Files

After: SAP CAP Service Definitions & Custom Handlers

Source Path Reference in converted files

Post Migration Common Changes

service.cds

service.js

custom-service.cds

custom-service.js

handlers

Tips

Step-7: Deployment of the Migrated database artifacts

Data Migration

Staged Migration

Known Issues in SAP HANA Application Migration Assistant

Supported Features

Unsupported Features

Learning Resources

How to obtain support

License

About

Topics

Resources

License

Code of conduct

Security policy

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors 7

Uh oh!

Languages

Packages