topic Re: MM02 - Changes not updated for custom fields in Application Development and Automation Discussions

MM02 - Changes not updated for custom fields

Former Member — Fri, 07 Jan 2011 15:59:26 GMT

Hi,

I have added new fields in MARC and created custom screen for these fields in Material master.

Have written code in EXIT_SAPLMGMU_001 to update MARC table when changes are done in MM02 in these new fields

My code in EXIT_SAPLMGMU_001 updates MARC on save(with new values in screen); but then the update gets overwritten by value in variable MARC present in standard code( these are old values in MARC table for the new fields ) .

Basically , on save , changes to these new fields is not updated in MARC variable present in standard code.

Is there a problem in configuration ? IS there a differnet BADI/Exit to be used?

Thanks

Re: MM02 - Changes not updated for custom fields

Former Member — Fri, 07 Jan 2011 16:07:41 GMT

It's depends on how you've created your custom screen, I think you fill the correct structure you shouldn't use an extra-code to update table MARC

Max

Re: MM02 - Changes not updated for custom fields

former_member156446 — Fri, 07 Jan 2011 18:53:34 GMT

Can you change values of MARC in the user exit...?

Changing : MARU

Tables: STEXT

SSTEUERTAB

SSTEUMMTAB

WMEINH

SMEAN_ME_TAB

Re: MM02 - Changes not updated for custom fields

Former Member — Sun, 09 Jan 2011 16:32:17 GMT

Hi Thanks.

How may I fill the fields in MARC? I was hoping Configuration in SPRO and T130F will do the job, but that has not happened.

Thanks

Re: MM02 - Changes not updated for custom fields

Praveendsv — Mon, 21 Jul 2025 07:57:27 GMT

Hi Guys,

Is there any update on this issue?

We’ve added a new field to the MARC table, as well as to the BAPI BAPI_MATERIAL_SAVEDATA and the OMSR structure. This field has also been added to the MM02 screen. We’re able to successfully create new materials with this field populated.

However, for existing (older) materials, the field does not update. When we open MM02 and select a value for the new field, it appears to save correctly—there’s no error, and the system confirms the save. But when we reopen MM02, the field is empty again, and no data is written to the MARC table.

Do you have any insights into what might be causing this? Any help would be appreciated.

Best regards,

Praveen de SIlva