Skip to content

Commit 74c2399

Browse files
committed
Update from SAP DITA CMS (squashed):
commit 4f98341b33c2248a6eae0383168e358bc20dfc23 Author: REDACTED Date: Wed May 14 19:52:32 2025 +0000 Update from SAP DITA CMS 2025-05-14 19:52:32 Project: dita-all/jjq1673438782153 Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap Output: loio2080d0faf9d84ce6aa14caa4caa32935 Language: en-US Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap commit 4d5e2f99e887e13f2a577672fd3a4af8d384976b Author: REDACTED Date: Wed May 14 19:28:52 2025 +0000 Update from SAP DITA CMS 2025-05-14 19:28:52 Project: dita-all/jjq1673438782153 Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap Output: loio2080d0faf9d84ce6aa14caa4caa32935 Language: en-US Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap commit 7501068ff9fff292ca83510abbbfef48b8520e31 Author: REDACTED Date: Wed May 14 19:04:21 2025 +0000 Update from SAP DITA CMS 2025-05-14 19:04:21 Project: dita-all/jjq1673438782153 Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap ################################################## [Remaining squash message was removed before commit...]
1 parent e98fb63 commit 74c2399

File tree

105 files changed

+5100
-980
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

105 files changed

+5100
-980
lines changed

docs/10-concepts/abap-development-tools-for-eclipse-54dd712.md

Lines changed: 17 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,9 @@ ABAP development tools for Eclipse is SAP’s state-of-the-art integrated develo
88

99
## Features
1010

11-
ABAP development tools for Eclipse enables you to perform ABAP-based development tasks, when you want to build, to extend, and to run ABAP applications based on SAP products, such as SAP S/4HANA and SAP S/4HANA Cloud, private edition for classic ABAP development as well as SAP BTP ABAP environment and SAP S/4HANA Cloud for Cloud development.
11+
ABAP development tools for Eclipse enables you to perform ABAP-based development tasks when you want to build, extend, and run ABAP applications based on SAP products, such as SAP S/4HANA and SAP S/4HANA Cloud Private Edition for classic ABAP development as well as SAP BTP ABAP environment and SAP S/4HANA Cloud Public Edition for Cloud development.
1212

13-
ABAP development tools for Eclipse supports ABAP developers with the following possibilities:
13+
It supports ABAP developers with the following possibilities:
1414

1515
- Highly flexible, customizable Eclipse UI for ABAP development tools
1616

@@ -27,7 +27,7 @@ ABAP development tools for Eclipse supports ABAP developers with the following p
2727
- Built-in extensibility of the IDE using the established Eclipse plug-in technology
2828

2929

30-
In particular, ABAP development tools for Eclipse is a modern development toolset where ABAP developers can use, for example the following features:
30+
In particular, ABAP development tools for Eclipse is a modern development toolset where ABAP developers can use, among others, the following features:
3131

3232
- Syntax check
3333

@@ -43,18 +43,26 @@ In particular, ABAP development tools for Eclipse is a modern development toolse
4343

4444
- Quick fixes
4545

46-
- and many more
47-
4846

4947

5048

5149
<a name="loio54dd7126d5b74efeb7a21f6b0bfe5f1a__section_k2h_hhy_gxb"/>
5250

53-
## Tools User Guides
51+
## Help Content
52+
53+
The [ABAP Development Tools for Eclipse guide](https://help.sap.com/docs/abap-cloud/abap-development-tools-user-guide/about-abap-development-tools-user-guide?version=sap_cross_product_abap) describes the following features and functionalities of ADT:
54+
55+
- Joule for developers, ABAP AI capabilities supports you in the end-to-end development using generative AI and can be integrated into ABAP development tools for Eclipse. It's currently only available for customers using SAP BTP ABAP environment or SAP S/4HANA Cloud Public Edition. To leverage Joule for developers, ABAP AI capabilities, you need to purchase an additional license. See [Getting Started](https://help.sap.com/docs/abap-ai/generative-ai-in-abap-cloud/prerequisites-and-required-authorizations).
56+
- Within the ABAP core development scenario: In particular, it focuses on use cases for creating, editing, testing, debugging, and profiling development objects like ABAP classes, ABAP Dictionary objects, function modules and so forth.
57+
58+
- For Core Data Services \(CDS\) in ABAP development for SAP HANA scenarios: In particular, it focuses on use cases for creating, editing, testing, and analyzing **ABAP CDS entities** like data definitions and so forth.
59+
60+
- When developing all types of SAP Fiori applications as well as publishing Web APIs in the context of the ABAP RESTful Application Programming Model \(RAP\)
61+
62+
- When creating lifecycle-stable and cloud-ready business apps, services, and extensions in the context of the [ABAP Cloud development model](https://help.sap.com/docs/abap-cloud/abap-cloud/abap-cloud-in-nutshell)
5463

55-
The [ABAP Development Tools: User Guide](https://help.sap.com/docs/abap-cloud/abap-development-tools-user-guide/about-abap-development-tools-user-guide?version=sap_btp) describes the functionality and usage of the possibilities. It focuses on use cases for creating, editing, testing, debugging, and profiling development objects.
64+
- For the integration of native SAP HANA objects \(in the context of SAP HANA repository content\) within the ABAP layer
5665

57-
The [ABAP CDS Development Tools: User Guide](https://help.sap.com/docs/abap-cloud/abap-cds-tools-user-guide/about-abap-cds-development-tools-user-guide?version=sap_btp) describes the functionality and usage of tools for ABAP Core Data Services \(CDS\) in the ABAP environment. It focuses on use cases for creating, editing, testing, and analyzing ABAP CDS entities.
5866

5967

6068

@@ -88,5 +96,5 @@ To install ABAP development tools for Eclipse, follow the [Installation Guide](h
8896

8997
## Support
9098

91-
The use of ABAP development tools for Eclipse is subject to the terms and conditions of your license agreement with SAP which is directly related to the SAP shipment channel from whichABAP development tools for Eclipse was initially downloaded and installed.
99+
The use of ABAP development tools for Eclipse is subject to the terms and conditions of your license agreement with SAP which is directly related to the SAP shipment channel from which ABAP development tools for Eclipse was initially downloaded and installed.
92100

docs/10-concepts/kyma-cli-292454b.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
# Kyma CLI
44

5-
Kyma CLI is an essential tool for application developers who want to get started quickly and efficiently with SAP BTP, Kyma runtime. Designed to streamline workflows, it simplifies complex tasks, enabling developers to deploy and manage applications easily
5+
Kyma CLI is an essential tool for application developers who want to get started quickly and efficiently with SAP BTP, Kyma runtime. Designed to streamline workflows, it simplifies complex tasks, enabling developers to deploy and manage applications easily.
66

77
> ### Caution:
88
> The `alpha` group commands are still in development, which means their functions and API may be modified over time. We encourage you to explore them, but keep in mind that changes may occur.

docs/10-concepts/kyma-dashboard-command-palette-7542ffb.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ You can use the command palette to perform the following actions:
1616

1717
![](images/Command_Palette_Quick_Navigation_9efa6cf.png)
1818

19-
- To see all navigation options and the resources' aliases, enter enter the question mark sign `(?)`. For example, if you want to see your namespaces, it's enough to type `ns`.
19+
- To see all navigation options and the resources' aliases, enter the question mark sign `(?)`. For example, if you want to see your namespaces, it's enough to type `ns`.
2020

2121
![](images/Namespaces_navigation_e12775a.png)
2222

docs/10-concepts/service-plans-and-metering-for-cloud-foundry-runtime-8d41fa4.md

Lines changed: 92 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This page explains the relationship between the service plans in the SAP Discove
1616

1717
### Overview
1818

19-
The diagram below shows how the service plans listed in the [SAP Discovery Center](https://discovery-center.cloud.sap/serviceCatalog/cloud-foundry-runtime?region=all&tab=service_plan) correspond to the plans you choose in the [SAP BTP cockpit](https://cockpit.btp.cloud.sap), depending on the commercial model of your enterprise global account. For more information about the commercial models offered by SAP, see [Commercial Models](commercial-models-263d400.md).
19+
The diagram below shows how the service plans listed in the [SAP Discovery Center](https://discovery-center.cloud.sap/serviceCatalog/cloud-foundry-runtime?region=all&tab=service_plan) correspond to the plans you choose in the SAP BTP cockpit, depending on the commercial model of your enterprise global account. For more information about the commercial models offered by SAP, see [Commercial Models](commercial-models-263d400.md).
2020

2121
![A diagram depicting the relationship between service plans in the SAP Discovery Center, service plans in the SAP BTP cockpit, environment plans in the SAP BTP cockpit, and the metric GB Memory. Consumption-based commercial model, line 1 of 2: Service Plan (SAP Discovery Center) - Standard; Service Plan (SAP BTP Cockpit) - not applicable; Environment Plan (SAP BTP Cockpit) - standard; Metrics - GB Memory; SKU - 8008837. Consumption-based commercial model, line 2 of 2: Service Plan (SAP Discovery Center) - Free; Service Plan (SAP BTP Cockpit) - free (Environment); Environment Plan (SAP BTP Cockpit) - free; Metrics - GB Memory; SKU - 8011138. Subscription-based commercial model, line 1 of 1: Service Plan (SAP Discovery Center) - Standard; Service Plan (SAP BTP Cockpit) - MEMORY, the plan is associated with a standalone service Cloud Foundry Runtime (technical name: APPLICATION_RUNTIME); Environment Plan (SAP BTP Cockpit) - standard; Metrics - GB Memory; SKU - 8008837.](images/SAP_BTP_Cloud_Foundry_Runtime_Commercial_Information_Plans_-_2024_V2_67db7c4.png)
2222

@@ -40,11 +40,15 @@ The plan that the global account administrator can assign to a subaccount or a d
4040
> ### Tip:
4141
> Open image in new tab for the full-screen version.
4242
43-
![A screenshot of the Entitlements screen in the SAP BTP cockpit, showing the assignment of a service plan to a subaccount.](images/English_-_Entitlements_-_SAP_BTP_Cloud_Foundry_Runtime_94337c9.png "Screenshot: Assigning a service plan to a subaccount in SAP BTP
44-
cockpit [Show/Hide]")
43+
![A screenshot of the Entitlements screen in the SAP BTP cockpit, showing the assignment of a service plan to a subaccount.](images/English_-_Entitlements_-_SAP_BTP_Cloud_Foundry_Runtime_94337c9.png "Screenshot: Assigning a service plan to a subaccount in
44+
SAP BTP
45+
cockpit [Show/Hide]")
4546

4647
For more information about the procedure, see [Configure Entitlements and Quotas for Subaccounts](../50-administration-and-ops/configure-entitlements-and-quotas-for-subaccounts-5ba357b.md) or [Configure Entitlements and Quotas for Directories](../50-administration-and-ops/configure-entitlements-and-quotas-for-directories-37f8871.md).
4748

49+
> ### Note:
50+
> The greyed out parts of the diagram indicate service plans that are automatically assigned to all subaccounts by default.
51+
4852

4953

5054
</dd><dt><b>
@@ -61,8 +65,9 @@ The plan that the subaccount administrator can select on the *Overview* page of
6165
> ### Tip:
6266
> Open image in new tab for the full-screen version.
6367
64-
![A screenshot of the Overview screen of a subaccount in the SAP BTP cockpit, showing the enablement of an environment plan.](images/English_-_Enable_Cloud_Foundry_-_SAP_BTP_Cloud_Foundry_Runtime_0377151.png "Screenshot: Selecting an environment plan for the subaccount in SAP BTP
65-
cockpit [Show/Hide]")
68+
![A screenshot of the Overview screen of a subaccount in the SAP BTP cockpit, showing the enablement of an environment plan.](images/English_-_Enable_Cloud_Foundry_-_SAP_BTP_Cloud_Foundry_Runtime_0377151.png "Screenshot: Selecting an environment plan for the subaccount
69+
in SAP BTP
70+
cockpit [Show/Hide]")
6671

6772

6873

@@ -271,9 +276,41 @@ standard
271276

272277
This is a **paid** plan for productive use. In the subscription-based commercial model, you pay for runtime memory quota in advance.
273278

274-
The runtime memory quota purchased with your subscription must be entitled to subaccounts through the service plan MEMORY. This service plan is associated with the service Cloud Foundry Runtime \(`APPLICATION_RUNTIME`\), which is specific to the subscription-based commercial model.
279+
The runtime memory quota purchased with your subscription must be assigned to subaccounts through the service plan MEMORY. This service plan is associated with the service Cloud Foundry Runtime \(`APPLICATION_RUNTIME`\).
280+
281+
The plan **standard** is assigned to all subaccounts by default and can be enabled by a subaccount administrator. The runtime memory quota can be assigned to the subaccount only by a global account administrator \(or a directory administrator\). These steps are independent, but both of them are required to run applications in the Cloud Foundry environment.
282+
283+
</td>
284+
</tr>
285+
<tr>
286+
<td valign="top" align="center">
287+
288+
\-
289+
290+
</td>
291+
<td valign="top">
292+
293+
Cloud Foundry Environment \(`cloudfoundry`\)
294+
295+
</td>
296+
<td valign="top">
297+
298+
build-runtime
299+
300+
</td>
301+
<td valign="top">
302+
303+
build-runtime
304+
305+
</td>
306+
<td valign="top">
307+
308+
This plan is only for using the SAP BTP, Cloud Foundry runtime as part of SAP Build. For more information, see [What Is SAP Build](https://help.sap.com/docs/build-service/build-service-guide/what-is-sap-build) and [Service Plans and Metering](https://help.sap.com/docs/build-service/build-service-guide/service-plans-and-metering).
309+
310+
> ### Note:
311+
> The plan is not depicted on the diagram in the **Overview** section.
312+
275313

276-
The plan **standard** is available for all subaccounts by default and can be enabled by a subaccount administrator. The runtime memory quota can be entitled to the subaccount only by a global account administrator \(or a directory administrator\). These steps are independent, but both of them are required to run applications in the Cloud Foundry environment.
277314

278315
</td>
279316
</tr>
@@ -324,12 +361,17 @@ The table below provides details about the metrics for SAP BTP, Cloud Foundry ru
324361
<tr>
325362
<th valign="top" align="center">
326363

327-
Service
364+
Metric
328365

329366
</th>
330367
<th valign="top" align="center">
331368

332-
Metric
369+
Service \(SAP BTP Cockpit\)
370+
371+
</th>
372+
<th valign="top" align="center">
373+
374+
Metric \(SAP BTP Cockpit\)
333375

334376
</th>
335377
<th valign="top" align="center">
@@ -346,6 +388,11 @@ Additional Information
346388
<tr>
347389
<td valign="top">
348390

391+
GB Memory
392+
393+
</td>
394+
<td valign="top">
395+
349396
Cloud Foundry Runtime
350397

351398
</td>
@@ -354,7 +401,7 @@ Cloud Foundry Runtime
354401
GB Memory
355402

356403
</td>
357-
<td valign="top" rowspan="2">
404+
<td valign="top" rowspan="3">
358405

359406
Temporary memory bank where computers store data that needs to be retrieved and processed quickly.
360407

@@ -363,13 +410,40 @@ The memory represents the size of the data that can be processed and CPU represe
363410
</td>
364411
<td valign="top">
365412

366-
For billing purposes, the metric GB Memory is calculated as the total hourly usage of Cloud Foundry runtime memory across all spaces in the global account over a calendar month, divided by 730 hours and rounded up to the next full GB. For an example of such calculation, see [Consumption Monitoring](https://help.sap.com/docs/cf-runtime/cloud-foundry-runtime/monitoring-and-troubleshooting?version=Cloud#consumption-monitoring).
413+
For billing purposes, the GB Memory metric for the Cloud Foundry Runtime service is calculated as the total hourly usage of Cloud Foundry runtime memory across all spaces in the global account over a calendar month, divided by 730 hours and rounded up to the next full GB. For an example of such calculation, see [Consumption Monitoring](https://help.sap.com/docs/cf-runtime/cloud-foundry-runtime/monitoring-and-troubleshooting?version=Cloud#consumption-monitoring).
367414

368415
> ### Note:
369416
> In the Cloud Foundry environment, applications get a guaranteed CPU share of ¼ core per GB of runtime memory quota reserved for an application instance. For more information, see [SAP BTP-Specific Configurations](sap-btp-specific-configurations-9809fa4.md).
370417
371418

372419

420+
</td>
421+
</tr>
422+
<tr>
423+
<td valign="top" rowspan="2">
424+
425+
Capacity Units
426+
427+
</td>
428+
<td valign="top">
429+
430+
SAP Build
431+
432+
</td>
433+
<td valign="top">
434+
435+
GB Memory
436+
437+
</td>
438+
<td valign="top">
439+
440+
In SAP Build, the usage of SAP BTP, Cloud Foundry runtime is measured in capacity units. The GB Memory metric for the SAP Build service in the SAP BTP cockpit is intended only for monitoring the approximate usage of SAP BTP, Cloud Foundry runtime in GB when it's consumed as part of SAP Build. For more information, see [What Is SAP Build](https://help.sap.com/docs/build-service/build-service-guide/what-is-sap-build?version=Cloud).
441+
442+
> ### Note:
443+
> The metric is not depicted on the diagram in [Service](service-plans-and-metering-for-cloud-foundry-runtime-8d41fa4.md#loio8d41fa40e47b45bf90d38e393a989c4c__service).
444+
445+
446+
373447
</td>
374448
</tr>
375449
<tr>
@@ -385,7 +459,7 @@ CF Runtime
385459
</td>
386460
<td valign="top">
387461

388-
The metric CF Runtime is intended for monitoring the usage of SAP BTP, Cloud Foundry runtime when it's used as part of SAP Build Code. For more information, see [What Is SAP Build Code](https://help.sap.com/docs/build_code/d0d8f5bfc3d640478854e6f4e7c7584a/504854f457cc4fbf9f79136dbc773618.html).
462+
In SAP Build Code, the usage of SAP BTP, Cloud Foundry runtime is measured in capacity units. The CF Runtime metric for the SAP Build Code service in the SAP BTP cockpit is intended only for monitoring the approximate usage of SAP BTP, Cloud Foundry runtime in GB when it's consumed as part of SAP Build Code. For more information, see [What Is SAP Build Code](https://help.sap.com/docs/build_code/d0d8f5bfc3d640478854e6f4e7c7584a/504854f457cc4fbf9f79136dbc773618.html) and [SAP Build Code Capacity Unit Calculator](https://build-code-calculator.cfapps.eu10-004.hana.ondemand.com/).
389463

390464
> ### Note:
391465
> The metric is not depicted on the diagram in [Service](service-plans-and-metering-for-cloud-foundry-runtime-8d41fa4.md#loio8d41fa40e47b45bf90d38e393a989c4c__service).
@@ -417,6 +491,9 @@ There are two application settings that define how much runtime memory an applic
417491
- Number of running application instances \(default: 1\)
418492

419493

494+
> ### Note:
495+
> The total amount of runtime memory that an application uses when all of its instances are running is displayed on the application's *Overview* page under *All Instances Memory*.
496+
420497
You can specify custom values for these settings when deploying an application in the Cloud Foundry environment. You can also change them for an application that has already been deployed without having to redeploy it.
421498

422499

@@ -435,9 +512,9 @@ You can specify custom values for these settings when deploying an application i
435512
- Using the SAP BTP cockpit: [Deploy an Application](../50-administration-and-ops/deploy-an-application-09fdb9b.md)
436513
- Using the Cloud Foundry CLI: [https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html](https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html)
437514

438-
- **Option 2:** In the SAP BTP cockpit, choose *Deploy Application*, deselect *Use Manifest* and specify the following:
515+
- **Option 2:** In the SAP BTP cockpit, choose *Deploy Application*, select *Custom Settings* and specify the following:
439516

440-
- *Instance Memory \(MB\)*: runtime memory quota per application instance
517+
- *Memory per Instance \(MB\)*: runtime memory quota per application instance
441518
- *Number of Instances*: number of application instances
442519

443520
For more information about the procedure, see [Deploy an Application](../50-administration-and-ops/deploy-an-application-09fdb9b.md).
@@ -456,7 +533,7 @@ You can specify custom values for these settings when deploying an application i
456533

457534
- **Option 1:** In the SAP BTP cockpit, on the *Overview* page of the application you can:
458535

459-
- Change the runtime memory quota per application instance under *Change Instance Details* \> *Instance Memory \(MB\)*
536+
- Change the runtime memory quota per application instance under *Change Instance Details* \> *Memory per Instance \(MB\)*
460537
- Change the number of application instances as described in [Manage Application Instances](../50-administration-and-ops/manage-application-instances-75836f1.md)
461538

462539
- **Option 2:** In the Cloud Foundry CLI, you can use the command `cf scale` with the following flags:
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
<!-- loioc6b49c938e974e93ae5f1b17d6eb8479 -->
2+
3+
# 401 Unauthorized or 403 Forbidden
4+
5+
6+
7+
<a name="loioc6b49c938e974e93ae5f1b17d6eb8479__section_fpd_5hr_v2c"/>
8+
9+
## Symptom
10+
11+
When you try to reach a service, you get ***401 Unauthorized*** or ***403 Forbidden*** in response.
12+
13+
14+
15+
<a name="loioc6b49c938e974e93ae5f1b17d6eb8479__section_rks_whr_v2c"/>
16+
17+
## Cause
18+
19+
The error ***401 Unauthorized*** occurs when you try to access a Service that requires authentication, and the appropriate credentials were not provided or were incorrect. You get the error ***403 Forbidden*** when you try to access a Service or perform an action for which you lack permission.
20+
21+
22+
23+
<a name="loioc6b49c938e974e93ae5f1b17d6eb8479__section_sbh_zhr_v2c"/>
24+
25+
## Solution
26+
27+
Make sure that you are using an active JSON Web Token \(JWT\) with proper scopes.
28+
29+
1. Decode the JWT.
30+
2. Check the validity and scopes of the JWT:
31+
32+
```
33+
{
34+
"sub": ********,
35+
"scp": "test",
36+
"aud": ********,
37+
"iss": ******,
38+
"exp": 1697120462,
39+
"iat": ******,
40+
"jti": ******,
41+
}
42+
```
43+
44+
3. [Generate a new JWT](https://kyma-project.io/#/api-gateway/user/tutorials/01-50-expose-and-secure-a-workload/01-51-get-jwt) if needed.
45+

0 commit comments

Comments
 (0)