SAP Business One SQL Server to HANA migration.
What the migration covers.
Database migration path
The company database is moved with the migration wizard and tooling SAP provides for SQL Server to HANA, on the versions SAP supports for it. We prepare, run and check the move together with your SAP partner or IT team.
Queries, views and formatted searches
Saved queries, user-defined views and formatted searches (FMS) rewritten from T-SQL to HANA SQL: quoted mixed-case column names, ISNULL to IFNULL, TOP to LIMIT, date and string functions, + to || for text.
Stored procedures and validations
User procedures, SBO_SP_TransactionNotification and SBO_SP_PostTransactionNotice rewritten in SQLScript and tested on adding and updating documents, because one error there blocks posting.
Crystal Reports conversion
Reports that use SQL commands or stored-procedure data sources converted to HANA SQL, pointed at the HANA data source and compared with the SQL Server output.
Add-on compatibility checks
C# add-ons on the DI API and Service Layer integrations checked for HANA: identifier case sensitivity, double-quoted identifiers, data types, functions and any SQL the code sends directly.
UDF, UDT and UDO checks
User-defined fields, tables and objects checked after the move, together with the queries and code that read them.
Data reconciliation
Record counts, account and business partner balances, stock and open documents compared between SQL Server and HANA before anyone signs off.
Parallel run and rollback plan
A period where results on HANA are compared with SQL Server, and a written rollback path, so you can go back if a check fails before the cut-over.
Go-live and hypercare
Cut-over support, close watch on the first days of live posting on HANA, then 3 months of free support.
Built for teams like yours.
Companies on SAP Business One for SQL Server that are planning a move to SAP HANA
Companies with many saved queries, formatted searches, Crystal Reports or custom add-ons that must keep working on HANA
SAP Business One partners who need a team to convert and test a customer’s queries, reports and code
How a project runs.
- Assessment and inventory: a free discovery call, then a list of everything that touches SQL: saved queries, formatted searches, user views, stored procedures, the transaction notification, Crystal Reports, alerts, add-ons and integrations, with who uses each one.
- Plan: what moves, what is rewritten, what can be dropped, the test and reconciliation checks, the parallel run and the rollback path, written into the proposal with a fixed price per phase.
- Conversion: T-SQL rewritten as HANA SQL and SQLScript, Crystal Reports re-pointed and converted, add-on and integration code adjusted where it sends SQL or depends on SQL Server behaviour.
- Testing on a copy: everything runs on a migrated copy of your company database, never on production first, and key users test the reports and screens they use every day.
- Reconciliation: counts, balances, stock and open documents compared between SQL Server and HANA, and every difference explained before moving on.
- Parallel run: results on HANA are compared with SQL Server for an agreed period, with the rollback path ready.
- Go-live: cut-over to HANA, with close support in the first days of live posting.
- Support: 3 months of free support after go-live: fixes and small adjustments, then optional monthly support.
What changes when SAP Business One moves to HANA?
The tables and fields stay the same, but the SQL around them does not. HANA turns unquoted names into upper case, so mixed-case SAP Business One columns must be written with double quotes, such as T0."CardCode". Text comparisons are case-sensitive. Functions differ: ISNULL becomes IFNULL, GETDATE becomes CURRENT_TIMESTAMP, DATEADD and DATEDIFF become ADD_DAYS and DAYS_BETWEEN, TOP becomes LIMIT, and + for joining text becomes ||.
Simple queries usually need small changes. Stored procedures, temporary tables, cursors and the transaction notification need a proper SQLScript rewrite, which is why we plan them first, not last.
Who owns the converted queries and scripts?
You do. The client owns the converted queries, scripts, procedures, report changes and documentation. You can keep maintaining them with your own team or your SAP Business One partner, or ask us to keep supporting them.
Can you go back to SQL Server if something goes wrong?
The plan is written so that you can. The SQL Server company database is kept as it was until the switch is final, the cut-over happens only after the tests, the reconciliation and the parallel run pass, and the rollback steps are agreed before go-live, so the decision to switch is made on checked results.
What support do you get after go-live?
Every migration includes 3 months of free post-go-live support for fixes and small adjustments, then optional monthly support. If you need a defined response time, ask for it in the proposal so it is written into the support terms.
Related guides: SAP B1 SQL Server to HANA query migration guide · Formatted search (FMS) guide · SBO_SP_TransactionNotification examples (SQL Server and HANA) · DI API error codes (-5002, -1029, -2035)
Free tools: SQL to HANA query converter · SAP B1 query library (SQL Server and HANA) · SAP B1 table reference
SAP Business One SQL Server to HANA migration: common questions
Do all our SAP Business One queries need rewriting for HANA?
Not all of them, but most need some change. Queries with mixed-case column names, ISNULL, GETDATE, DATEADD, CONVERT, TOP or + for text fail or return wrong results on HANA until they are converted. Simple queries take minutes; stored procedures, temporary tables and the transaction notification need a full SQLScript rewrite. Unused queries found in the inventory can be dropped instead of converted.
Do Crystal Reports work on SAP HANA?
Yes, once they are converted. Reports built on plain tables usually only need to be pointed at the HANA data source. Reports with SQL commands or stored-procedure data sources carry T-SQL, so the SQL is converted to HANA, the report is re-pointed, parameters are checked and the output is compared with the SQL Server version.
Will our add-ons break when we move to HANA?
They can, if they send SQL directly. Add-ons that use the DI API or the Service Layer for business objects are less affected, but any SQL in the code has to respect HANA identifier case sensitivity, double-quoted identifiers, data types and HANA functions. We review the code and test each add-on on a migrated copy of your company before go-live.
How do you check that the migrated data is correct?
By reconciling it. Record counts, account and business partner balances, stock and open documents are compared between SQL Server and HANA, and key users compare the reports they use daily. Every difference is explained before go-live, and the parallel run compares results again on live work.
Can we roll back to SQL Server?
Yes, that is part of the plan. The SQL Server company database is kept as it was until the switch is final, the switch happens only after the tests, reconciliation and parallel run pass, and the rollback steps are agreed before the cut-over.
Is Kodenova an SAP partner?
No. Kodenova is independent and works alongside your SAP partner. Your partner keeps the licences and the SAP side of the upgrade; we convert and test the queries, reports, procedures and add-ons, reconcile the data and support the go-live.
SAP Business One development
Any add-on your business needs: plant maintenance, payroll, approvals, warehouse, integrations and reports for SAP Business One.
ERP developmentCustom ERP & SaaS development
Custom web ERP systems, multi-tenant SaaS and industry software built around your operations.
PortalsWeb & B2B portals
Customer, vendor, commission and employee portals connected to SAP Business One.
Ready to get started?
Tell us what you need. You get a clear technical answer, a fixed scope and a price, usually within 24 hours.
