Creating reports is usually a seamless process. However, sometimes challenges do arise, and the user may need to troubleshoot the problem.
The following sections list some common reporting issues that can occur from time to time and highlight methods explaining how you can solve them.
Unable to Execute
The first common troubleshooting scenario is Unable to Execute.
This occurs when:
- There is an invalid join or an error in the data field. For example, if a report includes a formula that divides by 0 (which is an erroneous formula).
- If the report contains a data field from a module that isn’t associated with other modules in the report.
You might try to resolve this by doing the following:
- Evaluating the data fields to ensure there are no errors.
- Remove all fields for all but one module and then slowly add fields back in from other modules, one at a time – in case it was an invalid join causing the issue.
- If you cannot resolve the issue with these methods, you can submit a support case.
Too Many Rows Returned
This is caused when too much data is being pulled in the report.
In this case, you’re trying to pull a report of all workers. If there are too many workers in the system, too many rows are being pulled, thus an error.
You can resolve this by:
- Adding filters or narrowing the focus, such as pulling a report of workers in the past few months rather than the past five years.
- You can also evaluate the report and update the business goal.
Time Out
This occurs when the data is too large or too complex.
For example, let’s say the problem is that the fields are not optimized. This report only has one field from the Supplier module, and all of the other ones are from the invoice module.
You can resolve this issue by:
- Adjusting filters
- Using a smaller data set
- Reviewing the fields and modules
If you still have issues, you can contact SAP Fieldglass Support for assistance.
User Cannot See or Edit the Report
This will happen when a User is not associated to a report folder or the User does not have role permissions for a particular module.
You can resolve this issue by:
- Resetting access setting to Public and Editable
- Ensuring user is associated to the appropriate report folder
- Checking to see that the user has at least View permission for all modules in the report
- Making sure the user has the Manage permission for the Report module
Missing Data
This is caused when the User does not have visibility to the foundational data associations, like Business Unit, Cost Center, or Site.
There may also be an issue with the user role data view, and with the visibility in the reporting.
Additionally, the filter selection may be causing the problem or there could be an error with the relationship between the columns and the base module.
You can resolve this issue by:
- Making sure that the user has visibility to the data in the application
- Reviewing the filter section to ensure the correct one is selected
- Accounting for the transactional flow related to the base module chosen for the report
Multiple Rows
The cause of this issue is that the Scope filter selection is not restrictive enough.
You can resolve this issue by changing the Work Order Scope filter to only display the Latest Confirmed work order, rather than All.