topic Re: Material Update (MARC) in Application Development and Automation Discussions

Material Update (MARC)

former_member3003 — Mon, 20 Jun 2022 07:15:22 GMT

Dear colleagues,

Material is available in 2 plants (for example, A and B). User goes to MM02 (plant A) and changes a field (f1) on the tab Basic Data (table MARA). But this field (f1) affects on a plant-field (f2) for both plants (table MARC). How can we update the field (f2) for both plants automatically?

Best regards,

Dmitry

Re: Material Update (MARC)

former_member620069 — Mon, 20 Jun 2022 08:01:55 GMT

Use: BAPI_MATERIAL_SAVEDATA

Re: Material Update (MARC)

former_member3003 — Mon, 20 Jun 2022 08:10:14 GMT

When do I have to call it? in V2 process after saving material?

Re: Material Update (MARC)

venkateswaran_k — Mon, 20 Jun 2022 08:23:20 GMT

Can you please explain

1. Are you using MM02?

2. Which fields - you are trying to change?

Re: Material Update (MARC)

former_member3003 — Mon, 20 Jun 2022 08:55:24 GMT

1. yes, we use MM02

2. we change MARA-Zfield1 which trigger a change MARC-Zfield2 for all plants. how to update MARC-Zfield2 after saving MM02?

Re: Material Update (MARC)

RaymondGiuseppi — Tue, 28 Jun 2022 13:17:27 GMT

Did you look for a BAdI (such as those of Enh. spot ES_SAPLMGMU) an Exit (such as EXIT_SAPLMGMU_001) or a BTE (such as 00001250) to trigger an execution of (example) BAPI_MATERIAL_GETLIST, BAPI_MATERIAL_GET_DETAIL, BAPI_MATERIAL_SAVEDATA, BAPI_TRANSATION_COMMIT/ROLLBACK wrapped in a RFC enabled FM called in background task/unit to change/adapt related records after the transaction commit?

Re: Material Update (MARC)

former_member3003 — Tue, 28 Jun 2022 13:58:00 GMT

Hi, yes, this is I am going to do. Is this only solution?

Re: Material Update (MARC)

RaymondGiuseppi — Tue, 28 Jun 2022 16:00:47 GMT

There are many solutions, but this one is relatively simple and robust (in fact, a transaction like MM02 can only lock one MARC record at a time, so you'd have to twist it to get it to do the job...)