Update from SAP DITA CMS (squashed):

commit b12d9063153d8dc821b0573c49d49a1375de6aa8
Author: REDACTED
Date:   Wed Aug 23 09:26:08 2023 +0200

    Update from SAP DITA CMS ( 2023-08-23_09:26:08 )

    Project: loioc2f780f61c744155b0bd42b6f38fb70c (jjq1673438782153.project)

    * Project map: loioc2f780f61c744155b0bd42b6f38fb70c (ece1671458061492.ditamap)

    * Output: loio2080d0faf9d84ce6aa14caa4caa32935

    * Buildable map: loio0fcfe38e11674227bb0a8d014337319b (cbd1671459393582.ditamap)

    * Language: en-US

commit b8d0f5a78daa3bb275e51adb03b6045f9c40b66d
Author: REDACTED
Date:   Fri Aug 18 01:46:36 2023 +0200

    Update from SAP DITA CMS ( 2023-08-18_01:46:36 )

    Project: loioc2f780f61c744155b0bd42b6f38fb70c (jjq1673438782153.project)

    * Project map: loioc2f780f61c744155b0bd42b6f38fb70c (ece1671458061492.ditamap)

    * Output: loio2080d0faf9d84ce6aa14caa4caa32935

    * Buildable map: loio0fcfe38e11674227bb0a8d014337319b (cbd1671459393582.ditamap)

    * Language: en-US

##################################################
[Remaining squash message was removed before commit...]

docs/10-concepts/entitlements-and-quotas-00aa2c2.md

@@ -34,9 +34,13 @@ An **entitlement** is your right to provision and consume a resource. In other w
 
 A **quota** represents the numeric quantity that defines the maximum allowed consumption of a resource. In other words, **how much** of a service plan you're entitled to use.
 
-Some service plans use numeric quota, which means that you can increase or decrease the number of units available in a subaccount. Depending on the service, these units represent different things and may impact the number of service instances, applications, or routes you can have in a subaccount.
+Some service plans use a numeric quota, which means that you can increase or decrease the number of units available in a subaccount. Depending on the service, these units represent different things and may impact the number of service instances, applications, or routes you can have in a subaccount.
 
-There are also service plans where the quota is shown as “limited”. The unit that is metered and billed for service plans with limited quota depends on the service. In that case, you can entitle that service to multiple subaccounts without having to worry about how much of it to distribute to each subaccount. You can think of assigning entitlements for such service plans as “enabling” or "allowing" subaccounts to use them.
+There are also service plans where the quota is shown as either "limited" or "unlimited":
+
+-   **Limited:** Service plans specified as "limited" have a predefined quota that is available to a global account and which can be shared across all its subaccounts. These plans are represented as "*<n\>* shared units" in the *Entity Assignments* page in SAP BTP cockpit. Each service defines its shared units and how they are used. Note that most multitenant SaaS applications are offered as "limited" plans with a quota of one unit because they're always limited to one subscription per subaccount. You can think of assigning entitlements for such service plans as "enabling" or "allowing" subaccounts to use them.
+
+-   **Unlimited:** Service plans specified as "unlimited" have no restriction on the quota that can be allocated per subaccount. This is typical of most services that are eligible to global accounts with a consumption-based commercial model agreement.
 
 For more information, see [Managing Entitlements and Quotas Using the Cockpit](../50-administration-and-ops/managing-entitlements-and-quotas-using-the-cockpit-c824874.md).
 

docs/10-concepts/kyma-functionalities-4b83be9.md

@@ -8,7 +8,7 @@ SAP BTP, Kyma runtime and open source project "Kyma" offer slightly different fu
 
 
 
-For all functionalities that the Kyma environment offers, see the official [project "Kyma" documentation](https://kyma-project.io/docs/).
+For all functionalities that the Kyma environment offers, see the official [project "Kyma" documentation](https://kyma-project.io/#/).
 
 **Functionality Comparison**
 
@@ -35,13 +35,6 @@ SAP BTP, Kyma runtime
 
 
 
-</th>
-<th valign="top">
-
-Comments
-
-
-
 </th>
 </tr>
 <tr>
@@ -65,13 +58,6 @@ Service Level Agreements
 
 
 
-</td>
-<td valign="top">
-
-
-
-
-
 </td>
 </tr>
 <tr>
@@ -95,13 +81,6 @@ Managed Kubernetes
 
 
 
-</td>
-<td valign="top">
-
-
-
-
-
 </td>
 </tr>
 <tr>
@@ -125,19 +104,12 @@ Managed Kyma
 
 
 
-</td>
-<td valign="top">
-
-
-
-
-
 </td>
 </tr>
 <tr>
 <td valign="top">
 
-Logging<sup>[1](kyma-functionalities-4b83be9.md#loio4b83be95f7db4fddba5c46d388ebf39a__ol_tcn_pdp_pvb)</sup>
+Monitoring<sup>[1](kyma-functionalities-4b83be9.md#loio4b83be95f7db4fddba5c46d388ebf39a__ol_tcn_pdp_pvb)</sup>
 
 
 
@@ -151,44 +123,7 @@ Logging<sup>[1](kyma-functionalities-4b83be9.md#loio4b83be95f7db4fddba5c46d388eb
 </td>
 <td valign="top">
 
-limited
-
-
-
-</td>
-<td valign="top">
-
-No customization in SAP BTP, Kyma runtime
-
-
-
-</td>
-</tr>
-<tr>
-<td valign="top">
-
-Monitoring<sup>[2](kyma-functionalities-4b83be9.md#loio4b83be95f7db4fddba5c46d388ebf39a__ol_tcn_pdp_pvb)</sup>
-
-
-
-</td>
-<td valign="top">
-
-:heavy_check_mark:
-
-
-
-</td>
-<td valign="top">
-
-limited
-
-
-
-</td>
-<td valign="top">
-
-No customization in SAP BTP, Kyma runtime
+limited \(no customization in SAP BTP, Kyma runtime\)
 
 
 
@@ -211,14 +146,7 @@ Kyma CLI
 </td>
 <td valign="top">
 
-limited
-
-
-
-</td>
-<td valign="top">
-
-SAP BTP, Kyma runtime supports commands for serverless Functions, not the commands related to installation.
+limited \(SAP BTP, Kyma runtime supports commands for serverless Functions, not the commands related to installation.\)
 
 
 
@@ -245,13 +173,6 @@ Centrally hosted Kyma Dashboard
 
 
 
-</td>
-<td valign="top">
-
-
-
-
-
 </td>
 </tr>
 <tr>
@@ -275,13 +196,6 @@ System landscape management in SAP BTP cockpit
 
 
 
-</td>
-<td valign="top">
-
-
-
-
-
 </td>
 </tr>
 <tr>
@@ -305,24 +219,10 @@ In-cluster system landscape management \(Application Connector\)
 
 
 
-</td>
-<td valign="top">
-
-
-
-
-
 </td>
 </tr>
 </table>
 
 > ### Caution:  
-> The following functionalities have been deprecated:
-> 
-> 1.  The Logging capability based on Loki, which enables you to query application logs using Grafana, has been deprecated. For details, see [What's New for Kyma on Dec 1, 2022 and June 1, 2023](https://help.sap.com/whats-new/cf0cb2cb149647329b5d02aa96303f56?Component=Kyma%20Runtime&Software_Lifecycle=Deprecated&q=logging&locale=en-US&version=Cloud&Valid_as_Of=2022-12-01%3A2023-09-30).
-> 
-> 2.  The Monitoring capability based on Prometheus, which enables you to query metrics using Grafana, has been deprecated. For details, see [What's New for Kyma on Jan 20, 2023](https://help.sap.com/whats-new/cf0cb2cb149647329b5d02aa96303f56?Component=Kyma%20Runtime&locale=en-US&version=Cloud&Valid_as_Of=2023-01-20%3A2023-01-20).
-> 
-> 
-> In the future, they will be removed from both, SAP BTP, Kyma runtime and open source project "Kyma".
+> 1.  The Monitoring capability based on Prometheus, which enables you to query metrics using Grafana, has been deprecated. For details, see [What's New for Kyma on Jan 20, 2023](https://help.sap.com/whats-new/cf0cb2cb149647329b5d02aa96303f56?Component=Kyma%20Runtime&locale=en-US&version=Cloud&Valid_as_Of=2023-01-20%3A2023-01-20). In the future, it will be removed from both, SAP BTP, Kyma runtime and open source project "Kyma".
 

docs/10-concepts/kyma-modules-0dda141.md

@@ -64,7 +64,7 @@ Within the BTP Operator module, BTP Manager installs SAP BTP Service Operator th
 <td valign="top">
 
 -   [Using SAP BTP Services in the Kyma Environment](../30-development/using-sap-btp-services-in-the-kyma-environment-ea4dd81.md)
--   [BTP Operator module](https://docs.kyma-project.io//?basePath=https://raw.githubusercontent.com/kyma-project/btp-manager/main/&homepage=docs/user/README.md&sidebar=true&loadSidebar=docs/user/_sidebar.md&browser-tab-title=BTP%20Operator%20Documentation#/docs/user/README)
+-   [BTP Operator module](https://kyma-project.io/#/btp-manager/user/README)
 -   [BTP Manger releases](https://github.com/kyma-project/btp-manager/releases)
 -   [SAP BTP Service Operator releases](https://github.com/SAP/sap-btp-service-operator/releases)
 
@@ -89,7 +89,7 @@ The Keda module comes with Keda Manager, an extension to Kyma that allows you to
 </td>
 <td valign="top">
 
--   [Keda module](https://docs.kyma-project.io//?basePath=https://raw.githubusercontent.com/kyma-project/keda-manager/main/&homepage=docs/user/README.md&sidebar=true&loadSidebar=docs/user/_sidebar.md&browser-tab-title=Keda%20module%20Documentation#/docs/user/README)
+-   [Keda module](https://kyma-project.io/#/keda-manager/user/README)
 
 
 
@@ -112,7 +112,7 @@ Istio is a service mesh with Kyma-specific configuration.
 </td>
 <td valign="top">
 
--   [What is Service Mesh is Kyma?](https://kyma-project.io/docs/kyma/latest/01-overview/service-mesh/)
+-   [What is Service Mesh in Kyma?](https://kyma-project.io/#/01-overview/service-mesh/)
 
 
 
@@ -136,7 +136,7 @@ With the Serverless module, you can define simple code snippets \(Funtions\) wit
 <td valign="top">
 
 -   [Deploy Workloads in the Kyma Environment to Extend SAP Systems](../30-development/deploy-workloads-in-the-kyma-environment-to-extend-sap-systems-fe4ba5b.md)
--   [What is Serverless in Kyma?](https://kyma-project.io/docs/kyma/latest/01-overview/serverless/)
+-   [What is Serverless in Kyma?](https://kyma-project.io/#/01-overview/serverless/)
 -   [https://github.com/kyma-project/serverless-manager](https://github.com/kyma-project/serverless-manager)
 
 
@@ -160,7 +160,7 @@ Enable telemetry agents to easily collect application logs and distributed trace
 </td>
 <td valign="top">
 
--   [What is Telemetry in Kyma?](https://kyma-project.io/docs/kyma/latest/01-overview/telemetry/)
+-   [What is Telemetry in Kyma?](https://kyma-project.io/#/01-overview/telemetry/)
 -   [https://github.com/kyma-project/telemetry-manager](https://github.com/kyma-project/telemetry-manager)
 
 
@@ -256,7 +256,7 @@ API Gateway provides functionalities that allow you to expose and secure APIs.
 </td>
 <td valign="top">
 
--   [API Gateway in Kyma](https://kyma-project.io/docs/kyma/latest/01-overview/api-exposure/apix-01-api-gateway/)
+-   [API Gateway in Kyma](https://kyma-project.io/#/01-overview/api-exposure/apix-01-api-gateway)
 
 
 

docs/10-concepts/regions-350356d.md

@@ -65,7 +65,7 @@ SAP has a number of processes in place to support resilience in SAP BTP, and pro
 Some customer contracts include EU Access, which restricts processing of personal data to EEA/Switzerland. If the global account is marked with EU Access, the actual EU Access compliance status of subaccounts will be displayed during creation of subaccounts.
 
 > ### Note:  
-> If you need a subaccount with EU Access, make sure to select a provider and region, where EU Access is available. For more information, see [Regions](regions-350356d.md)
+> If you require a subaccount with EU Access, make sure to select a provider and region where EU Access is available. Regions that allow for EU Access are labeled as such in the map view filter in the SAP Discovery Center.
 > 
 > For some services, EU Access is generally not available, not even if the provider and region support EU Access.
 

docs/20-getting-started/getting-started-in-the-kyma-environment-d1abd18.md

@@ -15,6 +15,9 @@ As an administrator, you must perform several steps to set up a fully operationa
 -   Additionally, the subaccount admin must assign the Kyma environment as an entitlement to the subaccount. For details, see [Configure Entitlements and Quotas for Subaccounts](../50-administration-and-ops/configure-entitlements-and-quotas-for-subaccounts-5ba357b.md).
 
 
+> ### Note:  
+> The required Service Manager entitlement is added by default. If you remove the entitlement, you must add it again in your subaccount.
+
 
 
 <a name="loiod1abd18556f24fb091d081b2e3454b8b__steps_xs3_l23_nrb"/>

docs/30-development/build-product-version-8120bf6.md

@@ -6,16 +6,9 @@ You can use the *Build Product Version* app to easily trigger the build of new p
 
 The app guides you through the creation of runs for your product versions and triggers them to be deployed on a system.
 
-Since technical users are needed in various steps, the app can also be used to add and maintain credentials that can be reused in multiple products.
+Since technical users are needed in various steps, the app can also be used to add and maintain credentials that can be reused in multiple products, see [Maintain Credentials](maintain-credentials-67b5aee.md).
 
-Previously, the scenario has been described in project "Piper". For more information, see [Build and Publish Add-On Products on SAP BTP, ABAP Environment.](https://www.project-piper.io/scenarios/abapEnvironmentAddons/) We recommend using the *Build Product Version* app that enables the Build Add-On Product scenario for you without the need to set up a Jenkins server.
-
-> ### Note:  
-> Please notice, that only 99 builds can be saved in a 28 day period. In case of further builds, the oldest one will be deleted.
-> 
-> Therefore, you can only see the build protocols of the currently saved builds.
-> 
-> Although normally being singular, the number of builds for a version can vary. You are able to repeat the build processes for one version until it works.
+Previously, the scenario was described in project "Piper", see [Build and Publish Add-On Products on SAP BTP, ABAP Environment.](https://www.project-piper.io/scenarios/abapEnvironmentAddons/) We recommend using the *Build Product Version* app that enables the 'Build Add-On Products' scenario for you without the need to set up a Jenkins server.
 
 
 

docs/30-development/configure-and-implement-a-customer-project-363d2ea.md

@@ -90,4 +90,6 @@ As a business user in a *Partner Customer Test* or *Partner Customer Production*
 
 -   See [Custom Logic \(Deprecated\)](../50-administration-and-ops/custom-logic-deprecated-05880c7.md) for guidance on how to use the *Custom Logic* app to create and maintain custom logic for business add-ins \(BAdIs\).
 -   See [Configuring Predefined Custom Fields](../50-administration-and-ops/configuring-predefined-custom-fields-0033cbc.md) for guidance on how to configure predefined custom fields to customize applications and their UIs.
+-   See [Adapting SAP Fiori UIs at Runtime - Key User Adaptation](https://help.sap.com/docs/btp/sap-fiori-launchpad-for-sap-btp-abap-environment/adapting-sap-fiori-uis-at-runtime-key-user-adaptation?version=Cloud)for guidance on how to adapt the user interface of an app separately for specific user roles.
+
 

docs/30-development/create-deployment-configuration-58b90ec.md

@@ -108,7 +108,7 @@ You have created a solution \(see [Create Solution](create-solution-aca34fa.md)\
     </td>
     <td valign="top">
 
-    Cloud Foundry endpoint of the landscape the solution should be deployed to. You can find this information in the SAP BTP Cockpit, in your provider subaccount under Overview \> General tab\> Cloud Foundry Environment section\> API Endpoint. It could be that your region is located in an extension. In that case, please make sure to use the complete url that is displayed in the SAP BTP Cockpit, e.g. cfapps.eu10-004.hana.ondemand.com.
+    Cloud Foundry endpoint of the landscape the solution should be deployed to. You can find this information in the SAP BTP Cockpit, in your provider subaccount under Overview \> General tab\> Cloud Foundry Environment section\> API Endpoint.
 
 
 
@@ -214,7 +214,7 @@ You have created a solution \(see [Create Solution](create-solution-aca34fa.md)\
     </td>
     <td valign="top">
 
-    You can select an app domain from the list of the available SAP app domains. The app domain should match the region domain name, i.e. the CF endpoint URL, e.g. cfapps.eu10-004.hana.ondemand.com.
+    You can select an app domain from the list of the available SAP app domains.
 
 
 

docs/30-development/create-solution-aca34fa.md

@@ -2,7 +2,7 @@
 
 # Create Solution
 
-You want to prepare a new solution for delivery to your consumers. Since a solution can be deployed to more than one subaccount, the creation of the solution has been separated from the creation of its deployment configurations \(see Create Deployment Configuration\).
+You want to prepare a new solution for delivery to your consumers. Since a solution can be deployed to more than one subaccount, the creation of the solution has been separated from the creation of its deployment configurations \(see [Create Deployment Configuration](create-deployment-configuration-58b90ec.md)\).
 
 Here's how to create a new solution.
 
@@ -85,10 +85,10 @@ Here's how to create a new solution.
     </td>
     <td valign="top">
 
-    It is mandatory for you as a provider to name your ABAP system. When a value has been supplied, the new system\(s\) will be created with this parameter. To avoid using forbidden SIDs, read more aboutReserved SAP System Identifiers \(SAPSID\) with Software Provisioning Manager.
+    It is mandatory for you as a provider to name your ABAP system. When a value has been supplied, the new system\(s\) will be created with this parameter.
 
     > ### Note:  
-    > To avoid using forbidden SIDs, read more about[Reserved SAP System Identifiers \(SAPSID\) with Software Provisioning Manager](https://launchpad.support.sap.com/#/notes/1979280).
+    > To avoid using forbidden SIDs, read more about [Reserved SAP System Identifiers \(SAPSID\) with Software Provisioning Manager](https://launchpad.support.sap.com/#/notes/1979280).
 
 
 
@@ -193,7 +193,7 @@ Here's how to create a new solution.
     </td>
     <td valign="top">
 
-    The IFrame integration incorporates your solution into the Fiori Launchpad Build Work Zone which could result in security risks. The shell header and the application UI are decoupled from each other, and each can point to a different domain. If the two frames each point to different domains, it can lead to issues with the browser and cookie policies. See [Security Guidelines for Content Providers](https://help.sap.com/docs/build-work-zone-standard-edition/sap-build-work-zone-standard-edition/security-guidelines-for-content-providers)
+    The IFrame integration enables you to incorporate your solution into the Fiori Launchpad Build Work Zone. Keep in mind that enabling the IFrame integration might reduce security. The shell header and the application UI are decoupled from each other, and each can point to a different domain. If the two frames each point to different domains, it can lead to issues with the browser and cookie policies. See [Security Guidelines for Content Providers](https://help.sap.com/docs/build-work-zone-standard-edition/sap-build-work-zone-standard-edition/security-guidelines-for-content-providers)
 
 
 

docs/30-development/create-support-users-b31712c.md

@@ -10,6 +10,9 @@
 
 You can create a support user to access a consumer tenant.
 
+> ### Note:  
+> Support users can only be created in tenants that are live and are of type "Partner Customer Production Tenant" or type "Partner Customer Test Tenant", i.e. the tenant must have been created through a subscription \(see [Tenant Business Types](tenant-business-types-018e8bd.md)\). For test tenants created in the Landscape Portal, support users cannot be created.
+
 
 
 <a name="loiob31712cc9dbf44fb8a603ab4be6f8d28__section_dtt_2rf_knb"/>