Skip to content

Commit 902d095

Browse files
authored
Update simple-report.md
1 parent f711ea3 commit 902d095

1 file changed

Lines changed: 18 additions & 17 deletions

File tree

support/dynamics-365/finance/financial-reporting/simple-report.md

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,17 @@ ms.custom: sap:Financial reporting and management reporter\Issues with report de
2727

2828
A practical way to troubleshoot report design or missing data issues effectively is to simplify the process and control variables. Focusing on a specific scope is often more manageable than diagnosing an entire report. Start by creating the smallest possible reproduction of the issue and make changes one at a time. In some cases, manually recreating a report or starting over with the design helps uncover design flaws or process bugs.
2929

30-
To troubleshoot report issues, confirm that following:
31-
- Create a minimal report to troubleshoot the issue.
32-
- Check that your data mart integration is current and healthy.
30+
To troubleshoot report issues, confirm that following:
31+
- Check that your data mart integration is current and healthy.
32+
- Create a minimal report to troubleshoot the issue.
33+
34+
### Check the data mart state
35+
To check the state of your data mart, follow these steps:
36+
1. In **Report designer**, go to **Tools** > **Integration status**.
37+
2. Check that the **Status** isn't **Failed** and the **Last Runtime** date is after you created your data. Usually, the General Ledger transactions are tracked to **Fact map**. Occasionally, due to system load and data volume, data mart integration can take longer. You may need to wait more than one hour for larger data changes to complete integration into data mart.
38+
3. To check more detailed statistics, go to **Tools** > **Reset data mart**. DO NOT reset the data mart.
39+
If there are transactions with six or more attempts, there could be data integrity issues. Having amounts here doesn’t mean data is missing from your report, but it can be a source of missing data. Work with Microsoft support to determine the cause of the stuck data.
40+
4. If there are any **Misaligned main account** categories, reports based on account categories could report incorrect amounts.
3341

3442

3543
## Create a report for troubleshooting
@@ -39,28 +47,21 @@ To create a report to troubleshoot report issues, follow these steps:
3947
3. Set the **Detail level** to **Financial**, **Account**, and **Transaction**.
4048
4. Remove any other special options.
4149
5. In the row definition, include a single row with a single account or dimension combination.
42-
- No wildcard or ranges.
43-
- No modifiers or calculations to start.
50+
- No wildcard or ranges.
51+
- No modifiers or calculations to start.
4452
6. In the column definition, include a single **DESC** and **FD** column for a specific period.
45-
- Remove all modifiers for the column.
53+
- Fiscal year: 2025 (specific year)
54+
- Period: 11 (specific period)
55+
- Periods covered: PERIODIC
56+
- Remove all modifiers for the column.
4657
7. This should display a report with a single cell of data.
4758
8. Verify the report is working as expected.
48-
9. Add one modification at a time if your issue includes specific design requirements.
49-
a. For example: currency filter, attribute filter, year-to-date, or beginning balances.
59+
9. Add one modification at a time if your issue includes specific design requirements. For example: currency filter, attribute filter, year-to-date, or beginning balances.
5060
10. If the issue still exists, contact support and provide the following information:
5161
- Export the .tdbx files of the simplified and original reports.
5262
- Screenshots of the simplified report build block designs including rows and columns.
5363
- Excel export of the report output.
5464
- Reporting parameters: **Company**, **Reporting date**, and **Report name**.
5565
- Details about the incorrect amount and what the expected value is.
56-
57-
### Check the data mart state
58-
To check the state of your data mart, follow these steps:
59-
1. In **Report designer**, go to **Tools** > **Integration status**.
60-
2. Check that the **Status** isn't **Failed** and the **Last Runtime** date is after you created your data. Usually, the General Ledger transactions are tracked to **Fact map**. Occasionally, due to system load and data volume, data mart integration can take longer. You may need to wait more than one hour for larger data changes to complete integration into data mart.
61-
3. To check more detailed statistics, go to **Tools** > **Reset data mart**. DO NOT reset the data mart.
62-
If there are transactions with six or more attempts, there could be data integrity issues. Having amounts here doesn’t mean data is missing from your report, but it can be a source of missing data. Work with Microsoft support to determine the cause of the stuck data.
63-
4. If there are any **Misaligned main account** categories, reports based on account categories could report incorrect amounts.
64-
6566

6667

0 commit comments

Comments
 (0)