feedback changes.

Author: mohitmakhija1

articles/sap/business-process-solutions/currency-conversion.md

@@ -1,5 +1,6 @@
 ---
-title: Currency Conversion in Business Process Solutions
+title: Currency conversion
+titleSuffix: Business Process Solutions
 description: Learn how to do currency conversion in Business Process Solutions.
 author: mimansasingh
 ms.service: sap-on-azure
@@ -9,7 +10,7 @@ ms.date: 02/23/2026
 ms.author: mimansasingh
 ---
 
-# Currency Conversion in Business Process Solutions
+# Currency conversion in Business Process Solutions
 
 In SAP systems, transactions can be recorded in various currencies, creating a need for optional currency conversion capabilities. Most financial data already includes amounts in both the Transaction Currency and Company Code Currency, ensuring alignment between Business Process Solutions and the SAP system without extra conversion steps. Most financial data already includes amounts in both the **Transaction Currency** and **Company Code Currency**, ensuring alignment between Business Process Solutions and the SAP system without another conversion steps. 
 
@@ -21,11 +22,11 @@ We use currency conversion rates from SAP systems available in CDS View I_EXCHAN
 
 1. The I_EXCHANGERATERAWDATA view doesn't contain exchange rates for every day. Instead it contains the Validity Start Date column, which indicates the new exchange rate starting from a given date. The notebook forward-fill all missing dates using the Validity Start Date column.
 
-2. Business Process Solutions provides two levels of exchange rate granularity, allowing customers to choose between higher accuracy and better performance: 
+1. Business Process Solutions provides two levels of exchange rate granularity, allowing customers to choose between higher accuracy and better performance: 
 
-   1. **Fiscal period average exchange rates** – Optimize reporting performance by reducing the number of exchange rate lookups and calculations (table: I_EXCHANGERATERAWDATA_FISCALPERIOD) 
-   2. **Daily exchange rates** – Improve accuracy by capturing short-term currency fluctuations (table: I_EXCHANGERATERAWDATA_DAILY) 
+   1. **Fiscal period average exchange rates** – Optimize reporting performance by reducing the number of exchange rate lookups and calculations (table: I_EXCHANGERATERAWDATA_FISCALPERIOD)
+   1. **Daily exchange rates** – Improve accuracy by capturing short-term currency fluctuations (table: I_EXCHANGERATERAWDATA_DAILY)
 
-3. Exchange rates are computed separately for Fiscal Period and Company Code combinations.
+1. Exchange rates are computed separately for Fiscal Period and Company Code combinations.
 
-To ensure optimal performance in Power BI reports, we recommend using the average exchange rates per fiscal period. Instead of performing currency conversion at the row level, the report first groups all amounts by currency and fiscal period, then aggregates the values within each group before applying the fiscal period’s average exchange rate. This approach significantly reduces the computational overhead compared to converting each transaction individually. By eliminating row-level currency calculations, report performance is dramatically improved while maintaining reliable approximations of financial data.
+To ensure optimal performance in Power BI reports, we recommend using the average exchange rates per fiscal period. Instead of performing currency conversion at the row level, the report first groups all amounts by currency and fiscal period, then aggregates the values within each group before applying the fiscal period’s average exchange rate. This approach significantly reduces the computational overhead compared to converting each transaction individually. By eliminating row-level currency calculations, report performance is dramatically improved while maintaining reliable approximations of financial data.

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

@@ -1,5 +1,6 @@
 ---
 title: Monitoring data extraction in Azure Data Factory
+titleSuffix: Business Process Solutions
 description: Learn how to monitor data extraction in Azure Data Factory in Business Process Solutions.
 author: mimansasingh
 ms.service: sap-on-azure
@@ -23,11 +24,13 @@ Once the field metadata is processed, the **System Lookup** pipeline (p_s2s_syst
 2. Extracting data from dimensions (p_s2s_dimension_extract)
 
 These two jobs run sequentially, with the dimension extraction pipeline dependent on the successful completion of the fact extraction pipeline. If there's an issue with extracting facts, the subsequent dimension processing doesn't start.
+
     :::image type="content" source="./media/monitoring-data-extraction/data-extraction-steps.png" alt-text="Screenshot showing different steps to extract data." lightbox="./media/monitoring-data-extraction/data-extraction-steps.png":::
 
 Each pipeline executes a series of actions. If any step encounters an error, the entire pipeline registers a failure. This failure is reported back to the initiating pipelines, including System Lookup and Orchestration Master. Additionally, a failure in one pipeline prevents subsequent pipelines from starting. For example, a problem in the fact extraction step blocks the dimension extraction process.
 
 Below is an example of the monitoring view when a data processing step fails:
+
     :::image type="content" source="./media/monitoring-data-extraction/data-processing-failure.png" alt-text="Screenshot showing monitoring view if data processing fails." lightbox="./media/monitoring-data-extraction/data-processing-failure.png":::
 
 Each pipeline automatically determines the required actions based on the CDS View metadata. The following steps outline the logic:
@@ -38,6 +41,7 @@ Each pipeline automatically determines the required actions based on the CDS Vie
 4. **Convert to Delta**: Processes data extracted via the **SAP Table connector** and pushes it to the lakehouse. Applicable only if you process the initial extraction using the SAP Table connector.
 
 Here's an example of the dimension extraction pipeline encountering some failed activities. Failures in specific actions can cascade back to the initiating actions, like pipeline failures. The For-Each loop iterates through all objects set for extraction, and the Select Connector action determines the appropriate processing steps based on the CDS View metadata. Generally, each issue will manifest as two failed actions.
+
     :::image type="content" source="./media/monitoring-data-extraction/dim-pipeline-failure.png" alt-text="Screenshot showing dimension extraction pipeline failure." lightbox="./media/monitoring-data-extraction/dim-pipeline-failure.png":::
 
 When an extraction process fails, the first step is to review the error details. The nature of the error guides the corrective actions required.
@@ -56,13 +60,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.
+- **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. If the CDS View doesn't exists in your system remove the failed table from the dataset to resolve the issue.
 
    :::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.
+- **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.
+- **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-fabric-data-extraction-processing.md

@@ -1,5 +1,6 @@
 ---
 title: Monitoring data extraction and processing in Fabric
+titleSuffix: Business Process Solutions
 description: Learn how to monitor data extraction and processing in Fabric in Business Process Solutions.
 author: mimansasingh
 ms.service: sap-on-azure
@@ -41,9 +42,13 @@ 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.
+
     :::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.
 
 ## Check logs for a processing notebook executed from pipeline
@@ -52,11 +57,16 @@ When you want to check the logs for a notebook that was executed as a part of pi
 
 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.
+
     :::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. 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

articles/sap/business-process-solutions/toc.yml

@@ -23,9 +23,9 @@ items:
       href: run-extraction-data-processing.md
     - name: Configure insights
       href: configure-insights.md
-    - name: Currency Conversion
+    - name: Currency conversion
       href: currency-conversion.md
-    - name: Monitoring Data Extraction and Processing
+    - name: Monitoring data extraction and processing
       items:
       - name: Monitor in Azure Data Factory
         href: monitor-data-extraction.md