Problem statement: Hard dependency with SAP HANA SPSs and BI 4.1 SPs


Currently, from SAP BI 4.1 side, there is ‘one to one’ mapping with SAP BI 4.1 SP Vs SAP HANA SPSs. i.e. SAP BI SP releases are not forward compatible to SAP HANA SPSs – as per Product Availability Matrix (PAM).


Each time customer upgrades SAP HANA to a newer SPS version, it mandates SAP BI 4.1 upgrade as well to the supported SP. This constitutes a significant burden for our customers, sometimes it is a showstopper.


Proposed guideline and solution:

Teams internally did additional testing on the newer / previously unclaimed version combinations, to make sure SAP BI + SAP HANA customers will not have to go through this problem in future.


With this, there is a commitment from both SAP HANA and SAP BI team, for the compatibility between them.

For example, all the existing features from BI side will continue to work with new SAP HANA SPS version in this combination. Customer will get the support from SAP’s respective team to resolve the issue with the latest SAP HANA version, if there are any, while they continue with the existing SAP BI SP version in their landscape.


SAP BI PAM documents have been updated with this new proposal, i.e. all active SAP BI 4.1 SP lines will work with latest SAP HANA SPS release. Customer need not update the SAP BI 4.1 landscape, to consume latest SAP HANA SPS version.

Following is the model in which we are looking at supporting this combination. Please note that SAP HANA SPS10, and NEXT are not released as of now, so please use this as guideline only. (Refer PAM for actuals)

HANACompatibility1.PNG

Summary: In general, we would like to ensure the customer that ALL ACTIVE SAP BI 4.1 SPs will connect to latest SAP HANA SPSs. However, we advise you to continue using PAM document as THE reference for the support, to get the latest update on the versions supported and if there is any work-around needed.


To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply