MDG. How to turn off auto replication of materials

[Oleg_Turlov]

Dear SAP community,

Currently we have the following situation: When changing a material in MM02 or using MASS, IDOCs are automatically created and replication is performed. For change requests, the replication step is not added in BRF+, but replication is still performed automatically. If I add a replication step in BRF+, it is executed twice when the request is activated (two IDOCs are created with a time difference of less than a second for one material). How can I disable automatic replication, which is triggered by changes in MM02 or MASS? A similar question has already been raised, but the solution was not written: SAP MDG auto-replicating material to ECC via MM02 ... - SAP Community

[adityaIngale66]

Hi @Oleg_Turlov ,

You can check the following setting in DRFIMG to stop the auto replication.

In addition please check below link.

https://community.sap.com/t5/technology-q-a/controlling-data-replication-by-cr-type/qaq-p/10653650 

Best Regards,

Aditya

[Oleg_Turlov]

Hello Aditya. I tried setting the "Other Output" parameter in DRFIMG, but replication was not performed even with the configured step in BRF+

[Saikat7]

Hello @Oleg_Turlov ,

SAP makes sure that the changes done in the MDG system are being replicated to the target systems.
Kindly check the below sap notes: 
https://me.sap.com/notes/2700769
https://me.sap.com/notes/3066745

The changes done via backend transaction (MM02/MASS, etc.) in a MDG or S/4 HANA system is replicated using BTE framework (either called via application MDGM or LO-MD) depending on the set up. This makes sure that your changes are synced across the landscape.

Question that you should ask yourself:

Why do you not want to replicate the changes done via backend transactions?

If you think that you want to place a hard stop on replication for changes done via backend transactions, then you might want to think about placing a control via an enhancement in the DRF outbound class for your implementation.

Regards,
Saikat.

[Oleg_Turlov]

Hello

[Oleg_Turlov]

Hello Saikat. Thank you. I looked at these notes. I also looked at the documents: https://d.dam.sap.com/x/MPGHrJo/How-To%20Using%20Data%20Replication%20Framework%20for%20Material%20V... There is nothing specifically about disabling replication triggered by changes in materials. Regarding your question "Why do you not want to replicate the changes done via backend transactions?", there are several reasons. With mass changes, IDs are automatically created not by the number of changed materials, but by the number of changes in each material. That is, when changing 10 materials, we can have 1000 IDs of the MATMAS type. There is also a problem that I wrote about above, when adding a replication step in BRF+, double replication is performed: automatic and in accordance with the step in BRF+, this is very annoying

[Saikat7]

@Oleg_Turlov: You should not configure the replication step in the BRF+.

[Saikat7]

@Oleg_Turlov: You should not configure the replication step in the BRF+. The replication framework automatically gets triggered with the activation of change request.

[Oleg_Turlov]

I want to add background steps to BRF+ that will run after activation but before replication. In testing, auto-triggered replication was performed before the background step

[Saikat7]

Oleg_Turlov: Then multiple replications would get triggered.

[Saikat7]

Oleg_Turlov: Replication is supposed to be triggered at the last step. If you keep the replication step in BRF+ then multiple replication is bound to trigger. You then need to explicitly control that via enhancement.