Add images for monitoring data extraction and processing in Azure Data Factory and Fabric

Author: mohitmakhija1

articles/sap/business-process-solutions/media/monitoring-data-extraction/view-sap.png

@@ -57,8 +57,12 @@ This error indicates that the specified CDS View doesn't support delta extractio
 There are three possible root causes for this issue.
 
 1. **Verify the view is available in your SAP release** - To check whether the CDS View is available, you need to examine the view annotations. Open transaction SE16n and access the table DDHEADANNO, which stores all CDS View annotations. Enter the CDS View name in the STRUCOBJN field. Keep in mind, the error message shows the SQL View Name (ODPName) and not the CDS View Name. If the system returns list of annotations, the CDS View exists and you can proceed to step (b) for troubleshooting.
+
    :::image type="content" source="./media/monitoring-data-extraction/view-sap.png" alt-text="Screenshot showing view is available in SAP release." lightbox="./media/monitoring-data-extraction/view-sap.png":::
+
 1. If the CDS View doesn’t exists in your system remove the failed table from the dataset to resolve the issue.
 1. **Verify if the view is extractable** - Not all views defined in the system support extraction using the SAP CDC connector. To determine if a view can be extracted, review the list of annotations in the table DDHEADANNO and check for the annotation ANALYTICS.DATAEXTRACTION.ENABLED. This annotation confirms that the view is extractable using the ODP framework and the SAP CDC connector. If the required annotation is missing, you should switch the connector used for data extraction to SAP Table. This can be achieved by changing the context of the CDS View to SAP Table.
+
    :::image type="content" source="./media/monitoring-data-extraction/view-sap-extractable.png" alt-text="Screenshot showing if view is extractable." lightbox="./media/monitoring-data-extraction/view-sap-extractable.png":::
+
 1. **Check if you have the right authorizations** - Another common reason for extraction failures is missing authorizations in the source SAP system. Ensure that all required data sources are included in the SAP profile assigned to the user and pay special attention to the authorization objects S_RS_CDS_X and S_DHCDCCDS. To troubleshoot authorization issues, run the extraction using the test report RODPS_REPL_TEST with the same user defined in Business Process Solutions. After the test, execute transaction SU53 to review any missing authorizations. This process helps identify gaps that might be causing the extraction to fail.

articles/sap/business-process-solutions/monitor-data-extraction.md

@@ -38,23 +38,25 @@ The following table contains details about the extraction and processing pipelin
 Once a pipeline is triggered, the pipeline run history allows us to view both recent and historical executions. This helps us to understand how the pipeline behaved during a specific run and whether all activities completed successfully.
 
 Use the following steps to check the run history for a pipeline
-1.	Navigate to the pipeline in Fabric
-1.	Select "View run history" to see execution status, duration, and completion details for each run.
+
+1. Navigate to the pipeline in Fabric
+1. Select "View run history" to see execution status, duration, and completion details for each run.
     :::image type="content" source="./media/monitoring-fabric-data-extraction-and-processing/fabric-monitoring-view-run-history.png" alt-text="Screenshot showing view run history button." lightbox="./media/monitoring-fabric-data-extraction-and-processing/fabric-monitoring-view-run-history.png":::
 1. From the dialog box, open the execution you want to check.
     :::image type="content" source="./media/monitoring-fabric-data-extraction-and-processing/fabric-monitoring-execution-logs.png" alt-text="Screenshot showing list of execution logs." lightbox="./media/monitoring-fabric-data-extraction-and-processing/fabric-monitoring-execution-logs.png":::
-1.	Once you select the activity name you should be able to see all the steps that were executed as a part of pipeline execution and you can check the input, output and error message for each step.
+1. Once you select the activity name you should be able to see all the steps that were executed as a part of pipeline execution and you can check the input, output and error message for each step.
 
 ## Check logs for a processing notebook executed from pipeline
 
 When you want to check the logs for a notebook that was executed as a part of pipeline, follow the instructions
-1.	Open the pipeline run history and select the run that you want to check, follow the instructions mentioned in the previous section.
-1.	Once you open the pipeline snapshot, you should be able to see the notebook inside the pipeline.
+
+1. Open the pipeline run history and select the run that you want to check, follow the instructions mentioned in the previous section.
+1. Once you open the pipeline snapshot, you should be able to see the notebook inside the pipeline.
     :::image type="content" source="./media/monitoring-fabric-data-extraction-and-processing/fabric-monitoring-notebook.png" alt-text="Screenshot showing notebooks inside pipeline." lightbox="./media/monitoring-fabric-data-extraction-and-processing/fabric-monitoring-notebook.png":::
-1.	Select the activity name to open the details and then from the dialog box open the Notebook snapshot.
+1. Select the activity name to open the details and then from the dialog box open the Notebook snapshot.
     :::image type="content" source="./media/monitoring-fabric-data-extraction-and-processing/fabric-monitoring-notebook-snapshot.png" alt-text="Screenshot showing notebook snapshot." lightbox="./media/monitoring-fabric-data-extraction-and-processing/fabric-monitoring-notebook-snapshot.png":::
-1.	The notebook snapshot opens in a new browser tab. Once the page is loaded, you should be able to see the notebook snapshot and the output for each cell. 
-1.	Navigate to the cell that failed, and check the output of the cell to view the failure message.
+1. The notebook snapshot opens in a new browser tab. Once the page is loaded, you should be able to see the notebook snapshot and the output for each cell. 
+1. Navigate to the cell that failed, and check the output of the cell to view the failure message.
     :::image type="content" source="./media/monitoring-fabric-data-extraction-and-processing/fabric-monitoring-notebook-failure.png" alt-text="Screenshot showing failed notebooks and errors." lightbox="./media/monitoring-fabric-data-extraction-and-processing/fabric-monitoring-notebook-failure.png":::
 
 ## Next steps