sap-docs / btp-best-practices-guide Goto Github PK

https://help.sap.com/docs/btp/best-practices/basic-platform-concepts

Is the diagram still correct? A global account doesn't have a region according to my understaning (at least it cannot be chosen).

In addition, with hybrid global accounts it can also support two license types: subscription + CPEA/PAYG.

https://help.sap.com/docs/BTP/df50977d8bfa4c9a8a063ddb37113c43/cbd76632d8aa4cb7bbf175d7607db463.html?locale=en-US

The learning journey seems to be outdated. Why not refer to https://learning.sap.com/learning-journey/discover-sap-business-technology-platform/get-an-overview-of-the-intelligent-sustainable-enterprise ?

https://help.sap.com/docs/btp/best-practices/basic-platform-concepts

Hello SAP docs Team,

short question regarding the figures "Overview of Global Accounts and Subaccounts (Feature Set A)" and "Overview of Global Accounts, Directories, and Subaccounts (Feature Set B)".

There is is mentioned that you can only have 0-1 business user IdP per subaccount. If I am not mistaken this is wrong and technically you can have multiple and as a result will get in the application then in the login screen the possiblity to choose from the IdPs. Or am I missing something here?

Best regards,
Raphael

https://help.sap.com/docs/btp/best-practices/security-concepts?locale=en-US&version=Cloud

In section Identity Management and Authorization Management, I find it hard to keep an overview on the different services mentioned in prose text. My brain would prefer a list or potentially, two (for Authentication / Authorization), not quite sure.

• SAML
• OpenID Connect
• SAP ID Service (with SAP Universal ID?)
• Own identity provider
• SAP Cloud Identity Services - Identity Authentication.

The provider/subscriber approach is one of the important scenarios that that are supported with multitarget application.

There are two that here, one of them should be removed.

https://help.sap.com/docs/btp/best-practices/setting-up-authentication

According to slide 20 of the SAP S/4HANA Cloud 3-system landscape - Onboarding Guide, SAP recommends to connect the non-productive IAS to the non-productive S/4HANA Cloud environments and the productive IAS to the productive S/4HANA Cloud environment and CALM.

Unfortunately, we cannot find any clear recommendation for the IAS setup for BTP. Do you recommend the same setup here (non-productive IAS for non-productive subaccounts, productive IAS for productive accounts)? Even for dev or test environments, we work with ‘productive’ identities. For this reason and from our point of view, these subaccounts should be connected to a productive IAS or at least the productive Azure AD. According to our experience, the non-productive AD is usually just used for internal testing purposes and never connected to any enterprise applications.

If this is SAP’s recommendation, this also means that the configuration effort for groups and groups assignments doubles compared to the setup of just using the productive IAS for all subaccounts that we usually see. Or is there any transport mechanism for delta changes planned from one IAS to another that could reduce these efforts? Alternatively, the groups could be assigned in AD, but as of our understanding SAP’s strategic recommendation is to assign the groups in the IAS and not in AD, is this correct?

In context of SAP BTP, it is mostly referred to a Availability Zone or Region. Also as we refer to Multi-AZ set-up for services etc. So maybe I would be better understandable than talking of "data center". Also a section with more detailed guidance on how to set up a high-availability and a disaster recovery in BTP Multi-Cloud would be helpful.
https://help.sap.com/products/BTP/df50977d8bfa4c9a8a063ddb37113c43/df972c5529004c428e05a90966d17dca.html?version=Cloud

https://help.sap.com/products/BTP/df50977d8bfa4c9a8a063ddb37113c43/cbd76632d8aa4cb7bbf175d7607db463.html?locale=en-US

This Link leads nowhere: Getting Started Checklist/ Step 2: Use Cases on SAP BTP https://help.sap.com/docs/link-disclaimer?site=https%3A%2F%2Fwww.sap.com%2Fproducts%2Fbusiness-technology-platform%2Fuse-cases.htmll
Because there is an additional 'L' at the end of the link that shouldn't be there. ('.htmll' should be '.html')

https://help.sap.com/docs/BTP/df50977d8bfa4c9a8a063ddb37113c43/fdeddf22a6964d86a199b9eb11c7075e.html

It might make sense to rename "Cloud Administration Team" to "Platform Engineering Team". It is a pretty widely-used name nowadays and the description of the tasks fit exactly to the definition of a "Platform Engineering Team" - enable the Cloud Development Team to do whatever they want to do.

https://help.sap.com/docs/BTP/df50977d8bfa4c9a8a063ddb37113c43/765423ddb66147bc8141607a8522fe65.html

Hi, I think this page is helpful, but it could use some attention from doc developers. The descriptions of the methods are quite sparse and this page could be rewritten in a way that is more helpful for people who don't know all the concepts mentioned there already. Probably a table is not the best structure element for this kind of documentation.

I'd prefer this page to have a section for each method where a bit more details are explained about what the method is and which fields / information need to be configured for destinations with that given method.

Best,
Florian

https://help.sap.com/docs/BTP/df50977d8bfa4c9a8a063ddb37113c43/b5a6b58694784d0c9f4ff85f9b7336dd.html

Best practices for Kyma would be a great addition.
Some ideas:

• what is the impact on the proposed Subaccount structure when using Kyma
  - instead of or
  - in addition to CF
• What is the proposed namespace structure (when to use a new namespace)
• naming conventions
• etc.