cancel
Showing results for 
Search instead for 
Did you mean: 

MDG UI not behave not behave like the beckand

asher0668
Explorer
0 Kudos

HI

I set the flag in customization (t-code FBZP )"usage of payment method supplement" for company code 1005 but for company code 1114

i remove the flag.

in MDG backend (xk02) the field "payment method supplement" for company code 1114 is hidden

but in MDG UI the system behave differently ,the field "payment method supplement" is visible and the user can use it.

thanks

Asher Binhas

MM/MDG Functional

Accepted Solutions (0)

Answers (2)

Answers (2)

asher0668
Explorer
0 Kudos

Hi Saravanan,

thanks for your answer but in MDG UI it should behave as in the backend

in FBZP in set up all company code for payment transaction . The use is if you select this option, a payment method supplement can be predefined in the vendors of the company code.

i don't want the user to use payment method supplement in company code that im not Tick the box for payment method supplement

Saravanan_SD
Advisor
Advisor
0 Kudos

Hi Asher,

As mentioned in my previous comment, MDG UI and backend transactions will not behave similar for BP in all scenarios. This is the expected behavior of the MDG UI Framework for Business Partner.

Regards,
Saravanan

Saravanan_SD
Advisor
Advisor
0 Kudos

Hi Asher,

Please consider below restrictions on MDG UI for Supplier and Customer.

Field Groupings

  • Configure Field Attributes per Client
    In MDGS and MDGC this Customizing activity is relevant only for the column
Req. entry.

Restriction:

    In MDGS and MDGC you cannot use the following Customizing activities:
  • Configure Field Attributes per BP Role
  • Configure Field Attributes per Activity
  • Configure Field Attributes per Business Partner Type

It means MDG UI and backend transactions will not behave similar for same configurations. In such case, implement Field Property Badi to control the field property on MDG UI.

Regards,
Saravanan