Skip to Content

Classification defaulting in MDG custom create material change request.

Dear All,

Classification is defaulting in MDG custom create material change request. Can anyone please let me know, what are the ways these could have been achieved, I need to disable this. I'm unable to figure out how this has been done previously. The MDG version is 7.0 .

Any help would be sincerely appreciated.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Aug 24, 2015 at 03:56 PM

    How does it behave in MM01? The first place to look to see if the behavior is the same as in the standard MM01 transaction. If they behave the same, you should change MM01 first. If they behave differently, only then, you should look into changing this in the MDG space.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      I think Tushar's problem is the opposite. His Classification view defaults data that he does not want to. So, it seems that he would really like the behavior described in the OSS note to actually work.

      In any case, if you can (or have someone who can) debug Native Web Dynpro applications, you should be able to find where the defaults are coming from.

      Do you know if someone already modified/enhanced the classification WDA application? If so, you might want to check with them.