Showing results for 
Search instead for 
Did you mean: 

Define APO Release (Transaction code:NDV2) does not contain value 70

Former Member
0 Kudos


We are working with ECC 5.0 and SCM 7.0.

When I try to set the APO release to "70" in transaction NDV2, it says that the highest possible version is "50".

In ERP, we have PI plugin version 2004_1_500 SP18.

Any ideas?

Kind regards,


Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

We have been live on SCM 7.0 for several months now with NDV2 set at 50 with no issues!

Former Member
0 Kudos

Thanks for the info Micky.

Do you also have a PI plugin higher than 2004_1_500 SP10 and are you also not able to select release 7.0?

I'm wondering if this is a bug...

0 Kudos

We have 2 connection R/3 systems.

One is PI 2004_1_46C: patch 0013, NVD2 set to 50 (although 51 is now available for some reason)

The other is ECC 6.0 so no plug in, NVD2 set to 51 (although 70 is now available I think since a recent upgrade)

As far as I know it is used in some cif code where it structures data differently for different APO versions, however this doesn't necessarily mean it won't work for your particular design is you dn't have 70 set in NVD2

We found a couple of issues due to using an old version of R/3 with the latest version of APO, but nothing we couldn't work around with cif user exits.

So in principle it's not an issue as long as you test everything thouroughly before go-live!



Answers (0)