After the BW version 7.3 SP5 we can run SAP BW on SAP HANA platform , before migrate our SAP BW to new HANA platform , SAP recommendation is using the following new ABAP sizing report to calculate new machine specifications.

You can find the information about which Kernel version is required with which NW release and which NW SP Stack in this post , also the maintenance of each NW Kernel version ends and which higher Kernel version is available as DCK – “Downward Compatible Kernel” in order to apply Kernel patches.

If you want to install “HANA System” on your SUSE Linux installation , then you should select the following “Software’s” according to related SAP OSS notes while your Linux system installation is running.

If you want to download “SAP HANA Edition 1.0” or “Support Packages and Patches” then you can follow the below steps to get those files and get some summary information regarding “SAP HANA Server Installation Guide” document.

If you are getting an error or warning messages like “Inconsistency detected in tables…” then you can easily check the system situation regarding to this message with transaction SM65 (Background Processing Analysis Tool) with following features…

If you are getting an error like “Name or Password is incorrect” for “Workflow_Local_<ClientNumber>” on TRFC (Transaction SM58) then you should check the Workflow_Local_<ClientNumber> RFC connection on transaction code SM59.

If you are getting an error message like “Error : n entry found in buffer with no data file(s) transferred yet. Import has to be stopped!” while trying to import a transport request via STMS then it’s better to check this article before trying to find a solution…

If you are getting an error message like “Error : n entry found in buffer with no data file(s) transferred yet. Import has to be stopped!” while trying to import a transport request via STMS then it’s better to check this article before trying to find a solution…

If you are getting the error “AIF is in undefined state, that is not safe to be upgraded…” during the SUM upgrade process runs, then you should follow this post steps and reset the SUM to eliminate the situation…

If you want to check you SAP java system availability then you can easily use the function of the “JSMON” feature, you just need to connect your system over the operation system and use JSMON command to get detail information…

If you are getting the error message like “SAPOSCOL not running ? (shared memory not available )”when you are trying to access transaction code ST06 then you should check the “saposcol” situation over the OS level.