Nakisa 4.1 upgrade and customer specific infotype
We recently started to upgrade our Nakisa 3.0SP3 to the latest 4.1.
We started with the back-end development system (ECC6 EHP6).
The basis team installed the most recent add-on and transports from SAP service market place.
After the installation, we noticed that our customer specific infotype config had been overwritten by the transport (B65K900662 MKUMAR SVN 4.10 development config AOU). Our impacted infotype is 9820 but the transport also contains config for 9821, 9822, 9823 and 9824.
After talking to some SAP specialist, this is really not a good practice since customer specific ranges are reserved for customers (and vice versa, standard ranges are reserved for all SAP standard).
We have raised an OSS but I wanted to warn community members to be very careful with this Nakisa version.