Skip to content

Commit d458d45

Browse files
authored
Merge pull request #311679 from mohitmakhija1/users/momakhij/troubleshooting_page
added new trouble shooting page for business process solutions
2 parents 2ac80ed + c1a7346 commit d458d45

6 files changed

Lines changed: 55 additions & 1 deletion

File tree

33 KB
Loading
92.2 KB
Loading
10.4 KB
Loading
269 KB
Loading

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,4 +24,6 @@ items:
2424
- name: Configure insights
2525
href: configure-insights.md
2626
- name: Attestation Document
27-
href: attestation.md
27+
href: attestation.md
28+
- name: Troubleshooting common issues
29+
href: troubleshooting.md
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
title: Troubleshooting common issues
3+
description: Identify and track common Business Process Solutions issues and workarounds.
4+
author: mohitmakhija1
5+
ms.author: momakhij
6+
ms.service: sap-on-azure
7+
ms.subservice: center-sap-solutions
8+
ms.topic: troubleshooting
9+
ms.date: 02/11/2026
10+
---
11+
12+
# Troubleshooting known issues
13+
14+
Within the Business Process Solutions, we recognize that there are many moving parts. This article is intended to help you troubleshoot known issues that you can encounter. Use this article to quickly diagnose and remediate known issues. Each section summarizes symptoms, root cause, and the exact steps to fix and validate.
15+
16+
## Issue with semantic model refresh
17+
18+
For some semantic models, the refresh might fail with the following error message:
19+
Data source error: Expression.Error: The column 'MANDT' of the table wasn't found. MANDT. Microsoft.Data.Mashup.ErrorCode = 10224.
20+
21+
:::image type="content" source="./media/troubleshooting/semantic-model-refresh-error.png" alt-text="Screenshot showing the semantic model refresh error." lightbox="./media/troubleshooting/semantic-model-refresh-error.png":::
22+
23+
To resolve this issue, you need to refresh this semantic model using Power BI desktop. Follow these steps:
24+
25+
1. Install the latest version of Power BI desktop from Microsoft store.
26+
2. Navigate to your workspace.
27+
3. Open the semantic model that's failing to refresh. Click on File -> Download this file.
28+
:::image type="content" source="./media/troubleshooting/download-semantic-model.png" alt-text="Screenshot showing how to download the semantic model." lightbox="./media/troubleshooting/download-semantic-model.png":::
29+
4. Open the downloaded file in Power BI desktop and click on Refresh. You might be prompted to sign in. Once you sign in, the refresh should complete successfully.
30+
5. After the refresh is successful, publish the semantic model back to the workspace. Click on the publish button in Power BI desktop and select the workspace to publish.
31+
32+
## Gold view creation notebook failing for vtPURGDOCUMENTCATEGORYTEXT view creation
33+
34+
When you run the gold view creation notebook for the first time from the orchestration pipeline, it might fail while creating the vtPURGDOCUMENTCATEGORYTEXT view with the following Error Message:
35+
36+
'Notebook execution failed at Notebook service with http status code - '200', please check the Run logs on Notebook, additional details - 'Error name - ProgrammingError, Error value - ('ID - 43bd12c2-6e77-4466-a33e-25facde8939d | traceid = 729aa4f3-f4b1-4046-9717-466d58a41af9 42S02', "[42S02] [Microsoft][ODBC Driver 18 for SQL Server][SQL Server] Invalid object name 'I_PURGDOCUMENTCATEGORYTEXT'. (208) (SQLExecDirectW)")''
37+
38+
This error occurs because the view vtPURGDOCUMENTCATEGORYTEXT depends on the tables SAPLANGUAGE, I_PURGDOCUMENTCATEGORYTEXT, I_PURCHASINGDOCUMENTCATEGORY, but the check for the existence of these tables is incorrect in the notebook.
39+
40+
To solve this issue, you can follow these steps:
41+
42+
1. Navigate to your workspace.
43+
2. Open the notebook **bps_gold_view_creation**.
44+
:::image type="content" source="./media/troubleshooting/gold-view-notebook.png" alt-text="Screenshot showing how to open the bps_gold_view_creation notebook." lightbox="./media/troubleshooting/gold-view-notebook.png":::
45+
3. Open the search bar in the notebook and search for 'vtPURGDOCUMENTCATEGORYTEXT'.
46+
4. You find a cell with the SQL code that creates the view. In that cell, you need to change the code to check for the existence of the tables SAPLANGUAGE, I_PURGDOCUMENTCATEGORYTEXT, I_PURCHASINGDOCUMENTCATEGORY. In the following image you can see the part of the code that needs to be changed:
47+
:::image type="content" source="./media/troubleshooting/gold-view-notebook-error.png" alt-text="Screenshot showing the SQL code to create the vtPURGDOCUMENTCATEGORYTEXT view." lightbox="./media/troubleshooting/gold-view-notebook-error.png":::
48+
49+
## Next steps
50+
51+
- [Introduction to Business Process Solutions](about-business-process-solutions.md)
52+
- [Run extraction and data processing in Business Process Solutions](run-extraction-data-processing.md)

0 commit comments

Comments
 (0)