Merge branch 'main' into patricebender-patch-1

get-started/samples.md

@@ -98,3 +98,22 @@ The Sustainable SaaS (SusaaS) sample application has been built in a partner col
 Available for:
 
 [![Node.js logo](../assets/logos/nodejs.svg 'Link to the Sustainable SaaS (SusaaS) repository.'){style="height:2.5em; display:inline; margin:0 0.2em;"}](https://github.com/SAP-samples/btp-cap-multitenant-saas)
+
+
+## Partner Reference App {.github}
+
+The Partner Reference Application repository provides you with a “golden path” to becoming a SaaS provider of multi-tenant applications based on the SAP Business Technology Platform (SAP BTP).
+The guidance covers building, running, and integrating scalable full-stack cloud applications. It includes an ERP-agnostic design that lets you deliver your application as a side-by-side extension to consumers using any SAP solution, such as SAP S/4HANA Cloud, SAP Business One, and SAP Business ByDesign.
+
+By using BTP services and the SAP Cloud Application Programming Model (CAP), your application meets SAP standards for enterprise-class business solutions. It offers a harmonized user experience and seamless integration, including:
+- centralized identity and access management,
+- a common launchpad,
+- cross-application front-end navigation,
+- and secure back-channel integration.
+
+The repository includes the “Poetry Slam Manager” application as a ready-to-run example. It also provides tutorials on how to build the application from scratch using an incremental development approach.
+Based on this sample application, you will find the bill of materials and a sizing example. This addresses the question "Which BTP resources do I need to subscribe to and in what quantities?" and serves as a basis for cost calculation.
+
+Available for:
+
+[![Node.js logo](../assets/logos/nodejs.svg 'Link to the Partner Reference app repository.'){style="height:2.5em; display:inline; margin:0 0.2em;"}](https://github.com/SAP-samples/partner-reference-application)

guides/databases-postgres.md

@@ -370,6 +370,12 @@ When redeploying after you changed your CDS models, like adding fields, automati
 
 > You can disable automatic schema evolution, if necessary, by setting <Config>cds.requires.db.schema_evolution = false</Config>.
 
+::: danger No manual altering
+
+Manually altering the database will most likely break automatic schema evolution!
+
+:::
+
 ### Limitations
 
 Automatic schema evolution only allows changes without potential data loss.

guides/messaging/s4.md

@@ -9,10 +9,6 @@ SAP S/4HANA integrates SAP Event Mesh as well as SAP Cloud Application Event Hub
 Hence, it is relatively easy for CAP-based application to receive events from SAP S/4HANA systems.
 This guide provides detailed information on that.
 
-::: tip See also:
-[Tutorial: Consume Events from SAP S/4HANA Cloud Using CAP](https://developers.sap.com/mission.btp-consume-events-s4hana-cloud-cap.html)
-:::
-
 [[toc]]
 
 

guides/using-services.md

@@ -52,12 +52,8 @@ For outbound remote service consumption, the following features are supported:
 + [Projections on remote services](#supported-projection-features)
 
 ### Tutorials and Examples
-
-Most snippets in this guide are from the [Build an Application End-to-End using CAP, Node.js, and VS Code](https://developers.sap.com/mission.btp-application-cap-e2e.html) tutorial, in particular [Consume Remote Services from SAP S/4HANA Cloud Using CAP](https://developers.sap.com/mission.btp-consume-external-service-cap.html).
-
 | Example                                                                                                                            | Description                                                                               |
 | ---------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
-| [Consume Remote Services from SAP S/4HANA Cloud Using CAP](https://developers.sap.com/mission.btp-consume-external-service-cap.html) | End-to-end Tutorial, Node.js, SAP S/4HANA Cloud, SAP Business Accelerator Hub |
 | [Capire Bookshop (Fiori)](https://github.com/sap-samples/cloud-cap-samples/tree/main/fiori)                                                                                           | Example, Node.js, CAP-to-CAP                                                              |
 | [Example Application (Node.js)](https://github.com/SAP-samples/cloud-cap-risk-management/tree/ext-service-s4hc-suppliers-ui)       | Complete application from the end-to-end Tutorial                                         |
 | [Example Application (Java)](https://github.com/SAP-samples/cloud-cap-risk-management/tree/ext-service-s4hc-suppliers-ui-java)     | Complete application from the end-to-end Tutorial                                         |
@@ -73,8 +69,7 @@ You have all your answers and know your scenario, go on reading about [external
 
 #### Sample Scenario from End-to-End Tutorial
 
-<!-- Bookshop, SFlight, Incidents Mgmt, Risk Mgmt, Orders Mgmt. etc. -> we might want to cut down on our sample scenarios  -->
-The risk management use case of the previously mentioned [tutorial](https://developers.sap.com/mission.btp-application-cap-e2e.html) shows you one possible scenario:
+<!-- Bookshop, SFlight, Incidents Mgmt, Orders Mgmt. etc. -> we might want to cut down on our sample scenarios  -->
 
 ![A graphic showing the flow for one possible scenario. A user can either view risks or view the suppliers. The suppliers master data is already available from a system and is consumed in an application that enables the user to add the risks. From the maintained risks the user can get information about the supplier connected to a risk. From the supplier view, it's also possible to get details about a risk that is associated with a supplier. The user can block/unblock suppliers from the risk view.](./assets/using-services/risk-mgmt.drawio.svg){style="width: 500px"}