Update from SAP DITA CMS (squashed):

commit 487ad44df6146adda8acb97e8956cb81b140b5a7
Author: REDACTED
Date:   Wed Sep 3 14:58:33 2025 +0000

    Update from SAP DITA CMS 2025-09-03 14:58:33

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

commit ba2cc6f2a3b1494467c96c664662d1bb0cd2e7aa
Author: REDACTED
Date:   Wed Sep 3 14:32:41 2025 +0000

    Update from SAP DITA CMS 2025-09-03 14:32:41

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

commit 528d2b8909f0e43cd04bf44bc01458ccb68c0f00
Author: REDACTED
Date:   Tue Sep 2 18:28:26 2025 +0000

    Update from SAP DITA CMS 2025-09-02 18:28:26

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap

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

Author: ditaccms-bot

docs/10-concepts/regions-and-api-endpoints-for-the-abap-environment-879f373.md

@@ -1074,6 +1074,53 @@ Google Cloud
 </td>
 <td valign="top">
 
+il30
+
+</td>
+<td valign="top">
+
+Israel \(Tel Aviv\)
+
+</td>
+<td valign="top">
+
+cf-il30
+
+</td>
+<td valign="top">
+
+me-west1
+
+</td>
+<td valign="top">
+
+34.165.172.174, 34.165.28.224, 34.165.26.44, 34.165.46.220, 34.165.133.5, 34.165.21.8
+
+</td>
+<td valign="top">
+
+api.cf.il30.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+il30.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+[https://emea.cockpit.btp.cloud.sap/](https://emea.cockpit.btp.cloud.sap/)
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+Google Cloud
+
+</td>
+<td valign="top">
+
 in30
 
 </td>
@@ -1215,6 +1262,100 @@ Google Cloud
 </td>
 <td valign="top">
 
+sa30
+
+</td>
+<td valign="top">
+
+KSA \(Dammam - KSA Regulated Customers\)
+
+</td>
+<td valign="top">
+
+cf-sa30
+
+</td>
+<td valign="top">
+
+me-central2
+
+</td>
+<td valign="top">
+
+34.166.122.101, 34.166.13.193, 34.166.133.79, 34.166.95.100, 34.166.102.25, 34.166.180.181
+
+</td>
+<td valign="top">
+
+api.cf.sa30.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+sa30.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+[https://emea.cockpit.btp.cloud.sap/](https://emea.cockpit.btp.cloud.sap/)
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+Google Cloud
+
+</td>
+<td valign="top">
+
+sa31
+
+</td>
+<td valign="top">
+
+KSA \(Dammam - KSA Non-Regulated Customers\)
+
+</td>
+<td valign="top">
+
+cf-sa31
+
+</td>
+<td valign="top">
+
+me-central2
+
+</td>
+<td valign="top">
+
+34.166.162.172, 34.166.125.210, 34.166.181.228, 34.166.70.80, 34.166.99.127, 34.166.92.192
+
+</td>
+<td valign="top">
+
+api.cf.sa31.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+sa31.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+[https://emea.cockpit.btp.cloud.sap/](https://emea.cockpit.btp.cloud.sap/)
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+Google Cloud
+
+</td>
+<td valign="top">
+
 us30
 
 </td>

docs/10-concepts/using-free-service-plans-524e108.md

@@ -95,7 +95,7 @@ Once you've reached the limits of the free plan, you can upgrade the free servic
 > ### Note:  
 > To update the ABAP environment to a paid service plan, you first need to configure entitlements and quotas for the ABAP environment. You need at least the following entitlements assigned to your subaccount:
 > 
-> -   service plan: *standard*
+> -   service plan: *standard* or build-runtime \(service ABAP Environment\)
 > 
 > -   quota plans:
 > 

docs/20-getting-started/tutorial-overview-5de8374.md

@@ -259,6 +259,8 @@ without group/mission:
 
 -   [Integrate released Purchase Requisition API into Online Shop Business Object](https://developers.sap.com/mission.abap-env-intermediate.html)
 
+-   [Integrate List Report into SAP Fiori Launchpad](https://developers.sap.com/tutorials/abap-s4hanacloud-procurement-purchasereq-flp.html?locale=en-US)
+-   [Create a SAP Fiori App and Deploy it to SAP S/4HANA Cloud, ABAP Environment](https://developers.sap.com/tutorials/abap-s4hanacloud-procurement-purchasereq-shop-ui.html)
 
 
 

docs/20-getting-started/updating-an-abap-system-7890ffa.md

@@ -62,12 +62,12 @@ Your ABAP environment instance is being updated. This might take a while.
 
 ## Change the Service Plan of Your Service Instance
 
-Once you've reached the limits of the free plan, you can upgrade the free service plan to a paid plan.
+You can update the service plan from one ABAP environment service plan to another. For example: once you've reached the limits of the free plan, you can upgrade the free service plan to a paid plan \(standard plan or build-runtime plan\). You could also update your standard plan to a build-runtime plan if you have a SAP Build subscription that includes quota for the ABAP environment service.
 
 > ### Note:  
 > To update the ABAP environment to a paid service plan, you first need to configure entitlements and quotas for the ABAP environment. You need at least the following entitlements assigned to your subaccount:
 > 
-> -   service plan: standard
+> -   service plan: standard or build-runtime \(service ABAP Environment\)
 > 
 > -   quota plans:
 > 
@@ -86,12 +86,12 @@ Once you've reached the limits of the free plan, you can upgrade the free servic
 
 2.  Find the instance of the service and click <span class="SAP-icons-V5"></span> \(Actions\) and *Update*.
 
-3.  In the *Update Instance* dialog, change the plan to a paid service plan.
+3.  In the *Update Instance* dialog, change the plan to a new service plan. The following changes are possible:
 
-4.  To switch from a `standard` or `free` service plan to a `build-runtime` service plan, make sure you have the entitlement for the service plan `build-runtime` \(service `ABAP Environment`\) and choose *build-runtime* in the *Update Instance* dialog.
+    -   From free to standard
+    -   From free to build-runtime
+    -   From standard to build-runtime
 
-5.  Click *Update Instance* to save your changes.
-
-6.  You can now use the service without the limitations of the free service plan.
+4.  Click *Update Instance* to save your changes.
 
 

docs/30-development/accessing-abap-managed-data-using-sql-services-for-data-integration-scenarios-4082fe1.md

@@ -4,29 +4,27 @@
 
 As a developer in the ABAP environment, you can expose CDS view entities in an ABAP system for external consumption using SQL services.
 
-Using the open database connectivity \(ODBC\) as a standard API for accessing databases, you can use SQL statements in external analytical tools to access the data of these CDS view entities from your ABAP system and formulate ad-hoc SQL queries on your data. You can also use the exposed CDS view entities from SQL services to set up data replication for further processing of the data and combining it with data from other data sources.
+Using the open database connectivity \(ODBC\) as a standard API for accessing databases, you can use SQL statements in external applications to access the data of these CDS view entities from your ABAP system and formulate ad-hoc SQL queries on your data.
 
 
 
 <a name="loio4082fe1b66164eeb8aa41192166526af__section_jmw_lw4_vzb"/>
 
 ## Why SQL Services?
 
-There are situations where you would like to have external SQL read access to CDS objects owned by the ABAP system. Direct SQL read access to the underlying SAP HANA database of an ABAP system isn't recommended because, for example, ABAP-level security concepts are bypassed and typecasts might not be performed as expected \(see also SAP Note [2511210](https://me.sap.com/notes/2511210)\).
+There are situations where you would like to have external SQL access to CDS objects owned by the ABAP system. Direct SQL access to the underlying SAP HANA database of an ABAP system isn't recommended because, for example, ABAP-level security concepts are bypassed and typecasts might not be performed as expected \(see also SAP Note [2511210](https://me.sap.com/notes/2511210)\).
 
-Security concerns and other aspects such as authentication and authorization don't arise if you treat the ABAP system itself as a database by accessing the ABAP system directly using the SQL service exposure. In this case, authentication and authorization are done using an ABAP user. Full ABAP SQL semantics apply and even buffering on application server level can be used as well as ABAP-level access control and read access logging.
+Security concerns and other aspects such as authentication and authorization don't arise if you treat the ABAP system itself as a database by accessing the ABAP system directly using the SQL service exposure. In this case, authentication and authorization are done using an ABAP user. Full ABAP SQL semantics apply and even buffering on application server level can be used as well as ABAP-level access control and access logging.
 
 Compared to the OData interface, the SQL service exposure has the advantage that it allows for unrestricted SQL access to all exposed ABAP CDS view entities. Data from different entities can be joined in an ad-hoc fashion and data can be aggregated for analytical queries.
 
 
 
 <a name="loio4082fe1b66164eeb8aa41192166526af__section_klk_3jn_c1c"/>
 
-## Data Integration Patterns and Scenarios
+## Data Integration Scenarios
 
-Data access patterns for ABAP-managed data can be categorized into data federation and data replication, as well as privileged access and business user access. Data federation allows for live access to the source system without replicating the data, while data replication involves replicating the data to a second system for local execution. Privileged access enables communication between an SQL-based client and the ABAP system using a communication user. \(The communication user is a non-restricted technical power user or represents a technical system.\) Business user access applies access controls to limit data access based on authorizations of the business user.
-
-Examples of data consumption scenarios include data consumption using external ODBC clients like Microsoft Excel and LibreOffice, which can work with both privileged and business user access. Another example is data consumption using SAP Datasphere, where data is replicated from an ABAP system to SAP Datasphere for analytical scenarios.
+Examples of data integration scenarios include data consumption using external ODBC clients like Microsoft Excel and LibreOffice. Another example is data consumption using SAP HANA Cloud, where ABAP-managed data is accessed from SAP HANA Cloud for analytical scenarios.
 
 
 
@@ -36,7 +34,5 @@ Examples of data consumption scenarios include data consumption using external O
 
 For more information and a detailed end-to-end setup description, see the ABAP integration and connectivity guide on SAP Help Portal:
 
-[Data Integration](https://help.sap.com/docs/abap-cloud/abap-integration-connectivity/data-integration) \(concept and architecture overview\)
-
-[Data Integration](https://help.sap.com/docs/abap-cloud/abap-integration-connectivity/data-integration-84537caeb611420b9f3435efce209ef7) \(developer guide\)
+[Data Integration](https://help.sap.com/docs/ABAP_Cloud/eede1416d18c436e8810eaaeb20c38ae/50510582442e4e5d967cb88f3b7a2791.html) 
 

docs/30-development/development-in-classic-abap-e79a5b7.md

@@ -105,7 +105,7 @@ As shown in the above snippets, a callback class can be provided that allows pro
 
 ## Raising an intermediate message event for a SAP Build Process Automation process instance
 
-If the process expects a intermediate message event, this can be raised via the following code.
+If the process expects a intermediate message event \(IME\), this can be raised via the following code.
 
 > ### Sample Code:  
 > Raise an intermediate message event \(deprecated\)
@@ -133,6 +133,33 @@ If the process expects a intermediate message event, this can be raised via the
 > COMMIT WORK.
 > ```
 
+This approach works only for **old** workflow management process definitions being deployed from SAP Business Application Studio.
+
+For SAP Build Process Automation processes, you nee to trigger a intermediate message event by executing the corresponding API trigger, which can be done through the API as follows \(from SAP\_CLOUD 2511 / OP 2027 onwards\).
+
+> ### Sample Code:  
+> Raise an intermediate message event
+
+```abap
+
+CONSTANTS: lc_cp_workflow_def_id TYPE if_swf_cpwf_api=>cpwf_def_id      VALUE '<Your Workflow Definition ID>',
+              lc_api_trigger_uid    TYPE if_swf_cpwf_api=>cpwf_trigger_uid VALUE '<Your API Trigger UID>'.
+
+" Get a Instance for the CPWF Integration API
+   DATA(lo_cpwf_api) = cl_swf_cpwf_api_factory...=>get_api_instance( ... ).
+
+" actually raise the event
+   lo_cpwf_api->api_trigger(
+     EXPORTING
+       iv_cpwf_handle   = lv_cpwf_handle  " the BTP process instance handle
+       iv_event_def_id  = lc_api_trigger_uid
+   ).
+ 
+   COMMIT WORK.
+```
+
+Open your process in the SAP Build Process Automation Control Tower and check the list of triggers. View the trigger details to find the API trigger UID.
+
 
 
 <a name="loioe79a5b768e7a4d94b7aad204653475c6__section_wyg_3kg_42c"/>
@@ -146,9 +173,9 @@ For example, you can query the current lifecycle status of processes.
 > ### Sample Code:  
 > Read Workflow Instances
 > 
-> ```abap
+> ```
 > " Get a Instance for the CPWF Integration API
-> DATA(lo_cpwf_api) = cl_swf_cpwf_api_factory_a4c...=>get_api_instance( ... ).
+> DATA(lo_cpwf_api) = cl_swf_cpwf_api_factory...=>get_api_instance( ... ).
 > DATA(lo_wf_inst) = lo_cpwf_api->if_swf_cpwf_capi~get_workflow_instances_api( ).
 >  
 > DATA(lt_workflow_instance) = lo_wf_inst->query_instances(
@@ -157,7 +184,7 @@ For example, you can query the current lifecycle status of processes.
 > ).
 > ```
 
-or retrieve the current context:
+Or retrieve the current context:
 
 > ### Sample Code:  
 > Read Workflow Instance Context
@@ -170,7 +197,8 @@ or retrieve the current context:
 >        END OF ty_context.     
 >  
 > " Get a Instance for the CPWF Integration API
-> DATA(lo_cpwf_api) = cl_swf_cpwf_api_factory_a4c...=>get_api_instance( ... ).  DATA(lo_cp_json) = lo_cpwf_api->get_json_converter( ).
+> DATA(lo_cpwf_api) = cl_swf_cpwf_api_factory...=>get_api_instance( ... ). 
+> DATA(lo_cp_json) = lo_cpwf_api->get_json_converter( ).
 > DATA(lo_wf_inst_ctxt) = lo_cpwf_api->if_swf_cpwf_capi~get_wf_instance_context_api( ).
 >   
 > DATA ls_context TYPE ty_context.
@@ -185,7 +213,7 @@ As shown in the code there is also a JSON converter available to simplify the pr
 
 ## Restricting the retrieved process context
 
-To allow retrieving only relevant parts of the process context the APIs `IF_SWF_CPWF_API` →get\_workflow\_context and `IF_SWF_CPWF_CAPI_WF_INST_CTXT`-\>get\_instance\_context allow to provide an additional parameter `IV_CONTEXT_PATH`, that accepts any JSON path expression \(see SBPA API description\). This expression is forwarded to the Workflow API of SAP Build Process Automation. The JSON path expression is evaluated by the SBPA Workflow Service API, which returns then only the corresponding substructure of the context.
+To allow retrieving only relevant parts of the process context the APIs `IF_SWF_CPWF_API` →get\_workflow\_context and `IF_SWF_CPWF_CAPI_WF_INST_CTXT`-\>get\_instance\_context allow to provide an additional parameter `IV_CONTEXT_PATH`, that accepts any JSON path expression \(see SBPA API description\). This expression is forwarded to the Workflow API of SAP Build Process Automation. The JSON path expression is evaluated by the SAP Build Process Automation Workflow Service API, which returns then only the corresponding substructure of the context.
 
 The following examples show how the `IV_CONTEXT_PATH` parameter can be used.
 
@@ -282,3 +310,23 @@ The following examples show how the `IV_CONTEXT_PATH` parameter can be used.
 > "here"
 > ```
 
+
+
+<a name="loioe79a5b768e7a4d94b7aad204653475c6__section_vvf_dlb_kgc"/>
+
+## **API Enhancements \(2508 Cloud / 2025 OP\)**
+
+
+
+<a name="loioe79a5b768e7a4d94b7aad204653475c6__section_y4q_tmy_kgc"/>
+
+## API Enhancements \(2511 Cloud / 2027 OP\)
+
+-   Two new methods are available for executing specific triggers:
+
+    -   `API_TRIGGER`
+    -   `API_TRIGGER_BY_ID`
+
+    These methods replace the previous `API_RAISE_EVENT`used for triggering intermediate message events.
+
+