Impacts on change Event Reasons during a transfer

[JonasCosta]

Hello Experts,

I need to change an event from Transfer to Data Change type on my customer, but some employees have a current Transfer in progress.

What type of impacts can I expect if I change this event reason?

Another question is: the current starts of a temporary transfer is registered by a Transfer event reason, end the end of this mobility needs to be a Data Change, does you see any impact on this? The system will support this change? Or maybe I will have a pending Transfer change for that employees?

Thanks in advance!

JC

[JonasCosta · Accepted solution]

Hi Experts,

You can see the answer for this question here:

Case 543267/2025 - Change Event on Event Reason - SAP For Me

The impact of changing the 'return' event reason to be on the 'data change' event rather than the 'transfer' event will depend on your configuration and whether or not the 'transfer' event triggers the 'transfer' event in Intelligent Services.

From what I can see of our documentation, usually the 'Transfer' event is used to then trigger the business rule which triggers the 'Transfer' event in Intelligent Services, for job / position changes:

Transferring an Employee | SAP Help Portal

As such, if you are using this business rule and have it triggering when the 'transfer' and 'return' event reasons are used (or if it just checks that the event of the event reason being used is 'transfer'), then the 'return' event reason should be kept on the 'transfer' event so that it can continue to trigger this rule and the resulting 'Transfer' event in Intelligent Services. If you changed the 'return' event reason to 'data change' event and did not adjust the business rule accordingly, then it would no longer trigger the 'Transfer' event in Intelligent Services.

Additionally, while it should not have any real impact on employees who already have the event and event reason used, making such changes may cause issues down the line if you ever edit those employees' data with that event and event reason - Centralised Services has a big focus on data validation and data being correct, so if the event reason is moved from the old event, the system may trigger errors related to this down the line. As such, normally when customers want to make changes such as this, we would suggest that instead of moving the current 'return' event reason to 'data change' event, you should instead create a new event reason which can also be called 'return', and put it on the 'data change' event, and make the old 'return' event reason inactive so it remains configured correctly in the system and is just no longer usable, but can be turned back on at any time.

Best Regards,

JC