Sandra Rossi It's not working in one scenario and we have an open OSS incident with SAP for the same, they came back and said, the Receiver Type should be populated without giving any other info as to what the value should be for the Receiver Type, here is the scenario:

"In the Service Cloud, a move out is triggered by adding a new address, flow comes to ISU-ECC, the new address for the BP gets updated in the ISU side but the delta replication doesn't get triggered to send the updated address back to Service Cloud to be replicated in BP."

As a workaround, we have written a custom code(basically calling the standard delta replication report from the BADI) to make it work until we find the root cause as to why this program doesn't get triggered from the Change Event config in SWE2.

We have responded to SAP with the same and awaiting their response. In the meantime, I wanted to ask this question to understand the purpose of the Receiver Type field when using class/method to handle the events.

I have gone through the code in a debugger and didn't find any reference to the Receiver Type.

Then your question is not that clear, quoting you: "it's triggering without any issues even with Receiver Type left as blank".

So, SAP said it's mandatory. If you indicate DUMMY (or whatever), does it work now?

If not, as you are talking about "standard delta replication report from the BADI [...] Change Event config", please add all the details to your question (or ask a new one if you prefer).

Sandra Rossi I have edited my question to include the one scenario where it's not working, thanks for pointing that out. However, I am not asking here to resolve or find the root cause of this scenario, the question I am asking is whether it's mandatory to have this field populated when using class methods as event handlers.

Thanks