We faced an intriguing issue after our BW on HANA migration, wherein the Inventory InfoCubes conversion to HANA-optimized, failed.

This issue can, most likely, occur in other BW on HANA migrations and that is what prompted me to put forth this document which aims to

provide a way out for such scenarios, for my fellow BW consultants.

Context:

Converting Inventory Stnd InfoCubes to HANA-optimized InfoCubes.

Scenario:

Migration already completed to a HANA multi-node appliance.

Inventory InfoCubes still contain uncompressed, delta movement, requests.

Compression doesn’t work anymore, after migration, for multi-node (scale-out) systems.

Conversion process (RSMIGRHANADB) fails for these Inventory InfoCubes due to uncompressed requests.

InfoCube:

ZMIM_C001 – Inventory InfoCube.

The current state is that the system is already migrated to BW 7.4 on HANA SP10 and the Inventory InfoCube still contains few uncompressed requests.

These are delta movement requests. No historic movements requests.

Pic 1.png

Although the system is migrated, the InfoCube is still not converted to HANA-optimized.

Pic 2.png

We also made sure that this is an Inventory InfoCube with non-cumulative measures (Key figures):

Pic 3.png

First attempt to convert to HANA-Optimized InfoCube:

Pic 4.png

System issues an error message stating that the Inventory InfoCube must be fully compressed before the conversion:

Pic 5.png

Therefore, we attempted to compress the requests in the InfoCube:

Pic 6.png

Unfortunately, compression is no longer possible and system issues an information message that

No compression possible for Stnd InfoCubes in scale-out (multi-node) HANA systems:

Pic 7.png

Upon searching, we found the SAP Note confirming this limitation in a BW on HANA scale-out landscape

Pic 8.png

Therefore, even though the job completed successfully, it didn’t compress the request.

Pic 9.png

After perusing through multiple documents and notes, we found the panacea in the form of a tweak which needs

to be done in the RSADMIN table to force the compression to work.

Source: SAP Inventory – First Guidance doc for BW 7.4/7.5 on HANA

As per this document, we found the following important points, relevant to our scenario:

Post-migration, if you want to convert the Inventory InfoCubes without compressing the open delta movement requests* then:

Set the RSADMIN parameter FORCE_NCUM_CUBE_CONVERSION to value ‘X’

* If you have uncompressed Historic movements requests, you have to mandatorily compress them before the conversion.

Best Practice:

Post-migration, if you want to compress all the open requests and then convert the Inventory InfoCubes (which we should) then:

Set the RSADMIN parameter FORCE_NCUM_CUBE_COMPRESSION to value ‘X’

Don’t forget to:

Remove these RSADMIN parameters after the conversion/testing is done.

We followed the second (best practice) approach of first compressing the requests and then converting the

Cube to HANA-optimized.

First, we checked if the entry already exists in the RSADMIN table or not:

Pic 10.png

To insert the parameter, execute pgm: SAP_RSADMIN_MAINTAIN

Pic 12.png

Set the below parameters:

FORCE_NCUM_CUBE_COMPRESSION

value ‘X’

Pic 13.png

Pic 14.png

Confirmation

Pic 15.png

Now, we attempted to compress all the requests, one by one, and it completed successfully !

All requests successfully compressed:

Pic 19.png

Lastly, we attempted to convert the Infocube to HANA-optimized and it completed successfully !

Pic 20.png

We checked and found that the InfoCube is now HANA-Optimized:

Pic 21.png

As expected, the backend InfoCube tables structure confirms that only F table (No E table ) and Package Dimension table exist after conversion

Pic 22.png

Conclusion:

This tweak comes as a savior for the Inventory InfoCubes in scenarios depicted in this documented.

However, we should always try to compress the Inventory InfoCubes as part of pre-migration activities. This saves a lot of hassles.

To report this post you need to login first.

4 Comments

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

  1. Kiran Subramaniam

    Hello Debanshu,

    Thanks for the doc, very clear explanation of the issue and solution. I expect you face similar few issues post migration of Inventory Cube and you solve them and share your experience 🙂

    (0) 

Leave a Reply