Update from SAP DITA CMS (squashed):

commit b4488d9a4fd443e85546729ed68e2c80caec01fa Author: REDACTED Date: Mon Jun 17 11:57:45 2024 +0000 Update from SAP DITA CMS 2024-06-17 11:57:45 Project: dita-all/usv1716385622849 Project map: af2fcb3e6dd448f3af3c0ff9c70daaf9.ditamap Output: loiob8faae83b519439fb4ea9d0eb1a5f26e Language: en-US Builddable map: 4e1c1e1d5d1947f5875e93e7597c4f4c.ditamap commit 48fa3b975a53e09937943cfd72f78c2021e342ed Author: REDACTED Date: Mon Jun 17 11:57:28 2024 +0000 Update from SAP DITA CMS 2024-06-17 11:57:28 Project: dita-all/usv1716385622849 Project map: af2fcb3e6dd448f3af3c0ff9c70daaf9.ditamap Output: loioc25299a38b6448f889a43b42c9e5897d Language: en-US Builddable map: 678695d903b546e5947af69e56ed42b8.ditamap commit c2ade884fb13eca3c61cc5d7bed7a76371012251 Author: REDACTED Date: Mon Jun 17 11:57:02 2024 +0000 Update from SAP DITA CMS 2024-06-17 11:57:02 Project: dita-all/usv1716385622849 Project map: af2fcb3e6dd448f3af3c0ff9c70daaf9.ditamap Output: loiod3d776bb52294a17b48298443a286f55 Language: en-US Builddable map: 89ab8c0ed18c432d8fb87551823e7de7.ditamap ################################################## [Remaining squash message was removed before commit...]
SAP-docs · Jun 18, 2024 · bed6c7a · bed6c7a
1 parent 76bb6e9
commit bed6c7a
Show file tree

Hide file tree

Showing 140 changed files with 2,035 additions and 410 deletions.
diff --git a/...ata-Builder/add-a-source-table-ec702fe.md → ...-the-Data-Builder/add-a-source-ec702fe.md b/...ata-Builder/add-a-source-table-ec702fe.md → ...-the-Data-Builder/add-a-source-ec702fe.md
@@ -2,9 +2,9 @@
 
 <link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
 
-# Add a Source Table
+# Add a Source
 
-Add a source table to read data from. You can add multiple source tables and combine them together using join or union operators.
+Add a source to read data from.
 
 
 
@@ -14,9 +14,18 @@ Add a source table to read data from. You can add multiple source tables and com
 
 1.  Navigate to the *Graphical View Editor*.
 
-2.  Drag a table from the *Repository* and drop it onto the diagram.
+2.  Browse or search for the object you want to add on either of the tabs.
 
-3.  Click the source table node to display its properties in the side panel, and review the properties in the *General* section:
+    -   The *Repository* tab lists all the tables and views that are available in the space.
+    -   The *Sources* tab lists all the Open SQL schemas that have been integrated to the space from which you can import tables and views. Each Open SQL schema appears as a root node in this tab \(see [Integrating Data via Database Users/Open SQL Schemas](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/3de55a78a4614deda589633baea28645.html "Create a database user in your space to read and write directly to the SAP HANA Cloud database on which SAP Datasphere runs. Each database user has an Open SQL schema, which is attached to a space schema and provides a secure method for exchanging data with the space.") :arrow_upper_right:\).
+
+3.  Drag a table from the relevant tab and drop it onto the diagram.
+
+4.  If the source is a view containing one or more input parameters, the *Map Input Parameters* dialog is displayed, and you can enter a value to resolve the input parameter.
+
+    You can click*Cancel* in the dialog and do not specify a value to resolve the input parameter, an error is displayed on the source, and you must subsequently specify a value in the source side panel *Input Parameters* section.
+
+5.  Click the source node to display its properties in the side panel, and review the properties in the *General* section:
 
     ****
 
@@ -42,7 +51,7 @@ Add a source table to read data from. You can add multiple source tables and com
     </td>
     <td valign="top">
 
-    Information to identify the source table.
+    Information to identify the source object.
 
     </td>
     </tr>
@@ -54,7 +63,7 @@ Add a source table to read data from. You can add multiple source tables and com
     </td>
     <td valign="top">
 
-    You can specify an SQL alias for the table if required.
+    You can specify an SQL alias for the source object if required.
 
     </td>
     </tr>
@@ -66,7 +75,7 @@ Add a source table to read data from. You can add multiple source tables and com
     </td>
     <td valign="top">
 
-    Indicates whether the source table uses SELECT DISTINCT statements to return only distinct values.
+    Indicates whether the source object uses SELECT DISTINCT statements to return only distinct values.
 
     </td>
     </tr>
@@ -92,6 +101,18 @@ Add a source table to read data from. You can add multiple source tables and com
 
     The deployment and error status of the object. For more information, see [Saving and Deploying Objects](../saving-and-deploying-objects-7c0b560.md).
 
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+
+    Input Parameters
+
+    </td>
+    <td valign="top">
+
+    If the source contains input parameters, you can view them here.
+
     </td>
     </tr>
     </table>
@@ -102,7 +123,7 @@ Add a source table to read data from. You can add multiple source tables and com
 
     To load delta changes from a source table \(including deleted records\), the delta capture setting must be enabled for the table. It is only possible to load delta changes from one source table. If you want to load delta changes from a source table, you need to ensure that the value of the option *Delta Capture* is *On* for both the source table and for the target table. In the *Transformation Flow Properties* panel, ensure that the load type *Initial and Delta* is selected.
 
-4.  In the *Columns* section, you can view the columns of the source table. To check the data type of a column, hover over it and click <span class="FPA-icons-V3"></span>.
+6.  In the *Columns* section, you can view the columns of the source table. To check the data type of a column, hover over it and click <span class="FPA-icons-V3"></span>.
 
     If the delta capture setting is enabled for a table, two additional columns are present in the table to track changes. For more information, see [Capturing Delta Changes in Your Local Table](capturing-delta-changes-in-your-local-table-154bdff.md).
 

diff --git a/...-and-Preparing-Data-in-the-Data-Builder/add-or-create-a-target-table-0fa7805.md b/...-and-Preparing-Data-in-the-Data-Builder/add-or-create-a-target-table-0fa7805.md
@@ -19,7 +19,7 @@ Add a target table to write data to. You can only have one target table in a dat
     -   Drag an existing table from the *Source Browser*, drop it onto the canvas, and click the floating *Target* button to use it as the target table. You can choose:
         -   On the *Repository* tab - A local table.
         -   On the *Sources* tab:
-            -   A table in an Open SQL schema - if the space is granted write access to the table or schema \(see [Allow the Space to Write to the Open SQL Schema](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/7eaa370fe4624dea9f182ee9c9ab645f.html "To grant the space write privileges in the Open SQL schema, use the GRANT_PRIVILEGE_TO_SPACE stored procedure. Once this is done, data flows running in the space can select tables in the Open SQL schema as targets and write data to them.") :arrow_upper_right:\).
+            -   A table in an Open SQL schema - if the space is granted write access to the table or schema \(see [Allow the Space to Access the Open SQL Schema](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/7eaa370fe4624dea9f182ee9c9ab645f.html "To grant the space write privileges in the Open SQL schema and the ability to write data to target tables in the schema, use the GRANT_PRIVILEGE_TO_SPACE stored procedure. Once this is done, data flows running in the space can select tables in the Open SQL schema as targets and write data to them, and task chains can run procedures in the schema.") :arrow_upper_right:\).
             -   A table in a database user group schema - if the space is granted write access to the table or schema \(see [Allow a Space to Write to the Database User Group Schema](https://help.sap.com/viewer/935116dd7c324355803d4b85809cec97/DEV_CURRENT/en-US/5b27e03849fe4c7182bcb4274f010e90.html "To grant a space write privileges in the database user group schema, use the GRANT_PRIVILEGE_TO_SPACE stored procedure. Once this is done, data flows running in the space can select tables in the schema as targets and write data to them.") :arrow_upper_right:\).
             -   A table in an SAP HDI container - if the space is granted write access to the table or schema \(see [Allow Your Space to Write to Your HDI Container](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/aa3627f987d04b5f95fec1c45083dde9.html "To allow data flows in your SAP Datasphere space to use tables in your HDI container as targets, you must set the appropriate roles and add the container to your space.") :arrow_upper_right:\).
 

diff --git a/...Data-in-the-Data-Builder/capturing-delta-changes-in-your-local-table-154bdff.md b/...Data-in-the-Data-Builder/capturing-delta-changes-in-your-local-table-154bdff.md
@@ -134,8 +134,8 @@ The 2 objects are consumed differently by SAP Datasphere apps:
 -   Most SAP Datasphere apps consume a local table with delta capture through the *Active Records* table only. In these cases, local tables behave the same way independent of whether *Delta Capture* is set to "*On*" or "*Off*". For examples in Graphical Views, SQL Views, E/R Modeler or Business Builder.
 -   The following SAP Datasphere apps also interact with the Delta Capture Table that contains the delta columns:
     -   *Transformation Flow*:
-        -   As Source, you can choose between source with "Delta Capture" or "All Active Records". See [Add a Source Table](add-a-source-table-ec702fe.md)
-        -   As target, it depends of the combination of the load type used and the table type \(local table with or without delta capture\). See [Processing Changes to Source and Target Tables](processing-changes-to-source-and-target-tables-705292c.md) and [Add or Create a Target Table](add-or-create-a-target-table-0950746.md) 
+        -   As Source, you can choose between source with "Delta Capture" or "All Active Records". See [Add a Source](add-a-source-ec702fe.md)
+        -   As target, it depends of the combination of the load type used and the table type \(local table with or without delta capture\). See [Processing Changes to Sources and Target Tables](processing-changes-to-sources-and-target-tables-705292c.md) and [Add or Create a Target Table](add-or-create-a-target-table-0950746.md) 
 
     -   *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*:

diff --git a/...d-Preparing-Data-in-the-Data-Builder/configure-your-replication-flow-3f5ba0c.md b/...d-Preparing-Data-in-the-Data-Builder/configure-your-replication-flow-3f5ba0c.md
@@ -21,7 +21,7 @@ Define settings and properties for your replication flow and individual replicat
     -   *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 *Running* until it is stopped or paused or an issue occurs.
+        > -   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.
         > 
         > -   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).
         > 
@@ -42,14 +42,16 @@ Define settings and properties for your replication flow and individual replicat
 
     If the target structure does not yet exist or is empty, you can ignore the *Truncate* setting.
 
-4.  Click <span class="FPA-icons-V3"></span> \(Browse target settings\) to review the target settings **at replication flow level** and change them as appropriate.
+4.  Click <span class="FPA-icons-V3"></span> \(Browse target settings\) to review the target settings and change them as appropriate.
 
-    -   Replication Thread Limit: To modify the throughput, you can increase or decrease the default value for the number of replication threads as appropriate for your use case.
+    -   Target Thread Limit: To modify the throughput, you can increase or decrease the number of replication threads to be used for your replication flow as appropriate for your use case. In particular, the value you enter here determines how many partitions can be processed in parallel during *initial load*.
 
-        You can change the thread limit in the source accordingly by clicking <span class="FPA-icons-V3"></span> \(Browse source settings\) and entering the appropriate value. The recommendation is to use the same value for the source and the target. When replicating data from SAP HANA, specify an even number for the maximum number of connections, as this helps to improve performance.
+        You can change the thread limit in the source accordingly by clicking <span class="FPA-icons-V3"></span> \(Browse source settings\) and entering the appropriate value. We recommend using the same value for the source and the target. When replicating data from SAP HANA, specify an even number for the maximum number of connections, as this helps to improve performance.
 
         See also [Replication Flow Blog Series Part 4 - Sizing](https://blogs.sap.com/2023/12/15/replication-flow-blog-series-part-4-sizing/).
 
+    -   For **delta loading**, you can specify the number of threads to be used for parallel processing at replication object level. The default value is 1. The maximum possible value is determined by what you define for target thread limit and source thread limit, respectively, with an absolute maximum value of 10 - whichever is lowest. This option is only available for SLT tables and CDS views that have load type *Initial and Delta*.
+
     -   Overwrite Target Settings at Object Level: \[only relevant if the target is a cloud storage provider\] By default, any settings that you have made at replication object level are kept intact if you make a different setting at replication flow level. To change this, enable this option.
 
     -   Additional settings that are only relevant for a specific target type and can be made for the replication flow itself as well as for individual replication objects. For more information, see

diff --git a/...nd-Preparing-Data-in-the-Data-Builder/configuring-email-notification-7ff6a4e.md b/...nd-Preparing-Data-in-the-Data-Builder/configuring-email-notification-7ff6a4e.md
@@ -0,0 +1,54 @@
+<!-- loio7ff6a4e584a345a88d002c18c1fc321e -->
+
+<link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
+
+# Configuring Email Notification
+
+After creating and deploying a task chain, set up email notification of users for completion of task chain runs.
+
+
+
+## Context
+
+> ### Note:  
+> The DW Integrator role is required to set up email notification for completion of task chain runs. The *Email Notifications* section of the task chain *Properties* panel will not appear if you do not have this privilege assigned. For more information, see [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:. In addition to the DW Integrator role, when setting up email notifications, either the Team.Read or User.Read privilege is also required to display and add notification recipients from a list of current tenant members.
+
+
+
+## Procedure
+
+1.  In the *Email Notifications* section of the *Properties* panel, select when you want notifications to be sent for the current task chain. You can choose from the following options:
+
+    -   Send email notification only when the run has completed with an error.
+
+    -   Send email notification only when the run has completed successfully.
+
+    -   Send email notification when the run has completed.
+
+
+    The *Email Notifications* section expands to show details of the email notification message to be sent to users on completion of task chain runs.
+
+    ![](images/Email_Notification_Setup_d5f7c97.png)
+
+    The notification setup includes a default template you can customize for both the email message subject and body text. You can choose to send notifications to other tenant users or specify email addresses of other users to receive notifications \(up to 20 recipients total\). Email addresses must be in the same domain as the tenant owner.
+
+    > ### Note:  
+    > Task chains must also first be deployed before you can select or specify users to receive notifications.
+
+2.  Click the <span class="SAP-icons-V5"></span> link on the right side of the *Recipient Email Address* field to open a popup dialog in which you can add recipients of task chain notification email messages.
+
+    ![](images/Recipients_List_527a05c.png)
+
+    From this dialog, you can select member users of the same tenant or click the *Others* tab to specify email addresses of other users you want to receive notifications \(up to 20 total recipients\). Email addresses must match the domain of the tenant owner, for example, [email protected]. After saving your selections, the display returns to the *Properties* panel, showing the selected users in the *Recipient Email Address* field.
+
+    > ### Note:  
+    > When setting up email notification, either the Team.Read or User.Read privilege is required to be able to display and add notification recipients from the list of current tenant members. If you do not have this privilege assigned, you can still add recipients manually from the *Others* tab.
+
+3.  Review the default email subject and message body text and make any updates to either the text or placeholder variables used in the notification email message sent for the current task chain.
+
+    Placeholder variables within the subject and message fields are enclosed by $$ characters, for example, $$status$$. You can click the <span class="SAP-icons-V5"></span> icon to display a list of available placeholder variable names you may include in either the email subject or message body text fields.
+
+    > ### Note:  
+    > Changes you make to the email notification template are saved when you redeploy the updated task chain that has email notification subject and body text template changes. When the task chain is run and notification emails are sent out, placeholder variables in the notification template will be replaced with actual values available at runtime.
+
+
diff --git a/...Preparing-Data-in-the-Data-Builder/create-a-graphical-view-transform-c65e37c.md b/...Preparing-Data-in-the-Data-Builder/create-a-graphical-view-transform-c65e37c.md
@@ -4,7 +4,7 @@
 
 # Create a Graphical View Transform
 
-Create a graphical view transform that uses SQL syntax to combine and transform data as part of your transformation flow. You can drag and drop source tables from the *Repository*, join them as appropriate, add other operators to remove or create columns and filter or aggregate data.
+Create a graphical view transform that uses SQL syntax to combine and transform data as part of your transformation flow. You can drag and drop sources from the *Repository* tab or from the *Sources* tab, join them as appropriate, add other operators to remove or create columns and filter or aggregate data.
 
 
 
@@ -14,9 +14,9 @@ Create a graphical view transform that uses SQL syntax to combine and transform
 
 2.  Create a new *Graphical View Transform* for your transformation flow by clicking the *Graphical View Transform* button.
 
-3.  The system displays the *Graphical View Editor*. Add a source table. For more information, see [Add a Source Table](add-a-source-table-ec702fe.md).
+3.  The system displays the *Graphical View Editor*. Add a source. For more information, see [Add a Source](add-a-source-ec702fe.md).
 
-4.  Optional: Drag additional source tables from the repository and drop them onto a source table to create a join or union. For more information, see [Create a Join](create-a-join-bcb5f48.md) and [Create a Union](create-a-union-9cd6fbf.md).
+4.  Optional: Drag additional sources from the *Repository* tab or from the *Sources* tab and drop them onto a source to create a join or union. For more information, see [Create a Join](create-a-join-bcb5f48.md) and [Create a Union](create-a-union-9cd6fbf.md).
 
 5.  Click a node in the diagram to display tools for creating operators and performing other actions: