Thanks for this idea Maria! We and a lot of other implementation partners and customers all still have the same issue and I had created the following post in Viva Engage lately and was told to create an idea, which, as I found out, is already existing. Therefore I create this comment with the detailed info from my Viva Engage post.Weber, Jürgen on Viva Engage: "Multiple usage of the same operation in one route" Posted in Manufacturing on Jan 7, 2026Multiple usage of the same operation in one routeWe have again the issue that we can not use one and the same operation multiple times within one route, because if we do that fields and setups like the run time and the resource are always the same for each of the operations.This restriction however only applies when we setup the route under "All Routes" or directly from the released product. Here the following underlying tables are involved - Route, RouteOpr, ProdRoute, Once we have the production order created the behavior for the individual route of the production orders is different! We can e.g. enter further new operations with the same operation ID and indicate different run times and resources. Now we would like to get rid of this limitation already with the setup of the base data. The workaround to name the operation IDs with a pre- or suffix Number is suboptimal. Are there any other workarounds that we are not aware of or have any of you customized that behavior already? Or is perhaps MSFT thinking about improving this behavior in a future release?Thank you very much!