Workarea architecture for SF, C4C and Concur with SAP Companion

[Andrew86]

Hoping I could get some suggestions on how to determine the Workareas needed and the configuration required for the following scenario which I think probably quite a few different companies are in.

• Enable Now recently deployed
• SF EC presently being designed and developed (separate SF tenants being used aside from BAU tenants)
• Concur deployed
• C4C for Service deployed
• An S/4HANA programme will be underway in the coming year.
• Desire to use SAP Companion for In-App assistance for all technologies above. Additional Enable Now training material to be produced and offered out via SAP Companion and other means.
• No dedicated fulltime individual tasked with maintaining learning material on an ongoing basis. Maintaining consistency in output (look and feel) and the approach and processes adopted should be relatively straight forward without no complex publishing process required.

Questions:

1. Can all SAP based training material (SF, C4C, Concur, S/4HANA) be extracted into 1 Connected Workarea? Is this a good approach?
2. Is it better to have one SAP Companion Instance/Workarea for all the technologies listed OR have individual SAP Companion instances per technology i.e. Each technology is connected to a separate workarea to act as the SAP Companion.
3. Is it good practice to use an Extended Workarea as the SAP Companion instance?

Any thoughts or recommendations would be greatly appreciated. Many thanks, Andrew

[labutale]

Hi Andrea, I have a question for you. Our company is in a similiar journey with our recent deployments and projects leading up to S/4 Hana.
For C4C for Service - have you been able to configure the SAP Companion with your work area and custom content? If yes, how? We're running into some dead-ends with our configuration sprints.

[Andrew86]

Based on the advice from Dirk, we are using an Extended workarea based on C4C SAP based content. Initially on our Dev instance of C4C, I configure the following settings yet I am likely to amend to accommodate additional parameters available.

[DirkManuel · Accepted solution]

It's 100% possible to have all applications pointing to the same Workarea (and this be the same one containing the learning content). However, I generally advocate having separate Workareas for help vs. training for a number of reasons: (1) it is tidier (vs having all your help content cluttering up Unsorted in your training Workarea); (2) it makes it easier to carve out maintenance of the help content to a separate team' (3) SAP Companion has 2 separate parameters for these anyway, so clearly they thought it was a good idea...

I personally would advocate having a separate Workarea per application, as (1) It makes it easier to update the Versions en masse as you can just select everything vs. having to select help projects per application; (2) it makes it easier to carve out maintenance to separate teams per application (including security). (3) Extensibility: You can only base one Workarea on one other (see last point below)

You only want to use an Extended Workarea if you want to provide access to the standard help content AND augment this with your own content or changes. If you do want to do that then yes, you definitely need to use Extended Workareas. As noted above, though, you can only Extend one Workarea on one other, so if you have a single Help Workarea, you can base this on the S/4 standard content Workarea, or the SF standard content Work area, or... etc. So if you want to have the standard help content for each application to be available, you will need to use separate Workareas for this. And then you potentially have the same problem with Learning content...

These are just my views. There are multiple ways of working things, depending on how much effort you want to put into the set-up and maintenance.

[Andrew86 · Accepted solution]

Many thanks Dirk, your insight here is very much appreciated. I think it has provided some clarity that i needed.