Skip to content

Commit 01f9017

Browse files
committed
final edits
1 parent b480ad5 commit 01f9017

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

articles/data-factory/sap-change-data-capture-prepare-linked-service-source-dataset.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,7 @@ To create a Data Factory copy activity that uses an SAP ODP (preview) data sourc
6464
1. Select your SAP ODP linked service for the new source dataset and set the rest of the properties for the linked service:
6565

6666
1. In **Connect via integration runtime**, select your self-hosted integration runtime.
67+
6768
1. In **Context**, select the context of the ODP data extraction. Here are some examples:
6869

6970
- To extract ABAP CDS views from S/4HANA, select **ABAP_CDS**.
@@ -128,7 +129,7 @@ To create a Data Factory copy activity that uses an SAP ODP (preview) data sourc
128129

129130
### Set up the source sink
130131

131-
1. In the Data Factory copy activity, select the **Sink** tab. Select an existing sink dataset or create a new one for a data store like Azure Blob Storage or Azure Data Lake Storage Gen2.
132+
- In the Data Factory copy activity, select the **Sink** tab. Select an existing sink dataset or create a new one for a data store like Azure Blob Storage or Azure Data Lake Storage Gen2.
132133

133134
To increase throughput, you can enable the Data Factory copy activity to concurrently extract data packages that your SAP system produces in the ODQ. You can enforce all extraction processes to immediately write them to the sink in parallel. For example, if you use Data Lake Storage Gen2 as a sink, in **File path** for the sink dataset, leave **File name** empty. All extracted data packages will be written as separate files.
134135

articles/data-factory/sap-change-data-capture-prerequisites-configuration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ SAP Landscape Transformation Replication Server (SLT) is a database trigger-enab
9090

9191
1. In **Queue Alias**, enter the queue alias to use to select the context of your data extractions via ODP in Data Factory. Use the format `SLT-<your queue alias>`.
9292

93-
:::image type="content" source="media/sap-change-data-capture-solution/sap-cdc-slt-configurations.png" alt-text="Screenshot of the SAP SLT configuration dialog.":::
93+
:::image type="content" source="media/sap-change-data-capture-solution/sap-cdc-slt-configurations.png" alt-text="Screenshot of the SAP SLT configuration dialog.":::
9494

9595
For more information about SLT configurations, see [Replicating Data to SAP Business Warehouse](https://help.sap.com/docs/SAP_LANDSCAPE_TRANSFORMATION_REPLICATION_SERVER/969cf5258b964a5ba56380da648ac84e/737e69568fb4c359e10000000a441470.html).
9696

0 commit comments

Comments
 (0)