Multiple S/4 Hana versions/instances (on premise) and connected/extended workarea recommendations?

[Wallace]

We’re excited to start our SAP Companion journey and see the possibility of having multiple Production S/4 Hana instances on different releases (we are on-prem with S4 at this time).

I searched the community, found this blog: https://blogs.sap.com/2020/12/10/sap-enable-now-web-assistant-working-with-extended-content/ (some time after it was first posted and I asked a question from a different frame of view). I looked at the SAP Companion Integration Guide: https://help.sap.com/doc/74bfd245cde048458458f6df5d5cb567/2206/en-US/SAP_Companion_Integration_Guide... as well as this video from the SEN community page: https://sapvideoa35699dc5.hana.ondemand.com/?entry_id=0_s2mjv593

As we start to plan structure and setup using SEN Cloud for our SEN, I feel we should be running multiple sets of connected/extended workareas for the different solutions/Productive S4 instances to allow for flexibility and differing content for the different solutions.

I’m searching for recommendations, to try and establish the initial structure/way of working orderly/clean where possible and to avoid future confusion and rework/restructuring.

Grateful for any thoughts/guidance.

Best Regards,

Wallace

[DirkManuel · Accepted solution]

My recommendation is usually one Workarea per application type. One per version may be advisable for ongoing maintenance, but only if you never expect them to eventually synchronize to the same release. For Connected/Extended, you only need one Connected Workarea (per app type) and can Extend this to multiple client Workareas if you happen to go down the 'one Workarea per version' route.

[Wallace]

Thanks Dirk!