SAP-docs · kohlerm · May 29, 2025 · May 29, 2025 · May 29, 2025
diff --git a/docs/deploy-45d5acf.md b/docs/deploy-45d5acf.md
@@ -12,7 +12,7 @@ SAP Cloud Application Programming Model \(CAP\) applications can be deployed in
 
 After completing the functional implementation of the CAP application by following the best practices, you can deploy your application in the cloud for productive usage. The essential steps are illustrated in the following graphic:
 
-![](images/Deploy_a_CAP_Application_in_Cloud_Foundry_Runtime_50243ce.png)
+![A four-step process diagram illustrates the deployment of an application to Cloud Foundry, including preparing for production (once), freezing dependencies (once; when upgrading), building and assembling, and finally deploying.](images/Deploy_a_CAP_Application_in_Cloud_Foundry_Runtime_50243ce.png)
 
 With our recommended approach, the actual deployment in your SAP BTP, Cloud Foundry runtime is performed either by your [Continuous Integration and Delivery \(CI/CD\)](develop-and-build/continuous-integration-and-delivery-ci-cd-fe74df5.md) pipeline \(such as provided by SAP Continuous Integration and Delivery service\) or handled by transports \(via [SAP Cloud Transport Management](https://help.sap.com/docs/cloud-transport-management?version=Cloud), optionally orchestrated by SAP Cloud ALM\).
 
@@ -35,7 +35,6 @@ In consequence, two kinds of artifacts are needed to run applications on Kuberne
 
 The following diagram shows the steps to run on the SAP BTP, Kyma runtime:
 
-![](images/Deploy_a_CAP_Application_in_the_Kyma_Runtime_d3a3414.png)
-
-For detailed steps to deploying your application in the SAP BTP, Kyma runtime, see[Deploy in Kyma Runtime](https://cap.cloud.sap/docs/guides/deployment/deploy-to-kyma).
+![This diagram illustrates the **deployment architecture of a CAP (Cloud Application Programming) application in the SAP BTP, Kyma runtime**. It depicts the flow from a CAP project being built into container images and pushed to a container registry, then deployed via a CAP Helm Chart to create various Kyma resources (Deployments, Service Instances, Jobs, Pods), with Pods pulling images from the registry and Kyma Service Instances integrating with SAP BTP.](images/Deploy_a_CAP_Application_in_the_Kyma_Runtime_d3a3414.png)
 
+For detailed steps to deploying your application in the SAP BTP, Kyma runtime, see[Deploy in Kyma Runtime](https://cap.cloud.sap/docs/guides/deployment/deploy-to-kyma).
diff --git a/docs/design-a-transactional-application-608432c.md b/docs/design-a-transactional-application-608432c.md
@@ -8,13 +8,12 @@ A transactional application consists of a client, the business service exposure
 
 The following graphic gives you an overview of the main parts of the transactional application’s architecture:
 
-![](images/Design_a_Transactional_Application_d715f00.png)
+![This diagram illustrates a layered architectural overview for SAP application development, detailing components from data access and domain modeling to business service exposure and consumer interfaces like SAP Fiori UIs.](images/Design_a_Transactional_Application_d715f00.png)
 
 The client is either an SAP Fiori elements or SAPUI5 application or any API consumer.
 
 In the business service exposure the kind of service that is exposed is defined. A UI service is an OData service specifically designed to cater to SAP Fiori elements consumers but is used for OData UI consumers in general. API services expose the underlying data- and behavior-models as APIs to unspecified clients either with the OData protocol or business events. It is possible to define both UI and API services at the same time.
 
 The ABAP RESTful Application Programming Model \(RAP\) is used to create UI and API services including the domain model and implementation. The center piece of RAP is the business object. RAP's business objects consist of the data model implemented with the core data services and the transactional behavior implemented with the Entity Manipulation Language \(EML\).
 
-The architectural separation of concerns between the domain-specific implementation and the business service exposure allows you to expose the same data model for analytical and transactional applications and services.
-
+The architectural separation of concerns between the domain-specific implementation and the business service exposure allows you to expose the same data model for analytical and transactional applications and services.
diff --git a/docs/design-an-analytical-application-8819cb7.md b/docs/design-an-analytical-application-8819cb7.md
@@ -6,9 +6,8 @@ Analytical Applications implement use cases where multi-dimensional data models
 
 The following graphic gives you an overview of the main parts of the analytical architecture:
 
-![](images/Design_an_Analytical_Application_80e21cc.png)
+![This diagram illustrates the layered architecture of an SAP analytical application, detailing components from consumer UIs (SAP Fiori, SAP Analytics Cloud) and business service exposure, through domain-specific data modeling (Core Data Services) and programming, down to SAP HANA for data access, alongside various integration services.](images/Design_an_Analytical_Application_80e21cc.png)
 
 Analytical data models are CDS-based. The analytical provider consists of a reusable star or snowflake schema \(based on cubes, dimensions, and hierarchies\) and scenario-specific analytical projections \(analytical queries\).
 
-ABAP Cloud enables you to develop Information Access \(InA\)-based services for multidimensional user apps. The InA services are either consumed in SAP Fiori UIs or by SAP Analytics Cloud.
-
+ABAP Cloud enables you to develop Information Access \(InA\)-based services for multidimensional user apps. The InA services are either consumed in SAP Fiori UIs or by SAP Analytics Cloud.
diff --git a/docs/design-an-integration-service-ec2ac31.md b/docs/design-an-integration-service-ec2ac31.md
@@ -8,5 +8,4 @@ You can use data integration to exchange data between two or more parties withou
 
 Process integration requirements can span data exchange across system boundaries, like, for example, initiating follow-on actions with events when a value in an app is changed.
 
-![](images/Design_an_Integration_Service_c04a651.png)
-
+![A multi-layered architectural model illustrating the hierarchy from consumer-facing business services, through integration services for exposure and consumption, down to domain-specific programming (ABAP, Core Data Services) and data access points like SAP HANA.](images/Design_an_Integration_Service_c04a651.png)
diff --git a/docs/develop-58df1d6.md b/docs/develop-58df1d6.md
@@ -206,7 +206,7 @@ Use programming languages, libraries, and APIs tailored for full-stack applicati
 
 The following graphic is designed to help you find the information you need for your programming purposes. The bottom row represents the tools, frameworks, services, and deployment options recommended by SAP. If you want full flexibility you can also bring your own development tools and languages, as shown in the top row.
 
-![](images/Image_Map_Development_Options_Overview_d716bab.png)
+![This diagram outlines a software development flow, illustrating a "Recommended Path" with specific SAP technologies and an "Alternative Path" using generic tools and languages.](images/Image_Map_Development_Options_Overview_d716bab.png)
 
 
 
@@ -222,5 +222,4 @@ This development approach offers guidance for important development decisions an
 
 ## Tutorials and End-to-End Scenarios
 
-There are tutorials and end-to-end scenarios developed to show you how to apply the recommended path for the Cloud Application Programming Model \(CAP\). All these tutorials and scenarios are based on the Incident Management sample application. For a full list of the tutorials and their use cases, see [Tutorials for SAP Cloud Application Programming Model](tutorials-for-sap-cloud-application-programming-model-eb7420a.md).
-
+There are tutorials and end-to-end scenarios developed to show you how to apply the recommended path for the Cloud Application Programming Model \(CAP\). All these tutorials and scenarios are based on the Incident Management sample application. For a full list of the tutorials and their use cases, see [Tutorials for SAP Cloud Application Programming Model](tutorials-for-sap-cloud-application-programming-model-eb7420a.md).
diff --git a/docs/develop-a-transactional-application-373046e.md b/docs/develop-a-transactional-application-373046e.md
@@ -4,7 +4,7 @@
 
 Transactional applications in ABAP Cloud provide a robust and scalable solution for managing business processes and data. The ABAP RESTful Application Programming Model \(RAP\) defines how transactional applications are built. The following graphic shows the big picture:
 
-![](images/ABAP_Cloud_-_the_Big_Picture_5d4a7c9.png)
+![Layered architecture of the ABAP RESTful Application Programming Model (RAP), detailing the definition and exposure of data models and business objects for consumption via APIs, events, and Fiori UIs, highlighting extensibility.](images/ABAP_Cloud_-_the_Big_Picture_5d4a7c9.png)
 
 To build a transactional application, you define data models and implement business logic using a declarative approach. The data models as well as the behavior definition make up the ABAP RESTful Application Programming Model business object \(RAP BO\). The data model implemented with ABAP Core Data Services defines the structure of the data. The behavior definition is implemented with ABAP and the Entity Manipulation Language.
 
@@ -296,5 +296,4 @@ For an example, see:
 -   [OData Integration Tests](https://help.sap.com/docs/abap-cloud/abap-rap/odata-integration-tests?version=abap_cross_product)
 
 
-For more information about the OData Client Proxy, see [OData Client Proxy-Consumption Types](https://help.sap.com/docs/btp/sap-business-technology-platform/client-proxy-instance-types?version=Cloud#consumption-types).
-
+For more information about the OData Client Proxy, see [OData Client Proxy-Consumption Types](https://help.sap.com/docs/btp/sap-business-technology-platform/client-proxy-instance-types?version=Cloud#consumption-types).
diff --git a/docs/develop-an-analytical-application-b845c85.md b/docs/develop-an-analytical-application-b845c85.md
@@ -15,7 +15,7 @@ Analytical applications require a multidimensional data model that focuses on a
 -   **Analytical queries** that define the initial report layout that is displayed, select the initial data, and can calculate measures that weren’t included in the underlying cube.
 
 
-![](images/Develop_an_Analytical_Application_a994982.png)
+![A multi-layered architectural diagram depicting the development and consumption of analytical applications. It illustrates the progression from foundational Core Data Services (CDS) for data modeling and analytical providers, through business service exposure via analytical queries, to consumption by SAP Fiori UIs and SAP Analytics Cloud, with extensibility highlighted on the right.](images/Develop_an_Analytical_Application_a994982.png)
 
 
 
@@ -205,5 +205,4 @@ Analytical services use the Analytics Details annotations to specify the ana
 
 With the annotation `@AnalyticsDetails.query.axis:'<VALUE>’`, you can position the elements of a query on the different axis to define the basic layout for the report.
 
-For more information, see [AnalyticsDetails Annotations](https://help.sap.com/docs/abap-cloud/abap-rap/analyticsdetails-annotation?version=abap_cross_product).
-
+For more information, see [AnalyticsDetails Annotations](https://help.sap.com/docs/abap-cloud/abap-rap/analyticsdetails-annotation?version=abap_cross_product).
diff --git a/docs/develop-and-build/continuous-integration-and-delivery-ci-cd-fe74df5.md b/docs/develop-and-build/continuous-integration-and-delivery-ci-cd-fe74df5.md
@@ -17,7 +17,7 @@ The following graphic shows the basic flow for continuous integration and delive
 
 **Continuous Integration Basic Flow**
 
-![](images/ci-basic-flow-copy_b835ff9.png "Continuous Integration Basic Flow")
+![A circular diagram illustrating the Continuous Integration flow, detailing the cycle from a developer's code changes through SCM, triggering Continuous Integration and Delivery, and receiving feedback.](images/ci-basic-flow-copy_b835ff9.png "Continuous Integration Basic Flow")
 
 For more information about the continuous integration and continuous delivery concepts, see [What Are Continuous Integration and Continuous Delivery?](https://help.sap.com/viewer/8cacec64ed854b2a88e9a0973e0f97a2/Cloud/en-US/5ba483a2c97b4ad5ab0148f4a6c5a9ee.html).
 
@@ -106,6 +106,4 @@ Depending on your learning goals and level of expertise, you can choose from the
 
 -   **[Continuous Integration and Delivery Introduction Guide](https://help.sap.com/viewer/ee5a61247061455ab232c19179fe4c3b/Cloud/en-US)**
 
-    The CI/CD Introduction Guide provides you with basic knowledge for setting up and implementing continuous integration and delivery processes. It gives an overview of the concepts and principles of CI/CD, explains both procedures and their relation, and helps you plan your own CI/CD process.
-
-
+    The CI/CD Introduction Guide provides you with basic knowledge for setting up and implementing continuous integration and delivery processes. It gives an overview of the concepts and principles of CI/CD, explains both procedures and their relation, and helps you plan your own CI/CD process.
diff --git a/docs/develop-and-build/developing-resilient-applications-b1b929a.md b/docs/develop-and-build/developing-resilient-applications-b1b929a.md
@@ -28,7 +28,7 @@ During that period, the remaining instances in the healthy AZs have to carry the
 
 **Distribution During an Availability Zone Failure**
 
-![](images/AZ_failure_3e96947.png "Distribution During an Availability Zone Failure")
+![The scheduler reallocates instances to Availability Zones 2 and 3, bypassing the unavailable Availability Zone 1.](images/AZ_failure_3e96947.png "Distribution During an Availability Zone Failure")
 
 
 
@@ -41,5 +41,4 @@ Learn how to develop stable Kubernetes and microservice-based applications, as w
 **Related Information**  
 
 
-[Resilience, High Availability, and Disaster Recovery \(Cloud Foundry, ABAP and Kyma Environments\)](https://help.sap.com/docs/btp/sap-business-technology-platform/resilience-high-availability-and-disaster-recovery?locale=en-US&version=Cloud#loioe3ac4f7c25a3442ca585950095eec599)
-
+[Resilience, High Availability, and Disaster Recovery \(Cloud Foundry, ABAP and Kyma Environments\)](https://help.sap.com/docs/btp/sap-business-technology-platform/resilience-high-availability-and-disaster-recovery?locale=en-US&version=Cloud#loioe3ac4f7c25a3442ca585950095eec599)
diff --git a/docs/develop-the-user-interface-9f1d42e.md b/docs/develop-the-user-interface-9f1d42e.md
@@ -47,7 +47,7 @@ This approach is a hybrid in-between pure SAPUI5 and SAP Fiori elements. You can
 
 To make the right decision out of these three options, it's important for you as an application developer to understand their features and limitations. The overall recommendation would be to use as much SAP Fiori elements as possible, as much SAPUI5 freestyle as needed.
 
-![](images/User_Interface_116cf74.png)
+![The image displays a spectrum of programming models, illustrating a trade-off between efficiency and flexibility. It ranges from highly efficient "SAP Fiori Elements" using "Standard Floorplans" on the left, through hybrid approaches combining standard floorplans/building blocks with custom elements, to highly flexible "SAPUI5 Freestyle" with "Custom Layout" on the right.](images/User_Interface_116cf74.png)
 
 
 
@@ -61,6 +61,4 @@ If the current and foreseeable application UI design requirements comply with SA
 
 -   You can flexibly implement a custom layout and content by combining SAPUI5 with building blocks from the flexible programming model.
 
--   If there's a benefit from using building blocks in a freestyle SAPUI5 application, there's an easy path to integrate the flexible programming model when needed by following the [three-step approach](https://ui5.sap.com/test-resources/sap/fe/core/fpmExplorer/index.html#/buildingBlocks/guidance/guidanceCustomApps). If OData V4 is used and relevant annotations are being maintained in the back end, then such a benefit probably exists:
-
-
+-   If there's a benefit from using building blocks in a freestyle SAPUI5 application, there's an easy path to integrate the flexible programming model when needed by following the [three-step approach](https://ui5.sap.com/test-resources/sap/fe/core/fpmExplorer/index.html#/buildingBlocks/guidance/guidanceCustomApps). If OData V4 is used and relevant annotations are being maintained in the back end, then such a benefit probably exists:
diff --git a/docs/mission-develop-a-multitenant-cap-application-6d2cbe9.md b/docs/mission-develop-a-multitenant-cap-application-6d2cbe9.md
@@ -19,5 +19,4 @@ To try out the multitenant functionality on the Incident Management sample appli
 
 This image is interactive. Click the highlighted areas so you open the respective tutorial or mission.
 
-![](images/Mission_Develop_a_Multitenant_CAP_Application_1f4feba.png)
-
+![A flowchart visually outlines the process for developing a multitenant CAP application. It details steps from initial development and enabling multitenancy, through deployment on either SAP BTP Cloud Foundry or Kyma Runtimes, to subscribing to the application. A legend distinguishes between missions, GitHub repositories, and tutorials based on box color.](images/Mission_Develop_a_Multitenant_CAP_Application_1f4feba.png)
diff --git a/docs/mission-develop-a-side-by-side-cap-based-extension-application-2289e25.md b/docs/mission-develop-a-side-by-side-cap-based-extension-application-2289e25.md
@@ -35,5 +35,4 @@ See [Develop a Side-by-Side CAP-Based Extension Application Following the SAP BT
 
 This image is interactive. Click the highlighted areas so you open the respective tutorial or mission.
 
-![](images/Connect_to_a_Remote_Service_Based_on_the_Starter_Mission_82400ab.png)
-
+![A flowchart illustrating various pathways for connecting to a remote service and setting up eventing within SAP BTP, encompassing different development approaches, runtime environments (Cloud Foundry, Kyma), and integrations with SAP Destination and Event Mesh services.](images/Connect_to_a_Remote_Service_Based_on_the_Starter_Mission_82400ab.png)
diff --git a/docs/mission-develop-an-enterprise-grade-cap-application-b5be786.md b/docs/mission-develop-an-enterprise-grade-cap-application-b5be786.md
@@ -10,5 +10,4 @@ See [Develop an Enterprise-Grade CAP Application Following the SAP BTP Developer
 
 This image is interactive. Click the highlighted areas so you open the respective tutorial or mission.
 
-![](images/Mission_Develop_an_Enterprise-Grade_CAP_Application_Following_the_SAP_BTP_Developer_s_Guide_43b74ca.png)
-
+![A flowchart illustrating the development of an enterprise-grade CAP application, connecting foundational missions (blue), a reference GitHub repository (light blue), and specific feature tutorials (gray).](images/Mission_Develop_an_Enterprise-Grade_CAP_Application_Following_the_SAP_BTP_Developer_s_Guide_43b74ca.png)
diff --git a/docs/mission-implement-observability-in-a-full-stack-cap-application-c5636db.md b/docs/mission-implement-observability-in-a-full-stack-cap-application-c5636db.md
@@ -12,5 +12,4 @@ See [Implement Observability in a Full-Stack CAP Application Following SAP BTP D
 
 This image is interactive. Click the highlighted areas so you open the respective tutorial or mission.
 
-![](images/Implement_Observability_Based_on_the_Starter_Mission_ecb3950.png)
-
+![A flowchart titled "Implement Observability Based on the Starter Mission" depicts the process for implementing observability in SAP CAP applications. It starts with a main mission (dark blue), leading to application development and incident management setup (light blue boxes). Subsequent steps are detailed as tutorials (grey boxes) covering log, trace, and metrics collection, enabling observability in SAP BTP runtimes, and utilizing SAP Cloud ALM.](images/Implement_Observability_Based_on_the_Starter_Mission_ecb3950.png)
diff --git a/docs/operating-with-sap-cloud-alm-f7f2977.md b/docs/operating-with-sap-cloud-alm-f7f2977.md
@@ -29,7 +29,7 @@ SAP Cloud ALM is the central place to integrate and access the monitoring of you
 
 Inbound and outbound APIs enable you to integrate data from your own applications. For more information, see the [API Guide for SAP Cloud ALM](https://help.sap.com/docs/cloud-alm/apis/api-reference).
 
-![](images/SAPCloudALM_operations_d378eed.jpg)
+![A process flow diagram illustrating problem management, from inbound data integration and various detection methods (monitoring, analysis) to intelligent event routing and problem resolution (alerts, notifications, analytics, automation), concluding with outbound integrations. Business Service Management oversees the entire process.](images/SAPCloudALM_operations_d378eed.jpg)
 
 
 
@@ -48,5 +48,4 @@ Inbound and outbound APIs enable you to integrate data from your own application
 **Related Information**  
 
 
-[Operate](operate-34065a4.md "")
-
+[Operate](operate-34065a4.md "")
Original file line number	Diff line number	Diff line change
Expand Up		@@ -8,5 +8,4 @@ You can use data integration to exchange data between two or more parties withou

		Process integration requirements can span data exchange across system boundaries, like, for example, initiating follow-on actions with events when a value in an app is changed.

		![](images/Design_an_Integration_Service_c04a651.png)

		![A multi-layered architectural model illustrating the hierarchy from consumer-facing business services, through integration services for exposure and consumption, down to domain-specific programming (ABAP, Core Data Services) and data access points like SAP HANA.](images/Design_an_Integration_Service_c04a651.png)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -19,5 +19,4 @@ To try out the multitenant functionality on the Incident Management sample appli

		This image is interactive. Click the highlighted areas so you open the respective tutorial or mission.

		![](images/Mission_Develop_a_Multitenant_CAP_Application_1f4feba.png)

		![A flowchart visually outlines the process for developing a multitenant CAP application. It details steps from initial development and enabling multitenancy, through deployment on either SAP BTP Cloud Foundry or Kyma Runtimes, to subscribing to the application. A legend distinguishes between missions, GitHub repositories, and tutorials based on box color.](images/Mission_Develop_a_Multitenant_CAP_Application_1f4feba.png)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -35,5 +35,4 @@ See [Develop a Side-by-Side CAP-Based Extension Application Following the SAP BT

		This image is interactive. Click the highlighted areas so you open the respective tutorial or mission.

		![](images/Connect_to_a_Remote_Service_Based_on_the_Starter_Mission_82400ab.png)

		![A flowchart illustrating various pathways for connecting to a remote service and setting up eventing within SAP BTP, encompassing different development approaches, runtime environments (Cloud Foundry, Kyma), and integrations with SAP Destination and Event Mesh services.](images/Connect_to_a_Remote_Service_Based_on_the_Starter_Mission_82400ab.png)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -10,5 +10,4 @@ See [Develop an Enterprise-Grade CAP Application Following the SAP BTP Developer

		This image is interactive. Click the highlighted areas so you open the respective tutorial or mission.

		![](images/Mission_Develop_an_Enterprise-Grade_CAP_Application_Following_the_SAP_BTP_Developer_s_Guide_43b74ca.png)

		![A flowchart illustrating the development of an enterprise-grade CAP application, connecting foundational missions (blue), a reference GitHub repository (light blue), and specific feature tutorials (gray).](images/Mission_Develop_an_Enterprise-Grade_CAP_Application_Following_the_SAP_BTP_Developer_s_Guide_43b74ca.png)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -12,5 +12,4 @@ See [Implement Observability in a Full-Stack CAP Application Following SAP BTP D

		This image is interactive. Click the highlighted areas so you open the respective tutorial or mission.

		![](images/Implement_Observability_Based_on_the_Starter_Mission_ecb3950.png)

		![A flowchart titled "Implement Observability Based on the Starter Mission" depicts the process for implementing observability in SAP CAP applications. It starts with a main mission (dark blue), leading to application development and incident management setup (light blue boxes). Subsequent steps are detailed as tutorials (grey boxes) covering log, trace, and metrics collection, enabling observability in SAP BTP runtimes, and utilizing SAP Cloud ALM.](images/Implement_Observability_Based_on_the_Starter_Mission_ecb3950.png)