NDV2 inconsistency

[b_valavan]

Hi Experts,

Need some insight / information of NDV2

In ECC system we maintain the release information of the connected APO system via transaction NDV2. If this release information is incorrect what is the impact ? i.e if the connected APO is in SCM7.0 EHP3 , but the release in ECC is maintained as 5.1 what are the possible impact to CIF / integration ?

based on some initial search, i found the way the CIF structures will be modelled will vary depending on the release information maintained here. Do we have any further information ?

Regards

BVN

[rupesh_brahmankar3]

Hello,

In ECC system, transaction NDV2, the SCM Release must be maintained

ECC system has options for SCM EHP in transaction NDV2

Like

70 Release 7.0

701 Release 7.0 EHP 1

702 Release 7.0 EHP 2

713 Release 7.0 EHP 3

Use the F4 Help for selecting the correct Release.

Please refer OSS consulting note

1223963 - CIF Customizing: SCM 2007 and ECC release lower than 6.0

If you use an R/3 (ECC) system with a release lower than ECC 6.0, you must maintain SCM 5.0  in transaction NDV2.

Best Regards,

R.Brahmankar

[alok_jaiswal]

Hi,

To add - In our system we are in SAP 7.0 - Ehp3. However in NDV2 in ECC release which is maintained is "70" only and not "713". However we have not seen any issues due to this and same is present in Production system too.

Regards,

Alok