Customizing table change on upgrade to CC4 ABAP 2.4.0

Owned by Peter Weigel
Aug 14, 2024
1 min read

Issue

The order of the fields in table /XALM/CC4_SFM_T1 got changed. The language field is now the second key field.

Cause

All data will be kept during import of new version. The table change will be done automatically without loosing any data.

But: If you have open or unimported customizing requests changing the description of an CC4 configuration profile, you will face issues caused by the key changed.

Solution

Please release the transport request before importing the new version. Please import this customizing transport request to production before performing the upgrade there.

Alternatively keep the transport request open during upgrade. After upgrade, please remove the invalid keys from your customizing transport request and add the new keys to your customizing transport request using the transport feature of transaction SM34.