Material Update (MARC)

[former_member3003]

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

[former_member3003]

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...)

[former_member620069]

Use: BAPI_MATERIAL_SAVEDATA

[former_member3003]

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

[venkateswaran_k]

Can you please explain

1. Are you using MM02?

2. Which fields - you are trying to change?

[former_member3003]

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?

[RaymondGiuseppi]

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?

[former_member3003]

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

[RaymondGiuseppi]

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...)