Checklist of migrating SAP Business One from SQL Sever to

A completed version of cookbook available here:

# Procedures

Identifying the migration path and system landscape

1 architecture given the current version and target
version of customers SAP Business One system

(Optional) Upgrading the customers SAP

2 Business One system to the relevant version
which can be migrated as the migration path
identified above.

3 Installing SuSE Linux Enterprise

4 Installing SAP HANA, and SAP Business One,

version for SAP HANA.

5 Migrating SAP Business One Databases from

SQL Server to SAP HANA
 6 Upgrading the company schema with Upgrade
Wizard

7 Migrating the SQL query related customization

in SAP Business One

8 [Optional but recommended] Creating reusable HANA

Models for analytics scenarios

9 Migrating Crystal Reports and Dashboards

10 Add-On Migration
t of migrating SAP Business One from SQL Sever to SAP HANA
Cookbook of migrating SAP Business One from SQL Server to SAP HANA
Key factors for effort estimation

Perform an upgrade and sanity test

Knowledge about Linux.

A consultant with basic Linux knowledge should be

able to perform hardware configuration, like BiOS,
Harddisk partition, OS installation etc in 0.5~2
days.

Knowledge about Linux, SAP HANA and B1H.

This requires the consultant spend some time on
understanding the system landscape, installation
procedure, and preparing the download. Usually it
varies 1~4 days for a trained consultant.

1.The size and number of DB to be migrated

2.Specification of SQL Server machine
3.Specification of workstation running the
migration tool

The migration should be done in hours. e.g. A 40 G

DB takes 1.5 hours to be migrated with given 16 G
RAM SQL Server and a separate 8 G RAM migration
workstation. Effort for migration may vary from 0.5
day to 2 days etc
Normal upgrade with upgarde wizard.
0.5 days should be enough.

1.The complexitiy of SQL related customziation

1).SBO_SP_TransactionNotification
2).B1 Queries (Format Search, Alerts and Report
etc)
2.Knowlege of SAP HANA SQL and SQLScript, plus
semi-automatic SQL migration tool is avaialble.

This depends on the complexity of analytics

requirement and modeling skills.

The number and complexity of Crystal Reports and

Dashboards. If a Crystal Report is just using a table
or query as datasource, then replacing the
datasource and query with HANA.

1.The data storage of Add-On: UDT or non-UDT like

SQL table or external DB.
2.Data access:
Suported: SDK, JDBC, ODBC
Not supported: ADO.Net, LINQ and MS EF others.
(rewrite data access part)
3.Direct SQL query access or not.
4.Using specific SQL Server feature or function
SQL Sever to SAP HANA
e from SQL Server to SAP HANA
Remarks
Please check the notes below:
1754451 - Central Note for SAP Business One 8.82, version
for SAP HANA
1841037 - Central Note for SAP Business One 9.0, version for
SAP HANA

Normal B1 upgrade with upgrade wizard.

SAP Business One and SAP HANA related training options

for partners
https://cw.sdn.sap.com/cw/community/interactive/blog/201
2/11/19/sap-business-one-and-sap-hana-related-training-
options-for-our-partners

7_STEPS_SUSE_SAP_B1_HANA:
https://cw.sdn.sap.com/cw/servlet/JiveServlet/download/38-
101262/7_STEPS_SUSE_SAP_B1_HANA_28March2013.pdf

Installation Guide for SUSE Linux Enterprise Server with SAP

HANA and SAP Business One:
https://cw.sdn.sap.com/cw/servlet/JiveServlet/download/38-
101266/Installation%20Guide%20for%20SUSE%20Linux
%20Enterprise%20Server%20with%20SAP%20HANA%20and
%20SAP%20Business%20One.zip

FAQ about the Installation of SAP HANA and B1A/B1H:

http://scn.sap.com/docs/DOC-41991

B1H 9.0 from bare metal to live system:

http://scn.sap.com/community/business-
one/blog/2013/08/08/90-bare-metal-to-live-system

This step only migrates the database from SQL Server to SAP
HANA, no customized SQL query migrated and table
structure upgraded. SAP provides a tool migrating the
databases of SAP Business One from SQL Server to SAP HANA
in each patch CD, which can be found at
<<$B1H_Patch_CD\Packages\B1
Analytics\Disk1\tool\migration>>. You need to follow the
guidance in the section of Admin guide about
Upgrading to SAP Business One 8.82/9.0, Version for SAP
HANA
Migrating Company Databases from the Microsoft SQL Server
Database to the SAP HANA Database
How to Convert SQL from MS SQL Server to SAP HANA:
http://scn.sap.com/community/business-
one/blog/2013/04/10/how-to-convert-sql-from-ms-sql-
server-to-sap-hana

Implementing SP_SBO_TransactionNotification in SAP

Business One, Version for SAP HANA:
http://scn.sap.com/docs/DOC-47893

We recommend creating HANA models first, then

implementing the analytics requirement with HANA models.
However, in the intial phase of the project it may be easy to
migrate the reports and dashboard with datasource
replacement. Then think of implementing analytics with SAP
HANA modeling next phase. It relies on the project plan and
client requirement.

As above. We recommend creating models first, then using

models in the Crystal Reports and Dashboards.

SDK remains the same as it is for SQL version.

-ODBC and JDBC connection string need to be updated.
-The data access with ADO.net, LINQ and MS Entity
Framework need to be rewrited with SDK or ODBC, JDBC
-Direct SQL query access need to be migrated. Refer to step
7.
 Add-On Migration Checklist
Category Check list

Does your 3rd party solution store data in an external DB or

Data Storage direct SQL tables in a B1 company schema rather than UDT/UDF
of a B1 company schema?

Does your Add-On have direct access to the B1 company with

ODBC/JDBC?
Connection
Does your 3rd party solution use such as ADO.Net, LINQ or MS
Entity framework etc. instead of SDK for data access?

Does your Add-On solution use a direct SQL query?

1).DataTable.ExecuteQuery() in UI API
2).RecordSet.DoQuery() in DI API
Direct SQL 3). Use the ExecuteSQL command to runs SQL queries in DI Server
4).SQL call, executesql etc in B1if/B1iSN
5).Any other direct SQL query

Native SQL Does your Add-On use any native SQL Server object or
objects functions? Like views, procedures, change tracking, etc.
Migration Checklist
Comments

From legal contract standing point, for B1A/B1H customers,

SAP HANA is only allowed to be used for data storage of B1
solution, including B1 company schema. The Add-On with external
schema instead of UDT/UDF in B1 schema must be certified by SAP
to use SAP HANA as database engine.
SAP HANA support ODBC and JDBC connection. However, the
connection string is somehow different from SQL Server.
Currently SAP HANA doesnt support ADO.Net, LINQ and MS EF etc.
You need to replace the data access part with SDK or direct
ODBC/JDBC connection to SAP HANA.

Due to the syntax differences between SQL query in SQL Server and
SAP HANA, these queries in your Add-On solution need to be
migrated. See the section about Migrating the SQL query related
customization in SAP Business One.

Need to migrate Stored Procedure into HANA procedure, SQL View

to HANA table view or Models etc.