SAP FSM - Change of behavior for released Servicecalls and Activities on reassignment

Dear Customers and Partners, 


With the 2205 release (scheduled for May 2022), SAP will change the behavior for released Servicecalls and Activities on reassignment to a new Technician. This only applies to manual reassignment on the Planning board.
Reassignments through the Auto Scheduler/Optimization engine are not affected.

Current behavior: Released Activities that are reassigned to a new Technician and then released are copied to the new technician, while the old activity gets marked as cancelled. The full information Activity is retained. This behavior only holds true for Manual reassignments on the Planning board.

Future behavior ( Release 2205): Release Activities that are reassigned and released to a new Technician are directly assigned to the new technician, no copy is created.

Potential impact: Any Non-Standard integration to ECC, C4C might be affected if they rely on the coping of the Servicecall/Activity including Business Rules relying on the copy of an activity.


Reason for change: To unify the behavior of the Auto Scheduler/Optimizer and the Manual Planning.


Further information can be found in the SAP FSM documentation.


In case of questions regarding the changes, please contact our Support using the helpdesk.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


  • Hallo Karsten
    Kannst du mir bitte das Datum angeben für den beschriebenen Release 2111?
    Danke und Gruess Bruno

    Comment actions Permalink
  • Hallo Bruno,

    gemäss der Dokumentation ist 2111 aktuell für den 12. November 2021 eingeplant.

    Einsehbar ist dies in der SAP FSM Dokumentation:

    Beste Grüsse

    Comment actions Permalink
  • Hi Karsten, we are wondering why this change was moved from 2111 to 2205 and if it is really coming in 2205. We are having some business rules and one custom iFlow that relies on the activity ID. Regards, Florian

    Comment actions Permalink
  • Hi Florian,

    please note the following from the SAP documentation linked above:

    - The feature was initially planned for 2111, but moved to 2205 because of a higher level of complexity and the feedback received from customers seeking for more time to harmonize the integration in order to support the new behaviors.
    - With 2205 release, customers will be able to switch between the old and new behaviors for a time period of 3 months. During the 3 months, customers can harmonize the integration, adjust non-standard integration, and adjust business rules to support the new behaviors.
    - After the 3 months, the new behaviors will be effective by default.

    So far 2205 is the expected date and we have not yet received any information that this will change.
    If the release does not include this change in behavior, we will inform you in this post.

    Best Regards

    Comment actions Permalink

Please sign in to leave a comment.