alm-ts-backend vs alm-ts application roles

[Boglarka_Takacs1]

Hello All!

By now, I think I understand the meaning of the role templates for alm-ts which is for the SAP Cloud Transport Management application itself and from which 3 role templates are node specific (Export/Import/Transport Operator) which we have to create manually as per our nodes and need:

What I am not sure about is the same role structure for application alm-ts-backend: do we really need to manage transport mgmt related authorizations of the backend systems here on the BTP Cockpit? What happens if I do not provide access to those roles only for the ones under alm-ts itself?

Can you please direct me to the proper documentation explaining this? All I checked so far is the SAP Help document which is quite clear about alm-ts roles but I am in the dark with alm-ts-backend application roles. Also to understand what exactly alm-ts-backend mean and what is the deifference between alm-ts and alm-ts-backend applications from TMS perspective?

Setting Up Role Collections | SAP Help Portal

#SAP Cloud Transport Management

[Henry_Banks]

Hi @Boglarka_Takacs1 

the feedback we got via support ticket so far was: 

 the cTMS is SaaS Application consisting of different modules. So, the "alm-ts" roles are the ones which a business user needs to work with cTMS UI (frontend).

The alm-ts-backend is used for the backend, so for example, you create a service instance of our "transport" service and use the OAuth2 client for direct API calls to the cTMS backend.

There are 3 plans for the "transport" service, which differ only in the "assigned" scopes (to an OAuth2 clientID). 

hope this helps. 

regards, H 

[RaviRIyer]

Thank you for updating this with details.