MAM Server Driven replication - multiple clients, only one linked to MI

[Former Member]

Hello,

We use server driven replication for MAM30_030, MAM30_031 and MAM30_050. I had to use BADI ALM_ME_SERVERDRIVEN to delete the OBJECT_KEYS when the objects were changed in a client that is not linked to the Middleware.....

Is there a clean solution for this problem? I had to create a Z-table to store the client I want to allow....

Kind regards,

jeroen

[Former Member]

Hi Larissa,

Problem is that there is only 1 middleware client and multiple backend clients. The real problem is that customizing via transaction FIBF is client independent.

We have clients 110 (Unit Test) and 210 (Sandbox). We only want data from client 110 to be replicated to the MI middleware. When we change for instance a work order the partner, functional location and equipment are sent to the middleware. This is true for both clients...

So in my opinion you should decide already on the backend if you send the trigger to the MI middleware or not.

Kind regards,

jeroen

[former_member304703]

Hi Jeroen,

the only other solution I see (and I will not call it clean by no means):

1. Change variants on the backend to return empty list

2. call transactions used for initial replication (and with them you can specify an RFC destination of a specific MI server)

3. Mark "with deletion" flag

The other thing I would try and that would be clean:

on the desired middleware se37 -> MEREP_RDB_T01_RESET.

FM implies T01s, not T51s but in a way there is absolutely no difference fo MI between them excpet how records get updated from the backend.

I have never tried any of this solutions but your question made me think what is a possible solution.

Please let me know if you tried any of those options.

Regards,

Larissa Limarova