Update from SAP DITA CMS (squashed):

commit 354aab5bc400ba3aacbf99a80da7c41f6e08e001
Author: REDACTED
Date:   Tue Mar 4 10:44:34 2025 +0000

    Update from SAP DITA CMS 2025-03-04 10:44:34

    Project: dita-all/kky1738583959055
    Project map: af2fcb3e6dd448f3af3c0ff9c70daaf9.ditamap
    Output: loiod3d776bb52294a17b48298443a286f55
    Language: en-US
    Builddable map: 89ab8c0ed18c432d8fb87551823e7de7.ditamap

commit f29e340c9c28d82f735cbbc0ee12970e38e71d3a
Author: REDACTED
Date:   Tue Mar 4 10:43:28 2025 +0000

    Update from SAP DITA CMS 2025-03-04 10:43:28

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

commit 2add16f40ec227b00cf75ae7c0e069382ffe6f01
Author: REDACTED
Date:   Tue Mar 4 10:40:20 2025 +0000

    Update from SAP DITA CMS 2025-03-04 10:40:20

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

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

Author: ditaccms-bot

.reuse/dep5

@@ -0,0 +1,8 @@
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: sap-datasphere
+Upstream-Contact: Venet Cindy ([email protected])
+Source: https://github.com/sap-docs/sap-datasphere
+
+Files: *
+Copyright:  2023 SAP SE or an SAP affiliate company and sap-datasphere contributors
+License: CC-BY-4.0

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/acquiring-and-preparing-data-in-the-object-store-2a6bc3f.md

@@ -44,7 +44,7 @@ A user with an administrator role can create a space with SAP HANA data lake fil
 
 ## Load Data with Replication Flows
 
-Users with a modeler role can use replication flows to load data in local tables \(file\) that are stored in a file space \(see [SAP Datasphere Targets](sap-datasphere-targets-12c45eb.md)\). A replication flow writes data files to the inbound buffer \(specific folder in file storage\) of a target local table \(File\). To process data updates from this inbound buffer to the local table \(File\), and therefore make data visible, a merge task has to run via a task chain \(see [Creating a Task Chain](creating-a-task-chain-d1afbc2.md)\). You can monitor the buffer merge status using the *Local Tables \(File\)* monitor \(See [Monitoring Local Tables (File)](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/6b2d0073a8684ee6a59d6f47d00ec895.html "Monitor your local tables (file). Check how and when they were last updated and if new data has still to be merged.") :arrow_upper_right:\).
+Users with a modeler role can use replication flows to load data in local tables \(file\) that are stored in a file space \(see [SAP Datasphere Targets](sap-datasphere-targets-12c45eb.md)\). A replication flow writes data files to the inbound buffer \(specific folder in file storage\) of a target local table \(File\). To process data updates from this inbound buffer to the local table \(File\), and therefore make data visible, a merge task has to run via a task chain \(see [Creating a Task Chain](creating-a-task-chain-d1afbc2.md)\). You can monitor the buffer merge status using the *Local Tables \(File\)* monitor \(See [Monitoring Local Tables (File)](https://help.sap.com/viewer/be5967d099974c69b77f4549425ca4c0/cloud/en-US/6b2d0073a8684ee6a59d6f47d00ec895.html "Monitor your local tables (file). Check how and when they were last updated and if new data has still to be merged.") :arrow_upper_right:\).
 
 
 

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

@@ -29,6 +29,20 @@ Space administrators and integrators prepare connections and other sources to al
 
 Many connections \(including most connections to SAP systems\) support importing remote tables to federate or replicate data \(see [Integrating Data via Connections](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/eb85e157ab654152bd68a8714036e463.html "Users with a space administrator or integrator role can create connections to SAP and non-SAP source systems, including cloud and on-premise systems and partner tools, and to target systems for outbound replication flows. Users with modeler roles can import data via connections for preparation and modeling in SAP Datasphere.") :arrow_upper_right:\).
 
+SAP Datasphere is using two types of adaptors to connect to remote tables:
+
+-   SAP HANA smart data integration \(used in connections with *Data Provisioning* option = *Data Provisioning Agent*\).
+
+-   SAP HANA smart data access adaptors \(used in connections with no *Data Provisioning* option or *Data Provisioning* option = *Cloud Connector* or *Direct*\).
+
+> ### Note:  
+> If your source data comes from an SAP HANA On-Premise system, select the adaptor following your use case:
+> 
+> -   You want to access the data remotely: SAP HANA smart data access \(Data Provisioning Option: Direct\) would be the recommended adaptor to read the data. It allows higher degree of query pushdown to the remote database, leading to better response times and less resource consumption.
+> -   You want to replicate the data into SAP Datasphere: The preferred option for this is to use Replication Flows, see [Creating a Replication Flow](creating-a-replication-flow-25e2bd7.md). In case you require replication for remote tables, SAP HANA smart data integration \(Data Provisioning Option: Data Provisioning Agent\) is the recommended adaptor to push the data. It offers more options when loading the data, such as applying filter conditions or data partitioning.
+> 
+> For more information on these adaptors, see [Connecting SAP HANA Cloud, SAP HANA Database to Remote Data Sources](https://help.sap.com/docs/HANA_CLOUD/db19c7071e5f4101837e23f06e576495/afa3769a2ecb407695908cfb4e3a9463.html).
+
 You can import remote tables to make the data available in your space from the *Data Builder* start page, in an entity-relationship model, or directly as a source in a view.
 
 -   To get started: In the side navigation area, click <span class="FPA-icons-V3"></span> \(*Data Builder*\), select a space if necessary, and click *Import* \> *Import Remote Tables*. See [Import Remote Tables](import-remote-tables-fd04efb.md).

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/cloud-storage-provider-targets-43d93a2.md

@@ -185,6 +185,11 @@ The `.sap.partfile.metadata` objects include metadata information for the replic
 
 The replication flow creates multiple files \(<code>part-*.<i class="varname">&lt;extension&gt;</i></code>\) during initial and delta loading. The number and size of these files depends on the source table size and structure as well as change frequency \(during delta loading\).
 
+> ### Note:  
+> Parquet name files are generated using this logic:
+> 
+> The name pattern is part-<Replication Flow Task ID \(UUID, SAP internal\)\>-<delimitation number of the task \(01 to 60, SAP internal\)\>.parquet. This is just a random UUID+NN that is unique to the whole replication task process, to avoid accidentally overwriting an existing file.
+
 Each file contains the source columns as defined in the mapping for the replication object in the replication flow. The system appends the following columns:
 
 -   *\_\_operation\_type*: Identifies the type of target row:

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

@@ -341,8 +341,9 @@ This procedure explains how to create an empty table by defining its columns. Yo
 
     Delete records:
 
-    -   Standard table - Delete all records
-    -   Delta capture table- Delete all records, Delete all records \(mark as "deleted"\) or Delete all records marked for deletion which are older than the specified number of days.
+    -   Standard table: *Delete All Records* 
+    -   Delta capture table: *Delete All Records*, *Delete Records Marked as "Deleted"*, or *Delete all records marked for deletion which are older than the specified number of days*.
+    -   Local table \(file\): *Delete All Records \(Mark as Deleted\)* or *Delete previous versions \(Vacuum\), which are older than the specified number of days* 
 
     See [Load or Delete Local Table Data](load-or-delete-local-table-data-870401f.md).
 
@@ -379,6 +380,20 @@ This procedure explains how to create an empty table by defining its columns. Yo
     <tr>
     <td valign="top">
 
+    Versions
+    
+    </td>
+    <td valign="top">
+    
+    Open the *Version History* dialog for the object. 
+
+    See [Reviewing and Restoring Object Versions](../reviewing-and-restoring-object-versions-4f717cc.md).
+    
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+    
     Details
 
     </td>

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

@@ -31,7 +31,7 @@ SAP HANA Cloud, data lake allows SAP Datasphere to store and manage mass-data ef
 As a local table \(file\) is capturing delta changes via flows, it creates different entities in the repository after it is deployed:
 
 -   An active records entity for accessing the delta capture entity through a virtual table. It excludes the delta capture columns and deleted records, and keeps only the active records.
--   A delta capture entity that stores information on changes found in the delta capture table. It serves as target for flows at design time. In addition, every local table \(File\) has a specific folder in file storage \(inbound buffer\) to which a replication flow writes data files to a specific target object. To process data updates from this inbound buffer to the local table \(File\), and therefore make data visible, a merge task has to run via a task chain \(see [Creating a Task Chain](creating-a-task-chain-d1afbc2.md)\). You can monitor the buffer merge status using the *Local Tables \(File\)* monitor \(See and [Monitoring Local Tables (File)](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/6b2d0073a8684ee6a59d6f47d00ec895.html "Monitor your local tables (file). Check how and when they were last updated and if new data has still to be merged.") :arrow_upper_right:\)
+-   A delta capture entity that stores information on changes found in the delta capture table. It serves as target for flows at design time. In addition, every local table \(File\) has a specific folder in file storage \(inbound buffer\) to which a replication flow writes data files to a specific target object. To process data updates from this inbound buffer to the local table \(File\), and therefore make data visible, a merge task has to run via a task chain \(see [Creating a Task Chain](creating-a-task-chain-d1afbc2.md)\). You can monitor the buffer merge status using the *Local Tables \(File\)* monitor \(See and [Monitoring Local Tables (File)](https://help.sap.com/viewer/be5967d099974c69b77f4549425ca4c0/cloud/en-US/6b2d0073a8684ee6a59d6f47d00ec895.html "Monitor your local tables (file). Check how and when they were last updated and if new data has still to be merged.") :arrow_upper_right:\)
 
 
 

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

@@ -326,7 +326,7 @@ For more information about available connection types, sources, and targets, see
 
 8.  Click <span class="FPA-icons-V3"></span> \(Run\) to start your replication flow.
 
-    For more information about how to monitor your replication flow run, see [Monitoring Flows](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/b661ea0766a24c7d839df950330a89fd.html "In the Flows monitor, you can find all the deployed flows per space.") :arrow_upper_right:.
+    For more information about how to monitor your replication flow run, see [Monitoring Flows](https://help.sap.com/viewer/be5967d099974c69b77f4549425ca4c0/cloud/en-US/b661ea0766a24c7d839df950330a89fd.html "In the Flows monitor, you can find all the deployed flows per space.") :arrow_upper_right:.
 
 9.  The tools in the editor toolbar help you work with your object throughout its lifecycle:
 
@@ -429,6 +429,20 @@ For more information about available connection types, sources, and targets, see
     <tr>
     <td valign="top">
 
+    Versions
+    
+    </td>
+    <td valign="top">
+    
+    Open the *Version History* dialog for the object. 
+
+    See [Reviewing and Restoring Object Versions](../reviewing-and-restoring-object-versions-4f717cc.md).
+    
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+    
     Details
 
     </td>