Nakisa 4.1 upgrade and customer specific infotype

[Former Member]

Hello,

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.

[StephenBurr]

Since Nakisa is not SAP, they have used 9xxx infotypes for adding custom infotypes where required to support functionality in their solution extensions. I believe the transport listed was provided by Nakisa.

Infotype 9820 is Target /Activity Type.  The infotypes used are listed in the Addon PDF in the downloaded package (e..g "AddOn_VSN41_ECC6_EhP6-7_Install.pdf").

Are you saying that you were already using 9820 at your client for something else?

Stephen

[Former Member]

Yes, 9820 is already used here but as a PA infotype (for time management related data).

Hopefully, we have a work around which is re-overwriting the Nakisa infotype with ours.

Anyway, I find it unusual to use a custom infotype for Target/activity type since a standard object exists since 4.0, 63 and 64.

[StephenBurr]

9820 stores additional information for these objects that aren't found in infotype 1000.

I agree it is frustrating that this occurred in your scenario (where 9820 already in use).