Hi Martin,
I am completely with you!
I have known about this remote trusted navigation targets for some time in single roles, but when I noticed it in composite roles on CUA I thought (initially) it might in fact be a logical system assignment of the single role under the composite -> that would have been interesting. Hence my question whether it is an intention for a "Business Role" definition centrally (in the same sense as IDM systems have it).
But it is not the case as it turns out. It is menu synchronization between (incompatible) component systems of different types with prerequisites which are hard to achieve. Much too clever even if the theory works.
S/4HANA: Yep, I am also watching it. Customer often kept separate regional systems and HR separate as well because the development and patching cycles are different and the customizing is different because the business processes are different. Good point! The data model even changed in S/4HANA so the customizing options might have relaxed to consider local requirements which did not fit into the same box before. I have several international customers on EHP7 now rolling in the US, Asia, Zimbabwe and even Italy to the same system... ;-) Local requirements are more reporting related and less customizing that interferes with others. Roles are more complicated as some use release codes on purchase requisitions and others on the purchase orders, Others want a 3 way match, others 2 way match, and in Timbuktoo there is only 1 person so even workflow and UWL is not an option.
A nice thing about S/4HANA is that taking all old Z-programs with is not an option. Only a handful that are API based. Updates to SAP tables are also blocked technically now (I tried - it did not work with ABAP native commands).
Interesting challenges for sure, but correct way to go IMO.
But back to the original topic: Did anyone ever try this remote menu synchronization and navigation via single or composite roles? Did it live longer than you?
Cheers,
Julius