Update from SAP DITA CMS (squashed):

commit 590c6d9dfef531a68f9a73c6e664fa1df82b8779
Author: REDACTED
Date:   Mon Sep 1 09:49:59 2025 +0000

    Update from SAP DITA CMS 2025-09-01 09:49:59

    Project: dita-all/mfv1753212261668
    Project map: af2fcb3e6dd448f3af3c0ff9c70daaf9.ditamap
    Output: loiob8faae83b519439fb4ea9d0eb1a5f26e
    Language: en-US
    Builddable map: 4e1c1e1d5d1947f5875e93e7597c4f4c.ditamap

commit 26fa867869313892ab230449ff0d55d7da05ecd4
Author: REDACTED
Date:   Mon Sep 1 09:40:50 2025 +0000

    Update from SAP DITA CMS 2025-09-01 09:40:50

    Project: dita-all/mfv1753212261668
    Project map: af2fcb3e6dd448f3af3c0ff9c70daaf9.ditamap
    Output: loiob8faae83b519439fb4ea9d0eb1a5f26e
    Language: en-US
    Builddable map: 4e1c1e1d5d1947f5875e93e7597c4f4c.ditamap

commit 553832eb4d287d1f6aa149e2d50647bcbd6323b9
Author: REDACTED
Date:   Tue Aug 19 11:40:36 2025 +0000

    Update from SAP DITA CMS 2025-08-19 11:40:36

    Project: dita-all/mfv1753212261668
    Project map: af2fcb3e6dd448f3af3c0ff9c70daaf9.ditamap

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

Author: ditaccms-bot

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/acquiring-data-1f15a29.md

@@ -102,7 +102,7 @@ You can import data from a CSV file to create a new local table \(see [Creating
 
 ## Purchase Data from Data Marketplace
 
-Purchase data products from providers and download them directly into your space \(see  <?sap-ot O2O class="- topic/xref " href="4096fb8c97dd4d84a7200941c1721368.xml" text="" desc="" xtrc="xref:47" xtrf="file:/home/builder/src/dita-all/pug1751957928638/loioc25299a38b6448f889a43b42c9e5897d_en-US/src/content/localization/en-us/f3888e57ce0a4afa9759abc3bdb9befd.xml" output-class="" outputTopicFile="file:/home/builder/tp.net.sf.dita-ot/2.3/plugins/com.elovirta.dita.markdown_1.3.0/xsl/dita2markdownImpl.xsl" ?> \).
+Purchase data products from providers and download them directly into your space \(see [Evaluating and Installing Marketplace Data Products](../evaluating-and-installing-marketplace-data-products-92c35ef.md)\).
 
 You can become a data provider and offer your own data products for sale in Data Marketplace via the Data Sharing Cockpit \(see [Data Marketplace - Data Provider's Guide](https://help.sap.com/viewer/bb1899f0b39f415b9de29a845873d7af/DEV_CURRENT/en-US/e479b7b4c95741c7a7a1d42397984c7e.html "Users with a modeler role can create a data provider profile and publish data products to public, private, and internal Data Marketplaces.") :arrow_upper_right:\).
 

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/cloud-storage-provider-sources-4d481a2.md

@@ -22,6 +22,7 @@ The following cloud storage providers can be used as the source of a replication
 
 -   Microsoft Azure Data Lake Gen2
 
+-   Microsoft OneLake
 
 For more information about the corresponding connection types, see [Integrating Data via Connections](https://help.sap.com/docs/SAP_DATASPHERE/be5967d099974c69b77f4549425ca4c0/eb85e157ab654152bd68a8714036e463.html).
 

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/configure-a-replication-flow-3f5ba0c.md

@@ -14,15 +14,13 @@ Define settings and properties for your replication flow and individual replicat
 
     -   *Initial Only*: Load all selected data once.
 
-    -   *Initial and Delta*: After the initial load, the system checks for source data changes \(delta\) at regular intervals and copies the changes to the target. The default value for the delta load interval is 60 minutes. You can change it in the side panel by entering an integer between 0 and 24 for hours and 0 and 59 for minutes, respectively. The maximum allowed value is 24 hours 0 minutes. If you enter 0 hours and 0 minutes, the system replicates any source changes immediately.
+    -   *Initial and Delta*: After the initial load, the system checks for source data changes \(delta\) at regular intervals and copies the changes to the target. The default value for the delta load interval is 60 minutes. You can change it in the side panel by entering an integer between 0 and 24 for hours and 0 and 59 for minutes, respectively. The maximum allowed value is 24 hours 0 minutes. If you enter 0 hours and 0 minutes, the system replicates any source changes immediately. 
 
         > ### Note:  
         > -   A replication flow that contains objects with load type *Initial and Delta* does not have an end date. Once started, it remains in status *Active* until it is stopped or paused or an issue occurs.
         > 
         >     > ### Caution:  
-        >     > You must always stop or pause a running replication flow before a source system downtime. For more information, see [Working With Existing Replication Flow Runs](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/da62e1ee746448e8bc043e1be4377cbe.html "You can pause a replication flow run and resume it at a later point in time, or you can stop it completely.") :arrow_upper_right:
-        > 
-        >     .
+        >     > You must always stop or pause a running replication flow before a source system downtime. For more information, see [Working With Existing Replication Flow Runs](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/da62e1ee746448e8bc043e1be4377cbe.html "You can pause a replication flow run and resume it at a later point in time, or you can stop it completely.") :arrow_upper_right:.
         > 
         > -   The system load caused by the delta load operations can vary substantially depending on the frequency of changes in your data source in combination with the interval length you define. Make sure that your tenant configuration supports your settings. For more information, see [Configure the Size of your SAP Datasphere Tenant](https://help.sap.com/docs/SAP_DATASPHERE/9f804b8efa8043539289f42f372c4862/33f8ef4ec359409fb75925a68c23ebc3.html).
         > 
@@ -103,7 +101,7 @@ Define settings and properties for your replication flow and individual replicat
 
 5.  Review the settings for the individual replication objects and change or complete them as appropriate.
 
-    To do so, select the relevant repliation object. Its properties are then displayed in the side panel.
+    To do so, select the relevant replication object. Its properties are then displayed in the side panel.
 
     For a list of properties and further information, see [Creating a Replication Flow](creating-a-replication-flow-25e2bd7.md).
 

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/creating-a-local-table-2509fe4.md

@@ -118,6 +118,18 @@ In addition to working with tables in the editor, you can also:
 
 
 
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+    
+     
+    
+    </td>
+    <td valign="top">
+    
+    \[dimensions only\]
+    
     </td>
     </tr>
     <tr>
@@ -394,6 +406,22 @@ In addition to working with tables in the editor, you can also:
 
     See [Impact and Lineage Analysis](../impact-and-lineage-analysis-9da4892.md).
 
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+    
+    <span class="SAP-icons-V5"></span> \(Generate\)
+    
+    </td>
+    <td valign="top">
+    
+    Open the AI-assisted generation menu: 
+
+    -   Generate Semantics - Identify the semantic usage of your entity and the semantic types of its columns \(see [Generating Semantic Information](../Modeling-Data-in-the-Data-Builder/generating-semantic-information-2fc1d26.md)\).
+
+
+    
     </td>
     </tr>
     <tr>

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/creating-a-replication-flow-25e2bd7.md

@@ -21,7 +21,7 @@ You can use replication flows to copy data from the following source objects:
 
 CDS views and ODP artifacts that do not have a primary key can be used as the source for a replication flow if certain prerequisites are met. For more information, see [Using an Object Without Primary Key As the Source](using-an-object-without-primary-key-as-the-source-2267a9f.md).
 
-For more information about available connection types, sources, and targets, see .
+For more information about available connection types, sources, and targets, see [Connection Types Supporting Replication Flows](https://help.sap.com/docs/SAP_DATASPHERE/be5967d099974c69b77f4549425ca4c0/94562426f30c475286f50a1e2b45e743.html?connection_overview-rf=yes%20(source)&connection_overview-rf=yes%20(target)&connection_overview-rf=yes%20(source%20and%20target)&connection_overview-rf=via%20connection%20type%20SAP%20ABAP%20Connections%20(source)).
 
 > ### Note:  
 > To make sure that you have the most up-to-date information and important considerations regarding replication flows, please read SAP Note [3297105](https://me.sap.com/notes/3297105) **before** you start creating a replication flow.

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/define-mappings-in-a-replication-flow-2c7948f.md

@@ -35,6 +35,18 @@ Create mappings to specify how the source data is to be changed on its way into
 
     -   Add a new column: Choose *Add* and enter the necessary values for the new column.
 
+        To add a new column with string, number constants, or current UTC datetime functions:
+
+        1.  Click on Add to add the Column.
+        2.  Select the checkbox field under the Functions / Constant tab.
+        3.  Update target Column\(Technical Name\) and target Column\(Business Name\) as needed.
+        4.  Add the either of the following 3 functions in cell Functions / Constant:
+            1.  CURRENT\_UTCDATE - The column will be updated with current UTC date and select datatype as date.
+            2.  CURRENT\_UTCTIME - The column will be updated with current UTC time and select datatype as time.
+            3.  CURRENT\_UTCTIMESTAMP - The column will be updated with current UTC time stamp and select datatype as timestamp.
+
+        5.  For constant select the appropriate datatype\(example string\) and update appropriate value in the cell Functions / Constant.
+
     -   Remove a column: Select the relevant column and choose *Remove*.
 
         > ### Note:  

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/load-or-delete-local-table-data-870401f.md

@@ -94,7 +94,7 @@ To delete table records:
 3.  Depending if your local table is delta enabled or not, you will have different options. In the case of a table that is not delta enabled, you can delete all records contained in the table. In the case of a table that is delta capture enabled, you can choose between 3 options:
     -   Delete All Records: \[Table with or without delta capture\] This option allows you to delete all records from the table, no matter if they are used by other apps or not. It's up to you to check if the data you are about to delete have dependencies.
     -   Delete All Records \(Mark as "Deleted"\): \[Delta capture table only\]. This option doesn't physically delete the records. They will be marked as to be deleted \(they take the Change Type “D”\) but these records can still be processed by other apps until you decide to permanently delete them.
-    -   Delete all records marked for deletion which are older than the specified number of days: \[Delta capture table only\] If your table is delta capture enabled, when a record is deleted, it’s marked as deleted so that it won’t be visible in consuming \(view\) models, but it’s not physically deleted from the database. Indeed such deletion records from local tables with delta capture are considered by flows that are using the load type *Initial and Delta*. The records marked as deleted can’t be physically deleted until they have been processed by these flows. For more information, see [Capturing Delta Changes in Your Local Table](capturing-delta-changes-in-your-local-table-154bdff.md). Once this is given, selecting this option allows you to safely delete records already fully-processed. You also define a retention period.Once this is given, selecting this option allows you to safely delete records already fully-processed according to the retention period you've defined. Default retention period is 90 days.
+    -   Delete all records marked for deletion which are older than the specified number of days: \[Delta capture table only\] If your table is delta capture enabled, when a record is deleted, it’s marked as deleted so that it won’t be visible in consuming \(view\) models, but it’s not physically deleted from the database. Indeed such deletion records from local tables with delta capture are considered by flows that are using the load type *Initial and Delta*. The records marked as deleted can’t be physically deleted until they have been processed by these flows. For more information, see [Capturing Delta Changes in Your Local Table](capturing-delta-changes-in-your-local-table-154bdff.md). Once this is given, selecting this option allows you to safely delete records already fully-processed according to the retention period you've defined. Default retention period is 90 days.
 
         > ### Example:  
         > Today, it's January 13, 2025. I have the following table where 5 records have been marked for deletion. To make it easier, we will consider that all records have been fully-processed by other apps and are candidates for deletion:

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/load-types-and-connections-for-your-replication-flows-1089119.md

@@ -234,6 +234,28 @@ Supported
 
 Supported
 
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+AzureSQL
+
+</td>
+<td valign="top">
+
+Supported
+
+</td>
+<td valign="top">
+
+Supported
+
+</td>
+<td valign="top">
+
+Supported
+
 </td>
 </tr>
 </table>
@@ -442,6 +464,28 @@ Supported
 
 Not Supported
 
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+SAP Signavio
+
+</td>
+<td valign="top">
+
+Supported
+
+</td>
+<td valign="top">
+
+Supported
+
+</td>
+<td valign="top">
+
+Not Supported
+
 </td>
 </tr>
 </table>

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/maintain-local-table-data-4bd5e64.md

@@ -26,16 +26,17 @@ This topic contains the following sections:
 
 ## Prerequisites
 
-To edit local table data in the Data Editor, you must have a scoped role that grants you the following privileges:
+To edit local table data in the *Data Editor*, you must have a scoped role that grants you the following privileges:
 
--   **Data Warehouse General** \(-R------\) - To access SAP Datasphere.
--   **Data Warehouse Data Builder** \(-RU-----\) – To access the local table **Data Editor** screen in the **Data Builder**. The **DW Modeler** role template, for example, grants this privilege.
--   **Data Warehouse Data Integration**\(-RU-----\) – To load and delete data in a local table. The **DW Integrator** role template, for example, grants this privilege.
--   *Data Warehouse Consumption* \(-RU-----\) – To load and delete data in a local table. . The *DW Consumer*role template, for example, grants this privilege.
--   **Data Warehouse Consumption**\(----E---\) – To edit data in **Data Builder** local tables.
+-   *Data Warehouse General* \(`-R------`\) - To access SAP Datasphere.
+-   *Data Warehouse Data Builder* \(`-RU-----`\) - To access the local table *Data Editor* screen in the *Data Builder*. The *DW Modeler* role template, for example, grants this privilege.
+-   *Data Warehouse Consumption* \(`-RU-E---`\) - To add and delete data in a local table. The *DW Consumer* role template, for example, grants this privilege.
+
+    > ### Note:  
+    > To access the *Data Editor* from the *Data Integration Monitor* app, you need the privileges listed and in addition: *Data Warehouse Data Integration* \(-R------\). The *DW Integrator* role template, for example, grants this privilege.
 
-    For more information, see [Privileges and Permissions](https://help.sap.com/docs/SAP_DATASPHERE/9f804b8efa8043539289f42f372c4862/d7350c6823a14733a7a5727bad8371aa.html?locale=en-US&state=PRODUCTION&version=cloud) and [Standard Roles Delivered with SAP Datasphere](https://help.sap.com/docs/SAP_DATASPHERE/9f804b8efa8043539289f42f372c4862/a50a51d80d5746c9b805a2aacbb7e4ee.html?locale=en-US&state=PRODUCTION&version=cloud).
 
+For more information, see [Privileges and Permissions](https://help.sap.com/viewer/935116dd7c324355803d4b85809cec97/DEV_CURRENT/en-US/d7350c6823a14733a7a5727bad8371aa.html "A privilege represents a task or an area in SAP Datasphere and can be assigned to a specific role. The actions that can be performed in the area are determined by the permissions assigned to a privilege.") :arrow_upper_right: and [Standard Roles Delivered with SAP Datasphere](https://help.sap.com/viewer/935116dd7c324355803d4b85809cec97/DEV_CURRENT/en-US/a50a51d80d5746c9b805a2aacbb7e4ee.html "SAP Datasphere is delivered with several standard roles. A standard role includes a predefined set of privileges and permissions.") :arrow_upper_right:. 
 
 You can only maintain data in local tables that:
 
@@ -320,7 +321,7 @@ To find \(or find and replace\) data in text columns:
     </td>
     <td valign="top">
 
-    Select to ignore partial matches
+    Select to ignore partial matches.
 
     </td>
     </tr>

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/review-and-edit-imported-table-properties-75cea7b.md

@@ -461,6 +461,22 @@ Provide business-friendly names for your table and its columns, identify its sem
 
     See [Impact and Lineage Analysis](../impact-and-lineage-analysis-9da4892.md).
 
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+    
+    <span class="SAP-icons-V5"></span> \(Generate\)
+    
+    </td>
+    <td valign="top">
+    
+    Open the AI-assisted generation menu: 
+
+    -   Generate Semantics - Identify the semantic usage of your entity and the semantic types of its columns \(see [Generating Semantic Information](../Modeling-Data-in-the-Data-Builder/generating-semantic-information-2fc1d26.md)\).
+
+
+    
     </td>
     </tr>
     <tr>