🚀Kabeer – A Global SAP Partner needs your attention for a quick announcement!

We are delighted to inform you all that we have officially kicked off the SAP Business One implementation for a large company in the Poly-Chem Industry based in Delhi.

This is a great achievement and a reflection of the hard work, dedication, and teamwork shown by everyone involved.

Very well done, Team! 👏

#SAPBusinessOne #SAPB1 #SAPImplementation #GlobalSAPPartner #ERPForChemical #PolichemIndustry

Best Maintenance Management Application for SAP B1

#sapb1 #business #sap

https://youtu.be/2KPrxo4DuOQ?si=aMv8WkblKB_NDJqN

Zoho CRM Integration with SAP Business one | Automated Lead Sync Solution

#zohocrm #zoho #sapb1

https://youtu.be/XKKjl0gKKsY?si=VKDS7fYdhmAKLVTy

Great Day Everyone!

We are extremely Happy and proud to announce you all that we have successfully did the Go-Live of SAP Business One with a leading company in the Healthcare industry! 🚀

Great Work done by Sales Team & by our Support & Functional Team in making this project successful 👏👏

#SAPBusinessOne #GoLive #HealthCare #SAPB1 #AffordableERP #ERPforSME #KabeerConsultingGroup #SAPPartner

Introducing HANA

While I had planned something about the General Ledger for this newsletter, circumstances changed, so I’ll do something entirely different.

As many of you know, I’m no longer with Scientific Device Laboratory. If you’d like to know more about that situation, I have described it in detail here, but the very short version is that I lost the ability to access SAP B1 for this newsletter for the last nine months.

Fortunately, I found someone to help. Richard Duffy and SMB Solutions are graciously providing me with a new Demo instance of SAP Business One, but with one Wrinkle: It is HANA.

Before I go into anything other topics, I’m writing a series of newsletters about how HANA affects SAP B1. We’ll cover the basics of how to write queries in HANA for those curious or needing to translate SQL to HANA and back. Once we have all that, I’ll share with you what I plan to do about writing this newsletter on a HANA system. I’ll assume you know SQL or have taken my course SAP Business One Reporting and Customization.

First, let’s give a little background on HANA. SAP decided several years ago to make a database system they could use across their product line. It has its pluses and minuses. The marketing for HANA was often around its speed due to the in-memory column-based database.

Data in a computer system is stored in dimensional sequence, not the two dimensions we associate with a table. It is as if you had a spreadsheet of only one row.

The best we can do to represent a table is to take the rows or the columns as groups, add them in sequence, then add the next row or column.

Let’s suppose you had this table:

The data would be stored in row order like this in a row-based database.

This is fast for performance in adding and deleting data but presents performance problems in calculations. To get a sum for balances, for example, you have to load each row, get the balance, add it to the total, and then get the next row, which is lots of work.

On the other hand, a column-based database would do this:

All the data for the columns are grouped. To get a sum, it loads the column and sums it. Unlike the Row-based arrangement, there is no jumping around in the data, making it much faster. However, this usually requires in-memory access to the data instead of on-disk access. Such an arrangement requires a substantial amount of memory to run efficiently. Also, insertions and deletions of rows are more complicated as you add data in several places, not as one group.

HANA is not the only column-based database. Data analysis tools like Pandas and even Microsoft SQL Server 2012 have in-memory processing in columns.

Because the HANA implementation of the SAPB1 started from scratch, you will notice a different User interface when running HANA compared to a SQL Server version of Sap Business One. My disparaging quip about SAP B1 UI being as fashional as Windows 95 is no longer accurate.

I’ll discuss this UI in a later column, but from now on, you’ll see screenshots like this in my newsletters.

The real fun begins when you start making queries. HANA has its variant of SQL. Creating a query in the SAP B1 Query Generator of the names and quantities of inventory items produces this query.

You’ll notice the double quotes on the column names. Double quotes are required on column names. Some, like the table name, have optional quotes, but putting quotes around all tables, columns, and aliases like TO is legitimate and often good style.

What’s in the Quotes is case-sensitive. Can you spot the two errors here?

“T0″.”Itemcode” and “oitm” do not have the proper case. Interestingly, it will work if I do oitm without quotes.

Comments are still two dashes. Like many other programming languages, HANA adopts the /* and */ for block comments.

Basic selection, literal strings with single quotes, and sorting also work the same as SQL: this query works with a parameter and sorting:

If you look at only the basics, HANA looks a lot like SQL. However, once you get past the syntax, HANA starts getting different from SQL. In the next newsletter, I’ll look at some commonly-used functions in HANA.

#database #hana #performance #sap #sapB1 #sql #sqlServer