Update from SAP DITA CMS (squashed):

commit 44bd275105ce40c298bb35eb7a906cba4074f580
Author: REDACTED
Date:   Fri May 17 16:58:08 2024 +0000

    Update from SAP DITA CMS 2024-05-17 16:58:08
    Project: dita-all/hmd1713878557962
    Project map: af2fcb3e6dd448f3af3c0ff9c70daaf9.ditamap
    Output: loiod3d776bb52294a17b48298443a286f55
    Language: en-US
    Builddable map: 89ab8c0ed18c432d8fb87551823e7de7.ditamap

commit f9df7fe16d9464c0c46edc90314aa72fe5e0c66c
Author: REDACTED
Date:   Fri May 17 16:54:43 2024 +0000

    Update from SAP DITA CMS 2024-05-17 16:54:43
    Project: dita-all/hmd1713878557962
    Project map: af2fcb3e6dd448f3af3c0ff9c70daaf9.ditamap
    Output: loioc25299a38b6448f889a43b42c9e5897d
    Language: en-US
    Builddable map: 678695d903b546e5947af69e56ed42b8.ditamap

commit 5616acf3538ac8af3f4b6ef647ae62ab3f48455d
Author: REDACTED
Date:   Fri May 17 16:54:40 2024 +0000

    Update from SAP DITA CMS 2024-05-17 16:54:40
    Project: dita-all/hmd1713878557962
    Project map: af2fcb3e6dd448f3af3c0ff9c70daaf9.ditamap
    Output: loiob8faae83b519439fb4ea9d0eb1a5f26e
    Language: en-US
    Builddable map: 4e1c1e1d5d1947f5875e93e7597c4f4c.ditamap

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

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

@@ -176,9 +176,10 @@ All the objects you import or create in the *Data Builder* are listed on the *Da
 
     Import objects from files and connections:
 
-    -   *Import CSV File* - Import data from a CSV file to create a local table \(see [Creating a Local Table from a CSV File](creating-a-local-table-from-a-csv-file-8bba251.md)
-    -   *Import Objects from CSN/JSON File* - Import table and view definitions from a CSN file to create tables and views or import data flow definitions from a JSON file to create data flows. \(see [Importing Objects from a CSN/JSON File](../Creating-Finding-Sharing-Objects/importing-objects-from-a-csn-json-file-23599e6.md)\).
+    -   *Import CSV File* - Import data from a CSV file to create a local table \(see [Creating a Local Table from a CSV File](creating-a-local-table-from-a-csv-file-8bba251.md).
+    -   *Import Objects from CSN/JSON File* - Import table, view, and other object definitions from a CSN/JSON file \(see [Importing Objects from a CSN/JSON File](../Creating-Finding-Sharing-Objects/importing-objects-from-a-csn-json-file-23599e6.md)\).
     -   *Import Remote Tables* - Import remote tables from a connection \(see [Import Remote Tables](import-remote-tables-fd04efb.md)\).
+    -   *Import Permissions* - Import analysis authorizations from SAP BW and and SAP BW∕4HANA systems to create data access controls \(see [Import SAP BW and SAP BW∕4HANA Analysis Authorizations](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/f56e4271dc4943aa9f21223ce5c93873.html "You can import analysis authorizations defined in SAP BW and SAP BW∕4HANA systems into SAP Datasphere to provide row-level protection for data imported from these systems.") :arrow_upper_right:\).
 
 
 
@@ -204,18 +205,18 @@ All the objects you import or create in the *Data Builder* are listed on the *Da
     </td>
     <td valign="top">
 
-    Select one or more objects and deploy them at once.
+    Select one or more objects and deploy them together.
 
     Choose from the following entity types:
 
-    -   Local Table \(see [Creating a Local Table](creating-a-local-table-2509fe4.md)\)
-    -   Graphical View \(see [Creating a Graphical View](../creating-a-graphical-view-27efb47.md)\)
-    -   SQL View \(see [Creating an SQL View](../creating-an-sql-view-81920e4.md)\)
-    -   Data Access Control \(see [Create a "Single Values" Data Access Control](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/5246328ec59045cb9c2aa693daee2557.html "Users with the DW Space Administrator role (or equivalent privileges) can create data access controls in which criteria are defined as single values. Each user can only see the records that match any of the single values she is authorized for in the permissions entity.") :arrow_upper_right:\)
-    -   Analytic Model \(see [Creating an Analytic Model](../Modeling-Data-in-the-Data-Builder/creating-an-analytic-model-e5fbe9e.md)\)
-    -   Task Chain \(see [Creating a Task Chain](creating-a-task-chain-d1afbc2.md)\)
+    -   Local tables \(see [Creating a Local Table](creating-a-local-table-2509fe4.md)\)
+    -   Graphical views \(see [Creating a Graphical View](../creating-a-graphical-view-27efb47.md)\)
+    -   SQL views \(see [Creating an SQL View](../creating-an-sql-view-81920e4.md)\)
+    -   Data access controls \(see [Securing Data with Data Access Controls](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/a032e51c730147c7a1fcac125b4cfe14.html "Data access controls allow you to apply row-level security to your objects. When a data access control is applied to a data layer view or a business layer object, any user viewing its data will see only the rows for which they are authorized, based on the specified criteria.") :arrow_upper_right:\)
+    -   Analytic models \(see [Creating an Analytic Model](../Modeling-Data-in-the-Data-Builder/creating-an-analytic-model-e5fbe9e.md)\)
+    -   Task chains \(see [Creating a Task Chain](creating-a-task-chain-d1afbc2.md)\)
 
-    Other types of objects cannot be deployed.
+    Other types of objects can only be deployed via their editors.
 
     If one or more objects that you have selected cannot be deployed, the *Deploy* dialog opens, allowing you to review your selection. Click *Deploy* to deploy those objects listed on the *Deployable* tab, or *Cancel* to go back and alter your selection.
 
@@ -241,7 +242,7 @@ All the objects you import or create in the *Data Builder* are listed on the *Da
     </td>
     <td valign="top">
 
-    View the objects that depend on an analyzed object \(its impacts\) and the objects on which the analyzed object depends \(its lineage\)\(see [Impact and Lineage Analysis](../Creating-Finding-Sharing-Objects/impact-and-lineage-analysis-9da4892.md)\).
+    View the objects that depend on the selected object, and those objects on which it depends \(see [Impact and Lineage Analysis](../impact-and-lineage-analysis-9da4892.md)\).
 
     </td>
     </tr>
@@ -253,12 +254,7 @@ All the objects you import or create in the *Data Builder* are listed on the *Da
     </td>
     <td valign="top">
 
-    Delete the selected objects.
-
-    > ### Note:  
-    > If the object is used by one or more other objects then a dialog listing these dependencies opens, and the deletion is canceled.
-
-
+    Delete the selected objects \(see [Deleting Objects](../deleting-objects-1e69cbb.md)\).
 
     </td>
     </tr>

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-7b50e8e.md

@@ -115,7 +115,7 @@ Add a source to read data from. You can add multiple sources and combine them to
 
     \[read-only\] Displays the deployment and error status of the object. 
 
-    For more information, see [Saving and Deploying Objects](../Creating-Finding-Sharing-Objects/saving-and-deploying-objects-7c0b560.md).
+    For more information, see [Saving and Deploying Objects](../saving-and-deploying-objects-7c0b560.md).
 
     </td>
     </tr>

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-table-ec702fe.md

@@ -90,7 +90,7 @@ Add a source table to read data from. You can add multiple source tables and com
     </td>
     <td valign="top">
 
-    The deployment and error status of the object. For more information, see [Saving and Deploying Objects](../Creating-Finding-Sharing-Objects/saving-and-deploying-objects-7c0b560.md).
+    The deployment and error status of the object. For more information, see [Saving and Deploying Objects](../saving-and-deploying-objects-7c0b560.md).
 
     </td>
     </tr>

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-or-create-a-target-table-0950746.md

@@ -20,7 +20,7 @@ A transformation flow writes data to a target table. You can create a new target
 
 
     > ### Note:  
-    > If the load type of the transformation flow is *Initial and Delta* and you change the target table, only delta data will be transferred to the new target table. If you want to transfer all data to the target table, you can reset the watermark in the *Data Integration Monitor*. For more information, see [Watermarks](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/890897f00a4944c7a6f90d3816a8d4c6.html "") :arrow_upper_right:.
+    > If the load type of the transformation flow is *Initial and Delta* and you change the target table, only delta data will be transferred to the new target table. If you want to transfer all data to the target table, you can reset the watermark in the *Data Integration Monitor*. For more information, see [Watermarks](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/890897f00a4944c7a6f90d3816a8d4c6.html "When you run a transformation flow that loads delta changes to a target table, the system uses a watermark (a timestamp) to track the data that has been transferred.") :arrow_upper_right:.
 
 2.  Click the target node to display its properties in the side panel, and review the properties in the *General* section:
 
@@ -58,7 +58,7 @@ A transformation flow writes data to a target table. You can create a new target
     </td>
     <td valign="top">
 
-    The deployment and error status of the object. For more information, see [Saving and Deploying Objects](../Creating-Finding-Sharing-Objects/saving-and-deploying-objects-7c0b560.md).
+    The deployment and error status of the object. For more information, see [Saving and Deploying Objects](../saving-and-deploying-objects-7c0b560.md).
 
     </td>
     </tr>

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-or-create-a-target-table-0fa7805.md

@@ -158,7 +158,7 @@ Add a target table to write data to. You can only have one target table in a dat
 
     \[read-only\] Displays the deployment and error status of the object. 
 
-    For more information, see [Saving and Deploying Objects](../Creating-Finding-Sharing-Objects/saving-and-deploying-objects-7c0b560.md).
+    For more information, see [Saving and Deploying Objects](../saving-and-deploying-objects-7c0b560.md).
 
     </td>
     </tr>

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/additional-information-about-remote-tables-4c088d1.md

@@ -2,7 +2,9 @@
 
 # Additional Information About Remote Tables
 
-You can add remote tables located in SAP BW bridge spaces to a transformation flow. Note that remote tables located in SAP BW bridge spaces must be shared with the SAP Datasphere space you are using to create your transformation flow.
+You can add remote tables located in SAP BW bridge spaces to a transformation flow.
+
+Remote tables located in SAP BW bridge spaces must be shared with the SAP Datasphere space you are using to create your transformation flow.
 
 > ### Note:  
 > If you add a remote table located in SAP BW bridge spaces, it is not possible to preview the data being output by the view.
@@ -11,7 +13,7 @@ If you add a remote table located in an SAP BW bridge space that is configured t
 
 -   REQTSN\_LOW
 
-    When loading delta changes, the value of this input parameter is the watermark. When loading all active records, the value of this input parameter is the minimum timestamp. For more information, see [Watermarks](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/890897f00a4944c7a6f90d3816a8d4c6.html "") :arrow_upper_right:.
+    When loading delta changes, the value of this input parameter is the watermark. When loading all active records, the value of this input parameter is the minimum timestamp. For more information, see [Watermarks](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/890897f00a4944c7a6f90d3816a8d4c6.html "When you run a transformation flow that loads delta changes to a target table, the system uses a watermark (a timestamp) to track the data that has been transferred.") :arrow_upper_right:.
 
 -   REQTSN\_HIGH
 

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/additional-information-about-remote-tables-ab4db76.md

@@ -2,7 +2,9 @@
 
 # Additional Information About Remote Tables
 
-You can add remote tables located in SAP BW bridge spaces to a transformation flow. Note that remote tables located in SAP BW bridge spaces must be shared with the SAP Datasphere space you are using to create your transformation flow.
+You can add remote tables located in SAP BW bridge spaces to a transformation flow.
+
+Remote tables located in SAP BW bridge spaces must be shared with the SAP Datasphere space you are using to create your transformation flow.
 
 > ### Note:  
 > If you add a remote table located in SAP BW bridge spaces, it is not possible to preview the data being output by the view.
@@ -11,7 +13,7 @@ If you add a remote table located in an SAP BW bridge space that is configured t
 
 -   REQTSN\_LOW
 
-    When loading delta changes, the value of this input parameter is the watermark. When loading all active records, the value of this input parameter is the minimum timestamp. For more information, see [Watermarks](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/890897f00a4944c7a6f90d3816a8d4c6.html "") :arrow_upper_right:.
+    When loading delta changes, the value of this input parameter is the watermark. When loading all active records, the value of this input parameter is the minimum timestamp. For more information, see [Watermarks](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/890897f00a4944c7a6f90d3816a8d4c6.html "When you run a transformation flow that loads delta changes to a target table, the system uses a watermark (a timestamp) to track the data that has been transferred.") :arrow_upper_right:.
 
 -   REQTSN\_HIGH
 

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/aggregate-data-f368ba0.md

@@ -69,6 +69,6 @@ Add an *Aggregation* node to perform `SUM`, `COUNT`, `MIN`, and `MAX` calculatio
 
     When working on a large expression, click <span class="FPA-icons-V3"></span> \(Enter Full Screen\) to expand the expression editor.
 
-7.  Click <span class="FPA-icons-V3"></span> \(Preview Data\) to open the *Data Preview* panel and review the data output by this node. For more information, see [Viewing or Previewing Data in Data Builder Objects](../viewing-or-previewing-data-in-data-builder-objects-b338e4a.md).
+7.  Click <span class="FPA-icons-V3"></span> \(Preview Data\) to open the *Data Preview* panel and review the data output by this node. For more information, see [Viewing Object Data](../viewing-object-data-b338e4a.md).
 
 

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/capturing-delta-changes-in-your-local-table-154bdff.md

@@ -79,7 +79,7 @@ When *Delta Capture* is switched on:
     </td>
     <td valign="top">
 
-    This column will track the type of last change made to a record.When a record is inserted or updated corresponding change types are used \(for example "I" or "U"\). When an existing record is deleted other specific change types are used \(for example "D"\). Note that deleting a record will not physically delete it, so that the changes can be propagated to the different objects that consume it in delta mode. It is however filtered out when accessing the Local Table \(using the Active Records Table\). Also, note that the change types provided by the different SAP Datasphere apps vary and may depend on the actual source that is connected. The handling of the different change types is implemented internally by SAP Datasphere apps that consume the Delta Capture Table with no need for consideration in modeling. For more information on records deletion, see [Load or Delete Local Table Data](load-or-delete-local-table-data-870401f.md)
+    This column will track the type of last change made to a record.When a record is inserted or updated corresponding change types are used: "*I*" for insert \(a new record is added\), "*U*" for update \(an existing record gets an updated value\), or "*A*" for upsert \(insert records if they do not exist yet in the target table, or update them by primary key if they do exist\). When an existing record is deleted other specific change types are used \(for example "*D*"\). Note that deleting a record will not physically delete it, so that the changes can be propagated to the different objects that consume it in delta mode. It is however filtered out when accessing the Local Table \(using the Active Records Table\). Also, note that the change types provided by the different SAP Datasphere apps vary and may depend on the actual source that is connected. The handling of the different change types is implemented internally by SAP Datasphere apps that consume the Delta Capture Table with no need for consideration in modeling. For more information on records deletion, see [Load or Delete Local Table Data](load-or-delete-local-table-data-870401f.md)
 
     </td>
     </tr>
@@ -139,12 +139,15 @@ The 2 objects are consumed differently by SAP Datasphere apps:
 
     -   *Replication Flow*: The Delta Capture Table can be used as source \(with load type *Initial Only*\) or as target, see [Creating a Replication Flow](creating-a-replication-flow-25e2bd7.md) and [Add a Source](add-a-source-7496380.md).
     -   *Table Editor*:
-        -   Data Preview: Once deployment is completed, it show only the delta capture tables. See [Viewing or Previewing Data in Data Builder Objects](../viewing-or-previewing-data-in-data-builder-objects-b338e4a.md)
+        -   Data Preview: Once deployment is completed, it show only the delta capture tables. See [Viewing Object Data](../viewing-object-data-b338e4a.md)
         -   Data Maintenance: You can perform table maintenance on the delta capture table \(only\) once deployment is completed. See [Maintain Local Table Data](maintain-local-table-data-4bd5e64.md)
         -   File upload: You can update the delta capture table by uploading a new csv file, after deployment is completed. See [Load or Delete Local Table Data](load-or-delete-local-table-data-870401f.md)
 
 
 
+> ### Note:  
+> If the table is used as source or target in an object, for example in a flow, you can see it in the table editor under dependent objects. For more information, see [Review the Objects That Depend on Your Table or View](../review-the-objects-that-depend-on-your-table-or-view-ecac5fd.md).
+
 > ### Restriction:  
 > The Delta Capture Table is an internal table whose structure can incompatibly change at any time. It is not permitted for external data access and is only consumed by the above SAP Datasphere internal apps. Using the internal delta capture columns \(*Change Date* or *Change Type*\) or their content directly or indirectly for external delta replication outside the Premium Outbound Integration is also not permitted. For more information, see [Premium Outbound Integration](https://blogs.sap.com/2023/11/16/replication-flow-blog-series-part-2-premium-outbound-integration/).
 

docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/columns-8f0f40d.md

@@ -85,7 +85,7 @@ Data Type
 
 Select the type of data that the column will contain. 
 
-You can change the data type of a column. For more information, see [Modifying Objects That Have Dependent Objects](../Creating-Finding-Sharing-Objects/modifying-objects-that-have-dependent-objects-f315863.md) 
+You can change the data type of a column. For more information, see [Modifying Objects That Have Dependent Objects](../modifying-objects-that-have-dependent-objects-f315863.md) 
 
 For a list of available data types and their supported data type conversions, see [Column Data Types](column-data-types-7b1dc6e.md).
 
@@ -133,7 +133,7 @@ Change Type
 </td>
 <td valign="top">
 
-This column will track the type of last change made to a record. When a record is inserted or updated corresponding change types are used \(for example "I" or "U"\). When an existing record is deleted other specific change types are used \(for example "D"\). Note that deleting a record will not physically delete it, so that the changes can be propagated to the different objects that consume it in delta mode. It is however filtered out when accessing the Local Table \(using the Active Records Table\). Also, note that the change types provided by the different SAP Datasphere apps vary and may depend on the actual source that is connected. The handling of the different change types is implemented internally by SAP Datasphere apps that consume the Delta Capture Table with no need for consideration in modeling. For more information on records deletion, see [Load or Delete Local Table Data](load-or-delete-local-table-data-870401f.md) .
+This column will track the type of last change made to a record. When a record is inserted or updated corresponding change types are used: "*I*" for insert \(a new record is added\), "*U*" for update \(an existing record gets an updated value\), or "*A*" for upsert \(insert records if they do not exist yet in the target table, or update them by primary key if they do exist\). When an existing record is deleted other specific change types are used \(for example "*D*"\). Note that deleting a record will not physically delete it, so that the changes can be propagated to the different objects that consume it in delta mode. It is however filtered out when accessing the Local Table \(using the Active Records Table\). Also, note that the change types provided by the different SAP Datasphere apps vary and may depend on the actual source that is connected. The handling of the different change types is implemented internally by SAP Datasphere apps that consume the Delta Capture Table with no need for consideration in modeling. For more information on records deletion, see [Load or Delete Local Table Data](load-or-delete-local-table-data-870401f.md) .
 
 </td>
 </tr>