Naming Convention for Spaces (&Pages) in the context of SAP BTP Launchpad Service

[former_member596519]

Dear Community,

• the apps / tiles users have to access to fullfil there daily work could, span between various systems (maybe even several different S4H, MDG, HR, Ariba, GRC etc. & eventually "Non-SAP"-Systems)
• therefore, we are currently implementing the SAP BTP Launchpad Service to serve as central launchpad, integrating several different systems, by displaying tiles from these different systems in the very same Fiori Launchpad
• as for the content stemming from SAP-systems, as we know, the tiles are arranged in Spaces & Pages, which will then eventually be deployed to the BTP
• Imagine a drastic situation: a clerk working in multiple S4H ERP systems, in the FI area, having to execute tasks using the same apps in those different systems.
• The question is now: How would this user be able to easily distinguish the "source-system" of these apps/spaces etc.? Is there any recommendation / SAP's best practise / thoughts out there, regarding this? E.g. by introducing a naming convention for Spaces & Pages with this regard? If so, how should it be? "Technical", SID_<the usual space name>? Or rather something more self-speaking, not so technical? Or is there another way of providing the distinction (by a sort of navigation)

As explained, I do not talk about "obvious" situations, e.g. a manager working in procurement area, has to fulfill tasks in procurement area, e.g. approve purchase requisitons, invoices etc. and also approve vacation requests (e.g. HR/MSS), where one would be easily able to derive the original system from which the spaces are originating, in which the user is currently working in.

Another, situation would be: somebody working in procurement area, and his work involves both apps from ERP and Ariba, but wants to have the mixed content merged into one Space.

Thank you upfront!

BR Aleks