Skip to Content

material master data with different language description as mandatory field

Feb 12 at 07:02 PM


avatar image
Former Member

Hello Guys,

my question may seem strange but it has a valid business scenario.

while creating the material master i want the material description (MAKTX) for a second language key (Arabic) to be proposed as mandatory field and vice versa.

so whatever is the user logon language i need two language description as mandatory

i understand this cant be achieved by field selection group because i am asking for a default value with a duplicated field name - the standard description (MAKTX) with the default language (EN) is already mandatory- so i am stuck in a loop.

maybe this is done outside of MM configuration but it can ensure the ease of access to some users who cant understand English.


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Jürgen L
Feb 12 at 11:12 PM

the maintenance of material masters should be limited to a few people who understand what is required or can at least follow instructions.

There is a user exit for the material master and an ABAPer can add a small check whether the language was maintained and if not then an error message is send and the material can't be saved.

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

i agree that master data owners should be folks who understand SAP best practice and know what they are doing.

but the option to get a mandatory field for different language is a more reliable way to secure the system before we deliver it to the client.

So there is no standard solution for this, is there any workaround for this !


I think I told you already what can be done.

alternative from stopping the user to save "incomplete" material masters you can as well download the MAKT table and analyze with MS Excel formula VLOOKUP for which material the desired language is missing. More convenient if an ABAPer would create a report for such analysis.

What other workarounds would you expect?