Skip to Content
SAP S/4HANA

What changes, what does not change? After a migration to SAP HANA data base

Tags:

High-level overview:

What will happen to Pool and Cluster tables?

All cluster tables in FI and HR will be converted to transparent tables during data base migration.

As part of the preparation for a SAP HANA data base migration, and also as part of general good ERP house-keeping, SAP recommends to run a check report for pool and cluster tables at least once a year.

http://Service.sap.com/sap/support/notes/1784377

All row tables (VBRK) converted to column tables?

Yes, all row tables which contain transaction data will be converted. Most Meta data tables like customizing tables stay in row format.

Do we still have change log tables (CDHDR etc.)  in SoH?

Yes,  change log tables and change logging including table locking meachanism remain the same.

What happens with the SAP GUI, the user interface?

SAP has provided a detailed roadmap for the user interfaces in general under the theme:  New, Renew, Enable!

Please see the roadmap for details on the scope and plan to align UI’s across all devices: Mobile, desktop etc.

Some new UI’s are provided with the new Suite on HANA transactions as well, some new interfaces are provided with the Enhancement packages.

SAP Business Suite roadmap for User Experience - UI - Mobile etc.

https://websmp209.sap-ag.de/~sapidb/011000358700000215472013E.pdf

http://service.sap.com/roadmap

In addition SAP offers Personas http://wiki.sdn.sap.com/wiki/display/Img/SAPScreenPersonas and Fiori https://experience.sap.com/fiori as even more options to enhance the user experience.

Fiori overview: http://scn.sap.com/docs/DOC-41598

http://scn.sap.com/community/developer-center/front-end/blog/2013/05/16/architecting-an-sap-fiori-deployment

http://help.sap.com/fiori

HTML5 options are delivered for the SAP HANA Live analytical applications.

What happens to modifications and customizations after a migration from Suite on traditional data base to SAP Business Suite powered by SAP HANA?

In case of customizations using SAP BAdi's and BAPI's in the SAP name space, it is possible (depending on the design) that there is a negative impact on the performance. In this case the custom coding in the user exit might need to be adjusted.

In case of modifications, the ABAP code in the BAdi and BAPI might need to be adjusted.

With Suite on HANA, SAP will provide HANA optimized versions of some existing ABAP programs, to which the BAdi's and BAPI's will need to be pointed to.

For details on HANA optimized ABAP programs, please see the latest release notes for SAP Business Suite powered by SAP HANA.

https://websmp207.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000755177

What is the difference between SAP BAPI's and SAP BAdi's?

BAPI's are SAP delivered standard API's ((Business) Application Programming Interfaces) to allow SAP customers to meet custom requirements not covered by Standard functionality. All standard BAPI's can be found in the Business Object Repository (BOR). A BAPI is a stateless, business object-specific Function Module. Means a BAPI is unique to a Business Object, for example a Sales Order, and does not contain a commit function.

http://help.sap.com/saphelp_spm21_bw/helpdata/en/5c/f3f0371bc15d73e10000009b38f8cf/frameset.htm

SAP delivered Business Add-In's  used to customize SAP ERP components for SAP Industyr solutions and country variants. Also available for customers and partners for project-specifc enhancements.

So far there have been 3 levels of evolutions for BAdi’s:

• Up to R/3 4.6 - UserExits,

• R/4.6 to SAP NetWeaver 7.0 Classic BAdi's,

• From SAP NetWeaver 7.0 onwards "new" BAdi's

http://help.sap.com/saphelp_spm21_bw/helpdata/en/8c/c23a42949fb56be10000000a155106/frameset.htm

http://scn.sap.com/message/10791531