Update from SAP DITA CMS (squashed):

commit 25b2947f5cfc655b06d1864642388a3a19d0676f Author: REDACTED Date: Thu Sep 21 03:37:34 2023 +0200 Update from SAP DITA CMS ( 2023-09-21_03:37:34 ) Project: loioaf2fcb3e6dd448f3af3c0ff9c70daaf9 (def1691508833862.project) * Project map: loioaf2fcb3e6dd448f3af3c0ff9c70daaf9 (vgq1692648904051.ditamap) * Output: loioc25299a38b6448f889a43b42c9e5897d * Buildable map: loio678695d903b546e5947af69e56ed42b8 (wde1692648904154.ditamap) * Language: en-US commit 605ea464afebbe3a7d4ff2194115220dc788d1c2 Author: REDACTED Date: Fri Sep 15 11:55:45 2023 +0200 Update from SAP DITA CMS ( 2023-09-15_11:55:45 ) Project: loioaf2fcb3e6dd448f3af3c0ff9c70daaf9 (def1691508833862.project) * Project map: loioaf2fcb3e6dd448f3af3c0ff9c70daaf9 (vgq1692648904051.ditamap) * Output: loioc25299a38b6448f889a43b42c9e5897d * Buildable map: loio678695d903b546e5947af69e56ed42b8 (wde1692648904154.ditamap) * Language: en-US ################################################## [Remaining squash message was removed before commit...]
SAP-docs · Sep 22, 2023 · 1c165a8 · 1c165a8
1 parent b4bbd25
commit 1c165a8
Show file tree

Hide file tree

Showing 69 changed files with 2,279 additions and 155 deletions.
diff --git a/...reparing-Data-in-the-Data-Builder/acquiring-data-in-the-data-builder-1f15a29.md b/...reparing-Data-in-the-Data-Builder/acquiring-data-in-the-data-builder-1f15a29.md
@@ -2,13 +2,14 @@
 
 # Acquiring Data in the Data Builder
 
-Users with the *DW Modeler* role can import data directly into the *Data Builder* from connections and other sources, use replication flows to replicate multiple objects, and data flows to extract, transform and load data.
+Users with the *DW Modeler* role can import data directly into the *Data Builder* from connections and other sources, and use flows to replicate, extract, transform and load data.
 
 This topic contains the following sections:
 
 -   [Federate and Replicate Data in Remote Tables](acquiring-data-in-the-data-builder-1f15a29.md#loio1f15a29a25354ec28392ab10ca4e9350__section_federate_replicate)
 -   [Extract, Transform, and Load Data with Data Flows](acquiring-data-in-the-data-builder-1f15a29.md#loio1f15a29a25354ec28392ab10ca4e9350__section_etl)
 -   [Load Data from Multiple Objects with Replication Flows](acquiring-data-in-the-data-builder-1f15a29.md#loio1f15a29a25354ec28392ab10ca4e9350__section_replication_flows)
+-   [Load and Transform Data \(Including Delta Change Support\) with Transformation Flows](acquiring-data-in-the-data-builder-1f15a29.md#loio1f15a29a25354ec28392ab10ca4e9350__section_transformation_flows)
 -   [Import Entities from SAP S/4HANA](acquiring-data-in-the-data-builder-1f15a29.md#loio1f15a29a25354ec28392ab10ca4e9350__section_s4)
 -   [Import Entities from SAP BW Bridge](acquiring-data-in-the-data-builder-1f15a29.md#loio1f15a29a25354ec28392ab10ca4e9350__section_bw_bridge)
 -   [Import Data from CSV Files](acquiring-data-in-the-data-builder-1f15a29.md#loio1f15a29a25354ec28392ab10ca4e9350__section_import_csv)
@@ -70,6 +71,14 @@ Certain connections support loading data from multiple source objects to SAP Dat
 
 
 
+<a name="loio1f15a29a25354ec28392ab10ca4e9350__section_transformation_flows"/>
+
+## Load and Transform Data \(Including Delta Change Support\) with Transformation Flows
+
+Create a transformation flow to load data from one or more source repository tables, apply transformations, and output the result to a target table. You can load a full set of data or only delta changes from each source table \(see [Creating a Transformation Flow](creating-a-transformation-flow-f7161e6.md)\).
+
+
+
 <a name="loio1f15a29a25354ec28392ab10ca4e9350__section_s4"/>
 
 ## Import Entities from SAP S/4HANA

diff --git a/...g-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-7b50e8e.md b/...g-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-7b50e8e.md
@@ -29,6 +29,7 @@ Add a source to read data from. You can add multiple sources and combine them to
     > ### Note:  
     > -   You cannot use views with input parameters as sources in a data flow.
     > -   When browsing a remote file storage such as Amazon Simple Storage Service, Google Cloud Storage, or Microsoft Azure Blob Storage, you can only select files of type JSON/JSONL, CSV, XLS/XLSX, ORC, or PARQUET.
+    > -   Local tables with delta capture can be added as source tables. However only the active records will be used. See [Capturing Delta Changes in Your Local Table](capturing-delta-changes-in-your-local-table-154bdff.md)
 
 4.  Click the source node to display its properties in the side panel, and complete the properties in the *General* section:
 

diff --git a/.../Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-table-ec702fe.md b/.../Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-table-ec702fe.md
@@ -0,0 +1,133 @@
+<!-- loioec702fe3b1134f278c5c538b447b7435 -->
+
+<link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
+
+# Add a Source Table
+
+Add a source table to read data from. You can add multiple source tables and combine them together using join or union operators.
+
+
+
+<a name="loioec702fe3b1134f278c5c538b447b7435__steps_xpb_dqj_lyb"/>
+
+## Procedure
+
+1.  Navigate to the *View Transform Editor*.
+
+2.  Drag a table from the *Repository* and drop it onto the diagram.
+
+3.  Click the source table node to display its properties in the side panel, and review the properties in the *General* section:
+
+    ****
+
+
+    <table>
+    <tr>
+    <th valign="top">
+
+    Property
+
+
+
+    </th>
+    <th valign="top">
+
+    Description
+
+
+
+    </th>
+    </tr>
+    <tr>
+    <td valign="top">
+
+    Business Name / Technical Name
+
+
+
+    </td>
+    <td valign="top">
+
+    Information to identify the source table.
+
+
+
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+
+    Alias
+
+
+
+    </td>
+    <td valign="top">
+
+    You can specify an SQL alias for the table if required.
+
+
+
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+
+    Distinct Values
+
+
+
+    </td>
+    <td valign="top">
+
+    Indicates whether the source table uses SELECT DISTINCT statements to return only distinct values.
+
+
+
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+
+    Delta Capture
+
+
+
+    </td>
+    <td valign="top">
+
+    Indicates whether the delta capture setting is enabled for a table. For more information, see [Capturing Delta Changes in Your Local Table](capturing-delta-changes-in-your-local-table-154bdff.md).
+
+
+
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+
+    Status
+
+
+
+    </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).
+
+
+
+    </td>
+    </tr>
+    </table>
+
+    If the delta capture setting is enabled for a table, you can view the *Delta Settings* section. By default, the option *Delta Capture* is selected. This option loads delta changes to the target table. If required, you can select the option *All Active Records* to load the full set of data to the target table.
+
+    **Additional Information About Loading Delta Changes**
+
+    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"></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/...g-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-target-ab490fb.md b/...g-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-target-ab490fb.md
@@ -25,7 +25,9 @@ Select a target \(connection and container\) to define the target environment fo
 
 2.  Select the relevant one for your use case.
 
-3.  If you replicate to the local repository \(SAP Datasphere\), the target container is automatically defined as the space you are in. For any other target, click *Browse target container*. A list of available containers appears. Select the relevant one for your use case.
+3.  If you replicate to the local repository \(SAP Datasphere\), the target container is automatically defined as the space you are in, and the data is replicated to a local table. If you want to use load type *Initial and Delta*, the local table must support delta capturing. For more information, see [Capturing Delta Changes in Your Local Table](capturing-delta-changes-in-your-local-table-154bdff.md).
+
+    For any other target, click *Browse target container*. A list of available containers appears. Select the relevant one for your use case.
 
     To narrow down the selection, start typing a part of the container name in the *Search* field.
 

diff --git a/...-and-Preparing-Data-in-the-Data-Builder/add-or-create-a-target-table-0950746.md b/...-and-Preparing-Data-in-the-Data-Builder/add-or-create-a-target-table-0950746.md
@@ -0,0 +1,144 @@
+<!-- loio0950746ab4444e5ca6a665ee1b0380a1 -->
+
+<link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
+
+# Add or Create a Target Table
+
+A transformation flow writes data to a target table. You can create a new target table or use an existing one.
+
+
+
+## Procedure
+
+1.  Add a target table to the transformation flow in one of the following ways:
+
+    -   Click the *Create New Table* button.
+
+        The target table is added to your transformation flow, and the *Properties* panel for the table appears. Enter a business name and a technical name for your target table. When you enter a business name, the system automatically suggests a corresponding technical name, but you can change the technical name if required.
+
+    -   Drag an existing table from the *Repository*, and drop it onto the *Target* node.
+
+
+2.  Click the target node to display its properties in the side panel, and review the properties in the *General* section:
+
+
+    <table>
+    <tr>
+    <th valign="top">
+
+    Property
+
+
+
+    </th>
+    <th valign="top">
+
+    Description
+
+
+
+    </th>
+    </tr>
+    <tr>
+    <td valign="top">
+
+    Business Name / Technical Name
+
+
+
+    </td>
+    <td valign="top">
+
+    Information to identify the target table.
+
+
+
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+
+    Status
+
+
+
+    </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).
+
+
+
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+
+    Truncate
+
+
+
+    </td>
+    <td valign="top">
+
+    If the value of the *Truncate* option is *Yes*, when you start the transformation flow, the system deletes the table content, but leaves the table structure intact and fills it with the relevant data from the source table.
+
+    If not, the system inserts new data records after the existing data in the target table. For data records that already exist in the target table and have been changed in the source, the system updates the target records with the changed data from the source using the UPSERT mode.
+
+
+
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+
+    Delta Capture
+
+
+
+    </td>
+    <td valign="top">
+
+    Indicates whether the delta capture setting is enabled for the table. For more information, see [Capturing Delta Changes in Your Local Table](capturing-delta-changes-in-your-local-table-154bdff.md).
+
+
+
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+
+    Delta Capture Table Name
+
+
+
+    </td>
+    <td valign="top">
+
+    \[read-only\] The delta capture table name. The system displays this field if the delta capture setting is enabled for the table. For more information, see [Capturing Delta Changes in Your Local Table](capturing-delta-changes-in-your-local-table-154bdff.md).
+
+
+
+    </td>
+    </tr>
+    </table>
+
+3.  In the *Mappings* section, review the mappings of incoming columns to the target table columns.
+
+    -   When you connect any operator to the target table, each incoming columns that has the same name and a compatible data type with a column in the target table is automatically mapped to it.
+
+    -   You can manually map an incoming columns with a target table column that has a compatible datatype by dragging the column from the left list and dropping it onto the appropriate column in the right list.
+
+        > ### Note:  
+        > For the data type "string", incoming columns and target table columns do not need to be the same length. It is possible to map incoming columns to target table columns that have a greater length.
+
+    -   To delete a mapping, select it, and click *Delete*. To delete all mappings, *Remove all Mappings.*
+
+    -   You can, at any time, click <span class="FPA-icons"></span> \(Auto Map\) to relaunch automapping based on names and datatypes.
+
+
+4.  In the *Columns* section, view the columns of the target table. To check the data type of a column, hover over it and click <span class="FPA-icons"></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
@@ -25,6 +25,9 @@ Add a target table to write data to. You can only have one target table in a dat
 
 
 
+    > ### Note:  
+    > Local table with delta capture on can't be used as target table.
+
 2.  Click and drag the port on the right of the last operator in your data flow and drop it onto the target table.
 
     A flow is created between the operator and the target table.